From mip6-bounces@ietf.org Thu Mar 01 00:25:17 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMdmi-00016k-A2; Thu, 01 Mar 2007 00:24:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMdmh-00016Y-LS
	for mip6@ietf.org; Thu, 01 Mar 2007 00:24:55 -0500
Received: from omta01ps.mx.bigpond.com ([144.140.82.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMdmf-0001zt-Jc
	for mip6@ietf.org; Thu, 01 Mar 2007 00:24:55 -0500
Received: from oaamta01ps.mx.bigpond.com ([124.191.178.123])
	by omta01ps.mx.bigpond.com with ESMTP id
	<20070301052430.UOBZ3746.omta01ps.mx.bigpond.com@oaamta01ps.mx.bigpond.com>;
	Thu, 1 Mar 2007 05:24:30 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta01ps.mx.bigpond.com
	with ESMTP
	id <20070301052430.OLY6229.oaamta01ps.mx.bigpond.com@PC20005>;
	Thu, 1 Mar 2007 05:24:30 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Chowdhury, Kuntal'" <kchowdhury@starentnetworks.com>,
	"'Vijay Devarapalli'" <vijay.devarapalli@azairenet.com>
Subject: RE: [Mip6] DSMIP6 solution and integrated bootstrap scenario
Date: Thu, 1 Mar 2007 16:24:23 +1100
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: <7CCD07160348804497EF29E9EA5560D7FBD9EB@exchtewks2.starentnetworks.com>
Thread-Index: Acdbltp0lYGXBpi4QU6U2KbWTEFALwAIsSMgAAHmQeA=
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070301052430.OLY6229.oaamta01ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6@ietf.org, 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



 > Let's not debate over specific cases like the IPv4 only 
 > access network
 > case that you cite. 

=> This specific case forms about 70% of the rationale for the DSMIPv6 work,
so I don't see how you can ignore it. 

   There is no guarantee that the DNS 
 > method for Home
 > Agent discovery will produce the information the MN is 
 > looking for all
 > the time. What will the MN do in a situation when it fails 
 > to get the HA
 > information from DNS? It will fallback on some other scheme, no?

=> May be and may be not. If there is a general failure in the DNS system
today, there is very little that you can do. If you want to do online
banking and DNS is not working then you simply won't do it. My point is,
there is very little that we can do to get around a DNS failure. Similarly,
if DHAAD failed in the basic spec, there is nothing that the MN can do
unless it is manually configured, which is always possible.

Hesham



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



From mip6-bounces@ietf.org Thu Mar 01 05:18:00 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMiLW-0008Ty-Lk; Thu, 01 Mar 2007 05:17:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMi9u-00074R-OG
	for mip6@ietf.org; Thu, 01 Mar 2007 05:05:10 -0500
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMi9s-0008KM-D0
	for mip6@ietf.org; Thu, 01 Mar 2007 05:05:10 -0500
Received: by ug-out-1314.google.com with SMTP id 72so308691ugd
	for <mip6@ietf.org>; Thu, 01 Mar 2007 02:05:07 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=L/o4Wzx9x8uVOoxsFvh41uz3fLxN3wmludddZWMp+yZ/2crLt+RTM7LQF8GU5g1XNc/9PbNuzyMIVviUOeJMnLdIR6weGPNhzQKFLCbcMuPqeIEY4aNk7/DdMTa2tRC+v/PXAjqoWvpyXzqElzKzM3CBZ5+tUWzSqjnmySk+Ho4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=BEN1OqsEnDKMV8PYVqnHuoPqlQMMHcn+eEbJxifyfCD+hQJnKE3W4IEUUg6kb8LXoDs60EVztE0aHAQvGPAsTWlb+mXhWhtIVIlDBRI4CFb2pEuesbpfqEKWYNJNSmiG9ArNHvdS0L6bXy717toVurYQHDks4HE+xzXyeBdglng=
Received: by 10.66.232.9 with SMTP id e9mr1881146ugh.1172743507558;
	Thu, 01 Mar 2007 02:05:07 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Thu, 1 Mar 2007 02:05:07 -0800 (PST)
Message-ID: <eaa74a7e0703010205k6114ef79yfe98679b94e078f8@mail.gmail.com>
Date: Thu, 1 Mar 2007 11:05:07 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
In-Reply-To: <45E61B54.3040303@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7CCD07160348804497EF29E9EA5560D7FBD9D4$0001@exchtewks2.starentnetworks.com>
	<45E61B54.3040303@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: mip6@ietf.org, Basavaraj.Patil@nokia.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On 3/1/07, Vijay Devarapalli <vijay.devarapalli@azairenet.com> wrote:
> Chowdhury, Kuntal wrote:
>
> >> Basavaraj.Patil@nokia.com wrote:
> >>> Okay.. I see your point now.
> >>> I agree that the DS-MIP6 I-D could either refer or mention the
> > methods
> >>> by which the MN can discover the HA.
> >> We can mention in the DS-MIPv6 spec, that if DS-MIPv6
> >> is being used in the integrated scenario, DHCPv6 may
> >> also be used for HA bootstrapping. Thats not a big
> >> deal.
> >>
> > [KC>] IMHO, section 2.1 should just point to the two bootstrapping
> > solutions (i.e. split and integrated) so that deployments utilizing
> > either of the bootstrapping solution can use DSMIP6.
>
> No. We need to show at least one mechanism for MN to
> obtain the IPv4 address of the HA. Otherwise we are
> left only with manual configuration of HA's IPv4
> address on the mobile node. We have three paragraphs
> in section 2.1 that describes how one can add the
> 'A' record for the HA in the DNS entry in addition to
> the 'AAAA' record and how the mobile node may obtain
> the HA's IPv4 address.
>

I agree with Vijay. Text on section 2.1 is needed since in
bootstrapping-split draft we refer only to IPv6 HA addresses and AAAA
records.

--Gerardo

> Kuntal, I don't have a problem listing DHCP also as
> one of the solutions for DS-MIPv6 HA discovery,  but
> we need to extend DHCPv4 (only DHCPv4 is available
> on an IPv4 access network) to return the IPv6 and
> IPv4 address of the DS-MIPv6 home agent. Please work
> on these extensions before demanding that we add
> references to other solutions.
>
> 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 Thu Mar 01 05:20:20 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMiOU-0004QC-6R; Thu, 01 Mar 2007 05:20:14 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMiBb-0003yF-2t
	for mip6@ietf.org; Thu, 01 Mar 2007 05:06:55 -0500
Received: from cluster-e.mailcontrol.com ([217.79.216.190])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HMiBY-0007RM-O8
	for mip6@ietf.org; Thu, 01 Mar 2007 05:06:55 -0500
Received: from rly20e.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly20e.srv.mailcontrol.com (MailControl) with ESMTP id
	l219oBYX025155
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Thu, 1 Mar 2007 09:50:15 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly20e.srv.mailcontrol.com (MailControl) id l219nSnY024725
	for mip6@ietf.org; Thu, 1 Mar 2007 09:49:28 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly20e-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l219mILq023793; Thu, 01 Mar 2007 09:49:28 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 0aca_12df31c4_c7d7_11db_90b7_0030482aac25;
	Thu, 01 Mar 2007 10:27:28 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030110454476-1043098 ;
	Thu, 1 Mar 2007 10:45:44 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.156,BAYES_00: -1.665,TOTAL_SCORE: -1.821
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Thu, 1 Mar 2007 10:50:37 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02
In-Reply-To: <59D7431DE2527D4CB0F1EFEDA5683ED301A4014E@SEHAN021MB.tcad.telia.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02
Thread-Index: AcdbHjoLeiuXo3N2R5a7UKacFyd9gAAOMPHQAAQ6KFAAHmD+IA==
References: <59D7431DE2527D4CB0F1EFEDA5683ED301A4014E@SEHAN021MB.tcad.telia.se>
To: <jouni.korhonen@teliasonera.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F0127840F@lan-ex-01.panasonic.de>
Date: Thu, 1 Mar 2007 10:42:36 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-06-90 (www.mailcontrol.com) on 10.69.1.130
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53
Cc: mip6@ietf.org, heejin.jang@samsung.com, basavaraj.patil@nokia.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jouni, Kuntal,

please see inline.

> -----Original Message-----
> From: jouni.korhonen@teliasonera.com=20
> [mailto:jouni.korhonen@teliasonera.com]=20
> Sent: Mittwoch, 28. Februar 2007 20:03
> To: Kilian.Weniger@eu.panasonic.com
> Cc: kchowdhury@starentnetworks.com; heejin.jang@samsung.com;=20
> mip6@ietf.org; basavaraj.patil@nokia.com
> Subject: RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02
>=20
> Hi Kilian,=20
>=20
> > -----Original Message-----
> > From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]=20
> > Sent: 28. helmikuuta 2007 18:55
> > To: Korhonen, Jouni /TeliaSonera Finland Oyj
> > Cc: Chowdhury, Kuntal; Heejin Jang; mip6@ietf.org; Basavaraj Patil
> > Subject: RE: [Mip6] WGLC:=20
> draft-ietf-mip6-bootstrapping-integrated-02
> >=20
> > Hi Kuntal, Jouni,=20
> >=20
> > yes, encoding the service in the Home Network Identifier=20
> > field would also be possible (probably with changes to=20
> > [HIOPT]). However, this has the danger of overloading the=20
> > semantics, since this would change the network identifier to=20
> > something like a "network+service" identifier. And don't we=20
>=20
> Hmmm.. lets be careful here. We are talking about only
> assigning different flavors of HA, nothing more.

If I understood the proposal we are talking about correctly, the FQDN is
used to negotiate a type of mobility service (e.g., DSMIP HA, MIP HA,
NEMO HA) and a corresponding protocol (e.g., DSMIP, MIP, NEMO). The MN
can request a specific mobility service/protocol by encoding into the HA
FQDN and the network would assign one by encoding into the HA FQDN. This
means that the MN would choose the mobility protocol based on the FQDN
received from the network. Is my understanding of the proposal correct?

>=20
> > need to standardize a format then, since the format for=20
> > encoding the service into the FQDN must be understood by the=20
> > MSA *and all ASPs*, right?=20
>=20
> No. We cannot really mandate specific format as we probably do it
> wrong anyway for other SDOs in their architectures. Just state that
> FQDNs can be used to assign different flavors of HAs if an operator=20
> or a SDO wishes to do so.

Kuntal said that "Using different FQDNs under the same operator domain
for differentiating between types of service nodes is already practised
in some 'relevant' SDOs." The point is "under the same operator domain".
I think the situation here is a bit different, since at least MN, MSP
(=3DASP if ASP assigns HA to MN) and MSA must all understand the same
format and ASP and MSA are different operator domains.=20

My point was that without specifying a encoding format, there might be
problems due to different understanding of the format (e.g., MN uses
different protocol than assigned by network). Not sure if the draft can
say something like "How the mobility protocol is encoded into the FQDN
is not specified, but the implementors must make sure that all involved
entities from different operator domains understand the same encoding".=20

BTW, the IAB document RFC4367 talks about problems of information
encoded in domain names and recommends that "the behavior of the
protocol machinery should never change based on the domain name of the
host."

Regards,

Kilian

>=20
> Cheers,
> 	Jouni
>=20
> >=20
> > Cheers,
> >=20
> > Kilian
> >=20
> > > -----Original Message-----
> > > From: Jouni Korhonen [mailto:jouni.korhonen@teliasonera.com]
> > > Sent: Mittwoch, 28. Februar 2007 10:55
> > > To: Kilian Weniger
> > > Cc: Chowdhury, Kuntal; Heejin Jang; mip6@ietf.org; Basavaraj Patil
> > > Subject: Re: [Mip6] WGLC:=20
> > draft-ietf-mip6-bootstrapping-integrated-02
> > >=20
> > > Hi Kilian,
> > >=20
> > >=20
> > > [snip]
> > >=20
> > > >> I heard at least one operator requesting such feature (and
> > > note that
> > > >> this is in principle possible with the HA discovery/assignment=20
> > > >> mechanisms defined in the split scenario bootstrapping=20
> draft). A
> > > > simple
> > > >> way to support this in the integrated scenario would be to add
> > > > something
> > > >> like a "type of requested HA service" field in the=20
> Home Network=20
> > > >> Identifier Option of the DHCP information request sent by
> > > the MN. The
> > > >> new field would encode the type of service, e.g., 0=3DMIPv6,
> > > 1=3DDS-MIPv6,
> > > >> 2=3DNEMO,...). Similarly, the Home Network Information
> > > Sub-option could
> > > >> include a "type of HA service" field to inform the MN
> > > about the type
> > > > of
> > >=20
> > > Good point imho.
> > >=20
> > > >> service supported by the HA offered in this option.=20
> > > However, since the
> > > >> AAAH wouldn't know the HA service requested by the MN,
> > > AAAH would need
> > > >> to send at least one HA address per supported service=20
> to the NAS.
> > > >>
> > > > [KC>] Alternatively, we can encode the Home Network
> > > Identifier (FQDN) as
> > > > ha.dsmip6.domain, ha.mip6.domain. This is possible with=20
> > the current=20
> > > > HIOPT I-D, no? From the AAAH perspective, it (AAAH) needs
> > > to send the HA
> > > > address - Service pair. The service can be indicated by the
> > > FQDN AVP. We
> > > > have the following AVPs in=20
> draft-ietf-dime-mip6-integrated-03.txt:
> > > >=20
> > > >                                 [ MIP6-Home-Agent-Address ]
> > > >                                 [ MIP6-Home-Agent-FQDN ]
> > >=20
> > > Using different FQDNs under the same operator domain for=20
> > > differentiating between types of service nodes is already=20
> > practised in=20
> > > some 'relevant'
> > > SDOs. In that sense I think it could be a good approach.=20
> Dime's I-D=20
> > > draft-ietf-dime-mip6-integrated allows a NAS to give hints=20
> > already to=20
> > > the AAAH using AVPs mentioned above and since we are about=20
> > to revise=20
> > > the Dime I-D this part could be clarified further.
> > >=20
> > > > Perhaps we can group them under a new AVP for service, e.g.
> > > > MIP6-Home-Agent-Info AVP. For RADIUS we can perhaps link=20
> > the MIP6-HA=20
> > > > Attribute and MIP6-HA-FQDN Attribute.
> > >=20
> > > There was also some other SDO asking for more generic 'ASP=20
> > info' AVP=20
> > > e.g. for local HA assignment. MAybe these could be combined.
> > > IMHO this
> > > discussion should be brought to Dime as well.
> > >=20
> > > Cheers,
> > > 	Jouni
> > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >> What do you think?
> > > >>
> > > >> Cheers,
> > > >>
> > > >> Kilian
> > > >>
> > > >>
> > > >> Panasonic R&D Center Germany GmbH
> > > >> 63225 Langen, Hessen, Germany
> > > >> Reg: AG Offenbach (Hessen) HRB 33974 Managing Director: Thomas=20
> > > >> Micke
> > > >>
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > >=20
> > >=20
> > >=20
> >=20
> >=20
> > Panasonic R&D Center Germany GmbH
> > 63225 Langen, Hessen, Germany
> > Reg: AG Offenbach (Hessen) HRB 33974
> > Managing Director: Thomas Micke
> >=20
> >=20
> >=20
>=20
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Thu Mar 01 05:24:17 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMiSI-0002g2-LZ; Thu, 01 Mar 2007 05:24:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMiDi-0007Mu-Q9
	for mip6@ietf.org; Thu, 01 Mar 2007 05:09:06 -0500
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMiDh-0000Cw-EX
	for mip6@ietf.org; Thu, 01 Mar 2007 05:09:06 -0500
Received: by ug-out-1314.google.com with SMTP id 72so309117ugd
	for <mip6@ietf.org>; Thu, 01 Mar 2007 02:09:04 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=iUlJUzE4XgfcDtaC/WjgSzAfIYRGMerLRPnlPBGA2hdYhiZEwTvFfMtI8nMU5LxYwGfGiHYophf66vDSHCNFhMtq8LgX481+q389i3KhcT/IVbKTzyGq6h736OP5Ct+V6yVRp0F78Fz1UxNMMNDYkcv7HOMM7GMvgDw3IrIb2ms=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=c3xGzZ8vAwkuaPeUEm9oB/fAUcw0ClArdhxm2ZFtN0sWJ2vnlShfeSG9YS9Q/kSHYzgavHBa3pQ6FuFigP0M9Sz5CeZB+Ds/Mgij5JXk3A1m8KRUfu4kWIUTD/V/L4evfl3t/LYFRaeYjK8fxSsMi+NPpvQJrodBJfBaNty0PLo=
Received: by 10.67.98.9 with SMTP id a9mr1896545ugm.1172743744598;
	Thu, 01 Mar 2007 02:09:04 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Thu, 1 Mar 2007 02:09:04 -0800 (PST)
Message-ID: <eaa74a7e0703010209v793c6199p7ba34a8aa087cb9d@mail.gmail.com>
Date: Thu, 1 Mar 2007 11:09:04 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBD9EB@exchtewks2.starentnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7CCD07160348804497EF29E9EA5560D7FBD9EB@exchtewks2.starentnetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mip6@ietf.org, 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

Kuntal,

we may add a reference to the integrated scenario draft, but you
cannot hide the fact that the solution defined for the integrated
scenario is based on DHCPv6 and cannot be used in IPv4-only access
networks (that are the main scope of this draft).

Therefore the reference to the integrated scenario solution, if added,
must come with a clear applicability statement that can be used only
in case the access network from which the MN is bootstrapping is
dual-stack.

--Gerardo

On 3/1/07, Chowdhury, Kuntal <kchowdhury@starentnetworks.com> wrote:
> Vijay,
>
> Let's not debate over specific cases like the IPv4 only access network
> case that you cite. There is no guarantee that the DNS method for Home
> Agent discovery will produce the information the MN is looking for all
> the time. What will the MN do in a situation when it fails to get the HA
> information from DNS? It will fallback on some other scheme, no?
>
> The MN needs to have fallback options regardless of which method is used
> i.e. DNS or DHCP or something else. There is no need in the DSMIP6 I-D
> to get into "preference" for mip6 bootstrap solution. Depending on the
> use case, access network capabilities (e.g. v4 or v6 or dual stack),
> deployment scenario, roaming agreement etc. either split or the
> integrated modes of mip6 bootstrapping will be used. The current draft
> is unduly biased towards DNS option and I am raising the point to fix
> that.
>
> I want the DSMIP6 I-D to be agnostic to the bootstrapping solution.
>
> -Kuntal
>
>
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Wednesday, February 28, 2007 6:16 PM
> > To: Chowdhury, Kuntal
> > Cc: Basavaraj.Patil@nokia.com; mip6@ietf.org
> > Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
> >
> > Chowdhury, Kuntal wrote:
> >
> > >> Basavaraj.Patil@nokia.com wrote:
> > >>> Okay.. I see your point now.
> > >>> I agree that the DS-MIP6 I-D could either refer or mention the
> > > methods
> > >>> by which the MN can discover the HA.
> > >> We can mention in the DS-MIPv6 spec, that if DS-MIPv6
> > >> is being used in the integrated scenario, DHCPv6 may
> > >> also be used for HA bootstrapping. Thats not a big
> > >> deal.
> > >>
> > > [KC>] IMHO, section 2.1 should just point to the two bootstrapping
> > > solutions (i.e. split and integrated) so that deployments utilizing
> > > either of the bootstrapping solution can use DSMIP6.
> >
> > No. We need to show at least one mechanism for MN to
> > obtain the IPv4 address of the HA. Otherwise we are
> > left only with manual configuration of HA's IPv4
> > address on the mobile node. We have three paragraphs
> > in section 2.1 that describes how one can add the
> > 'A' record for the HA in the DNS entry in addition to
> > the 'AAAA' record and how the mobile node may obtain
> > the HA's IPv4 address.
> >
> > Kuntal, I don't have a problem listing DHCP also as
> > one of the solutions for DS-MIPv6 HA discovery,  but
> > we need to extend DHCPv4 (only DHCPv4 is available
> > on an IPv4 access network) to return the IPv6 and
> > IPv4 address of the DS-MIPv6 home agent. Please work
> > on these extensions before demanding that we add
> > references to other solutions.
> >
> > 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 Thu Mar 01 06:17:34 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMjHK-0000Gu-NN; Thu, 01 Mar 2007 06:16:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMjHJ-0000GX-9X
	for mip6@ietf.org; Thu, 01 Mar 2007 06:16:53 -0500
Received: from av6-2-sn3.vrr.skanova.net ([81.228.9.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMjHH-000898-NV
	for mip6@ietf.org; Thu, 01 Mar 2007 06:16:53 -0500
Received: by av6-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id D990338077; Thu,  1 Mar 2007 12:16:48 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av6-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id A8AED3808A; Thu,  1 Mar 2007 12:16:48 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 6A68737E5C;
	Thu,  1 Mar 2007 12:16:45 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HMjHA-0000kH-La; Thu, 01 Mar 2007 12:16:44 +0100
Message-ID: <45E6B61E.6070707@levkowetz.com>
Date: Thu, 01 Mar 2007 12:16:46 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
References: <7CCD07160348804497EF29E9EA5560D7FBD9EB@exchtewks2.starentnetworks.com>
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBD9EB@exchtewks2.starentnetworks.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: kchowdhury@starentnetworks.com,
	vijay.devarapalli@azairenet.com, mip6@ietf.org,
	Basavaraj.Patil@nokia.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: mip6@ietf.org, 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="===============0811328918=="
Errors-To: mip6-bounces@ietf.org

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

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


on 2007-03-01 05:43 Chowdhury, Kuntal said the following:
> Vijay,
>=20
> Let's not debate over specific cases like the IPv4 only access network
> case that you cite.

Since the main reason for having DSMIPv6 is to be able to roam into IPv4
only access networks, this isn't a case to be discarded or ignored, it is=

*the* main use case that has to be supported.

> There is no guarantee that the DNS method for Home
> Agent discovery will produce the information the MN is looking for all
> the time. What will the MN do in a situation when it fails to get the H=
A
> information from DNS? It will fallback on some other scheme, no?
>=20
> The MN needs to have fallback options regardless of which method is use=
d
> i.e. DNS or DHCP or something else. There is no need in the DSMIP6 I-D
> to get into "preference" for mip6 bootstrap solution. Depending on the
> use case, access network capabilities (e.g. v4 or v6 or dual stack),
> deployment scenario, roaming agreement etc. either split or the
> integrated modes of mip6 bootstrapping will be used. The current draft
> is unduly biased towards DNS option and I am raising the point to fix
> that.
>=20
> I want the DSMIP6 I-D to be agnostic to the bootstrapping solution.=20

Then you'll have to provide all the components of the solution, as alread=
y
pointed out by Vijay earlier!  Those aren't in place today, so we can't
refer to them today.


	Henrik


> -Kuntal
>=20
>=20
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>> Sent: Wednesday, February 28, 2007 6:16 PM
>> To: Chowdhury, Kuntal
>> Cc: Basavaraj.Patil@nokia.com; mip6@ietf.org
>> Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
>>=20
>> Chowdhury, Kuntal wrote:
>>=20
>> >> Basavaraj.Patil@nokia.com wrote:
>> >>> Okay.. I see your point now.
>> >>> I agree that the DS-MIP6 I-D could either refer or mention the met=
hods
>> >>> by which the MN can discover the HA.
>> >> We can mention in the DS-MIPv6 spec, that if DS-MIPv6
>> >> is being used in the integrated scenario, DHCPv6 may
>> >> also be used for HA bootstrapping. Thats not a big
>> >> deal.
>> >>
>> > [KC>] IMHO, section 2.1 should just point to the two bootstrapping
>> > solutions (i.e. split and integrated) so that deployments utilizing
>> > either of the bootstrapping solution can use DSMIP6.
>>=20
>> No. We need to show at least one mechanism for MN to
>> obtain the IPv4 address of the HA. Otherwise we are
>> left only with manual configuration of HA's IPv4
>> address on the mobile node. We have three paragraphs
>> in section 2.1 that describes how one can add the
>> 'A' record for the HA in the DNS entry in addition to
>> the 'AAAA' record and how the mobile node may obtain
>> the HA's IPv4 address.
>>=20
>> Kuntal, I don't have a problem listing DHCP also as
>> one of the solutions for DS-MIPv6 HA discovery,  but
>> we need to extend DHCPv4 (only DHCPv4 is available
>> on an IPv4 access network) to return the IPv6 and
>> IPv4 address of the DS-MIPv6 home agent. Please work
>> on these extensions before demanding that we add
>> references to other solutions.
>>=20
>> Vijay
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


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

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

iD8DBQFF5rYeeVhrtTJkXCMRAtOIAJ4iDu+ZQdQG+Z8c2ytE5bk5wKDFdgCferZe
nDRNLQ08ry7hJR6n5j1mfCA=
=0x1j
-----END PGP SIGNATURE-----

--------------enig0B13096F0AD9DD2CBF3A4C8B--


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

--===============0811328918==--




From mip6-bounces@ietf.org Thu Mar 01 09:27:50 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMmFY-0005o0-Ee; Thu, 01 Mar 2007 09:27:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMmFX-0005mu-Dv
	for mip6@ietf.org; Thu, 01 Mar 2007 09:27:15 -0500
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMmFW-0003VN-17
	for mip6@ietf.org; Thu, 01 Mar 2007 09:27:15 -0500
Received: by ug-out-1314.google.com with SMTP id 72so350537ugd
	for <mip6@ietf.org>; Thu, 01 Mar 2007 06:27:11 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=TbxqMW7GyTPlxMn41ipTD/1qaRU0AoxcjYja3OKwLS6Sd4+LgmPtOYWK61rCPWOcUPUGKsNy0raZWcy5Q06gecGFWNSeQXDTJdahaMk/WyWnoT2tGvcHvd+0GQqDRgQBApe5kl8gvUYyH4NI3TXYHdhEF1oZtk9Z6Wvtfcc7sPA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=SwQpq1Wsha2c5uMEtCqQxXqsHqw4TvDbzSm6NbRWo7sFENE80FvgJ+wvVsGZUgvigB8TSxT7rSviqnStiYGQ7pIV65BkILqz55KLjnbptHs+Jb5ZwEyUGjlAFGMfL91wEkww3CqFjDz6szOU0rLquKcGhTDPwkvZTS/0aWWfJBo=
Received: by 10.67.106.3 with SMTP id i3mr2035785ugm.1172759231204;
	Thu, 01 Mar 2007 06:27:11 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Thu, 1 Mar 2007 06:27:11 -0800 (PST)
Message-ID: <eaa74a7e0703010627k2c64e311n7e7e1fd148489412@mail.gmail.com>
Date: Thu, 1 Mar 2007 15:27:11 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
In-Reply-To: <45E63AE1.4090708@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <459A5A6C.5070602@piuha.net>
	<eaa74a7e0702230640g722a28fcyc89360e69337c768@mail.gmail.com>
	<45E00DD3.1010701@piuha.net> <45E32B26.7050702@azairenet.com>
	<eaa74a7e0702270515v20f5be3ar91f97555539aa1b3@mail.gmail.com>
	<45E4D408.8050709@azairenet.com>
	<eaa74a7e0702280118g5881ffdy8684e84f63880dcb@mail.gmail.com>
	<45E63AE1.4090708@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On 3/1/07, Vijay Devarapalli <vijay.devarapalli@azairenet.com> wrote:
> Gerardo Giaretta wrote:
>
> >> > The AAA exchange may not be an additional one. Currently we are
> >> > discussing this issue in DIME WG (please, it would be great if you
> >> > take part on that discussion too); there are two options under
> >> > discussion, depending if the authorization for MIPv6 bootstrapping is
> >> > performed during the bootstrapping or after the first BU. The latter
> >> > option derives from the consideration that the MN is actually using
> >> > the MIP service only after the first BU.
> >>
> >> Why would a mobile node setup security associations with
> >> a home agent or send a BU to the home agent if not for
> >> mobility service?
> >>
> >
> > I agree for the BU.
> >
> > However, suppose the HA is acting also as VPN concentrator (or 3GPP
> > PDG or similar): there may be cases where the MN sets up a SA with
> > this box and then use it not for MIPv6. This is an issue in DIME
> > design: we are discussing when the authorization for MIPv6 should be
> > performed.
>
> That should be irrelevant. We are talking about DIME extensions
> to support MIPv6. If someone co-locates a PDG and a Mobile IPv6
> HA, why do we care? It is for them to figure out how to make it
> work. :)
>

Not sure about that. The MIP6 service must be explicitly authorized,
so the IKEv2 responder should understand that the IKEv2 exchange is
related to MIP6. Otherwise you need to authorize the service when the
first BU is sent.

--Gerardo

> Vijay
>

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



From mip6-bounces@ietf.org Thu Mar 01 10:31:45 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMnFT-0007vU-8p; Thu, 01 Mar 2007 10:31:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMnFR-0007sB-4g
	for mip6@ietf.org; Thu, 01 Mar 2007 10:31:13 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMnFN-0004Wd-WB
	for mip6@ietf.org; Thu, 01 Mar 2007 10:31:13 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 717909006C
	for <mip6@ietf.org>; Thu,  1 Mar 2007 10:31:06 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 09653-03 for <mip6@ietf.org>;
	Thu, 1 Mar 2007 10:31:00 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Thu,  1 Mar 2007 10:31:00 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 1 Mar 2007 10:31:00 -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] DSMIP6 solution and integrated bootstrap scenario
Date: Thu, 1 Mar 2007 10:31:00 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD9F6@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] DSMIP6 solution and integrated bootstrap scenario
Thread-Index: Acdb6agO1g6ZClZER3mQRGkRTgtvswALG3Qg
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 01 Mar 2007 15:31:00.0801 (UTC)
	FILETIME=[9DB10B10:01C75C16]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: mip6@ietf.org, 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: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> Sent: Thursday, March 01, 2007 4:09 AM
> To: Chowdhury, Kuntal
> Cc: Vijay Devarapalli; mip6@ietf.org; Basavaraj.Patil@nokia.com
> Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
>=20
> Kuntal,
>=20
> we may add a reference to the integrated scenario draft, but you
> cannot hide the fact that the solution defined for the integrated
> scenario is based on DHCPv6 and cannot be used in IPv4-only access
> networks (that are the main scope of this draft).
>=20
[KC>] Gerardo, I do not suggest that we hide any facts. So, stating
current limitation would be alright.


> Therefore the reference to the integrated scenario solution, if added,
> must come with a clear applicability statement that can be used only
> in case the access network from which the MN is bootstrapping is
> dual-stack.
>=20
[KC>] I have no problem with such statement. It will clarify the current
limitation with DHCPv6 operation in an IPv4 only ASP and at the same
time remove any confusion that DSMIP6 works with split scenario only.


> --Gerardo
>=20
> On 3/1/07, Chowdhury, Kuntal <kchowdhury@starentnetworks.com> wrote:
> > Vijay,
> >
> > Let's not debate over specific cases like the IPv4 only access
network
> > case that you cite. There is no guarantee that the DNS method for
Home
> > Agent discovery will produce the information the MN is looking for
all
> > the time. What will the MN do in a situation when it fails to get
the HA
> > information from DNS? It will fallback on some other scheme, no?
> >
> > The MN needs to have fallback options regardless of which method is
used
> > i.e. DNS or DHCP or something else. There is no need in the DSMIP6
I-D
> > to get into "preference" for mip6 bootstrap solution. Depending on
the
> > use case, access network capabilities (e.g. v4 or v6 or dual stack),
> > deployment scenario, roaming agreement etc. either split or the
> > integrated modes of mip6 bootstrapping will be used. The current
draft
> > is unduly biased towards DNS option and I am raising the point to
fix
> > that.
> >
> > I want the DSMIP6 I-D to be agnostic to the bootstrapping solution.
> >
> > -Kuntal
> >
> >
> > > -----Original Message-----
> > > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > > Sent: Wednesday, February 28, 2007 6:16 PM
> > > To: Chowdhury, Kuntal
> > > Cc: Basavaraj.Patil@nokia.com; mip6@ietf.org
> > > Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap
scenario
> > >
> > > Chowdhury, Kuntal wrote:
> > >
> > > >> Basavaraj.Patil@nokia.com wrote:
> > > >>> Okay.. I see your point now.
> > > >>> I agree that the DS-MIP6 I-D could either refer or mention the
> > > > methods
> > > >>> by which the MN can discover the HA.
> > > >> We can mention in the DS-MIPv6 spec, that if DS-MIPv6
> > > >> is being used in the integrated scenario, DHCPv6 may
> > > >> also be used for HA bootstrapping. Thats not a big
> > > >> deal.
> > > >>
> > > > [KC>] IMHO, section 2.1 should just point to the two
bootstrapping
> > > > solutions (i.e. split and integrated) so that deployments
utilizing
> > > > either of the bootstrapping solution can use DSMIP6.
> > >
> > > No. We need to show at least one mechanism for MN to
> > > obtain the IPv4 address of the HA. Otherwise we are
> > > left only with manual configuration of HA's IPv4
> > > address on the mobile node. We have three paragraphs
> > > in section 2.1 that describes how one can add the
> > > 'A' record for the HA in the DNS entry in addition to
> > > the 'AAAA' record and how the mobile node may obtain
> > > the HA's IPv4 address.
> > >
> > > Kuntal, I don't have a problem listing DHCP also as
> > > one of the solutions for DS-MIPv6 HA discovery,  but
> > > we need to extend DHCPv4 (only DHCPv4 is available
> > > on an IPv4 access network) to return the IPv6 and
> > > IPv4 address of the DS-MIPv6 home agent. Please work
> > > on these extensions before demanding that we add
> > > references to other solutions.
> > >
> > > 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 Thu Mar 01 10:58:12 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMnfT-0000Sk-Bl; Thu, 01 Mar 2007 10:58:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMnfS-0000Sf-Fh
	for mip6@ietf.org; Thu, 01 Mar 2007 10:58:06 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMnfR-000272-0o
	for mip6@ietf.org; Thu, 01 Mar 2007 10:58:06 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 8A0E89009B
	for <mip6@ietf.org>; Thu,  1 Mar 2007 10:58:01 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 10707-07 for <mip6@ietf.org>;
	Thu, 1 Mar 2007 10:57:57 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Thu,  1 Mar 2007 10:57:57 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 1 Mar 2007 10:57:54 -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] DSMIP6 solution and integrated bootstrap scenario
Date: Thu, 1 Mar 2007 10:57:54 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD9F7@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] DSMIP6 solution and integrated bootstrap scenario
Thread-Index: Acdbltp0lYGXBpi4QU6U2KbWTEFALwAIsSMgAAHmQeAAFWnjUA==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Hesham Soliman" <Hesham@elevatemobile.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 01 Mar 2007 15:57:54.0405 (UTC)
	FILETIME=[5F797950:01C75C1A]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: mip6@ietf.org, 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: Hesham Soliman [mailto:Hesham@elevatemobile.com]
> Sent: Wednesday, February 28, 2007 11:24 PM
> To: Chowdhury, Kuntal; 'Vijay Devarapalli'
> Cc: mip6@ietf.org; Basavaraj.Patil@nokia.com
> Subject: RE: [Mip6] DSMIP6 solution and integrated bootstrap scenario
>=20
>=20
>=20
>  > Let's not debate over specific cases like the IPv4 only
>  > access network
>  > case that you cite.
>=20
> =3D> This specific case forms about 70% of the rationale for the =
DSMIPv6
> work,
> so I don't see how you can ignore it.
>=20
[KC>] I don't think your quantification of the rationale for DSMIP6 is
based on any fact. I may run DSMIP6 if I am connected to an IPv6 or dual
stack ASP and I want to obtain a v4 address. IMHO, ASP with only v4
capability is one scenario. ASP with dual stack capability is another
scenario where the integrated solution will work w/o any change. Already
two SDOs adopted the integrated scenario solution. The operators I have
spoken with, all have plans to deploy dual stack NASs (e.g. ASN-GWs for
WiMAX) when they roll out v6 service. So, I don't buy your argument that
v4 only ASP is the main scenario that we need to consider for DSMIP6.


>    There is no guarantee that the DNS
>  > method for Home
>  > Agent discovery will produce the information the MN is
>  > looking for all
>  > the time. What will the MN do in a situation when it fails
>  > to get the HA
>  > information from DNS? It will fallback on some other scheme, no?
>=20
> =3D> May be and may be not. If there is a general failure in the DNS
system
> today, there is very little that you can do. If you want to do online
> banking and DNS is not working then you simply won't do it. My point
is,
> there is very little that we can do to get around a DNS failure.
Similarly,
> if DHAAD failed in the basic spec, there is nothing that the MN can do
> unless it is manually configured, which is always possible.
>=20
[KC>] Home Agent address discovery falls under the category of IP host
configuration. DHCP is the protocol for IP host configuration NOT DNS.
The MN should try to use DHCP as default for all IP config. That way,
operators can provision ALL IP config options/parameters in one place
i.e. DHCP server. DNS may be used as a fallback if DHCP cannot be run
(e.g. v4 only ASP) or DHCP comes back with no usable IP config
information. In other cases, DHCP should be used as default, IMHO.

> Hesham
>=20


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



From mip6-bounces@ietf.org Thu Mar 01 11:00:54 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMni6-0002rD-BZ; Thu, 01 Mar 2007 11:00:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMni4-0002kd-HT
	for mip6@ietf.org; Thu, 01 Mar 2007 11:00:48 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMni3-0002XG-5f
	for mip6@ietf.org; Thu, 01 Mar 2007 11:00:48 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id C05959009B
	for <mip6@ietf.org>; Thu,  1 Mar 2007 11:00:43 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 11057-04 for <mip6@ietf.org>;
	Thu, 1 Mar 2007 11:00:39 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Thu,  1 Mar 2007 11:00:38 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 1 Mar 2007 11:00:38 -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] DSMIP6 solution and integrated bootstrap scenario
Date: Thu, 1 Mar 2007 11:00:38 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD9F8@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] DSMIP6 solution and integrated bootstrap scenario
Thread-Index: Acdb6RpTZrVFAX7LS56FwlZy2meUrgAMVQsA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 01 Mar 2007 16:00:38.0905 (UTC)
	FILETIME=[C1862E90:01C75C1A]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: mip6@ietf.org, 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: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> Sent: Thursday, March 01, 2007 4:05 AM
> To: Vijay Devarapalli
> Cc: Chowdhury, Kuntal; mip6@ietf.org; Basavaraj.Patil@nokia.com
> Subject: Re: [Mip6] DSMIP6 solution and integrated bootstrap scenario
>=20
> On 3/1/07, Vijay Devarapalli <vijay.devarapalli@azairenet.com> wrote:
> > Chowdhury, Kuntal wrote:
> >
> > >> Basavaraj.Patil@nokia.com wrote:
> > >>> Okay.. I see your point now.
> > >>> I agree that the DS-MIP6 I-D could either refer or mention the
> > > methods
> > >>> by which the MN can discover the HA.
> > >> We can mention in the DS-MIPv6 spec, that if DS-MIPv6
> > >> is being used in the integrated scenario, DHCPv6 may
> > >> also be used for HA bootstrapping. Thats not a big
> > >> deal.
> > >>
> > > [KC>] IMHO, section 2.1 should just point to the two bootstrapping
> > > solutions (i.e. split and integrated) so that deployments
utilizing
> > > either of the bootstrapping solution can use DSMIP6.
> >
> > No. We need to show at least one mechanism for MN to
> > obtain the IPv4 address of the HA. Otherwise we are
> > left only with manual configuration of HA's IPv4
> > address on the mobile node. We have three paragraphs
> > in section 2.1 that describes how one can add the
> > 'A' record for the HA in the DNS entry in addition to
> > the 'AAAA' record and how the mobile node may obtain
> > the HA's IPv4 address.
> >
>=20
> I agree with Vijay. Text on section 2.1 is needed since in
> bootstrapping-split draft we refer only to IPv6 HA addresses and AAAA
> records.
>=20
[KC>] OK. I can live with some _additional_ clarification around the use
of DNS for DSMIP6 bootstrapping in the DSMIP6 I-D. But, we should also
add references to the integrated scenario which uses DHCP (albeit with
caveats like v4 only ASP).



> --Gerardo
>=20
> > Kuntal, I don't have a problem listing DHCP also as
> > one of the solutions for DS-MIPv6 HA discovery,  but
> > we need to extend DHCPv4 (only DHCPv4 is available
> > on an IPv4 access network) to return the IPv6 and
> > IPv4 address of the DS-MIPv6 home agent. Please work
> > on these extensions before demanding that we add
> > references to other solutions.
> >
> > 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 Thu Mar 01 14:53:08 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMrK0-0004gR-9s; Thu, 01 Mar 2007 14:52:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMrJz-0004ff-L1
	for mip6@ietf.org; Thu, 01 Mar 2007 14:52:11 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMrJx-0001ex-6B
	for mip6@ietf.org; Thu, 01 Mar 2007 14:52:11 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 01 Mar 2007 11:52:09 -0800
X-IronPort-AV: i="4.14,238,1170662400"; 
	d="scan'208"; a="395499321:sNHT55021736"
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/8.12.11) with ESMTP id l21Jq8fl026304; 
	Thu, 1 Mar 2007 11:52:08 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l21Jq7nH012692;
	Thu, 1 Mar 2007 11:52:08 -0800 (PST)
Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 11:52:03 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Revised  Milestones for MIP6 Working Group
Date: Thu, 1 Mar 2007 11:52:01 -0800
Message-ID: <28CEA477BE98ED48AF08A0B637A74BF40321CFAE@xmb-sjc-224.amer.cisco.com>
In-Reply-To: <20070301040921.YUUO6229.oaamta01ps.mx.bigpond.com@PC20005>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Revised  Milestones for MIP6 Working Group
Thread-Index: AcdbpQ7W+jFwzapJQ6GRUN+r68ZwKQAEjlSgACDrNUA=
From: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>
To: "Hesham Soliman" <Hesham@elevatemobile.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 01 Mar 2007 19:52:03.0272 (UTC)
	FILETIME=[15407480:01C75C3B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1169; t=1172778728;
	x=1173642728; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=gdommety@cisco.com;
	z=From:=20=22Gopal=20Dommety=20\(gdommety\)=22=20<gdommety@cisco.com>
	|Subject:=20RE=3A=20[Mip6]=20Revised=20=20Milestones=20for=20MIP6=20Worki
	ng=20Group |Sender:=20;
	bh=5dNhr9NEpZW2bRhxUwZGuda+UkKkacxQ5B5wv91B+o4=;
	b=jRZsm8XnAn1XmYwnSqcS8DRmnPxMj3omBbkUhTPoGYXKMkm3/HWQYqiYT2/ScM04b328d7zQ
	84BaXRZ2Uju1Uk7T9n2KWAVsb/YP6TURcPrmhMUQWO8AbfPi56MIiGRy;
Authentication-Results: sj-dkim-6; header.From=gdommety@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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


There are no penalties for being early..I will leave the date as it is
then.

-Gopal


Gopal Dommety, Ph.D
-------------------------------------------------------
Judgment hinders imagination
----------------------------------------------


-----Original Message-----
From: Hesham Soliman [mailto:Hesham@elevatemobile.com]=20
Sent: Wednesday, February 28, 2007 8:09 PM
To: 'Vijay Devarapalli'; Gopal Dommety (gdommety)
Cc: mip6@ietf.org; 'Basavaraj Patil'
Subject: RE: [Mip6] Revised Milestones for MIP6 Working Group

I don't think there are penalties for being early, so this date is fine
with me.

Hesham=20

 > -----Original Message-----
 > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
 > Sent: Thursday, March 01, 2007 12:53 PM  > To: Gopal Dommety
(gdommety)  > Cc: mip6@ietf.org; Basavaraj Patil  > Subject: Re: [Mip6]
Revised Milestones for MIP6 Working Group  >  > Gopal Dommety (gdommety)
wrote:
 >=20
 > > Sep 2007    Submit I-D 'Mobile IPv6 Dual-Stack Operation'=20
 > to IESG for
 > > publication as a Proposed Standard.=20
 >
 > We should try to send this to the IESG sooner than Sep 2007.
 >=20

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



From mip6-bounces@ietf.org Thu Mar 01 15:05:14 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMrWN-0003s4-Me; Thu, 01 Mar 2007 15:04:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMrST-0000xA-Jo
	for mip6@ietf.org; Thu, 01 Mar 2007 15:00:57 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMrRw-0002KY-Ei
	for mip6@ietf.org; Thu, 01 Mar 2007 15:00:28 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 01 Mar 2007 12:00:23 -0800
X-IronPort-AV: i="4.14,238,1170662400"; 
	d="scan'208"; a="44233604:sNHT237515481"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l21K0NjA013695; 
	Thu, 1 Mar 2007 12:00:23 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l21K0MDs015724;
	Thu, 1 Mar 2007 12:00:23 -0800 (PST)
Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 12:00:16 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Revised  Milestones for MIP6 Working Group
Date: Thu, 1 Mar 2007 12:00:13 -0800
Message-ID: <28CEA477BE98ED48AF08A0B637A74BF40321CFBE@xmb-sjc-224.amer.cisco.com>
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBD9EC$0001@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Revised  Milestones for MIP6 Working Group
Thread-Index: Acdbgt6Wt9v630z6R+K5+perrE75TQAOdrhwAB/FRMA=
From: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 01 Mar 2007 20:00:16.0328 (UTC)
	FILETIME=[3B22D480:01C75C3C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5122; t=1172779223;
	x=1173643223; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=gdommety@cisco.com;
	z=From:=20=22Gopal=20Dommety=20\(gdommety\)=22=20<gdommety@cisco.com>
	|Subject:=20RE=3A=20[Mip6]=20Revised=20=20Milestones=20for=20MIP6=20Worki
	ng=20Group |Sender:=20;
	bh=Vzm8S5FzPkFOZkkFRv9jASQCeAqj9e+f2ELdm3bMpLw=;
	b=Yjky1gfRycxXqOwgkqHpuBazcah/GMRwyfYR7d9wBqQgOYIxI51o+/2hVtu/eP6ox6wdzmbf
	JqzrhF8W4TUyDHlym0vmKRG4yeQgsHdI4hpUuUEj9bMWk+sx5uQzJAUK;
Authentication-Results: sj-dkim-2; header.From=gdommety@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: 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

Kuntal,

	I changed the milestones to Apr. Since there is still some
discussion, we might not be able to have them any sooner.  Also, there
are no penalities for getting them ready sooner. Let us send it to IESG
as soon as they are ready. The ball is in your court to get them ready,
since you are an author on both..

Cheers,
-Gopal



Gopal Dommety, Ph.D
-------------------------------------------------------
Judgment hinders imagination
----------------------------------------------


-----Original Message-----
From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
Sent: Wednesday, February 28, 2007 8:54 PM
To: Gopal Dommety (gdommety); mip6@ietf.org
Cc: Basavaraj Patil
Subject: RE: [Mip6] Revised Milestones for MIP6 Working Group

Hi Gopal,

"
May 2007   Submit I-D 'Bootstrapping solution for Integrated Scenario'
to IESG for publication as a Proposed Standard

Jul 2007     Submit I-D 'DHCP Options for Home Information Discovery in
MIPv6' for publication as a proposed standard
"

May and Jul 2007 milestones are way too conservative/late. I think 3GPP2
has dependencies on these two I-Ds (past due):

http://www.3gpp2.org/Public_html/IETF/IETF_Dependencies.cfm

Can these dates be revised? We may need to have a chat with AC Mahendran
and Thomas Narten (3GPP2 and IETF liaisons) to update these dates.

Regards,
Kuntal



________________________________________
From: Gopal Dommety (gdommety) [mailto:gdommety@cisco.com]
Sent: Wednesday, February 28, 2007 4:06 PM
To: mip6@ietf.org
Cc: Basavaraj Patil
Subject: [Mip6] Revised Milestones for MIP6 Working Group

Hello,
=20
    I am attaching the revised  Milestones for the MIP6 Working Group.
Please let me know if there are any changes required.
=20
Regards,
Gopal Dommety
=20
=20
=20
Goals and Milestones:
Done    Submit I-D 'Issues with firewall Problem statement' to IESG =20
Done    Submit I-D 'MIPv6 MIB' to IESG =20
Done    Submit I-D 'Extensions to Socket Advanced API for MIPv6' to IESG

Done    Submit I-D 'Alternate Route Optimization (Pre-config Key)
scheme' to IESG =20
Done    Submit Bootstrapping problem statement to IESG =20
Done    Submit I-D 'Authentication Option for MIPv6' to IESG =20
Done    Submit I-D 'Identification Option for MIPv6' to IESG =20
Done    Submit I-D 'MIPv6 operation with IKEV2 and the revised IPsec
Architecture to IESG =20
Done    Submit Problem statement and Solution to Mobile IPv6 transition
between v4/v6 networks to IESG=20
Done    Submit I-D 'Mobility management for Dual stack mobile nodes: A
Problem Statement' to IESG for publication as Informational. =20
Done    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
Statement' to IESG for publication as Informational. =20
Done    Submit I-D 'Bootstrapping solution for split Scenario' to IESG
for publication as a Proposed Standard.=20
Done   Submit I-D 'Using IPsec between Mobile and Correspondent IPv6
Nodes' to IESG for publication as Experimental.
Apr 2007    Submit I-D 'Motivation for Authentication I-D' to IESG for
publication as Informational. =20
May 2007   Submit I-D 'Bootstrapping solution for Integrated Scenario'
to IESG for publication as a Proposed Standard. =20
Jul 2007     Submit I-D 'DHCP Options for Home Information Discovery in
MIPv6' for publication as a proposed standard. =20
Jul 2007     Submit I-D 'Mobility Header Home Agent Switch Message' to
IESG for publication as a Proposed Standard.=20
Aug 2007    Submit I-D 'Goals for AAA HA Interface' to IESG for
publication as Informational. =20
Sep 2007    Submit I-D 'Home agent reliability' to IESG for publication
as a Proposed Standard. =20
Sep 2007    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
publication as a Proposed Standard. =20
Oct 2007    Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
publication as a Proposed Standard. =20
Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
for publication as a Proposed Standard. =20
Dec 2007    Submit I-D 'RADIUS Mobile IPv6 Support' to IESG for
publication as a proposed standard. =20
Feb 2008    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
for publication as Informational. =20
Feb 2008    Submit I-D(s) related to specific updates and corrections of
RFC 3775 to IESG for publication as Proposed Standard. =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 Thu Mar 01 15:05:19 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMrWh-0004vH-N5; Thu, 01 Mar 2007 15:05:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMrWf-0004ZB-Ap
	for mip6@ietf.org; Thu, 01 Mar 2007 15:05:17 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMrWc-0002wE-Lt
	for mip6@ietf.org; Thu, 01 Mar 2007 15:05:17 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 01 Mar 2007 12:05:14 -0800
X-IronPort-AV: i="4.14,238,1170662400"; 
	d="scan'208,217"; a="44237522:sNHT356938443"
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/8.12.11) with ESMTP id l21K5Dod031481
	for <mip6@ietf.org>; Thu, 1 Mar 2007 12:05:13 -0800
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 l21K4tH8029321
	for <mip6@ietf.org>; Thu, 1 Mar 2007 12:05:12 -0800 (PST)
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.1830); 
	Thu, 1 Mar 2007 12:05:02 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 1 Mar 2007 12:05:00 -0800
Message-ID: <28CEA477BE98ED48AF08A0B637A74BF40321CFCC@xmb-sjc-224.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revised  Milestones for MIP6 Working Group
Thread-Index: Acdbgt6Wt9v630z6R+K5+perrE75TQ==
From: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 01 Mar 2007 20:05:02.0913 (UTC)
	FILETIME=[E5F43B10:01C75C3C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7726; t=1172779513;
	x=1173643513; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=gdommety@cisco.com;
	z=From:=20=22Gopal=20Dommety=20\(gdommety\)=22=20<gdommety@cisco.com>
	|Subject:=20Revised=20=20Milestones=20for=20MIP6=20Working=20Group
	|Sender:=20; bh=P3lc+mWlK10rm3+wm6zF8fbBlvYMbeFjvreLeY6pW7A=;
	b=nL+phUC9FeMO8aKQDJZIyFBnrSpVm/QvwWsz/yGUgEe0VDjoP4tpmsFMFCxoawtLq6hh8+WA
	HN0Hz/NnZlzvxQrD7bmF/jaubNk7OSlfa6nQK8Kc2dFXvN1NcMJzoPejn6+Obe3GoU0QfwPrHK
	fgsIqpCR1KkTeRJgNVthWQNYI=;
Authentication-Results: sj-dkim-1; header.From=gdommety@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Subject: [Mip6] Revised  Milestones for MIP6 Working Group
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============0506871257=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0506871257==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75C3C.E5DD972D"

This is a multi-part message in MIME format.

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

Hello,
=20
    I am attaching the new revised  Milestones for the MIP6 Working
Group. I made changes based on comments I received. Please let me know
if there are any changes required.
=20
Regards,
Gopal Dommety
=20
Goals and Milestones:
Done    Submit I-D 'Issues with firewall Problem statement' to IESG =20
Done    Submit I-D 'MIPv6 MIB' to IESG =20
Done    Submit I-D 'Extensions to Socket Advanced API for MIPv6' to IESG

Done    Submit I-D 'Alternate Route Optimization (Pre-config Key)
scheme' to IESG =20
Done    Submit Bootstrapping problem statement to IESG =20
Done    Submit I-D 'Authentication Option for MIPv6' to IESG =20
Done    Submit I-D 'Identification Option for MIPv6' to IESG =20
Done    Submit I-D 'MIPv6 operation with IKEV2 and the revised IPsec
Architecture to IESG =20
Done    Submit Problem statement and Solution to Mobile IPv6 transition
between v4/v6 networks to IESG=20
Done    Submit I-D 'Mobility management for Dual stack mobile nodes: A
Problem Statement' to IESG for publication as Informational. =20
Done    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
Statement' to IESG for publication as Informational. =20
Done    Submit I-D 'Bootstrapping solution for split Scenario' to IESG
for publication as a Proposed Standard.=20
Done  Submit I-D 'Using IPsec between Mobile and Correspondent IPv6
Nodes' to IESG for publication as Experimental.
Apr 2007    Submit I-D 'Motivation for Authentication I-D' to IESG for
publication as Informational. =20
APR 2007    Submit I-D 'Bootstrapping solution for Integrated Scenario'
to IESG for publication as a Proposed Standard. =20
APR 2007    Submit I-D 'DHCP Options for Home Information Discovery in
MIPv6' for publication as a proposed standard. =20
Jul 2007    Submit I-D 'Mobility Header Home Agent Switch Message' to
IESG for publication as a Proposed Standard.=20
Aug 2007    Submit I-D 'Goals for AAA HA Interface' to IESG for
publication as Informational. =20
Sep 2007    Submit I-D 'Home agent reliability' to IESG for publication
as a Proposed Standard. =20
Sep 2007    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
publication as a Proposed Standard. =20
Oct 2007    Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
publication as a Proposed Standard. =20
Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
for publication as a Proposed Standard. =20
Dec 2007    Submit I-D 'RADIUS Mobile IPv6 Support' to IESG for
publication as a informational. =20
Feb 2008    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
for publication as Informational. =20
Feb 2008    Submit I-D(s) related to specific updates and corrections of
RFC 3775 to IESG for publication as Proposed Standard. =20

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D563584421-28022007>Hello,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D563584421-28022007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D563584421-28022007>&nbsp;&nbsp;&nbsp;&nbsp;I&nbsp;am attaching =
the new=20
revised&nbsp; Milestones for the MIP6 Working Group. I=20
made&nbsp;changes&nbsp;based on&nbsp;comments I received. Please let me =
know if=20
there are any changes required.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D563584421-28022007></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN =
class=3D563584421-28022007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D563584421-28022007>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D563584421-28022007>Gopal=20
Dommety</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D563584421-28022007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D563584421-28022007>Goals =
and=20
Milestones:<BR>Done&nbsp;&nbsp;&nbsp; Submit I-D 'Issues with firewall =
Problem=20
statement' to IESG&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; Submit I-D 'MIPv6 =
MIB' to=20
IESG&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; Submit I-D 'Extensions to Socket =
Advanced=20
API for MIPv6' to IESG&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; Submit I-D =
'Alternate=20
Route Optimization (Pre-config Key) scheme' to IESG&nbsp;=20
<BR>Done&nbsp;&nbsp;&nbsp; Submit Bootstrapping problem statement to =
IESG&nbsp;=20
<BR>Done&nbsp;&nbsp;&nbsp; Submit I-D 'Authentication Option for MIPv6' =
to=20
IESG&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; Submit I-D 'Identification Option =
for=20
MIPv6' to IESG&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; Submit I-D 'MIPv6 =
operation with=20
IKEV2 and the revised IPsec Architecture to IESG&nbsp;=20
<BR>Done&nbsp;&nbsp;&nbsp; Submit Problem statement and Solution to =
Mobile IPv6=20
transition between v4/v6 networks to IESG <BR>Done&nbsp;&nbsp;&nbsp; =
Submit I-D=20
'Mobility management for Dual stack mobile nodes: A Problem Statement' =
to IESG=20
for publication as Informational.&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; =
Submit I-D=20
'Address Location Privacy and Mobile IPv6 Problem Statement' to IESG for =

publication as Informational.&nbsp; <BR>Done&nbsp;&nbsp;&nbsp; Submit =
I-D=20
'Bootstrapping solution for split Scenario' to IESG for publication as a =

Proposed Standard. <BR>Done &nbsp;Submit I-D 'Using IPsec between Mobile =
and=20
Correspondent IPv6 Nodes' to IESG for publication as =
Experimental.<BR>Apr=20
2007&nbsp;&nbsp;&nbsp; Submit I-D 'Motivation for Authentication I-D' to =
IESG=20
for publication as Informational.&nbsp; <BR>APR 2007&nbsp;&nbsp;&nbsp; =
Submit=20
I-D 'Bootstrapping solution for Integrated Scenario' to IESG for =
publication as=20
a Proposed Standard.&nbsp; <BR>APR 2007&nbsp;&nbsp;&nbsp; Submit I-D =
'DHCP=20
Options for Home Information Discovery in MIPv6' for publication as a =
proposed=20
standard.&nbsp; <BR>Jul 2007&nbsp;&nbsp;&nbsp; Submit I-D 'Mobility =
Header Home=20
Agent Switch Message' to IESG for publication as a Proposed Standard. =
<BR>Aug=20
2007&nbsp;&nbsp;&nbsp; Submit I-D 'Goals for AAA HA Interface' to IESG =
for=20
publication as Informational.&nbsp; <BR>Sep 2007&nbsp;&nbsp;&nbsp; =
Submit I-D=20
'Home agent reliability' to IESG for publication as a Proposed =
Standard.&nbsp;=20
<BR>Sep 2007&nbsp;&nbsp;&nbsp; Submit I-D 'Mobile IPv6 Dual-Stack =
Operation' to=20
IESG for publication as a Proposed Standard.&nbsp; <BR>Oct=20
2007&nbsp;&nbsp;&nbsp; Submit I-D 'Mobile IPv6 Vendor Specific Option' =
to IESG=20
for publication as a Proposed Standard.&nbsp; <BR>Dec =
2007&nbsp;&nbsp;&nbsp;=20
Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for =
publication as a=20
Proposed Standard.&nbsp; <BR>Dec 2007&nbsp;&nbsp;&nbsp; Submit I-D =
'RADIUS=20
Mobile IPv6 Support' to IESG for publication as a informational.&nbsp; =
<BR>Feb=20
2008&nbsp;&nbsp;&nbsp; Submit I-D 'Mobile IPv6 Operation with Firewalls' =
to IESG=20
for publication as Informational.&nbsp; <BR>Feb 2008&nbsp;&nbsp;&nbsp; =
Submit=20
I-D(s) related to specific updates and corrections of RFC 3775 to IESG =
for=20
publication as Proposed Standard.&nbsp; =
</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C75C3C.E5DD972D--


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

--===============0506871257==--




From mip6-bounces@ietf.org Thu Mar 01 15:24:55 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMrpM-0005aa-0o; Thu, 01 Mar 2007 15:24:36 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMrpL-0005Zt-2o
	for mip6@ietf.org; Thu, 01 Mar 2007 15:24:35 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HMrpD-00061y-O9
	for mip6@ietf.org; Thu, 01 Mar 2007 15:24:30 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 12:24:21 -0800
Message-ID: <45E73675.6080300@azairenet.com>
Date: Thu, 01 Mar 2007 12:24:21 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
References: <459A5A6C.5070602@piuha.net>	
	<eaa74a7e0702230640g722a28fcyc89360e69337c768@mail.gmail.com>	
	<45E00DD3.1010701@piuha.net> <45E32B26.7050702@azairenet.com>	
	<eaa74a7e0702270515v20f5be3ar91f97555539aa1b3@mail.gmail.com>	
	<45E4D408.8050709@azairenet.com>	
	<eaa74a7e0702280118g5881ffdy8684e84f63880dcb@mail.gmail.com>	
	<45E63AE1.4090708@azairenet.com>
	<eaa74a7e0703010627k2c64e311n7e7e1fd148489412@mail.gmail.com>
In-Reply-To: <eaa74a7e0703010627k2c64e311n7e7e1fd148489412@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Mar 2007 20:24:21.0457 (UTC)
	FILETIME=[98800410:01C75C3F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

>> > However, suppose the HA is acting also as VPN concentrator (or 3GPP
>> > PDG or similar): there may be cases where the MN sets up a SA with
>> > this box and then use it not for MIPv6. This is an issue in DIME
>> > design: we are discussing when the authorization for MIPv6 should be
>> > performed.
>>
>> That should be irrelevant. We are talking about DIME extensions
>> to support MIPv6. If someone co-locates a PDG and a Mobile IPv6
>> HA, why do we care? It is for them to figure out how to make it
>> work. :)
>>
> 
> Not sure about that. The MIP6 service must be explicitly authorized,
> so the IKEv2 responder should understand that the IKEv2 exchange is
> related to MIP6. Otherwise you need to authorize the service when the
> first BU is sent.

As far as the use of IKEv2 for Mobile IPv6 signaling messages
goes, a mobile node would not do IKEv2 authentication with a
home agent unless it is for MIPv6 service. So I don't think a
separate step is required.

We didn't add a goal in the HA-AAAH goals document to separate
authentication and authorization, correct?

I don't think that someone co-locating a VPN concentrator with
a MIPv6 home agent is reason enough for us to require separating
authentication and authorization for basic MIPv6 operation. What
am I missing here?

Vijay

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



From mip6-bounces@ietf.org Thu Mar 01 15:43:17 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMs6o-0005Jb-JH; Thu, 01 Mar 2007 15:42:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMs6n-0005Eu-I7
	for mip6@ietf.org; Thu, 01 Mar 2007 15:42:37 -0500
Received: from tao.fdupont.fr ([82.236.136.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMs6k-0000pK-Su
	for mip6@ietf.org; Thu, 01 Mar 2007 15:42:37 -0500
Received: from tao.fdupont.fr (localhost [127.0.0.1])
	by tao.fdupont.fr (8.13.5/8.13.5) with ESMTP id l21Kfe3C021372;
	Thu, 1 Mar 2007 21:41:40 +0100 (CET)
Received: from tao.fdupont.fr (dupont@localhost)
	by tao.fdupont.fr (8.13.5/8.13.5/Submit) with ESMTP id l21KfdkB021368; 
	Thu, 1 Mar 2007 21:41:40 +0100 (CET)
Message-Id: <200703012041.l21KfdkB021368@tao.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>
Subject: Re: [Mip6] Revised Milestones for MIP6 Working Group 
In-reply-to: Your message of Wed, 28 Feb 2007 14:38:40 PST.
	<28CEA477BE98ED48AF08A0B637A74BF40321CC21@xmb-sjc-224.amer.cisco.com> 
Date: Thu, 01 Mar 2007 21:41:39 +0100
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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

 In your previous mail you wrote:

   	It shows up in the ID-Tracker as Experimental. Was there a
   change to this?It's intended status is  Experimental. Isn't it? 
   
=> the intended status is Proposed Standard as the RFC 4449 is.
   
Thanks
   
Francis.Dupont@fdupont.fr

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



From mip6-bounces@ietf.org Thu Mar 01 15:50:24 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMsEK-0000wJ-Hm; Thu, 01 Mar 2007 15:50:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMsDz-0000b0-Qn; Thu, 01 Mar 2007 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMsDz-0001Xp-HQ; Thu, 01 Mar 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 7AFB3328F8;
	Thu,  1 Mar 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HMsDz-0002eQ-Bw; Thu, 01 Mar 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HMsDz-0002eQ-Bw@stiedprstage1.ietf.org>
Date: Thu, 01 Mar 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
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-04.txt
	Pages		: 9
	Date		: 2007-3-1
	
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 Optimization.  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-04.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mip6-cn-ipsec-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-3-1124337.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-3-1124337.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 Mar 01 16:45:37 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMt5S-0008FN-5Y; Thu, 01 Mar 2007 16:45:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMt5R-0008FC-Az
	for mip6@ietf.org; Thu, 01 Mar 2007 16:45:17 -0500
Received: from web60318.mail.yahoo.com ([209.73.178.126])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HMt5O-0003Qn-Mp
	for mip6@ietf.org; Thu, 01 Mar 2007 16:45:17 -0500
Received: (qmail 20179 invoked by uid 60001); 1 Mar 2007 21:38:33 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=t8cu0139vCxblLZrlLka6umvTBrfMkLfL4SAkNQX/8i36qoQCHgAYlTw4OLAz9wA05Uku4FQQqC0aaK+rD0MVTFwu9fSVvGYCO1gpwwv9Np9znvPZrSneeuqRmEudEvxI4DIw62XO/EQfMFiVxWU99xa8fmJJYf1cUNud+9s4II=;
X-YMail-OSG: KZX0X94VM1lEZcLpu3xtyjLR8X4LteBDpea.XcZqllDFmxBh1RrfIpBSFuLLIPW7UNyknngAoj8JhYpglqMYDHs4n9Z9cImUqjzMNbFpthVv5FDPliJy8VDdw7uqvz8O6ZGBO_h0GqGXS.5M
Received: from [206.16.17.212] by web60318.mail.yahoo.com via HTTP;
	Thu, 01 Mar 2007 13:38:33 PST
X-Mailer: YahooMailRC/468 YahooMailWebService/0.6.132.8
Date: Thu, 1 Mar 2007 13:38:33 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt
To: Francis Dupont <Francis.Dupont@fdupont.fr>
MIME-Version: 1.0
Message-ID: <339965.20152.qm@web60318.mail.yahoo.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
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="===============0020981973=="
Errors-To: mip6-bounces@ietf.org

--===============0020981973==
Content-Type: multipart/alternative; boundary="0-1983749016-1172785113=:20152"

--0-1983749016-1172785113=:20152
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Francis,=0A  =0AMaybe it is too late to have any technical comments on t=
his draft =0AHowever, can I have the following editorial comments?=0A=0AIn =
Sec. 7, you said:=0Athe ingress filtering blocks topologically incorrect Ca=
re-of=0A      Addresses (because there are source addresses too), =0A=0As/t=
here/they?=0A=0AIn Sec. 4, you said:=0ABy just setting up an IPsec SA with =
the CN, the MN is able to send=0A   packets directly to the CN, i.e., trian=
gular routing is enabled.=0As/triangular routing/route optimization/?=0A=0A=
Wait, there is one more:=0AIn Sec. 9:=0AWhen the Home Address is bound to a=
 public key, for instance when the=0A   Home Address is a Cryptographically=
 Generated Addresses [RFC3972],=0As/Addresses/Address/=0A=0ARegards,=0A=0A-=
-behcet=0A----- Original Message ----=0AFrom: "Internet-Drafts@ietf.org" <I=
nternet-Drafts@ietf.org>=0ATo: i-d-announce@ietf.org=0ACc: mip6@ietf.org=0A=
Sent: Thursday, March 1, 2007 2:50:03 PM=0ASubject: [Mip6] I-D ACTION:draft=
-ietf-mip6-cn-ipsec-04.txt=0A=0A=0AA New Internet-Draft is available from t=
he on-line Internet-Drafts =0Adirectories.=0AThis draft is a work item of t=
he Mobility for IPv6 Working Group of the IETF.=0A=0A    Title        : Usi=
ng IPsec between Mobile and Correspondent IPv6 Nodes=0A    Author(s)    : F=
. Dupont, J. Combes=0A    Filename    : draft-ietf-mip6-cn-ipsec-04.txt=0A =
   Pages        : 9=0A    Date        : 2007-3-1=0A    =0AMobile IPv6 uses =
IPsec to protect signaling between the Mobile Node=0A   and the Home Agent.=
  This document defines how IPsec can be used=0A   between the Mobile Node =
and Correspondent Nodes for Home Address=0A   Option validation (aka. trian=
gular routing) and protection of=0A   mobility signaling for Route Optimiza=
tion.  The configuration details=0A   for IPsec and IKE are also provided.=
=0A=0AA URL for this Internet-Draft is:=0Ahttp://www.ietf.org/internet-draf=
ts/draft-ietf-mip6-cn-ipsec-04.txt=0A=0ATo remove yourself from the I-D Ann=
ouncement list, send a message to =0Ai-d-announce-request@ietf.org with the=
 word unsubscribe in the body of =0Athe message. =0AYou can also visit http=
s://www1.ietf.org/mailman/listinfo/I-D-announce =0Ato change your subscript=
ion settings.=0A=0AInternet-Drafts are also available by anonymous FTP. Log=
in with the =0Ausername "anonymous" and a password of your e-mail address. =
After =0Alogging in, type "cd internet-drafts" and then =0A"get draft-ietf-=
mip6-cn-ipsec-04.txt".=0A=0AA list of Internet-Drafts directories can be fo=
und in=0Ahttp://www.ietf.org/shadow.html =0Aor ftp://ftp.ietf.org/ietf/1sha=
dow-sites.txt=0A=0AInternet-Drafts can also be obtained by e-mail.=0A=0ASen=
d a message to:=0A    mailserv@ietf.org.=0AIn the body type:=0A    "FILE /i=
nternet-drafts/draft-ietf-mip6-cn-ipsec-04.txt".=0A    =0ANOTE:    The mail=
 server at ietf.org can return the document in=0A    MIME-encoded form by u=
sing the "mpack" utility.  To use this=0A    feature, insert the command "E=
NCODING mime" before the "FILE"=0A    command.  To decode the response(s), =
you will need "munpack" or=0A    a MIME-compliant mail reader.  Different M=
IME-compliant mail readers=0A    exhibit different behavior, especially whe=
n dealing with=0A    "multipart" MIME messages (i.e. documents which have b=
een split=0A    up into multiple messages), so check your local documentati=
on on=0A    how to manipulate these messages.=0A=0ABelow is the data which =
will enable a MIME compliant mail reader=0Aimplementation to automatically =
retrieve the ASCII version of the=0AInternet-Draft.=0A_____________________=
__________________________=0AMip6 mailing list=0AMip6@ietf.org=0Ahttps://ww=
w1.ietf.org/mailman/listinfo/mip6
--0-1983749016-1172785113=:20152
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman=
, new york, times, serif">Hi Francis,</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt=
; FONT-FAMILY: times new roman, new york, times, serif">&nbsp; <BR>Maybe it=
 is too late to have any technical comments on this draft <IMG src=3D"http:=
//us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif"><BR>However, can I ha=
ve the following editorial comments?</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt;=
 FONT-FAMILY: times new roman, new york, times, serif">&nbsp;</DIV>=0A<DIV =
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, se=
rif">In Sec. 7, you said:</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMIL=
Y: times new roman, new york, times, serif">the ingress filtering blocks to=
pologically incorrect Care-of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Addresses (=
because there are source addresses too), </DIV>=0A<DIV style=3D"FONT-SIZE: =
12pt; FONT-FAMILY: times new roman, new york, times, serif">&nbsp;</DIV>=0A=
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, time=
s, serif">s/there/they?</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY:=
 times new roman, new york, times, serif">&nbsp;</DIV>=0A<DIV style=3D"FONT=
-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">In Sec. =
4, you said:</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new =
roman, new york, times, serif">By just setting up an IPsec SA with the CN, =
the MN is able to send<BR>&nbsp;&nbsp; packets directly to the CN, i.e., tr=
iangular routing is enabled.</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FA=
MILY: times new roman, new york, times, serif">s/triangular routing/route o=
ptimization/?</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new=
 roman, new york, times, serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12p=
t; FONT-FAMILY: times new roman, new york, times, serif">Wait, there is one=
 more:</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,=
 new york, times, serif">In Sec. 9:</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; =
FONT-FAMILY: times new roman, new york, times, serif">When the Home Address=
 is bound to a public key, for instance when the<BR>&nbsp;&nbsp; Home Addre=
ss is a Cryptographically Generated Addresses [RFC3972],<BR>s/Addresses/Add=
ress/</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, =
new york, times, serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-=
FAMILY: times new roman, new york, times, serif">Regards,</DIV>=0A<DIV styl=
e=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"=
>&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman=
, new york, times, serif">--behcet</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; F=
ONT-FAMILY: times new roman, new york, times, serif">----- Original Message=
 ----<BR>From: "Internet-Drafts@ietf.org" &lt;Internet-Drafts@ietf.org&gt;<=
BR>To: i-d-announce@ietf.org<BR>Cc: mip6@ietf.org<BR>Sent: Thursday, March =
1, 2007 2:50:03 PM<BR>Subject: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-0=
4.txt<BR><BR>=0A<DIV>A New Internet-Draft is available from the on-line Int=
ernet-Drafts <BR>directories.<BR>This draft is a work item of the Mobility =
for IPv6 Working Group of the IETF.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;Title&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Using IPsec between Mobile a=
nd Correspondent IPv6 Nodes<BR>&nbsp;&nbsp;&nbsp;&nbsp;Author(s)&nbsp;&nbsp=
;&nbsp;&nbsp;: F. Dupont, J. Combes<BR>&nbsp;&nbsp;&nbsp;&nbsp;Filename&nbs=
p;&nbsp;&nbsp;&nbsp;: draft-ietf-mip6-cn-ipsec-04.txt<BR>&nbsp;&nbsp;&nbsp;=
&nbsp;Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 9<BR>&nbsp;&nb=
sp;&nbsp;&nbsp;Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2007-3=
-1<BR>&nbsp;&nbsp;&nbsp;&nbsp;<BR>Mobile IPv6 uses IPsec to protect signali=
ng between the Mobile Node<BR>&nbsp;&nbsp; and the Home Agent.&nbsp;&nbsp;T=
his document defines how IPsec can be used<BR>&nbsp;&nbsp; between the Mobi=
le Node and Correspondent Nodes for Home Address<BR>&nbsp;&nbsp; Option val=
idation (aka. triangular
 routing) and protection of<BR>&nbsp;&nbsp; mobility signaling for Route Op=
timization.&nbsp;&nbsp;The configuration details<BR>&nbsp;&nbsp; for IPsec =
and IKE are also provided.<BR><BR>A URL for this Internet-Draft is:<BR><A h=
ref=3D"http://www.ietf.org/internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt"=
 target=3D_blank>http://www.ietf.org/internet-drafts/draft-ietf-mip6-cn-ips=
ec-04.txt</A><BR><BR>To remove yourself from the I-D Announcement list, sen=
d a message to <BR>i-d-announce-request@ietf.org with the word unsubscribe =
in the body of <BR>the message. <BR>You can also visit <A href=3D"https://w=
ww1.ietf.org/mailman/listinfo/I-D-announce" target=3D_blank>https://www1.ie=
tf.org/mailman/listinfo/I-D-announce</A> <BR>to change your subscription se=
ttings.<BR><BR>Internet-Drafts are also available by anonymous FTP. Login w=
ith the <BR>username "anonymous" and a password of your e-mail address. Aft=
er <BR>logging in, type "cd internet-drafts" and then <BR>"get
 draft-ietf-mip6-cn-ipsec-04.txt".<BR><BR>A list of Internet-Drafts directo=
ries can be found in<BR><A href=3D"http://www.ietf.org/shadow.html" target=
=3D_blank>http://www.ietf.org/shadow.html</A> <BR>or ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt<BR><BR>Internet-Drafts can also be obtained by e-mail.<=
BR><BR>Send a message to:<BR>&nbsp;&nbsp;&nbsp;&nbsp;mailserv@ietf.org.<BR>=
In the body type:<BR>&nbsp;&nbsp;&nbsp;&nbsp;"FILE /internet-drafts/draft-i=
etf-mip6-cn-ipsec-04.txt".<BR>&nbsp;&nbsp;&nbsp;&nbsp;<BR>NOTE:&nbsp;&nbsp;=
&nbsp;&nbsp;The mail server at ietf.org can return the document in<BR>&nbsp=
;&nbsp;&nbsp;&nbsp;MIME-encoded form by using the "mpack" utility.&nbsp;&nb=
sp;To use this<BR>&nbsp;&nbsp;&nbsp;&nbsp;feature, insert the command "ENCO=
DING mime" before the "FILE"<BR>&nbsp;&nbsp;&nbsp;&nbsp;command.&nbsp;&nbsp=
;To decode the response(s), you will need "munpack" or<BR>&nbsp;&nbsp;&nbsp=
;&nbsp;a MIME-compliant mail reader.&nbsp;&nbsp;Different MIME-compliant ma=
il
 readers<BR>&nbsp;&nbsp;&nbsp;&nbsp;exhibit different behavior, especially =
when dealing with<BR>&nbsp;&nbsp;&nbsp;&nbsp;"multipart" MIME messages (i.e=
. documents which have been split<BR>&nbsp;&nbsp;&nbsp;&nbsp;up into multip=
le messages), so check your local documentation on<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;how to manipulate these messages.<BR><BR>Below is the data which will en=
able a MIME compliant mail reader<BR>implementation to automatically retrie=
ve the ASCII version of the<BR>Internet-Draft.</DIV>=0A<DIV>_______________=
________________________________<BR>Mip6 mailing list<BR>Mip6@ietf.org<BR><=
A href=3D"https://www1.ietf.org/mailman/listinfo/mip6" target=3D_blank>http=
s://www1.ietf.org/mailman/listinfo/mip6</A></DIV></DIV>=0A<DIV style=3D"FON=
T-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR></D=
IV></div></body></html>
--0-1983749016-1172785113=:20152--


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

--===============0020981973==--




From mip6-bounces@ietf.org Thu Mar 01 17:31:42 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMtnz-0008I2-On; Thu, 01 Mar 2007 17:31:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMtny-0008H7-5B; Thu, 01 Mar 2007 17:31:18 -0500
Received: from mail1.rz.fhtw-berlin.de ([141.45.5.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMtnt-00023B-9n; Thu, 01 Mar 2007 17:31:18 -0500
Received: from dhcp-15-128.rdg.ac.uk ([134.225.15.128])
	by mail1.rz.fhtw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.42 (FreeBSD))
	id 1HMsnx-0001YN-JD; Thu, 01 Mar 2007 22:27:13 +0100
Message-ID: <45E74665.207@fhtw-berlin.de>
Date: Thu, 01 Mar 2007 22:32:21 +0100
From: Thomas C Schmidt <schmidt@fhtw-berlin.de>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: mobopts <mobopts@irtf.org>,  mipshop@ietf.org, Mip6 <mip6@ietf.org>, 
	sam@irtf.org,  ssm@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: 
Subject: [Mip6] [Mobopts] New ID: Multicast Mobility in MIPv6: Problem
	Statement
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: schmidt@fhtw-berlin.de
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

we submitted an updated version of the problem statement
draft on extending Multicast to Mobility.

It should be in the ID directory soon and can immediatly be downloaded
under:

http://www.realmv6.org/papers/draft-schmidt-mobopts-mmcastv6-ps-02.txt

Details:


               Multicast Mobility in MIPv6: Problem Statement
                   <draft-schmidt-mobopts-mmcastv6-ps-02.txt>

Abstract

     In this document we discuss mobility extensions to current IP layer
    multicast solutions. Problems arising from mobile group communication
    in general, in the case of multicast listener mobility and for mobile
    Any Source Multicast as well as Source Specific Multicast senders are
    documented. Characteristic aspects of multicast routing and
    deployment issues are summarized. The principal approaches to the
    multicast mobility problems are outlined subsequently.


The new document contains a number of clarification & language fixes and 
has been extended to include

  o further routing issues, especially bi-directional PIM;
  o additional approaches to a solution of mobile multicast tasks;
  o further references;
  o all major comments from reviewers.


As it seems desirable to advance on the subject, we'd like to emphasize
solicitation of comments & reviews ...

Looking forward to your discussions!

See you in Prague,

thomas



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



From mip6-bounces@ietf.org Thu Mar 01 18:11:19 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMuLJ-0000cs-7F; Thu, 01 Mar 2007 18:05:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMuLG-0000W9-E7
	for mip6@ietf.org; Thu, 01 Mar 2007 18:05:42 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMuJL-0005k6-U3
	for mip6@ietf.org; Thu, 01 Mar 2007 18:03:45 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 15:03:41 -0800
Message-ID: <45E75BCB.1050304@azairenet.com>
Date: Thu, 01 Mar 2007 15:03:39 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Local HA assignment using DNS (was Re: [Mip6] AD review of
	draft-ietf-mip6-bootstrapping-split)
References: <459A5A6C.5070602@piuha.net>
	<eaa74a7e0702230640g722a28fcyc89360e69337c768@mail.gmail.com>
	<45DF3F77.7070203@azairenet.com> <45E00DD7.70701@piuha.net>
In-Reply-To: <45E00DD7.70701@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Mar 2007 23:03:41.0370 (UTC)
	FILETIME=[DAA6F9A0:01C75C55]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:
> Vijay,
>> There was an explicit requirement to support local HA
>> assignment using DNS. IMO, local HA assignment is
>> required for any HA discovery/assignment mechanism. So
>> I would like to keep the text instead of saying it is
>> out of scope.
>>
>> The example is trying to describe how a particular
>> operator may "name" the home agents, what entries appear
>> in the DNS servers, and what FQDNs are provisioned in
>> the mobile node.
>>
>> This particular paragraph underwent multiple changes.
>> I can re-write the text to better explain how it can be
>> done or to address any specific concern.
> 
> The reason that I am reacting on this is that we should
> either explain, fully, how to do it or otherwise declare
> it out of scope.
> 
> I see several holes in the example text, including, for
> instance, how the mobile nodes determine the locations,
> how changes in the available locations are managed
> between the MN and HA implementations, etc.

I re-wrote the text a bit. Here is the new text.

    Additionally, the ability to provide a mobile node with a localized
    home agent (e.g. on the visited link) can help to optimize handover
    signaling and improve routing efficiency in bi-directional tunneling
    mode.  There are many mechanisms to assign a local home agent to a
    mobile node.  These mechanisms are out of scope for this document,
    but a couple of them are described here as examples.  One mechanism
    is to provision the mobile node with an FQDN for a local home agent
    when it attaches to the local link through an access link specific
    mechanism.  For example the FQDN of the local home agent can be sent
    to the mobile node using DHCP.  Another mechanism is to specify an
    interoperable naming convention for constructing home agent FQDNs
    based on the mobile node's location.  For example, a mobile network
    operator may assign the FQDN "ha.locationA.operator.com" to the Home
    Agent located in "location A" and the FQDN
    "ha.locationB.operator.com" to the Home Agent located in "location
    B".  If the Mobile Node is attached to "location A" and wants to use
    a Home Agent located in "location A", it will set the QNAME to
    "ha.locationA.operator.com" in the DNS request.  The Mobile Node
    determines that it is attached to "location A" through access link
    specific mechanisms.  If the mobile operator changes the location
    information for a particular local link, the FQDNs for the home
    agents on the local link should also be updated with the new location
    information.

    If the mobile node is unable to discover a local home agent, it MUST
    use the home agent on its home link.

Comments?

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



From mip6-bounces@ietf.org Thu Mar 01 18:25:23 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMudy-0007kk-4A; Thu, 01 Mar 2007 18:25:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMudw-0007kc-Gz
	for mip6@ietf.org; Thu, 01 Mar 2007 18:25:00 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMudv-00010c-Vx
	for mip6@ietf.org; Thu, 01 Mar 2007 18:25:00 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 15:24:53 -0800
Message-ID: <45E760C3.5050103@azairenet.com>
Date: Thu, 01 Mar 2007 15:24:51 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
References: <4D2F935F08D41A4C8866693F4F0D7C4F01278236@lan-ex-01.panasonic.de>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4F01278236@lan-ex-01.panasonic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Mar 2007 23:24:53.0898 (UTC)
	FILETIME=[D12356A0:01C75C58]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kilian Weniger wrote:

>>>    If an anycast address is returned in response to DNS 
>> resolution of
>>>    an FQDN, the IKEv2 transaction between the Mobile Node and Home
>>>    Agent is slightly modified. The Mobile Node sends the IKE_SA_INIT
>>>    request to the anycast address. The node which has the anycast
>>>    address assigned to one of its network interfaces selects a Home
>>>    Agent address from the set of Home Agents managed by the 
>> node, and
>>>    forwards the IKE_SA_INIT. If the set of Home Agents is 
>> empnty, the
>>>    node simply drops the packet. The Home Agent answers 
>> using its own
>>>    address, and includes an "under attack" cookie, in 
>> accordance with
>>>    RFC 4306 [7]. The Mobile Node notes the Home Agent address and
>>>    resends the IKE_SA_INIT message to the Home Agent, along with the
>>>    cookie. 
>> There are several issues in this. First, I think I understand
>> at least one reason why the cookie exchange makes sense,
>> but is that something that has to be mandated? What if the
> 
> There were two reasons for mandating the cookie exchange:
> 1. anycast HA address is typically a single well-known and public
> address, which makes it a possible target of DoS attacks. 
> 2. less impact on IKEv2 exchange, since the complete IKEv2 exchange is
> done with unicast address.

In my mind, the second one was the main reason.

> If nobody sees a big issue with an anycasted IKE_SA_INIT followed by a
> unicast IKE_SA_INIT response without cookie, I'm fine with "SHOULD"
> instead of "MUST" for the cookie (Vijay, from your reply it seems you
> have concerns?). Using the cookie due to reason 1 can be left to
> operator's decision IMHO.

Lets get the mechanism right. I prefer not to add yet
another optional mechanism. If its not needed we should
remove it.

The way I see it the cookie is used by the responder (the
HA that sent the cookie) to tie the first IKE_SA_INIT
exchange with the second one. The cookie is also used by
the initiator (the mobile node) to figure out why its
first IKE_SA_INIT exchange did not succeed and why it
needs to do a second IKE_SA_INIT exchange.

>> home network simply figures out what HA should be used and
>> responds in the usual IKEv2 way?
> 
> yes, IMHO we can relax this and it can be left to HA
> configuration/operator's decision whether HA always includes cookie or
> not (see above). 

I would prefer one concrete way of doing it.

>> Secondly, responding with the home agent's own address
>> is in violation of a MUST in RFC 4306, Section 2.11. I talked
>> to one of the IKEv2 designers about this and his advice
>> was that the MUST may have been a mistake. Or at least it
>> should be limited to unicast addresses, and leave the behaviour
>> for anycast addresses for future documents. In any case,
>> this deviation from RFC 4306 should be highlighted and
>> justified in the document.
> 
> we could add something like "the MUST in RFC4306 refers to unicast
> only". 

How about the following text?

   Note that when the mobile node sends an IKE_SA_INIT request
   message to an anycast address, the response comes back from
   a unicast address.  RFC 4306 requires that the responder MUST
   use the destination address on the request message as the
   source address on the response message.  It is likely that
   RFC 4306 was talking about unicast addresses in that context.
   The mobile node implementation compliant to this specification
   must relax the requirement from RFC 4306 and be willing to
   process the response from an unicast address when it sends a
   request to an anycast address.

>> The third issue is the above notion of a node that owns an
>> anycast address. How does this relate to the usual arrangement
>> where the routing system handles the delivery of the anycast
>> packets to the "closest" place that advertises that address?
> 
> all HAs on home link should have same distance in hops from MN, so there
> shouldn't be any impact on the notion of delivery of anycast packets by
> the routing system. This forwarding allows the operator to control the
> assignment of a HA on the home link on a per-case basis based on
> parameters defined by operator(e.g., load).
> 
>> When you say "forwards", do you mean that the packet is
>> forwarded unmodified, or that the particular home agent's
>> address replaces the destination address? 
> 
> good question. Some options for forwarding are 
> 1. MAC address replacement, 
> 2. IP tunneling,
> 3. IP address replacement. 
> 
> The first (and maybe the second) option have the issue that the receiver
> of a unmodified packet has no way to determine whether the packet was
> already forwarded by another HA or comes from the MN. Hence, it would
> apply the same mechanism to forwarded packets as to packets received
> directly from the MN. This means that unmodified packets may be
> forwarded many times, if the considered parameters (e.g., load) have
> changed since the last forwarding or are not the same at all HAs. This
> could be prevented by modifying forwarded packets somehow, so that the
> HA is able to identify those and doesn't apply the forwarding mechanism
> to already forwarded packets. This is not needed if the third option is
> used.

We already say the following in the draft.

    Note that this procedure requires the implementation of anycast
    forwarding in such a way that the Home Agent can distinguish
    between an IKE_SA_INIT forwarded through an anycast address and
    one sent directly from the Mobile Node.

>> Four: What happens when the IKE SA dies or is
>> deleted, but a binding for the mobile node remains
>> in the selected home agent? Will the mobile node
>> re-establish the IKE SA using the anycast address,
>> or the address of the selected home agent?
> 
> Yes, some text should be added about that. The MN could first try to
> re-establish the SA with the current HA's unicast address, as Vijay
> said. But if this fails, the MN should try to find a new HA, e.g., by
> using the anycast HA assignment. 

How about the following text?

   A mobile node's security associations with its home agent may
   expire while it still has a valid binding cache entry at the
   the home agent.  In this case, the mobile node MUST NOT use an
   anycast address as the destination address in the IKE_SA_INIT
   exchange to setup new security associations.  It MUST try to
   setup security associations with its existing home agent.

Vijay

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



From mip6-bounces@ietf.org Thu Mar 01 20:41:39 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMwlx-0003um-L1; Thu, 01 Mar 2007 20:41:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMwlw-0003ub-9N; Thu, 01 Mar 2007 20:41:24 -0500
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMwlg-0001aK-DR; Thu, 01 Mar 2007 20:41:24 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JE9007345ZLJR@szxga03-in.huawei.com>; Fri,
	02 Mar 2007 09:40:33 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JE900IM55ZK5Y@szxga03-in.huawei.com>; Fri,
	02 Mar 2007 09:40:33 +0800 (CST)
Received: from q52443 ([10.164.5.107])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JE90036N5ZH9B@szxml03-in.huawei.com>; Fri,
	02 Mar 2007 09:40:32 +0800 (CST)
Date: Fri, 02 Mar 2007 09:40:29 +0800
From: qinxia <alice.Q@huawei.com>
To: mipshop@ietf.org
Message-id: <043201c75c6b$c2b757c0$6b05a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acdca8JvZMQHmFFLS82Llv9p2mWMgw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mip6@ietf.org, netlmm@ietf.org
Subject: [Mip6] [mipshop] please review my new draft :
	draft-qin-mipshop-pmipro-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


Hello All,
       My new draft is available, please review it,
http://tools.ietf.org/wg/mipshop/draft-qin-mipshop-pmipro-00.txt

   This document defines route optimization protocol for Proxy Mobile     
   IPv6.  Proxy home test, concurrent proxy care-of test and handover     
   procedures are explained.  Proxy mobile agent uses cryptographically   
   generated home addresses so that no more home test is needed after     
   the initial home test.  Handover home keygen token is used during      
   handover in order to eliminate home test for the next proxy mobile     
   agent.  A different route optimization protocol is defined for inter-  
   proxy mobile agent operation if the correspondent node is not Mobile   
   IPv6 enabled.                                                          


your comments are sincerely welcome.

Best regards

Alice Qin



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



From mip6-bounces@ietf.org Thu Mar 01 20:46:30 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMwqa-0001lE-4L; Thu, 01 Mar 2007 20:46:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMwqY-0001gT-Oi
	for mip6@ietf.org; Thu, 01 Mar 2007 20:46:10 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMwqX-0002Hw-BZ
	for mip6@ietf.org; Thu, 01 Mar 2007 20:46:10 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id C39F690054
	for <mip6@ietf.org>; Thu,  1 Mar 2007 20:46:05 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 22783-16 for <mip6@ietf.org>;
	Thu, 1 Mar 2007 20:46:01 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Thu,  1 Mar 2007 20:46:01 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 1 Mar 2007 20:46:01 -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: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
Date: Thu, 1 Mar 2007 20:46:01 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA16@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
Thread-Index: AcdcV1zUIXMDpd+2Qfy5jAfK8bDflQAFJFwQ
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Jari Arkko" <jari.arkko@piuha.net>
X-OriginalArrivalTime: 02 Mar 2007 01:46:01.0542 (UTC)
	FILETIME=[883F4660:01C75C6C]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
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

> One mechanism
>     is to provision the mobile node with an FQDN for a local home
agent
>     when it attaches to the local link through an access link specific
>     mechanism.  For example the FQDN of the local home agent can be
sent
>     to the mobile node using DHCP.

Why only FQDN? The local HA address can be sent directly to the MN. Why
asking the MN to do one more roundtrip with DNS? Just use the DHCP
options in HIOPT. If DHCP is used by the MN, and if the DHCP server has
local HA address info, it should be able to give it out to the MN.

-Kuntal


> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Thursday, March 01, 2007 5:04 PM
> To: Jari Arkko
> Cc: Mobile IPv6 Mailing List
> Subject: Local HA assignment using DNS (was Re: [Mip6] AD review
ofdraft-
> ietf-mip6-bootstrapping-split)
>=20
> Jari Arkko wrote:
> > Vijay,
> >> There was an explicit requirement to support local HA
> >> assignment using DNS. IMO, local HA assignment is
> >> required for any HA discovery/assignment mechanism. So
> >> I would like to keep the text instead of saying it is
> >> out of scope.
> >>
> >> The example is trying to describe how a particular
> >> operator may "name" the home agents, what entries appear
> >> in the DNS servers, and what FQDNs are provisioned in
> >> the mobile node.
> >>
> >> This particular paragraph underwent multiple changes.
> >> I can re-write the text to better explain how it can be
> >> done or to address any specific concern.
> >
> > The reason that I am reacting on this is that we should
> > either explain, fully, how to do it or otherwise declare
> > it out of scope.
> >
> > I see several holes in the example text, including, for
> > instance, how the mobile nodes determine the locations,
> > how changes in the available locations are managed
> > between the MN and HA implementations, etc.
>=20
> I re-wrote the text a bit. Here is the new text.
>=20
>     Additionally, the ability to provide a mobile node with a
localized
>     home agent (e.g. on the visited link) can help to optimize
handover
>     signaling and improve routing efficiency in bi-directional
tunneling
>     mode.  There are many mechanisms to assign a local home agent to a
>     mobile node.  These mechanisms are out of scope for this document,
>     but a couple of them are described here as examples.  One
mechanism
>     is to provision the mobile node with an FQDN for a local home
agent
>     when it attaches to the local link through an access link specific
>     mechanism.  For example the FQDN of the local home agent can be
sent
>     to the mobile node using DHCP.  Another mechanism is to specify an
>     interoperable naming convention for constructing home agent FQDNs
>     based on the mobile node's location.  For example, a mobile
network
>     operator may assign the FQDN "ha.locationA.operator.com" to the
Home
>     Agent located in "location A" and the FQDN
>     "ha.locationB.operator.com" to the Home Agent located in "location
>     B".  If the Mobile Node is attached to "location A" and wants to
use
>     a Home Agent located in "location A", it will set the QNAME to
>     "ha.locationA.operator.com" in the DNS request.  The Mobile Node
>     determines that it is attached to "location A" through access link
>     specific mechanisms.  If the mobile operator changes the location
>     information for a particular local link, the FQDNs for the home
>     agents on the local link should also be updated with the new
location
>     information.
>=20
>     If the mobile node is unable to discover a local home agent, it
MUST
>     use the home agent on its home link.
>=20
> Comments?
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Thu Mar 01 20:51:22 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMwvK-0003hF-Pf; Thu, 01 Mar 2007 20:51:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMwvK-0003hA-55
	for mip6@ietf.org; Thu, 01 Mar 2007 20:51:06 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMwvG-0002j7-KW
	for mip6@ietf.org; Thu, 01 Mar 2007 20:51:06 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 17:50:59 -0800
Message-ID: <45E78306.8020502@azairenet.com>
Date: Thu, 01 Mar 2007 17:51:02 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
References: <7CCD07160348804497EF29E9EA5560D7FBDA16$0001@exchtewks2.starentnetworks.com>
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBDA16$0001@exchtewks2.starentnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2007 01:50:59.0774 (UTC)
	FILETIME=[3A01DDE0:01C75C6D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
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

Chowdhury, Kuntal wrote:
>> One mechanism
>>     is to provision the mobile node with an FQDN for a local home
> agent
>>     when it attaches to the local link through an access link specific
>>     mechanism.  For example the FQDN of the local home agent can be
> sent
>>     to the mobile node using DHCP.
> 
> Why only FQDN? The local HA address can be sent directly to the MN. Why
> asking the MN to do one more roundtrip with DNS? Just use the DHCP
> options in HIOPT. If DHCP is used by the MN, and if the DHCP server has
> local HA address info, it should be able to give it out to the MN.

Kuntal, I know you are very passionate about DHCP. :)
But here we are talking about using DNS to bootstrap
a home agent. The assumption is that support for
draft-ietf-mip6-hiopt-02.txt is not available on the
local network.

If DHCP-based HA assignment is available, it can of
course be used.

Vijay


> 
> -Kuntal
> 
> 
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>> Sent: Thursday, March 01, 2007 5:04 PM
>> To: Jari Arkko
>> Cc: Mobile IPv6 Mailing List
>> Subject: Local HA assignment using DNS (was Re: [Mip6] AD review
> ofdraft-
>> ietf-mip6-bootstrapping-split)
>>
>> Jari Arkko wrote:
>>> Vijay,
>>>> There was an explicit requirement to support local HA
>>>> assignment using DNS. IMO, local HA assignment is
>>>> required for any HA discovery/assignment mechanism. So
>>>> I would like to keep the text instead of saying it is
>>>> out of scope.
>>>>
>>>> The example is trying to describe how a particular
>>>> operator may "name" the home agents, what entries appear
>>>> in the DNS servers, and what FQDNs are provisioned in
>>>> the mobile node.
>>>>
>>>> This particular paragraph underwent multiple changes.
>>>> I can re-write the text to better explain how it can be
>>>> done or to address any specific concern.
>>> The reason that I am reacting on this is that we should
>>> either explain, fully, how to do it or otherwise declare
>>> it out of scope.
>>>
>>> I see several holes in the example text, including, for
>>> instance, how the mobile nodes determine the locations,
>>> how changes in the available locations are managed
>>> between the MN and HA implementations, etc.
>> I re-wrote the text a bit. Here is the new text.
>>
>>     Additionally, the ability to provide a mobile node with a
> localized
>>     home agent (e.g. on the visited link) can help to optimize
> handover
>>     signaling and improve routing efficiency in bi-directional
> tunneling
>>     mode.  There are many mechanisms to assign a local home agent to a
>>     mobile node.  These mechanisms are out of scope for this document,
>>     but a couple of them are described here as examples.  One
> mechanism
>>     is to provision the mobile node with an FQDN for a local home
> agent
>>     when it attaches to the local link through an access link specific
>>     mechanism.  For example the FQDN of the local home agent can be
> sent
>>     to the mobile node using DHCP.  Another mechanism is to specify an
>>     interoperable naming convention for constructing home agent FQDNs
>>     based on the mobile node's location.  For example, a mobile
> network
>>     operator may assign the FQDN "ha.locationA.operator.com" to the
> Home
>>     Agent located in "location A" and the FQDN
>>     "ha.locationB.operator.com" to the Home Agent located in "location
>>     B".  If the Mobile Node is attached to "location A" and wants to
> use
>>     a Home Agent located in "location A", it will set the QNAME to
>>     "ha.locationA.operator.com" in the DNS request.  The Mobile Node
>>     determines that it is attached to "location A" through access link
>>     specific mechanisms.  If the mobile operator changes the location
>>     information for a particular local link, the FQDNs for the home
>>     agents on the local link should also be updated with the new
> location
>>     information.
>>
>>     If the mobile node is unable to discover a local home agent, it
> MUST
>>     use the home agent on its home link.
>>
>> Comments?
>>
>> _______________________________________________
>> 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 Mar 01 20:51:22 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMwva-0003iN-9b; Thu, 01 Mar 2007 20:51:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMwvX-0003iF-Jb
	for mip6@ietf.org; Thu, 01 Mar 2007 20:51:19 -0500
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMwvW-0002kG-1Y
	for mip6@ietf.org; Thu, 01 Mar 2007 20:51:19 -0500
Received: OTM-MO(otm-mgo01) id l221oED4086567;
	Fri, 2 Mar 2007 10:50:15 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l221oENA092569;
	Fri, 2 Mar 2007 10:50:14 +0900 (JST)
Received: from [127.0.0.1] (keiichi00-4.osaka.iij.ad.jp [192.168.64.45])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp00) id l221oDZT095028
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 2 Mar 2007 10:50:14 +0900 (JST)
In-Reply-To: <20070228025801.ZXHR17816.oaamta02ps.mx.bigpond.com@PC20005>
References: <20070228025801.ZXHR17816.oaamta02ps.mx.bigpond.com@PC20005>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <3BDF2960-F241-42CB-9895-E608A7AB42AB@iijlab.net>
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue93] Payload Qualifiers when using IPv4-UDP
	transportfor both IPv4 and IPv6 payloads
Date: Fri, 2 Mar 2007 10:50:21 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, mip6@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>, 'Sri Gundavelli' <sgundave@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1490393390=="
Errors-To: mip6-bounces@ietf.org


--===============1490393390==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-1--927990675;
	protocol="application/pkcs7-signature"


--Apple-Mail-1--927990675
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi,

On 2007/02/28, at 11:57, Hesham Soliman wrote:

> => I know the following question is not necessarily the crux of  
> your issue
> but does anyone implement MIPv6 as an application? I know it's  
> possible to
> do that but no one seemed to make that choice to my knowledge, but  
> I could
> be wrong.
>

FYI, our BSD based implementation (SHISA) processes all MIPv6 signal  
messages in user space programs.

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




--Apple-Mail-1--927990675
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKbjCCBF8w
ggJHoAMCAQICAhIQMA0GCSqGSIb3DQEBBQUAMEUxCzAJBgNVBAYTAkpQMRUwEwYDVQQKEwxXSURF
IFByb2plY3QxHzAdBgNVBAMTFm1lbWJlcnMgb3JpZW50ZWQgQ0EgMDIwHhcNMDYwNjEyMDQ1NTA5
WhcNMDcwNjMwMjM1OTU5WjBkMQswCQYDVQQGFAJKUDEVMBMGA1UEChQMV0lERSBQcm9qZWN0MRsw
GQYDVQQDFBIwMzI4IEtlaWljaGkgU2hpbWExITAfBgkqhkiG9w0BCQEUEmtlaWljaGlAaWlqbGFi
Lm5ldDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAu6pTSPQTKzeSygFymRWYipFcZRaePRSU
nruo6RtpQuNgDyUKvaMOa1KuNWRPYHp28hoWYe0YBrGj5SdHH2A3wbJ2zP5cXQFgMJMxJXhcWuSu
+Foo7n9T1+yFjuc37Us9N4LoXZaM3krFqBHz2XSUCSigzTstdkIXWPwxDg+db4MCAwEAAaOBvTCB
ujAOBgNVHQ8BAQAEBAMCBLAwIAYDVR0RAQEABBYwFIESa2VpaWNoaUBpaWpsYWIubmV0MDYGA1Ud
HwEBAAQsMCowKKAmoCSGImh0dHA6Ly93d3cubW9jYS53aWRlLmFkLmpwL2NybC5jcmwwIgYDVR0j
AQEABBgwFoAUOM7FCTrTDVTyVXHmSMda90Tf6bowKgYDVR0lAQEABCAwHgYIKwYBBQUHAwQGCCsG
AQUFBwMDBggrBgEFBQcDAjANBgkqhkiG9w0BAQUFAAOCAgEAlB3DdeJJZ1gJh4sszEgoUg9DIHRG
eaotuAi5FfGkd+KmzEARKYvgfh1A8AVAoHISFvavv0OD9w9dmzGyAmNUTBUsSMeH/5XiLuWJPbjU
3bVK467oyDEFaA+XFJurRY6RuPb4afHoi+aCHtY/pmcGCCSQPKnOuN8BviNLp/haDQyPVVwA+9it
s7PwUArSkPnkBo1GXk4FSFDkijbw6zzJkXePBLHkE3QcFBYIo0woy6P2NFFYz8nPmd8M8qyT0Yh8
A9g0UVxvcWk4gUaJP0AeZ8/raNCr7eXBMByhDx5FSvparc21zEmQ5MnCVduDuM9eM8Qc8zFqzTzg
mmZza69jiiq98kL1yFqjfL4+Nu7+N9D8Q/NuaIYLd9E++s20X9Kb7dW1xqMS1E30I8ZZnIwu2Fox
ZRziQnKHkatDFBI+zuNY3+nIcE8bvzm/Y36xwk2GhN8p707CsT5i17ZCzkvriCdkE13riXNhXDOe
qGR6Kj1aZLLBxHeLvFUa72q65+ShesszO6lOxf66auFbXYsOfzIUhG3z5YmM6Lk5NtJom6F7Drob
jPjyDv2zZoGNGdIqbDbOaFkmBEYchuToVMNzYk6v6d+v4A/MrnGlexgQbzfgC0Ld32NwPlDDGFnO
LPjaEZ19bFK65rWjWwEyLsO15GD7jotBrDU5yngkhu15RKowggYHMIID76ADAgECAgIJFjANBgkq
hkiG9w0BAQUFADA+MQswCQYDVQQGEwJKUDEVMBMGA1UEChMMV0lERSBQcm9qZWN0MRgwFgYDVQQD
Ew9XSURFIFJPT1QgQ0EgMDIwHhcNMDYwNTE4MTMzNTM2WhcNMTYwNjMwMjM1OTU5WjBFMQswCQYD
VQQGEwJKUDEVMBMGA1UEChMMV0lERSBQcm9qZWN0MR8wHQYDVQQDExZtZW1iZXJzIG9yaWVudGVk
IENBIDAyMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA4BYQZ8z3YdyJUt0ZbDh0+rVf
fpf/Aw2J2GKNLy4fMIGpEhjS+OhAPC9TUH6rNVV2AR6myr94stzWhGY++bZjd7/oYYRLa+tCtUKa
Om49ibS8CHSqfeR/Yb0YHKTrHCaAu2PUw6kENGZ3bDCiMbuDPkPLVkYuN3rSRp3qHd1XJ8DZ2bTX
DbW3cwVqHFxKjVf6mdBInlL8pMs9z4T9GNpcqQO1i7Uk467KLZYbi1W1d5m23Jodr/7/y08bc078
ppWE3dP9eNEysmRxdIvKMgTHfTjtYN3ZhnfUEsYoJ6W9flc9Qoe+5UqdBt+O5ruJM3m1viWf+Rs8
xvvs9ZnodrqaxAIDwgmgpHePLCV2Qc/Fix3vkLY2Rt9KXeRCjLOzgdCYhtuJI42hY/l9dJjrRRK/
Qo5jABzbRRJzCavDlqS25q1OXenrO64nU+7T92PfFeOv1ORg5PcCSoY0dIzN9lcL51yb2PLn3cUx
ya4itIYV9MHFXaIDM4inLLmBUR/0xD4Q+Ju1Zqd5n+uK5lCrQ48+kMPKbrDyrDyvqHYTo8XRuyAU
Z1F56NJFv6umd+/m0ADC1M7Q9HNXwt8dRZyvVgH8l4teYu9We32NtZ7H8dyNaa34R2zs1bP2ftDT
Au//Bi/3u47JTSJ6M1zE6lsc7OwP6c32okaCRCwayxVYi+FgNdUCAwEAAaOCAQYwggECMA8GA1Ud
EwEB/wQFMAMBAf8wDgYDVR0PAQEABAQDAgH+MFsGA1UdIAEBAARRME8wTQYJKoMIjJwYAQECMEAw
PgYIKwYBBQUHAgEWMmh0dHA6Ly9tb2NhLndpZGUuYWQuanAvbW9jYV9ndWlkZS9tb2NhX3BvbGlj
eS5odG1sMDwGA1UdHwEBAAQyMDAwLqAsoCqGKGh0dHA6Ly93d3cud2lkZS5hZC5qcC9jYS93aWRl
cm9vdGNybC5jcmwwIAYDVR0OAQEABBYEFDjOxQk60w1U8lVx5kjHWvdE3+m6MCIGA1UdIwEBAAQY
MBaAFAzMoku5z7HsuNTr5KwJl0+xojExMA0GCSqGSIb3DQEBBQUAA4ICAQAKZpGub2X1UG9aXuAS
P1MsRJtlgcataxapi6Lbox+8/5nrLXA6M5+FSD/3wjO96KEdv+KGK4WIE6AAsGKdH0dFE8jgzGVw
uyoyXZg+UWhFrCMB3lbNfY9UsTBJfVx1TlMC1BXaT5qKCgp2N5dF6s2yeNa1kgGvR+xDkxNGDf6q
3xcN3QiC9ofyUyeRaZEacTjUp7bo4VREFtv3txyocbT6B961inhUS3PZNx6nIzJqiZA2CX/QGrlg
7uE1EoXgSJ+N77MdasX5Tl69Cb+fJCAdlbji1LAgWLEPXM0kHyYnfsLHfEXo4bCRdpN+GpPvqyhW
DOk8ZEmrzYglsK38KIIG4Mp0tUoj25nzXhHnkNt0OCLSvzPcTopabRaPl4MnvQQ1tGsKbSafUBR5
gzdjA/f/o9bQKYwZC+fP8Gu50Ib4sYc5BbXEZdUx0Pjc/1nbIuM0t1YFrfLOiWP+Ar0x/WuPrtLZ
gUyRnVBVyHm73be8T9wfE31aJw9E+2a92cjrp0lyCfWoCKjHGxdsPFvPIg1gKVG/IlgKeKEnKu1N
O4PmD//LW/7p6A5V/W1vGZn8jI9ErwVz2cMiyJJfRVaviV5TcC58vrREH6qB9LfJwA7jy4CRu1oP
GsaQRg5ZTMaV1JZ5cFBNHKcJiSDPTqVdKPkjmSUVUlYvEN+08pPGK/4KcTGCAgwwggIIAgEBMEsw
RTELMAkGA1UEBhMCSlAxFTATBgNVBAoTDFdJREUgUHJvamVjdDEfMB0GA1UEAxMWbWVtYmVycyBv
cmllbnRlZCBDQSAwMgICEhAwCQYFKw4DAhoFAKCCARcwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMDcwMzAyMDE1MDIxWjAjBgkqhkiG9w0BCQQxFgQUNVSiLON9EZ48
BBuhlm8dhkA+HiswWgYJKwYBBAGCNxAEMU0wSzBFMQswCQYDVQQGEwJKUDEVMBMGA1UEChMMV0lE
RSBQcm9qZWN0MR8wHQYDVQQDExZtZW1iZXJzIG9yaWVudGVkIENBIDAyAgISEDBcBgsqhkiG9w0B
CRACCzFNoEswRTELMAkGA1UEBhMCSlAxFTATBgNVBAoTDFdJREUgUHJvamVjdDEfMB0GA1UEAxMW
bWVtYmVycyBvcmllbnRlZCBDQSAwMgICEhAwDQYJKoZIhvcNAQEBBQAEgYCWmxFfiDI/bxW6syZ4
0wjn3TTzgt8SMfm29DGfhOoSmq0vykzWtIuM2atsOZzYm6pcTGu/13c1zOUOX/36T58x+4ZNJkOZ
aTz7fEsJ5wUc279I6ryaHDkEt+g6Pb0Qf38aydA+3x1+gmnGouuIi+IF22ueWvs6+OM2S3aIyCiq
mgAAAAAAAA==

--Apple-Mail-1--927990675--


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

--===============1490393390==--




From mip6-bounces@ietf.org Thu Mar 01 21:39:54 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMxfn-00081S-QG; Thu, 01 Mar 2007 21:39:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMxfm-00081N-Gy
	for mip6@ietf.org; Thu, 01 Mar 2007 21:39:06 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HMxfk-0001Kc-0t
	for mip6@ietf.org; Thu, 01 Mar 2007 21:39:06 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Mar 2007 18:38:58 -0800
Message-ID: <45E78E42.2070903@azairenet.com>
Date: Thu, 01 Mar 2007 18:38:58 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] [issue93] Payload Qualifiers when using
	IPv4-UDP	transportfor both IPv4 and IPv6 payloads
References: <20070228025801.ZXHR17816.oaamta02ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070228025801.ZXHR17816.oaamta02ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2007 02:38:58.0845 (UTC)
	FILETIME=[EE113CD0:01C75C73]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, mip6@ietf.org,
	'Sri Gundavelli' <sgundave@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hesham Soliman wrote:
> 
>  > Version field can be used to distinguish that. But, when
>  > a packet is encapsulated in any application header,
>  > it needs to be wrapped in a TLV format. Example: RFC-3519.
>  > If there is no wrapper, application would not even know the
>  > size of that packet, or the type of the packet, unless its
>  > derived from the IP header. That adds some complexity w.r.t
>  > the way applications use the socket interface ..options etc.
>  > Having a wrapper would be usefull. The normal encapsulation
>  > modes in L3 such as IP/IP, IPv6/IPv6, GRE, all have the type
>  > field and so when we wrap a packet in L4, we need an identifier
>  > some where, IMO.
> 
> => I know the following question is not necessarily the crux of your issue
> but does anyone implement MIPv6 as an application? I know it's possible to
> do that but no one seemed to make that choice to my knowledge, but I could
> be wrong.

The first MIPv6 implementation I had worked on (Nokia Research
Center) was all in the kernel. Turned out to be a bad idea.
Causes too much code bloat in the kernel. Has a lot of issues
too. It actually makes sense to implement it in the user space
and only have the tunneling part, Home Address option, routing
header addition and few other things in the kernel.

Vijay

> 
> I'd love to hear what others think, I think it's a good point to discuss. 
> 
> Hesham
> 
>  > 
>  > Thanks
>  > Sri
>  > 
>  > 
>  > On Wed, 28 Feb 2007, Hesham Soliman wrote:
>  > 
>  > > Hi Sri,
>  > >
>  > > Why can't the receiver do the switch on the version field?
>  > > I mean, how does the receiver of any encapsulated packet 
>  > know the version of
>  > > the inner header?
>  > >
>  > > Hesham
>  > >
>  > > > -----Original Message-----
>  > > > From: Sri Gundavelli [mailto:tracker-mip6@mip4.org]
>  > > > Sent: Wednesday, February 28, 2007 8:38 AM
>  > > > To: mip6@ietf.org
>  > > > Subject: [Mip6] [issue93] Payload Qualifiers when using
>  > > > IPv4-UDP transportfor both IPv4 and IPv6 payloads
>  > > >
>  > > >
>  > > > New submission from Sri Gundavelli <sgundave@cisco.com>:
>  > > >
>  > > > Reference to section 4.3.1 and 4.4.1.
>  > > >
>  > > > For the IPv4 transport and with NAT in path, the opaque
>  > > > encapsulation mode of IPv4-UDP for both IPv4 and IPv6
>  > > > payload packets i.e IPv6/IPv4-UDP or IPv4/IPv4-UDP is being
>  > > > recommended by the draft. With out a payload qualifier
>  > > > in the UDP header, I wonder how the tunnel peer handles
>  > > > the packet after decapsulation ? How would it know, if it
>  > > > is an IPv4 payload packet or an IPv6 packet ? Do you expect
>  > > > some packet inspection after decapsulation ?
>  > > >
>  > > > One option is to have thin header such as the MIP Tunnel
>  > > > Data Message from RFC-3519, as suggested by Kent Leung.
>  > > >
>  > > >
>  > > > MIP Tunnel Data Message
>  > > >
>  > > >     0                   1                   2                   3
>  > > >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 
>  > 6 7 8 9 0 1
>  > > >    
>  > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  > > >    |     Type      |  Next Header  |           Reserved  
>  >           |
>  > > >    
>  > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>  > > >
>  > > >
>  > > > We want a quick resolution on this.
>  > > > draft-sgundave-mip6-proxymip6-02.txt
>  > > > has normative reference to the DSMIP6 spec.
>  > > >
>  > > > Thanks
>  > > > Sri
>  > > >
>  > > > ----------
>  > > > category: Technical
>  > > > draft: draft-ietf-mip6-nemo-v4traversal
>  > > > messages: 330
>  > > > nosy: sri
>  > > > priority: Must fix
>  > > > status: No discussion
>  > > > title: Payload Qualifiers when using IPv4-UDP transport for
>  > > > both IPv4 and IPv6 payloads
>  > > >
>  > > > _________________________________________________
>  > > > Mip6 issue tracker <tracker-mip6@mip4.org>
>  > > > <http://www.mip4.org/issues/tracker/mip6/issue93>
>  > > > _________________________________________________
>  > > >
>  > > > _______________________________________________
>  > > > 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 Fri Mar 02 04:37:13 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN4BF-0006BY-OK; Fri, 02 Mar 2007 04:36:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN4BD-0006BS-GK
	for mip6@ietf.org; Fri, 02 Mar 2007 04:35:59 -0500
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN4B9-0000VK-5R
	for mip6@ietf.org; Fri, 02 Mar 2007 04:35:59 -0500
Received: by ug-out-1314.google.com with SMTP id 72so605659ugd
	for <mip6@ietf.org>; Fri, 02 Mar 2007 01:35:54 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=gmDmmmIN8FHiTl6xN97HJQ61V18/t0oR8D+Immk4jK1g5e87jNc56cjsNCRyO/C2qJ/X+in5TDXhRVVE/6MgZStbJ/tD9/dwvopNFd05vgxpm/f0Trm/2iCoyzB88FSGa8cO6fl1gLMtXTo+h2EhC8K+uG2j2iUwtYoBqLLC4GM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=fuJJIZ5zw4ZqFRKqRxK71The1LfG5mDaRYeRCRs6lVn+B8S4sXmUQCFBTVYIsuWXbcW8l7cz7I84B72bxHil3U8rLaQ6vSWfcP0SkpMB99RyO+ZuVqz3xZT9PBUkk9JBSavO/C/ObL1AD7IJupnE5IJcBvSpNvjh4n5N0HYbRk0=
Received: by 10.67.119.9 with SMTP id w9mr3137129ugm.1172828154490;
	Fri, 02 Mar 2007 01:35:54 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Fri, 2 Mar 2007 01:35:54 -0800 (PST)
Message-ID: <eaa74a7e0703020135j6464fd71oe357caee0ffd36af@mail.gmail.com>
Date: Fri, 2 Mar 2007 10:35:54 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
In-Reply-To: <45E73675.6080300@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <459A5A6C.5070602@piuha.net>
	<eaa74a7e0702230640g722a28fcyc89360e69337c768@mail.gmail.com>
	<45E00DD3.1010701@piuha.net> <45E32B26.7050702@azairenet.com>
	<eaa74a7e0702270515v20f5be3ar91f97555539aa1b3@mail.gmail.com>
	<45E4D408.8050709@azairenet.com>
	<eaa74a7e0702280118g5881ffdy8684e84f63880dcb@mail.gmail.com>
	<45E63AE1.4090708@azairenet.com>
	<eaa74a7e0703010627k2c64e311n7e7e1fd148489412@mail.gmail.com>
	<45E73675.6080300@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On 3/1/07, Vijay Devarapalli <vijay.devarapalli@azairenet.com> wrote:
> Gerardo Giaretta wrote:
>
> >> > However, suppose the HA is acting also as VPN concentrator (or 3GPP
> >> > PDG or similar): there may be cases where the MN sets up a SA with
> >> > this box and then use it not for MIPv6. This is an issue in DIME
> >> > design: we are discussing when the authorization for MIPv6 should be
> >> > performed.
> >>
> >> That should be irrelevant. We are talking about DIME extensions
> >> to support MIPv6. If someone co-locates a PDG and a Mobile IPv6
> >> HA, why do we care? It is for them to figure out how to make it
> >> work. :)
> >>
> >
> > Not sure about that. The MIP6 service must be explicitly authorized,
> > so the IKEv2 responder should understand that the IKEv2 exchange is
> > related to MIP6. Otherwise you need to authorize the service when the
> > first BU is sent.
>
> As far as the use of IKEv2 for Mobile IPv6 signaling messages
> goes, a mobile node would not do IKEv2 authentication with a
> home agent unless it is for MIPv6 service. So I don't think a
> separate step is required.
>
> We didn't add a goal in the HA-AAAH goals document to separate
> authentication and authorization, correct?
>

Correct.

> I don't think that someone co-locating a VPN concentrator with
> a MIPv6 home agent is reason enough for us to require separating
> authentication and authorization for basic MIPv6 operation. What
> am I missing here?
>

Nothing. The main reason for authentication and authorization split
discussed in DIME was not related to this issue (but to the EAP
application support). This was a side issue.

Anyway if the group is fine to not consider this issue, that is fine
with me too.

Going back to the original discussion: how can the AAA server provide
the right identity of the MN for DNS update to the HA?

--Gerardo

> Vijay
>

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



From mip6-bounces@ietf.org Fri Mar 02 04:38:38 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN4Di-00056N-Ls; Fri, 02 Mar 2007 04:38:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN4Dg-0004tc-Vl
	for mip6@ietf.org; Fri, 02 Mar 2007 04:38:33 -0500
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN4Dg-0000oZ-0Q
	for mip6@ietf.org; Fri, 02 Mar 2007 04:38:32 -0500
Received: by ug-out-1314.google.com with SMTP id 72so606223ugd
	for <mip6@ietf.org>; Fri, 02 Mar 2007 01:38:31 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Ci/9Ikh4C+B+b2vrw9dR1PE0QxkEUNNdBkEmnrq6xy4Lcvkz+7lz5NbR91IfZGKJ9LeJB7DuglM6U87CzeYb3+r5C3uIWbAKSJq1UwacTWTPnrcOkiB+VVkryjDWDjiJPOGr0MsU0g/KybpmR7+hI7gSNISYwOquxHljHkTGe8w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=X5n4C/L+1JqMXUZZcwikYU0gwDfqCU08OM1HBH3eTnNfNmct08gZDuQxeUB0Mkz7XSMvrWAnxZZLvkSE8feNneQhOP3aF0U3ttcSCTRjmPu90kxDdhgYrswXwCr5zceAWCKx2BvHFjWGEK9PeF0zZW87SGpgHXWTL6zLAhAMBHw=
Received: by 10.67.31.17 with SMTP id i17mr3130798ugj.1172828311218;
	Fri, 02 Mar 2007 01:38:31 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Fri, 2 Mar 2007 01:38:31 -0800 (PST)
Message-ID: <eaa74a7e0703020138k27c3fb2fw16ce73bd11152df6@mail.gmail.com>
Date: Fri, 2 Mar 2007 10:38:31 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBDA16@exchtewks2.starentnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7CCD07160348804497EF29E9EA5560D7FBDA16@exchtewks2.starentnetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
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

On 3/2/07, Chowdhury, Kuntal <kchowdhury@starentnetworks.com> wrote:
> > One mechanism
> >     is to provision the mobile node with an FQDN for a local home
> agent
> >     when it attaches to the local link through an access link specific
> >     mechanism.  For example the FQDN of the local home agent can be
> sent
> >     to the mobile node using DHCP.
>
> Why only FQDN? The local HA address can be sent directly to the MN. Why
> asking the MN to do one more roundtrip with DNS? Just use the DHCP
> options in HIOPT. If DHCP is used by the MN, and if the DHCP server has
> local HA address info, it should be able to give it out to the MN.
>

Kuntal, this text is for split scenario draft. The DHCP option is not
a solution for split scenario.

--Gerardo

> -Kuntal
>
>
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Thursday, March 01, 2007 5:04 PM
> > To: Jari Arkko
> > Cc: Mobile IPv6 Mailing List
> > Subject: Local HA assignment using DNS (was Re: [Mip6] AD review
> ofdraft-
> > ietf-mip6-bootstrapping-split)
> >
> > Jari Arkko wrote:
> > > Vijay,
> > >> There was an explicit requirement to support local HA
> > >> assignment using DNS. IMO, local HA assignment is
> > >> required for any HA discovery/assignment mechanism. So
> > >> I would like to keep the text instead of saying it is
> > >> out of scope.
> > >>
> > >> The example is trying to describe how a particular
> > >> operator may "name" the home agents, what entries appear
> > >> in the DNS servers, and what FQDNs are provisioned in
> > >> the mobile node.
> > >>
> > >> This particular paragraph underwent multiple changes.
> > >> I can re-write the text to better explain how it can be
> > >> done or to address any specific concern.
> > >
> > > The reason that I am reacting on this is that we should
> > > either explain, fully, how to do it or otherwise declare
> > > it out of scope.
> > >
> > > I see several holes in the example text, including, for
> > > instance, how the mobile nodes determine the locations,
> > > how changes in the available locations are managed
> > > between the MN and HA implementations, etc.
> >
> > I re-wrote the text a bit. Here is the new text.
> >
> >     Additionally, the ability to provide a mobile node with a
> localized
> >     home agent (e.g. on the visited link) can help to optimize
> handover
> >     signaling and improve routing efficiency in bi-directional
> tunneling
> >     mode.  There are many mechanisms to assign a local home agent to a
> >     mobile node.  These mechanisms are out of scope for this document,
> >     but a couple of them are described here as examples.  One
> mechanism
> >     is to provision the mobile node with an FQDN for a local home
> agent
> >     when it attaches to the local link through an access link specific
> >     mechanism.  For example the FQDN of the local home agent can be
> sent
> >     to the mobile node using DHCP.  Another mechanism is to specify an
> >     interoperable naming convention for constructing home agent FQDNs
> >     based on the mobile node's location.  For example, a mobile
> network
> >     operator may assign the FQDN "ha.locationA.operator.com" to the
> Home
> >     Agent located in "location A" and the FQDN
> >     "ha.locationB.operator.com" to the Home Agent located in "location
> >     B".  If the Mobile Node is attached to "location A" and wants to
> use
> >     a Home Agent located in "location A", it will set the QNAME to
> >     "ha.locationA.operator.com" in the DNS request.  The Mobile Node
> >     determines that it is attached to "location A" through access link
> >     specific mechanisms.  If the mobile operator changes the location
> >     information for a particular local link, the FQDNs for the home
> >     agents on the local link should also be updated with the new
> location
> >     information.
> >
> >     If the mobile node is unable to discover a local home agent, it
> MUST
> >     use the home agent on its home link.
> >
> > Comments?
> >
> > _______________________________________________
> > 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 Mar 02 04:58:45 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN4Wb-0006NN-Az; Fri, 02 Mar 2007 04:58:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN4Wa-0006ND-5g
	for mip6@ietf.org; Fri, 02 Mar 2007 04:58:04 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN4WV-0005Ft-MC
	for mip6@ietf.org; Fri, 02 Mar 2007 04:58:04 -0500
Received: from [88.234.3.65] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HN4W42Fc3-00068i; Fri, 02 Mar 2007 04:57:44 -0500
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Chowdhury, Kuntal'" <kchowdhury@starentnetworks.com>,
	"'Gerardo Giaretta'" <gerardo.giaretta@gmail.com>,
	"'Vijay Devarapalli'" <vijay.devarapalli@azairenet.com>
Subject: RE: [Mip6] DSMIP6 solution and integrated bootstrap scenario
Date: Fri, 2 Mar 2007 11:57:29 +0200
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.3028
Thread-Index: Acdb6RpTZrVFAX7LS56FwlZy2meUrgAMVQsAACWnMaA=
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBD9F8@exchtewks2.starentnetworks.com>
Message-ID: <0MKp2t-1HN4W42Fc3-00068i@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Provags-ID2: V01U2FsdGVkX1/hnykUFa745YwAN50xuhuHxGVzVccUjGioxjP
	00BAE2SPFcjLUMbVjCh/ZFyIpZH5eVGPDEj9qdycBuT7lWYY0V
	RUiAiloBO+0Eca7A7fOYQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: mip6@ietf.org, 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 agree with Vijay. Text on section 2.1 is needed since in
> > bootstrapping-split draft we refer only to IPv6 HA addresses and AAAA
> > records.
> >
> [KC>] OK. I can live with some _additional_ clarification around the use
> of DNS for DSMIP6 bootstrapping in the DSMIP6 I-D. But, we should also
> add references to the integrated scenario which uses DHCP (albeit with
> caveats like v4 only ASP).

This makes sense. Why would there be an objection to such a thing?

Alper



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



From mip6-bounces@ietf.org Fri Mar 02 05:34:07 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN558-0002ef-BX; Fri, 02 Mar 2007 05:33:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN53e-00028a-9g
	for mip6@ietf.org; Fri, 02 Mar 2007 05:32:14 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN4pP-0000fe-Gv
	for mip6@ietf.org; Fri, 02 Mar 2007 05:17:33 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l22AHUL1002589
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Fri, 2 Mar 2007 02:17:30 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l22AHUmF028747
	for <mip6@ietf.org>; Fri, 2 Mar 2007 02:17:30 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Mar 2007 02:17:29 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 2 Mar 2007 02:17:30 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC: Review of draft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBA==
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 02 Mar 2007 10:17:29.0450 (UTC)
	FILETIME=[FBAA6CA0:01C75CB3]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Subject: [Mip6] WGLC: Review of
	draft-ietf-mip6-bootstrapping-integrated-dhc-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,
Some comments on the draft:

1. The title of the document should be changed to reflect the real
solution provided - something along the lines of "Dynamic MIP6 Home
Agent Discovery using AAA and DHCP" would be more appropriate. The
current title seems to indicate that the document is providing a
complete MIP6 bootstrapping solution, which is not the case. Also, this
solution does not function without AAA, hence, it is not a solution that
employs DHCP alone.=20

2. The assumptions made by this solution must be stated in a separate
section (perhaps under introduction?). I think Kilian had a reasonable
list in one of his emails. The assumptions are currently scattered
throughout the document and this is not entirely clear. So, collectively
listing that would be good.=20

3. The method by which the DHCP Relay maintains the mapping of the Home
Agent and corresponding mobile node is unclear. At the end of network
access authentication, it is assumed that the HA address is sent to the
NAS/DHCP Relay. Subsequently, when the MN attempts to use DHCP to obtain
the HA address, the Relay agent must be able to associate the incoming
request with the appropriate HA that was assigned. There is no
assumption on the client ID used in the DHCP message to be of any use in
this respect and that makes sense. However, the use of a link layer
address to maintain such a mapping is problematic. For one, link layer
addresses may be easily spoofed, causing the wrong HA address to be sent
to the MN. Further, link visibility at the NAS, while feasible
sometimes, may not be always available.=20

4. The security considerations section is confusing to me. In
particular:=20

   - The first paragraph states "No new security considerations are
imposed by the usage of this document.  The security mechanisms provided
by [RFC2865] and [RFC3588] are applicable and provide adequate security
for this purpose." This indicates that the requirements for AAA
transport security are the same as that for MIP6 HA discovery. This is
not quite true - depending on what information is transported in AAA and
the sensitivity of it, the requirements are different. For instance,
keys transported using AAA will need to be encrypted and integrity
protected, while, HA information may only need integrity protection.
Hence, first stating the requirements and then stating that RADIUS
and/or Diameter security is sufficient would be good.=20

   - The next paragraph states "The communication between the NAS/DHCP
relay agent to the DHCP server must be authenticated, integrity and
replay protected.  Deployments MAY either rely on lower-layer security,
(i.e., physical or link layer security), or rely on security mechanisms
specifically defined for DHCPv6, such as [RFC4030]." The first sentence
seems to be inconsistent with the next one. For one, it is necessary to
state if the protection needed is end-to-end between the relay agent and
the server. Next, I don't see how physical security can provide
authentication or replay protection.=20

   - The following paragraph states a similar requirement between the
DHCP client and server. But then it goes on to say that either
link-layer security or DHCP security may be used. Link-layer security in
this case, is incapable of providing the stated security "between the
DHCP client and server". It would only provide the security between the
client and the access enforcement point. Also, I'm not sure what it
means to say that such security is "required". For instance, if a
particular technology decided to use no message authentication at the
link layer, can this method of bootstrapping not be used? I don't think
that is the intention, but, it needs to be clarified.=20

   - The next paragraph states, "An adversary that is able to modify
home agent information can force the mobile node to use a different home
agent than intended by the MSA.  However, this type of attack can be
detected by the security mechanism between the mobile node and the home
agent." I'm not sure how this attack is detectable by the security
mechanism between the MN and HA - it may be detectable if IKEv2 PSKs are
used between the MN and HA. If IKEv2 with EAP is used, as long as the HA
is able to act as an EAP authenticator and get the MN authenticated via
the AAA server and obtain an MSK, it doesn't seem to be detectable. In
that case, the AAA server wouldn't be able to tell the difference
between this and any other EAP exchange. It is then only detectable if
the AAA server policy prevents use of that HA as an authenticator.=20

   - The section currently states, "If the home agent selected by the
mobile node is local or nearby, (as in section 3.2.2), disclosing the
mobile node's home address (e.g., by updating the mobile node's FQDN in
the DNS) has the potential to expose some information about the mobile
node's location." I don't understand the intended implication here. How
is this different from an HA in the MSP performing the DNS update?=20

   - The next paragraph states, "...For instance, if an attacker knows
that the mobile node's home agent selection policy is to bootstrap with
a new local home agent whenever entering a new network (e.g., because
the mobile node wants to improve routing efficiency in Bi-directional
Tunneling mode), the attacker can track the mobile node's movement if it
is aware of the mobile node's current home addresses." The MN's movement
is tracked by the attacker using what? The HoAs are changing with every
new HA in every local network. If anything, this should make tracking
the MN more difficult. I don't follow the discussion in that paragraph
or the conclusion.=20

   - Finally, the last paragraph states, "Consequently, if a high level
of location privacy is desired, a mobile node should not switch to local
home agents in an eager manner or should not reveal its home address to
untrusted nodes. Furthermore, the disclosure of policy information that
can help locating the mobile node should be carefully considered." Given
that this is first discussion of privacy in the document, what does
"high level of location privacy" mean? If there is such a thing, what is
then a "lower level of location privacy" and how is that achieved?
Further, it is not clear as to what element of privacy is needed or
which elements the privacy is needed from. This text is recommending
against using local home agents - is this to provide privacy from the
local network? If this is only about providing privacy from
correspondent and other observing nodes, I don't understand the
difference made by local or remote HAs. Also, I don't follow the
disclosure of policy information - this document is only discussing HA
bootstrapping; is there such policy information that may be disclosed
leading to this privacy concern?=20

5. I noticed a discussion based on Kilian's comments to include the HoA
allocation via DHCP as a possible option. If we decide to include that,
it would be important to talk about how that HoA gets tied to the SA
created between the MN and HA. If the HoA is assinged via IKEv2, IKEv2
takes care of such a binding. If not, we need to describe how the
address is bound to the SA. The use of DHCP to assign anything requiring
particular security values is tricky to handle and I suggest that we
don't get into that in this draft.=20

6. In general, a number of the security considerations revolving around
packet modification attacks apply equally to the DHCP and DNS solutions.
However, in the DNS case, the use of DNSSEC between the DNS client and
server is the only thing needed to ensure protection against such
attacks. In this case, the security solution needed relies on several
transitive trust relationships - trust between AAA parties, DHCP Relay
Agent and Server, and DHCP client and server. This is not unreasonable,
but, probably worth mentioning.=20

Thanks,
Vidya

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



From mip6-bounces@ietf.org Fri Mar 02 06:27:27 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN5uh-0007CS-AW; Fri, 02 Mar 2007 06:27:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN5ue-0007CI-Eu
	for mip6@ietf.org; Fri, 02 Mar 2007 06:27:01 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN5ue-0005H8-0M
	for mip6@ietf.org; Fri, 02 Mar 2007 06:27:00 -0500
Received: from [88.234.3.65] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1HN5tp2CnW-0008U8; Fri, 02 Mar 2007 06:26:35 -0500
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Narayanan, Vidya'" <vidyan@qualcomm.com>,
	"'Mobile IPv6 Mailing List'" <mip6@ietf.org>
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Fri, 2 Mar 2007 13:25:59 +0200
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.3028
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5g
In-Reply-To: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
Message-ID: <0MKoyl-1HN5tp2CnW-0008U8@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Provags-ID2: V01U2FsdGVkX1/eEpUeXbVD64qtvdMT6zgGlAiY4xVPOuqsT52
	TosHlZ7TzFCz2hqedsypTAFSuLfFPIpkUt5lVis+hUm3RJBMUr
	WLVbnW46tGAyxo3KDC8vw==
X-Spam-Score: 1.1 (+)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
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 Vidya,

Thank you for the review and feedback.

> 1. The title of the document should be changed to reflect the real
> solution provided - something along the lines of "Dynamic MIP6 Home
> Agent Discovery using AAA and DHCP" would be more appropriate. The
> current title seems to indicate that the document is providing a
> complete MIP6 bootstrapping solution, which is not the case. Also, this
> solution does not function without AAA, hence, it is not a solution that
> employs DHCP alone.

The complete solution also includes IKEv2.
So, either we should state all components of the solution in the title, or
none. I think "none" is better, along the lines of what we did for the split
scenario.


> 2. The assumptions made by this solution must be stated in a separate
> section (perhaps under introduction?). I think Kilian had a reasonable
> list in one of his emails. The assumptions are currently scattered
> throughout the document and this is not entirely clear. So, collectively
> listing that would be good.

Good idea.


> 
> 3. The method by which the DHCP Relay maintains the mapping of the Home
> Agent and corresponding mobile node is unclear. At the end of network
> access authentication, it is assumed that the HA address is sent to the
> NAS/DHCP Relay. Subsequently, when the MN attempts to use DHCP to obtain
> the HA address, the Relay agent must be able to associate the incoming
> request with the appropriate HA that was assigned. There is no
> assumption on the client ID used in the DHCP message to be of any use in
> this respect and that makes sense. However, the use of a link layer
> address to maintain such a mapping is problematic. For one, link layer
> addresses may be easily spoofed, causing the wrong HA address to be sent
> to the MN. Further, link visibility at the NAS, while feasible
> sometimes, may not be always available.

This is a generic issue with the RFC4014, which we are simply using not
defining. We can discuss this on a separate thread in DHC mailing list if
you like.


> 
> 4. The security considerations section is confusing to me. In
> particular:
> 
>    - The first paragraph states "No new security considerations are
> imposed by the usage of this document.  The security mechanisms provided
> by [RFC2865] and [RFC3588] are applicable and provide adequate security
> for this purpose." This indicates that the requirements for AAA
> transport security are the same as that for MIP6 HA discovery. This is
> not quite true - depending on what information is transported in AAA and
> the sensitivity of it, the requirements are different. For instance,
> keys transported using AAA will need to be encrypted and integrity
> protected, while, HA information may only need integrity protection.
> Hence, first stating the requirements and then stating that RADIUS
> and/or Diameter security is sufficient would be good.

Good idea.


> 
>    - The next paragraph states "The communication between the NAS/DHCP
> relay agent to the DHCP server must be authenticated, integrity and
> replay protected.  Deployments MAY either rely on lower-layer security,
> (i.e., physical or link layer security), or rely on security mechanisms
> specifically defined for DHCPv6, such as [RFC4030]." The first sentence
> seems to be inconsistent with the next one. 

You are right. It should read "MUST", not "MAY".

> For one, it is necessary to
> state if the protection needed is end-to-end between the relay agent and
> the server. 

Yes it is. And we can state that.

> Next, I don't see how physical security can provide
> authentication or replay protection.

I don't think use of RFC 4030 is mandatory. Deployments are free to use
physical security instead of RFC 4030. This, again, is not a specific issue
for our I-D. If you like, we can discuss this under another thread.


> 
>    - The following paragraph states a similar requirement between the
> DHCP client and server. But then it goes on to say that either
> link-layer security or DHCP security may be used. Link-layer security in
> this case, is incapable of providing the stated security "between the
> DHCP client and server". It would only provide the security between the
> client and the access enforcement point. Also, I'm not sure what it
> means to say that such security is "required". For instance, if a
> particular technology decided to use no message authentication at the
> link layer, can this method of bootstrapping not be used? I don't think
> that is the intention, but, it needs to be clarified.

I think trying to explain DHCP security is getting us into trouble. I would
really want to say in this document "DHCP is secured however it is secured"
:-) People can start discussing DHCP security in general. But that does not
take anything away from the use of DHCP, especially the way we are using --
standard. 

Would you agree we should reduce this whole discussion about DHCP security?



> 
>    - The next paragraph states, "An adversary that is able to modify
> home agent information can force the mobile node to use a different home
> agent than intended by the MSA.  However, this type of attack can be
> detected by the security mechanism between the mobile node and the home
> agent." I'm not sure how this attack is detectable by the security
> mechanism between the MN and HA - it may be detectable if IKEv2 PSKs are
> used between the MN and HA. If IKEv2 with EAP is used, as long as the HA
> is able to act as an EAP authenticator and get the MN authenticated via
> the AAA server and obtain an MSK, it doesn't seem to be detectable. 

Not "any" HA on the Internet can act as a pass-through authenticator and
talk to the home AAA server of the MN. We shall clarify that in the text.

> In
> that case, the AAA server wouldn't be able to tell the difference
> between this and any other EAP exchange. It is then only detectable if
> the AAA server policy prevents use of that HA as an authenticator.

Yes, and it should. A AAA server would not be passing MSKs to any one how
happens to forward EAP traffic.



> 
>    - The section currently states, "If the home agent selected by the
> mobile node is local or nearby, (as in section 3.2.2), disclosing the
> mobile node's home address (e.g., by updating the mobile node's FQDN in
> the DNS) has the potential to expose some information about the mobile
> node's location." I don't understand the intended implication here. How
> is this different from an HA in the MSP performing the DNS update?

I'd not mind removing this text.


> 
>    - The next paragraph states, "...For instance, if an attacker knows
> that the mobile node's home agent selection policy is to bootstrap with
> a new local home agent whenever entering a new network (e.g., because
> the mobile node wants to improve routing efficiency in Bi-directional
> Tunneling mode), the attacker can track the mobile node's movement if it
> is aware of the mobile node's current home addresses." The MN's movement
> is tracked by the attacker using what? The HoAs are changing with every
> new HA in every local network. If anything, this should make tracking
> the MN more difficult. I don't follow the discussion in that paragraph
> or the conclusion.

I think you have a valid point, and I don't mind removing this text.


> 
>    - Finally, the last paragraph states, "Consequently, if a high level
> of location privacy is desired, a mobile node should not switch to local
> home agents in an eager manner or should not reveal its home address to
> untrusted nodes. Furthermore, the disclosure of policy information that
> can help locating the mobile node should be carefully considered." Given
> that this is first discussion of privacy in the document, what does
> "high level of location privacy" mean? If there is such a thing, what is
> then a "lower level of location privacy" and how is that achieved?
> Further, it is not clear as to what element of privacy is needed or
> which elements the privacy is needed from. This text is recommending
> against using local home agents - is this to provide privacy from the
> local network? If this is only about providing privacy from
> correspondent and other observing nodes, I don't understand the
> difference made by local or remote HAs. Also, I don't follow the
> disclosure of policy information - this document is only discussing HA
> bootstrapping; is there such policy information that may be disclosed
> leading to this privacy concern?

I personally don't mind removing this text either.


> 
> 5. I noticed a discussion based on Kilian's comments to include the HoA
> allocation via DHCP as a possible option. If we decide to include that,
> it would be important to talk about how that HoA gets tied to the SA
> created between the MN and HA. If the HoA is assinged via IKEv2, IKEv2
> takes care of such a binding. If not, we need to describe how the
> address is bound to the SA. The use of DHCP to assign anything requiring
> particular security values is tricky to handle and I suggest that we
> don't get into that in this draft.

I'll leave this to Kuntal. 

> 6. In general, a number of the security considerations revolving around
> packet modification attacks apply equally to the DHCP and DNS solutions.
> However, in the DNS case, the use of DNSSEC between the DNS client and
> server is the only thing needed to ensure protection against such
> attacks. In this case, the security solution needed relies on several
> transitive trust relationships - trust between AAA parties, DHCP Relay
> Agent and Server, and DHCP client and server. This is not unreasonable,
> but, probably worth mentioning.

Sure we can mention that. And that's what RFC 4014 is built upon. We are
simply using that model, not introducing anything new.

Thanks again, these are very useful comments.

Alper



> 
> Thanks,
> Vidya
> 
> _______________________________________________
> 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 Mar 02 07:50:31 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN7CR-0000DB-Fw; Fri, 02 Mar 2007 07:49:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN7CP-0000Cz-U1
	for mip6@ietf.org; Fri, 02 Mar 2007 07:49:25 -0500
Received: from cluster-j.mailcontrol.com ([86.111.223.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN7CO-00034n-Ca
	for mip6@ietf.org; Fri, 02 Mar 2007 07:49:25 -0500
Received: from rly24j.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly24j.srv.mailcontrol.com (MailControl) with ESMTP id
	l22Cn7ws014489
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Fri, 2 Mar 2007 12:49:09 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly24j.srv.mailcontrol.com (MailControl) id l22CmcpA013337
	for mip6@ietf.org; Fri, 2 Mar 2007 12:48:38 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly24j-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l22CmWeT013153; Fri, 02 Mar 2007 12:48:38 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4f67_70222174_c8b9_11db_806a_0030482aac25;
	Fri, 02 Mar 2007 13:27:51 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030213483046-1127665 ;
	Fri, 2 Mar 2007 13:48:30 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.155,BAYES_00: -1.665,TOTAL_SCORE: -1.820
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Fri, 2 Mar 2007 13:53:26 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
In-Reply-To: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAAA+ifw
References: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F01278512@lan-ex-01.panasonic.de>
Date: Fri, 2 Mar 2007 13:45:16 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-06-00-00 (www.mailcontrol.com) on 10.74.1.134
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.2 (+)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
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 Vidya,

I'll comment on your questions about the location privacy issue
described in the security considerations section, since the text was
provided by James and me. However, the initial text was longer, maybe we
cut too much and need to add some more text again to make the issue
clear.=20

I don't agree with removing the text as Alper suggested. IMHO, the text
describes a valid security issue that that implementors should be aware
of and that can be avoided when following the recommendations in the
text. Thus, the text is important IMHO.

The issue is the following:

A HoA anchored at a local HA (henceforth called local HoA) has a prefix
belonging to the access network the MN is currently attached to.
Consequently, a local HoA contains some location information. If any
entity =20
1. knows the MN's HoA and=20
2. knows that the corresponding HA is currently a *local* HA,=20
it can infer the MN's location from the local HoA prefix.

The attacker (any node that is not authorized to get the MN's location)
can get the MN's location if

1. If the attacker can obtain the MN's local HoA, e.g., by monitoring
the DNS entry (in case the MN's DNS entry is always updated after
bootstrapping) or by initiating communication with the MN (if the MN
will use the local HoA for optimized communication) or by eavesdropping
the MN's traffic.

2. If the attacker knows that the HoA obtained in 1 is local. This is
possible under certain circumstances, e.g., when a MN's or an operator's
policy is that the MN shall always try to bootstrap with a local HA when
entering an ASP's network (this may make sense for routing efficiency
reasons) and the attacker is aware of this policy.

See some more comments inline.

>    - The section currently states, "If the home agent selected by the
> mobile node is local or nearby, (as in section 3.2.2), disclosing the
> mobile node's home address (e.g., by updating the mobile=20
> node's FQDN in
> the DNS) has the potential to expose some information about the mobile
> node's location." I don't understand the intended implication=20
> here. How
> is this different from an HA in the MSP performing the DNS update?=20

If a HA is not local, the corrsponding HoA prefix does not contain
location information and the issue described above doesn't exist. Maybe
we should add something like "A local HoA contains location information,
since the prefix is linked to the MN's current access network.".

>=20
>    - The next paragraph states, "...For instance, if an attacker knows
> that the mobile node's home agent selection policy is to=20
> bootstrap with
> a new local home agent whenever entering a new network (e.g., because
> the mobile node wants to improve routing efficiency in Bi-directional
> Tunneling mode), the attacker can track the mobile node's=20
> movement if it
> is aware of the mobile node's current home addresses." The=20
> MN's movement
> is tracked by the attacker using what? The HoAs are changing=20
> with every
> new HA in every local network. If anything, this should make tracking
> the MN more difficult. I don't follow the discussion in that paragraph
> or the conclusion.=20

If the attacker monitors the DNS entry of the MN and if the DNS entry of
the MN is always updated with a new local HoA after bootstrapping with a
new local HA, the attacker can track the MN's movement to some extent.

>=20
>    - Finally, the last paragraph states, "Consequently, if a=20
> high level
> of location privacy is desired, a mobile node should not=20
> switch to local
> home agents in an eager manner or should not reveal its home=20
> address to
> untrusted nodes. Furthermore, the disclosure of policy=20
> information that
> can help locating the mobile node should be carefully=20
> considered." Given
> that this is first discussion of privacy in the document, what does
> "high level of location privacy" mean? If there is such a=20

The "level of location privacy" refers to the granularity of disclosed
location information. For some users it may be acceptable to disclose
the prefix of the current access network, while it is not acceptable to
disclose the current AR. Such "access network-level" of location privacy
can, e.g., be achieved with localized MM, where a MN's MIPv6 CoA is
equal to the MN's PMIP-HoA anchored at a local PMIP-HA. In this case, an
attacker acting as correspondent node could at most learn the MN's
current access network (from the MN's CoA in MIPv6 route optimization
mode).

For other people this "level" of location privacy is not acceptable.
They have stronger requirements on location privacy, where the attacker
cannot figure out the current access network. For instance, some users
don't want that it is possible to find out that they are on a business
trip or on vacation in another country (e.g., to prevent that someone
uses this information for a burglary). This was referred to as "high
level" of location privacy. Maybe we need to add some text about this.

> thing, what is
> then a "lower level of location privacy" and how is that achieved?
> Further, it is not clear as to what element of privacy is needed or
> which elements the privacy is needed from. This text is recommending
> against using local home agents - is this to provide privacy from the
> local network? If this is only about providing privacy from
> correspondent and other observing nodes, I don't understand the
> difference made by local or remote HAs. Also, I don't follow the
> disclosure of policy information - this document is only discussing HA
> bootstrapping; is there such policy information that may be disclosed
> leading to this privacy concern?=20

The policy information refers to the MN's policy to eagerly bootstrap
with a local HA and updating the HoA when entering a new network.

Regards,

Kilian


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Fri Mar 02 08:00:41 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN7N3-0005Uf-Id; Fri, 02 Mar 2007 08:00:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN7N1-0005TR-VP
	for mip6@ietf.org; Fri, 02 Mar 2007 08:00:24 -0500
Received: from cluster-j.mailcontrol.com ([86.111.223.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN7N0-0004Ye-8p
	for mip6@ietf.org; Fri, 02 Mar 2007 08:00:23 -0500
Received: from rly37j.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly37j.srv.mailcontrol.com (MailControl) with ESMTP id
	l22D0JGB018444
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Fri, 2 Mar 2007 13:00:21 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly37j.srv.mailcontrol.com (MailControl) id l22CxURK013768
	for mip6@ietf.org; Fri, 2 Mar 2007 12:59:30 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly37j-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l22CxTak013676; Fri, 02 Mar 2007 12:59:30 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4ecc_f7906bce_c8ba_11db_86a2_0030482aac25;
	Fri, 02 Mar 2007 13:38:47 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030213592575-1128441 ;
	Fri, 2 Mar 2007 13:59:25 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.154,BAYES_00: -1.665,TOTAL_SCORE: -1.819
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Fri, 2 Mar 2007 14:04:20 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
In-Reply-To: <45E760C3.5050103@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
Thread-Index: AcdcWHkR7c9gdeRHSVOuw72j+n57jAARhdKQ
References: <4D2F935F08D41A4C8866693F4F0D7C4F01278236@lan-ex-01.panasonic.de>
	<45E760C3.5050103@azairenet.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F01278515@lan-ex-01.panasonic.de>
Date: Fri, 2 Mar 2007 13:56:22 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MailControl A-07-06-90 (www.mailcontrol.com) on 10.74.1.147
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
> Sent: Freitag, 2. M=E4rz 2007 00:25
> To: Kilian Weniger
> Cc: Jari Arkko; Mobile IPv6 Mailing List; James Kempf
> Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
>=20
> Kilian Weniger wrote:
>=20
> >>>    If an anycast address is returned in response to DNS=20
> >> resolution of
> >>>    an FQDN, the IKEv2 transaction between the Mobile Node and Home
> >>>    Agent is slightly modified. The Mobile Node sends the=20
> IKE_SA_INIT
> >>>    request to the anycast address. The node which has the anycast
> >>>    address assigned to one of its network interfaces=20
> selects a Home
> >>>    Agent address from the set of Home Agents managed by the=20
> >> node, and
> >>>    forwards the IKE_SA_INIT. If the set of Home Agents is=20
> >> empnty, the
> >>>    node simply drops the packet. The Home Agent answers=20
> >> using its own
> >>>    address, and includes an "under attack" cookie, in=20
> >> accordance with
> >>>    RFC 4306 [7]. The Mobile Node notes the Home Agent address and
> >>>    resends the IKE_SA_INIT message to the Home Agent,=20
> along with the
> >>>    cookie.=20
> >> There are several issues in this. First, I think I understand
> >> at least one reason why the cookie exchange makes sense,
> >> but is that something that has to be mandated? What if the
> >=20
> > There were two reasons for mandating the cookie exchange:
> > 1. anycast HA address is typically a single well-known and public
> > address, which makes it a possible target of DoS attacks.=20
> > 2. less impact on IKEv2 exchange, since the complete IKEv2=20
> exchange is
> > done with unicast address.
>=20
> In my mind, the second one was the main reason.
>=20
> > If nobody sees a big issue with an anycasted IKE_SA_INIT=20
> followed by a
> > unicast IKE_SA_INIT response without cookie, I'm fine with "SHOULD"
> > instead of "MUST" for the cookie (Vijay, from your reply it=20
> seems you
> > have concerns?). Using the cookie due to reason 1 can be left to
> > operator's decision IMHO.
>=20
> Lets get the mechanism right. I prefer not to add yet
> another optional mechanism. If its not needed we should
> remove it.
>=20
> The way I see it the cookie is used by the responder (the
> HA that sent the cookie) to tie the first IKE_SA_INIT
> exchange with the second one. The cookie is also used by
> the initiator (the mobile node) to figure out why its
> first IKE_SA_INIT exchange did not succeed and why it
> needs to do a second IKE_SA_INIT exchange.

Those are reasons for having a cookie when two IKE_SA_INIT exchanges are =
done. I assume that we only have one IKE_SA_INIT exchange if we don't =
use the cookie. Then the question is whether there is a problem, when an =
IKE_SA_INIT *anycast* request is followed by an IKE_SA_INIT unicast =
response *without cookie*, followed by the usual IKE_SA_AUTH exchange =
etc, i.e., is there a problem with the following exchanges:

        Initiator                         Responder ("best" HA)=20
       -----------                        ---------------------=20
   =20
       (IP_I:500 -> ANYCAST:500)=20
       HDR(A,0), SAi1, KEi, Ni   -->=20
   =20
                                 (IP_R:500 -> IP_I:500)=20
                             <-- HDR(A,B), SAr1, KEr, Nr,[CERTREQ]=20

      =20

       (IP_I:500 -> IP_R:500)=20
       HDR(A,B), SK {IDi, [CERT,] [CERTREQ,] =20
       [IDr,]AUTH, SAi2, TSi, TSr} -->=20
   =20
                                 (IP_R:500 -> IP_I:500)=20
                             <-- HDR(A,B), SK {IDr, [CERT,] AUTH,=20
                                                 SAr2, TSi, TSr}=20
	...


>=20
> >> home network simply figures out what HA should be used and
> >> responds in the usual IKEv2 way?
> >=20
> > yes, IMHO we can relax this and it can be left to HA
> > configuration/operator's decision whether HA always=20
> includes cookie or
> > not (see above).=20
>=20
> I would prefer one concrete way of doing it.
>=20
> >> Secondly, responding with the home agent's own address
> >> is in violation of a MUST in RFC 4306, Section 2.11. I talked
> >> to one of the IKEv2 designers about this and his advice
> >> was that the MUST may have been a mistake. Or at least it
> >> should be limited to unicast addresses, and leave the behaviour
> >> for anycast addresses for future documents. In any case,
> >> this deviation from RFC 4306 should be highlighted and
> >> justified in the document.
> >=20
> > we could add something like "the MUST in RFC4306 refers to unicast
> > only".=20
>=20
> How about the following text?
>=20
>    Note that when the mobile node sends an IKE_SA_INIT request
>    message to an anycast address, the response comes back from
>    a unicast address.  RFC 4306 requires that the responder MUST
>    use the destination address on the request message as the
>    source address on the response message.  It is likely that
>    RFC 4306 was talking about unicast addresses in that context.
>    The mobile node implementation compliant to this specification
>    must relax the requirement from RFC 4306 and be willing to
>    process the response from an unicast address when it sends a
>    request to an anycast address.

sounds good to me.

>=20
> >> The third issue is the above notion of a node that owns an
> >> anycast address. How does this relate to the usual arrangement
> >> where the routing system handles the delivery of the anycast
> >> packets to the "closest" place that advertises that address?
> >=20
> > all HAs on home link should have same distance in hops from=20
> MN, so there
> > shouldn't be any impact on the notion of delivery of=20
> anycast packets by
> > the routing system. This forwarding allows the operator to=20
> control the
> > assignment of a HA on the home link on a per-case basis based on
> > parameters defined by operator(e.g., load).
> >=20
> >> When you say "forwards", do you mean that the packet is
> >> forwarded unmodified, or that the particular home agent's
> >> address replaces the destination address?=20
> >=20
> > good question. Some options for forwarding are=20
> > 1. MAC address replacement,=20
> > 2. IP tunneling,
> > 3. IP address replacement.=20
> >=20
> > The first (and maybe the second) option have the issue that=20
> the receiver
> > of a unmodified packet has no way to determine whether the=20
> packet was
> > already forwarded by another HA or comes from the MN.=20
> Hence, it would
> > apply the same mechanism to forwarded packets as to packets received
> > directly from the MN. This means that unmodified packets may be
> > forwarded many times, if the considered parameters (e.g., load) have
> > changed since the last forwarding or are not the same at=20
> all HAs. This
> > could be prevented by modifying forwarded packets somehow,=20
> so that the
> > HA is able to identify those and doesn't apply the=20
> forwarding mechanism
> > to already forwarded packets. This is not needed if the=20
> third option is
> > used.
>=20
> We already say the following in the draft.
>=20
>     Note that this procedure requires the implementation of anycast
>     forwarding in such a way that the Home Agent can distinguish
>     between an IKE_SA_INIT forwarded through an anycast address and
>     one sent directly from the Mobile Node.

Right. But the current text doesn't say how the IKE_SA_INIT can be =
forwarded and how the HA can distinguish between forwarded packets and =
packets coming from the MN. Since this is required for interoperability, =
don't we need to specify this?

>=20
> >> Four: What happens when the IKE SA dies or is
> >> deleted, but a binding for the mobile node remains
> >> in the selected home agent? Will the mobile node
> >> re-establish the IKE SA using the anycast address,
> >> or the address of the selected home agent?
> >=20
> > Yes, some text should be added about that. The MN could first try to
> > re-establish the SA with the current HA's unicast address, as Vijay
> > said. But if this fails, the MN should try to find a new=20
> HA, e.g., by
> > using the anycast HA assignment.=20
>=20
> How about the following text?
>=20
>    A mobile node's security associations with its home agent may
>    expire while it still has a valid binding cache entry at the
>    the home agent.  In this case, the mobile node MUST NOT use an
>    anycast address as the destination address in the IKE_SA_INIT
>    exchange to setup new security associations.  It MUST try to
>    setup security associations with its existing home agent.

Sounds good to me. We could additionally specify the behaviour for the =
case that the IKE SA dies before the lifetime expires. In this case the =
mobile node should try to find a new home agent IMHO:

     If the security associations with the home agent die before=20
     they expire, e.g., because the mobile node detects that the=20
     peer is dead or because the peer deleted the security =20
     associations), the mobile node should try to bootstrap with a=20
     new home agent using one of the mechanisms specified in this=20
     document.

Regards,

Kilian

>=20
> Vijay
>=20
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Fri Mar 02 08:14:59 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN7at-00049j-0n; Fri, 02 Mar 2007 08:14:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN7ar-00048y-5b
	for mip6@ietf.org; Fri, 02 Mar 2007 08:14:41 -0500
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN7Vs-0005cM-1U
	for mip6@ietf.org; Fri, 02 Mar 2007 08:09:33 -0500
Received: by ug-out-1314.google.com with SMTP id 72so648127ugd
	for <mip6@ietf.org>; Fri, 02 Mar 2007 05:09:31 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Zs6S7oiLT6dikuwBb2z+k+OVu2LyauZbTPcNSlS2L73uIjubRorD7gBgpFXL4oHLE0G0LAg9TKXJFBk9qDSbDfq0bK+68ZFPzazNAxR+8NqIeNV/rIQNUd3pe1Z/NOtBQ5OhZti/hqChK5FNPscxgIpIn6Jms4Le00iuddZabyg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=PkmlhnEBg9EOAffRpD6/gKUSEIncBFotF6g6x8cdscI0mSjgzS14R9SN1AAnlb8dmk3WWjKri5Z7nGahpwVUNkuV38GZ5eQgiOV1rbgJpk/U49uptygq4d3wnR9vRrWy16IAbXJ+SMLc+Aq5SUKMd7c4wPXkyzXgSYJLvWmsrAA=
Received: by 10.78.151.3 with SMTP id y3mr273305hud.1172840971241;
	Fri, 02 Mar 2007 05:09:31 -0800 (PST)
Received: by 10.78.106.13 with HTTP; Fri, 2 Mar 2007 05:09:31 -0800 (PST)
Message-ID: <729b68be0703020509s2a346be6h326f60896e370982@mail.gmail.com>
Date: Fri, 2 Mar 2007 14:09:31 +0100
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Francis Dupont" <Francis.Dupont@fdupont.fr>
Subject: Re: [Mip6] Revised Milestones for MIP6 Working Group
In-Reply-To: <200703012041.l21KfdkB021368@tao.fdupont.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <28CEA477BE98ED48AF08A0B637A74BF40321CC21@xmb-sjc-224.amer.cisco.com>
	<200703012041.l21KfdkB021368@tao.fdupont.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>, 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,

I agree with Francis, I don't understand why this proposal should be
Experimental knowing this one is only based on PS protocols.

Best regards.

JMC, back in business

2007/3/1, Francis Dupont <Francis.Dupont@fdupont.fr>:
>  In your previous mail you wrote:
>
>         It shows up in the ID-Tracker as Experimental. Was there a
>    change to this?It's intended status is  Experimental. Isn't it?
>
> => the intended status is Proposed Standard as the RFC 4449 is.
>
> Thanks
>
> Francis.Dupont@fdupont.fr
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Fri Mar 02 08:22:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HN7i5-0007Vh-SY; Fri, 02 Mar 2007 08:22:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HN7i3-0007QS-G1
	for mip6@ietf.org; Fri, 02 Mar 2007 08:22:07 -0500
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN7i0-0000HK-La
	for mip6@ietf.org; Fri, 02 Mar 2007 08:22:07 -0500
Received: by ug-out-1314.google.com with SMTP id 72so650909ugd
	for <mip6@ietf.org>; Fri, 02 Mar 2007 05:22:04 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=CKN18dxHAVU3yTGFN14fGXjBPdtAKYXXel+q+bGnw+JlYzZyr2eNkC1hdjjRsj0qGyM3Zsjz/caXUq8zVM94K0shUQdu4JBlBu4N7fc+XY2lgqu8wACcEZb8R4gttQufvV/6/aRgLamUYOQ5/qDrvk/4rEIcFXtUP0MIu8adLc4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=l3xUsyClv+BZqc4SARU7DH51zaZQf8JFVgaf4hwuR/o17FiFOqMXsbc5J7qSwL/kmnEh14SKrvpl4L7MD0GGaxhEk15TgX01ZiOSJa2mNvj5ELhWfG95hAeKSYzP7GoCtSdkSlAFNyPTgfGxTWgRVECjac/r/KPXRFTbX6ElrlA=
Received: by 10.78.193.5 with SMTP id q5mr269567huf.1172841723712;
	Fri, 02 Mar 2007 05:22:03 -0800 (PST)
Received: by 10.78.106.13 with HTTP; Fri, 2 Mar 2007 05:22:03 -0800 (PST)
Message-ID: <729b68be0703020522v7a144601yece681c5ad2c7728@mail.gmail.com>
Date: Fri, 2 Mar 2007 14:22:03 +0100
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt
In-Reply-To: <339965.20152.qm@web60318.mail.yahoo.com>
MIME-Version: 1.0
References: <339965.20152.qm@web60318.mail.yahoo.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: mip6@ietf.org, Francis Dupont <Francis.Dupont@fdupont.fr>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1781029884=="
Errors-To: mip6-bounces@ietf.org

--===============1781029884==
Content-Type: multipart/alternative; 
	boundary="----=_Part_24832_11134765.1172841723427"

------=_Part_24832_11134765.1172841723427
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Behcet,

2007/3/1, Behcet Sarikaya <behcetsarikaya@yahoo.com>:
>
> Hi Francis,
>
> Maybe it is too late to have any technical comments on this draft
> However, can I have the following editorial comments?
>
> In Sec. 7, you said:
> the ingress filtering blocks topologically incorrect Care-of
>       Addresses (because there are source addresses too),
>
> s/there/they?
>

<JMC>
 Yes. Thanks.
<JMC>

In Sec. 4, you said:
> By just setting up an IPsec SA with the CN, the MN is able to send
>    packets directly to the CN, i.e., triangular routing is enabled.
> s/triangular routing/route optimization/?
>


<JMC>
No, the term triangular routing is correct :)
The reason is that _all_ packets the MN sends to the CN are secured with
IPsec. The CN knows so the MN is allowed to use the HoA and so this is not a
reflection attack.
<JMC>

Wait, there is one more:
> In Sec. 9:
> When the Home Address is bound to a public key, for instance when the
>    Home Address is a Cryptographically Generated Addresses [RFC3972],
> s/Addresses/Address/
>

<JMC>
Agree. Thanks.
<JMC>

Best regards.

JMC.

Regards,
>
> --behcet
> ----- Original Message ----
> From: "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
> To: i-d-announce@ietf.org
> Cc: mip6@ietf.org
> Sent: Thursday, March 1, 2007 2:50:03 PM
> Subject: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt
>
> 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-04.txt
>     Pages        : 9
>     Date        : 2007-3-1
>
> 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 Optimization.  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-04.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-ietf-mip6-cn-ipsec-04.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>     mailserv@ietf.org.
> In the body type:
>     "FILE /internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt".
>
> NOTE:    The mail server at ietf.org can return the document in
>     MIME-encoded form by using the "mpack" utility.  To use this
>     feature, insert the command "ENCODING mime" before the "FILE"
>     command.  To decode the response(s), you will need "munpack" or
>     a MIME-compliant mail reader.  Different MIME-compliant mail readers
>     exhibit different behavior, especially when dealing with
>     "multipart" MIME messages (i.e. documents which have been split
>     up into multiple messages), so check your local documentation on
>     how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> _______________________________________________
> 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
>
>

------=_Part_24832_11134765.1172841723427
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Behcet,<br><br><div><span class="gmail_quote">2007/3/1, Behcet Sarikaya &lt;<a href="mailto:behcetsarikaya@yahoo.com">behcetsarikaya@yahoo.com</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">Hi Francis,</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">&nbsp; <br>Maybe it is too late to have any technical comments on this draft <img><br>However, can I have the following editorial comments?</div>

<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">&nbsp;</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">In Sec. 7, you said:</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">the ingress filtering blocks topologically incorrect Care-of<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Addresses (because there are source addresses too), </div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">&nbsp;</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">s/there/they?</div></div></div></blockquote><div><br>&lt;JMC&gt;<br>&nbsp;Yes. Thanks.<br>&lt;JMC&gt;<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">In Sec. 4, you said:</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">By just setting up an IPsec SA with the CN, the MN is able to send<br>&nbsp;&nbsp; packets directly to the CN, i.e., triangular routing is enabled.</div>

<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">s/triangular routing/route optimization/?</div></div></div></blockquote><div><br><br>&lt;JMC&gt;<br>No, the term triangular routing is correct :)
<br>The reason is that _all_ packets the MN sends to the CN are secured with IPsec. The CN knows so the MN is allowed to use the HoA and so this is not a reflection attack.<br>&lt;JMC&gt;<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">Wait, there is one more:</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">In Sec. 9:</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">When the Home Address is bound to a public key, for instance when the<br>&nbsp;&nbsp; Home Address is a Cryptographically Generated Addresses [RFC3972],
<br>s/Addresses/Address/</div></div></div></blockquote><div><br>&lt;JMC&gt;<br>Agree. Thanks.<br>&lt;JMC&gt;<br>&nbsp;<br>Best regards.<br><br>JMC.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">Regards,</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">&nbsp;</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">--behcet</div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;"><div><span class="e" id="q_1110f78033968867_1">----- Original Message ----<br>From: &quot;<a href="mailto:Internet-Drafts@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Internet-Drafts@ietf.org</a>&quot; &lt;<a href="mailto:Internet-Drafts@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Internet-Drafts@ietf.org</a>&gt;<br>To: <a href="mailto:i-d-announce@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
i-d-announce@ietf.org</a><br>Cc: <a href="mailto:mip6@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mip6@ietf.org</a><br>Sent: Thursday, March 1, 2007 2:50:03 PM<br>Subject: [Mip6] I-D ACTION:
draft-ietf-mip6-cn-ipsec-04.txt<br><br>
<div>A New Internet-Draft is available from the on-line Internet-Drafts <br>directories.<br>This draft is a work item of the Mobility for IPv6 Working Group of the IETF.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Using IPsec between Mobile and Correspondent IPv6 Nodes
<br>&nbsp;&nbsp;&nbsp;&nbsp;Author(s)&nbsp;&nbsp;&nbsp;&nbsp;: F. Dupont, J. Combes<br>&nbsp;&nbsp;&nbsp;&nbsp;Filename&nbsp;&nbsp;&nbsp;&nbsp;: draft-ietf-mip6-cn-ipsec-04.txt<br>&nbsp;&nbsp;&nbsp;&nbsp;Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 9<br>&nbsp;&nbsp;&nbsp;&nbsp;Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2007-3-1<br>&nbsp;&nbsp;&nbsp;&nbsp;<br>Mobile IPv6 uses IPsec to protect signaling between the Mobile Node
<br>&nbsp;&nbsp; and the Home Agent.&nbsp;&nbsp;This document defines how IPsec can be used<br>&nbsp;&nbsp; between the Mobile Node and Correspondent Nodes for Home Address<br>&nbsp;&nbsp; Option validation (aka. triangular
 routing) and protection of<br>&nbsp;&nbsp; mobility signaling for Route Optimization.&nbsp;&nbsp;The configuration details<br>&nbsp;&nbsp; for IPsec and IKE are also provided.<br><br>A URL for this Internet-Draft is:<br><a href="http://www.ietf.org/internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.ietf.org/internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt</a><br><br>To remove yourself from the I-D Announcement list, send a message to <br><a href="mailto:i-d-announce-request@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
i-d-announce-request@ietf.org</a> with the word unsubscribe in the body of <br>the message. <br>You can also visit <a href="https://www1.ietf.org/mailman/listinfo/I-D-announce" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://www1.ietf.org/mailman/listinfo/I-D-announce</a> <br>to change your subscription settings.<br><br>Internet-Drafts are also available by anonymous FTP. Login with the <br>username &quot;anonymous&quot; and a password of your e-mail address. After 
<br>logging in, type &quot;cd internet-drafts&quot; and then <br>&quot;get
 draft-ietf-mip6-cn-ipsec-04.txt&quot;.<br><br>A list of Internet-Drafts directories can be found in<br><a href="http://www.ietf.org/shadow.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.ietf.org/shadow.html
</a> <br>or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>Internet-Drafts can also be obtained by e-mail.
<br><br>Send a message to:<br>&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:mailserv@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mailserv@ietf.org</a>.<br>In the body type:<br>&nbsp;&nbsp;&nbsp;&nbsp;&quot;FILE /internet-drafts/draft-
ietf-mip6-cn-ipsec-04.txt&quot;.<br>&nbsp;&nbsp;&nbsp;&nbsp;<br>NOTE:&nbsp;&nbsp;&nbsp;&nbsp;The mail server at <a href="http://ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ietf.org</a> can return the document in<br>&nbsp;&nbsp;&nbsp;&nbsp;MIME-encoded form by using the &quot;mpack&quot; utility.&nbsp;&nbsp;To use this
<br>&nbsp;&nbsp;&nbsp;&nbsp;feature, insert the command &quot;ENCODING mime&quot; before the &quot;FILE&quot;<br>&nbsp;&nbsp;&nbsp;&nbsp;command.&nbsp;&nbsp;To decode the response(s), you will need &quot;munpack&quot; or<br>&nbsp;&nbsp;&nbsp;&nbsp;a MIME-compliant mail reader.&nbsp;&nbsp;Different MIME-compliant mail
 readers<br>&nbsp;&nbsp;&nbsp;&nbsp;exhibit different behavior, especially when dealing with<br>&nbsp;&nbsp;&nbsp;&nbsp;&quot;multipart&quot; MIME messages (i.e. documents which have been split<br>&nbsp;&nbsp;&nbsp;&nbsp;up into multiple messages), so check your local documentation on
<br>&nbsp;&nbsp;&nbsp;&nbsp;how to manipulate these messages.<br><br>Below is the data which will enable a MIME compliant mail reader<br>implementation to automatically retrieve the ASCII version of the<br>Internet-Draft.</div></span></div>
<div>_______________________________________________<br>Mip6 mailing list<br><a href="mailto:Mip6@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Mip6@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/mip6" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://www1.ietf.org/mailman/listinfo/mip6</a></div></div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;"><br></div></div></div><br>_______________________________________________<br>Mip6 mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Mip6@ietf.org">
Mip6@ietf.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www1.ietf.org/mailman/listinfo/mip6" target="_blank">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br></blockquote></div><br>

------=_Part_24832_11134765.1172841723427--


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

--===============1781029884==--




From mip6-bounces@ietf.org Fri Mar 02 11:00:02 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNA9Z-0008Sd-Ml; Fri, 02 Mar 2007 10:58:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNA9A-0006aK-4f
	for mip6@ietf.org; Fri, 02 Mar 2007 10:58:16 -0500
Received: from web60317.mail.yahoo.com ([209.73.178.125])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HNA57-0008G3-JE
	for mip6@ietf.org; Fri, 02 Mar 2007 10:54:08 -0500
Received: (qmail 16922 invoked by uid 60001); 2 Mar 2007 15:54:05 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=Q0L+gRcP8bVylsXAG8wPgfAuZBye9jIcKzxw0IWOFwYy0Zon1irZCyDRgGWDAAS2WVF+qys9mkwJquYDixjAHbxDutJxFea2XE4w506tbuWmbXh+oHu97DBtHc7AyYBrpvKEou0v2stA2O8WpIsodtKDMN7FimeuD7g51uCMNF0=;
X-YMail-OSG: FZ1zg9wVM1nNW3mOxhjua8Zn.zPs7aL3zR0niyZBU3NH3ughJE_Lz4v0uPUWKtrv.6UAjKjbm3_l4djw3AcxIRJNDqfaw42yc796A5UDVI_QL3EwVQrwYZJAq892S9PYLMqfYwGn8U4AssvRtFGXo8mKOng-
Received: from [206.16.17.212] by web60317.mail.yahoo.com via HTTP;
	Fri, 02 Mar 2007 07:54:05 PST
X-Mailer: YahooMailRC/468 YahooMailWebService/0.6.132.8
Date: Fri, 2 Mar 2007 07:54:05 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
MIME-Version: 1.0
Message-ID: <187690.4335.qm@web60317.mail.yahoo.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 36fb765c89ed47dab364ab702a78e8fd
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="===============0787944656=="
Errors-To: mip6-bounces@ietf.org

--===============0787944656==
Content-Type: multipart/alternative; boundary="0-708688189-1172850845=:4335"

--0-708688189-1172850845=:4335
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

OK, it seems you're right but then I would suggest changing the sentence a =
bit to clarify:=0Athe MN is able to send=0A   packets directly to the CN, i=
.e., triangular routing is enabled=0Ato =0Athe MN is able to send=0A   pack=
ets to the CN via the home network, i.e., triangular routing is enabled=0Ab=
ecause directly to the CN implies route optimized delivery, IMO.=0A=0ARegar=
ds,=0A=0A--behcet=0A=0A----- Original Message ----=0AFrom: Jean-Michel Comb=
es <jeanmichel.combes@gmail.com>=0ATo: Behcet Sarikaya <sarikaya@ieee.org>=
=0ACc: mip6@ietf.org; Francis Dupont <Francis.Dupont@fdupont.fr>=0ASent: Fr=
iday, March 2, 2007 7:22:03 AM=0ASubject: Re: [Mip6] I-D ACTION:draft-ietf-=
mip6-cn-ipsec-04.txt=0A=0AHi Behcet,=0A=0A=0A2007/3/1, Behcet Sarikaya <beh=
cetsarikaya@yahoo.com>:=0AHi Francis,=0A  =0AMaybe it is too late to have a=
ny technical comments on this draft =0AHowever, can I have the following ed=
itorial comments?=0A =0AIn Sec. 7, you said:=0Athe ingress filtering blocks=
 topologically incorrect Care-of=0A      Addresses (because there are sourc=
e addresses too), =0A =0As/there/they?=0A=0A<JMC>=0A Yes. Thanks.=0A<JMC>=
=0A=0A=0A=0AIn Sec. 4, you said:=0ABy just setting up an IPsec SA with the =
CN, the MN is able to send=0A   packets directly to the CN, i.e., triangula=
r routing is enabled.=0As/triangular routing/route optimization/?=0A=0A=0A<=
JMC>=0ANo, the term triangular routing is correct :) =0AThe reason is that =
_all_ packets the MN sends to the CN are secured with IPsec. The CN knows s=
o the MN is allowed to use the HoA and so this is not a reflection attack.=
=0A<JMC>=0A=0A=0A=0AWait, there is one more:=0AIn Sec. 9:=0AWhen the Home A=
ddress is bound to a public key, for instance when the=0A   Home Address is=
 a Cryptographically Generated Addresses [RFC3972], =0As/Addresses/Address/=
=0A=0A<JMC>=0AAgree. Thanks.=0A<JMC>=0A =0ABest regards.=0A=0AJMC.=0A=0A=0A=
=0ARegards,=0A =0A--behcet=0A----- Original Message ----=0AFrom: " Internet=
-Drafts@ietf.org" <Internet-Drafts@ietf.org>=0ATo: i-d-announce@ietf.org=0A=
Cc: mip6@ietf.org=0ASent: Thursday, March 1, 2007 2:50:03 PM=0ASubject: [Mi=
p6] I-D ACTION: draft-ietf-mip6-cn-ipsec-04.txt=0A=0A=0AA New Internet-Draf=
t is available from the on-line Internet-Drafts =0Adirectories.=0AThis draf=
t is a work item of the Mobility for IPv6 Working Group of the IETF.=0A=0A =
   Title        : Using IPsec between Mobile and Correspondent IPv6 Nodes =
=0A    Author(s)    : F. Dupont, J. Combes=0A    Filename    : draft-ietf-m=
ip6-cn-ipsec-04.txt=0A    Pages        : 9=0A    Date        : 2007-3-1=0A =
   =0AMobile IPv6 uses IPsec to protect signaling between the Mobile Node =
=0A   and the Home Agent.  This document defines how IPsec can be used=0A  =
 between the Mobile Node and Correspondent Nodes for Home Address=0A   Opti=
on validation (aka. triangular routing) and protection of=0A   mobility sig=
naling for Route Optimization.  The configuration details=0A   for IPsec an=
d IKE are also provided.=0A=0AA URL for this Internet-Draft is:=0Ahttp://ww=
w.ietf.org/internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt=0A=0ATo remove y=
ourself from the I-D Announcement list, send a message to =0Ai-d-announce-r=
equest@ietf.org with the word unsubscribe in the body of =0Athe message. =
=0AYou can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce =
=0Ato change your subscription settings.=0A=0AInternet-Drafts are also avai=
lable by anonymous FTP. Login with the =0Ausername "anonymous" and a passwo=
rd of your e-mail address. After =0Alogging in, type "cd internet-drafts" a=
nd then =0A"get draft-ietf-mip6-cn-ipsec-04.txt".=0A=0AA list of Internet-D=
rafts directories can be found in=0Ahttp://www.ietf.org/shadow.html =0Aor f=
tp://ftp.ietf.org/ietf/1shadow-sites.txt=0A=0AInternet-Drafts can also be o=
btained by e-mail. =0A=0ASend a message to:=0A    mailserv@ietf.org.=0AIn t=
he body type:=0A    "FILE /internet-drafts/draft- ietf-mip6-cn-ipsec-04.txt=
".=0A    =0ANOTE:    The mail server at ietf.org can return the document in=
=0A    MIME-encoded form by using the "mpack" utility.  To use this =0A    =
feature, insert the command "ENCODING mime" before the "FILE"=0A    command=
.  To decode the response(s), you will need "munpack" or=0A    a MIME-compl=
iant mail reader.  Different MIME-compliant mail readers=0A    exhibit diff=
erent behavior, especially when dealing with=0A    "multipart" MIME message=
s (i.e. documents which have been split=0A    up into multiple messages), s=
o check your local documentation on =0A    how to manipulate these messages=
.=0A=0ABelow is the data which will enable a MIME compliant mail reader=0Ai=
mplementation to automatically retrieve the ASCII version of the=0AInternet=
-Draft.=0A_______________________________________________=0AMip6 mailing li=
st=0AMip6@ietf.org=0Ahttps://www1.ietf.org/mailman/listinfo/mip6=0A=0A=0A=
=0A_______________________________________________=0AMip6 mailing list=0AMi=
p6@ietf.org=0Ahttps://www1.ietf.org/mailman/listinfo/mip6=0A=0A=0A=0A=0A___=
____________________________________________=0AMip6 mailing list=0AMip6@iet=
f.org=0Ahttps://www1.ietf.org/mailman/listinfo/mip6
--0-708688189-1172850845=:4335
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman=
, new york, times, serif">OK, it seems you're right but then I would sugges=
t changing the sentence a bit to clarify:</DIV>=0A<DIV style=3D"FONT-SIZE: =
12pt; FONT-FAMILY: times new roman, new york, times, serif"><FONT color=3D#=
0060bf>the MN is able to send<BR>&nbsp;&nbsp; packets directly to the CN, i=
.e., triangular routing is enabled</FONT><BR>to <BR><FONT color=3D#bf005f>t=
he MN is able to send<BR>&nbsp;&nbsp; packets to the CN via the home networ=
k, i.e., triangular routing is enabled</FONT></DIV>=0A<DIV style=3D"FONT-SI=
ZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">because dir=
ectly to the CN implies route optimized delivery, IMO.</DIV>=0A<DIV style=
=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">=
&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,=
 new york, times, serif">Regards,</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FO=
NT-FAMILY: times new roman, new york, times, serif">&nbsp;</DIV>=0A<DIV sty=
le=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif=
">--behcet</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new ro=
man, new york, times, serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; =
FONT-FAMILY: times new roman, new york, times, serif">----- Original Messag=
e ----<BR>From: Jean-Michel Combes &lt;jeanmichel.combes@gmail.com&gt;<BR>T=
o: Behcet Sarikaya &lt;sarikaya@ieee.org&gt;<BR>Cc: mip6@ietf.org; Francis =
Dupont &lt;Francis.Dupont@fdupont.fr&gt;<BR>Sent: Friday, March 2, 2007 7:2=
2:03 AM<BR>Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt<B=
R><BR>Hi Behcet,<BR><BR>=0A<DIV><SPAN class=3Dgmail_quote>2007/3/1, Behcet =
Sarikaya &lt;<A href=3D"mailto:behcetsarikaya@yahoo.com" target=3D_blank re=
l=3Dnofollow>behcetsarikaya@yahoo.com</A>&gt;:</SPAN>=0A<BLOCKQUOTE class=
=3Dgmail_quote style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDE=
R-LEFT: rgb(204,204,204) 1px solid">=0A<DIV>=0A<DIV style=3D"FONT-SIZE: 12p=
t; FONT-FAMILY: times new roman,new york,times,serif">=0A<DIV style=3D"FONT=
-SIZE: 12pt; FONT-FAMILY: times new roman,new york,times,serif">Hi Francis,=
</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new yo=
rk,times,serif">&nbsp; <BR>Maybe it is too late to have any technical comme=
nts on this draft <IMG><BR>However, can I have the following editorial comm=
ents?</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,n=
ew york,times,serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAM=
ILY: times new roman,new york,times,serif">In Sec. 7, you said:</DIV>=0A<DI=
V style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new york,times,ser=
if">the ingress filtering blocks topologically incorrect Care-of<BR>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; Addresses (because there are source addresses too),=
 </DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new y=
ork,times,serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY:=
 times new roman,new york,times,serif">s/there/they?</DIV></DIV></DIV></BLO=
CKQUOTE>=0A<DIV><BR>&lt;JMC&gt;<BR>&nbsp;Yes. Thanks.<BR>&lt;JMC&gt;<BR></D=
IV><BR>=0A<BLOCKQUOTE class=3Dgmail_quote style=3D"PADDING-LEFT: 1ex; MARGI=
N: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">=0A<DIV>=0A<=
DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new york,times,s=
erif">=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new yo=
rk,times,serif">In Sec. 4, you said:</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt;=
 FONT-FAMILY: times new roman,new york,times,serif">By just setting up an I=
Psec SA with the CN, the MN is able to send<BR>&nbsp;&nbsp; packets directl=
y to the CN, i.e., triangular routing is enabled.</DIV>=0A<DIV style=3D"FON=
T-SIZE: 12pt; FONT-FAMILY: times new roman,new york,times,serif">s/triangul=
ar routing/route optimization/?</DIV></DIV></DIV></BLOCKQUOTE>=0A<DIV><BR><=
BR>&lt;JMC&gt;<BR>No, the term triangular routing is correct :) <BR>The rea=
son is that _all_ packets the MN sends to the CN are secured with IPsec. Th=
e CN knows so the MN is allowed to use the HoA and so this is not a reflect=
ion attack.<BR>&lt;JMC&gt;<BR></DIV><BR>=0A<BLOCKQUOTE class=3Dgmail_quote =
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204=
,204,204) 1px solid">=0A<DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY:=
 times new roman,new york,times,serif">=0A<DIV style=3D"FONT-SIZE: 12pt; FO=
NT-FAMILY: times new roman,new york,times,serif">Wait, there is one more:</=
DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new york=
,times,serif">In Sec. 9:</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY=
: times new roman,new york,times,serif">When the Home Address is bound to a=
 public key, for instance when the<BR>&nbsp;&nbsp; Home Address is a Crypto=
graphically Generated Addresses [RFC3972], <BR>s/Addresses/Address/</DIV></=
DIV></DIV></BLOCKQUOTE>=0A<DIV><BR>&lt;JMC&gt;<BR>Agree. Thanks.<BR>&lt;JMC=
&gt;<BR>&nbsp;<BR>Best regards.<BR><BR>JMC.<BR></DIV><BR>=0A<BLOCKQUOTE cla=
ss=3Dgmail_quote style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BOR=
DER-LEFT: rgb(204,204,204) 1px solid">=0A<DIV>=0A<DIV style=3D"FONT-SIZE: 1=
2pt; FONT-FAMILY: times new roman,new york,times,serif">=0A<DIV style=3D"FO=
NT-SIZE: 12pt; FONT-FAMILY: times new roman,new york,times,serif">Regards,<=
/DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new yor=
k,times,serif">&nbsp;</DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: t=
imes new roman,new york,times,serif">--behcet</DIV>=0A<DIV style=3D"FONT-SI=
ZE: 12pt; FONT-FAMILY: times new roman,new york,times,serif">=0A<DIV><SPAN =
class=3De id=3Dq_1110f78033968867_1>----- Original Message ----<BR>From: "<=
A href=3D"mailto:Internet-Drafts@ietf.org" target=3D_blank rel=3Dnofollow> =
Internet-Drafts@ietf.org</A>" &lt;<A href=3D"mailto:Internet-Drafts@ietf.or=
g" target=3D_blank rel=3Dnofollow>Internet-Drafts@ietf.org</A>&gt;<BR>To: <=
A href=3D"mailto:i-d-announce@ietf.org" target=3D_blank rel=3Dnofollow>i-d-=
announce@ietf.org</A><BR>Cc: <A href=3D"mailto:mip6@ietf.org" target=3D_bla=
nk rel=3Dnofollow>mip6@ietf.org</A><BR>Sent: Thursday, March 1, 2007 2:50:0=
3 PM<BR>Subject: [Mip6] I-D ACTION: draft-ietf-mip6-cn-ipsec-04.txt<BR><BR>=
=0A<DIV>A New Internet-Draft is available from the on-line Internet-Drafts =
<BR>directories.<BR>This draft is a work item of the Mobility for IPv6 Work=
ing Group of the IETF.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;Title&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Using IPsec between Mobile and Correspond=
ent IPv6 Nodes <BR>&nbsp;&nbsp;&nbsp;&nbsp;Author(s)&nbsp;&nbsp;&nbsp;&nbsp=
;: F. Dupont, J. Combes<BR>&nbsp;&nbsp;&nbsp;&nbsp;Filename&nbsp;&nbsp;&nbs=
p;&nbsp;: draft-ietf-mip6-cn-ipsec-04.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;Pages&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 9<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2007-3-1<BR>&nbsp;=
&nbsp;&nbsp;&nbsp;<BR>Mobile IPv6 uses IPsec to protect signaling between t=
he Mobile Node <BR>&nbsp;&nbsp; and the Home Agent.&nbsp;&nbsp;This documen=
t defines how IPsec can be used<BR>&nbsp;&nbsp; between the Mobile Node and=
 Correspondent Nodes for Home Address<BR>&nbsp;&nbsp; Option validation (ak=
a. triangular
 routing) and protection of<BR>&nbsp;&nbsp; mobility signaling for Route Op=
timization.&nbsp;&nbsp;The configuration details<BR>&nbsp;&nbsp; for IPsec =
and IKE are also provided.<BR><BR>A URL for this Internet-Draft is:<BR><A h=
ref=3D"http://www.ietf.org/internet-drafts/draft-ietf-mip6-cn-ipsec-04.txt"=
 target=3D_blank rel=3Dnofollow>http://www.ietf.org/internet-drafts/draft-i=
etf-mip6-cn-ipsec-04.txt</A><BR><BR>To remove yourself from the I-D Announc=
ement list, send a message to <BR><A href=3D"mailto:i-d-announce-request@ie=
tf.org" target=3D_blank rel=3Dnofollow>i-d-announce-request@ietf.org</A> wi=
th the word unsubscribe in the body of <BR>the message. <BR>You can also vi=
sit <A href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce" target=
=3D_blank rel=3Dnofollow>https://www1.ietf.org/mailman/listinfo/I-D-announc=
e</A> <BR>to change your subscription settings.<BR><BR>Internet-Drafts are =
also available by anonymous FTP. Login with the <BR>username "anonymous" an=
d a password of your e-mail
 address. After <BR>logging in, type "cd internet-drafts" and then <BR>"get=
 draft-ietf-mip6-cn-ipsec-04.txt".<BR><BR>A list of Internet-Drafts directo=
ries can be found in<BR><A href=3D"http://www.ietf.org/shadow.html" target=
=3D_blank rel=3Dnofollow>http://www.ietf.org/shadow.html </A><BR>or <A href=
=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D_blank rel=3Dnofoll=
ow>ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A><BR><BR>Internet-Drafts can=
 also be obtained by e-mail. <BR><BR>Send a message to:<BR>&nbsp;&nbsp;&nbs=
p;&nbsp;<A href=3D"mailto:mailserv@ietf.org" target=3D_blank rel=3Dnofollow=
>mailserv@ietf.org</A>.<BR>In the body type:<BR>&nbsp;&nbsp;&nbsp;&nbsp;"FI=
LE /internet-drafts/draft- ietf-mip6-cn-ipsec-04.txt".<BR>&nbsp;&nbsp;&nbsp=
;&nbsp;<BR>NOTE:&nbsp;&nbsp;&nbsp;&nbsp;The mail server at <A href=3D"http:=
//ietf.org/" target=3D_blank rel=3Dnofollow>ietf.org</A> can return the doc=
ument in<BR>&nbsp;&nbsp;&nbsp;&nbsp;MIME-encoded form by using the "mpack" =
utility.&nbsp;&nbsp;To use this
 <BR>&nbsp;&nbsp;&nbsp;&nbsp;feature, insert the command "ENCODING mime" be=
fore the "FILE"<BR>&nbsp;&nbsp;&nbsp;&nbsp;command.&nbsp;&nbsp;To decode th=
e response(s), you will need "munpack" or<BR>&nbsp;&nbsp;&nbsp;&nbsp;a MIME=
-compliant mail reader.&nbsp;&nbsp;Different MIME-compliant mail readers<BR=
>&nbsp;&nbsp;&nbsp;&nbsp;exhibit different behavior, especially when dealin=
g with<BR>&nbsp;&nbsp;&nbsp;&nbsp;"multipart" MIME messages (i.e. documents=
 which have been split<BR>&nbsp;&nbsp;&nbsp;&nbsp;up into multiple messages=
), so check your local documentation on <BR>&nbsp;&nbsp;&nbsp;&nbsp;how to =
manipulate these messages.<BR><BR>Below is the data which will enable a MIM=
E compliant mail reader<BR>implementation to automatically retrieve the ASC=
II version of the<BR>Internet-Draft.</DIV></SPAN></DIV>=0A<DIV>____________=
___________________________________<BR>Mip6 mailing list<BR><A href=3D"mail=
to:Mip6@ietf.org" target=3D_blank rel=3Dnofollow>Mip6@ietf.org</A><BR><A hr=
ef=3D"https://www1.ietf.org/mailman/listinfo/mip6" target=3D_blank rel=3Dno=
follow>https://www1.ietf.org/mailman/listinfo/mip6</A></DIV></DIV>=0A<DIV s=
tyle=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new york,times,serif"=
><BR></DIV></DIV></DIV><BR>_______________________________________________<=
BR>Mip6 mailing list<BR><A href=3D"mailto:Mip6@ietf.org" target=3D_blank re=
l=3Dnofollow>Mip6@ietf.org</A><BR><A href=3D"https://www1.ietf.org/mailman/=
listinfo/mip6" target=3D_blank rel=3Dnofollow>https://www1.ietf.org/mailman=
/listinfo/mip6</A><BR><BR></BLOCKQUOTE></DIV><BR>=0A<DIV>__________________=
_____________________________<BR>Mip6 mailing list<BR>Mip6@ietf.org<BR><A h=
ref=3D"https://www1.ietf.org/mailman/listinfo/mip6" target=3D_blank>https:/=
/www1.ietf.org/mailman/listinfo/mip6</A></DIV></DIV>=0A<DIV style=3D"FONT-S=
IZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR></DIV>=
</div></body></html>
--0-708688189-1172850845=:4335--


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

--===============0787944656==--




From mip6-bounces@ietf.org Fri Mar 02 11:28:06 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNAbY-0007TG-5C; Fri, 02 Mar 2007 11:27:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNAbW-0007I4-KJ
	for mip6@ietf.org; Fri, 02 Mar 2007 11:27:34 -0500
Received: from tao.fdupont.fr ([82.236.136.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNAbT-0006Mh-L0
	for mip6@ietf.org; Fri, 02 Mar 2007 11:27:34 -0500
Received: from tao.fdupont.fr (localhost [127.0.0.1])
	by tao.fdupont.fr (8.13.5/8.13.5) with ESMTP id l22GQTRU000704;
	Fri, 2 Mar 2007 17:26:30 +0100 (CET)
Received: from tao.fdupont.fr (dupont@localhost)
	by tao.fdupont.fr (8.13.5/8.13.5/Submit) with ESMTP id l22GQTlU000699; 
	Fri, 2 Mar 2007 17:26:29 +0100 (CET)
Message-Id: <200703021626.l22GQTlU000699@tao.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt 
In-reply-to: Your message of Thu, 01 Mar 2007 13:38:33 PST.
	<339965.20152.qm@web60318.mail.yahoo.com> 
Date: Fri, 02 Mar 2007 17:26:29 +0100
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Maybe it is too late to have any technical comments on this draft 

=> it is never too late for improvements...

   However, can I have the following editorial comments?

=> caught.

   In Sec. 4, you said:
   By just setting up an IPsec SA with the CN, the MN is able to send
   packets directly to the CN, i.e., triangular routing is enabled.
   s/triangular routing/route optimization/?

=> no, it is only the MN->CN way so it is only triangular routing...

Thanks

Francis.Dupont@fdupont.fr

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



From mip6-bounces@ietf.org Fri Mar 02 11:46:53 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNAtk-0001Jf-GM; Fri, 02 Mar 2007 11:46:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNAtj-0001JX-3O
	for mip6@ietf.org; Fri, 02 Mar 2007 11:46:23 -0500
Received: from tao.fdupont.fr ([82.236.136.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNAtg-0000OY-Di
	for mip6@ietf.org; Fri, 02 Mar 2007 11:46:23 -0500
Received: from tao.fdupont.fr (localhost [127.0.0.1])
	by tao.fdupont.fr (8.13.5/8.13.5) with ESMTP id l22Gjdpn000850;
	Fri, 2 Mar 2007 17:45:39 +0100 (CET)
Received: from tao.fdupont.fr (dupont@localhost)
	by tao.fdupont.fr (8.13.5/8.13.5/Submit) with ESMTP id l22GjcrP000847; 
	Fri, 2 Mar 2007 17:45:38 +0100 (CET)
Message-Id: <200703021645.l22GjcrP000847@tao.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt 
In-reply-to: Your message of Fri, 02 Mar 2007 07:54:05 PST.
	<187690.4335.qm@web60317.mail.yahoo.com> 
Date: Fri, 02 Mar 2007 17:45:38 +0100
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   OK, it seems you're right but then I would suggest changing the sentence a
   bit to clarify:

=> I agree about a clarification but not this clarification.

   the MN is able to send packets directly to the CN, i.e., triangular
   routing is enabled
to 

   the MN is able to send packets to the CN via the home network, i.e.,
   triangular routing is enabled because directly to the CN implies
   route optimized delivery, IMO.

=> I understand the opposite of the triangular routing...

Thanks

Francis.Dupont@fdupont.fr

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



From mip6-bounces@ietf.org Fri Mar 02 16:48:40 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNFKF-00007d-0x; Fri, 02 Mar 2007 16:30:03 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNEiW-0001yk-Q4; Fri, 02 Mar 2007 15:51:04 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HNEiV-0003Ro-P2; Fri, 02 Mar 2007 15:51:04 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 569F6176CD;
	Fri,  2 Mar 2007 20:50:04 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HNEhY-0002ZJ-1T; Fri, 02 Mar 2007 15:50:04 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HNEhY-0002ZJ-1T@stiedprstage1.ietf.org>
Date: Fri, 02 Mar 2007 15:50:04 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-ha-switch-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		: Mobility Header Home Agent Switch Message
	Author(s)	: B. Haley, et al.
	Filename	: draft-ietf-mip6-ha-switch-03.txt
	Pages		: 12
	Date		: 2007-3-2
	
This document specifies a new Mobility Header message type that can
   be used between a home agent and mobile node to signal a mobile node
   that it should acquire a new home agent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-ha-switch-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-ha-switch-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-ha-switch-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: <2007-3-2142408.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-ha-switch-03.txt

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

Content-Type: text/plain
Content-ID: <2007-3-2142408.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 Fri Mar 02 17:10:15 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNFwz-0005uz-4z; Fri, 02 Mar 2007 17:10:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNFwx-0005uV-Ma
	for mip6@ietf.org; Fri, 02 Mar 2007 17:10:03 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNFwv-0000SS-QW
	for mip6@ietf.org; Fri, 02 Mar 2007 17:10:03 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Mar 2007 14:10:00 -0800
Message-ID: <45E8A0B8.40200@azairenet.com>
Date: Fri, 02 Mar 2007 14:10:00 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
References: <459A5A6C.5070602@piuha.net>	
	<eaa74a7e0702230640g722a28fcyc89360e69337c768@mail.gmail.com>	
	<45E00DD3.1010701@piuha.net> <45E32B26.7050702@azairenet.com>	
	<eaa74a7e0702270515v20f5be3ar91f97555539aa1b3@mail.gmail.com>	
	<45E4D408.8050709@azairenet.com>	
	<eaa74a7e0702280118g5881ffdy8684e84f63880dcb@mail.gmail.com>	
	<45E63AE1.4090708@azairenet.com>	
	<eaa74a7e0703010627k2c64e311n7e7e1fd148489412@mail.gmail.com>	
	<45E73675.6080300@azairenet.com>
	<eaa74a7e0703020135j6464fd71oe357caee0ffd36af@mail.gmail.com>
In-Reply-To: <eaa74a7e0703020135j6464fd71oe357caee0ffd36af@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2007 22:10:00.0959 (UTC)
	FILETIME=[858D00F0:01C75D17]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> Nothing. The main reason for authentication and authorization split
> discussed in DIME was not related to this issue (but to the EAP
> application support). This was a side issue.
> 
> Anyway if the group is fine to not consider this issue, that is fine
> with me too.
> 
> Going back to the original discussion: how can the AAA server provide
> the right identity of the MN for DNS update to the HA?

How about in the Diameter EAP Response message or the
AA Answer message depending on whether authentication
and authorization are done together or separately?

Vijay

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



From mip6-bounces@ietf.org Fri Mar 02 17:17:23 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNG3s-0000Ni-Pm; Fri, 02 Mar 2007 17:17:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNG3r-0000Mx-SK
	for mip6@ietf.org; Fri, 02 Mar 2007 17:17:11 -0500
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNG3q-0001jH-DF
	for mip6@ietf.org; Fri, 02 Mar 2007 17:17:11 -0500
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Mar 2007 14:17:09 -0800
Message-ID: <45E8A264.1070705@azairenet.com>
Date: Fri, 02 Mar 2007 14:17:08 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
References: <4D2F935F08D41A4C8866693F4F0D7C4F01278236@lan-ex-01.panasonic.de>
	<45E760C3.5050103@azairenet.com>
	<4D2F935F08D41A4C8866693F4F0D7C4F01278515@lan-ex-01.panasonic.de>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4F01278515@lan-ex-01.panasonic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2007 22:17:09.0584 (UTC)
	FILETIME=[8507FD00:01C75D18]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kilian Weniger wrote:


>>> There were two reasons for mandating the cookie exchange:
>>> 1. anycast HA address is typically a single well-known and public
>>> address, which makes it a possible target of DoS attacks. 
>>> 2. less impact on IKEv2 exchange, since the complete IKEv2 
>> exchange is
>>> done with unicast address.
>> In my mind, the second one was the main reason.
>>
>>> If nobody sees a big issue with an anycasted IKE_SA_INIT 
>> followed by a
>>> unicast IKE_SA_INIT response without cookie, I'm fine with "SHOULD"
>>> instead of "MUST" for the cookie (Vijay, from your reply it 
>> seems you
>>> have concerns?). Using the cookie due to reason 1 can be left to
>>> operator's decision IMHO.
>> Lets get the mechanism right. I prefer not to add yet
>> another optional mechanism. If its not needed we should
>> remove it.
>>
>> The way I see it the cookie is used by the responder (the
>> HA that sent the cookie) to tie the first IKE_SA_INIT
>> exchange with the second one. The cookie is also used by
>> the initiator (the mobile node) to figure out why its
>> first IKE_SA_INIT exchange did not succeed and why it
>> needs to do a second IKE_SA_INIT exchange.
> 
> Those are reasons for having a cookie when two IKE_SA_INIT exchanges are done. I assume that we only have one IKE_SA_INIT exchange if we don't use the cookie. Then the question is whether there is a problem, when an IKE_SA_INIT *anycast* request is followed by an IKE_SA_INIT unicast response *without cookie*, followed by the usual IKE_SA_AUTH exchange etc, i.e., is there a problem with the following exchanges:
> 
>         Initiator                         Responder ("best" HA) 
>        -----------                        --------------------- 
>     
>        (IP_I:500 -> ANYCAST:500) 
>        HDR(A,0), SAi1, KEi, Ni   --> 
>     
>                                  (IP_R:500 -> IP_I:500) 
>                              <-- HDR(A,B), SAr1, KEr, Nr,[CERTREQ] 
> 
>        
> 
>        (IP_I:500 -> IP_R:500) 
>        HDR(A,B), SK {IDi, [CERT,] [CERTREQ,]  
>        [IDr,]AUTH, SAi2, TSi, TSr} --> 
>     
>                                  (IP_R:500 -> IP_I:500) 
>                              <-- HDR(A,B), SK {IDr, [CERT,] AUTH, 
>                                                  SAr2, TSi, TSr} 
> 	...

I understood what you were saying in the earlier mail
itself. I think the cookie is necessary since it ties
the two IKE_SA_INIT exchanges together.

>>     Note that this procedure requires the implementation of anycast
>>     forwarding in such a way that the Home Agent can distinguish
>>     between an IKE_SA_INIT forwarded through an anycast address and
>>     one sent directly from the Mobile Node.
> 
> Right. But the current text doesn't say how the IKE_SA_INIT can be forwarded and how the HA can distinguish between forwarded packets and packets coming from the MN. Since this is required for interoperability, don't we need to specify this?

We currently have this out of scope. Do we have consensus
on one solution?

>>>> Four: What happens when the IKE SA dies or is
>>>> deleted, but a binding for the mobile node remains
>>>> in the selected home agent? Will the mobile node
>>>> re-establish the IKE SA using the anycast address,
>>>> or the address of the selected home agent?
>>> Yes, some text should be added about that. The MN could first try to
>>> re-establish the SA with the current HA's unicast address, as Vijay
>>> said. But if this fails, the MN should try to find a new 
>> HA, e.g., by
>>> using the anycast HA assignment. 
>> How about the following text?
>>
>>    A mobile node's security associations with its home agent may
>>    expire while it still has a valid binding cache entry at the
>>    the home agent.  In this case, the mobile node MUST NOT use an
>>    anycast address as the destination address in the IKE_SA_INIT
>>    exchange to setup new security associations.  It MUST try to
>>    setup security associations with its existing home agent.
> 
> Sounds good to me. We could additionally specify the behaviour for the case that the IKE SA dies before the lifetime expires. In this case the mobile node should try to find a new home agent IMHO:
> 
>      If the security associations with the home agent die before 
>      they expire, e.g., because the mobile node detects that the 
>      peer is dead or because the peer deleted the security  
>      associations), the mobile node should try to bootstrap with a 
>      new home agent using one of the mechanisms specified in this 
>      document.

I am not so sure about the second paragraph. Unless you
know why the HA deleted the security associations, it is
hard to recommend a particular behavior. What if the HA
deleted the security associations but not the binding
cache entry? :)

Vijay

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



From mip6-bounces@ietf.org Fri Mar 02 17:24:59 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNEo8-0001MP-Cr; Fri, 02 Mar 2007 15:56:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNEi1-0001Ge-Dt; Fri, 02 Mar 2007 15:50:33 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HNEi0-0003OZ-Qq; Fri, 02 Mar 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id BA242176B8;
	Fri,  2 Mar 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HNEhW-0002W4-Fo; Fri, 02 Mar 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HNEhW-0002W4-Fo@stiedprstage1.ietf.org>
Date: Fri, 02 Mar 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-rfc4285bis-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		: Authentication Protocol for Mobile IPv6
	Author(s)	: A. Patel, et al.
	Filename	: draft-ietf-mip6-rfc4285bis-00.txt
	Pages		: 23
	Date		: 2007-3-2
	
   IPsec is specified as the means of securing signaling messages
   between the Mobile Node and Home agent for Mobile IPv6 (MIPv6).
   MIPv6 signalling messages that are secured include the Binding
   Updates and Acknowledgement messages used for managing the bindings
   between a Mobile Node and its Home Agent.  This document proposes an
   alternate method for securing MIPv6 signaling messages between a
   Mobile Nodes and Home Agents.  The alternate method defined here
   conists of a MIPv6-specific authentication option that can be added
   to MIPv6 signalling messages.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-rfc4285bis-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-rfc4285bis-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-rfc4285bis-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: <2007-3-2110935.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-rfc4285bis-00.txt

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

Content-Type: text/plain
Content-ID: <2007-3-2110935.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 Fri Mar 02 23:15:13 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNLdT-0002bA-GC; Fri, 02 Mar 2007 23:14:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNLdR-0002b0-Oe
	for mip6@ietf.org; Fri, 02 Mar 2007 23:14:17 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNLdQ-00027d-9Y
	for mip6@ietf.org; Fri, 02 Mar 2007 23:14:17 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id A5A9F90011
	for <mip6@ietf.org>; Fri,  2 Mar 2007 23:14:10 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 18039-10 for <mip6@ietf.org>;
	Fri, 2 Mar 2007 23:14:06 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Fri,  2 Mar 2007 23:14:06 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 23:14:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
Date: Fri, 2 Mar 2007 23:14:03 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA2D@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
Thread-Index: AcdcbT4Li8AnGHEhQs+v//ghFugAWQA28GLg
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 03 Mar 2007 04:14:03.0598 (UTC)
	FILETIME=[60C736E0:01C75D4A]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
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



> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Thursday, March 01, 2007 7:51 PM
> To: Chowdhury, Kuntal
> Cc: Jari Arkko; Mobile IPv6 Mailing List
> Subject: Re: Local HA assignment using DNS (was Re: [Mip6] AD review
> ofdraft-ietf-mip6-bootstrapping-split)
>=20
> Chowdhury, Kuntal wrote:
> >> One mechanism
> >>     is to provision the mobile node with an FQDN for a local home
> > agent
> >>     when it attaches to the local link through an access link
specific
> >>     mechanism.  For example the FQDN of the local home agent can be
> > sent
> >>     to the mobile node using DHCP.
> >
> > Why only FQDN? The local HA address can be sent directly to the MN.
Why
> > asking the MN to do one more roundtrip with DNS? Just use the DHCP
> > options in HIOPT. If DHCP is used by the MN, and if the DHCP server
has
> > local HA address info, it should be able to give it out to the MN.
>=20
> Kuntal, I know you are very passionate about DHCP. :)
> But here we are talking about using DNS to bootstrap
> a home agent. The assumption is that support for
> draft-ietf-mip6-hiopt-02.txt is not available on the
> local network.
>=20
[KC>] I think a DSMIP6 MN can attach to a v6 access network (ASP). In
that case, it can obtain the local Home Agent address by setting the
id-type =3D 0 in the Home Network Identifier Option. This saves it from
doing another DNS roundtrip. I think this need to be clarified in the
DSMIP6 I-D.



> If DHCP-based HA assignment is available, it can of
> course be used.
>=20
[KC>] OK. I hope you will clarify this in the draft.


> Vijay
>=20
>=20
> >
> > -Kuntal
> >
> >
> >> -----Original Message-----
> >> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> >> Sent: Thursday, March 01, 2007 5:04 PM
> >> To: Jari Arkko
> >> Cc: Mobile IPv6 Mailing List
> >> Subject: Local HA assignment using DNS (was Re: [Mip6] AD review
> > ofdraft-
> >> ietf-mip6-bootstrapping-split)
> >>
> >> Jari Arkko wrote:
> >>> Vijay,
> >>>> There was an explicit requirement to support local HA
> >>>> assignment using DNS. IMO, local HA assignment is
> >>>> required for any HA discovery/assignment mechanism. So
> >>>> I would like to keep the text instead of saying it is
> >>>> out of scope.
> >>>>
> >>>> The example is trying to describe how a particular
> >>>> operator may "name" the home agents, what entries appear
> >>>> in the DNS servers, and what FQDNs are provisioned in
> >>>> the mobile node.
> >>>>
> >>>> This particular paragraph underwent multiple changes.
> >>>> I can re-write the text to better explain how it can be
> >>>> done or to address any specific concern.
> >>> The reason that I am reacting on this is that we should
> >>> either explain, fully, how to do it or otherwise declare
> >>> it out of scope.
> >>>
> >>> I see several holes in the example text, including, for
> >>> instance, how the mobile nodes determine the locations,
> >>> how changes in the available locations are managed
> >>> between the MN and HA implementations, etc.
> >> I re-wrote the text a bit. Here is the new text.
> >>
> >>     Additionally, the ability to provide a mobile node with a
> > localized
> >>     home agent (e.g. on the visited link) can help to optimize
> > handover
> >>     signaling and improve routing efficiency in bi-directional
> > tunneling
> >>     mode.  There are many mechanisms to assign a local home agent
to a
> >>     mobile node.  These mechanisms are out of scope for this
document,
> >>     but a couple of them are described here as examples.  One
> > mechanism
> >>     is to provision the mobile node with an FQDN for a local home
> > agent
> >>     when it attaches to the local link through an access link
specific
> >>     mechanism.  For example the FQDN of the local home agent can be
> > sent
> >>     to the mobile node using DHCP.  Another mechanism is to specify
an
> >>     interoperable naming convention for constructing home agent
FQDNs
> >>     based on the mobile node's location.  For example, a mobile
> > network
> >>     operator may assign the FQDN "ha.locationA.operator.com" to the
> > Home
> >>     Agent located in "location A" and the FQDN
> >>     "ha.locationB.operator.com" to the Home Agent located in
"location
> >>     B".  If the Mobile Node is attached to "location A" and wants
to
> > use
> >>     a Home Agent located in "location A", it will set the QNAME to
> >>     "ha.locationA.operator.com" in the DNS request.  The Mobile
Node
> >>     determines that it is attached to "location A" through access
link
> >>     specific mechanisms.  If the mobile operator changes the
location
> >>     information for a particular local link, the FQDNs for the home
> >>     agents on the local link should also be updated with the new
> > location
> >>     information.
> >>
> >>     If the mobile node is unable to discover a local home agent, it
> > MUST
> >>     use the home agent on its home link.
> >>
> >> Comments?
> >>
> >> _______________________________________________
> >> 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 Fri Mar 02 23:24:06 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNLmm-0007iv-6j; Fri, 02 Mar 2007 23:23:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNLml-0007ii-Ax
	for mip6@ietf.org; Fri, 02 Mar 2007 23:23:55 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNLmj-0002o8-SW
	for mip6@ietf.org; Fri, 02 Mar 2007 23:23:55 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id A781890011
	for <mip6@ietf.org>; Fri,  2 Mar 2007 23:23:50 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 17667-01 for <mip6@ietf.org>;
	Fri, 2 Mar 2007 23:23:44 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Fri,  2 Mar 2007 23:23:44 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 23:23:44 -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: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
Date: Fri, 2 Mar 2007 23:23:44 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA2E@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Local HA assignment using DNS (was Re: [Mip6] AD review
	ofdraft-ietf-mip6-bootstrapping-split)
Thread-Index: AcdcxYx6B8eWog1RQ/6TyzqAv8eFfQAhOQHw
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 03 Mar 2007 04:23:44.0568 (UTC)
	FILETIME=[BB103380:01C75D4B]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
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



> -----Original Message-----
> From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> Sent: Friday, March 02, 2007 3:39 AM
> To: Chowdhury, Kuntal
> Cc: Vijay Devarapalli; Jari Arkko; Mobile IPv6 Mailing List
> Subject: Re: Local HA assignment using DNS (was Re: [Mip6] AD review
> ofdraft-ietf-mip6-bootstrapping-split)
>=20
> On 3/2/07, Chowdhury, Kuntal <kchowdhury@starentnetworks.com> wrote:
> > > One mechanism
> > >     is to provision the mobile node with an FQDN for a local home
> > agent
> > >     when it attaches to the local link through an access link
specific
> > >     mechanism.  For example the FQDN of the local home agent can
be
> > sent
> > >     to the mobile node using DHCP.
> >
> > Why only FQDN? The local HA address can be sent directly to the MN.
Why
> > asking the MN to do one more roundtrip with DNS? Just use the DHCP
> > options in HIOPT. If DHCP is used by the MN, and if the DHCP server
has
> > local HA address info, it should be able to give it out to the MN.
> >
>=20
> Kuntal, this text is for split scenario draft. The DHCP option is not
> a solution for split scenario.
>=20
[KC>] Gerardo, I understand. But, we are talking about local HA
assignment in the ASP. The proposed text says that the MN will first
figure out the local network name via DHCP, then the MN will use DNS to
figure out an HA in the local domain. The point is, if the MN can do
DHCPv6 and if it can send Home Network Identifier Option in the first
place, it won't have to do two roundtrips. Do you think it will be bad
to refer to an easier option for the MN in the split I-D.? i.e. If
possible, use DHCPv6 directly to obtain local HA address. I think it
makes sense since it reduces the number of roundtrips.


> --Gerardo
>=20
> > -Kuntal
> >
> >
> > > -----Original Message-----
> > > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > > Sent: Thursday, March 01, 2007 5:04 PM
> > > To: Jari Arkko
> > > Cc: Mobile IPv6 Mailing List
> > > Subject: Local HA assignment using DNS (was Re: [Mip6] AD review
> > ofdraft-
> > > ietf-mip6-bootstrapping-split)
> > >
> > > Jari Arkko wrote:
> > > > Vijay,
> > > >> There was an explicit requirement to support local HA
> > > >> assignment using DNS. IMO, local HA assignment is
> > > >> required for any HA discovery/assignment mechanism. So
> > > >> I would like to keep the text instead of saying it is
> > > >> out of scope.
> > > >>
> > > >> The example is trying to describe how a particular
> > > >> operator may "name" the home agents, what entries appear
> > > >> in the DNS servers, and what FQDNs are provisioned in
> > > >> the mobile node.
> > > >>
> > > >> This particular paragraph underwent multiple changes.
> > > >> I can re-write the text to better explain how it can be
> > > >> done or to address any specific concern.
> > > >
> > > > The reason that I am reacting on this is that we should
> > > > either explain, fully, how to do it or otherwise declare
> > > > it out of scope.
> > > >
> > > > I see several holes in the example text, including, for
> > > > instance, how the mobile nodes determine the locations,
> > > > how changes in the available locations are managed
> > > > between the MN and HA implementations, etc.
> > >
> > > I re-wrote the text a bit. Here is the new text.
> > >
> > >     Additionally, the ability to provide a mobile node with a
> > localized
> > >     home agent (e.g. on the visited link) can help to optimize
> > handover
> > >     signaling and improve routing efficiency in bi-directional
> > tunneling
> > >     mode.  There are many mechanisms to assign a local home agent
to a
> > >     mobile node.  These mechanisms are out of scope for this
document,
> > >     but a couple of them are described here as examples.  One
> > mechanism
> > >     is to provision the mobile node with an FQDN for a local home
> > agent
> > >     when it attaches to the local link through an access link
specific
> > >     mechanism.  For example the FQDN of the local home agent can
be
> > sent
> > >     to the mobile node using DHCP.  Another mechanism is to
specify an
> > >     interoperable naming convention for constructing home agent
FQDNs
> > >     based on the mobile node's location.  For example, a mobile
> > network
> > >     operator may assign the FQDN "ha.locationA.operator.com" to
the
> > Home
> > >     Agent located in "location A" and the FQDN
> > >     "ha.locationB.operator.com" to the Home Agent located in
"location
> > >     B".  If the Mobile Node is attached to "location A" and wants
to
> > use
> > >     a Home Agent located in "location A", it will set the QNAME to
> > >     "ha.locationA.operator.com" in the DNS request.  The Mobile
Node
> > >     determines that it is attached to "location A" through access
link
> > >     specific mechanisms.  If the mobile operator changes the
location
> > >     information for a particular local link, the FQDNs for the
home
> > >     agents on the local link should also be updated with the new
> > location
> > >     information.
> > >
> > >     If the mobile node is unable to discover a local home agent,
it
> > MUST
> > >     use the home agent on its home link.
> > >
> > > Comments?
> > >
> > > _______________________________________________
> > > 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 Mar 02 23:53:38 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNMEy-0001jd-Hb; Fri, 02 Mar 2007 23:53:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNMEw-0001jY-Ve
	for mip6@ietf.org; Fri, 02 Mar 2007 23:53:02 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNMEt-0004yo-LH
	for mip6@ietf.org; Fri, 02 Mar 2007 23:53:02 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 2CD8090011
	for <mip6@ietf.org>; Fri,  2 Mar 2007 23:52:51 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 18783-05 for <mip6@ietf.org>;
	Fri, 2 Mar 2007 23:52:45 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Fri,  2 Mar 2007 23:52:45 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 23:52:45 -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] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Fri, 2 Mar 2007 23:52:45 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA2F@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5gACVGXHA=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 03 Mar 2007 04:52:45.0636 (UTC)
	FILETIME=[C8D21840:01C75D4F]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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: Alper Yegin [mailto:alper.yegin@yegin.org]
> Sent: Friday, March 02, 2007 5:26 AM
> To: 'Narayanan, Vidya'; 'Mobile IPv6 Mailing List'
> Subject: RE: [Mip6] WGLC: Reviewofdraft-ietf-mip6-bootstrapping-
> integrated-dhc-02
>=20
> >
> > 5. I noticed a discussion based on Kilian's comments to include the
HoA
> > allocation via DHCP as a possible option. If we decide to include
that,
> > it would be important to talk about how that HoA gets tied to the SA
> > created between the MN and HA. If the HoA is assinged via IKEv2,
IKEv2
> > takes care of such a binding. If not, we need to describe how the
> > address is bound to the SA. The use of DHCP to assign anything
requiring
> > particular security values is tricky to handle and I suggest that we
> > don't get into that in this draft.
>=20
> I'll leave this to Kuntal.
>=20
[KC>] Well, I don't understand what is tricky in getting an IPv6 address
assigned from DHCP server and using it in the IKEv2 CFG_REQUEST as
*requested* INTERNAL_IP6_ADDRESS. This is clearly allowed in RFC 4306.
Even mip6-ikev2 spec talks about this:

"
   The mobile node could suggest a home address that it wants to use in
   the CFG_REQUEST.  For example, this could be a home address that it
   was allocated before or could be an address the mobile node auto-
   configured from the IPv6 prefix on the home link.  The Home Agent
   could let the mobile node use the same home address by setting the
   INTERNAL_IP6_ADDRESS attribute in the CFG_REPLY payload to the same
   home address.  If the home agent wants the mobile node to use a
   different home address, it sends a new home address in the
   INTERNAL_IP6_ADDRESS attribute in the CFG_REPLY payload.  The Mobile
   Node MUST stop using its old home address and start using the newly
   allocated home address.
"

-Kuntal
=20

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



From mip6-bounces@ietf.org Sat Mar 03 08:53:16 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNUeI-0005e6-Ry; Sat, 03 Mar 2007 08:51:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNUeI-0005e1-1y
	for mip6@ietf.org; Sat, 03 Mar 2007 08:51:46 -0500
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNUeG-0004qf-Dx
	for mip6@ietf.org; Sat, 03 Mar 2007 08:51:46 -0500
Received: from ep_ms5_bk (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 <0JEB00FCJYHXBI@mailout2.samsung.com> for mip6@ietf.org;
	Sat, 03 Mar 2007 22:51:33 +0900 (KST)
Received: from ep_spt01 (ms5.samsung.com [203.254.225.113])
	by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTP id <0JEB0025CYHW2E@ms5.samsung.com> for mip6@ietf.org; Sat,
	03 Mar 2007 22:51:33 +0900 (KST)
Content-return: prohibited
Date: Sat, 03 Mar 2007 13:51:32 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Message-id: <0JEB0025DYHW2E@ms5.samsung.com>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070303135132849@heejin.jang
X-MTR: 20070303135132849@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Generator: NamoMIME 6.0.0.8
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: "mip6@ietf.org" <mip6@ietf.org>
Subject: [Mip6] Re: HIOPT clarification
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: heejin.jang@samsung.com
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0857490005=="
Errors-To: mip6-bounces@ietf.org

--===============0857490005==
Content-return: prohibited
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: base64

PEhUTUw+PEhFQUQ+CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9J3RleHQv
aHRtbDsgY2hhcnNldD13aW5kb3dzLTEyNTInPgo8dGl0bGU+U2Ftc3VuZyBFbnRlcnByaXNlIFBv
cnRhbCBteVNpbmdsZTwvdGl0bGU+CjxzdHlsZT4gUCwgdGQsIGxpIHtmb250LWZhbWlseTpBcmlh
bCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7IG1hcmdpbi10b3A6NXB4O21hcmdpbi1ib3R0b206NXB4
O30gYm9keXtmb250LWZhbWlseTpBcmlhbCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7fTwvc3R5bGU+
CjwvSEVBRD48Qk9EWT5IaSwgS3VudGFsIGFuZCBhbGwuDQo8cD5LaW5kbHkgc2VlIHRoZSBpbmxp
bmUuPC9wPg0KPGJyPi0tLS0tLS0gPGI+T3JpZ2luYWwgTWVzc2FnZTwvYj4gLS0tLS0tLTxicj48
Yj5TZW5kZXI8L2I+IDogQ2hvd2RodXJ5LCBLdW50YWwmbHQ7a2Nob3dkaHVyeUBzdGFyZW50bmV0
d29ya3MuY29tJmd0Ozxicj48Yj5EYXRlPC9iPiAgIDogMjAwNy0wMy0wMSAwMjoxODxicj48Yj5U
aXRsZTwvYj4gIDogSElPUFQgY2xhcmlmaWNhdGlvbjxicj48YnI+SGkmbmJzcDtIZWVqaW4sJm5i
c3A7YWxsLA0KPGJyPg0KPGJyPkJhc2VkJm5ic3A7b24mbmJzcDt0aGUmbmJzcDtjb21tZW50Jm5i
c3A7ZnJvbSZuYnNwO0tpbGlhbiwmbmJzcDtJJm5ic3A7dGhpbmsmbmJzcDt3ZSZuYnNwO3Nob3Vs
ZCZuYnNwO2NsYXJpZnkmbmJzcDtob3cmbmJzcDt0aGUmbmJzcDtNTg0KPGJyPnJlcXVlc3RzJm5i
c3A7SEEmbmJzcDthZGRyZXNzJm5ic3A7Zm9yJm5ic3A7ZGlmZmVyZW50Jm5ic3A7c2VydmljZS9w
cm90b2NvbC4mbmJzcDtNeSZuYnNwO3Byb3Bvc2FsJm5ic3A7aXM6DQo8YnI+DQo8YnI+SW4mbmJz
cDt0aGUmbmJzcDtISU9QVCZuYnNwO0ktRCwmbmJzcDt3ZSZuYnNwO2luY2x1ZGUmbmJzcDtleGFt
cGxlJm5ic3A7ZW5jb2RpbmcmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO0hvbWUmbmJzcDtOZXR3b3Jr
DQo8YnI+SWRlbnRpZmllciZuYnNwOyhGUUROKSZuYnNwO2FzJm5ic3A7Zm9sbG93czoNCjxicj4N
Cjxicj5JUHY2Jm5ic3A7YWRkcmVzcyZuYnNwO29mJm5ic3A7TUlQNiZuYnNwO0hBOiZuYnNwO2hh
Lm1pcDYuZG9tYWluDQo8YnI+SVB2NiZuYnNwO2FkZHJlc3MmbmJzcDtvZiZuYnNwO0RTTUlQNiZu
YnNwO0hBOiZuYnNwO2hhLmRzbWlwNi5pcDYuZG9tYWluDQo8YnI+SVB2NCZuYnNwO2FkZHJlc3Mm
bmJzcDtvZiZuYnNwO0RTTUlQNiZuYnNwO0hBOiZuYnNwO2hhLmRzbWlwNi5pcDQuZG9tYWluDQo8
YnI+DQo8cD4mbmJzcDs8L3A+DQo8cD4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtISiZn
dDsmZ3Q7Jm5ic3A7UkZDMjc4MiBkZXNjcmliZXMmbmJzcDtzdWNoJm5ic3A7YSANCmVuY29kZWQg
JnF1b3Q7IF9TZXJ2aWNlLl9Qcm90by5OYW1lJnF1b3Q7IGZvcm1hdDwvcD4NCjxwPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOygnXycgZm9yIA0KICAgICAgICB0aGUgc2VydmljZSBpZGVu
dGlmaWVyIHRvIGF2b2lkIGNvbGxpc2lvbnMgd2l0aCBETlMgbGFiZWxzLikNCjwvcD4NCjxwPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0ZvciB0aGUgcHJvcG9zZWQmbmJzcDsqZW5jb2Rl
ZCogRlFETiwgJm5ic3A7SSANCnRoaW5rICZuYnNwO3RoZSBydWxlIGZvciBlbmNvZGluZyBzaG91
bGQgYmUgc3RhbmRhcmRpemVkIGFzIFJGQzI3ODIuIDwvcD4NCjxwPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwO0kgcHJlZmVyIHRvIGxldCBpdCBhbm90aGVyIHN0YW5kYWxvbmUg
DQpzdGFuZGFyZCBvciBwb3NzaWJseSZuYnNwO2JlIHJlZmxlY3RlZCBpbiBuZXh0LXZlcnNpb24t
b2YgUkZDMjc4MiwmbmJzcDthbmQgDQpqdXN0PC9wPg0KPHA+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7bWFrZSBhIHNpbXBsZSZuYnNwO3N0YXRlbWVudCByZWZlcmluZyB0byBpdCANCmlu
IEhJT1BUIGRvY3VtZW50LjwvcD4NCjxwPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOzwvcD4NCjxwPlRoZSZuYnNwO3N1Yi1vcHQtY29kZSZuYnNwO2ZpZWxkJm5ic3A7aW4mbmJz
cDt0aGUmbmJzcDtNSVA2Jm5ic3A7UmVsYXkmbmJzcDtBZ2VudCZuYnNwO1N1Yi1vcHRpb24mbmJz
cDthbmQmbmJzcDtIb21lDQo8YnI+TmV0d29yayZuYnNwO0luZm9ybWF0aW9uJm5ic3A7U3ViLW9w
dGlvbiZuYnNwO3Nob3VsZCZuYnNwO2JlJm5ic3A7ZW5jb2RlZCZuYnNwO2FjY29yZGluZ2x5Lg0K
PGJyPg0KPGJyPkNvbW1lbnRzPw0KPGJyPg0KPGJyPi1LdW50YWwNCjxicj4NCjxicj4NCjxicj4m
cXVvdDtUaGlzJm5ic3A7ZW1haWwmbmJzcDttZXNzYWdlJm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7
YXR0YWNobWVudHMmbmJzcDthcmUmbmJzcDtjb25maWRlbnRpYWwmbmJzcDtpbmZvcm1hdGlvbiZu
YnNwO29mJm5ic3A7U3RhcmVudCZuYnNwO05ldHdvcmtzLCZuYnNwO0NvcnAuJm5ic3A7VGhlJm5i
c3A7aW5mb3JtYXRpb24mbmJzcDt0cmFuc21pdHRlZCZuYnNwO21heSZuYnNwO25vdCZuYnNwO2Jl
Jm5ic3A7dXNlZCZuYnNwO3RvJm5ic3A7Y3JlYXRlJm5ic3A7b3ImbmJzcDtjaGFuZ2UmbmJzcDth
bnkmbmJzcDtjb250cmFjdHVhbCZuYnNwO29ibGlnYXRpb25zJm5ic3A7b2YmbmJzcDtTdGFyZW50
Jm5ic3A7TmV0d29ya3MsJm5ic3A7Q29ycC4mbmJzcDsmbmJzcDtBbnkmbmJzcDtyZXZpZXcsJm5i
c3A7cmV0cmFuc21pc3Npb24sJm5ic3A7ZGlzc2VtaW5hdGlvbiZuYnNwO29yJm5ic3A7b3RoZXIm
bmJzcDt1c2UmbmJzcDtvZiwmbmJzcDtvciZuYnNwO3Rha2luZyZuYnNwO29mJm5ic3A7YW55Jm5i
c3A7YWN0aW9uJm5ic3A7aW4mbmJzcDtyZWxpYW5jZSZuYnNwO3Vwb24mbmJzcDt0aGlzJm5ic3A7
ZS1tYWlsJm5ic3A7YW5kJm5ic3A7aXRzJm5ic3A7YXR0YWNobWVudHMmbmJzcDtieSZuYnNwO3Bl
cnNvbnMmbmJzcDtvciZuYnNwO2VudGl0aWVzJm5ic3A7b3RoZXImbmJzcDt0aGFuJm5ic3A7dGhl
Jm5ic3A7aW50ZW5kZWQmbmJzcDtyZWNpcGllbnQmbmJzcDtpcyZuYnNwO3Byb2hpYml0ZWQuJm5i
c3A7SWYmbmJzcDt5b3UmbmJzcDthcmUmbmJzcDtub3QmbmJzcDt0aGUmbmJzcDtpbnRlbmRlZCZu
YnNwO3JlY2lwaWVudCwmbmJzcDtwbGVhc2UmbmJzcDtub3RpZnkmbmJzcDt0aGUmbmJzcDtzZW5k
ZXImbmJzcDtpbW1lZGlhdGVseSZuYnNwOy0tJm5ic3A7YnkmbmJzcDtyZXBseWluZyZuYnNwO3Rv
Jm5ic3A7dGhpcyZuYnNwO21lc3NhZ2UmbmJzcDtvciZuYnNwO2J5Jm5ic3A7c2VuZGluZyZuYnNw
O2FuJm5ic3A7ZW1haWwmbmJzcDt0byZuYnNwO3Bvc3RtYXN0ZXJAc3RhcmVudG5ldHdvcmtzLmNv
bSZuYnNwOy0tJm5ic3A7YW5kJm5ic3A7ZGVzdHJveSZuYnNwO2FsbCZuYnNwO2NvcGllcyZuYnNw
O29mJm5ic3A7dGhpcyZuYnNwO21lc3NhZ2UmbmJzcDthbmQmbmJzcDthbnkmbmJzcDthdHRhY2ht
ZW50cyZuYnNwO3dpdGhvdXQmbmJzcDtyZWFkaW5nJm5ic3A7b3ImbmJzcDtkaXNjbG9zaW5nJm5i
c3A7dGhlaXImbmJzcDtjb250ZW50cy4mbmJzcDtUaGFuayZuYnNwO3lvdS4mcXVvdDsNCjxicj4N
Cjxicj4NJm5ic3A7LS0mbmJzcDsmbmJzcDsmbmJzcDtSZWdhcmQKPGJyPjwvcD4NCjxwPkhlZWpp
bjwvcD4NCjwvQk9EWT48L0hUTUw+




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

--===============0857490005==--



From mip6-bounces@ietf.org Sun Mar 04 14:03:35 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HNvyf-0003Vt-Fr; Sun, 04 Mar 2007 14:02:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HNvye-0003UY-Hv
	for mip6@ietf.org; Sun, 04 Mar 2007 14:02:36 -0500
Received: from smtp.elet.polimi.it ([131.175.120.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNvyc-0001iH-Vv
	for mip6@ietf.org; Sun, 04 Mar 2007 14:02:36 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.elet.polimi.it (Postfix) with ESMTP id A99A515DF91
	for <mip6@ietf.org>; Sun,  4 Mar 2007 20:02:33 +0100 (CET)
X-Virus-Scanned: amavisd-new at elet.polimi.it
Received: from smtp.elet.polimi.it ([127.0.0.1])
	by localhost (smtp1.elet.polimi.it [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id Xl8J1MeGRVpX for <mip6@ietf.org>;
	Sun,  4 Mar 2007 20:02:33 +0100 (CET)
Received: from laptopcapone (host-84-221-106-200.cust-adsl.tiscali.it
	[84.221.106.200]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client did not present a certificate)
	by smtp.elet.polimi.it (Postfix) with ESMTP id 3DD6B15DF8E
	for <mip6@ietf.org>; Sun,  4 Mar 2007 20:02:33 +0100 (CET)
From: "Antonio Capone" <capone@elet.polimi.it>
To: <mip6@ietf.org>
Date: Sun, 4 Mar 2007 20:02:35 +0100
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.3028
Thread-Index: Acdej4c3Uf4GXm72Q4SPIdwX1+AmDQ==
Message-Id: <20070304190233.3DD6B15DF8E@smtp.elet.polimi.it>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Subject: [Mip6] MOBIQUITOUS 2007: Paper submission deadline approaching
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: capone@elet.polimi.it
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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.

MOBIQUITOUS 2007
Deadline approaching!
Paper Registration Deadline: March 13, 2007
Paper Submission Deadline: March 20, 2007


========================================================================
                           CALL FOR PAPERS

                           MOBIQUITOUS 2007
The 4th Annual International Conference on Mobile and Ubiquitous Systems:
                   Computing, Networking and Services
                       http://www.mobiquitous.org
                  August 6-10, 2007 -  Philadelphia, PA
                    In Cooperation with ACM SIGMOBILE
      Technical-sponsored by IEEE and IEEE Computer Society (pending)
                   Co-sponsored by Create-Net and ICST

========================================================================

The combination of mobile and ubiquitous computing is emerging as a 
promising new paradigm. Through the use of mobile devices and devices 
embedded in the surrounding physical environments, users can be provided 
transparent computing and communication services at all times and in all 
places. The complexity of providing such services stems from the fact that 
the communication devices and the objects with which they interact may 
both be mobile. The implementation of such a paradigm requires advances in 
wireless network technologies and devices, development of infrastructures 
supporting cognitive environments, discovery and identification of 
ubiquitous computing applications and services, and an understanding of 
the cross-layer interactions between all of these components. The Fourth 
Annual International Conference on Mobile and Ubiquitous Systems: 
Computing, Networking and Services (Mobiquitous-07) will provide a forum 
where practitioners and researchers coming from many areas involved in 
ubiquitous solutions, design and deployment will be able to interact and 
exchange experiences needed to build successful ubiquitous systems. Areas 
addressed by the conference include applications, service-oriented 
computing, middleware, networking, agents, data management and services, 
all with special focus on mobility and ubiquitous computing. The conference 
publications will be considered for inclusion in the following places:
IEEE Xplore, SCI/ISI Web of Knowledge, Inspec, EI(Elsevier)/Scopus, DBLP, 
Directory of Published Proceedings (InterDok), The Collection of Computer 
Science Bibliographies(CSB), EBSCO, British Library, American Mathematical 
Society (AMS), Crossref, German National Library of Science and Technology.

PAPERS: Technical papers describing original, previously unpublished 
research, not currently under review by another conference or journal, are 
solicited. Technical papers clearly identifying how the specific 
contributions fit to an overall working solution are particularly of 
interest. Topics include, but are not limited to, the following feature 
topics as applied to mobile and ubiquitous environments:

- Ubiquitous architectures, systems and applications
- Wearable computing and personal area networks
- Wireless technologies for mobile and ubiquitous
     (Bluetooth, ZigBee, 802.15.x, WiFi)
- Wireless Internet access in ubiquitous systems
- Ad hoc and sensor networks support for ubiquitous computing
- Reconfigurability and personalization of wireless networks
- Wireless/mobile service management and delivery
- Security, privacy and social issues of mobile and ubiquitous systems
- Service and knowledge discovery, matching and composition mechanisms
- Location-based services and tracking in ubiquitous environments
- Context- and location-aware applications
- Agent technologies in ubiquitous, wearable, and mobile systems
- Context modeling, services and frameworks
- Toolkits, testbeds, development environments, and languages for
      ubiquitous computing
- Rapid prototyping of ubiquitous applications
- Ontologies for mobile and ubiquitous computing
- Mobile and ubiquitous data management and processing
- Data replication, migration and dissemination in ubiquitous environments
- Queries, transactions and workflows in mobile and ubiquitous environments
- Multimodal interfaces (speech, video kinetic, tactile)

SUBMISSION INSTRUCTIONS: All paper submissions will be handled 
electronically (see the conference web page for details). Authors should 
prepare an Adobe Acrobat PDF version of their full paper. Papers must not 
exceed 8 pages double column (US Letter size, 8.5 x 11 inches) including 
text, figures and references. The font size must be at least 10 points.

PUBLICATION: All submitted papers will be rigorously reviewed by the 
international technical program committee. Accepted papers will be 
published in the conference proceedings. Papers of particular merit will 
be proposed for publication in the ACM/Kluwer Mobile Networks and 
Applications (MONET) journal.

IMPORTANT DATES:

Paper Registration Deadline: March 13, 2007
Paper Submission Deadline: March 20, 2007
Notification of Acceptance: May 4, 2007
Camera-ready Manuscripts due: June 4, 2007


CONFERENCE ORGANIZING COMMITTEE:

GENERAL CHAIR:
Guohong Cao, The Pennsylvania State University

TECHNICAL PROGRAM CHAIR:
Robin Kravets, University of Illinois at Urbana-Champaign

TECHNICAL PROGRAM CO-CHAIRS:
Anind Dey, Carnegie Mellon University
Hui Lei, IBM Research

WORKSHOP CHAIR:
Suman Banerjee, University of Wisconsin-Madison

DEMO CHAIR:
Hao Zhu, Florida International University

POSTER CHAIR:
Al Harris, Universita di Padova
Dong Xuan, Ohio State University

FINANCE CHAIR:
Karen Decker, ICST

PUBLICATION CHAIR:
Cristina Nita-Rotaru, Purdue university

PUBLICITY CHAIR:
Antonio Capone, Politecnico di Milano
Wensheng Zhang, Iowa State University

LOCAL CHAIR:
Zhen Jiang, West Chester University of Pennsylvania

WEB CHAIR:
Hui Song, Penn State University

CONFERENCE COORDINATOR
Zita Rozsa, ICST

STEERING COMMITTEE
Imrich Chlamtac, Create-Net (chair)
Fausto Giunchiglia, University of Trento
Tom La Porta, Penn State University
Francesco De Pellegrini, Create-Net
Chiara Petrioli, Universita di Roma "La Sapienza"
Krishna Sivalingam, University of Maryland Baltimore County
Michele Zorzi, Universita di Padova

TECHNICAL PROGRAM COMMITTEE:
See  http://www.mobiquitous.org




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



From mip6-bounces@ietf.org Mon Mar 05 04:21:04 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HO9N6-0004Yh-Pw; Mon, 05 Mar 2007 04:20:44 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HO9N4-0004YZ-Ud
	for mip6@ietf.org; Mon, 05 Mar 2007 04:20:43 -0500
Received: from cluster-j.mailcontrol.com ([86.111.223.190])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HO9N2-00008p-RV
	for mip6@ietf.org; Mon, 05 Mar 2007 04:20:42 -0500
Received: from rly11j.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly11j.srv.mailcontrol.com (MailControl) with ESMTP id
	l259KJoL012007
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Mon, 5 Mar 2007 09:20:24 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly11j.srv.mailcontrol.com (MailControl) id l259JsHT010672
	for mip6@ietf.org; Mon, 5 Mar 2007 09:19:54 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly11j-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l259JlPF010485; Mon, 05 Mar 2007 09:19:54 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 1db4_cd73cf9a_caf7_11db_98ee_0030482aac25;
	Mon, 05 Mar 2007 09:59:18 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030510193582-1224435 ;
	Mon, 5 Mar 2007 10:19:35 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.154,BAYES_00: -1.665,TOTAL_SCORE: -1.819
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 5 Mar 2007 10:24:32 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: home network requested by MN may be != assigned network (was: RE:
	[Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBD9BA@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: home network requested by MN may be != assigned network (was:
	RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
Thread-Index: AcdZUPl3RCOZHB9nQb6+3hPvBup2ywBYXBGgARQFcMA=
References: <7CCD07160348804497EF29E9EA5560D7FBD9BA@exchtewks2.starentnetworks.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F012785AB@lan-ex-01.panasonic.de>
Date: Mon, 5 Mar 2007 10:16:27 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MailControl A-07-06-80 (www.mailcontrol.com) on 10.74.1.121
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 38a35b5fc88e9b9a2affced027b040a4
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, heejin.jang@samsung.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kuntal, Heejin,

since the MN's MSA is the entity that assigns a home network and an MSP =
to the MN, I guess that it is allowed that the MSA assigns a different =
home network from a different MSP to the MN than requested by the MN in =
the Home Network Identifier DHCP Option. This is needed, e.g., when the =
MSA doesn't have a roaming relationship with the MSP requested by the =
MN, when the requested MSP doesn't provide the required service (e.g., =
DSMIP, NEMO etc) or when the MSA knows of a better (e.g., less loaded) =
home network from a different MSP. I think this is currently not =
mentioned in the draft and it would be good to clarify.

Regards,

Kilian


> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
> Sent: Dienstag, 27. Februar 2007 22:02
> To: heejin.jang@samsung.com; Kilian Weniger
> Cc: mip6@ietf.org; Basavaraj Patil
> Subject: RE: RE: RE: [Mip6] WGLC:=20
> draft-ietf-mip6-bootstrapping-integrated-02
>=20
> Thanks Heejin. I think your suggested clarification # 3 is good.=20
>=20
> -Kuntal
>=20
>=20
> ________________________________________
> From: Heejin Jang [mailto:heejin.jang@samsung.com]=20
> Sent: Sunday, February 25, 2007 8:45 PM
> To: Kilian Weniger
> Cc: mip6@ietf.org; Basavaraj Patil
> Subject: Re: RE: RE: [Mip6] WGLC:=20
> draft-ietf-mip6-bootstrapping-integrated-02
>=20
> Hi, Kilian.=20
> Thanks for the comments.=20
> =A0
> Regarding the use of term, the draft(hiopt)=A0supports all the=20
> three following networks as target networks
> 1) ASP (MN's currently visited network)
> 2) Home MSP (=3D MSA)
> 3) MSP (network which is nether =A0ASP nor Home MSP but has=20
> trust relationship with MN's MSA)
> =A0
> The=A0term 'home MSP' can be ambiguous since it does not include 3),=20
> so we will modify it to 'MSP with roaming =A0relationship with=20
> MN's MSA' for more clarification.
> Thanks.
> =A0
> Regards,=20
> Heejin.
>=20
> ------ Original Message -------
> Sender : Kilian Weniger<Kilian.Weniger@eu.panasonic.com>
> Date : 2007-02-22 23:00
> Title : RE: RE: [Mip6] WGLC:=20
> draft-ietf-mip6-bootstrapping-integrated-02
>=20
> Hi=A0Heejin,=20
>=20
> thanks=A0for=A0your=A0comments,=A0see=A0my=A0replies=A0inline.=A0=20
>=20
> =
Please=A0note=A0that=A0the=A0comments=A0in=A0my=A0mail=A0were=A0referring=
=A0to=20
> =
draft-ietf-mip6-bootstrapping-integrated-02.=A0And=A0since=A0the=A0refere=
nce=20
> =
[HIOPT]=A0in=A0draft-ietf-mip6-bootstrapping-integrated-02=A0is=A0hiopt-0=
1,=A0I=20
> didn't=A0consider=A0hiopt-02.=A0=20
>=20
> >=A0-----Original=A0Message-----=20
> >=A0From:=A0Heejin=A0Jang=A0[mailto:heejin.jang@samsung.com]=A0=20
> >=A0Sent:=A0Dienstag,=A020.=A0Februar=A02007=A008:31=20
> >=A0To:=A0Kilian=A0Weniger=20
> >=A0Cc:=A0Basavaraj=A0Patil;=A0mip6@ietf.org=20
> >=A0Subject:=A0Re:=A0RE:=A0[Mip6]=A0WGLC:=A0=20
> >=A0draft-ietf-mip6-bootstrapping-integrated-02=20
> >=A0=20
> >=A0Hi,=A0=A0Kilian=A0Weniger.=A0=20
> >=A0=20
> >=A0Thanks=A0for=A0the=A0detailedl=A0comments.=A0=20
> >=A0=20
> =
>=A0Please=A0see=A0the=A0inline=A0comments=A0for=A0the=A0HIOPT=A0draft.=20
> >=A0=20
> >=A0=20
> >=A0-------=A0Original=A0Message=A0-------=20
> >=A0Sender=A0:=A0Kilian=A0Weniger<Kilian.Weniger@eu.panasonic.com>=20
> >=A0Date=A0:=A02007-02-16=A017:31=20
> >=A0Title=A0:=A0RE:=A0[Mip6]=A0WGLC:=A0
> draft-ietf-mip6-bootstrapping-integrated-02=20
> >=A0=20
> >=A0Hi,=A0=20
> >=A0=20
> >=A0please=A0find=A0below=A0some=A0comments=A0about=A0=A0=20
> >=A0draft-ietf-mip6-bootstrapping-integrated-02.=A0=20
> >=A0=20
> =
>=A0The=A0draft=A0is=A0well=A0written=A0and=A0easy=A0to=A0understand=A0(t=
hanks=A0to=A0=20
> >=A0figures=A0and=A0=20
> =
>=A0message=A0sequence=A0text).=A0However,=A0some=A0details=A0and=A0corne=
r=A0=20
> >=A0cases=A0are=A0not=A0=20
> >=A0addressed,=A0which=A0may=A0need=A0to=A0be=A0specified,=A0e.g.:=A0=20
> >=A0=20
> =
>=A0-=A0How=A0does=A0the=A0NAS/relay=A0map=A0a=A0DHCP=A0request=A0receive=
d=A0from=A0a=A0=20
> >=A0specific=A0MN=A0=A0=20
> =
>=A0=A0=A0to=A0the=A0cached=A0home=A0network=A0information=A0previously=A0=
received=A0=20
> >=A0from=A0AAAH=A0=A0=20
> =
>=A0=A0=A0for=A0this=A0MN,=A0so=A0that=A0it=A0can=A0include=A0the=A0corre=
ct=A0home=A0network=A0=A0=20
> >=A0=A0=A0information=A0in=A0a=A0received=A0DHCP=A0request?=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0The=A0mapping=A0mechanism=A0is=A0added=A0in=A0section=A04.3=
=A0of=A0the=A0=20
> >=A0latest=A0version=A0of=A0the=A0document=A0(hiopt-02).=20
>=20
> =
It=A0should=A0be=A0in=A0section=A04.2,=A0since=A0my=A0question=A0was=A0re=
lated=A0to=A0
the=A0DHCP=20
> =
relay=A0behaviour.=A0Maybe=A0I=A0missed=A0it,=A0but=A0I=A0can't=A0see=A0a=
ny=A0
related=A0text=A0in=20
> =
section=A04.2=A0of=A0hiopt-02=A0about=A0mapping=A0of=A0home=A0information=
=A0
received=A0from=20
> =
AAA=A0server=A0to=A0DHCP=A0request=A0received=A0from=A0MN.=A0But=A0Kuntal=
=A0
answered=A0to=A0my=20
> question=A0in=A0his=A0reply=A0email.=A0=20
>=20
> >=A0=20
> =
>=A0The=A0information=A0is=A0mapped=A0based=A0on=A0NAI=A0not=A0by=A0NAS=A0=
but=A0by=A0DHCP=A0=20
> >=A0server.=A0Rrefer=A0to=A0hiopt-02=A0for=A0more=A0details.=20
> >=A0=20
> >=A0=20
> =
>=A0-=A0What=A0is=A0the=A0conceptual=A0data=A0structure=A0needed=A0for=A0=
this=A0in=A0=20
> >=A0the=A0NAS/DHCP=A0=A0=20
> >=A0=A0=A0relay?=A0=20
> =
>=A0-=A0Any=A0default=A0value=A0for=A0how=A0long=A0NAS=A0should=A0cache=A0=
home=A0network=A0=A0=20
> =
>=A0=A0=A0information=A0received=A0from=A0AAA=A0for=A0a=A0specific=A0MN=A0=
(i.e.,=A0
when=A0is=A0NAS=A0=A0=20
> =
>=A0=A0=A0allowed=A0to=A0delete=A0cache=A0entry?)?=A0If=A0this=A0is=A0spe=
cified=A0in=A0=20
> >=A0[MIP6-Dime]=A0=A0=20
> =
>=A0=A0=A0or=A0[MIP6-RADIUS]=A0it=A0should=A0be=A0mentioned=A0and=A0refer=
enced.=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0This=A0is=A0implementation-specific.=A0I'm=A0not=A0sure=A0w=
e=A0need=A0=20
> >=A0to=A0describe=A0down=A0to=A0the=A0smallest=A0detail.=A0=20
>=20
> =
A=A0value=A0doesn't=A0need=A0to=A0be=A0mandated,=A0but=A0I=A0think=A0some=
=A0guidance=A0to=A0the=20
> implementor=A0would=A0be=A0good.=20
>=20
> >=A0=20
> >=A0=20
> =
>=A0-=A0What=A0should=A0NAS=A0do=A0if=A0DHCP=A0request=A0with=A0Home=A0ne=
twork=A0identifier=A0=A0=20
> =
>=A0=A0=A0option=A0is=A0received=A0from=A0a=A0MN=A0and=A0NAS=A0doesn't=A0=
find=A0valid=A0=20
> >=A0home=A0network=A0=A0=20
> =
>=A0=A0=A0information=A0for=A0this=A0MN=A0in=A0its=A0cache=A0(e.g.,=A0sin=
ce=A0the=A0
cache=A0entry=A0=A0=20
> >=A0=A0=A0has=A0expired)?=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>In=A0that=A0case,=A0there=A0is=A0nothing=A0NAS=A0can=A0do.=A0I=
f=A0the=A0=A0=20
> >=A0corresponding=A0information=A0=20
> >=A0=20
> >=A0is=A0configured=A0on=A0the=A0DHCP=A0server=A0(for=A0e.g.,=A0=20
> >=A0pre-configuration),=A0the=A0server=A0will=20
> =
>=A0provide=A0it.=A0Otherwise,=A0it=A0will=A0reply=A0with=A00-lengh=A0opt=
ion.=20
>=20
> =
ok.=A0My=A0comment=A0was=A0that=A0this=A0should=A0be=A0documented=A0(i.e.=
,=A0DHCP=A0server=20
> must=A0reply=A0with=A00-lengh=A0option=A0in=A0this=A0case)=20
>=20
> >=A0=20
> >=A0=20
> =
>=A0-=A0What=A0should=A0DHCP=A0relay/server=A0do=A0if=A0the=A0MN=A0does=A0=
not=A0include=A0the=A0=A0=20
> >=A0=A0=A0OPTION_CLIENTID=A0in=A0the=A0DHCP=A0request=A0or=A0if=A0
> OPTION_MIP6-RELAY-Option=A0=A0=20
> >=A0=A0=A0is=A0missing=A0in=A0request?=A0=20
> >=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0The=A0existing=A0DHCP=A0options=A0are=A0handled=A0according=
=A0to=A0
> [RFC=A03315].=20
> >=A0=20
> =
>=A0The=A0request=A0not=A0including=A0OPTION_CLIENTID=A0is=A0discarded=A0=
in=A0the=A0=20
> >=A0relay/server=20
> >=A0=20
> >=A0as=A0described=A0in=A015.4=A0of=A0[RFC=A03315].=A0=20
>=20
> ok.=20
>=20
> >=A0=20
> >=A0=20
> =
>=A0The=A0draft=A0may=A0need=A0better=A0aligned=A0with=A0[HIOPT].=A0For=A0=
instance,=A0=20
> >=A0it=A0is=A0not=A0=20
> =
>=A0clear=A0to=A0me=A0how=A0exactly=A0the=A0home=A0network=A0identifier=A0=
option=A0=20
> >=A0and=A0the=A0home=A0=A0=20
> =
>=A0network=A0information=A0option=A0specified=A0in=A0[HIOPT]=A0are=A0all=
owed=A0=20
> >=A0to=A0be=A0used=A0=20
> >=A0in=A0draft-ietf-mip6-bootstrapping-integrated-02:=A0=A0=20
> >=A0=20
> =
>=A0-=A0[HIOPT]=A0supports=A0home=A0address=A0allocation.=A0This=A0is=A0n=
ot=A0
mentioned=A0in=A0=A0=20
> >=A0=A0=A0draft-ietf-mip6-bootstrapping-integrated-02.=A0Is=A0this=A0
forbidden=A0or=A0=A0=20
> =
>=A0=A0=A0allowed=A0or=A0out-of-scope?=A0If=A0allowed,=A0when=A0does=A0NA=
S=A0set=A0the=A0=20
> >=A0A-flag=A0in=A0=A0=20
> >=A0=A0=A0the=A0home=A0network=A0identifier=A0option?=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0NAS=A0SHOULD=A0not=A0modify=A0the=A0Home=A0Network=A0Identi=
fier=A0option.=A0=20
> =
>=A0The=A0A-flag=A0is=A0set=A0to=A00/1=A0only=A0by=A0the=A0mobile=A0node.=
=A0If=A0there=A0is=A0=20
> >=A0home=A0address=20
> =
>=A0information=A0at=A0NAS=A0that=A0was=A0acquired=A0during=A0AAA=A0trans=
action,=A0=20
> >=A0it=A0is=A0delivered=20
> =
>=A0to=A0the=A0DHCP=A0server=A0with=A0MIP6-Relay=A0option.=A0(Refer=A0hio=
pt-02.txt)=20
>=20
> =
I=A0was=A0aware=A0of=A0HoA=A0allocation=A0support=A0in=A0[HIOPT].=A0My=A0=
question=A0was=20
> whether=A0it=A0is=A0supported=A0in=A0
> draft-ietf-mip6-bootstrapping-integrated-02=20
> as=A0well,=A0since=A0HoA=A0allocation=A0is=A0not=A0mentioned=A0there.=20
>=20
> >=A0=20
> >=A0=20
> =
>=A0-=A0Is=A0it=A0allowed=A0that=A0multiple=A0HA=A0addresses=A0are=A0retu=
rned=A0in=A0
> the=A0home=A0=A0=20
> >=A0=A0=A0network=A0information=A0option?=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0It=A0is=A0allowed=A0by=A0using=A0multiple=A0home=A0network=A0=
=20
> >=A0information=A0option.=20
> >=A0=20
> =
>=A0=A0=A0"Multiple=A0sub-options=A0may=A0exist=A0in=A0a=A0Home=A0Network=
=A0
Information=A0option=20
> >=A0=20
> =
>=A0=A0=A0=A0to=A0carry=A0more=A0than=A0one=A0home=A0information."=A0(in=A0=
section=A03.3.1)=20
> >=A0=20
> >=A0=20
> =
>=A0-=A0[HIOPT]=A0allows=A0that=A0the=A0home=A0network=A0identifier=A0opt=
ion=A0
> includes=A0an=A0=A0=20
> =
>=A0=A0=A0identifier=A0of=A0a=A0target=A0network,=A0which=A0is=A0differen=
t=A0from=A0home=A0or=A0=A0=20
> =
>=A0=A0=A0visited=A0network=A0of=A0MN.=A0This=A0is=A0not=A0mentioned=A0in=
=A0=A0=20
> =
>=A0=A0=A0draft-ietf-mip6-bootstrapping-integrated-02.=A0Is=A0this=A0allo=
wed=A0or=A0=A0=20
> >=A0=A0=A0forbidden?=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0A=A0target=A0network=A0may=A0or=A0may=A0not=A0be=A0home=A0n=
etwork=A0of=A0
> the=A0MN.=A0=A0=20
>=20
> =
good.=A0I=A0guess=A0"home=A0network"=A0means=A0"home=A0MSP"=A0in=A0this=A0=
case,=A0right?=20
> =
According=A0to=A0RFC4640,=A0the=A0"home=A0MSP"=A0is=A0MN's=A0MSA=A0provid=
ing=A0mobility=20
> service=A0to=A0MN.=A0=20
> =
According=A0to=A0Kuntal's=A0comment,=A0also=A0MSPs=A0other=A0than=A0MSA=A0=
(or=A0
"home=A0MSP")=20
> =
and=A0ASP=A0are=A0supported=A0as=A0target=A0networks.=A0If=A0this=A0is=A0=
true=A0for=A0
hiopt=A0(and=20
> it=A0should=A0be=A0if=A0it=A0is=A0true=A0for=20
> =
draft-ietf-mip6-bootstrapping-integrated-02),=A0then=A0it=A0seems=A0that=A0=
the=20
> =
hiopt=A0draft=A0also=A0uses=A0the=A0term=A0"home=A0MSP"=A0differently=A0t=
han=A0defined=A0in=20
> =
RFC4640.=A0For=A0instance,=A0section=A04.3,=A0case=A0C=A0(id-type=A02)=A0=
says=A0=20
>=20
> =
"In=A0case=A0the=A0server=A0cannot=A0not=A0find=A0any=A0home=A0informatio=
n=A0neither=A0for=20
> =
=A0=A0=A0the=A0local=A0network=A0nor=A0for=A0the=A0*home=A0MSP*,=A0it=A0M=
UST=A0return=A0a=A0Home=20
> Network=20
> =A0=A0=A0Information=A0option=A0with=A0the=A00-length=A0data."=20
>=20
> =
This=A0would=A0restrict=A0HA/HoA=A0allocation=A0from=A0ASP=A0and=A0MSA=A0=
(=3Dhome=A0MSP).=A0I=20
> =
guess=A0you=A0also=A0want=A0to=A0support=A0allocation=A0from=A0MSPs=A0oth=
er=A0
> than=A0ASP=A0and=20
> =
MSA,=A0no?=A0So=A0shouldn't=A0"home=A0MSP"=A0be=A0replaced=A0by=A0"any=A0=
other=A0MSP=A0with=20
> roaming=A0relationship=A0to=A0MN's=A0MSA"?=20
>=20
> Same=A0for=A0id-type=A01:=A0section=A03.1=A0says=A0=20
>=20
>=20
> "=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0id-type=20
>=20
> =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0The=A0type=A0of=A0Home=A0Network=A0=
Identifier:=20
>=20
> =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A00=A0=A0=A0=
=A0Visited=A0domain=A0(local=A0ASP)=20
>=20
> =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A01=A0=A0=A0=
=A0Home=A0domain=A0(home=A0MSP)=20
> ....=20
> =
=A0=A0=A0Id-type=A01=A0indicates=A0the=A0mobile=A0node=A0is=A0interested=A0=
in=A0learning=A0the=20
> =
=A0=A0=A0home=A0network=A0information=A0that=A0pertains=A0to=A0the=A0give=
n=A0realm.=A0
=A0This=A0type=20
> =
=A0=A0=A0can=A0be=A0used=A0to=A0discover=A0home=A0agents=A0that=A0are=A0h=
osted=A0by=A0a=A0
> user's=A0home=20
> =
=A0=A0=A0domain=A0(as=A0indicated=A0by=A0his/her=A0NAI-based=A0username=A0=
--=A0user@=20
> =
=A0=A0=A0HomeRealm).=A0=A0The=A0Home=A0Network=A0Identifier=A0field=A0MUS=
T=A0be=A0set=A0to=A0the=20
> =A0=A0=A0target=A0home=A0MSP.=A0=A0"=20
>=20
> =
This=A0text=A0implies=A0that=A0HA/HoA=A0allocation=A0from=A0other=A0MSPs=A0=
than=A0
> home=A0MSP=20
> =
(which=A0is=A0equal=A0to=A0MSA)=A0is=A0not=A0supported=A0with=A0id-type=A0=
1,=A0even=A0
if=A0those=20
> =
MSPs=A0have=A0a=A0roaming=A0relationship=A0with=A0the=A0MN's=A0MSA.=A0Is=A0=
this=A0true?=A0=20
>=20
> Regards,=20
>=20
> Kilian=20
>=20
> >=A0=20
> =
>=A0In=A0current=A0draft,=A0the=A0server=A0is=A0supposed=A0to=A0provide=A0=
the=A0HA=A0=20
> >=A0information=A0if=A0it=A0has=20
> >=A0=20
> =
>=A0the=A0corresponding=A0information.=A0If=A0the=A0given=A0HA=A0does=A0n=
ot=A0=20
> >=A0function=A0as=A0HA=A0for=20
> >=A0=20
> =
>=A0the=A0requesting=A0MN,=A0it=A0will=A0reply=A0with=A0the=A0BA=A0status=
=A0=3D=A0132=A0or=A0133=A0=A0=20
> >=A0=20
> =
>=A0(Not=A0home=A0subnet=A0/=A0home=A0agent=A0for=A0this=A0mobile=A0node)=
=A0during=A0=20
> >=A0MN's=A0registration.=20
> >=A0=20
> >=A0=20
> =
>=A0-=A0Which=A0HA=A0information=A0should=A0the=A0MN=A0use=A0if=A0it=A0re=
ceives,=A0=20
> >=A0e.g.,=A0an=A0FQDN=A0=A0=20
> =
>=A0=A0=A0and=A0a=A0HA=A0address=A0in=A0DHCP=A0reply?=A0[HIOPT]=A0refers=A0=
to=A0section=A0
> 3.6=A0of=A0=A0=20
> >=A0=A0=A0draft-ietf-mip6-bootstrapping-integrated-01,=A0but=A0this=A0 =

> >=A0section=A0doesn't=A0=20
> =
>=A0=A0=A0exist=A0in=A0draft-ietf-mip6-bootstrapping-integrated-02=A0anym=
ore...=A0=20
> >=A0=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> =
>=A0Hiopt>>=A0It=A0is=A0within=A0the=A0MN's=A0own=A0discretion=A0as=A0fol=
lows.=A0=20
> >=A0=20
> =
>=A0I=A0don't=A0think=A0it=A0should=A0be=A0standardized=A0in=A0HIOPT=A0do=
cument.=A0=20
> >=A0=20
> =
>=A0"For=A0example,=A0if=A0the=A0mobile=A0node=A0acquires=A0both=A0IPv6=A0=
=20
> >=A0address(es)=A0and=A0FQDN(s)=20
> =
>=A0=A0of=A0the=A0home=A0agents,=A0it=A0may=A0try=A0to=A0use=A0the=A0addr=
ess=A0=20
> >=A0information=A0of=A0the=A0home=A0agent(s)=A0first."=20
> >=A0=20
> >=A0=A0=20
> >=A0=20
> >=A0=20
> >=A0Some=A0other=A0comments:=A0=20
> >=A0=20
> =
>=A0-=A0It=A0would=A0be=A0good=A0to=A0have=A0a=A0section,=A0which=A0expli=
citly=A0states=A0=A0=20
> =
>=A0=A0=A0assumptions=A0and=A0applicability=A0of=A0the=A0protocol.=A0This=
=A0
should=A0include:=A0=20
> =
>=A0=A0=A0=A0=A0-=A0MSA=A0and=A0ASA=A0must=A0be=A0co-located=A0(i.e.,=A0i=
ntegrated=A0scenario)=A0=20
> =
>=A0=A0=A0=A0=A0-=A0AAA=A0infrastructure=A0assumed=A0and=A0some=A0kind=A0=
of=A0roaming=A0=A0=20
> =
>=A0=A0=A0=A0=A0=A0=A0=A0=A0relationship=A0between=A0ASP=A0and=A0MSA/ASA=A0=
is=A0required=A0=20
> =
>=A0=A0=A0=A0=A0-=A0MSP=A0is=A0either=A0co-located=A0with=A0ASP=A0or=A0MS=
A=A0or=A0both=A0=20
> =
>=A0=A0=A0=A0=A0=A0=A0=A0=A0(Or=A0are=A0other=A0target=A0networks=A0allow=
ed;=A0see=A0above)?=A0=20
> =
>=A0=A0=A0=A0=A0-=A0DHCP=A0relay=A0and=A0NAS=A0must=A0be=A0co-located=A0 =

> >=A0=20
> =
>=A0-=A0At=A0some=A0places=A0in=A0the=A0text=A0the=A0use=A0of=A0the=A0ter=
m=A0"MSP"=A0is=A0
> ambiguous,=A0=A0=20
> =
>=A0=A0=A0since=A0MSP=A0can=A0refer=A0to=A0at=A0least=A0home=A0and=A0visi=
ted=A0network.=A0
Better=A0=A0=20
> >=A0=A0=A0use=A0"home=A0MSP"=A0for=A0MSP=A0in=A0home=A0network.=A0=20
> >=A0=A0=A0=A0=A0-=A0e.g.,=A0section=A03.1:=A0=20
> >=A0=A0=A0"Note=A0that=A0a=A0home=A0agent=A0for=A0usage=A0=20
> =
>=A0=A0=A0=A0with=A0the=A0mobile=A0node=A0might=A0be=A0selected=A0in=A0th=
e=A0access=A0service=A0=20
> =
>=A0=A0=A0=A0provider's=A0network=A0or=A0alternatively=A0in=A0the=A0*home=
*=A0
> mobility=A0service=A0=20
> >=A0=A0=A0=A0provider's=A0network."=A0=20
> >=A0=A0=A0=A0=A0-=A0or=A0in=A0section=A03.2:=A0=20
> >=A0=A0=A0"The=A0message=A0flows=A0for=A0home=A0agent=A0=20
> =
>=A0=A0=A0=A0allocation=A0in=A0the=A0ASP=A0and=A0the=A0*home*=A0MSP=A0are=
=A0illustrated=A0
> below.=A0=A0=A0=20
> >=A0=A0=A0=A0=A0-=A0or=A0in=A0section=A03.2.1:=A0=20
> =
>=A0=A0=A0"3.2.1.=A0=A0Home=A0Agent=A0allocation=A0in=A0the=A0*home*=A0MS=
P",=A0=20
> =
>=A0=A0=A0"(4)...=A0mobile=A0node=A0is=A0requesting=A0home=A0agent=A0info=
rmation=A0in=A0the=A0=A0=20
> >=A0=A0=A0*home*=A0MSP..."=A0=20
> >=A0=20
> =
>=A0-=A0Section=A03.3=A0currently=A0mentions=A0DNS-based=A0HA=A0address=A0=
=20
> >=A0discovery=A0method=A0=20
> =
>=A0=A0=A0only,=A0but=A0[BOOT-SPLIT]=A0also=A0specifies=A0an=A0anycast-ba=
sed=A0HA=A0
address=A0=A0=20
> =
>=A0=A0=A0discovery=A0method.=A0Either=A0both=A0or=A0none=A0should=A0be=A0=
mentioned.=A0=20
> >=A0=20
> =
>=A0-=A0The=A0title=A0of=A0draft-ietf-mip6-bootstrapping-integrated-02=A0=

can=A0cause=A0=A0=20
> =
>=A0=A0=A0the=A0impression=A0that=A0the=A0draft=A0defines=A0a=A0complete=A0=
bootstrapping=A0=A0=A0=20
> =
>=A0=A0=A0procedure.=A0But=A0draft-ietf-mip6-bootstrapping-integrated-02=A0=
=20
> >=A0defines=A0a=A0=A0=20
> =
>=A0=A0=A0method=A0for=A0HA=A0address=A0assignment=A0only.=A0I=A0think=A0=
this=A0is=A0
misleading.=A0=A0=20
> =
>=A0=A0=A0Why=A0not=A0name=A0the=A0draft=A0according=A0to=A0what=A0it=A0s=
pecifies=A0
> (e.g.,=A0"HA=A0=A0=20
> =
>=A0=A0=A0address=A0assignment=A0using=A0DHCP=A0and=A0AAA"=A0or=A0"HA=A0a=
ddress=A0=20
> >=A0assignment=A0for=A0=A0=20
> =
>=A0=A0=A0the=A0integrated=A0scenario=A0using=A0DHCP=A0and=A0AAA"=A0inste=
ad=A0of=A0=A0=20
> =
>=A0=A0=A0"MIP6-bootstrapping=A0for=A0the=A0integrated=A0scenario")?=A0=20
> >=A0=20
> >=A0Regards,=A0=20
> >=A0=20
> >=A0Kilian=A0=20
> >=A0=20
> >=A0>=A0-----Original=A0Message-----=A0=20
> =
>=A0>=A0From:=A0Basavaraj=A0Patil=A0[mailto:basavaraj.patil@nokia.com]=A0=
=A0=20
> >=A0>=A0Sent:=A0Mittwoch,=A014.=A0Februar=A02007=A019:10=A0=20
> >=A0>=A0To:=A0mip6@ietf.org=A0=20
> >=A0>=A0Subject:=A0[Mip6]=A0WGLC:=A0
> draft-ietf-mip6-bootstrapping-integrated-02=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0Hello,=A0=20
> >=A0>=A0=A0=20
> =
>=A0>=A0This=A0is=A0a=A0MIP6=A0Working=A0group=A0last=A0call=A0for=A0the=A0=
WG=A0I-D:=A0=20
> >=A0>=A0"MIP6-bootstrapping=A0for=A0the=A0Integrated=A0Scenario",=A0=20
> >=A0>=A0draft-ietf-mip6-bootstrapping-integrated-02.txt=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0I-D:=A0=A0=20
> =
>=A0>=A0http://ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-=A0=
=20
> >=A0>=A0integrated-dhc=A0=20
> >=A0>=A0-02.txt=A0=20
> >=A0>=A0=A0=20
> =
>=A0>=A0Please=A0review=A0and=A0submit=A0your=A0comments=A0to=A0the=A0aut=
hors=A0or=A0=20
> >=A0the=A0mailing=A0=20
> =
>=A0>=A0list.=A0The=A0WGLC=A0will=A0expire=A0on=A0March=A01st,=A007.=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0-Chairs=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0_______________________________________________=A0=20
> >=A0>=A0Mip6=A0mailing=A0list=A0=20
> >=A0>=A0Mip6@ietf.org=A0=20
> >=A0>=A0https://www1.ietf.org/mailman/listinfo/mip6=A0=20
> >=A0>=A0=A0=20
> >=A0>=A0=A0=20
> >=A0=20
> >=A0=20
> >=A0Panasonic=A0R&D=A0Center=A0Germany=A0GmbH=A0=20
> >=A063225=A0Langen,=A0Hessen,=A0Germany=A0=20
> >=A0Reg:=A0AG=A0Offenbach=A0(Hessen)=A0HRB=A033974=A0=20
> >=A0Managing=A0Director:=A0Thomas=A0Micke=A0=20
> >=A0=20
> >=A0=20
> >=A0=20
> >=A0_______________________________________________=A0=20
> >=A0Mip6=A0mailing=A0list=A0=20
> >=A0Mip6@ietf.org=A0=20
> >=A0https://www1.ietf.org/mailman/listinfo/mip6=A0=20
> >=A0=20
> >=A0=20
> >=A0=20
> >=A0=20
> >=A0=20
>=20
>=20
> Panasonic=A0R&D=A0Center=A0Germany=A0GmbH=20
> 63225=A0Langen,=A0Hessen,=A0Germany=20
> Reg:=A0AG=A0Offenbach=A0(Hessen)=A0HRB=A033974=20
> Managing=A0Director:=A0Thomas=A0Micke=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Mon Mar 05 09:52:44 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOEXp-00053F-7A; Mon, 05 Mar 2007 09:52:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOEXn-00050y-Bd
	for mip6@ietf.org; Mon, 05 Mar 2007 09:52:07 -0500
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOEXm-00046J-25
	for mip6@ietf.org; Mon, 05 Mar 2007 09:52:07 -0500
Received: by ug-out-1314.google.com with SMTP id 72so1234693ugd
	for <mip6@ietf.org>; Mon, 05 Mar 2007 06:52:05 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=U5veKePwk7MEdddDZtgyqsudotPU6Pm1Bv55CDBHSBo8+4VPF68ekzFK6O5CCUpttqNX7xwpw40RjYkZ7sZPZh24IJKxckllqiyQJNkYiB4700zGxKNwTzmdqhJdKkvw+NlMg8ch0OL0Ub+kQkm8eUc7cK0jquCqPVCB3hFEots=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=MYPmyvsypiJO4Cjyd9LBZ4rVulFM7fX+rZA/0HATBiyjskO1DmgOaXdYbhrUe7DTeN0Ejm8m2dDdHWaN1DT/eUQodAdQyINuGBoRZytMNNMhMpnHbYZO0kb88jG0aRwrImp+qomjet2pvnOvw7tg2kuORF/IayGeOtVRZu9iUyU=
Received: by 10.67.31.17 with SMTP id i17mr10865145ugj.1173106325186;
	Mon, 05 Mar 2007 06:52:05 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Mon, 5 Mar 2007 06:52:05 -0800 (PST)
Message-ID: <eaa74a7e0703050652i77e3f70dh8cf99a2793ca020d@mail.gmail.com>
Date: Mon, 5 Mar 2007 15:52:05 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Mobile IPv6 Mailing List" <mip6@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [Mip6] Review of draft-ietf-mip6-bootstrapping-integrated-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 all,

I reviewed this draft for the WGLC. I have two comments:

1) I think something is missing for the local HA assignment. In
section 3.2.2 it is stated that the AAAH assigns a HA in the home MSP
but the MN requests a HA in the ASP and the AAAH is  unaware of it.
I think that the ASP should assign a local HA to the MN only after an
indication from the AAAH that the MN is authorized to use a local HA
based on the MN's user profile. There is already a goal about this in
the AAA goals draft (G 6.4).
Therefore in step 1 of Figure 3 the AAAH must include a notification
to the NAS in case the local HA assignment is possible based on MN's
profile.

2) I think that BOOT-SPLIT is a normative reference since this draft
defines only a HA assignment mechanism and all other procedures needed
for MIP6 bootstrapping are defined in BOOT-SPLIT.

--Gerardo

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



From mip6-bounces@ietf.org Mon Mar 05 11:05:28 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOFgQ-0000XW-OD; Mon, 05 Mar 2007 11:05:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOFgP-0000XO-Hk
	for mip6@ietf.org; Mon, 05 Mar 2007 11:05:05 -0500
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOFgO-0001xH-7d
	for mip6@ietf.org; Mon, 05 Mar 2007 11:05:05 -0500
Received: by ug-out-1314.google.com with SMTP id 72so1256190ugd
	for <mip6@ietf.org>; Mon, 05 Mar 2007 08:05:03 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=QRH1pDfmEDXXhNrcHT/9cW2qYGTxiwFWrA8qXc3c8DBjyTAlZvNQkxiuVpGUe88oIrTSBRqznunwgFut4fcHqyHEK0tA3i8k7c+SHjydj3lVmz5RD0Z/PMEU7GfUdCIveTQXcmVM/6Gl4xwKxQ7hVpNhi/Qhc2acO7eMeI+mX3k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=r/r6bgAZWWonZ6Wg3Uyi1FH1l2BdU5TBsiwvlkh0GrgWULeiIjXLYxn6TMJlxnexEvJYTqavVvYDvEcs9fKkKAPf+fOaLs7UTalUMqiRTFeRntZM8DAeQ7XSuG87+b34lPjmEdkYh7mIIVxXO9AiZ+LwT/3o0jXM5F7Rt24/uYI=
Received: by 10.67.26.7 with SMTP id d7mr10985879ugj.1173110703376;
	Mon, 05 Mar 2007 08:05:03 -0800 (PST)
Received: by 10.66.238.6 with HTTP; Mon, 5 Mar 2007 08:05:03 -0800 (PST)
Message-ID: <eaa74a7e0703050805q247afb3au98d23821aca4a498@mail.gmail.com>
Date: Mon, 5 Mar 2007 17:05:03 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Mobile IPv6 Mailing List" <mip6@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Mip6] Review of draft-ietf-mip6-hiopt-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 all,

I went through draft-ietf-mip6-hiopt-02. I have two general comments
and some detailed ones.

The general comments are:

- the draft defines a way to assign the HoA via DHCP (e.g. A flag in
the Home Network Identifier Option). However, HoA assignment based on
DHCP is not introduced either in split or in integrated document. As
far as I can tell, the bootstrapping architecture defined in MIP6 WG
is based on IKEv2 HoA assignment. Also the bootstrapping document for
auth protocol does not use DHCP.
I guess that the only scenario where this HoA assignment solution may
be used is the case where the HoA is statically allocated to the MN
(e.g. in the user profile) and provided by the AAA server during
network authentication to the relay agent. If this is not the case,
which is the scenario you have in mind for HoA allocation via DHCP?
Again, the question is based on the fact that neither integrated nor
split document mentions this HoA allocation method.

- this draft defines the DHCP options for MIP6 parameters discovery in
the integrated scenario. However since there is already a companion
draft about integrated scenario architecture solution, I would suggest
to refer to it in the document and remove some text that have some
architectural description (e.g. some text in section 4.2. and 4.3).
Moreover I don't think we need to specify that the options are carried
in an Information-Request message: this draft defines the options and
the integrated draft defines how they are used.


Some detailed comments:

- I suggest to remove the reference to HMIP in the introduction. Other
solutions have been defined for MAP discovery; moreover, MAPs are
always located in the ASP and this is not the case for MIPv6 HAs.

- In section 3.1, second paragraph, I suggest to add a reference to
the integrated scenario draft and not to RADIUS attributes draft. I
think draft-ietf-mip6-hiopt-02 is a companion draft of the integrated
scenario draft that defines the architecture of the solution.
Otherwise, in case you want to keep also the reference to RADIUS,
please add a reference also to the DIME work.

- references need to be split in normative and informative

--Gerardo

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



From mip6-bounces@ietf.org Mon Mar 05 11:15:47 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOFqN-0004r0-NZ; Mon, 05 Mar 2007 11:15:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOFqM-0004qa-Fn
	for mip6@ietf.org; Mon, 05 Mar 2007 11:15:22 -0500
Received: from cluster-j.mailcontrol.com ([86.111.223.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOFqJ-0004HC-SP
	for mip6@ietf.org; Mon, 05 Mar 2007 11:15:22 -0500
Received: from rly38j.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly38j.srv.mailcontrol.com (MailControl) with ESMTP id
	l25GF3jq015367
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Mon, 5 Mar 2007 16:15:08 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly38j.srv.mailcontrol.com (MailControl) id l25GEhwe013103
	for mip6@ietf.org; Mon, 5 Mar 2007 16:14:43 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly38j-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l25GEgr3013026; Mon, 05 Mar 2007 16:14:43 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 1d7a_c4ecdbca_cb31_11db_92f3_0030482aac25;
	Mon, 05 Mar 2007 16:54:15 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030517143361-1263243 ;
	Mon, 5 Mar 2007 17:14:33 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.152,BAYES_00: -1.665,TOTAL_SCORE: -1.817
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 5 Mar 2007 17:19:31 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
In-Reply-To: <45E8A264.1070705@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
Thread-Index: AcddGCetR4q2RrWeTXO262+xF59VEQB4bBoQ
References: <4D2F935F08D41A4C8866693F4F0D7C4F01278236@lan-ex-01.panasonic.de>
	<45E760C3.5050103@azairenet.com>
	<4D2F935F08D41A4C8866693F4F0D7C4F01278515@lan-ex-01.panasonic.de>
	<45E8A264.1070705@azairenet.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F01278667@lan-ex-01.panasonic.de>
Date: Mon, 5 Mar 2007 17:11:19 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MailControl A-07-06-90 (www.mailcontrol.com) on 10.74.1.148
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
> Sent: Freitag, 2. M=E4rz 2007 23:17
> To: Kilian Weniger
> Cc: Jari Arkko; Mobile IPv6 Mailing List; James Kempf
> Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
>=20
> Kilian Weniger wrote:
>=20
>=20
> >>> There were two reasons for mandating the cookie exchange:
> >>> 1. anycast HA address is typically a single well-known and public
> >>> address, which makes it a possible target of DoS attacks.=20
> >>> 2. less impact on IKEv2 exchange, since the complete IKEv2=20
> >> exchange is
> >>> done with unicast address.
> >> In my mind, the second one was the main reason.
> >>
> >>> If nobody sees a big issue with an anycasted IKE_SA_INIT=20
> >> followed by a
> >>> unicast IKE_SA_INIT response without cookie, I'm fine=20
> with "SHOULD"
> >>> instead of "MUST" for the cookie (Vijay, from your reply it=20
> >> seems you
> >>> have concerns?). Using the cookie due to reason 1 can be left to
> >>> operator's decision IMHO.
> >> Lets get the mechanism right. I prefer not to add yet
> >> another optional mechanism. If its not needed we should
> >> remove it.
> >>
> >> The way I see it the cookie is used by the responder (the
> >> HA that sent the cookie) to tie the first IKE_SA_INIT
> >> exchange with the second one. The cookie is also used by
> >> the initiator (the mobile node) to figure out why its
> >> first IKE_SA_INIT exchange did not succeed and why it
> >> needs to do a second IKE_SA_INIT exchange.
> >=20
> > Those are reasons for having a cookie when two IKE_SA_INIT=20
> exchanges are done. I assume that we only have one=20
> IKE_SA_INIT exchange if we don't use the cookie. Then the=20
> question is whether there is a problem, when an IKE_SA_INIT=20
> *anycast* request is followed by an IKE_SA_INIT unicast=20
> response *without cookie*, followed by the usual IKE_SA_AUTH=20
> exchange etc, i.e., is there a problem with the following exchanges:
> >=20
> >         Initiator                         Responder ("best" HA)=20
> >        -----------                        ---------------------=20
> >    =20
> >        (IP_I:500 -> ANYCAST:500)=20
> >        HDR(A,0), SAi1, KEi, Ni   -->=20
> >    =20
> >                                  (IP_R:500 -> IP_I:500)=20
> >                              <-- HDR(A,B), SAr1, KEr, Nr,[CERTREQ]=20
> >=20
> >       =20
> >=20
> >        (IP_I:500 -> IP_R:500)=20
> >        HDR(A,B), SK {IDi, [CERT,] [CERTREQ,] =20
> >        [IDr,]AUTH, SAi2, TSi, TSr} -->=20
> >    =20
> >                                  (IP_R:500 -> IP_I:500)=20
> >                              <-- HDR(A,B), SK {IDr, [CERT,] AUTH,=20
> >                                                  SAr2, TSi, TSr}=20
> > 	...
>=20
> I understood what you were saying in the earlier mail
> itself. I think the cookie is necessary since it ties
> the two IKE_SA_INIT exchanges together.

I think we are talking past each other. My question was whether there =
would be a problem if we use a *single* IKE_SA_INIT exchange with =
anycasting, i.e., the initial IKE_SA_INIT request is anycasted, the =
subsequent IKE_SA_INIT unicast response doesn't contain a cookie, and =
the next exchanges are the usual IKE_AUTH, etc.


>=20
> >>     Note that this procedure requires the implementation of anycast
> >>     forwarding in such a way that the Home Agent can distinguish
> >>     between an IKE_SA_INIT forwarded through an anycast address and
> >>     one sent directly from the Mobile Node.
> >=20
> > Right. But the current text doesn't say how the IKE_SA_INIT=20
> can be forwarded and how the HA can distinguish between=20
> forwarded packets and packets coming from the MN. Since this=20
> is required for interoperability, don't we need to specify this?
>=20
> We currently have this out of scope. Do we have consensus
> on one solution?

MAC destination address replacement is problematic IMHO, since the HA =
may not be able to distinguish between forwarded and non-forwarded =
IKE_SA_INIT requests. I prefer IP tunneling, this seems to be the =
cleaner than IP destination address replacement. The HA would be able to =
identify forwarded IKE_SA_INIT requests as they are received over an IP =
tunnel.

What do others think?

>=20
> >>>> Four: What happens when the IKE SA dies or is
> >>>> deleted, but a binding for the mobile node remains
> >>>> in the selected home agent? Will the mobile node
> >>>> re-establish the IKE SA using the anycast address,
> >>>> or the address of the selected home agent?
> >>> Yes, some text should be added about that. The MN could=20
> first try to
> >>> re-establish the SA with the current HA's unicast=20
> address, as Vijay
> >>> said. But if this fails, the MN should try to find a new=20
> >> HA, e.g., by
> >>> using the anycast HA assignment.=20
> >> How about the following text?
> >>
> >>    A mobile node's security associations with its home agent may
> >>    expire while it still has a valid binding cache entry at the
> >>    the home agent.  In this case, the mobile node MUST NOT use an
> >>    anycast address as the destination address in the IKE_SA_INIT
> >>    exchange to setup new security associations.  It MUST try to
> >>    setup security associations with its existing home agent.
> >=20
> > Sounds good to me. We could additionally specify the=20
> behaviour for the case that the IKE SA dies before the=20
> lifetime expires. In this case the mobile node should try to=20
> find a new home agent IMHO:
> >=20
> >      If the security associations with the home agent die before=20
> >      they expire, e.g., because the mobile node detects that the=20
> >      peer is dead or because the peer deleted the security =20
> >      associations), the mobile node should try to bootstrap with a=20
> >      new home agent using one of the mechanisms specified in this=20
> >      document.
>=20
> I am not so sure about the second paragraph. Unless you
> know why the HA deleted the security associations, it is
> hard to recommend a particular behavior. What if the HA

I think we need to specify a behaviour, especially when there is a =
problem with one of the possible MN behaviors.=20

> deleted the security associations but not the binding
> cache entry? :)

The receiver of the anycast IKE_SA_INIT request could forward it to the =
HA with the MN's BCE, if there is an HA on the link with an active BCE =
for the MN. This of course would require that the receiver knows the =
BCEs of all HAs on the link.

Regards,

Kilian

>=20
> Vijay
>=20
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Mon Mar 05 11:17:28 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOFsO-0005vc-BC; Mon, 05 Mar 2007 11:17:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOFsM-0005tY-8r
	for mip6@ietf.org; Mon, 05 Mar 2007 11:17:26 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOFsL-0004kj-Cz
	for mip6@ietf.org; Mon, 05 Mar 2007 11:17:26 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 0B63F90092
	for <mip6@ietf.org>; Mon,  5 Mar 2007 11:17:18 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 21610-07 for <mip6@ietf.org>;
	Mon, 5 Mar 2007 11:17:13 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Mon,  5 Mar 2007 11:17:13 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 5 Mar 2007 11:17:13 -0500
Content-class: urn:content-classes:message
Subject: RE: home network requested by MN may be != assigned network (was: RE:
	[Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 5 Mar 2007 11:17:12 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA4F@exchtewks2.starentnetworks.com>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4F012785AB@lan-ex-01.panasonic.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: home network requested by MN may be != assigned network (was:
	RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
Thread-Index: AcdZUPl3RCOZHB9nQb6+3hPvBup2ywBYXBGgARQFcMAAD4CxkA==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
X-OriginalArrivalTime: 05 Mar 2007 16:17:13.0157 (UTC)
	FILETIME=[BBCBFF50:01C75F41]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 66ff42a56498684039efb58366a4b354
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, heejin.jang@samsung.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kilian,

If the MSA assigns Home Agent info in domain X which is MN's home MSP =
and the MN requests for Home Agent info for domain Y (another MSP), the =
DHCP server may not have that info. In that case, it returns a local =
Home Agent. I think this is mentioned in HIOPT I-D:

"
Id-type 1 indicates the mobile node is interested in learning the
   home network information that pertains to the given realm.  This type
   can be used to discover home agents that are hosted by a user's home
   domain (as indicated by his/her NAI-based username -- user@
   HomeRealm).  The Home Network Identifier field MUST be set to the
   target home MSP.  In case there is no available home information for
   the specified home MSP in the DHCP server, the local home information
   is provided.
"

We can clarify this in the integrated I-D as you suggested.

Thanks for your comments.

-Kuntal


> -----Original Message-----
> From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]
> Sent: Monday, March 05, 2007 3:16 AM
> To: Chowdhury, Kuntal
> Cc: heejin.jang@samsung.com; Mobile IPv6 Mailing List
> Subject: home network requested by MN may be !=3D assigned network =
(was: RE:
> [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
>=20
> Hi Kuntal, Heejin,
>=20
> since the MN's MSA is the entity that assigns a home network and an =
MSP to
> the MN, I guess that it is allowed that the MSA assigns a different =
home
> network from a different MSP to the MN than requested by the MN in the
> Home Network Identifier DHCP Option. This is needed, e.g., when the =
MSA
> doesn't have a roaming relationship with the MSP requested by the MN, =
when
> the requested MSP doesn't provide the required service (e.g., DSMIP, =
NEMO
> etc) or when the MSA knows of a better (e.g., less loaded) home =
network
> from a different MSP. I think this is currently not mentioned in the =
draft
> and it would be good to clarify.
>=20
> Regards,
>=20
> Kilian
>=20
>=20
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Dienstag, 27. Februar 2007 22:02
> > To: heejin.jang@samsung.com; Kilian Weniger
> > Cc: mip6@ietf.org; Basavaraj Patil
> > Subject: RE: RE: RE: [Mip6] WGLC:
> > draft-ietf-mip6-bootstrapping-integrated-02
> >
> > Thanks Heejin. I think your suggested clarification # 3 is good.
> >
> > -Kuntal
> >
> >
> > ________________________________________
> > From: Heejin Jang [mailto:heejin.jang@samsung.com]
> > Sent: Sunday, February 25, 2007 8:45 PM
> > To: Kilian Weniger
> > Cc: mip6@ietf.org; Basavaraj Patil
> > Subject: Re: RE: RE: [Mip6] WGLC:
> > draft-ietf-mip6-bootstrapping-integrated-02
> >
> > Hi, Kilian.
> > Thanks for the comments.
> >
> > Regarding the use of term, the draft(hiopt)=A0supports all the
> > three following networks as target networks
> > 1) ASP (MN's currently visited network)
> > 2) Home MSP (=3D MSA)
> > 3) MSP (network which is nether =A0ASP nor Home MSP but has
> > trust relationship with MN's MSA)
> >
> > The=A0term 'home MSP' can be ambiguous since it does not include 3),
> > so we will modify it to 'MSP with roaming =A0relationship with
> > MN's MSA' for more clarification.
> > Thanks.
> >
> > Regards,
> > Heejin.
> >
> > ------ Original Message -------
> > Sender : Kilian Weniger<Kilian.Weniger@eu.panasonic.com>
> > Date : 2007-02-22 23:00
> > Title : RE: RE: [Mip6] WGLC:
> > draft-ietf-mip6-bootstrapping-integrated-02
> >
> > Hi=A0Heejin,
> >
> > thanks=A0for=A0your=A0comments,=A0see=A0my=A0replies=A0inline.
> >
> > =
Please=A0note=A0that=A0the=A0comments=A0in=A0my=A0mail=A0were=A0referring=
=A0to
> > =
draft-ietf-mip6-bootstrapping-integrated-02.=A0And=A0since=A0the=A0refere=
nce
> > =
[HIOPT]=A0in=A0draft-ietf-mip6-bootstrapping-integrated-02=A0is=A0hiopt-0=
1,=A0I
> > didn't=A0consider=A0hiopt-02.
> >
> > >=A0-----Original=A0Message-----
> > >=A0From:=A0Heejin=A0Jang=A0[mailto:heejin.jang@samsung.com]
> > >=A0Sent:=A0Dienstag,=A020.=A0Februar=A02007=A008:31
> > >=A0To:=A0Kilian=A0Weniger
> > >=A0Cc:=A0Basavaraj=A0Patil;=A0mip6@ietf.org
> > >=A0Subject:=A0Re:=A0RE:=A0[Mip6]=A0WGLC:
> > >=A0draft-ietf-mip6-bootstrapping-integrated-02
> > >
> > >=A0Hi,=A0=A0Kilian=A0Weniger.
> > >
> > >=A0Thanks=A0for=A0the=A0detailedl=A0comments.
> > >
> > =
>=A0Please=A0see=A0the=A0inline=A0comments=A0for=A0the=A0HIOPT=A0draft.
> > >
> > >
> > >=A0-------=A0Original=A0Message=A0-------
> > >=A0Sender=A0:=A0Kilian=A0Weniger<Kilian.Weniger@eu.panasonic.com>
> > >=A0Date=A0:=A02007-02-16=A017:31
> > >=A0Title=A0:=A0RE:=A0[Mip6]=A0WGLC:
> > draft-ietf-mip6-bootstrapping-integrated-02
> > >
> > >=A0Hi,
> > >
> > >=A0please=A0find=A0below=A0some=A0comments=A0about
> > >=A0draft-ietf-mip6-bootstrapping-integrated-02.
> > >
> > =
>=A0The=A0draft=A0is=A0well=A0written=A0and=A0easy=A0to=A0understand=A0(t=
hanks=A0to
> > >=A0figures=A0and
> > =
>=A0message=A0sequence=A0text).=A0However,=A0some=A0details=A0and=A0corne=
r
> > >=A0cases=A0are=A0not
> > >=A0addressed,=A0which=A0may=A0need=A0to=A0be=A0specified,=A0e.g.:
> > >
> > =
>=A0-=A0How=A0does=A0the=A0NAS/relay=A0map=A0a=A0DHCP=A0request=A0receive=
d=A0from=A0a
> > >=A0specific=A0MN
> > =
>=A0=A0=A0to=A0the=A0cached=A0home=A0network=A0information=A0previously=A0=
received
> > >=A0from=A0AAAH
> > =
>=A0=A0=A0for=A0this=A0MN,=A0so=A0that=A0it=A0can=A0include=A0the=A0corre=
ct=A0home=A0network
> > >=A0=A0=A0information=A0in=A0a=A0received=A0DHCP=A0request?
> > >
> > >
> > >
> > =
>=A0Hiopt>>=A0The=A0mapping=A0mechanism=A0is=A0added=A0in=A0section=A04.3=
=A0of=A0the
> > >=A0latest=A0version=A0of=A0the=A0document=A0(hiopt-02).
> >
> > =
It=A0should=A0be=A0in=A0section=A04.2,=A0since=A0my=A0question=A0was=A0re=
lated=A0to
> the=A0DHCP
> > =
relay=A0behaviour.=A0Maybe=A0I=A0missed=A0it,=A0but=A0I=A0can't=A0see=A0a=
ny
> related=A0text=A0in
> > =
section=A04.2=A0of=A0hiopt-02=A0about=A0mapping=A0of=A0home=A0information=

> received=A0from
> > =
AAA=A0server=A0to=A0DHCP=A0request=A0received=A0from=A0MN.=A0But=A0Kuntal=

> answered=A0to=A0my
> > question=A0in=A0his=A0reply=A0email.
> >
> > >
> > =
>=A0The=A0information=A0is=A0mapped=A0based=A0on=A0NAI=A0not=A0by=A0NAS=A0=
but=A0by=A0DHCP
> > >=A0server.=A0Rrefer=A0to=A0hiopt-02=A0for=A0more=A0details.
> > >
> > >
> > =
>=A0-=A0What=A0is=A0the=A0conceptual=A0data=A0structure=A0needed=A0for=A0=
this=A0in
> > >=A0the=A0NAS/DHCP
> > >=A0=A0=A0relay?
> > =
>=A0-=A0Any=A0default=A0value=A0for=A0how=A0long=A0NAS=A0should=A0cache=A0=
home=A0network
> > =
>=A0=A0=A0information=A0received=A0from=A0AAA=A0for=A0a=A0specific=A0MN=A0=
(i.e.,
> when=A0is=A0NAS
> > =
>=A0=A0=A0allowed=A0to=A0delete=A0cache=A0entry?)?=A0If=A0this=A0is=A0spe=
cified=A0in
> > >=A0[MIP6-Dime]
> > =
>=A0=A0=A0or=A0[MIP6-RADIUS]=A0it=A0should=A0be=A0mentioned=A0and=A0refer=
enced.
> > >
> > =
>=A0Hiopt>>=A0This=A0is=A0implementation-specific.=A0I'm=A0not=A0sure=A0w=
e=A0need
> > >=A0to=A0describe=A0down=A0to=A0the=A0smallest=A0detail.
> >
> > =
A=A0value=A0doesn't=A0need=A0to=A0be=A0mandated,=A0but=A0I=A0think=A0some=
=A0guidance=A0to=A0the
> > implementor=A0would=A0be=A0good.
> >
> > >
> > >
> > =
>=A0-=A0What=A0should=A0NAS=A0do=A0if=A0DHCP=A0request=A0with=A0Home=A0ne=
twork=A0identifier
> > =
>=A0=A0=A0option=A0is=A0received=A0from=A0a=A0MN=A0and=A0NAS=A0doesn't=A0=
find=A0valid
> > >=A0home=A0network
> > =
>=A0=A0=A0information=A0for=A0this=A0MN=A0in=A0its=A0cache=A0(e.g.,=A0sin=
ce=A0the
> cache=A0entry
> > >=A0=A0=A0has=A0expired)?
> > >
> > >
> > >
> > =
>=A0Hiopt>>In=A0that=A0case,=A0there=A0is=A0nothing=A0NAS=A0can=A0do.=A0I=
f=A0the
> > >=A0corresponding=A0information
> > >
> > >=A0is=A0configured=A0on=A0the=A0DHCP=A0server=A0(for=A0e.g.,
> > >=A0pre-configuration),=A0the=A0server=A0will
> > =
>=A0provide=A0it.=A0Otherwise,=A0it=A0will=A0reply=A0with=A00-lengh=A0opt=
ion.
> >
> > =
ok.=A0My=A0comment=A0was=A0that=A0this=A0should=A0be=A0documented=A0(i.e.=
,=A0DHCP=A0server
> > must=A0reply=A0with=A00-lengh=A0option=A0in=A0this=A0case)
> >
> > >
> > >
> > =
>=A0-=A0What=A0should=A0DHCP=A0relay/server=A0do=A0if=A0the=A0MN=A0does=A0=
not=A0include=A0the
> > >=A0=A0=A0OPTION_CLIENTID=A0in=A0the=A0DHCP=A0request=A0or=A0if
> > OPTION_MIP6-RELAY-Option
> > >=A0=A0=A0is=A0missing=A0in=A0request?
> > >
> > >
> > >
> > >
> > =
>=A0Hiopt>>=A0The=A0existing=A0DHCP=A0options=A0are=A0handled=A0according=
=A0to
> > [RFC=A03315].
> > >
> > =
>=A0The=A0request=A0not=A0including=A0OPTION_CLIENTID=A0is=A0discarded=A0=
in=A0the
> > >=A0relay/server
> > >
> > >=A0as=A0described=A0in=A015.4=A0of=A0[RFC=A03315].
> >
> > ok.
> >
> > >
> > >
> > =
>=A0The=A0draft=A0may=A0need=A0better=A0aligned=A0with=A0[HIOPT].=A0For=A0=
instance,
> > >=A0it=A0is=A0not
> > =
>=A0clear=A0to=A0me=A0how=A0exactly=A0the=A0home=A0network=A0identifier=A0=
option
> > >=A0and=A0the=A0home
> > =
>=A0network=A0information=A0option=A0specified=A0in=A0[HIOPT]=A0are=A0all=
owed
> > >=A0to=A0be=A0used
> > >=A0in=A0draft-ietf-mip6-bootstrapping-integrated-02:
> > >
> > =
>=A0-=A0[HIOPT]=A0supports=A0home=A0address=A0allocation.=A0This=A0is=A0n=
ot
> mentioned=A0in
> > >=A0=A0=A0draft-ietf-mip6-bootstrapping-integrated-02.=A0Is=A0this
> forbidden=A0or
> > =
>=A0=A0=A0allowed=A0or=A0out-of-scope?=A0If=A0allowed,=A0when=A0does=A0NA=
S=A0set=A0the
> > >=A0A-flag=A0in
> > >=A0=A0=A0the=A0home=A0network=A0identifier=A0option?
> > >
> > >
> > >
> > =
>=A0Hiopt>>=A0NAS=A0SHOULD=A0not=A0modify=A0the=A0Home=A0Network=A0Identi=
fier=A0option.
> > =
>=A0The=A0A-flag=A0is=A0set=A0to=A00/1=A0only=A0by=A0the=A0mobile=A0node.=
=A0If=A0there=A0is
> > >=A0home=A0address
> > =
>=A0information=A0at=A0NAS=A0that=A0was=A0acquired=A0during=A0AAA=A0trans=
action,
> > >=A0it=A0is=A0delivered
> > =
>=A0to=A0the=A0DHCP=A0server=A0with=A0MIP6-Relay=A0option.=A0(Refer=A0hio=
pt-02.txt)
> >
> > =
I=A0was=A0aware=A0of=A0HoA=A0allocation=A0support=A0in=A0[HIOPT].=A0My=A0=
question=A0was
> > whether=A0it=A0is=A0supported=A0in
> > draft-ietf-mip6-bootstrapping-integrated-02
> > =
as=A0well,=A0since=A0HoA=A0allocation=A0is=A0not=A0mentioned=A0there.
> >
> > >
> > >
> > =
>=A0-=A0Is=A0it=A0allowed=A0that=A0multiple=A0HA=A0addresses=A0are=A0retu=
rned=A0in
> > the=A0home
> > >=A0=A0=A0network=A0information=A0option?
> > >
> > >
> > >
> > =
>=A0Hiopt>>=A0It=A0is=A0allowed=A0by=A0using=A0multiple=A0home=A0network
> > >=A0information=A0option.
> > >
> > =
>=A0=A0=A0"Multiple=A0sub-options=A0may=A0exist=A0in=A0a=A0Home=A0Network=

> Information=A0option
> > >
> > =
>=A0=A0=A0=A0to=A0carry=A0more=A0than=A0one=A0home=A0information."=A0(in=A0=
section=A03.3.1)
> > >
> > >
> > =
>=A0-=A0[HIOPT]=A0allows=A0that=A0the=A0home=A0network=A0identifier=A0opt=
ion
> > includes=A0an
> > =
>=A0=A0=A0identifier=A0of=A0a=A0target=A0network,=A0which=A0is=A0differen=
t=A0from=A0home=A0or
> > =
>=A0=A0=A0visited=A0network=A0of=A0MN.=A0This=A0is=A0not=A0mentioned=A0in=

> > =
>=A0=A0=A0draft-ietf-mip6-bootstrapping-integrated-02.=A0Is=A0this=A0allo=
wed=A0or
> > >=A0=A0=A0forbidden?
> > >
> > >
> > >
> > =
>=A0Hiopt>>=A0A=A0target=A0network=A0may=A0or=A0may=A0not=A0be=A0home=A0n=
etwork=A0of
> > the=A0MN.
> >
> > =
good.=A0I=A0guess=A0"home=A0network"=A0means=A0"home=A0MSP"=A0in=A0this=A0=
case,=A0right?
> > =
According=A0to=A0RFC4640,=A0the=A0"home=A0MSP"=A0is=A0MN's=A0MSA=A0provid=
ing=A0mobility
> > service=A0to=A0MN.
> > =
According=A0to=A0Kuntal's=A0comment,=A0also=A0MSPs=A0other=A0than=A0MSA=A0=
(or
> "home=A0MSP")
> > =
and=A0ASP=A0are=A0supported=A0as=A0target=A0networks.=A0If=A0this=A0is=A0=
true=A0for
> hiopt=A0(and
> > it=A0should=A0be=A0if=A0it=A0is=A0true=A0for
> > =
draft-ietf-mip6-bootstrapping-integrated-02),=A0then=A0it=A0seems=A0that=A0=
the
> > =
hiopt=A0draft=A0also=A0uses=A0the=A0term=A0"home=A0MSP"=A0differently=A0t=
han=A0defined=A0in
> > =
RFC4640.=A0For=A0instance,=A0section=A04.3,=A0case=A0C=A0(id-type=A02)=A0=
says
> >
> > =
"In=A0case=A0the=A0server=A0cannot=A0not=A0find=A0any=A0home=A0informatio=
n=A0neither=A0for
> > =
=A0=A0=A0the=A0local=A0network=A0nor=A0for=A0the=A0*home=A0MSP*,=A0it=A0M=
UST=A0return=A0a=A0Home
> > Network
> > =A0=A0=A0Information=A0option=A0with=A0the=A00-length=A0data."
> >
> > =
This=A0would=A0restrict=A0HA/HoA=A0allocation=A0from=A0ASP=A0and=A0MSA=A0=
(=3Dhome=A0MSP).=A0I
> > =
guess=A0you=A0also=A0want=A0to=A0support=A0allocation=A0from=A0MSPs=A0oth=
er
> > than=A0ASP=A0and
> > =
MSA,=A0no?=A0So=A0shouldn't=A0"home=A0MSP"=A0be=A0replaced=A0by=A0"any=A0=
other=A0MSP=A0with
> > roaming=A0relationship=A0to=A0MN's=A0MSA"?
> >
> > Same=A0for=A0id-type=A01:=A0section=A03.1=A0says
> >
> >
> > "=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0id-type
> >
> > =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0The=A0type=A0of=A0Home=A0Network=A0=
Identifier:
> >
> > =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A00=A0=A0=A0=
=A0Visited=A0domain=A0(local=A0ASP)
> >
> > =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A01=A0=A0=A0=
=A0Home=A0domain=A0(home=A0MSP)
> > ....
> > =
=A0=A0=A0Id-type=A01=A0indicates=A0the=A0mobile=A0node=A0is=A0interested=A0=
in=A0learning=A0the
> > =
=A0=A0=A0home=A0network=A0information=A0that=A0pertains=A0to=A0the=A0give=
n=A0realm.
> =A0This=A0type
> > =
=A0=A0=A0can=A0be=A0used=A0to=A0discover=A0home=A0agents=A0that=A0are=A0h=
osted=A0by=A0a
> > user's=A0home
> > =
=A0=A0=A0domain=A0(as=A0indicated=A0by=A0his/her=A0NAI-based=A0username=A0=
--=A0user@
> > =
=A0=A0=A0HomeRealm).=A0=A0The=A0Home=A0Network=A0Identifier=A0field=A0MUS=
T=A0be=A0set=A0to=A0the
> > =A0=A0=A0target=A0home=A0MSP.=A0=A0"
> >
> > =
This=A0text=A0implies=A0that=A0HA/HoA=A0allocation=A0from=A0other=A0MSPs=A0=
than
> > home=A0MSP
> > =
(which=A0is=A0equal=A0to=A0MSA)=A0is=A0not=A0supported=A0with=A0id-type=A0=
1,=A0even
> if=A0those
> > =
MSPs=A0have=A0a=A0roaming=A0relationship=A0with=A0the=A0MN's=A0MSA.=A0Is=A0=
this=A0true?
> >
> > Regards,
> >
> > Kilian
> >
> > >
> > =
>=A0In=A0current=A0draft,=A0the=A0server=A0is=A0supposed=A0to=A0provide=A0=
the=A0HA
> > >=A0information=A0if=A0it=A0has
> > >
> > =
>=A0the=A0corresponding=A0information.=A0If=A0the=A0given=A0HA=A0does=A0n=
ot
> > >=A0function=A0as=A0HA=A0for
> > >
> > =
>=A0the=A0requesting=A0MN,=A0it=A0will=A0reply=A0with=A0the=A0BA=A0status=
=A0=3D=A0132=A0or=A0133
> > >
> > =
>=A0(Not=A0home=A0subnet=A0/=A0home=A0agent=A0for=A0this=A0mobile=A0node)=
=A0during
> > >=A0MN's=A0registration.
> > >
> > >
> > =
>=A0-=A0Which=A0HA=A0information=A0should=A0the=A0MN=A0use=A0if=A0it=A0re=
ceives,
> > >=A0e.g.,=A0an=A0FQDN
> > =
>=A0=A0=A0and=A0a=A0HA=A0address=A0in=A0DHCP=A0reply?=A0[HIOPT]=A0refers=A0=
to=A0section
> > 3.6=A0of
> > >=A0=A0=A0draft-ietf-mip6-bootstrapping-integrated-01,=A0but=A0this
> > >=A0section=A0doesn't
> > =
>=A0=A0=A0exist=A0in=A0draft-ietf-mip6-bootstrapping-integrated-02=A0anym=
ore...
> > >
> > >
> > >
> > >
> > =
>=A0Hiopt>>=A0It=A0is=A0within=A0the=A0MN's=A0own=A0discretion=A0as=A0fol=
lows.
> > >
> > =
>=A0I=A0don't=A0think=A0it=A0should=A0be=A0standardized=A0in=A0HIOPT=A0do=
cument.
> > >
> > =
>=A0"For=A0example,=A0if=A0the=A0mobile=A0node=A0acquires=A0both=A0IPv6
> > >=A0address(es)=A0and=A0FQDN(s)
> > =
>=A0=A0of=A0the=A0home=A0agents,=A0it=A0may=A0try=A0to=A0use=A0the=A0addr=
ess
> > >=A0information=A0of=A0the=A0home=A0agent(s)=A0first."
> > >
> > >
> > >
> > >
> > >=A0Some=A0other=A0comments:
> > >
> > =
>=A0-=A0It=A0would=A0be=A0good=A0to=A0have=A0a=A0section,=A0which=A0expli=
citly=A0states
> > =
>=A0=A0=A0assumptions=A0and=A0applicability=A0of=A0the=A0protocol.=A0This=

> should=A0include:
> > =
>=A0=A0=A0=A0=A0-=A0MSA=A0and=A0ASA=A0must=A0be=A0co-located=A0(i.e.,=A0i=
ntegrated=A0scenario)
> > =
>=A0=A0=A0=A0=A0-=A0AAA=A0infrastructure=A0assumed=A0and=A0some=A0kind=A0=
of=A0roaming
> > =
>=A0=A0=A0=A0=A0=A0=A0=A0=A0relationship=A0between=A0ASP=A0and=A0MSA/ASA=A0=
is=A0required
> > =
>=A0=A0=A0=A0=A0-=A0MSP=A0is=A0either=A0co-located=A0with=A0ASP=A0or=A0MS=
A=A0or=A0both
> > =
>=A0=A0=A0=A0=A0=A0=A0=A0=A0(Or=A0are=A0other=A0target=A0networks=A0allow=
ed;=A0see=A0above)?
> > =
>=A0=A0=A0=A0=A0-=A0DHCP=A0relay=A0and=A0NAS=A0must=A0be=A0co-located
> > >
> > =
>=A0-=A0At=A0some=A0places=A0in=A0the=A0text=A0the=A0use=A0of=A0the=A0ter=
m=A0"MSP"=A0is
> > ambiguous,
> > =
>=A0=A0=A0since=A0MSP=A0can=A0refer=A0to=A0at=A0least=A0home=A0and=A0visi=
ted=A0network.
> Better
> > >=A0=A0=A0use=A0"home=A0MSP"=A0for=A0MSP=A0in=A0home=A0network.
> > >=A0=A0=A0=A0=A0-=A0e.g.,=A0section=A03.1:
> > >=A0=A0=A0"Note=A0that=A0a=A0home=A0agent=A0for=A0usage
> > =
>=A0=A0=A0=A0with=A0the=A0mobile=A0node=A0might=A0be=A0selected=A0in=A0th=
e=A0access=A0service
> > =
>=A0=A0=A0=A0provider's=A0network=A0or=A0alternatively=A0in=A0the=A0*home=
*
> > mobility=A0service
> > >=A0=A0=A0=A0provider's=A0network."
> > >=A0=A0=A0=A0=A0-=A0or=A0in=A0section=A03.2:
> > >=A0=A0=A0"The=A0message=A0flows=A0for=A0home=A0agent
> > =
>=A0=A0=A0=A0allocation=A0in=A0the=A0ASP=A0and=A0the=A0*home*=A0MSP=A0are=
=A0illustrated
> > below.
> > >=A0=A0=A0=A0=A0-=A0or=A0in=A0section=A03.2.1:
> > =
>=A0=A0=A0"3.2.1.=A0=A0Home=A0Agent=A0allocation=A0in=A0the=A0*home*=A0MS=
P",
> > =
>=A0=A0=A0"(4)...=A0mobile=A0node=A0is=A0requesting=A0home=A0agent=A0info=
rmation=A0in=A0the
> > >=A0=A0=A0*home*=A0MSP..."
> > >
> > =
>=A0-=A0Section=A03.3=A0currently=A0mentions=A0DNS-based=A0HA=A0address
> > >=A0discovery=A0method
> > =
>=A0=A0=A0only,=A0but=A0[BOOT-SPLIT]=A0also=A0specifies=A0an=A0anycast-ba=
sed=A0HA
> address
> > =
>=A0=A0=A0discovery=A0method.=A0Either=A0both=A0or=A0none=A0should=A0be=A0=
mentioned.
> > >
> > =
>=A0-=A0The=A0title=A0of=A0draft-ietf-mip6-bootstrapping-integrated-02
> can=A0cause
> > =
>=A0=A0=A0the=A0impression=A0that=A0the=A0draft=A0defines=A0a=A0complete=A0=
bootstrapping
> > =
>=A0=A0=A0procedure.=A0But=A0draft-ietf-mip6-bootstrapping-integrated-02
> > >=A0defines=A0a
> > =
>=A0=A0=A0method=A0for=A0HA=A0address=A0assignment=A0only.=A0I=A0think=A0=
this=A0is
> misleading.
> > =
>=A0=A0=A0Why=A0not=A0name=A0the=A0draft=A0according=A0to=A0what=A0it=A0s=
pecifies
> > (e.g.,=A0"HA
> > =
>=A0=A0=A0address=A0assignment=A0using=A0DHCP=A0and=A0AAA"=A0or=A0"HA=A0a=
ddress
> > >=A0assignment=A0for
> > =
>=A0=A0=A0the=A0integrated=A0scenario=A0using=A0DHCP=A0and=A0AAA"=A0inste=
ad=A0of
> > >=A0=A0=A0"MIP6-bootstrapping=A0for=A0the=A0integrated=A0scenario")?
> > >
> > >=A0Regards,
> > >
> > >=A0Kilian
> > >
> > >=A0>=A0-----Original=A0Message-----
> > =
>=A0>=A0From:=A0Basavaraj=A0Patil=A0[mailto:basavaraj.patil@nokia.com]
> > >=A0>=A0Sent:=A0Mittwoch,=A014.=A0Februar=A02007=A019:10
> > >=A0>=A0To:=A0mip6@ietf.org
> > >=A0>=A0Subject:=A0[Mip6]=A0WGLC:
> > draft-ietf-mip6-bootstrapping-integrated-02
> > >=A0>
> > >=A0>
> > >=A0>=A0Hello,
> > >=A0>
> > =
>=A0>=A0This=A0is=A0a=A0MIP6=A0Working=A0group=A0last=A0call=A0for=A0the=A0=
WG=A0I-D:
> > >=A0>=A0"MIP6-bootstrapping=A0for=A0the=A0Integrated=A0Scenario",
> > >=A0>=A0draft-ietf-mip6-bootstrapping-integrated-02.txt
> > >=A0>
> > >=A0>=A0I-D:
> > =
>=A0>=A0http://ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-
> > >=A0>=A0integrated-dhc
> > >=A0>=A0-02.txt
> > >=A0>
> > =
>=A0>=A0Please=A0review=A0and=A0submit=A0your=A0comments=A0to=A0the=A0aut=
hors=A0or
> > >=A0the=A0mailing
> > >=A0>=A0list.=A0The=A0WGLC=A0will=A0expire=A0on=A0March=A01st,=A007.
> > >=A0>
> > >=A0>=A0-Chairs
> > >=A0>
> > >=A0>
> > >=A0>=A0_______________________________________________
> > >=A0>=A0Mip6=A0mailing=A0list
> > >=A0>=A0Mip6@ietf.org
> > >=A0>=A0https://www1.ietf.org/mailman/listinfo/mip6
> > >=A0>
> > >=A0>
> > >
> > >
> > >=A0Panasonic=A0R&D=A0Center=A0Germany=A0GmbH
> > >=A063225=A0Langen,=A0Hessen,=A0Germany
> > >=A0Reg:=A0AG=A0Offenbach=A0(Hessen)=A0HRB=A033974
> > >=A0Managing=A0Director:=A0Thomas=A0Micke
> > >
> > >
> > >
> > >=A0_______________________________________________
> > >=A0Mip6=A0mailing=A0list
> > >=A0Mip6@ietf.org
> > >=A0https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> > >
> > >
> > >
> >
> >
> > Panasonic=A0R&D=A0Center=A0Germany=A0GmbH
> > 63225=A0Langen,=A0Hessen,=A0Germany
> > Reg:=A0AG=A0Offenbach=A0(Hessen)=A0HRB=A033974
> > Managing=A0Director:=A0Thomas=A0Micke
> >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
>=20
>=20
> Panasonic R&D Center Germany GmbH
> 63225 Langen, Hessen, Germany
> Reg: AG Offenbach (Hessen) HRB 33974
> Managing Director: Thomas Micke
>=20


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



From mip6-bounces@ietf.org Mon Mar 05 11:30:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOG4F-0000Oy-R2; Mon, 05 Mar 2007 11:29:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOG4E-0000Og-5v
	for mip6@ietf.org; Mon, 05 Mar 2007 11:29:42 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOG49-0007l0-PW
	for mip6@ietf.org; Mon, 05 Mar 2007 11:29:42 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 8728D900CE
	for <mip6@ietf.org>; Mon,  5 Mar 2007 11:29:34 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 21740-12 for <mip6@ietf.org>;
	Mon, 5 Mar 2007 11:29:30 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Mon,  5 Mar 2007 11:29:30 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 5 Mar 2007 11:29:30 -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] Review of draft-ietf-mip6-bootstrapping-integrated-02
Date: Mon, 5 Mar 2007 11:29:29 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA50@exchtewks2.starentnetworks.com>
In-Reply-To: <eaa74a7e0703050652i77e3f70dh8cf99a2793ca020d@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Review of draft-ietf-mip6-bootstrapping-integrated-02
Thread-Index: AcdfNiJswHoUcMhCQVmLqDJiumUMwwAC9jMQ
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 05 Mar 2007 16:29:30.0027 (UTC)
	FILETIME=[73016FB0:01C75F43]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 1.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

Hi Gerardo,

Thanks for your review and comments. Please see inline....

> -----Original Message-----
> From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> Sent: Monday, March 05, 2007 8:52 AM
> To: Mobile IPv6 Mailing List
> Subject: [Mip6] Review of draft-ietf-mip6-bootstrapping-integrated-02
>=20
> Hi all,
>=20
> I reviewed this draft for the WGLC. I have two comments:
>=20
> 1) I think something is missing for the local HA assignment. In
> section 3.2.2 it is stated that the AAAH assigns a HA in the home MSP
> but the MN requests a HA in the ASP and the AAAH is  unaware of it.
> I think that the ASP should assign a local HA to the MN only after an
> indication from the AAAH that the MN is authorized to use a local HA
> based on the MN's user profile. There is already a goal about this in
> the AAA goals draft (G 6.4).
> Therefore in step 1 of Figure 3 the AAAH must include a notification
> to the NAS in case the local HA assignment is possible based on MN's
> profile.
>=20
[KC>] I agree with your comment. In fact this has been discussed w.r.t
the Dime I-D for the AAA part. Basically the ASP includes an Home Agent
information that it will assign to the MN if the MSA authorizes local HA
assignment and if the MN requests for a local HA. Please see section 6.3
in :=20
http://www.tschofenig.com/svn/draft-ietf-dime-mip6-integrated/draft-ietf
-dime-mip6-integrated-04.txt

This is a further update based on comments received so far. It will be
posted as soon as the I-D submission gate opens again. We will add
similar clarification in the RADIUS I-D as well. The step 1 in this
(integrated I-D) will be updated as well.


> 2) I think that BOOT-SPLIT is a normative reference since this draft
> defines only a HA assignment mechanism and all other procedures needed
> for MIP6 bootstrapping are defined in BOOT-SPLIT.
>=20
[KC>] I agree. We will make that change.

> --Gerardo
>=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 Mon Mar 05 16:47:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOL0x-0002jp-I3; Mon, 05 Mar 2007 16:46:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOL0t-0002fe-Fj; Mon, 05 Mar 2007 16:46:35 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HOL0j-0007Kz-Ku; Mon, 05 Mar 2007 16:46:35 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 758FF26E5D;
	Mon,  5 Mar 2007 21:46:25 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HOL0j-0001oi-Bz; Mon, 05 Mar 2007 16:46:25 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1HOL0j-0001oi-Bz@stiedprstage1.ietf.org>
Date: Mon, 05 Mar 2007 16:46:25 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: mip6 mailing list <mip6@ietf.org>, mip6 chair <mip6-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Mip6] Document Action: 'IP Address Location Privacy and 
 Mobile IPv6: Problem Statement' to Informational RFC 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

The IESG has approved the following document:

- 'IP Address Location Privacy and Mobile IPv6: Problem Statement '
   <draft-ietf-mip6-location-privacy-ps-06.txt> as an Informational RFC

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

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-location-privacy-ps-06.txt

Technical Summary
 
  This document discusses Location Privacy as applicable to
  Mobile IPv6.  We document the concerns arising from revealing Home
  Address to an on-looker and from disclosing Care of Address to a
  correspondent.
 
Working Group Summary

  This document was done in collaboration with the Mobopts
  research group. No specific concerns or issues were raised
  during the WG LC. The document has also been presented and
  discussed at the MIP6 WG meetings.

Protocol Quality
 
  This specification has been reviewed by Jari Arkko for
  the IESG, and Gopal Dommety for the WG. The document 
  is only capturing issues associated with location 
  privacy and does not specify a new protocol. Hence
  there is no implementation experience.


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



From mip6-bounces@ietf.org Mon Mar 05 22:15:19 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOQ7l-00011s-Oj; Mon, 05 Mar 2007 22:14:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOQ7k-0000u8-6h
	for mip6@ietf.org; Mon, 05 Mar 2007 22:14:00 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOQ7j-0008Mh-FN
	for mip6@ietf.org; Mon, 05 Mar 2007 22:14:00 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l263DvYo019263
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Mar 2007 19:13:58 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l263Dv4Y025666; Mon, 5 Mar 2007 19:13:57 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 19:13:56 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Mon, 5 Mar 2007 19:13:56 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325134F21CC@NAEX13.na.qualcomm.com>
In-Reply-To: <0MKoyl-1HN5tp2CnW-0008U8@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5gALaqrpA=
References: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
	<0MKoyl-1HN5tp2CnW-0008U8@mrelay.perfora.net>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 06 Mar 2007 03:13:56.0947 (UTC)
	FILETIME=[7A493230:01C75F9D]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 79bb66f827e54e9d5c5c7f1f9d645608
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 Alper,
Please see inline. =20

> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Sent: Friday, March 02, 2007 3:26 AM
> To: Narayanan, Vidya; 'Mobile IPv6 Mailing List'
> Subject: RE: [Mip6] WGLC: Review=20
> ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
>=20
> Hi Vidya,
>=20
> Thank you for the review and feedback.
>=20
> > 1. The title of the document should be changed to reflect the real=20
> > solution provided - something along the lines of "Dynamic MIP6 Home=20
> > Agent Discovery using AAA and DHCP" would be more appropriate. The=20
> > current title seems to indicate that the document is providing a=20
> > complete MIP6 bootstrapping solution, which is not the case. Also,=20
> > this solution does not function without AAA, hence, it is not a=20
> > solution that employs DHCP alone.
>=20
> The complete solution also includes IKEv2.
> So, either we should state all components of the solution in=20
> the title, or none. I think "none" is better, along the lines=20
> of what we did for the split scenario.
>=20

It was just a suggestion. I see your point about the split scenario
document also. In a way, both documents could be titled more
appropriately I guess :)

>=20
> > 2. The assumptions made by this solution must be stated in=20
> a separate=20
> > section (perhaps under introduction?). I think Kilian had a=20
> reasonable=20
> > list in one of his emails. The assumptions are currently scattered=20
> > throughout the document and this is not entirely clear. So,=20
> > collectively listing that would be good.
>=20
> Good idea.
>=20
>=20
> >=20
> > 3. The method by which the DHCP Relay maintains the mapping of the=20
> > Home Agent and corresponding mobile node is unclear. At the end of=20
> > network access authentication, it is assumed that the HA address is=20
> > sent to the NAS/DHCP Relay. Subsequently, when the MN=20
> attempts to use=20
> > DHCP to obtain the HA address, the Relay agent must be able to=20
> > associate the incoming request with the appropriate HA that was=20
> > assigned. There is no assumption on the client ID used in the DHCP=20
> > message to be of any use in this respect and that makes sense.=20
> > However, the use of a link layer address to maintain such a=20
> mapping is=20
> > problematic. For one, link layer addresses may be easily spoofed,=20
> > causing the wrong HA address to be sent to the MN. Further, link=20
> > visibility at the NAS, while feasible sometimes, may not be=20
> always available.
>=20
> This is a generic issue with the RFC4014, which we are simply=20
> using not defining. We can discuss this on a separate thread=20
> in DHC mailing list if you like.
>=20

Thanks for the reference here. I quickly scanned RFC4014 and it seems to
have no description of how the attributes received via RADIUS may be
linked with the DHCP request coming from a client. Did I miss it? In any
case, I agree that we need to discuss this in the context of RFC4014,
but, I'm concerned about ambiguity caused by the reference not having
sufficient information.=20

>=20
> >=20
> > 4. The security considerations section is confusing to me. In
> > particular:
> >=20
> >    - The first paragraph states "No new security considerations are=20
> > imposed by the usage of this document.  The security mechanisms=20
> > provided by [RFC2865] and [RFC3588] are applicable and provide=20
> > adequate security for this purpose." This indicates that the=20
> > requirements for AAA transport security are the same as=20
> that for MIP6=20
> > HA discovery. This is not quite true - depending on what=20
> information=20
> > is transported in AAA and the sensitivity of it, the=20
> requirements are=20
> > different. For instance, keys transported using AAA will need to be=20
> > encrypted and integrity protected, while, HA information=20
> may only need integrity protection.
> > Hence, first stating the requirements and then stating that RADIUS=20
> > and/or Diameter security is sufficient would be good.
>=20
> Good idea.
>=20
>=20
> >=20
> >    - The next paragraph states "The communication between=20
> the NAS/DHCP=20
> > relay agent to the DHCP server must be authenticated, integrity and=20
> > replay protected.  Deployments MAY either rely on lower-layer=20
> > security, (i.e., physical or link layer security), or rely=20
> on security=20
> > mechanisms specifically defined for DHCPv6, such as [RFC4030]." The=20
> > first sentence seems to be inconsistent with the next one.
>=20
> You are right. It should read "MUST", not "MAY".
>=20
> > For one, it is necessary to
> > state if the protection needed is end-to-end between the=20
> relay agent=20
> > and the server.
>=20
> Yes it is. And we can state that.
>=20
> > Next, I don't see how physical security can provide=20
> authentication or=20
> > replay protection.
>=20
> I don't think use of RFC 4030 is mandatory. Deployments are=20
> free to use physical security instead of RFC 4030. This,=20
> again, is not a specific issue for our I-D. If you like, we=20
> can discuss this under another thread.
>=20

Well, if we say that use of RFC4030 is not mandatory, we should then not
be mandating channel security, right? Or, perhaps I am misunderstanding
what you mean by "physical security"... =20


> >=20
> >    - The following paragraph states a similar requirement=20
> between the=20
> > DHCP client and server. But then it goes on to say that either=20
> > link-layer security or DHCP security may be used.=20
> Link-layer security=20
> > in this case, is incapable of providing the stated security=20
> "between=20
> > the DHCP client and server". It would only provide the security=20
> > between the client and the access enforcement point. Also, I'm not=20
> > sure what it means to say that such security is "required". For=20
> > instance, if a particular technology decided to use no message=20
> > authentication at the link layer, can this method of=20
> bootstrapping not=20
> > be used? I don't think that is the intention, but, it needs=20
> to be clarified.
>=20
> I think trying to explain DHCP security is getting us into=20
> trouble. I would really want to say in this document "DHCP is=20
> secured however it is secured"
> :-) People can start discussing DHCP security in general. But=20
> that does not take anything away from the use of DHCP,=20
> especially the way we are using -- standard.=20
>=20
> Would you agree we should reduce this whole discussion about=20
> DHCP security?
>=20

More or less, yes :) If the additional information that we want DHCP to
carry is more sensitive compared to the normal DHCP attributes, then, it
is fine to say that DHCP security may or may not be used depending on
the deployment and that is fine. In the case of HA assignment, I think
that is true. So, we should not make a statement that implies that some
kind of security between the DHCP client and server is "required".=20

>=20
>=20
> >=20
> >    - The next paragraph states, "An adversary that is able=20
> to modify=20
> > home agent information can force the mobile node to use a different=20
> > home agent than intended by the MSA.  However, this type of=20
> attack can=20
> > be detected by the security mechanism between the mobile=20
> node and the=20
> > home agent." I'm not sure how this attack is detectable by the=20
> > security mechanism between the MN and HA - it may be detectable if=20
> > IKEv2 PSKs are used between the MN and HA. If IKEv2 with=20
> EAP is used,=20
> > as long as the HA is able to act as an EAP authenticator=20
> and get the=20
> > MN authenticated via the AAA server and obtain an MSK, it=20
> doesn't seem to be detectable.
>=20
> Not "any" HA on the Internet can act as a pass-through=20
> authenticator and talk to the home AAA server of the MN. We=20
> shall clarify that in the text.
>=20

Okay.=20

> > In
> > that case, the AAA server wouldn't be able to tell the difference=20
> > between this and any other EAP exchange. It is then only=20
> detectable if=20
> > the AAA server policy prevents use of that HA as an authenticator.
>=20
> Yes, and it should. A AAA server would not be passing MSKs to=20
> any one how happens to forward EAP traffic.
>=20

Yes, but, this would still mean that the AAA server cannot tell the
difference between a HA it explicitly meant to assign and a different HA
that is also allowed to be an EAP authenticator. In other words, there
is no check here to see if the EAP authenticator is the same as the HA
that the AAA meant to assign to the MN. This may lead to the AAA server
assuming that the MN is served by one HA, when, it is really served by a
different HA.=20

>=20
>=20
> >=20
> >    - The section currently states, "If the home agent=20
> selected by the=20
> > mobile node is local or nearby, (as in section 3.2.2),=20
> disclosing the=20
> > mobile node's home address (e.g., by updating the mobile=20
> node's FQDN=20
> > in the DNS) has the potential to expose some information about the=20
> > mobile node's location." I don't understand the intended=20
> implication=20
> > here. How is this different from an HA in the MSP=20
> performing the DNS update?
>=20
> I'd not mind removing this text.
>=20

That would be fine.=20

>=20
> >=20
> >    - The next paragraph states, "...For instance, if an=20
> attacker knows=20
> > that the mobile node's home agent selection policy is to bootstrap=20
> > with a new local home agent whenever entering a new network (e.g.,=20
> > because the mobile node wants to improve routing efficiency in=20
> > Bi-directional Tunneling mode), the attacker can track the mobile=20
> > node's movement if it is aware of the mobile node's current home=20
> > addresses." The MN's movement is tracked by the attacker=20
> using what?=20
> > The HoAs are changing with every new HA in every local network. If=20
> > anything, this should make tracking the MN more difficult. I don't=20
> > follow the discussion in that paragraph or the conclusion.
>=20
> I think you have a valid point, and I don't mind removing this text.
>=20

I would support removing this text - I'll respond to Kilian separately
on this topic.=20

>=20
> >=20
> >    - Finally, the last paragraph states, "Consequently, if a high=20
> > level of location privacy is desired, a mobile node should=20
> not switch=20
> > to local home agents in an eager manner or should not=20
> reveal its home=20
> > address to untrusted nodes. Furthermore, the disclosure of policy=20
> > information that can help locating the mobile node should=20
> be carefully=20
> > considered." Given that this is first discussion of privacy in the=20
> > document, what does "high level of location privacy" mean?=20
> If there is=20
> > such a thing, what is then a "lower level of location=20
> privacy" and how is that achieved?
> > Further, it is not clear as to what element of privacy is needed or=20
> > which elements the privacy is needed from. This text is=20
> recommending=20
> > against using local home agents - is this to provide=20
> privacy from the=20
> > local network? If this is only about providing privacy from=20
> > correspondent and other observing nodes, I don't understand the=20
> > difference made by local or remote HAs. Also, I don't follow the=20
> > disclosure of policy information - this document is only=20
> discussing HA=20
> > bootstrapping; is there such policy information that may be=20
> disclosed=20
> > leading to this privacy concern?
>=20
> I personally don't mind removing this text either.
>=20

Again, I'll respond to Kilian on the privacy topic in general...=20

>=20
> >=20
> > 5. I noticed a discussion based on Kilian's comments to include the=20
> > HoA allocation via DHCP as a possible option. If we decide=20
> to include=20
> > that, it would be important to talk about how that HoA gets tied to=20
> > the SA created between the MN and HA. If the HoA is assinged via=20
> > IKEv2, IKEv2 takes care of such a binding. If not, we need=20
> to describe=20
> > how the address is bound to the SA. The use of DHCP to=20
> assign anything=20
> > requiring particular security values is tricky to handle=20
> and I suggest=20
> > that we don't get into that in this draft.
>=20
> I'll leave this to Kuntal.=20
>=20
> > 6. In general, a number of the security considerations revolving=20
> > around packet modification attacks apply equally to the=20
> DHCP and DNS solutions.
> > However, in the DNS case, the use of DNSSEC between the DNS=20
> client and=20
> > server is the only thing needed to ensure protection against such=20
> > attacks. In this case, the security solution needed relies=20
> on several=20
> > transitive trust relationships - trust between AAA parties,=20
> DHCP Relay=20
> > Agent and Server, and DHCP client and server. This is not=20
> > unreasonable, but, probably worth mentioning.
>=20
> Sure we can mention that. And that's what RFC 4014 is built=20
> upon. We are simply using that model, not introducing anything new.
>=20

Agreed.=20

Thanks,
Vidya

> Thanks again, these are very useful comments.
>=20
> Alper
>=20
>=20
>=20
> >=20
> > Thanks,
> > Vidya
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20

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



From mip6-bounces@ietf.org Mon Mar 05 22:31:20 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOQOT-00015d-Mw; Mon, 05 Mar 2007 22:31:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOQOR-00015H-Pb
	for mip6@ietf.org; Mon, 05 Mar 2007 22:31:15 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOQOR-0002n8-6n
	for mip6@ietf.org; Mon, 05 Mar 2007 22:31:15 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l263Uwom004842
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Mar 2007 19:30:59 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l263Uvk9000346; Mon, 5 Mar 2007 19:30:58 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 19:30:57 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Mon, 5 Mar 2007 19:30:57 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325134F21CD@NAEX13.na.qualcomm.com>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4F01278512@lan-ex-01.panasonic.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAAA+ifwALlocQA=
References: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
	<4D2F935F08D41A4C8866693F4F0D7C4F01278512@lan-ex-01.panasonic.de>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
X-OriginalArrivalTime: 06 Mar 2007 03:30:57.0731 (UTC)
	FILETIME=[DAB87930:01C75F9F]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
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 Kilian,
I must say that I'm still confused :) Specifically,
=20
1. What privacy are we talking about here and who is the attacker? For
instance, are we talking about privacy of the HoA/CoA from CNs (here, CN
would be the potential attacker)? Or, are we talking about entities on
path between the MN and HA being able to know the HoA-CoA mapping? Or,
are we just generally talking about even an off-path entity being able
to obtain the MN's HoA (say, via DNS or something)? It seems to me like
you are talking about the last one, but, I'm not sure.=20

2. Why is an MN that is interested in privacy updating the DNS record
with its HoA? That seems counter-intuitive to me. Updating DNS with an
address is as good as publishing the address on a public website (or an
intranet, when DNSSEC is used) :) So, it sounds to me like if an MN
wants to keep its HoA location private, it would not be updating the DNS
record with its HoA. Or, if the MN needs to get its DNS record updated
and if the MN's policy is to get a local HA for optimal routing, the MN
is clearly not interested in such privacy. Alternately, if the operator
policy is to assign a local HA, the MN must either choose to not publish
its HoA using DNS (if it wants such privacy) or accept that there is no
privacy. It simply cannot be both ways :)=20

3. If you meant any disclosure of HoA/CoA mapping to entities, that is a
problem that is unrelated to any DNS updates. However, such a problem
exists regardless of the HA location, since the CoA is the one that
really discloses the current location of the MN and that topologically
identifies the location irrespective of where the HoA is anchored.=20

Thanks,
Vidya

> -----Original Message-----
> From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]=20
> Sent: Friday, March 02, 2007 4:45 AM
> To: Narayanan, Vidya
> Cc: Mobile IPv6 Mailing List; Alper Yegin
> Subject: RE: [Mip6] WGLC: Review=20
> ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
>=20
> Hi Vidya,
>=20
> I'll comment on your questions about the location privacy=20
> issue described in the security considerations section, since=20
> the text was provided by James and me. However, the initial=20
> text was longer, maybe we cut too much and need to add some=20
> more text again to make the issue clear.=20
>=20
> I don't agree with removing the text as Alper suggested.=20
> IMHO, the text describes a valid security issue that that=20
> implementors should be aware of and that can be avoided when=20
> following the recommendations in the text. Thus, the text is=20
> important IMHO.
>=20
> The issue is the following:
>=20
> A HoA anchored at a local HA (henceforth called local HoA)=20
> has a prefix belonging to the access network the MN is=20
> currently attached to.
> Consequently, a local HoA contains some location information.=20
> If any entity 1. knows the MN's HoA and 2. knows that the=20
> corresponding HA is currently a *local* HA, it can infer the=20
> MN's location from the local HoA prefix.
>=20
> The attacker (any node that is not authorized to get the MN's=20
> location) can get the MN's location if
>=20
> 1. If the attacker can obtain the MN's local HoA, e.g., by=20
> monitoring the DNS entry (in case the MN's DNS entry is=20
> always updated after
> bootstrapping) or by initiating communication with the MN (if=20
> the MN will use the local HoA for optimized communication) or=20
> by eavesdropping the MN's traffic.
>=20
> 2. If the attacker knows that the HoA obtained in 1 is local.=20
> This is possible under certain circumstances, e.g., when a=20
> MN's or an operator's policy is that the MN shall always try=20
> to bootstrap with a local HA when entering an ASP's network=20
> (this may make sense for routing efficiency
> reasons) and the attacker is aware of this policy.
>=20
> See some more comments inline.
>=20
> >    - The section currently states, "If the home agent=20
> selected by the=20
> > mobile node is local or nearby, (as in section 3.2.2),=20
> disclosing the=20
> > mobile node's home address (e.g., by updating the mobile=20
> node's FQDN=20
> > in the DNS) has the potential to expose some information about the=20
> > mobile node's location." I don't understand the intended=20
> implication=20
> > here. How is this different from an HA in the MSP=20
> performing the DNS=20
> > update?
>=20
> If a HA is not local, the corrsponding HoA prefix does not=20
> contain location information and the issue described above=20
> doesn't exist. Maybe we should add something like "A local=20
> HoA contains location information, since the prefix is linked=20
> to the MN's current access network.".
>=20
> >=20
> >    - The next paragraph states, "...For instance, if an=20
> attacker knows=20
> > that the mobile node's home agent selection policy is to bootstrap=20
> > with a new local home agent whenever entering a new network (e.g.,=20
> > because the mobile node wants to improve routing efficiency in=20
> > Bi-directional Tunneling mode), the attacker can track the mobile=20
> > node's movement if it is aware of the mobile node's current home=20
> > addresses." The MN's movement is tracked by the attacker=20
> using what?=20
> > The HoAs are changing with every new HA in every local network. If=20
> > anything, this should make tracking the MN more difficult. I don't=20
> > follow the discussion in that paragraph or the conclusion.
>=20
> If the attacker monitors the DNS entry of the MN and if the=20
> DNS entry of the MN is always updated with a new local HoA=20
> after bootstrapping with a new local HA, the attacker can=20
> track the MN's movement to some extent.
>=20
> >=20
> >    - Finally, the last paragraph states, "Consequently, if a high=20
> > level of location privacy is desired, a mobile node should=20
> not switch=20
> > to local home agents in an eager manner or should not=20
> reveal its home=20
> > address to untrusted nodes. Furthermore, the disclosure of policy=20
> > information that can help locating the mobile node should=20
> be carefully=20
> > considered." Given that this is first discussion of privacy in the=20
> > document, what does "high level of location privacy" mean?=20
> If there is=20
> > such a
>=20
> The "level of location privacy" refers to the granularity of=20
> disclosed location information. For some users it may be=20
> acceptable to disclose the prefix of the current access=20
> network, while it is not acceptable to disclose the current=20
> AR. Such "access network-level" of location privacy can,=20
> e.g., be achieved with localized MM, where a MN's MIPv6 CoA=20
> is equal to the MN's PMIP-HoA anchored at a local PMIP-HA. In=20
> this case, an attacker acting as correspondent node could at=20
> most learn the MN's current access network (from the MN's CoA=20
> in MIPv6 route optimization mode).
>=20
> For other people this "level" of location privacy is not acceptable.
> They have stronger requirements on location privacy, where=20
> the attacker cannot figure out the current access network.=20
> For instance, some users don't want that it is possible to=20
> find out that they are on a business trip or on vacation in=20
> another country (e.g., to prevent that someone uses this=20
> information for a burglary). This was referred to as "high=20
> level" of location privacy. Maybe we need to add some text about this.
>=20
> > thing, what is
> > then a "lower level of location privacy" and how is that achieved?
> > Further, it is not clear as to what element of privacy is needed or=20
> > which elements the privacy is needed from. This text is=20
> recommending=20
> > against using local home agents - is this to provide=20
> privacy from the=20
> > local network? If this is only about providing privacy from=20
> > correspondent and other observing nodes, I don't understand the=20
> > difference made by local or remote HAs. Also, I don't follow the=20
> > disclosure of policy information - this document is only=20
> discussing HA=20
> > bootstrapping; is there such policy information that may be=20
> disclosed=20
> > leading to this privacy concern?
>=20
> The policy information refers to the MN's policy to eagerly=20
> bootstrap with a local HA and updating the HoA when entering=20
> a new network.
>=20
> Regards,
>=20
> Kilian
>=20
>=20
> Panasonic R&D Center Germany GmbH
> 63225 Langen, Hessen, Germany
> Reg: AG Offenbach (Hessen) HRB 33974
> Managing Director: Thomas Micke
>=20
>=20
>=20

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



From mip6-bounces@ietf.org Mon Mar 05 22:49:01 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOQfL-00052X-Ay; Mon, 05 Mar 2007 22:48:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOQfJ-0004t5-BS
	for mip6@ietf.org; Mon, 05 Mar 2007 22:48:41 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOQfH-0004dL-SX
	for mip6@ietf.org; Mon, 05 Mar 2007 22:48:41 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l263mcvo005958
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Mar 2007 19:48:38 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l263mbMY004839; Mon, 5 Mar 2007 19:48:37 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 19:48:37 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Mon, 5 Mar 2007 19:48:36 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325134F21CE@NAEX13.na.qualcomm.com>
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBDA2F$0001@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5gACVGXHAAlGX2EA==
References: <7CCD07160348804497EF29E9EA5560D7FBDA2F$0001@exchtewks2.starentnetworks.com>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 06 Mar 2007 03:48:37.0582 (UTC)
	FILETIME=[5270E6E0:01C75FA2]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
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 Kuntal,=20

> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
> Sent: Friday, March 02, 2007 8:53 PM
> To: Alper Yegin; Narayanan, Vidya; Mobile IPv6 Mailing List
> Subject: RE: [Mip6] WGLC:=20
> Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
>=20
>=20
>=20
> > -----Original Message-----
> > From: Alper Yegin [mailto:alper.yegin@yegin.org]
> > Sent: Friday, March 02, 2007 5:26 AM
> > To: 'Narayanan, Vidya'; 'Mobile IPv6 Mailing List'
> > Subject: RE: [Mip6] WGLC: Reviewofdraft-ietf-mip6-bootstrapping-
> > integrated-dhc-02
> >=20
> > >
> > > 5. I noticed a discussion based on Kilian's comments to=20
> include the
> HoA
> > > allocation via DHCP as a possible option. If we decide to include
> that,
> > > it would be important to talk about how that HoA gets=20
> tied to the SA=20
> > > created between the MN and HA. If the HoA is assinged via IKEv2,
> IKEv2
> > > takes care of such a binding. If not, we need to describe how the=20
> > > address is bound to the SA. The use of DHCP to assign anything
> requiring
> > > particular security values is tricky to handle and I=20
> suggest that we=20
> > > don't get into that in this draft.
> >=20
> > I'll leave this to Kuntal.
> >=20
> [KC>] Well, I don't understand what is tricky in getting an=20
> IPv6 address assigned from DHCP server and using it in the=20
> IKEv2 CFG_REQUEST as
> *requested* INTERNAL_IP6_ADDRESS. This is clearly allowed in RFC 4306.
> Even mip6-ikev2 spec talks about this:
>=20
> "
>    The mobile node could suggest a home address that it wants=20
> to use in
>    the CFG_REQUEST.  For example, this could be a home address that it
>    was allocated before or could be an address the mobile node auto-
>    configured from the IPv6 prefix on the home link.  The Home Agent
>    could let the mobile node use the same home address by setting the
>    INTERNAL_IP6_ADDRESS attribute in the CFG_REPLY payload to the same
>    home address.  If the home agent wants the mobile node to use a
>    different home address, it sends a new home address in the
>    INTERNAL_IP6_ADDRESS attribute in the CFG_REPLY payload. =20
> The Mobile
>    Node MUST stop using its old home address and start using the newly
>    allocated home address.
> "
>=20


Yes, requesting a certain address to be assigned in IKEv2 is certainly
allowed. However, RFC4306 does not cover the case where the client,
outside the IKEv2 exchange, uses DHCP to obtain an IP address and then
request that address to be assigned. This has the following
implications:=20

- since the MN doesn't really indicate that the IP address was obtained
via DHCP, does the HA (IKEv2 responder function, really) know that that
was the case?=20

- if the HA is also using a DHCP server to assign addresses, does it
check to see if the address is available? If the DHCP pool management is
done right, it should be the same server from which the MN obtained its
HoA to begin with (having two servers managing the same prefix would be
a problem). However, if that is the case, is the DHCP server going to
say that the address is taken? How does it know that the address was
taken by the same MN?=20

- does the HA know the lease parameters of the DHCP-assigned HoA of the
MN? RFC4306 states "INTERNAL_ADDRESS_EXPIRY - Specifies the number of
seconds that the host can use the internal IP address.  The host MUST
renew the IP address before this expiry time." This behavior will allow
the HA to ensure that the MN is never capable of redirecting traffic for
another node by continuing to use the SA with that IP address even after
that address expires. If the DHCP process was done outside of IKEv2, it
is not clear how that is feasible and how the HA can keep track of that.


It doesn't look like the HIOPT draft addresses such issues either. We
can discuss those issues in the context of the HIOPT draft, but, for
now, I think not referring to this is a good way to move forward with
this draft.=20

Hope that helps.=20

Regards,
Vidya


> -Kuntal
> =20
>=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=20
> 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



From mip6-bounces@ietf.org Tue Mar 06 05:30:02 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOWv0-0008Gr-Ru; Tue, 06 Mar 2007 05:29:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOWuz-0008Gj-Ki; Tue, 06 Mar 2007 05:29:17 -0500
Received: from mail.unilim.fr ([164.81.1.45] helo=smtp.unilim.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HOWuv-0001jZ-5w; Tue, 06 Mar 2007 05:29:17 -0500
Received: from [164.81.60.82] (sauveron-port.msi.unilim.fr [164.81.60.82])
	(authenticated bits=0)
	by smtp.unilim.fr (8.13.1/8.13.1) with ESMTP id l26AT1nh020291
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Mar 2007 11:29:01 +0100
Message-ID: <45ED426C.6000800@xlim.fr>
Date: Tue, 06 Mar 2007 11:29:00 +0100
From: Damien Sauveron <damien.sauveron@xlim.fr>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: manet@ietf.org, mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Univ-Limoges-Greylist: Sender succeeded SMTP AUTH authentication, not
	delayed by milter-greylist-2.0.2 (smtp.unilim.fr [164.81.1.45]);
	Tue, 06 Mar 2007 11:29:01 +0100 (CET)
X-Univ-Limoges-MailScanner-Information: Serveur Anti-virus Please contact the
	SCI, Univ. of Limoges, for more information
X-Univ-Limoges-MailScanner: Found to be clean
X-Univ-Limoges-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (cached, score=-101.299, requis 6, autolearn=not spam,
	ALL_TRUSTED -1.80, BAYES_50 0.00, SMTP_AUTH -100.00,
	VOWEL_TOCC_5 0.50)
X-Univ-Limoges-MailScanner-Envelope-From: damien.sauveron@xlim.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.unilim.fr id
	l26AT1nh020291
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: 
Subject: [Mip6] CFP IAS'07 (Paper Submission Deadline: 20th March 2007)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Call for Papers (Paper Submission Deadline: 20th March 2007)

The Third International Symposium on Information Assurance and Security
(IAS'07) http://www.ias07.org/

August 29-31, 2007, Manchester, United Kingdom

Proceedings published by IEEE CS press

Technically sponsored by ICST (http://www.icst.org/) and CREATE-NET
(http://www.create-net.it/)

Overview:

Information assurance and security has become an important research
issue in networked and distributed information sharing environments.
Finding effective ways to protect information systems, networks and
sensitive data within the critical information infrastructure is
challenging even with the most advanced technology and trained
professionals. The International Symposium on Information Assurance and
Security aims to bring together researchers, practitioners, developers,
and policy makers involved in multiple disciplines of information
security and assurance to exchange ideas and to learn the latest
development in this important field.

Topics:

Previously unpublished work offering novel research and application
contributions in any aspect of information assurance, security and
privacy are solicited for submission to the IAS'07 symposium. Topics of
interest include, but are not limited to, the following:

- Agent and Mobile Code Security

- Anonymity and User Privacy

- Authentication and Identity Management

- Authorization and Access Control

- Biometrics Security and Applications

- Computer Forensics

- Cryptographic Protocols

- Data Integrity and Privacy

- Database Security

- Denial of Service and Intrusion Detection

- Distributed System Security

- E-Commerce and E-Government Security

- Fraud Control

- Information Warfare and Cyber-terrorism

- Intellectual Property Protection

- Internet and Web Services Security

- Key Management and Recovery

- New Ideas and Paradigms for Security

- Operating System Security

- Secure Hardware and Smartcards

- Secure Software Technologies

- Security Education and Training

- Security Management and Strategy

- Security Models and Architectures

- Security Verification, Evaluations and Measurements

- Trust Negotiation, Establishment and Management

- Ubiquitous Computing Security



Paper Submission:

Papers should be original and contain contributions of theoretical,
experimental or application nature, or be unique experience reports.
Papers must be submitted no later than March 20, 2007 and electronic
submission in PDF or Word is required. The page limit for a full-length
paper is 6 pages. Short papers describing novel research visions,
work-in-progress or less mature results are also welcome, with the limit
of 4 pages. All submissions should be in the IEEE 8.5" x 11" two-column
format. Papers should contain up to 5 keywords. Papers will be evaluated
for originality, significance, clarity, and soundness, and will be
reviewed by at least three independent reviewers. The IAS'07 paper
submission system is available at:
http://www.ias07.org/paper_submission.php.


Conference Proceedings:

Accepted papers will be published by IEEE Computer Society Press.
Selected papers presented in the conference will be considered for
publication in a special issue of an international journal.


Best Paper Awards:

The IAS'07 Program Committee will select one winner for the Best Paper
Award (all regular papers are eligible) and one winner for the Best
Student Paper Award (to be eligible, the student must be the sole author
of the paper, or the first author and primary contributor. A cover
letter to the General Chair/Program Chair must identify the paper as a
candidate for this competition at the time of submission). The award
winners will each be presented with an award certificate and a direct
payment of =A3200 at the conference, and an invitation to submit an
extended version of the award-winning paper for the consideration of
publication in an international journal, JIAS.


Key Deadlines:

Paper Submission Deadline: March 20, 2007

Author Notification: May 10, 2007

Camera Ready Submission Deadline (6 pages): June 8, 2007

Author Registration Deadline: June 8, 2007


Panel/Tutorial Proposal Submission Deadline: April 20, 2007

Proposal Notification: May 10, 2007


Contacts:

Further enquiries regarding matters related to IAS'07 can be sent to the
Conference Local Organising Chairs:

Ms Bryony Quick; or

Mr Iain Hart;

Email: ias07@cs.man.ac.uk

Tel: +44 (0)161 275 6130

Fax: +44 (0)161 275 6204
--=20
Damien Sauveron



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



From mip6-bounces@ietf.org Tue Mar 06 07:44:49 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOZ1N-0002mr-OI; Tue, 06 Mar 2007 07:44:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOZ1M-0002me-Tb
	for mip6@ietf.org; Tue, 06 Mar 2007 07:44:00 -0500
Received: from tao.fdupont.fr ([82.236.136.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOZ1K-0007tP-Be
	for mip6@ietf.org; Tue, 06 Mar 2007 07:44:00 -0500
Received: from tao.fdupont.fr (localhost [127.0.0.1])
	by tao.fdupont.fr (8.13.5/8.13.5) with ESMTP id l26Ch41O013116;
	Tue, 6 Mar 2007 13:43:04 +0100 (CET)
Received: from tao.fdupont.fr (dupont@localhost)
	by tao.fdupont.fr (8.13.5/8.13.5/Submit) with ESMTP id l26Ch3hS013112; 
	Tue, 6 Mar 2007 13:43:03 +0100 (CET)
Message-Id: <200703061243.l26Ch3hS013112@tao.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt 
In-reply-to: Your message of Mon, 19 Feb 2007 17:19:47 CST.
	<C1FF8CB3.2EF82%basavaraj.patil@nokia.com> 
Date: Tue, 06 Mar 2007 13:43:03 +0100
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: mip6@ietf.org, ietf-ipsec-failover.vpnc.org@tao.fdupont.fr
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Comments about draft-ietf-mip6-ha-switch-03.txt:

 - I really like the draft as I believe the service it provides is needed
  and is a major missing piece for MIPv6 in the real world but I have
  a critical concern with it: it collides with the IPsec failover
  activity, i.e., we could get two competiting mechanisms for the same
  thing. So this issue must be solved before going further:
   * obviously the basic mechanisms are the same: the server sends to the
    client a "look-somewhere-else" message with a list of potential "better"
    servers.
   * when the message is delivered to the MIPv6 stack the information
    must be propagated IKE, when it is deliveded to IKE (for instance by
    a new notification) it must be propagated to the MIPv6 stack: in all
    cases there must be an API between both.
   * when the two mechanisms overlap they don't handle exactly the same
    cases so we'll need a way to extend the coverage of the chosen one.
   * IKE has a little advantage for the security because it has a secured
    built-in reliable request/reply facility. At the opposite a new
    MH message needs an extra SPD entry, retransmission policy, etc.

 - 1.Introduction (comment): note the security function can be considered
  as an integral part of the Home Agent service.

 - 4.1 Sending Home Agent Switch Messages "o A home  agent to mobile
   node authentication option": this idle introduces a bidding down
   security issue. I propose to say the authentication MUST use the
   same mechanism than BU/BA (this is what we want and this should keep
   everybody happy :-).

 - 5.1 Receiving Home Agent Switch Messages "o The packet MUST be
   authenticated, either...": same issue (and same proposed solution).

 - 5.1 Receiving Home Agent Switch Messages: the presentation can suggest
   the connection to a new HA has to be done after leaving the current one
   (obviously this is not the intended behavior).

 - 5.1 Receiving Home Agent Switch Messages:
   perform home agent discovery -> perform home agent address discovery?

 - 9. Security Considerations: again...

 - 9. Security Considerations: use the home agent -> use a home agent?

Regards

Francis.Dupont@fdupont.fr

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



From mip6-bounces@ietf.org Tue Mar 06 09:42:01 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOaqr-0000xs-JI; Tue, 06 Mar 2007 09:41:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOaqq-0000wf-0i
	for mip6@ietf.org; Tue, 06 Mar 2007 09:41:16 -0500
Received: from static-ip-163-194-65-202.rev.dyxnet.com ([202.65.194.163]
	helo=hitachihk6.hitachi.cn) by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HOaoK-0007I6-QD
	for mip6@ietf.org; Tue, 06 Mar 2007 09:38:46 -0500
Received: (qmail 29002 invoked from network); 6 Mar 2007 14:38:31 -0000
X-NetworkBox-HamSign: 0101;OUT;hitachihk6;5aed71223b149612acf5f3f868ed32fb;
Received: from unknown (HELO hitachihk5.hitachi.cn) (170.95.94.1)
	by static-ip-163-194-65-202.rev.dyxnet.com with SMTP;
	6 Mar 2007 14:38:30 -0000
Received: (qmail 18869 invoked from network); 6 Mar 2007 14:38:29 -0000
X-NetworkBox-HamSign: 0101;OUT;hitachihk5;c908017db0eb16326d224ecd350e7ebf;
Received: from hchidc204.hitachi-china.com (HELO hchidc204.hitachi.cn)
	(170.95.82.6) by 172.16.10.9 with SMTP; 6 Mar 2007 14:38:29 -0000
Received: from hcbjdc2.hitachi.cn ([170.95.81.2]) by hchidc204.hitachi.cn with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 Mar 2007 22:38:29 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt 
Date: Tue, 6 Mar 2007 22:38:27 +0800
Message-ID: <8386EDF347730C46BA47710F87AE1FE90216C7@hcbjdc2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt 
Thread-Index: Acdf7bPfk7dewzbZSbSbJfMfUkcSEAADSsMw
From: "DENG, HUI -HCHBJ" <hdeng@hitachi.cn>
To: "Francis Dupont" <Francis.Dupont@fdupont.fr>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
X-OriginalArrivalTime: 06 Mar 2007 14:38:29.0124 (UTC)
	FILETIME=[1B360C40:01C75FFD]
X-Scanned-By-hitachihk5: Virus scan performed by network-box
X-Scanned-By-hitachihk5: Scanner file id is hitachihk5-1173191909.301-18866-000
X-Scanned-By-hitachihk5: No known viruses found in message (received+scanned
	in 0.02/0.08 secs)
X-Scanned-By-hitachihk5: Spam-Check-Result: No,
	hits=0 required=7 tests= autolearn=no version=2.0
X-Spam-Status: No
X-Scanned-By-hitachihk6: Virus scan performed by network-box
X-Scanned-By-hitachihk6: Scanner file id is hitachihk6-1173191909.655-28971-000
X-Scanned-By-hitachihk6: No known viruses found in message (received+scanned
	in 0.02/1.06 secs)
X-Scanned-By-hitachihk6: Spam-Check-Result: No,
	hits=0 required=7 tests= autolearn=no version=2.0
X-Scanned-By-hitachihk6: Whitelisted with valid signature (outbound via
	Network Box hitachihk5)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: mip6@ietf.org, ietf-ipsec-failover.vpnc.org@tao.fdupont.fr
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi, Francis,

Thanks for your review,=20
Please check some reply below inline headed with [Hui]

Regards,

-Hui

-----Original Message-----
From: Francis Dupont [mailto:Francis.Dupont@fdupont.fr]=20
Sent: 2007=C4=EA3=D4=C26=C8=D5 20:43
To: Basavaraj Patil
Cc: mip6@ietf.org; ietf-ipsec-failover.vpnc.org@tao.fdupont.fr
Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt=20

Comments about draft-ietf-mip6-ha-switch-03.txt:

 - I really like the draft as I believe the service it provides is =
needed
  and is a major missing piece for MIPv6 in the real world but I have
  a critical concern with it: it collides with the IPsec failover
  activity, i.e., we could get two competiting mechanisms for the same
  thing. So this issue must be solved before going further:
[Hui] I agree that IKE could do this too if this mechanism is only =
dedicated to home agent switch with one more assumption: authentication =
option is not used here. I guess that it could have multiple usages in =
the future.

   * obviously the basic mechanisms are the same: the server sends to =
the
    client a "look-somewhere-else" message with a list of potential =
"better"
    servers.
   * when the message is delivered to the MIPv6 stack the information
    must be propagated IKE, when it is deliveded to IKE (for instance by
    a new notification) it must be propagated to the MIPv6 stack: in all
    cases there must be an API between both.
[Hui] Do you mean IPsec other than IKE here? Why these messages need to =
be propagated to IKE? There is a need about API between MIP6 and IKE, =
but this is a generic requirement, not only happen in home agent switch =
case.=20

   * when the two mechanisms overlap they don't handle exactly the same
    cases so we'll need a way to extend the coverage of the chosen one.
   * IKE has a little advantage for the security because it has a =
secured
    built-in reliable request/reply facility. At the opposite a new
    MH message needs an extra SPD entry, retransmission policy, etc.

 - 1.Introduction (comment): note the security function can be =
considered
  as an integral part of the Home Agent service.

 - 4.1 Sending Home Agent Switch Messages "o A home  agent to mobile
   node authentication option": this idle introduces a bidding down
   security issue. I propose to say the authentication MUST use the
   same mechanism than BU/BA (this is what we want and this should keep
   everybody happy :-).

 - 5.1 Receiving Home Agent Switch Messages "o The packet MUST be
   authenticated, either...": same issue (and same proposed solution).

 - 5.1 Receiving Home Agent Switch Messages: the presentation can =
suggest
   the connection to a new HA has to be done after leaving the current =
one
   (obviously this is not the intended behavior).

 - 5.1 Receiving Home Agent Switch Messages:
   perform home agent discovery -> perform home agent address discovery?

 - 9. Security Considerations: again...

 - 9. Security Considerations: use the home agent -> use a home agent?

Regards

Francis.Dupont@fdupont.fr

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

Disclaimer:
The contents of this e-mail, and its attachments, if any, are confidential and may be protected
by law against any unauthorized use.  If you have received this e-mail by mistake or have
reason to believe that you are not the intended recipient, please notify the sender by reply
e-mail as soon as possible and delete it from your computer system immediately thereafter.
If you are not the intended recipient, you must not copy this e-mail or attachment or disclose
the contents to any other person.  While we have made every effort to keep our network virus free,
we take no responsibility for any computer virus which might be transferred by way of this e-mail.

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



From mip6-bounces@ietf.org Tue Mar 06 11:31:36 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOcYv-0007zh-US; Tue, 06 Mar 2007 11:30:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOcYv-0007zK-8U
	for mip6@ietf.org; Tue, 06 Mar 2007 11:30:53 -0500
Received: from cluster-b.mailcontrol.com ([217.68.146.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOcYt-0007dw-Vp
	for mip6@ietf.org; Tue, 06 Mar 2007 11:30:53 -0500
Received: from rly24b.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly24b.srv.mailcontrol.com (MailControl) with ESMTP id
	l26GP1RZ005652
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Tue, 6 Mar 2007 16:30:42 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly24b.srv.mailcontrol.com (MailControl) id l26Fu9hY020164
	for mip6@ietf.org; Tue, 6 Mar 2007 15:56:09 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly24b-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l26Fu0je019401; Tue, 06 Mar 2007 15:56:09 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 0af1_54848e38_cbf8_11db_9b0f_0030482aac25;
	Tue, 06 Mar 2007 16:35:36 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030616553705-27954 ;
	Tue, 6 Mar 2007 16:55:37 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.152,BAYES_00: -1.665,TOTAL_SCORE: -1.817
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 6 Mar 2007 17:00:33 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: home network requested by MN may be != assigned network (was: RE:
	[Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBDA4F$0001@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: home network requested by MN may be != assigned network (was:
	RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
Thread-Index: AcdZUPl3RCOZHB9nQb6+3hPvBup2ywBYXBGgARQFcMAAD4CxkAAf7ZPg
References: <4D2F935F08D41A4C8866693F4F0D7C4F012785AB@lan-ex-01.panasonic.de>
	<7CCD07160348804497EF29E9EA5560D7FBDA4F$0001@exchtewks2.starentnetworks.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F01278715@lan-ex-01.panasonic.de>
Date: Tue, 6 Mar 2007 16:48:34 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MailControl A-07-06-90 (www.mailcontrol.com) on 10.66.1.134
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 578029c71870398e30dc7af6a1ae528d
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, heejin.jang@samsung.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kuntal,

thanks for the clarification, but it is still not clear to me how =
assignment of HA information pertaining to an MSP X different from ASP =
and Home MSP Y (that has trust relationship with MN's MSA) works. Heejin =
and you said that in an earlier mail that this is supported, but I can't =
find any details in the drafts.=20

Is the MSA allowed to send HA information to the NAS during network =
authentication, which pertains to an MSP X different from the MN's home =
MSP Y, so that the NAS/DHCP would associate the received information =
with the home MSP domain Y? The NAS/DHCP would then return home =
information pertaining to MSP X to the MN, even though the target =
network requested by the MN was (home) MSP Y.

Or is such assignment only possible if the MN requests a target network =
MSP X, which is neither ASP nor Home MSP Y? Since the MSA doesn't know =
the target network requested by the MN at the time of network =
authentication, would the MSA always send to the NAS during network =
authentication multiple HAs pertaining to all MSPs that the MN is =
allowed to use and the DHCP server picks the correct one according to =
the requested target network?=20

Thanks,

Kilian

> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
> Sent: Montag, 5. M=E4rz 2007 17:17
> To: Kilian Weniger
> Cc: heejin.jang@samsung.com; Mobile IPv6 Mailing List
> Subject: RE: home network requested by MN may be !=3D assigned=20
> network (was: RE: [Mip6] WGLC:=20
> draft-ietf-mip6-bootstrapping-integrated-02)
>=20
> Hi Kilian,
>=20
> If the MSA assigns Home Agent info in domain X which is MN's=20
> home MSP and the MN requests for Home Agent info for domain Y=20
> (another MSP), the DHCP server may not have that info. In=20
> that case, it returns a local Home Agent. I think this is=20
> mentioned in HIOPT I-D:
>=20
> "
> Id-type 1 indicates the mobile node is interested in learning the
>    home network information that pertains to the given realm.=20
>  This type
>    can be used to discover home agents that are hosted by a=20
> user's home
>    domain (as indicated by his/her NAI-based username -- user@
>    HomeRealm).  The Home Network Identifier field MUST be set to the
>    target home MSP.  In case there is no available home=20
> information for
>    the specified home MSP in the DHCP server, the local home=20
> information
>    is provided.
> "
>=20
> We can clarify this in the integrated I-D as you suggested.
>=20
> Thanks for your comments.
>=20
> -Kuntal
>=20
>=20
> > -----Original Message-----
> > From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]
> > Sent: Monday, March 05, 2007 3:16 AM
> > To: Chowdhury, Kuntal
> > Cc: heejin.jang@samsung.com; Mobile IPv6 Mailing List
> > Subject: home network requested by MN may be !=3D assigned=20
> network (was: RE:
> > [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
> >=20
> > Hi Kuntal, Heejin,
> >=20
> > since the MN's MSA is the entity that assigns a home=20
> network and an MSP to
> > the MN, I guess that it is allowed that the MSA assigns a=20
> different home
> > network from a different MSP to the MN than requested by=20
> the MN in the
> > Home Network Identifier DHCP Option. This is needed, e.g.,=20
> when the MSA
> > doesn't have a roaming relationship with the MSP requested=20
> by the MN, when
> > the requested MSP doesn't provide the required service=20
> (e.g., DSMIP, NEMO
> > etc) or when the MSA knows of a better (e.g., less loaded)=20
> home network
> > from a different MSP. I think this is currently not=20
> mentioned in the draft
> > and it would be good to clarify.
> >=20
> > Regards,
> >=20
> > Kilian
> >=20
> >=20
> > > -----Original Message-----
> > > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > > Sent: Dienstag, 27. Februar 2007 22:02
> > > To: heejin.jang@samsung.com; Kilian Weniger
> > > Cc: mip6@ietf.org; Basavaraj Patil
> > > Subject: RE: RE: RE: [Mip6] WGLC:
> > > draft-ietf-mip6-bootstrapping-integrated-02
> > >
> > > Thanks Heejin. I think your suggested clarification # 3 is good.
> > >
> > > -Kuntal
> > >
> > >
> > > ________________________________________
> > > From: Heejin Jang [mailto:heejin.jang@samsung.com]
> > > Sent: Sunday, February 25, 2007 8:45 PM
> > > To: Kilian Weniger
> > > Cc: mip6@ietf.org; Basavaraj Patil
> > > Subject: Re: RE: RE: [Mip6] WGLC:
> > > draft-ietf-mip6-bootstrapping-integrated-02
> > >
> > > Hi, Kilian.
> > > Thanks for the comments.
> > >
> > > Regarding the use of term, the draft(hiopt) supports all the
> > > three following networks as target networks
> > > 1) ASP (MN's currently visited network)
> > > 2) Home MSP (=3D MSA)
> > > 3) MSP (network which is nether  ASP nor Home MSP but has
> > > trust relationship with MN's MSA)
> > >
> > > The term 'home MSP' can be ambiguous since it does not include 3),
> > > so we will modify it to 'MSP with roaming  relationship with
> > > MN's MSA' for more clarification.
> > > Thanks.
> > >
> > > Regards,
> > > Heejin.
> > >
> > > ------ Original Message -------
> > > Sender : Kilian Weniger<Kilian.Weniger@eu.panasonic.com>
> > > Date : 2007-02-22 23:00
> > > Title : RE: RE: [Mip6] WGLC:
> > > draft-ietf-mip6-bootstrapping-integrated-02
> > >
> > > Hi Heejin,
> > >
> > > thanks for your comments, see my replies inline.
> > >
> > > Please note that the comments in my mail were referring to
> > > draft-ietf-mip6-bootstrapping-integrated-02. And since=20
> the reference
> > > [HIOPT] in draft-ietf-mip6-bootstrapping-integrated-02 is=20
> hiopt-01, I
> > > didn't consider hiopt-02.
> > >
> > > > -----Original Message-----
> > > > From: Heejin Jang [mailto:heejin.jang@samsung.com]
> > > > Sent: Dienstag, 20. Februar 2007 08:31
> > > > To: Kilian Weniger
> > > > Cc: Basavaraj Patil; mip6@ietf.org
> > > > Subject: Re: RE: [Mip6] WGLC:
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > >
> > > > Hi,  Kilian Weniger.
> > > >
> > > > Thanks for the detailedl comments.
> > > >
> > > > Please see the inline comments for the HIOPT draft.
> > > >
> > > >
> > > > ------- Original Message -------
> > > > Sender : Kilian Weniger<Kilian.Weniger@eu.panasonic.com>
> > > > Date : 2007-02-16 17:31
> > > > Title : RE: [Mip6] WGLC:
> > > draft-ietf-mip6-bootstrapping-integrated-02
> > > >
> > > > Hi,
> > > >
> > > > please find below some comments about
> > > > draft-ietf-mip6-bootstrapping-integrated-02.
> > > >
> > > > The draft is well written and easy to understand (thanks to
> > > > figures and
> > > > message sequence text). However, some details and corner
> > > > cases are not
> > > > addressed, which may need to be specified, e.g.:
> > > >
> > > > - How does the NAS/relay map a DHCP request received from a
> > > > specific MN
> > > >   to the cached home network information previously received
> > > > from AAAH
> > > >   for this MN, so that it can include the correct home network
> > > >   information in a received DHCP request?
> > > >
> > > >
> > > >
> > > > Hiopt>> The mapping mechanism is added in section 4.3 of the
> > > > latest version of the document (hiopt-02).
> > >
> > > It should be in section 4.2, since my question was related to
> > the DHCP
> > > relay behaviour. Maybe I missed it, but I can't see any
> > related text in
> > > section 4.2 of hiopt-02 about mapping of home information
> > received from
> > > AAA server to DHCP request received from MN. But Kuntal
> > answered to my
> > > question in his reply email.
> > >
> > > >
> > > > The information is mapped based on NAI not by NAS but by DHCP
> > > > server. Rrefer to hiopt-02 for more details.
> > > >
> > > >
> > > > - What is the conceptual data structure needed for this in
> > > > the NAS/DHCP
> > > >   relay?
> > > > - Any default value for how long NAS should cache home network
> > > >   information received from AAA for a specific MN (i.e.,
> > when is NAS
> > > >   allowed to delete cache entry?)? If this is specified in
> > > > [MIP6-Dime]
> > > >   or [MIP6-RADIUS] it should be mentioned and referenced.
> > > >
> > > > Hiopt>> This is implementation-specific. I'm not sure we need
> > > > to describe down to the smallest detail.
> > >
> > > A value doesn't need to be mandated, but I think some=20
> guidance to the
> > > implementor would be good.
> > >
> > > >
> > > >
> > > > - What should NAS do if DHCP request with Home network=20
> identifier
> > > >   option is received from a MN and NAS doesn't find valid
> > > > home network
> > > >   information for this MN in its cache (e.g., since the
> > cache entry
> > > >   has expired)?
> > > >
> > > >
> > > >
> > > > Hiopt>>In that case, there is nothing NAS can do. If the
> > > > corresponding information
> > > >
> > > > is configured on the DHCP server (for e.g.,
> > > > pre-configuration), the server will
> > > > provide it. Otherwise, it will reply with 0-lengh option.
> > >
> > > ok. My comment was that this should be documented (i.e.,=20
> DHCP server
> > > must reply with 0-lengh option in this case)
> > >
> > > >
> > > >
> > > > - What should DHCP relay/server do if the MN does not=20
> include the
> > > >   OPTION_CLIENTID in the DHCP request or if
> > > OPTION_MIP6-RELAY-Option
> > > >   is missing in request?
> > > >
> > > >
> > > >
> > > >
> > > > Hiopt>> The existing DHCP options are handled according to
> > > [RFC 3315].
> > > >
> > > > The request not including OPTION_CLIENTID is discarded in the
> > > > relay/server
> > > >
> > > > as described in 15.4 of [RFC 3315].
> > >
> > > ok.
> > >
> > > >
> > > >
> > > > The draft may need better aligned with [HIOPT]. For instance,
> > > > it is not
> > > > clear to me how exactly the home network identifier option
> > > > and the home
> > > > network information option specified in [HIOPT] are allowed
> > > > to be used
> > > > in draft-ietf-mip6-bootstrapping-integrated-02:
> > > >
> > > > - [HIOPT] supports home address allocation. This is not
> > mentioned in
> > > >   draft-ietf-mip6-bootstrapping-integrated-02. Is this
> > forbidden or
> > > >   allowed or out-of-scope? If allowed, when does NAS set the
> > > > A-flag in
> > > >   the home network identifier option?
> > > >
> > > >
> > > >
> > > > Hiopt>> NAS SHOULD not modify the Home Network=20
> Identifier option.
> > > > The A-flag is set to 0/1 only by the mobile node. If there is
> > > > home address
> > > > information at NAS that was acquired during AAA transaction,
> > > > it is delivered
> > > > to the DHCP server with MIP6-Relay option. (Refer hiopt-02.txt)
> > >
> > > I was aware of HoA allocation support in [HIOPT]. My question was
> > > whether it is supported in
> > > draft-ietf-mip6-bootstrapping-integrated-02
> > > as well, since HoA allocation is not mentioned there.
> > >
> > > >
> > > >
> > > > - Is it allowed that multiple HA addresses are returned in
> > > the home
> > > >   network information option?
> > > >
> > > >
> > > >
> > > > Hiopt>> It is allowed by using multiple home network
> > > > information option.
> > > >
> > > >   "Multiple sub-options may exist in a Home Network
> > Information option
> > > >
> > > >    to carry more than one home information." (in section 3.3.1)
> > > >
> > > >
> > > > - [HIOPT] allows that the home network identifier option
> > > includes an
> > > >   identifier of a target network, which is different=20
> from home or
> > > >   visited network of MN. This is not mentioned in
> > > >   draft-ietf-mip6-bootstrapping-integrated-02. Is this=20
> allowed or
> > > >   forbidden?
> > > >
> > > >
> > > >
> > > > Hiopt>> A target network may or may not be home network of
> > > the MN.
> > >
> > > good. I guess "home network" means "home MSP" in this case, right?
> > > According to RFC4640, the "home MSP" is MN's MSA=20
> providing mobility
> > > service to MN.
> > > According to Kuntal's comment, also MSPs other than MSA (or
> > "home MSP")
> > > and ASP are supported as target networks. If this is true for
> > hiopt (and
> > > it should be if it is true for
> > > draft-ietf-mip6-bootstrapping-integrated-02), then it=20
> seems that the
> > > hiopt draft also uses the term "home MSP" differently=20
> than defined in
> > > RFC4640. For instance, section 4.3, case C (id-type 2) says
> > >
> > > "In case the server cannot not find any home information=20
> neither for
> > >    the local network nor for the *home MSP*, it MUST return a Home
> > > Network
> > >    Information option with the 0-length data."
> > >
> > > This would restrict HA/HoA allocation from ASP and MSA=20
> (=3Dhome MSP). I
> > > guess you also want to support allocation from MSPs other
> > > than ASP and
> > > MSA, no? So shouldn't "home MSP" be replaced by "any=20
> other MSP with
> > > roaming relationship to MN's MSA"?
> > >
> > > Same for id-type 1: section 3.1 says
> > >
> > >
> > > "          id-type
> > >
> > >              The type of Home Network Identifier:
> > >
> > >                      0    Visited domain (local ASP)
> > >
> > >                      1    Home domain (home MSP)
> > > ....
> > >    Id-type 1 indicates the mobile node is interested in=20
> learning the
> > >    home network information that pertains to the given realm.
> >  This type
> > >    can be used to discover home agents that are hosted by a
> > > user's home
> > >    domain (as indicated by his/her NAI-based username -- user@
> > >    HomeRealm).  The Home Network Identifier field MUST be=20
> set to the
> > >    target home MSP.  "
> > >
> > > This text implies that HA/HoA allocation from other MSPs than
> > > home MSP
> > > (which is equal to MSA) is not supported with id-type 1, even
> > if those
> > > MSPs have a roaming relationship with the MN's MSA. Is this true?
> > >
> > > Regards,
> > >
> > > Kilian
> > >
> > > >
> > > > In current draft, the server is supposed to provide the HA
> > > > information if it has
> > > >
> > > > the corresponding information. If the given HA does not
> > > > function as HA for
> > > >
> > > > the requesting MN, it will reply with the BA status =3D 132 or =
133
> > > >
> > > > (Not home subnet / home agent for this mobile node) during
> > > > MN's registration.
> > > >
> > > >
> > > > - Which HA information should the MN use if it receives,
> > > > e.g., an FQDN
> > > >   and a HA address in DHCP reply? [HIOPT] refers to section
> > > 3.6 of
> > > >   draft-ietf-mip6-bootstrapping-integrated-01, but this
> > > > section doesn't
> > > >   exist in draft-ietf-mip6-bootstrapping-integrated-02=20
> anymore...
> > > >
> > > >
> > > >
> > > >
> > > > Hiopt>> It is within the MN's own discretion as follows.
> > > >
> > > > I don't think it should be standardized in HIOPT document.
> > > >
> > > > "For example, if the mobile node acquires both IPv6
> > > > address(es) and FQDN(s)
> > > >  of the home agents, it may try to use the address
> > > > information of the home agent(s) first."
> > > >
> > > >
> > > >
> > > >
> > > > Some other comments:
> > > >
> > > > - It would be good to have a section, which explicitly states
> > > >   assumptions and applicability of the protocol. This
> > should include:
> > > >     - MSA and ASA must be co-located (i.e., integrated scenario)
> > > >     - AAA infrastructure assumed and some kind of roaming
> > > >         relationship between ASP and MSA/ASA is required
> > > >     - MSP is either co-located with ASP or MSA or both
> > > >         (Or are other target networks allowed; see above)?
> > > >     - DHCP relay and NAS must be co-located
> > > >
> > > > - At some places in the text the use of the term "MSP" is
> > > ambiguous,
> > > >   since MSP can refer to at least home and visited network.
> > Better
> > > >   use "home MSP" for MSP in home network.
> > > >     - e.g., section 3.1:
> > > >   "Note that a home agent for usage
> > > >    with the mobile node might be selected in the access service
> > > >    provider's network or alternatively in the *home*
> > > mobility service
> > > >    provider's network."
> > > >     - or in section 3.2:
> > > >   "The message flows for home agent
> > > >    allocation in the ASP and the *home* MSP are illustrated
> > > below.
> > > >     - or in section 3.2.1:
> > > >   "3.2.1.  Home Agent allocation in the *home* MSP",
> > > >   "(4)... mobile node is requesting home agent=20
> information in the
> > > >   *home* MSP..."
> > > >
> > > > - Section 3.3 currently mentions DNS-based HA address
> > > > discovery method
> > > >   only, but [BOOT-SPLIT] also specifies an anycast-based HA
> > address
> > > >   discovery method. Either both or none should be mentioned.
> > > >
> > > > - The title of draft-ietf-mip6-bootstrapping-integrated-02
> > can cause
> > > >   the impression that the draft defines a complete bootstrapping
> > > >   procedure. But draft-ietf-mip6-bootstrapping-integrated-02
> > > > defines a
> > > >   method for HA address assignment only. I think this is
> > misleading.
> > > >   Why not name the draft according to what it specifies
> > > (e.g., "HA
> > > >   address assignment using DHCP and AAA" or "HA address
> > > > assignment for
> > > >   the integrated scenario using DHCP and AAA" instead of
> > > >   "MIP6-bootstrapping for the integrated scenario")?
> > > >
> > > > Regards,
> > > >
> > > > Kilian
> > > >
> > > > > -----Original Message-----
> > > > > From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> > > > > Sent: Mittwoch, 14. Februar 2007 19:10
> > > > > To: mip6@ietf.org
> > > > > Subject: [Mip6] WGLC:
> > > draft-ietf-mip6-bootstrapping-integrated-02
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > This is a MIP6 Working group last call for the WG I-D:
> > > > > "MIP6-bootstrapping for the Integrated Scenario",
> > > > > draft-ietf-mip6-bootstrapping-integrated-02.txt
> > > > >
> > > > > I-D:
> > > > > http://ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-
> > > > > integrated-dhc
> > > > > -02.txt
> > > > >
> > > > > Please review and submit your comments to the authors or
> > > > the mailing
> > > > > list. The WGLC will expire on March 1st, 07.
> > > > >
> > > > > -Chairs
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Mip6 mailing list
> > > > > Mip6@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > > >
> > > > >
> > > >
> > > >
> > > > Panasonic R&D Center Germany GmbH
> > > > 63225 Langen, Hessen, Germany
> > > > Reg: AG Offenbach (Hessen) HRB 33974
> > > > Managing Director: Thomas Micke
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > Panasonic R&D Center Germany GmbH
> > > 63225 Langen, Hessen, Germany
> > > Reg: AG Offenbach (Hessen) HRB 33974
> > > Managing Director: Thomas Micke
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> >=20
> >=20
> > Panasonic R&D Center Germany GmbH
> > 63225 Langen, Hessen, Germany
> > Reg: AG Offenbach (Hessen) HRB 33974
> > Managing Director: Thomas Micke
> >=20
>=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=20
> 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
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Tue Mar 06 11:31:41 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOcYv-0007zP-CN; Tue, 06 Mar 2007 11:30:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOcYt-0007z9-8v
	for mip6@ietf.org; Tue, 06 Mar 2007 11:30:51 -0500
Received: from cluster-b.mailcontrol.com ([217.68.146.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOcYs-0007dr-6u
	for mip6@ietf.org; Tue, 06 Mar 2007 11:30:51 -0500
Received: from rly24b.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly24b.srv.mailcontrol.com (MailControl) with ESMTP id
	l26GN2uo000320
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Tue, 6 Mar 2007 16:30:41 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly24b.srv.mailcontrol.com (MailControl) id l26Fu8b1020150
	for mip6@ietf.org; Tue, 6 Mar 2007 15:56:08 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly24b-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l26Fu01R019404; Tue, 06 Mar 2007 15:56:08 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 0bd7_54806bf0_cbf8_11db_99aa_0030482aac25;
	Tue, 06 Mar 2007 16:35:36 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007030616553781-27957 ;
	Tue, 6 Mar 2007 16:55:37 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.152,BAYES_00: -1.665,TOTAL_SCORE: -1.817
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 6 Mar 2007 17:00:33 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
In-Reply-To: <C24CB51D5AA800449982D9BCB90325134F21CD@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAAA+ifwALlocQAACBjAsA==
References: <C24CB51D5AA800449982D9BCB90325134F201E@NAEX13.na.qualcomm.com>
	<4D2F935F08D41A4C8866693F4F0D7C4F01278512@lan-ex-01.panasonic.de>
	<C24CB51D5AA800449982D9BCB90325134F21CD@NAEX13.na.qualcomm.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F01278714@lan-ex-01.panasonic.de>
Date: Tue, 6 Mar 2007 16:52:29 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MailControl A-07-06-90 (www.mailcontrol.com) on 10.66.1.134
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.2 (+)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935
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 Vidya,=20

> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]=20
> Sent: Dienstag, 6. M=E4rz 2007 04:31
> To: Kilian Weniger
> Cc: Mobile IPv6 Mailing List; Alper Yegin
> Subject: RE: [Mip6] WGLC: Review=20
> ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
>=20
> Hi Kilian,
> I must say that I'm still confused :) Specifically,
> =20
> 1. What privacy are we talking about here and who is the attacker? For
> instance, are we talking about privacy of the HoA/CoA from=20
> CNs (here, CN
> would be the potential attacker)? Or, are we talking about entities on
> path between the MN and HA being able to know the HoA-CoA mapping? Or,
> are we just generally talking about even an off-path entity being able
> to obtain the MN's HoA (say, via DNS or something)? It seems=20
> to me like
> you are talking about the last one, but, I'm not sure.=20

There are multiple possible scenarios. The point is that the attacker =
only needs to know the MN's HoA (as opposed to the CoA) to find out the =
MN's location, if the MN uses a local HA and the attacker knows that. =
This is especially a problem, since the attacker can be off-path. Such =
attacker can learn the local HoA by monitoring the MN's DNS entry =
(assuming the MN updates DNS with its local HoA) or by acting as CN, =
e.g., by initiating a SIP session with the MN. An on-path attacker could =
find out the HoA by eavesdropping the traffic.=20

Of course, the attacker must additionally be able to associate the =
learned HoA (which is typically dynamically assigned to the MN) with a =
specific MN, i.e., it must know an associated identity. This may, e.g., =
be possible:
- with the FQDN for the scenario where the attacker monitors the MN's =
DNS entry and the MN updates its DNS entry with a local HoA=20
- with information from higher layers (e.g., SIP URI, voice/answering =
machine in case of voice call, etc) for the scenario where the attacker =
acts as CN (or eavesdrops the traffic to/from the MN).

>=20
> 2. Why is an MN that is interested in privacy updating the DNS record
> with its HoA? That seems counter-intuitive to me. Updating DNS with an
> address is as good as publishing the address on a public=20
> website (or an
> intranet, when DNSSEC is used) :) So, it sounds to me like if an MN
> wants to keep its HoA location private, it would not be=20
> updating the DNS
> record with its HoA. Or, if the MN needs to get its DNS record updated
> and if the MN's policy is to get a local HA for optimal=20
> routing, the MN
> is clearly not interested in such privacy. Alternately, if=20
> the operator
> policy is to assign a local HA, the MN must either choose to=20
> not publish
> its HoA using DNS (if it wants such privacy) or accept that=20
> there is no=20

This is exactly what the text in the security section is about. The =
purpose of the text is to raise awareness of the privacy issue that a =
local HoA contains location information (as opposed to a HoA that is =
non-local, which is the typical case in MIPv6). The text basically =
recommends that, if location privacy is required by the MN, the MN =
should either not reveal the local HoA (i.e., no DNS updates for local =
HoA and not use a local HoA for sessions with untrusted CNs) or hide the =
fact that the HoA is local. The latter may be out of control of the MN, =
e.g., if local HA assignment is enforced by the operator's policy.

> privacy. It simply cannot be both ways :)=20

Right. With the current mechanisms, a MN basically has to choose between =
optimized routing and location privacy. Mobopts is working on solutions =
to achieve both simultaneously.

>=20
> 3. If you meant any disclosure of HoA/CoA mapping to=20
> entities, that is a
> problem that is unrelated to any DNS updates. However, such a problem
> exists regardless of the HA location, since the CoA is the one that
> really discloses the current location of the MN and that topologically
> identifies the location irrespective of where the HoA is anchored.=20
>=20

I agree, but the problem of disclosing the HoA/CoA mapping (e.g., in =
MIPv6 route optimization mode) is not related to this specific issue. =
The privacy issue I was talking about is due to a HoA that contains =
location information, and that is only the case for a local HoA.

Hope this resolves the confusion.

Regards,

Kilian

> Thanks,
> Vidya
>=20
> > -----Original Message-----
> > From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]=20
> > Sent: Friday, March 02, 2007 4:45 AM
> > To: Narayanan, Vidya
> > Cc: Mobile IPv6 Mailing List; Alper Yegin
> > Subject: RE: [Mip6] WGLC: Review=20
> > ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
> >=20
> > Hi Vidya,
> >=20
> > I'll comment on your questions about the location privacy=20
> > issue described in the security considerations section, since=20
> > the text was provided by James and me. However, the initial=20
> > text was longer, maybe we cut too much and need to add some=20
> > more text again to make the issue clear.=20
> >=20
> > I don't agree with removing the text as Alper suggested.=20
> > IMHO, the text describes a valid security issue that that=20
> > implementors should be aware of and that can be avoided when=20
> > following the recommendations in the text. Thus, the text is=20
> > important IMHO.
> >=20
> > The issue is the following:
> >=20
> > A HoA anchored at a local HA (henceforth called local HoA)=20
> > has a prefix belonging to the access network the MN is=20
> > currently attached to.
> > Consequently, a local HoA contains some location information.=20
> > If any entity 1. knows the MN's HoA and 2. knows that the=20
> > corresponding HA is currently a *local* HA, it can infer the=20
> > MN's location from the local HoA prefix.
> >=20
> > The attacker (any node that is not authorized to get the MN's=20
> > location) can get the MN's location if
> >=20
> > 1. If the attacker can obtain the MN's local HoA, e.g., by=20
> > monitoring the DNS entry (in case the MN's DNS entry is=20
> > always updated after
> > bootstrapping) or by initiating communication with the MN (if=20
> > the MN will use the local HoA for optimized communication) or=20
> > by eavesdropping the MN's traffic.
> >=20
> > 2. If the attacker knows that the HoA obtained in 1 is local.=20
> > This is possible under certain circumstances, e.g., when a=20
> > MN's or an operator's policy is that the MN shall always try=20
> > to bootstrap with a local HA when entering an ASP's network=20
> > (this may make sense for routing efficiency
> > reasons) and the attacker is aware of this policy.
> >=20
> > See some more comments inline.
> >=20
> > >    - The section currently states, "If the home agent=20
> > selected by the=20
> > > mobile node is local or nearby, (as in section 3.2.2),=20
> > disclosing the=20
> > > mobile node's home address (e.g., by updating the mobile=20
> > node's FQDN=20
> > > in the DNS) has the potential to expose some information=20
> about the=20
> > > mobile node's location." I don't understand the intended=20
> > implication=20
> > > here. How is this different from an HA in the MSP=20
> > performing the DNS=20
> > > update?
> >=20
> > If a HA is not local, the corrsponding HoA prefix does not=20
> > contain location information and the issue described above=20
> > doesn't exist. Maybe we should add something like "A local=20
> > HoA contains location information, since the prefix is linked=20
> > to the MN's current access network.".
> >=20
> > >=20
> > >    - The next paragraph states, "...For instance, if an=20
> > attacker knows=20
> > > that the mobile node's home agent selection policy is to=20
> bootstrap=20
> > > with a new local home agent whenever entering a new=20
> network (e.g.,=20
> > > because the mobile node wants to improve routing efficiency in=20
> > > Bi-directional Tunneling mode), the attacker can track the mobile=20
> > > node's movement if it is aware of the mobile node's current home=20
> > > addresses." The MN's movement is tracked by the attacker=20
> > using what?=20
> > > The HoAs are changing with every new HA in every local=20
> network. If=20
> > > anything, this should make tracking the MN more=20
> difficult. I don't=20
> > > follow the discussion in that paragraph or the conclusion.
> >=20
> > If the attacker monitors the DNS entry of the MN and if the=20
> > DNS entry of the MN is always updated with a new local HoA=20
> > after bootstrapping with a new local HA, the attacker can=20
> > track the MN's movement to some extent.
> >=20
> > >=20
> > >    - Finally, the last paragraph states, "Consequently, if a high=20
> > > level of location privacy is desired, a mobile node should=20
> > not switch=20
> > > to local home agents in an eager manner or should not=20
> > reveal its home=20
> > > address to untrusted nodes. Furthermore, the disclosure of policy=20
> > > information that can help locating the mobile node should=20
> > be carefully=20
> > > considered." Given that this is first discussion of=20
> privacy in the=20
> > > document, what does "high level of location privacy" mean?=20
> > If there is=20
> > > such a
> >=20
> > The "level of location privacy" refers to the granularity of=20
> > disclosed location information. For some users it may be=20
> > acceptable to disclose the prefix of the current access=20
> > network, while it is not acceptable to disclose the current=20
> > AR. Such "access network-level" of location privacy can,=20
> > e.g., be achieved with localized MM, where a MN's MIPv6 CoA=20
> > is equal to the MN's PMIP-HoA anchored at a local PMIP-HA. In=20
> > this case, an attacker acting as correspondent node could at=20
> > most learn the MN's current access network (from the MN's CoA=20
> > in MIPv6 route optimization mode).
> >=20
> > For other people this "level" of location privacy is not acceptable.
> > They have stronger requirements on location privacy, where=20
> > the attacker cannot figure out the current access network.=20
> > For instance, some users don't want that it is possible to=20
> > find out that they are on a business trip or on vacation in=20
> > another country (e.g., to prevent that someone uses this=20
> > information for a burglary). This was referred to as "high=20
> > level" of location privacy. Maybe we need to add some text=20
> about this.
> >=20
> > > thing, what is
> > > then a "lower level of location privacy" and how is that achieved?
> > > Further, it is not clear as to what element of privacy is=20
> needed or=20
> > > which elements the privacy is needed from. This text is=20
> > recommending=20
> > > against using local home agents - is this to provide=20
> > privacy from the=20
> > > local network? If this is only about providing privacy from=20
> > > correspondent and other observing nodes, I don't understand the=20
> > > difference made by local or remote HAs. Also, I don't follow the=20
> > > disclosure of policy information - this document is only=20
> > discussing HA=20
> > > bootstrapping; is there such policy information that may be=20
> > disclosed=20
> > > leading to this privacy concern?
> >=20
> > The policy information refers to the MN's policy to eagerly=20
> > bootstrap with a local HA and updating the HoA when entering=20
> > a new network.
> >=20
> > Regards,
> >=20
> > Kilian
> >=20
> >=20
> > Panasonic R&D Center Germany GmbH
> > 63225 Langen, Hessen, Germany
> > Reg: AG Offenbach (Hessen) HRB 33974
> > Managing Director: Thomas Micke
> >=20
> >=20
> >=20
>=20
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



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



From mip6-bounces@ietf.org Tue Mar 06 15:55:53 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOggs-0003Qw-KH; Tue, 06 Mar 2007 15:55:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOgci-0005Xh-5q; Tue, 06 Mar 2007 15:51:04 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HOgch-0000Y7-Ag; Tue, 06 Mar 2007 15:51:04 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id EDEB32ACD5;
	Tue,  6 Mar 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HOgbj-000672-Mc; Tue, 06 Mar 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HOgbj-000672-Mc@stiedprstage1.ietf.org>
Date: Tue, 06 Mar 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-hareliability-01.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
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		: Home Agent Reliability Protocol
	Author(s)	: R. Wakikawa
	Filename	: draft-ietf-mip6-hareliability-01.txt
	Pages		: 45
	Date		: 2007-3-6
	
The home agent can be a single point of failure when Mobile IPv6 is
   used in a system.  It is critical to provide home agent reliability
   in the event of a home agent crashing or becoming unavailable.  This
   would allow another home agent to take over and continue providing
   service to the mobile nodes.  This document describes the problem
   scope briefly and provides a mechanism of home agent failure
   detection, home agent state transfer, and home agent switching for
   home agent redundancy and reliability.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mip6-hareliability-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-hareliability-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-3-6140743.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-hareliability-01.txt

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

Content-Type: text/plain
Content-ID: <2007-3-6140743.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Wed Mar 07 04:06:24 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOs5v-0000JS-Bo; Wed, 07 Mar 2007 04:05:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOjvx-0003wK-GT
	for mip6@ietf.org; Tue, 06 Mar 2007 19:23:09 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOjvv-0005CY-4f
	for mip6@ietf.org; Tue, 06 Mar 2007 19:23:09 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l270N5MA022339
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 6 Mar 2007 16:23:05 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l270N2PU013770;
	Tue, 6 Mar 2007 16:23:05 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Mar 2007 16:22:30 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Tue, 6 Mar 2007 16:22:30 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325134F228F@NAEX13.na.qualcomm.com>
In-Reply-To: <0MKoyl-1HOjID2ICZ-0008Tg@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5gALaqrpAALRJzsAABl0UA
References: <C24CB51D5AA800449982D9BCB90325134F21CC@NAEX13.na.qualcomm.com>
	<0MKoyl-1HOjID2ICZ-0008Tg@mrelay.perfora.net>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 07 Mar 2007 00:22:30.0769 (UTC)
	FILETIME=[B1A8BE10:01C7604E]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

> > >
> >=20
> > Yes, but, this would still mean that the AAA server cannot tell the=20
> > difference between a HA it explicitly meant to assign and a=20
> different=20
> > HA that is also allowed to be an EAP authenticator. In other words,=20
> > there is no check here to see if the EAP authenticator is=20
> the same as=20
> > the HA that the AAA meant to assign to the MN. This may lead to the=20
> > AAA server assuming that the MN is served by one HA, when, it is=20
> > really served by a different HA.
>=20
> AAA server can check that. It can compare the IP address of=20
> the AAA client that forwarded the EAP auth with the IP=20
> address of the assigned HA. But....
> this is a bit tricky. The two may not be the same. The AAA=20
> server may need to maintain a table matching a HA IP address=20
> to one or more AAA client IP address(es). This is doable, if=20
> AAA server seeks such a feature.
>=20

I agree it is doable, but, tricky :) That is what I was trying to get
at.. So, we can perhaps just add a couple of sentences about this and
leave it at that.=20

Vidya

> Alper
>=20


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



From mip6-bounces@ietf.org Wed Mar 07 04:06:45 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOs6e-0001d3-JJ; Wed, 07 Mar 2007 04:06:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOjJL-0001By-L0
	for mip6@ietf.org; Tue, 06 Mar 2007 18:43:15 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOjIK-0007su-3C
	for mip6@ietf.org; Tue, 06 Mar 2007 18:42:12 -0500
Received: from [88.233.140.237] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1HOjID2ICZ-0008Tg; Tue, 06 Mar 2007 18:42:09 -0500
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Narayanan, Vidya'" <vidyan@qualcomm.com>,
	"'Mobile IPv6 Mailing List'" <mip6@ietf.org>
Subject: RE: [Mip6] WGLC: Review
	ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Wed, 7 Mar 2007 01:42:02 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5gALaqrpAALRJzsA==
In-Reply-To: <C24CB51D5AA800449982D9BCB90325134F21CC@NAEX13.na.qualcomm.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-ID: <0MKoyl-1HOjID2ICZ-0008Tg@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Provags-ID2: V01U2FsdGVkX18x+0NNaA2cRqIoNucxzr0DHpdorY+PgmvzYOu
	MWIBSo8KbX++SBx0I2TgTvKzRAhl2gTkG3Tj0/fio/DZAb+Bmt
	KpC/DjVBLyXyaYJ6p2Aog==
X-Spam-Score: 1.1 (+)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
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

> > >    - The next paragraph states, "An adversary that is able
> > to modify
> > > home agent information can force the mobile node to use a different
> > > home agent than intended by the MSA.  However, this type of
> > attack can
> > > be detected by the security mechanism between the mobile
> > node and the
> > > home agent." I'm not sure how this attack is detectable by the
> > > security mechanism between the MN and HA - it may be detectable if
> > > IKEv2 PSKs are used between the MN and HA. If IKEv2 with
> > EAP is used,
> > > as long as the HA is able to act as an EAP authenticator
> > and get the
> > > MN authenticated via the AAA server and obtain an MSK, it
> > doesn't seem to be detectable.
> >
> > Not "any" HA on the Internet can act as a pass-through
> > authenticator and talk to the home AAA server of the MN. We
> > shall clarify that in the text.
> >
> 
> Okay.
> 
> > > In
> > > that case, the AAA server wouldn't be able to tell the difference
> > > between this and any other EAP exchange. It is then only
> > detectable if
> > > the AAA server policy prevents use of that HA as an authenticator.
> >
> > Yes, and it should. A AAA server would not be passing MSKs to
> > any one how happens to forward EAP traffic.
> >
> 
> Yes, but, this would still mean that the AAA server cannot tell the
> difference between a HA it explicitly meant to assign and a different HA
> that is also allowed to be an EAP authenticator. In other words, there
> is no check here to see if the EAP authenticator is the same as the HA
> that the AAA meant to assign to the MN. This may lead to the AAA server
> assuming that the MN is served by one HA, when, it is really served by a
> different HA.

AAA server can check that. It can compare the IP address of the AAA client
that forwarded the EAP auth with the IP address of the assigned HA. But....
this is a bit tricky. The two may not be the same. The AAA server may need
to maintain a table matching a HA IP address to one or more AAA client IP
address(es). This is doable, if AAA server seeks such a feature.

Alper




> 
> >
> >
> > >
> > >    - The section currently states, "If the home agent
> > selected by the
> > > mobile node is local or nearby, (as in section 3.2.2),
> > disclosing the
> > > mobile node's home address (e.g., by updating the mobile
> > node's FQDN
> > > in the DNS) has the potential to expose some information about the
> > > mobile node's location." I don't understand the intended
> > implication
> > > here. How is this different from an HA in the MSP
> > performing the DNS update?
> >
> > I'd not mind removing this text.
> >
> 
> That would be fine.
> 
> >
> > >
> > >    - The next paragraph states, "...For instance, if an
> > attacker knows
> > > that the mobile node's home agent selection policy is to bootstrap
> > > with a new local home agent whenever entering a new network (e.g.,
> > > because the mobile node wants to improve routing efficiency in
> > > Bi-directional Tunneling mode), the attacker can track the mobile
> > > node's movement if it is aware of the mobile node's current home
> > > addresses." The MN's movement is tracked by the attacker
> > using what?
> > > The HoAs are changing with every new HA in every local network. If
> > > anything, this should make tracking the MN more difficult. I don't
> > > follow the discussion in that paragraph or the conclusion.
> >
> > I think you have a valid point, and I don't mind removing this text.
> >
> 
> I would support removing this text - I'll respond to Kilian separately
> on this topic.
> 
> >
> > >
> > >    - Finally, the last paragraph states, "Consequently, if a high
> > > level of location privacy is desired, a mobile node should
> > not switch
> > > to local home agents in an eager manner or should not
> > reveal its home
> > > address to untrusted nodes. Furthermore, the disclosure of policy
> > > information that can help locating the mobile node should
> > be carefully
> > > considered." Given that this is first discussion of privacy in the
> > > document, what does "high level of location privacy" mean?
> > If there is
> > > such a thing, what is then a "lower level of location
> > privacy" and how is that achieved?
> > > Further, it is not clear as to what element of privacy is needed or
> > > which elements the privacy is needed from. This text is
> > recommending
> > > against using local home agents - is this to provide
> > privacy from the
> > > local network? If this is only about providing privacy from
> > > correspondent and other observing nodes, I don't understand the
> > > difference made by local or remote HAs. Also, I don't follow the
> > > disclosure of policy information - this document is only
> > discussing HA
> > > bootstrapping; is there such policy information that may be
> > disclosed
> > > leading to this privacy concern?
> >
> > I personally don't mind removing this text either.
> >
> 
> Again, I'll respond to Kilian on the privacy topic in general...
> 
> >
> > >
> > > 5. I noticed a discussion based on Kilian's comments to include the
> > > HoA allocation via DHCP as a possible option. If we decide
> > to include
> > > that, it would be important to talk about how that HoA gets tied to
> > > the SA created between the MN and HA. If the HoA is assinged via
> > > IKEv2, IKEv2 takes care of such a binding. If not, we need
> > to describe
> > > how the address is bound to the SA. The use of DHCP to
> > assign anything
> > > requiring particular security values is tricky to handle
> > and I suggest
> > > that we don't get into that in this draft.
> >
> > I'll leave this to Kuntal.
> >
> > > 6. In general, a number of the security considerations revolving
> > > around packet modification attacks apply equally to the
> > DHCP and DNS solutions.
> > > However, in the DNS case, the use of DNSSEC between the DNS
> > client and
> > > server is the only thing needed to ensure protection against such
> > > attacks. In this case, the security solution needed relies
> > on several
> > > transitive trust relationships - trust between AAA parties,
> > DHCP Relay
> > > Agent and Server, and DHCP client and server. This is not
> > > unreasonable, but, probably worth mentioning.
> >
> > Sure we can mention that. And that's what RFC 4014 is built
> > upon. We are simply using that model, not introducing anything new.
> >
> 
> Agreed.
> 
> Thanks,
> Vidya
> 
> > Thanks again, these are very useful comments.
> >
> > Alper
> >
> >
> >
> > >
> > > Thanks,
> > > Vidya
> > >
> > > _______________________________________________
> > > 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 Mar 07 04:06:52 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOs6m-0001un-21; Wed, 07 Mar 2007 04:06:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOiyp-0005V0-SW
	for mip6@ietf.org; Tue, 06 Mar 2007 18:22:03 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOi0Y-0004GI-MR
	for mip6@ietf.org; Tue, 06 Mar 2007 17:19:47 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 36A4E90046
	for <mip6@ietf.org>; Tue,  6 Mar 2007 17:19:42 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 01235-03 for <mip6@ietf.org>;
	Tue, 6 Mar 2007 17:19:38 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Tue,  6 Mar 2007 17:19:38 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 6 Mar 2007 17:19:38 -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] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Tue, 6 Mar 2007 17:19:38 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDA86@exchtewks2.starentnetworks.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325134F21CE@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Thread-Index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAABUA5gACVGXHAAlGX2EAAl3H0Q
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 06 Mar 2007 22:19:38.0557 (UTC)
	FILETIME=[877A76D0:01C7603D]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 1.1 (+)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
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 Vidya,

Please see my comments inline....

Thanks,
Kuntal


> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> Sent: Monday, March 05, 2007 9:49 PM
> To: Chowdhury, Kuntal; Alper Yegin; Mobile IPv6 Mailing List
> Subject: RE: [Mip6] WGLC: Reviewofdraft-ietf-mip6-bootstrapping-
> integrated-dhc-02
>=20
> Hi Kuntal,
>=20
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Friday, March 02, 2007 8:53 PM
> > To: Alper Yegin; Narayanan, Vidya; Mobile IPv6 Mailing List
> > Subject: RE: [Mip6] WGLC:
> > Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
> >
> >
> >
> > > -----Original Message-----
> > > From: Alper Yegin [mailto:alper.yegin@yegin.org]
> > > Sent: Friday, March 02, 2007 5:26 AM
> > > To: 'Narayanan, Vidya'; 'Mobile IPv6 Mailing List'
> > > Subject: RE: [Mip6] WGLC: Reviewofdraft-ietf-mip6-bootstrapping-
> > > integrated-dhc-02
> > >
> > > >
> > > > 5. I noticed a discussion based on Kilian's comments to
> > include the
> > HoA
> > > > allocation via DHCP as a possible option. If we decide to
include
> > that,
> > > > it would be important to talk about how that HoA gets
> > tied to the SA
> > > > created between the MN and HA. If the HoA is assinged via IKEv2,
> > IKEv2
> > > > takes care of such a binding. If not, we need to describe how
the
> > > > address is bound to the SA. The use of DHCP to assign anything
> > requiring
> > > > particular security values is tricky to handle and I
> > suggest that we
> > > > don't get into that in this draft.
> > >
> > > I'll leave this to Kuntal.
> > >
> > [KC>] Well, I don't understand what is tricky in getting an
> > IPv6 address assigned from DHCP server and using it in the
> > IKEv2 CFG_REQUEST as
> > *requested* INTERNAL_IP6_ADDRESS. This is clearly allowed in RFC
4306.
> > Even mip6-ikev2 spec talks about this:
> >
> > "
> >    The mobile node could suggest a home address that it wants
> > to use in
> >    the CFG_REQUEST.  For example, this could be a home address that
it
> >    was allocated before or could be an address the mobile node auto-
> >    configured from the IPv6 prefix on the home link.  The Home Agent
> >    could let the mobile node use the same home address by setting
the
> >    INTERNAL_IP6_ADDRESS attribute in the CFG_REPLY payload to the
same
> >    home address.  If the home agent wants the mobile node to use a
> >    different home address, it sends a new home address in the
> >    INTERNAL_IP6_ADDRESS attribute in the CFG_REPLY payload.
> > The Mobile
> >    Node MUST stop using its old home address and start using the
newly
> >    allocated home address.
> > "
> >
>=20
>=20
> Yes, requesting a certain address to be assigned in IKEv2 is certainly
> allowed. However, RFC4306 does not cover the case where the client,
> outside the IKEv2 exchange, uses DHCP to obtain an IP address and then
> request that address to be assigned. This has the following
> implications:
>=20
[KC>] Note that in the integrated scenario, the HoA is obtained by the
MN (DHCP Client) NOT as IA_NA/IA_TA options, but as an IP config option
as carried in Home Network Information Option sub-opt-code =3D 3. The
NAS/DHCP server receives this address as part of the Home Network
Information received from the MSA (AAA server). So, there is no state in
the DHCP server for this parameter.

The case when the MN is trying to use an IPv6 address which it obtained
via DHCPv6 IA_NA/IA_TA options as the HoA (INTERNAL_IP6_ADDRESS), is
also possible. Nothing prevents it from doing that. But, that scenario
is outside the scope of the integrated scenario solution.

> - since the MN doesn't really indicate that the IP address was
obtained
> via DHCP, does the HA (IKEv2 responder function, really) know that
that
> was the case?
>=20
[KC>] No it does not. I don't think IKEv2 responder cares how the MN
obtained the INTERNAL_IP6_ADDRESS hint.

> - if the HA is also using a DHCP server to assign addresses, does it
> check to see if the address is available? If the DHCP pool management
is
> done right, it should be the same server from which the MN obtained
its
> HoA to begin with (having two servers managing the same prefix would
be
> a problem). However, if that is the case, is the DHCP server going to
> say that the address is taken? How does it know that the address was
> taken by the same MN?
>=20
[KC>] The address is assigned by the MSA (AAA server returns the address
to the NAS at the time of access auth/authz). The IKEv2 responder
authorizes the MN to use that address (that is requested by the IKEv2
initiator) by interacting with the AAA server in the MSA. If the
authorization fails, the IKEv2 responder may suggest/assign a different
INTERNAL_IP6_ADDRESS address to the MN. This address can be obtained by
the IKEv2 responder out of band (DHCP is one possible option).


> - does the HA know the lease parameters of the DHCP-assigned HoA of
the
> MN? RFC4306 states "INTERNAL_ADDRESS_EXPIRY - Specifies the number of
> seconds that the host can use the internal IP address.  The host MUST
> renew the IP address before this expiry time." This behavior will
allow
> the HA to ensure that the MN is never capable of redirecting traffic
for
> another node by continuing to use the SA with that IP address even
after
> that address expires. If the DHCP process was done outside of IKEv2,
it
> is not clear how that is feasible and how the HA can keep track of
that.
>=20
[KC>] The scenario that you are describing here is applicable when the
MN obtains an IPv6 address via stateful DHCPv6 operation (use IA_NA/TA
options). This case is outside the scope of the integrated scenario
solution, but as I mentioned, it is possible since nothing prevents it
from happening. In such case, the Home Agent / IKEv2 responder need not
know the DHCP lease time for the address that the MN requested/hinted in
INTERNAL_IP6_ADDRESS. It can set the INTERNAL_ADDRESS_EXPIRY field with
a value that it is configured to support. I don't think this value needs
to be coordinated with the DHCP lease time. The DHCP client in the MN
will ensure lease renewal based on DHCP lease timer as per RFC 3315. The
IKEv2 implementation in the MN will ensure the IKEv2/IPsec session is
renewed as per RFC 4306.
=20

>=20
> It doesn't look like the HIOPT draft addresses such issues either. We
> can discuss those issues in the context of the HIOPT draft, but, for
> now, I think not referring to this is a good way to move forward with
> this draft.
>=20
[KC>] N0, HIOPT I-D is not defining stateful DHCP IP address assignment
behavior. So, it should not have to describe these scenarios.

> Hope that helps.
>
[KC>] Your comments do bring up some good points that should be
clarified in the integrated solution I-D. Again, thanks for your
comments.

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

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



From mip6-bounces@ietf.org Wed Mar 07 11:34:06 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOz5J-0000ZC-LJ; Wed, 07 Mar 2007 11:33:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOz5I-0000Z6-Is
	for mip6@ietf.org; Wed, 07 Mar 2007 11:33:48 -0500
Received: from smtp.elet.polimi.it ([131.175.120.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOz5G-00053J-TK
	for mip6@ietf.org; Wed, 07 Mar 2007 11:33:48 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.elet.polimi.it (Postfix) with ESMTP id 7921815DF30
	for <mip6@ietf.org>; Wed,  7 Mar 2007 17:32:48 +0100 (CET)
X-Virus-Scanned: amavisd-new at elet.polimi.it
Received: from smtp.elet.polimi.it ([127.0.0.1])
	by localhost (smtp1.elet.polimi.it [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id BPGJ8iJ9L8ZS for <mip6@ietf.org>;
	Wed,  7 Mar 2007 17:32:48 +0100 (CET)
Received: from laptopcapone (lap-capone.elet.polimi.it [131.175.123.211])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client did not present a certificate)
	by smtp.elet.polimi.it (Postfix) with ESMTP id 9555D15DF32
	for <mip6@ietf.org>; Wed,  7 Mar 2007 17:32:47 +0100 (CET)
From: "Antonio Capone" <capone@elet.polimi.it>
To: <mip6@ietf.org>
Date: Wed, 7 Mar 2007 17:33:38 +0100
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.3028
Thread-Index: Acdg1hEqMbeUeDpGTQOib+v+XhIbfQ==
Message-Id: <20070307163247.9555D15DF32@smtp.elet.polimi.it>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Subject: [Mip6] MOBIQUITOUS 2007: Paper registration deadline approaching
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: capone@elet.polimi.it
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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.

Paper registration deadline is approaching!
Paper Registration Deadline: March 13, 2007
Paper Submission Deadline: March 20, 2007

News: It is my pleasure to announce that MOBIQUITOUS 2007 is
Technical-sponsored by IEEE and IEEE Computer Society.



========================================================================
                          CALL FOR PAPERS

                          MOBIQUITOUS 2007
The 4th Annual International Conference on Mobile and Ubiquitous Systems:
                  Computing, Networking and Services
                      http://www.mobiquitous.org
                 August 6-10, 2007 - Philadelphia, PA
                   In Cooperation with ACM SIGMOBILE
     Technical-sponsored by IEEE and IEEE Computer Society
                  Co-sponsored by Create-Net and ICST

========================================================================

The combination of mobile and ubiquitous computing is emerging as a 
promising new paradigm. Through the use of mobile devices and devices 
embedded in the surrounding physical environments, users can be provided 
transparent computing and communication services at all times and in all 
places. The complexity of providing such services stems from the fact that 
the communication devices and the objects with which they interact may 
both be mobile. The implementation of such a paradigm requires advances in 
wireless network technologies and devices, development of infrastructures 
supporting cognitive environments, discovery and identification of 
ubiquitous computing applications and services, and an understanding of 
the cross-layer interactions between all of these components. The Fourth 
Annual International Conference on Mobile and Ubiquitous Systems: 
Computing, Networking and Services (Mobiquitous-07) will provide a forum 
where practitioners and researchers coming from many areas involved in 
ubiquitous solutions, design and deployment will be able to interact and 
exchange experiences needed to build successful ubiquitous systems. Areas 
addressed by the conference include applications, service-oriented 
computing, middleware, networking, agents, data management and services, 
all with special focus on mobility and ubiquitous computing. The conference 
publications will be considered for inclusion in the following places:
IEEE Xplore, SCI/ISI Web of Knowledge, Inspec, EI(Elsevier)/Scopus, DBLP, 
Directory of Published Proceedings (InterDok), The Collection of Computer 
Science Bibliographies(CSB), EBSCO, British Library, American Mathematical 
Society (AMS), Crossref, German National Library of Science and Technology.

PAPERS: Technical papers describing original, previously unpublished 
research, not currently under review by another conference or journal, are 
solicited. Technical papers clearly identifying how the specific 
contributions fit to an overall working solution are particularly of 
interest. Topics include, but are not limited to, the following feature 
topics as applied to mobile and ubiquitous environments:

- Ubiquitous architectures, systems and applications
- Wearable computing and personal area networks
- Wireless technologies for mobile and ubiquitous
    (Bluetooth, ZigBee, 802.15.x, WiFi)
- Wireless Internet access in ubiquitous systems
- Ad hoc and sensor networks support for ubiquitous computing
- Reconfigurability and personalization of wireless networks
- Wireless/mobile service management and delivery
- Security, privacy and social issues of mobile and ubiquitous systems
- Service and knowledge discovery, matching and composition mechanisms
- Location-based services and tracking in ubiquitous environments
- Context- and location-aware applications
- Agent technologies in ubiquitous, wearable, and mobile systems
- Context modeling, services and frameworks
- Toolkits, testbeds, development environments, and languages for
     ubiquitous computing
- Rapid prototyping of ubiquitous applications
- Ontologies for mobile and ubiquitous computing
- Mobile and ubiquitous data management and processing
- Data replication, migration and dissemination in ubiquitous environments
- Queries, transactions and workflows in mobile and ubiquitous environments
- Multimodal interfaces (speech, video kinetic, tactile)

SUBMISSION INSTRUCTIONS: All paper submissions will be handled 
electronically (see the conference web page for details). Authors should 
prepare an Adobe Acrobat PDF version of their full paper. Papers must not 
exceed 8 pages double column (US Letter size, 8.5 x 11 inches) including 
text, figures and references. The font size must be at least 10 points.

PUBLICATION: All submitted papers will be rigorously reviewed by the 
international technical program committee. Accepted papers will be 
published in the conference proceedings. Papers of particular merit will 
be proposed for publication in the ACM/Kluwer Mobile Networks and 
Applications (MONET) journal.

WORKSHOPS: Several workshops will be run in conjunction with the conference.

The purpose of these workshops is to discuss work in progress and explore 
opportunities for new research related to mobile and ubiquitous systems: 
computing, networking and services. Proposals for workshops should be at 
most four pages in length and should be submitted to Dr. Suman Banerjee 
(suman at cs.wisc.edu) by February 1, 2007.

IMPORTANT DATES:

Workshop Proposal Deadline: February 1, 2007
Paper Registration Deadline: March 13, 2007
Paper Submission Deadline: March 20, 2007
Notification of Acceptance: May 4, 2007
Camera-ready Manuscripts due: June 4, 2007


CONFERENCE ORGANIZING COMMITTEE:

GENERAL CHAIR:
Guohong Cao, The Pennsylvania State University

TECHNICAL PROGRAM CHAIR:
Robin Kravets, University of Illinois at Urbana-Champaign

TECHNICAL PROGRAM CO-CHAIRS:
Anind Dey, Carnegie Mellon University
Hui Lei, IBM Research

WORKSHOP CHAIR:
Suman Banerjee, University of Wisconsin-Madison

DEMO CHAIR:
Hao Zhu, Florida International University

POSTER CHAIR:
Al Harris, Universita di Padova
Dong Xuan, Ohio State University

FINANCE CHAIR:
Karen Decker, ICST

PUBLICATION CHAIR:
Cristina Nita-Rotaru, Purdue university

PUBLICITY CHAIR:
Antonio Capone, Politecnico di Milano
Wensheng Zhang, Iowa State University

LOCAL CHAIR:
Zhen Jiang, West Chester University of Pennsylvania

WEB CHAIR:
Hui Song, Penn State University

CONFERENCE COORDINATOR
Zita Rozsa, ICST

STEERING COMMITTEE
Imrich Chlamtac, Create-Net (chair)
Fausto Giunchiglia, University of Trento
Tom La Porta, Penn State University
Francesco De Pellegrini, Create-Net
Chiara Petrioli, Universita di Roma "La Sapienza"
Krishna Sivalingam, University of Maryland Baltimore County
Michele Zorzi, Universita di Padova

TECHNICAL PROGRAM COMMITTEE:
See  http://www.mobiquitous.org


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



From mip6-bounces@ietf.org Thu Mar 08 15:53:03 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HPPau-0001LJ-To; Thu, 08 Mar 2007 15:52:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HPPYs-0006r5-4K; Thu, 08 Mar 2007 15:50:06 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HPPYr-0007bn-9r; Thu, 08 Mar 2007 15:50:05 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 0C7AC32A8A;
	Thu,  8 Mar 2007 20:50:05 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HPPYq-0007Jq-Tx; Thu, 08 Mar 2007 15:50:04 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HPPYq-0007Jq-Tx@stiedprstage1.ietf.org>
Date: Thu, 08 Mar 2007 15:50:04 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-radius-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

--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		: RADIUS Mobile IPv6 Support
	Author(s)	: K. Chowdhury, et al.
	Filename	: draft-ietf-mip6-radius-02.txt
	Pages		: 32
	Date		: 2007-3-8
	
A Mobile IPv6 node requires a home agent(HA) address, a home
   address(HOA), and IPsec security association with its HA before it
   can start utilizing Mobile IPv6 service.  RFC 3775 requires that some
   or all of these parameters are statically configured.  Ongoing work
   aims to make this information dynamically available to the mobile
   node.  An important aspect of the Mobile IPv6 bootstrapping solution
   is to support interworking with existing authentication,
   authorization and accounting (AAA) infrastructure.  This document
   defines new attributes to facilitate Mobile IPv6 bootstrapping via a
   RADIUS infrastructure.  This information exchange may take place as
   part of the initial network access authentication procedure or as
   part of a separate protocol exchange between the mobile node, the HA
   and the AAA infrastructure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-radius-02.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-radius-02.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-radius-02.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: <2007-3-8135346.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-radius-02.txt

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

Content-Type: text/plain
Content-ID: <2007-3-8135346.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 Fri Mar 09 04:04:56 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HPb11-0000LO-U9; Fri, 09 Mar 2007 04:03:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HPPYw-0006vR-0l; Thu, 08 Mar 2007 15:50:11 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HPPYv-0007cq-8P; Thu, 08 Mar 2007 15:50:09 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E655826F2A;
	Thu,  8 Mar 2007 20:50:05 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HPPYq-0007Jb-Qf; Thu, 08 Mar 2007 15:50:04 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HPPYq-0007Jb-Qf@stiedprstage1.ietf.org>
Date: Thu, 08 Mar 2007 15:50:04 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-04.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)
	Author(s)	: H. Soliman
	Filename	: draft-ietf-mip6-nemo-v4traversal-04.txt
	Pages		: 23
	Date		: 2007-3-8
	
The current Mobile IPv6 and NEMO specification support only IPv6.
   Hence, this specification extends those standards to allow the
   registration of IPv4 addresses and prefixes, respectively, and the
   transport of both IPv4 and IPv6 packets over the tunnel to the HA.
   This specification allows also the Mobile Node to roam over both IPv6
   and IPv4, including the case where Network Address Translation is
   present on the path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-nemo-v4traversal-04.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-mip6-nemo-v4traversal-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-nemo-v4traversal-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-3-8134522.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-nemo-v4traversal-04.txt

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

Content-Type: text/plain
Content-ID: <2007-3-8134522.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 Fri Mar 09 18:17:18 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HPoKD-0002sn-P4; Fri, 09 Mar 2007 18:16:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HPRyW-0002Oi-IV
	for mip6@ietf.org; Thu, 08 Mar 2007 18:24:44 -0500
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPRyV-0001xJ-3k
	for mip6@ietf.org; Thu, 08 Mar 2007 18:24:44 -0500
Received: from [10.20.30.108] (adsl-66-125-125-65.dsl.pltn13.pacbell.net
	[66.125.125.65]) (authenticated bits=0)
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l28NOX81017967
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Thu, 8 Mar 2007 16:24:34 -0700 (MST)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062408eec2164b257049@[10.20.30.108]>
Date: Thu, 8 Mar 2007 15:22:45 -0800
To: MIP6 WB <mip6@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
X-Mailman-Approved-At: Fri, 09 Mar 2007 18:16:35 -0500
Subject: [Mip6] Invitation to the IFARE BoF
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Greetings. There will be a BoF at Prague that might be of interest to 
you. IFARE (IPsec FAilover and REdundancy) will be meeting Wednesday 
morning to discuss our charter and, if that goes well, requirements 
for a protocol to meet the goals in the charter.

The agenda and current proposed charter are at 
<http://www3.ietf.org/proceedings/07mar/agenda/ifare.txt>. If you are 
interested, please join the mailing list (see 
<http://www.vpnc.org/ietf-ipsec-failover/>) and go through the 
reasonably short list archive 
(<http://www.vpnc.org/ietf-ipsec-failover/mail-archive/>). It would 
be grand if everyone at the BoF had read the charter and the proposed 
requirements doc 
(<http://www.ietf.org/internet-drafts/draft-vidya-ipsec-failover-ps-01.txt>).

--Paul Hoffman, Director
--VPN Consortium

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



From mip6-bounces@ietf.org Sat Mar 10 09:08:33 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HQ2Ec-0003GH-Ki; Sat, 10 Mar 2007 09:07:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HQ2Eb-0003FJ-IM
	for mip6@ietf.org; Sat, 10 Mar 2007 09:07:45 -0500
Received: from py-out-1112.google.com ([64.233.166.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQ2Ea-00029r-AZ
	for mip6@ietf.org; Sat, 10 Mar 2007 09:07:45 -0500
Received: by py-out-1112.google.com with SMTP id f47so382785pye
	for <mip6@ietf.org>; Sat, 10 Mar 2007 06:07:44 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:mime-version:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=oKGSM+TZqZ1DgauVDSVcbd09falnjcUL4VzDA5Q1BDxH9YLZbu391GkbuBQ5NOy5rQFSYM72ORE2l3i8YfVUCsqQXByYJGmWX2UGpo9GiDc/hVXpWykQlqlK78NBF1yoAvlzGlmQVvFC27q/p8SsqNjy3hiXIb80nxuLWVbk+W8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:mime-version:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=pvm4Hk5rOtPHuCVvannjcM7v6EMmS2PN7X3vee8beZ0ycb9eH8KWEq7HHxwi3Cxz4KK3hDbDwGDKSuoJvW2728H21SXs0wfzz6lUOJ4aCmQbVJ7oKJxDH5Er5uge1MGU3qpcJEcmGQbTQfYFEeZLpCXTTTVgW795EF2NIDRheIw=
Received: by 10.35.114.16 with SMTP id r16mr6267860pym.1173535663633;
	Sat, 10 Mar 2007 06:07:43 -0800 (PST)
Received: from ?10.0.1.199? ( [219.110.220.105])
	by mx.google.com with ESMTP id x56sm7031940pyg.2007.03.10.06.07.41;
	Sat, 10 Mar 2007 06:07:43 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B8538B1C-00B5-4D71-BD70-2E3F7062DCA6@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Date: Sat, 10 Mar 2007 23:07:09 +0900
To: mip6@ietf.org,
 nemo@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: 
Subject: [Mip6] NDP operation on virtual home link
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello all,

We recently publish draft-wakikawa-mip6-no-ndp-00.txt.
http://tools.ietf.org/id/draft-wakikawa-mip6-no-ndp-00.txt


Abstract
    This document summarizes operations of home agent without using the
    proxy NDP.  The Proxy NDP is mainly used to intercept packets by a
    Home Agent on Mobile IPv6 and NEMO.

We intend to submit this document as an informational doc.

regards,
ryuji

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



From mip6-bounces@ietf.org Sat Mar 10 09:10:39 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HQ2HK-0003nN-Vt; Sat, 10 Mar 2007 09:10:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HQ2HJ-0003nH-T7
	for mip6@ietf.org; Sat, 10 Mar 2007 09:10:33 -0500
Received: from wr-out-0506.google.com ([64.233.184.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQ2HH-0002VC-LP
	for mip6@ietf.org; Sat, 10 Mar 2007 09:10:33 -0500
Received: by wr-out-0506.google.com with SMTP id 71so1629460wri
	for <mip6@ietf.org>; Sat, 10 Mar 2007 06:10:31 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer;
	b=lGdBbAW/hlwq/MDuutUAsmtoBDFhdj5Hs8G9gLU/PvaP/dgVye3y77H+uShuYZtwOMukMwC7qKrwIUlt0bDyW0x5W2vhW04yOj5/5DBgeBWra68VjgamdmzYm4vWaEDvnboN0gF1wlmah/NFL6EmKG3/GVpEuFln3nDqEbRpX4M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer;
	b=jDcVIcJoaKTYbEW9x4I4GIJ7PnUP61/tznyjEbFbhAnajanqqvXus9MymzbPWuJLL1nQwLjjLNRNvGEnZJRyrWPiIxk/I7yOwlE/SLglLNN0JTbHusWDttFHJ047OA2insVabbKhCfa8GvhpG9+/zmUTc9l/Ba/CraQIl5lkxCo=
Received: by 10.35.32.9 with SMTP id k9mr2001155pyj.1173535831130;
	Sat, 10 Mar 2007 06:10:31 -0800 (PST)
Received: from ?10.0.1.199? ( [219.110.220.105])
	by mx.google.com with ESMTP id v56sm6992316pyh.2007.03.10.06.10.29;
	Sat, 10 Mar 2007 06:10:30 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <46757010-4B07-49D5-AD5C-895B59C97869@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: mip6@ietf.org
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Date: Sat, 10 Mar 2007 23:10:03 +0900
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [Mip6] HA reliability draft update
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

We finally updated HA reliability draft according to comments in the  
previous IETF.

http://tools.ietf.org/id/draft-ietf-mip6-hareliability-01.txt

regards
ryuji

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



From mip6-bounces@ietf.org Tue Mar 13 10:38:20 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HR882-0001zh-0z; Tue, 13 Mar 2007 10:37:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HR880-0001zZ-HV
	for mip6@ietf.org; Tue, 13 Mar 2007 10:37:28 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HR87z-0001fo-9P
	for mip6@ietf.org; Tue, 13 Mar 2007 10:37:28 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-4.tower-119.messagelabs.com!1173796646!16841925!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 16151 invoked from network); 13 Mar 2007 14:37:26 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-4.tower-119.messagelabs.com with SMTP;
	13 Mar 2007 14:37:26 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2DEbQGW029374
	for <mip6@ietf.org>; Tue, 13 Mar 2007 07:37:26 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l2DEbMDD015754
	for <mip6@ietf.org>; Tue, 13 Mar 2007 09:37:24 -0500 (CDT)
Message-ID: <45F6B71B.6090304@gmail.com>
Date: Tue, 13 Mar 2007 15:37:15 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [Mip6] One difference between DSMIP6 and other transitioning
	mechanisms
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

One difference between DSMIPv6 transitioning and all other existing 
transitioning mechanisms is that it can offer 2 ways of encapsulating 
IPv6 in IPv4:  IPv6-in-IPv4 and IPv6-in-UDPv4.

Other transitioning mechanisms use only one of those two.

Is this an advantage?  An inconvenient?

For example, if one wants to put together MIPv6 and 6to4 then one can 
traverse some NATs but using only IPv6-in-IPv4 (not in UDP).  Some 
extension may be needed for communicating NAT detection.

If one wants to use MIPv6 and TEREDO with "origin auth" then one would 
have to use IPv6-in-specialexisting-header-in-UDPv4.  One could also use 
IPv6-in-UDPv4 with TEREDO.

Now, can one use DS-MIPv6 and TEREDO at the same time?

Can one use DS-MIPv6 and 6to4 at the same time?

Alex

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From mip6-bounces@ietf.org Tue Mar 13 23:51:38 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRKVQ-0002Vn-BO; Tue, 13 Mar 2007 23:50:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKVO-0002Vh-GR
	for mip6@ietf.org; Tue, 13 Mar 2007 23:50:26 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKVL-0007TF-IF
	for mip6@ietf.org; Tue, 13 Mar 2007 23:50:26 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 035E190011
	for <mip6@ietf.org>; Tue, 13 Mar 2007 22:50:20 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 10888-05 for <mip6@ietf.org>;
	Tue, 13 Mar 2007 22:50:15 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Tue, 13 Mar 2007 22:50:15 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 13 Mar 2007 23:50:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: home network requested by MN may be != assigned network (was: RE:
	[Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
Date: Tue, 13 Mar 2007 23:50:15 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDAF5@exchtewks2.starentnetworks.com>
In-reply-to: <4D2F935F08D41A4C8866693F4F0D7C4F01278715@lan-ex-01.panasonic.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: home network requested by MN may be != assigned network (was:
	RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
thread-index: AcdZUPl3RCOZHB9nQb6+3hPvBup2ywBYXBGgARQFcMAAD4CxkAAf7ZPgAYqfl7A=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
X-OriginalArrivalTime: 14 Mar 2007 03:50:15.0445 (UTC)
	FILETIME=[E0139C50:01C765EB]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd530fb5c702ad6eef32cae6dcb86145
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, heejin.jang@samsung.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kilian,

Sorry for the late follow-up. Please see my reply inline...

-Kuntal

> -----Original Message-----
> From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]
> Sent: Tuesday, March 06, 2007 9:49 AM
> To: Chowdhury, Kuntal
> Cc: Mobile IPv6 Mailing List; heejin.jang@samsung.com
> Subject: RE: home network requested by MN may be !=3D assigned network =
(was:
> RE: [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
>=20
> Hi Kuntal,
>=20
> thanks for the clarification, but it is still not clear to me how
> assignment of HA information pertaining to an MSP X different from ASP =
and
> Home MSP Y (that has trust relationship with MN's MSA) works. Heejin =
and
> you said that in an earlier mail that this is supported, but I can't =
find
> any details in the drafts.
>=20
[KC>] the information of all the home agents assigned in the MSPs (home =
or not) will come in AAA attributes. Each assigned home agent address =
will have an associated FQDN in the AAA attributes. The DHCP server =
stores this info and sends the home agent information that matches the =
FQDN in the home network information field in the DHCP request to the =
FQDN stored (received from AAA).
=20
=20
> Is the MSA allowed to send HA information to the NAS during network
> authentication, which pertains to an MSP X different from the MN's =
home
> MSP Y, so that the NAS/DHCP would associate the received information =
with
> the home MSP domain Y? The NAS/DHCP would then return home information
> pertaining to MSP X to the MN, even though the target network =
requested by
> the MN was (home) MSP Y.
>
[KC>] No, if the MN requested home info for target network X, the DHCP =
server should not return home info for target network Y. I think HIOPT =
says that in such case, the DHCP server may return home info for the =
local network in case the MN can utilize the services of a local home =
agent.

=20
> Or is such assignment only possible if the MN requests a target =
network
> MSP X, which is neither ASP nor Home MSP Y? Since the MSA doesn't know =
the
> target network requested by the MN at the time of network =
authentication,
> would the MSA always send to the NAS during network authentication
> multiple HAs pertaining to all MSPs that the MN is allowed to use and =
the
> DHCP server picks the correct one according to the requested target
> network?
>=20
[KC>] Yes, the MSA does not know a priori which target network's home =
info the MN is going to request. That's why the MSA (AAA server) sends =
all the authorized target network info to the NAS at the time of access =
auth.

> Thanks,
>=20
> Kilian
>=20
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Montag, 5. M=E4rz 2007 17:17
> > To: Kilian Weniger
> > Cc: heejin.jang@samsung.com; Mobile IPv6 Mailing List
> > Subject: RE: home network requested by MN may be !=3D assigned
> > network (was: RE: [Mip6] WGLC:
> > draft-ietf-mip6-bootstrapping-integrated-02)
> >
> > Hi Kilian,
> >
> > If the MSA assigns Home Agent info in domain X which is MN's
> > home MSP and the MN requests for Home Agent info for domain Y
> > (another MSP), the DHCP server may not have that info. In
> > that case, it returns a local Home Agent. I think this is
> > mentioned in HIOPT I-D:
> >
> > "
> > Id-type 1 indicates the mobile node is interested in learning the
> >    home network information that pertains to the given realm.
> >  This type
> >    can be used to discover home agents that are hosted by a
> > user's home
> >    domain (as indicated by his/her NAI-based username -- user@
> >    HomeRealm).  The Home Network Identifier field MUST be set to the
> >    target home MSP.  In case there is no available home
> > information for
> >    the specified home MSP in the DHCP server, the local home
> > information
> >    is provided.
> > "
> >
> > We can clarify this in the integrated I-D as you suggested.
> >
> > Thanks for your comments.
> >
> > -Kuntal
> >
> >
> > > -----Original Message-----
> > > From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]
> > > Sent: Monday, March 05, 2007 3:16 AM
> > > To: Chowdhury, Kuntal
> > > Cc: heejin.jang@samsung.com; Mobile IPv6 Mailing List
> > > Subject: home network requested by MN may be !=3D assigned
> > network (was: RE:
> > > [Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
> > >
> > > Hi Kuntal, Heejin,
> > >
> > > since the MN's MSA is the entity that assigns a home
> > network and an MSP to
> > > the MN, I guess that it is allowed that the MSA assigns a
> > different home
> > > network from a different MSP to the MN than requested by
> > the MN in the
> > > Home Network Identifier DHCP Option. This is needed, e.g.,
> > when the MSA
> > > doesn't have a roaming relationship with the MSP requested
> > by the MN, when
> > > the requested MSP doesn't provide the required service
> > (e.g., DSMIP, NEMO
> > > etc) or when the MSA knows of a better (e.g., less loaded)
> > home network
> > > from a different MSP. I think this is currently not
> > mentioned in the draft
> > > and it would be good to clarify.
> > >
> > > Regards,
> > >
> > > Kilian
> > >
> > >
> > > > -----Original Message-----
> > > > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > > > Sent: Dienstag, 27. Februar 2007 22:02
> > > > To: heejin.jang@samsung.com; Kilian Weniger
> > > > Cc: mip6@ietf.org; Basavaraj Patil
> > > > Subject: RE: RE: RE: [Mip6] WGLC:
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > >
> > > > Thanks Heejin. I think your suggested clarification # 3 is good.
> > > >
> > > > -Kuntal
> > > >
> > > >
> > > > ________________________________________
> > > > From: Heejin Jang [mailto:heejin.jang@samsung.com]
> > > > Sent: Sunday, February 25, 2007 8:45 PM
> > > > To: Kilian Weniger
> > > > Cc: mip6@ietf.org; Basavaraj Patil
> > > > Subject: Re: RE: RE: [Mip6] WGLC:
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > >
> > > > Hi, Kilian.
> > > > Thanks for the comments.
> > > >
> > > > Regarding the use of term, the draft(hiopt) supports all the
> > > > three following networks as target networks
> > > > 1) ASP (MN's currently visited network)
> > > > 2) Home MSP (=3D MSA)
> > > > 3) MSP (network which is nether  ASP nor Home MSP but has
> > > > trust relationship with MN's MSA)
> > > >
> > > > The term 'home MSP' can be ambiguous since it does not include =
3),
> > > > so we will modify it to 'MSP with roaming  relationship with
> > > > MN's MSA' for more clarification.
> > > > Thanks.
> > > >
> > > > Regards,
> > > > Heejin.
> > > >
> > > > ------ Original Message -------
> > > > Sender : Kilian Weniger<Kilian.Weniger@eu.panasonic.com>
> > > > Date : 2007-02-22 23:00
> > > > Title : RE: RE: [Mip6] WGLC:
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > >
> > > > Hi Heejin,
> > > >
> > > > thanks for your comments, see my replies inline.
> > > >
> > > > Please note that the comments in my mail were referring to
> > > > draft-ietf-mip6-bootstrapping-integrated-02. And since
> > the reference
> > > > [HIOPT] in draft-ietf-mip6-bootstrapping-integrated-02 is
> > hiopt-01, I
> > > > didn't consider hiopt-02.
> > > >
> > > > > -----Original Message-----
> > > > > From: Heejin Jang [mailto:heejin.jang@samsung.com]
> > > > > Sent: Dienstag, 20. Februar 2007 08:31
> > > > > To: Kilian Weniger
> > > > > Cc: Basavaraj Patil; mip6@ietf.org
> > > > > Subject: Re: RE: [Mip6] WGLC:
> > > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > > >
> > > > > Hi,  Kilian Weniger.
> > > > >
> > > > > Thanks for the detailedl comments.
> > > > >
> > > > > Please see the inline comments for the HIOPT draft.
> > > > >
> > > > >
> > > > > ------- Original Message -------
> > > > > Sender : Kilian Weniger<Kilian.Weniger@eu.panasonic.com>
> > > > > Date : 2007-02-16 17:31
> > > > > Title : RE: [Mip6] WGLC:
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > > >
> > > > > Hi,
> > > > >
> > > > > please find below some comments about
> > > > > draft-ietf-mip6-bootstrapping-integrated-02.
> > > > >
> > > > > The draft is well written and easy to understand (thanks to
> > > > > figures and
> > > > > message sequence text). However, some details and corner
> > > > > cases are not
> > > > > addressed, which may need to be specified, e.g.:
> > > > >
> > > > > - How does the NAS/relay map a DHCP request received from a
> > > > > specific MN
> > > > >   to the cached home network information previously received
> > > > > from AAAH
> > > > >   for this MN, so that it can include the correct home network
> > > > >   information in a received DHCP request?
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>> The mapping mechanism is added in section 4.3 of the
> > > > > latest version of the document (hiopt-02).
> > > >
> > > > It should be in section 4.2, since my question was related to
> > > the DHCP
> > > > relay behaviour. Maybe I missed it, but I can't see any
> > > related text in
> > > > section 4.2 of hiopt-02 about mapping of home information
> > > received from
> > > > AAA server to DHCP request received from MN. But Kuntal
> > > answered to my
> > > > question in his reply email.
> > > >
> > > > >
> > > > > The information is mapped based on NAI not by NAS but by DHCP
> > > > > server. Rrefer to hiopt-02 for more details.
> > > > >
> > > > >
> > > > > - What is the conceptual data structure needed for this in
> > > > > the NAS/DHCP
> > > > >   relay?
> > > > > - Any default value for how long NAS should cache home network
> > > > >   information received from AAA for a specific MN (i.e.,
> > > when is NAS
> > > > >   allowed to delete cache entry?)? If this is specified in
> > > > > [MIP6-Dime]
> > > > >   or [MIP6-RADIUS] it should be mentioned and referenced.
> > > > >
> > > > > Hiopt>> This is implementation-specific. I'm not sure we need
> > > > > to describe down to the smallest detail.
> > > >
> > > > A value doesn't need to be mandated, but I think some
> > guidance to the
> > > > implementor would be good.
> > > >
> > > > >
> > > > >
> > > > > - What should NAS do if DHCP request with Home network
> > identifier
> > > > >   option is received from a MN and NAS doesn't find valid
> > > > > home network
> > > > >   information for this MN in its cache (e.g., since the
> > > cache entry
> > > > >   has expired)?
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>>In that case, there is nothing NAS can do. If the
> > > > > corresponding information
> > > > >
> > > > > is configured on the DHCP server (for e.g.,
> > > > > pre-configuration), the server will
> > > > > provide it. Otherwise, it will reply with 0-lengh option.
> > > >
> > > > ok. My comment was that this should be documented (i.e.,
> > DHCP server
> > > > must reply with 0-lengh option in this case)
> > > >
> > > > >
> > > > >
> > > > > - What should DHCP relay/server do if the MN does not
> > include the
> > > > >   OPTION_CLIENTID in the DHCP request or if
> > > > OPTION_MIP6-RELAY-Option
> > > > >   is missing in request?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>> The existing DHCP options are handled according to
> > > > [RFC 3315].
> > > > >
> > > > > The request not including OPTION_CLIENTID is discarded in the
> > > > > relay/server
> > > > >
> > > > > as described in 15.4 of [RFC 3315].
> > > >
> > > > ok.
> > > >
> > > > >
> > > > >
> > > > > The draft may need better aligned with [HIOPT]. For instance,
> > > > > it is not
> > > > > clear to me how exactly the home network identifier option
> > > > > and the home
> > > > > network information option specified in [HIOPT] are allowed
> > > > > to be used
> > > > > in draft-ietf-mip6-bootstrapping-integrated-02:
> > > > >
> > > > > - [HIOPT] supports home address allocation. This is not
> > > mentioned in
> > > > >   draft-ietf-mip6-bootstrapping-integrated-02. Is this
> > > forbidden or
> > > > >   allowed or out-of-scope? If allowed, when does NAS set the
> > > > > A-flag in
> > > > >   the home network identifier option?
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>> NAS SHOULD not modify the Home Network
> > Identifier option.
> > > > > The A-flag is set to 0/1 only by the mobile node. If there is
> > > > > home address
> > > > > information at NAS that was acquired during AAA transaction,
> > > > > it is delivered
> > > > > to the DHCP server with MIP6-Relay option. (Refer =
hiopt-02.txt)
> > > >
> > > > I was aware of HoA allocation support in [HIOPT]. My question =
was
> > > > whether it is supported in
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > > as well, since HoA allocation is not mentioned there.
> > > >
> > > > >
> > > > >
> > > > > - Is it allowed that multiple HA addresses are returned in
> > > > the home
> > > > >   network information option?
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>> It is allowed by using multiple home network
> > > > > information option.
> > > > >
> > > > >   "Multiple sub-options may exist in a Home Network
> > > Information option
> > > > >
> > > > >    to carry more than one home information." (in section =
3.3.1)
> > > > >
> > > > >
> > > > > - [HIOPT] allows that the home network identifier option
> > > > includes an
> > > > >   identifier of a target network, which is different
> > from home or
> > > > >   visited network of MN. This is not mentioned in
> > > > >   draft-ietf-mip6-bootstrapping-integrated-02. Is this
> > allowed or
> > > > >   forbidden?
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>> A target network may or may not be home network of
> > > > the MN.
> > > >
> > > > good. I guess "home network" means "home MSP" in this case, =
right?
> > > > According to RFC4640, the "home MSP" is MN's MSA
> > providing mobility
> > > > service to MN.
> > > > According to Kuntal's comment, also MSPs other than MSA (or
> > > "home MSP")
> > > > and ASP are supported as target networks. If this is true for
> > > hiopt (and
> > > > it should be if it is true for
> > > > draft-ietf-mip6-bootstrapping-integrated-02), then it
> > seems that the
> > > > hiopt draft also uses the term "home MSP" differently
> > than defined in
> > > > RFC4640. For instance, section 4.3, case C (id-type 2) says
> > > >
> > > > "In case the server cannot not find any home information
> > neither for
> > > >    the local network nor for the *home MSP*, it MUST return a =
Home
> > > > Network
> > > >    Information option with the 0-length data."
> > > >
> > > > This would restrict HA/HoA allocation from ASP and MSA
> > (=3Dhome MSP). I
> > > > guess you also want to support allocation from MSPs other
> > > > than ASP and
> > > > MSA, no? So shouldn't "home MSP" be replaced by "any
> > other MSP with
> > > > roaming relationship to MN's MSA"?
> > > >
> > > > Same for id-type 1: section 3.1 says
> > > >
> > > >
> > > > "          id-type
> > > >
> > > >              The type of Home Network Identifier:
> > > >
> > > >                      0    Visited domain (local ASP)
> > > >
> > > >                      1    Home domain (home MSP)
> > > > ....
> > > >    Id-type 1 indicates the mobile node is interested in
> > learning the
> > > >    home network information that pertains to the given realm.
> > >  This type
> > > >    can be used to discover home agents that are hosted by a
> > > > user's home
> > > >    domain (as indicated by his/her NAI-based username -- user@
> > > >    HomeRealm).  The Home Network Identifier field MUST be
> > set to the
> > > >    target home MSP.  "
> > > >
> > > > This text implies that HA/HoA allocation from other MSPs than
> > > > home MSP
> > > > (which is equal to MSA) is not supported with id-type 1, even
> > > if those
> > > > MSPs have a roaming relationship with the MN's MSA. Is this =
true?
> > > >
> > > > Regards,
> > > >
> > > > Kilian
> > > >
> > > > >
> > > > > In current draft, the server is supposed to provide the HA
> > > > > information if it has
> > > > >
> > > > > the corresponding information. If the given HA does not
> > > > > function as HA for
> > > > >
> > > > > the requesting MN, it will reply with the BA status =3D 132 or =
133
> > > > >
> > > > > (Not home subnet / home agent for this mobile node) during
> > > > > MN's registration.
> > > > >
> > > > >
> > > > > - Which HA information should the MN use if it receives,
> > > > > e.g., an FQDN
> > > > >   and a HA address in DHCP reply? [HIOPT] refers to section
> > > > 3.6 of
> > > > >   draft-ietf-mip6-bootstrapping-integrated-01, but this
> > > > > section doesn't
> > > > >   exist in draft-ietf-mip6-bootstrapping-integrated-02
> > anymore...
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hiopt>> It is within the MN's own discretion as follows.
> > > > >
> > > > > I don't think it should be standardized in HIOPT document.
> > > > >
> > > > > "For example, if the mobile node acquires both IPv6
> > > > > address(es) and FQDN(s)
> > > > >  of the home agents, it may try to use the address
> > > > > information of the home agent(s) first."
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Some other comments:
> > > > >
> > > > > - It would be good to have a section, which explicitly states
> > > > >   assumptions and applicability of the protocol. This
> > > should include:
> > > > >     - MSA and ASA must be co-located (i.e., integrated =
scenario)
> > > > >     - AAA infrastructure assumed and some kind of roaming
> > > > >         relationship between ASP and MSA/ASA is required
> > > > >     - MSP is either co-located with ASP or MSA or both
> > > > >         (Or are other target networks allowed; see above)?
> > > > >     - DHCP relay and NAS must be co-located
> > > > >
> > > > > - At some places in the text the use of the term "MSP" is
> > > > ambiguous,
> > > > >   since MSP can refer to at least home and visited network.
> > > Better
> > > > >   use "home MSP" for MSP in home network.
> > > > >     - e.g., section 3.1:
> > > > >   "Note that a home agent for usage
> > > > >    with the mobile node might be selected in the access =
service
> > > > >    provider's network or alternatively in the *home*
> > > > mobility service
> > > > >    provider's network."
> > > > >     - or in section 3.2:
> > > > >   "The message flows for home agent
> > > > >    allocation in the ASP and the *home* MSP are illustrated
> > > > below.
> > > > >     - or in section 3.2.1:
> > > > >   "3.2.1.  Home Agent allocation in the *home* MSP",
> > > > >   "(4)... mobile node is requesting home agent
> > information in the
> > > > >   *home* MSP..."
> > > > >
> > > > > - Section 3.3 currently mentions DNS-based HA address
> > > > > discovery method
> > > > >   only, but [BOOT-SPLIT] also specifies an anycast-based HA
> > > address
> > > > >   discovery method. Either both or none should be mentioned.
> > > > >
> > > > > - The title of draft-ietf-mip6-bootstrapping-integrated-02
> > > can cause
> > > > >   the impression that the draft defines a complete =
bootstrapping
> > > > >   procedure. But draft-ietf-mip6-bootstrapping-integrated-02
> > > > > defines a
> > > > >   method for HA address assignment only. I think this is
> > > misleading.
> > > > >   Why not name the draft according to what it specifies
> > > > (e.g., "HA
> > > > >   address assignment using DHCP and AAA" or "HA address
> > > > > assignment for
> > > > >   the integrated scenario using DHCP and AAA" instead of
> > > > >   "MIP6-bootstrapping for the integrated scenario")?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Kilian
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> > > > > > Sent: Mittwoch, 14. Februar 2007 19:10
> > > > > > To: mip6@ietf.org
> > > > > > Subject: [Mip6] WGLC:
> > > > draft-ietf-mip6-bootstrapping-integrated-02
> > > > > >
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > This is a MIP6 Working group last call for the WG I-D:
> > > > > > "MIP6-bootstrapping for the Integrated Scenario",
> > > > > > draft-ietf-mip6-bootstrapping-integrated-02.txt
> > > > > >
> > > > > > I-D:
> > > > > > =
http://ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-
> > > > > > integrated-dhc
> > > > > > -02.txt
> > > > > >
> > > > > > Please review and submit your comments to the authors or
> > > > > the mailing
> > > > > > list. The WGLC will expire on March 1st, 07.
> > > > > >
> > > > > > -Chairs
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Mip6 mailing list
> > > > > > Mip6@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > Panasonic R&D Center Germany GmbH
> > > > > 63225 Langen, Hessen, Germany
> > > > > Reg: AG Offenbach (Hessen) HRB 33974
> > > > > Managing Director: Thomas Micke
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Mip6 mailing list
> > > > > Mip6@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > Panasonic R&D Center Germany GmbH
> > > > 63225 Langen, Hessen, Germany
> > > > Reg: AG Offenbach (Hessen) HRB 33974
> > > > Managing Director: Thomas Micke
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> > > >
> > >
> > >
> > > Panasonic R&D Center Germany GmbH
> > > 63225 Langen, Hessen, Germany
> > > Reg: AG Offenbach (Hessen) HRB 33974
> > > Managing Director: Thomas Micke
> > >
> >
> >
> > "This email message and any attachments are confidential
> > information of Starent Networks, Corp. The information
> > transmitted may not be used to create or change any
> > contractual obligations of Starent Networks, Corp.  Any
> > review, retransmission, dissemination or other use of, or
> > taking of any action in reliance upon this e-mail and its
> > attachments by persons or entities other than the intended
> > recipient is prohibited. If you are not the intended
> > recipient, please notify the sender immediately -- by
> > replying to this message or by sending an email to
> > postmaster@starentnetworks.com -- and destroy all copies of
> > this message and any attachments without reading or
> > disclosing their contents. Thank you."
> >
> >
>=20
>=20
> Panasonic R&D Center Germany GmbH
> 63225 Langen, Hessen, Germany
> Reg: AG Offenbach (Hessen) HRB 33974
> Managing Director: Thomas Micke
>=20


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



From mip6-bounces@ietf.org Wed Mar 14 00:11:03 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRKox-0006Wp-SW; Wed, 14 Mar 2007 00:10:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKox-0006Wj-3U
	for mip6@ietf.org; Wed, 14 Mar 2007 00:10:39 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKow-0002t0-BV
	for mip6@ietf.org; Wed, 14 Mar 2007 00:10:39 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 0B4E090011
	for <mip6@ietf.org>; Tue, 13 Mar 2007 23:10:35 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 11510-05 for <mip6@ietf.org>;
	Tue, 13 Mar 2007 23:10:30 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip6@ietf.org>; Tue, 13 Mar 2007 23:10:30 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 14 Mar 2007 00:10:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
Date: Wed, 14 Mar 2007 00:10:29 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBDAF6@exchtewks2.starentnetworks.com>
In-reply-to: <4D2F935F08D41A4C8866693F4F0D7C4F01278714@lan-ex-01.panasonic.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [Mip6] WGLC:
	Reviewofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
thread-index: Acdcs/wxWEzeVw0GT1e2IbWN7Z0QBAAA+ifwALlocQAACBjAsAGLoQ+A
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>
X-OriginalArrivalTime: 14 Mar 2007 04:10:30.0161 (UTC)
	FILETIME=[B41A9010:01C765EE]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 1094b1c84fa6e846d476f39271f5074f
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 Kilian, Vidya,

I don't see a convergence on this location privacy issue with local HA =
assignment. I will mark this as an open issue for now.

-Kuntal
=20

> -----Original Message-----
> From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]
> Sent: Tuesday, March 06, 2007 9:52 AM
> To: Narayanan, Vidya
> Cc: Mobile IPv6 Mailing List
> Subject: RE: [Mip6] WGLC: Reviewofdraft-ietf-mip6-bootstrapping-
> integrated-dhc-02
>=20
> Hi Vidya,
>=20
> > -----Original Message-----
> > From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> > Sent: Dienstag, 6. M=E4rz 2007 04:31
> > To: Kilian Weniger
> > Cc: Mobile IPv6 Mailing List; Alper Yegin
> > Subject: RE: [Mip6] WGLC: Review
> > ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
> >
> > Hi Kilian,
> > I must say that I'm still confused :) Specifically,
> >
> > 1. What privacy are we talking about here and who is the attacker? =
For
> > instance, are we talking about privacy of the HoA/CoA from
> > CNs (here, CN
> > would be the potential attacker)? Or, are we talking about entities =
on
> > path between the MN and HA being able to know the HoA-CoA mapping? =
Or,
> > are we just generally talking about even an off-path entity being =
able
> > to obtain the MN's HoA (say, via DNS or something)? It seems
> > to me like
> > you are talking about the last one, but, I'm not sure.
>=20
> There are multiple possible scenarios. The point is that the attacker =
only
> needs to know the MN's HoA (as opposed to the CoA) to find out the =
MN's
> location, if the MN uses a local HA and the attacker knows that. This =
is
> especially a problem, since the attacker can be off-path. Such =
attacker
> can learn the local HoA by monitoring the MN's DNS entry (assuming the =
MN
> updates DNS with its local HoA) or by acting as CN, e.g., by =
initiating a
> SIP session with the MN. An on-path attacker could find out the HoA by
> eavesdropping the traffic.
>=20
> Of course, the attacker must additionally be able to associate the =
learned
> HoA (which is typically dynamically assigned to the MN) with a =
specific
> MN, i.e., it must know an associated identity. This may, e.g., be
> possible:
> - with the FQDN for the scenario where the attacker monitors the MN's =
DNS
> entry and the MN updates its DNS entry with a local HoA
> - with information from higher layers (e.g., SIP URI, voice/answering
> machine in case of voice call, etc) for the scenario where the =
attacker
> acts as CN (or eavesdrops the traffic to/from the MN).
>=20
> >
> > 2. Why is an MN that is interested in privacy updating the DNS =
record
> > with its HoA? That seems counter-intuitive to me. Updating DNS with =
an
> > address is as good as publishing the address on a public
> > website (or an
> > intranet, when DNSSEC is used) :) So, it sounds to me like if an MN
> > wants to keep its HoA location private, it would not be
> > updating the DNS
> > record with its HoA. Or, if the MN needs to get its DNS record =
updated
> > and if the MN's policy is to get a local HA for optimal
> > routing, the MN
> > is clearly not interested in such privacy. Alternately, if
> > the operator
> > policy is to assign a local HA, the MN must either choose to
> > not publish
> > its HoA using DNS (if it wants such privacy) or accept that
> > there is no
>=20
> This is exactly what the text in the security section is about. The
> purpose of the text is to raise awareness of the privacy issue that a
> local HoA contains location information (as opposed to a HoA that is =
non-
> local, which is the typical case in MIPv6). The text basically =
recommends
> that, if location privacy is required by the MN, the MN should either =
not
> reveal the local HoA (i.e., no DNS updates for local HoA and not use a
> local HoA for sessions with untrusted CNs) or hide the fact that the =
HoA
> is local. The latter may be out of control of the MN, e.g., if local =
HA
> assignment is enforced by the operator's policy.
>=20
> > privacy. It simply cannot be both ways :)
>=20
> Right. With the current mechanisms, a MN basically has to choose =
between
> optimized routing and location privacy. Mobopts is working on =
solutions to
> achieve both simultaneously.
>=20
> >
> > 3. If you meant any disclosure of HoA/CoA mapping to
> > entities, that is a
> > problem that is unrelated to any DNS updates. However, such a =
problem
> > exists regardless of the HA location, since the CoA is the one that
> > really discloses the current location of the MN and that =
topologically
> > identifies the location irrespective of where the HoA is anchored.
> >
>=20
> I agree, but the problem of disclosing the HoA/CoA mapping (e.g., in =
MIPv6
> route optimization mode) is not related to this specific issue. The
> privacy issue I was talking about is due to a HoA that contains =
location
> information, and that is only the case for a local HoA.
>=20
> Hope this resolves the confusion.
>=20
> Regards,
>=20
> Kilian
>=20
> > Thanks,
> > Vidya
> >
> > > -----Original Message-----
> > > From: Kilian Weniger [mailto:Kilian.Weniger@eu.panasonic.com]
> > > Sent: Friday, March 02, 2007 4:45 AM
> > > To: Narayanan, Vidya
> > > Cc: Mobile IPv6 Mailing List; Alper Yegin
> > > Subject: RE: [Mip6] WGLC: Review
> > > ofdraft-ietf-mip6-bootstrapping-integrated-dhc-02
> > >
> > > Hi Vidya,
> > >
> > > I'll comment on your questions about the location privacy
> > > issue described in the security considerations section, since
> > > the text was provided by James and me. However, the initial
> > > text was longer, maybe we cut too much and need to add some
> > > more text again to make the issue clear.
> > >
> > > I don't agree with removing the text as Alper suggested.
> > > IMHO, the text describes a valid security issue that that
> > > implementors should be aware of and that can be avoided when
> > > following the recommendations in the text. Thus, the text is
> > > important IMHO.
> > >
> > > The issue is the following:
> > >
> > > A HoA anchored at a local HA (henceforth called local HoA)
> > > has a prefix belonging to the access network the MN is
> > > currently attached to.
> > > Consequently, a local HoA contains some location information.
> > > If any entity 1. knows the MN's HoA and 2. knows that the
> > > corresponding HA is currently a *local* HA, it can infer the
> > > MN's location from the local HoA prefix.
> > >
> > > The attacker (any node that is not authorized to get the MN's
> > > location) can get the MN's location if
> > >
> > > 1. If the attacker can obtain the MN's local HoA, e.g., by
> > > monitoring the DNS entry (in case the MN's DNS entry is
> > > always updated after
> > > bootstrapping) or by initiating communication with the MN (if
> > > the MN will use the local HoA for optimized communication) or
> > > by eavesdropping the MN's traffic.
> > >
> > > 2. If the attacker knows that the HoA obtained in 1 is local.
> > > This is possible under certain circumstances, e.g., when a
> > > MN's or an operator's policy is that the MN shall always try
> > > to bootstrap with a local HA when entering an ASP's network
> > > (this may make sense for routing efficiency
> > > reasons) and the attacker is aware of this policy.
> > >
> > > See some more comments inline.
> > >
> > > >    - The section currently states, "If the home agent
> > > selected by the
> > > > mobile node is local or nearby, (as in section 3.2.2),
> > > disclosing the
> > > > mobile node's home address (e.g., by updating the mobile
> > > node's FQDN
> > > > in the DNS) has the potential to expose some information
> > about the
> > > > mobile node's location." I don't understand the intended
> > > implication
> > > > here. How is this different from an HA in the MSP
> > > performing the DNS
> > > > update?
> > >
> > > If a HA is not local, the corrsponding HoA prefix does not
> > > contain location information and the issue described above
> > > doesn't exist. Maybe we should add something like "A local
> > > HoA contains location information, since the prefix is linked
> > > to the MN's current access network.".
> > >
> > > >
> > > >    - The next paragraph states, "...For instance, if an
> > > attacker knows
> > > > that the mobile node's home agent selection policy is to
> > bootstrap
> > > > with a new local home agent whenever entering a new
> > network (e.g.,
> > > > because the mobile node wants to improve routing efficiency in
> > > > Bi-directional Tunneling mode), the attacker can track the =
mobile
> > > > node's movement if it is aware of the mobile node's current home
> > > > addresses." The MN's movement is tracked by the attacker
> > > using what?
> > > > The HoAs are changing with every new HA in every local
> > network. If
> > > > anything, this should make tracking the MN more
> > difficult. I don't
> > > > follow the discussion in that paragraph or the conclusion.
> > >
> > > If the attacker monitors the DNS entry of the MN and if the
> > > DNS entry of the MN is always updated with a new local HoA
> > > after bootstrapping with a new local HA, the attacker can
> > > track the MN's movement to some extent.
> > >
> > > >
> > > >    - Finally, the last paragraph states, "Consequently, if a =
high
> > > > level of location privacy is desired, a mobile node should
> > > not switch
> > > > to local home agents in an eager manner or should not
> > > reveal its home
> > > > address to untrusted nodes. Furthermore, the disclosure of =
policy
> > > > information that can help locating the mobile node should
> > > be carefully
> > > > considered." Given that this is first discussion of
> > privacy in the
> > > > document, what does "high level of location privacy" mean?
> > > If there is
> > > > such a
> > >
> > > The "level of location privacy" refers to the granularity of
> > > disclosed location information. For some users it may be
> > > acceptable to disclose the prefix of the current access
> > > network, while it is not acceptable to disclose the current
> > > AR. Such "access network-level" of location privacy can,
> > > e.g., be achieved with localized MM, where a MN's MIPv6 CoA
> > > is equal to the MN's PMIP-HoA anchored at a local PMIP-HA. In
> > > this case, an attacker acting as correspondent node could at
> > > most learn the MN's current access network (from the MN's CoA
> > > in MIPv6 route optimization mode).
> > >
> > > For other people this "level" of location privacy is not =
acceptable.
> > > They have stronger requirements on location privacy, where
> > > the attacker cannot figure out the current access network.
> > > For instance, some users don't want that it is possible to
> > > find out that they are on a business trip or on vacation in
> > > another country (e.g., to prevent that someone uses this
> > > information for a burglary). This was referred to as "high
> > > level" of location privacy. Maybe we need to add some text
> > about this.
> > >
> > > > thing, what is
> > > > then a "lower level of location privacy" and how is that =
achieved?
> > > > Further, it is not clear as to what element of privacy is
> > needed or
> > > > which elements the privacy is needed from. This text is
> > > recommending
> > > > against using local home agents - is this to provide
> > > privacy from the
> > > > local network? If this is only about providing privacy from
> > > > correspondent and other observing nodes, I don't understand the
> > > > difference made by local or remote HAs. Also, I don't follow the
> > > > disclosure of policy information - this document is only
> > > discussing HA
> > > > bootstrapping; is there such policy information that may be
> > > disclosed
> > > > leading to this privacy concern?
> > >
> > > The policy information refers to the MN's policy to eagerly
> > > bootstrap with a local HA and updating the HoA when entering
> > > a new network.
> > >
> > > Regards,
> > >
> > > Kilian
> > >
> > >
> > > Panasonic R&D Center Germany GmbH
> > > 63225 Langen, Hessen, Germany
> > > Reg: AG Offenbach (Hessen) HRB 33974
> > > Managing Director: Thomas Micke
> > >
> > >
> > >
> >
> >
>=20
>=20
> Panasonic R&D Center Germany GmbH
> 63225 Langen, Hessen, Germany
> Reg: AG Offenbach (Hessen) HRB 33974
> Managing Director: Thomas Micke
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Wed Mar 14 05:17:32 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRPae-0006n2-9U; Wed, 14 Mar 2007 05:16:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRPad-0006mr-1f
	for mip6@ietf.org; Wed, 14 Mar 2007 05:16:11 -0400
Received: from cluster-e.mailcontrol.com ([217.79.216.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRPab-0001Hm-KS
	for mip6@ietf.org; Wed, 14 Mar 2007 05:16:11 -0400
Received: from rly33e.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly33e.srv.mailcontrol.com (MailControl) with ESMTP id
	l2E9FiT9002787
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Wed, 14 Mar 2007 09:15:52 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly33e.srv.mailcontrol.com (MailControl) id l2E9F6sr001717
	for mip6@ietf.org; Wed, 14 Mar 2007 09:15:06 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly33e-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l2E9EuWe001182; Wed, 14 Mar 2007 09:15:06 +0000 (GMT)
Received: from eundadmi02.pan.eu(10.100.96.65) by hhe500-02.hbg.de.pan.eu via
	smtp id 76b9_b6d9287a_d209_11db_9805_0030482aac25;
	Wed, 14 Mar 2007 09:55:09 +0100
Received: from VPN-MRelay-02.PRDCG.Panasonic.de ([10.100.176.57])
	by eundadmi02.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007031410145286-47800 ;
	Wed, 14 Mar 2007 10:14:52 +0100 
X-Spam-Status: No, hits=0.0 required=4.0
	tests=TOTAL_SCORE: 0.000
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-02.PRDCG.Panasonic.de;
	Wed, 14 Mar 2007 10:24:41 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: home network requested by MN may be != assigned network (was:
	RE:[Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBDAF5@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: home network requested by MN may be != assigned network (was:
	RE:[Mip6] WGLC: draft-ietf-mip6-bootstrapping-integrated-02)
thread-index: AcdZUPl3RCOZHB9nQb6+3hPvBup2ywBYXBGgARQFcMAAD4CxkAAf7ZPgAYqfl7AACXlrkA==
References: <4D2F935F08D41A4C8866693F4F0D7C4F01278715@lan-ex-01.panasonic.de>
	<7CCD07160348804497EF29E9EA5560D7FBDAF5@exchtewks2.starentnetworks.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F01278B0C@lan-ex-01.panasonic.de>
Date: Wed, 14 Mar 2007 10:11:22 +0100
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-06-90 (www.mailcontrol.com) on 10.69.1.143
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, heejin.jang@samsung.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kuntal,

<snip>
> [KC>] Yes, the MSA does not know a priori which target=20
> network's home info the MN is going to request. That's why=20
> the MSA (AAA server) sends all the authorized target network=20
> info to the NAS at the time of access auth.
<snip>

ok, this should work. Some more text about this would be good to have in
the next version of the draft.=20

However, I'm not sure if the current version of
draft-ietf-dime-mip6-integrated supports sending more than one MIPv6
bootstrapping AVP of the same type (e.g., MIP6-Home-Agent-FQDN) from
AAAH to NAS. It might require a slight update to clarify that this is
supported.

Regards,

Kilian=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke




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



From mip6-bounces@ietf.org Wed Mar 14 08:34:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRSf1-00065H-PV; Wed, 14 Mar 2007 08:32:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRSez-00065B-Jh
	for mip6@ietf.org; Wed, 14 Mar 2007 08:32:53 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRSex-0007zK-V9
	for mip6@ietf.org; Wed, 14 Mar 2007 08:32:53 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id B4369198720;
	Wed, 14 Mar 2007 14:32:50 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 3786C19871F;
	Wed, 14 Mar 2007 14:32:50 +0200 (EET)
Message-ID: <45F7EB74.7060405@piuha.net>
Date: Wed, 14 Mar 2007 14:32:52 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-cn-ipsec-04.txt
References: <E1HMsDz-0002eQ-Bw@stiedprstage1.ietf.org>
In-Reply-To: <E1HMsDz-0002eQ-Bw@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: b5d20af10c334b36874c0264b10f59f1
Cc: 'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@orange-ft.com>,
	mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis, Jean-Michel,

I looked at the new revision. I wanted to move forward with
it, but it still has two issues:

1. The security considerations section does not, in my opinion,
    describe the full security implications. Basically, you simply
    state that IPsec/IKE based mechanism is the "best possible
    defense", and then you go on arguing why care-of addressing
    checking is not needed. I do not mind having the document say
    that the mechanism is strong, and I do not disagree
    with the specific points about the care-of address checking.
    However, the security considerations should describe the
    security rather than claim its the best possible one.

2. The possible enhancement section makes statements about
    various extension ideas and other IETF designs that I do not
    think you should be making. For instance, you state that
    BTNS is too weak but present no technical argument why
    this might be the case. It may well be the case, but its
    really not the place of this document to make broad claims,
    at least not if they are not supported by a detailed analysis.
    This section should also not employ keywords, to avoid
    interpreting a list of enhancement ideas as implementation
    requirements.

Since I would rather move forward than keep this document on
my table forever, please find attached suggested edits that
take care of the above issues. They are based on a merge of
your current text and the earlier text that I proposed when
I looked at the document the last time. If you agree with the or
some other edits with a similar intent, I can place the document
for IESG review immediately. Otherwise we'll probably have to
go to the next revision and continue discussing.

Replace two first paragraphs of Section 7 with this:

   The Mobile IPv6 Route Optimization security design background
   document [RFC4225] describes the unauthorized creation of Binding
   Cache entries as the main avenue of attack.  The authentication and
   authorization of the Mobile Node provided by IPsec/IKE is a strong
   defense against this threat.

   Where the means to create suitable IPsec security associations
   exist, this mechanism provides origin authentication, integrity
   protection, replay protection and optional confidentiality services
   for the Mobile IPv6 signalling. This improves the security over
   RFC 3775 route optimization, as the signaling packets in the latter
   are vulnerable to man-in-the-middle attacks. The implications of
   this vulnerability are subtle, however, given that an attacker in
   the same position is also capable of seeing all the payload packets
   and could launch other attacks with similar implications. For
   instance, such an attacker could see or modify the contents of
   payload packets not protected with end-to-end security and cause
   denial-of-service for others. However, the RFC 3775 mechanism
   allows such attacks in a short time window even after the attacker
   is no longer in a position to see the payload packets
   themselves. The mechanism defined in this specification removes
   this vulnerability, and is also secure independently of the
   possible vulnerabilities related to payload packets.

   However, unlike RFC 3775 this mechanism should only be used when
   the correspondent node has good reason to trust the actions of the
   mobile node. In particular, the correspondent node needs to be
   certain that the mobile node will not launch flooding attacks
   against a third party as described in [RODESIGN]. Without such
   trust the only protection comes from the application of ingress
   filtering in the network where the attacker resides. However, at
   the moment ingress filtering has not been universally deployed.
   This mechanism is vulnerable to flooding attacks as it does not
   verify the validity of a claimed new care-of address. Note,
   however, the following:

   -  The attacker has to be the Mobile Node itself, i.e., the IPsec/IKE
      peer, which is supposed to be the subject of a minimal level of
      trust.

   -  The attack can be traced back to the Mobile Node.

Replace Section 9 with this:

   A number of potential enhancements of this method are possible,
   including, for instance, various mechanisms for verification of
   Care-of Addresses or use of addresses bound to keys.  [ROENC]
   describes many proposals for the general Route Optimization problem.

   [COOKIE] is an alternate approach to testing Care-of Addresses.

   When the Home Address is bound to a public key, for instance when the
   Home Address is a Cryptographically Generated Addresses [RFC3972],
   [IKECGA] describes an alternative approach to the use of strong
   authentication.


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



From mip6-bounces@ietf.org Wed Mar 14 10:07:46 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRU81-0006s5-55; Wed, 14 Mar 2007 10:06:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRU7z-0006ra-5M
	for mip6@ietf.org; Wed, 14 Mar 2007 10:06:55 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRU7w-0005W4-Ae
	for mip6@ietf.org; Wed, 14 Mar 2007 10:06:55 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id B07DB198720;
	Wed, 14 Mar 2007 16:06:51 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 6222819871F;
	Wed, 14 Mar 2007 16:06:51 +0200 (EET)
Message-ID: <45F8017D.1060608@piuha.net>
Date: Wed, 14 Mar 2007 16:06:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [Mip6] Revised Milestones for MIP6 Working Group
References: <200702282228.l1SMSO4Y019124@tao.fdupont.fr>
In-Reply-To: <200702282228.l1SMSO4Y019124@tao.fdupont.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: d6b246023072368de71562c0ab503126
Cc: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>, 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


>    Done   Submit I-D 'Using IPsec between Mobile and Correspondent IPv6
>    Nodes' to IESG for publication as Experimental.
>
> => s/Experimental/Proposed Standard/
> BTW I submitted a revised version some hours ago.
>   

We talked about this during WG recharter last year. This document
does not appear in the charter at all, and its listing in the milestones
is actually an error (I reviewed the new list, sorry I didn't catch this
earlier).

The CN-IPsec document is being taken as an individual submission,
so called AD sponsored submission to Experimental.  We talked
about that status too, last year.

Jari


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



From mip6-bounces@ietf.org Wed Mar 14 12:36:59 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRWSw-0001Ah-15; Wed, 14 Mar 2007 12:36:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRWSu-00018Q-IJ
	for mip6@ietf.org; Wed, 14 Mar 2007 12:36:40 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRWSo-0002Hn-VG
	for mip6@ietf.org; Wed, 14 Mar 2007 12:36:40 -0400
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr
	[157.159.103.217])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 42B412FD2B
	for <mip6@ietf.org>; Wed, 14 Mar 2007 17:36:28 +0100 (CET)
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: mip6@ietf.org
In-Reply-To: <45F7EB74.7060405@piuha.net>
References: <E1HMsDz-0002eQ-Bw@stiedprstage1.ietf.org>
	<45F7EB74.7060405@piuha.net>
Content-Type: text/plain
Organization: INT Evry
Date: Wed, 14 Mar 2007 17:36:51 +0100
Message-Id: <1173890211.17956.10.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Content-Transfer-Encoding: 7bit
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-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027
Subject: [Mip6] Disposable Home Addresses
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hello could you comment on the following
very short I-D?

Thanks in advance.
Regards,

pars mutaf



----------------8<  cut here  8<--------------------




Network Working Group                                         Pars Mutaf
Internet-Draft                                     Institut National des
Intended status: Informational                        Telecommunications
Expires: September 15, 2007                               March 14, 2007


                       Disposable home addresses
                        draft-mutaf-dhoa-00.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on September 15, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   The "home address" in Mobile IPv6 should be considered as private
   information, as it allows access to a mobile host regardless of its
   location.  This document presents a discussion of "disposable home
   addresses" for Mobile IPv6.







Mutaf                  Expires September 15, 2007               [Page 1]

Internet-Draft          Disposable home addresses             March 2007


1.  Introduction

   Inspired from [TDIGITS] [DPN], this document presents a discussion of
   "disposable home addresses" in Mobile IPv6.

   A mobile host can have multiple home addresses in the same or
   different home networks[?].  This has important benefits in terms of
   privacy and security.

   The host can distribute different home addresses to different
   entities.  Later, if one of the addresses is abused (for example, for
   spam, DoS attack, or location discovery), then that home address can
   be disposed i.e., destroyed by its owner.

   Techniques for distributing disposable home addresses falls out of
   this document's scope.  They can be reliably shared with "a priori"
   trusted parties using a technology like Bluetooth.  Or, one can use
   [PIQ].


2.  Security considerations

   TBD.


3.  IANA considerations

   None.


4.  Conclusion

   This document presented a discussion of disposable home addresses.


5.  Informative References

   [DPN]      Disposable phone numbers, "URL:
              http://dpn.sourceforge.net/".

   [PIQ]      Mutaf, P., "Private information queries (Problem
              Statement)", draft-mutaf-piqproblem-00.txt (work in
              progress), 2007.
              URL:
http://www.ietf.org/internet-drafts/draft-mutaf-piqproblem-00.txt

   [TDIGITS]  Tossable Digits, "URL: http://www.tossabledigits.com/".





Mutaf                  Expires September 15, 2007               [Page 2]

Internet-Draft          Disposable home addresses             March 2007


Author's Address

   Pars Mutaf
   Institut National des Telecommunications

   Email: pars.mutaf@int-evry.fr













































Mutaf                  Expires September 15, 2007               [Page 3]

Internet-Draft          Disposable home addresses             March 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Mutaf                  Expires September 15, 2007               [Page 4]










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



From mip6-bounces@ietf.org Wed Mar 14 17:02:18 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRaaW-0003Ls-Ex; Wed, 14 Mar 2007 17:00:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRaaT-0003GS-Tc
	for mip6@ietf.org; Wed, 14 Mar 2007 17:00:45 -0400
Received: from mail153.messagelabs.com ([216.82.253.51])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HRaaS-0003cP-EM
	for mip6@ietf.org; Wed, 14 Mar 2007 17:00:45 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-8.tower-153.messagelabs.com!1173906043!3634023!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 25468 invoked from network); 14 Mar 2007 21:00:43 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-8.tower-153.messagelabs.com with SMTP;
	14 Mar 2007 21:00:43 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2EL0c8v028338;
	Wed, 14 Mar 2007 14:00:38 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l2EL0aT4028596;
	Wed, 14 Mar 2007 16:00:37 -0500 (CDT)
Message-ID: <45F86273.3070509@gmail.com>
Date: Wed, 14 Mar 2007 22:00:35 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] [issue93] Payload Qualifiers when using
	IPv4-UDP	transportfor both IPv4 and IPv6 payloads
References: <20070228025801.ZXHR17816.oaamta02ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070228025801.ZXHR17816.oaamta02ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, mip6@ietf.org,
	'Sri Gundavelli' <sgundave@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hesham Soliman wrote:
> 
>> Version field can be used to distinguish that. But, when a packet
>> is encapsulated in any application header, it needs to be wrapped
>> in a TLV format. Example: RFC-3519. If there is no wrapper,
>> application would not even know the size of that packet, or the
>> type of the packet, unless its derived from the IP header. That
>> adds some complexity w.r.t the way applications use the socket
>> interface ..options etc. Having a wrapper would be usefull. The
>> normal encapsulation modes in L3 such as IP/IP, IPv6/IPv6, GRE, all
>> have the type field and so when we wrap a packet in L4, we need an
>> identifier some where, IMO.
> 
> => I know the following question is not necessarily the crux of your
> issue but does anyone implement MIPv6 as an application? I know it's
> possible to do that but no one seemed to make that choice to my
> knowledge, but I could be wrong.
> 
> I'd love to hear what others think, I think it's a good point to
> discuss.

Sorry for replying late on this.  I got redirected here from NETLMM WG.

I deal with three types of mip6 implementations: kernel exclusively, app
exclusively and mixed.

My initial was kernel-exclusively.  Then people said it's complicated.
Then some app-exclusively mip6 implementation had some advantages but
turned out to not send BU upon handover because the ongoing audio/video
stream was taking too many resources.

Just to say that it depends on what kind of environment one works on, 
and that there _are_ advantages to do kernel only.

Alex


> 
> Hesham
> 
>> 
>> Thanks Sri
>> 
>> 
>> On Wed, 28 Feb 2007, Hesham Soliman wrote:
>> 
>>> Hi Sri,
>>> 
>>> Why can't the receiver do the switch on the version field? I
>>> mean, how does the receiver of any encapsulated packet
>> know the version of
>>> the inner header?
>>> 
>>> Hesham
>>> 
>>>> -----Original Message----- From: Sri Gundavelli
>>>> [mailto:tracker-mip6@mip4.org] Sent: Wednesday, February 28,
>>>> 2007 8:38 AM To: mip6@ietf.org Subject: [Mip6] [issue93]
>>>> Payload Qualifiers when using IPv4-UDP transportfor both IPv4
>>>> and IPv6 payloads
>>>> 
>>>> 
>>>> New submission from Sri Gundavelli <sgundave@cisco.com>:
>>>> 
>>>> Reference to section 4.3.1 and 4.4.1.
>>>> 
>>>> For the IPv4 transport and with NAT in path, the opaque 
>>>> encapsulation mode of IPv4-UDP for both IPv4 and IPv6 payload
>>>> packets i.e IPv6/IPv4-UDP or IPv4/IPv4-UDP is being recommended
>>>> by the draft. With out a payload qualifier in the UDP header, I
>>>> wonder how the tunnel peer handles the packet after
>>>> decapsulation ? How would it know, if it is an IPv4 payload
>>>> packet or an IPv6 packet ? Do you expect some packet inspection
>>>> after decapsulation ?
>>>> 
>>>> One option is to have thin header such as the MIP Tunnel Data
>>>> Message from RFC-3519, as suggested by Kent Leung.
>>>> 
>>>> 
>>>> MIP Tunnel Data Message
>>>> 
>>>> 0                   1                   2                   3 0
>>>> 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
>> 6 7 8 9 0 1
>>>> 
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> |     Type      |  Next Header  |           Reserved
>> |
>>>> 
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>> 
>>>> 
>>>> We want a quick resolution on this. 
>>>> draft-sgundave-mip6-proxymip6-02.txt has normative reference to
>>>> the DSMIP6 spec.
>>>> 
>>>> Thanks Sri
>>>> 
>>>> ---------- category: Technical draft:
>>>> draft-ietf-mip6-nemo-v4traversal messages: 330 nosy: sri 
>>>> priority: Must fix status: No discussion title: Payload
>>>> Qualifiers when using IPv4-UDP transport for both IPv4 and IPv6
>>>> payloads
>>>> 
>>>> _________________________________________________ Mip6 issue
>>>> tracker <tracker-mip6@mip4.org> 
>>>> <http://www.mip4.org/issues/tracker/mip6/issue93> 
>>>> _________________________________________________
>>>> 
>>>> _______________________________________________ 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
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From mip6-bounces@ietf.org Wed Mar 14 20:36:13 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRdwF-0007b3-9Z; Wed, 14 Mar 2007 20:35:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRdwD-0007ag-I9
	for mip6@ietf.org; Wed, 14 Mar 2007 20:35:25 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRdwC-0006NU-8E
	for mip6@ietf.org; Wed, 14 Mar 2007 20:35:25 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Mar 2007 17:35:23 -0700
Message-ID: <45F894C7.1030808@azairenet.com>
Date: Wed, 14 Mar 2007 17:35:19 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] Revised Milestones for MIP6 Working Group
References: <200702282228.l1SMSO4Y019124@tao.fdupont.fr>
	<45F8017D.1060608@piuha.net>
In-Reply-To: <45F8017D.1060608@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Mar 2007 00:35:23.0699 (UTC)
	FILETIME=[D1AA8030:01C76699]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>, mip6@ietf.org,
	Francis Dupont <Francis.Dupont@fdupont.fr>,
	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

Jari Arkko wrote:
>>    Done   Submit I-D 'Using IPsec between Mobile and Correspondent IPv6
>>    Nodes' to IESG for publication as Experimental.
>>
>> => s/Experimental/Proposed Standard/
>> BTW I submitted a revised version some hours ago.
>>   
> 
> We talked about this during WG recharter last year. This document
> does not appear in the charter at all, and its listing in the milestones
> is actually an error (I reviewed the new list, sorry I didn't catch this
> earlier).
> 
> The CN-IPsec document is being taken as an individual submission,
> so called AD sponsored submission to Experimental.  We talked
> about that status too, last year.

Thats odd. My understanding is that this document is a
MIP6 WG document. It was presented numerous times. There
was even a WG last call on this document. See
http://www1.ietf.org/mail-archive/web/mip6/current/msg04111.html

I don't know why it does not appear in the charter
currently.

Vijay

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



From mip6-bounces@ietf.org Thu Mar 15 01:39:22 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRif7-00019G-Vd; Thu, 15 Mar 2007 01:38:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRif6-00017D-N6
	for mip6@ietf.org; Thu, 15 Mar 2007 01:38:04 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRiex-0001Rr-GL
	for mip6@ietf.org; Thu, 15 Mar 2007 01:38:04 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 1B8DF198721;
	Thu, 15 Mar 2007 07:37:52 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id A6EDE19871E;
	Thu, 15 Mar 2007 07:37:51 +0200 (EET)
Message-ID: <45F8DBB1.9060700@piuha.net>
Date: Thu, 15 Mar 2007 07:37:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] Revised Milestones for MIP6 Working Group
References: <200702282228.l1SMSO4Y019124@tao.fdupont.fr>
	<45F8017D.1060608@piuha.net> <45F894C7.1030808@azairenet.com>
In-Reply-To: <45F894C7.1030808@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>, mip6@ietf.org,
	Francis Dupont <Francis.Dupont@fdupont.fr>,
	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


> Thats odd. My understanding is that this document is a
> MIP6 WG document.

What may be confusing is that the document still has draft-ietf
filename. This is for historical reasons, however. We could change
that but it seems pointless given that we're so close to getting
this shipped to the RFC Editor.

Part of the reason that we did the recharter last year was that
the group had adopted a number of documents and what it
worked on no longer exactly matched the charter. At that point
it was important to discuss what should be in the charter
and what should not; after a lengthy discussion we came up
with the charter that appears in the IETF web page. And as
usual, your AD had opinions on what should be in the charter
(such as maintenance) or what should not (such as the draft
we are discussing), to ensure that important tasks are covered,
focus is kept, you do not take on too much, etc. And I also
want to enforce the new charter so that the group works within
its defined tasks. Having said that, I believed the draft in
question was useful to get published, so that's why I took
it on as an AD sponsored item. More information on AD
sponsored items here, by the way:

   http://www.ietf.org/IESG/content/ions/drafts/ion-ad-sponsoring.html

These can basically produce exactly the same end result
as documents coming from Working Groups, even on
Standards Track. But they do not come from WGs, and
its an AD judgment call to take them on.

Jari


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



From mip6-bounces@ietf.org Thu Mar 15 02:45:51 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRji4-0005kw-2U; Thu, 15 Mar 2007 02:45:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HRji2-0005kn-Do
	for mip6@ietf.org; Thu, 15 Mar 2007 02:45:10 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRji1-0002cM-39
	for mip6@ietf.org; Thu, 15 Mar 2007 02:45:10 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Mar 2007 23:45:08 -0700
Message-ID: <45F8EB73.2000900@azairenet.com>
Date: Wed, 14 Mar 2007 23:45:07 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] Revised Milestones for MIP6 Working Group
References: <200702282228.l1SMSO4Y019124@tao.fdupont.fr>
	<45F8017D.1060608@piuha.net> <45F894C7.1030808@azairenet.com>
	<45F8DBB1.9060700@piuha.net>
In-Reply-To: <45F8DBB1.9060700@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Mar 2007 06:45:08.0565 (UTC)
	FILETIME=[78E06850:01C766CD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>, mip6@ietf.org,
	Francis Dupont <Francis.Dupont@fdupont.fr>,
	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

Jari Arkko wrote:
>> Thats odd. My understanding is that this document is a
>> MIP6 WG document.
> 
> What may be confusing is that the document still has draft-ietf
> filename. This is for historical reasons, however. We could change
> that but it seems pointless given that we're so close to getting
> this shipped to the RFC Editor.
> 
> Part of the reason that we did the recharter last year was that
> the group had adopted a number of documents and what it
> worked on no longer exactly matched the charter. At that point
> it was important to discuss what should be in the charter
> and what should not; after a lengthy discussion we came up
> with the charter that appears in the IETF web page. And as
> usual, your AD had opinions on what should be in the charter
> (such as maintenance) or what should not (such as the draft
> we are discussing), to ensure that important tasks are covered,
> focus is kept, you do not take on too much, etc. And I also
> want to enforce the new charter so that the group works within
> its defined tasks. Having said that, I believed the draft in
> question was useful to get published, so that's why I took
> it on as an AD sponsored item. More information on AD
> sponsored items here, by the way:
> 
>    http://www.ietf.org/IESG/content/ions/drafts/ion-ad-sponsoring.html
> 
> These can basically produce exactly the same end result
> as documents coming from Working Groups, even on
> Standards Track. But they do not come from WGs, and
> its an AD judgment call to take them on.

I don't have a problem standardizing this document as an
AD sponsored document.

What is odd is that this document underwent a MIP6 WG
last call, and was forwarded to the IESG for publication
as Proposed Standard. But after that it became an AD
sponsored Experimental document. :)

Vijay

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



From mip6-bounces@ietf.org Thu Mar 15 06:13:36 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRmws-0002Km-U3; Thu, 15 Mar 2007 06:12:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRmwr-00027M-BP; Thu, 15 Mar 2007 06:12:41 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HRmwm-0000Go-Hl; Thu, 15 Mar 2007 06:12:41 -0400
Received: from [82.129.133.254] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HRmwT-0003Lc-W8; Thu, 15 Mar 2007 21:12:19 +1100
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: <mip6@ietf.org>
Date: Thu, 15 Mar 2007 21:11:49 +1100
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: <45F802A6.5010402@piuha.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdmQryEI0u6jQD5SFC8WC6cS2V/gQAplD7A
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Cc: 'Thomas Narten' <narten@us.ibm.com>, iesg@ietf.org
Subject: [Mip6] RE: DISCUSS: draft-ietf-mip6-dsmip-problem comments from
	Thomas
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org
Message-Id: <E1HRmws-0002Km-U3@megatron.ietf.org>

Thomas, 

Thanks for the review. Some comments below. FYI, I've added the IESG just as
an FYI that the discussion is taking place on the WG list. Whoever responds
should remove them. 



 > Not sure these are all that significant. But I think this document
 > kind of oversimplifies the problem statement. 
 > 
 > 2007-02-22: review of 03
 > 
 > 
 > > > 4.3.  Operational Burdens
 > > > 
 > > >    As mentioned earlier, deploying both protocols will 
 > require managing
 > > >    both protocols in the mobile node and the home agent. 
 >  This adds
 > > >    significant operational issues for the network 
 > operator.  It would
 > > >    certainly require the network operator to have deep 
 > knowledge in both
 > > >    protocols which is something an operator may not be 
 > able to justify
 > > >    due to the lack of substantial gains.
 > > > 
 > > >    In addition, deploying both protocols will require 
 > duplication of
 > > >    security credentials on mobile nodes and home agents. 
 >  This includes,
 > > >    IPsec security associations, keying material, and new 
 > authentication
 > > >    protocols for Mobile IPv6, in addition to the 
 > security credentials
 > > >    and associations required by Mobile IPv4.  Depending 
 > on the security
 > > >    mechanisms used and with some further work it might 
 > be possible to
 > > >    optimize some of these processes.  Assuming nothing 
 > else changes,
 > > >    however, such duplication is again significant with 
 > no gain to the
 > > >    operator or the mobile node.
 > >   
 > 
 > This is true at one level, but ignores the underlying reality. By
 > definition, transition means you are stuck with something that is
 > already deployed, with limited ability to upgrade. So if the
 > implication is that a clean-slate approach that combines both is
 > better, that misses the point.

=> It's true that the deployed IPv4 infrastructure cannot be assumed to be
"upgradeable". This is certainly the case for the MIPv6-based approach. The
only functions that are upgraded by this approach are the MIPv6-specific
ones, i.e., MN and HA. The same goes for the MIPv4-based approach. The draft
doesn't talk about how to solve the problem so I'm just giving some context.


 > > > 4.4.  Mobility Management Inefficiencies
 > > > 
 > > >    Suppose that a mobile node is moving within a dual 
 > stack access
 > > >    network.  Every time the mobile node moves it needs 
 > to send two
 > > >    mobile IP messages to its home agent to allow its 
 > IPv4 and IPv6
 > > >    connections to survive.  There is no reason for such 
 > duplication.  
 > >   
 > 
 > Sure there is. It may well be that the IPv4 and IPv6 HA are on
 > different nodes. (And this would be for historical/transitional
 > reasons, i.e., not changable.)

=> Sure, but the point was that you don't need both protocols simultaneously
in many cases. This is independent of whether they run on the same node or
different ones. 

 > > >    with Mobile IPv4 or Mobile IPv6, non of the known 
 > mechanisms have
 > >   
 > 
 > run through spell.

=> ok.

 > 
 > 
 > > >      - It should be possible to run one mobility 
 > management protocol
 > > >       that can manage mobility for both IPv4 and IPv6 
 > addresses used by
 > > >       upper layers.  Both Mobile IPv4 and Mobile IPv6 
 > should be able of
 > > >       performing such task.  It may not be possible to 
 > support route
 > > >       optimization for Mobile IPv6 in all cases; 
 > however, mobility
 > > >       management and session continuity can be supported.
 > >   
 > 
 > I'm surprised to see this. My understanding is that RO is one of the
 > benefits being marketed with MIPv6. Above, the suggests that it is OK
 > to reduce/cripple this functionality.

=> Only when it *can't* be used. For instance, if the CN is IPv4-only, or if
the access network is IPv4-only. You can't use RO in those scenarios today.

 > 
 > 
 > > >       - It should be possible to create IPv4 extensions 
 > to Mobile IPv6
 > > >       so that an IPv4 and IPv6 capable mobile node can 
 > register its IPv4
 > > >       and IPv6 home addresses to an IPv4 and IPv6 
 > enabled Home Agent
 > > >       using MIPv6 signaling only.
 > > > 
 > > >       - It should be possible to create IPv6 extensions 
 > to Mobile IPv4
 > > >       so that an IPv4 and IPv6 capable mobile node can 
 > register its IPv4
 > > >       and IPv6 home addresses to an IPv4 and IPv6 
 > enabled Home Agent
 > > >       using Mobile IPv4 signaling only.
 > >   
 > 
 > I'm not sure I agree with "should" above. Sure, its "desirable". But
 > "should" is stronger than that.

=> I'm fine with "desirable".

 > 
 > And I wonder about the implication. I.e., if one has MIPv6, but roams
 > to an IPv4 only network, the fundamental problem that needs 
 > solving is
 > associating an IPv6 address (presumably the Home Address) 
 > with an IPv4
 > COA. Neither MIPv4 nor MIPv6 does that today. So we are now talking
 > about extending MIPv6, not just adding reducing signaling. Hmm. Maybe
 > we can use IPv4-compatable addresses here. (Finally, a possible use
 > for such addresses?)

=> Compatible addresses were deprecated, but you're absolutely right, we're
using mapped addresses in the MIPv6 solution.

 > 
 > But when a MN attaches to an IPv6 only network, the MIPv4 HA 
 > can't use
 > MIPv4 because the MN doesn't have an IPv4 address. I don't see  how
 > this can be addressed without actually extending MIPv4. So the
 > implication here seems to be that this document may be implying more
 > substantive protocol changes than first appears.

=> Yes it does imply extending both protocols. 

Thanks,
Hesham



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



From mip6-bounces@ietf.org Fri Mar 16 08:20:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSBP7-0002Z0-24; Fri, 16 Mar 2007 08:19:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSBP6-0002Yq-0U
	for mip6@ietf.org; Fri, 16 Mar 2007 08:19:28 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSBP4-0005k4-2Q
	for mip6@ietf.org; Fri, 16 Mar 2007 08:19:27 -0400
Received: from [196.205.136.253] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HSBOU-0003sL-KF
	for <mip6@ietf.org>; Fri, 16 Mar 2007 23:18:51 +1100
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: <mip6@ietf.org>
Date: Fri, 16 Mar 2007 23:18:42 +1100
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.3028
Thread-Index: AcdWXAtOagSNDykWQ3m5DCNx50ygGAAEK6OQBFYXyeA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Subject: [Mip6] FW: DISCUSS: draft-ietf-mip6-dsmip-problem Brian's comments
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org
Message-Id: <E1HSBP7-0002Z0-24@megatron.ietf.org>

Folks, 

FYI, we need to address Brian's comments on the doc. I sent the comments
below to Brian.
Your comments are welcome.

Hesham 

-----Original Message-----
From: Hesham Soliman [mailto:Hesham@elevatemobile.com] 
Sent: Thursday, February 22, 2007 9:52 PM
To: 'Brian Carpenter'; 'iesg@ietf.org'
Cc: 'mip6-chairs@tools.ietf.org'; 'tsirtsis@qualcomm.com'
Subject: RE: DISCUSS: draft-ietf-mip6-dsmip-problem 



 > Discuss:
 > The draft is very clear; the problem description is excellent
 > and long overdue. However, I have serious trouble with the
 > recommendation that we should simultaneously "create IPv4
 > extensions to Mobile IPv6" and "create IPv6 extensions to
 > Mobile IPv4".
 > 
 > This might console vendors or SPs who've invested heavily 
 > in one or the other, but it causes severe problems for roaming
 > users, whose need is a single Mobile IP, period. Roaming 
 > users may not be always bound to the same home site and 
 > service provider (that's called consumer choice). If a roaming 
 > user wants to choose between multiple SPs, and wants dual stack
 > service from all of them, the mobile host will in any case have
 > to support both varieties of dual stack MIP, and will have to
 > choose automagically between them. So the effect of this
 > dual recommendation is an increase in complexity and/or a
 > reduction in interoperability.

=> I think your concern above is valid for those cases where a device roams
into a network and wants to pick a local HA/MAP in that domain. OTOH, this
concern should not apply to cases where the device is connected to one or
more "permanent" home sites because those relationships are not established
on the fly. However, unfortunately, something has to give. Either SPs will
deploy both versions, or will have roaming agreements with others who deploy
the same version, or devices that want this relationship on the fly will
implement both versions for maximum freedom. 

But to put things in perspective I have to mention two important points for
this discussion. First, from a practical short term view, you can't go wrong
with MIPv4. Wherever MIP is deployed, MIPv4 is used. So at least in the
short term, devices that have MIPv4 only will be ok. The other point is that
(again from a practical point of view, given deployments today) the need for
this "on the fly" relationship with a local agent is limited to a few
deployments that really require it. Users don't really care where their
tunnel end point is located provided they have connectivity. Presumably a
user is ok with his/her permanent anchor as far as the service is concerned
(e.g. VPN is enabled..etc). The *need* for a different agent is typically
either due to a real need to reduce delays (e.g. for real time traffic) or
because the local technology being used requires it. IMHO both of those
scenarios today occur in well co-ordinated networks where such
interoperability issues are taken care of in other standard groups that I
don't go to anymore :) 

I know that this is not an ideal answer in terms of generality and
flexibility, but it's a "plan B" for those who don't want to run both
versions simultaneously. I just don't see the option of mandating one
extension as a valid one, I find it more limiting to operators and
implementers of mobile devices. For instance, if we go with the "one MIP
version" scenario, which one do we pick and why? We can't ignore the
deployed MIPv4, and of course we shouldn't deprive MIPv6 from this feature
for medium and long term deployments.

 > 
 > I didn't understand when MIP4 was rechartered that we
 > were in effect approving this dual approach in the words:
 > "A problem statement covering both Mobile IPv4 and IPv6 dual-stack
 > issues is expected to come out of MIP6 WG, and will not be developed
 > in MIP4 WG."
 > 
 > I think the choice of direction here is for the IETF, not
 > for a single WG or the IESG. I think we should not proceed 
 > on this path without a real debate, to reach consensus on one 
 > interoperable direction.

=> A debate about this is definitely useful for everyone.
I'm ok with the text below if we decide to go that way.

Hesham

 > 
 > As far as this draft goes, if the recommendation to do
 > both is the consensus of the MIP6 WG, I'd be satisfied with
 > a text change in section 5 that would make it clear
 > that this is not an IETF consensus. For example
 > 
 > OLD
 >    In order to allow for a gradual transition based on 
 > current standards
 >    and deployment, the following work areas seem to be reasonable:
 > 
 > NEW
 >    The Mobile IPv6 Working Group has reached the view that to allow 
 >    for a gradual transition based on current standards and 
 > deployment, 
 >    the following work areas would be reasonable:
 > 
 > and
 > OLD
 >    Following the steps listed above, a vendor can choose to 
 > support one
 >    mobility management protocol while avoiding the 
 > incompatibility and
 >    inefficiency problems listed in this document.  
 > Similarly, operators
 >    can decide to continue using one mobility management 
 > protocol while
 >    addressing the transition scenarios that a mobile node is 
 > likely to
 >    face when roaming within the Internet.
 > 
 > NEW
 >    If the IETF chooses to pursue all these paths, a vendor 
 > could choose 
 >    to support one mobility management protocol while avoiding the 
 >    incompatibility and inefficiency problems listed in this document.
 >    Similarly, operators could decide to continue using one mobility
 >    management protocol throughout the period of IPv4 and 
 > IPv6 coexistence.
 >    However, a mobile node would be forced to choose one approach
 >    or the other, or nevertheless to install both and use one or
 >    the other according to circumstances.
 > 
 > 
 > 



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



From mip6-bounces@ietf.org Fri Mar 16 09:18:00 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSCIh-0000cZ-P8; Fri, 16 Mar 2007 09:16:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HPS1O-0001AA-GY
	for mip6@ietf.org; Thu, 08 Mar 2007 18:27:42 -0500
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 1HPS1O-0002xe-2L
	for mip6@ietf.org; Thu, 08 Mar 2007 18:27:42 -0500
Message-ID: <01a001c761d9$5944b120$2b6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jari Arkko" <jari.arkko@piuha.net>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
References: <459A5A6C.5070602@piuha.net>
	<eaa74a7e0702230640g722a28fcyc89360e69337c768@mail.gmail.com>
	<45E00DD3.1010701@piuha.net>
Subject: Re: [Mip6] AD review of draft-ietf-mip6-bootstrapping-split
Date: Thu, 8 Mar 2007 15:27:33 -0800
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: 6e922792024732fb1bb6f346e63517e4
X-Mailman-Approved-At: Fri, 16 Mar 2007 09:16:54 -0400
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

>>> >    Mobile IPv6 bootstrapping recommends the Home Agent to update the
>>> >    Mobile Node's FQDN with a dynamically assigned home address rather
>>> >    than have the Mobile Node itself do it (see Section 6 above). This
>>> >    choice was motivated by a concern for preventing redirection-based
>>> >    flooding attacks (see draft-ietf-mip6-ro-sec [21] for more
>>> >    information about redirection-based flooding attacks and the role
>>> >    preventing them played in the design of Mobile IPv6 route
>>> >    optimization security). Exactly as for route optimization, it is
>>> >    possible for a node that is the legitimate owner of a DNS FQDN -
>>> >    in the sense that it has a security association with the DNS
>>> >    server allowing it to perform dynamic DNS update of its FQDN - to
>>> >    bind its FQDN to the address of a victim, then redirect large
>>> >    volumes of traffic at the victim. The attack may be propagated
>>> >    without the owner's knowledge, for example, if the node is
>>> >    compromised by malware, or it may be intentional if the node
>>> >    itself is the attacker.
>>> >
>>> >    While it is possible to prevent redirection attacks through
>>> >    ingress filtering on access routers, ISPs have little or no
>>> >    incentive to deploy ingress filtering. In some cases, if an attack
>>> >    could result in substantial financial gain, it is even possible
>>> >    that a corrupt ISP may have an incentive not to deploy ingress
>>> >    filters such as has been the case for spam. Consequently, the
>>> >    security for dynamic Mobile Node FQDN update has been assigned to
>>> >    the Home Agent, where active network administration and vigilant
>>> >    defense measures are more likely to (but are not assured of)
>>> >    mitigating problems, and the owner of the Mobile Node is more
>>> >    likely to detect a problem if it occurs.
>>> There are good reasons why using a proxy to do the
>>> DynDNS update from your behalf makes sense. But I
>>> don't think the above is such a good reason.  The
>>> route optimization redirect problem assumes that
>>> traffic from an ongoing session is suddenly moved
>>> to a new address. If you just change the DNS information,
>>> ongoing sessions are not affected, and all new sessions
>>> go through the usual TCP slow start etc.
>>>
>>> (A good reason why it makes sense to use a proxy
>>> is that then you just need a secret between the
>>> DNS server and the home agent, not between the
>>> DNS server and every mobile node.)
>>>
>>
>> I'm fine with removing that text. However, I would like to hear
>> thoughts from James, since he has been very active in that part of the
>> draft.
>
> Ok.
>

Sure, go ahead and remove it. The point Jari raised about maintaining a 
single SA between the DNS server and the HA rather than multiple ones should 
be sufficient motivation.

>>
>>> >    Notice that if certificates are used in
>>> >    IKEv2, the authorization information about the FQDN for DNS update
>>> >    MUST be present in the certificate provided by the Mobile Node.
>>> Yes -- but can you write this in more explicit
>>> form? For instance, I assume that you meant
>>> the FQDN must appear in some specific field
>>> in the certificate.
>>>
>>
>> Yes, this is certainly one option. Again I would leave to James the
>> proposed text on this.
>>
>
> Ok. James?
>

It is a little tough to be more precise about this since the IKEv2 spec 
defines no less that 12 different certificate formats that may be used, and 
ultimately concludes that the exact certificate encoding is out of scope of 
the spec. In RFC 4718, Paul and Pasi recommend restricting use to only four 
types to facilitate interoperability. One of the recommended types in both 
documents is "X.509 Certificate - Signature". We could put more text in as 
follows:

       Since the IKEv2 specification [ref] does not include a required 
certificate
       type, it is not possible to specify precisely how the Moible Node's 
FQDN
       should appear in the certificate. However, as an example, if the 
certificate
       type is "X.509 Certificate - Signature" (one of the recommended 
types)
       then the FQDN may appear in the subjectAltName attribute
      extension [ref2].

[ref2] Housley, R., Polk, W., Ford, W., and Solo, D., "Internet X.509 Public 
Key Infrastructure Certificate and Certificate Revocation List (CRL) 
Profile", RFC 3280, April, 2002.

How does that sound?

                    jak





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



From mip6-bounces@ietf.org Fri Mar 16 09:40:06 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSCev-0007u7-E2; Fri, 16 Mar 2007 09:39:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSCeu-0007tj-D6; Fri, 16 Mar 2007 09:39:52 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HSCes-0007rF-VL; Fri, 16 Mar 2007 09:39:52 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id C0253198721;
	Fri, 16 Mar 2007 15:39:33 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 2F0B919871E;
	Fri, 16 Mar 2007 15:39:33 +0200 (EET)
Message-ID: <45FA925A.8020601@piuha.net>
Date: Fri, 16 Mar 2007 14:49:30 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>, 
	Monami6 Mailing List <monami6@ietf.org>, Nemo Mailing List <nemo@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: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Internet Area <int-area@ietf.org>
Subject: [Mip6] reorganization of Mobile IPv6 related working groups
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Jari Arkko <jari.arkko@piuha.net>, Internet Area <int-area@ietf.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi all,

We are planning to reorganize the MIP6, MONAMI6, and NEMO
working groups in the Internet Area. The idea is to merge
these three groups, all of which work around the Mobile IPv6
protocol and its extensions. The merge will not happen
immediately, but around the IETF69 time frame when
MIP6 has completed a few more of its work items, MONAMI6
has submitted its main specification, and NEMO has gotten
on its way with its newly chartered work. The resulting
working group will be bigger, but still committed to
completing work on all three aspects, i.e., base features,
support for multiple care-of addresses, and network
mobility. The chartered work items or their planned
delivery dates will not be changed because of this.

The reasons why we are making this change include

- Putting most of work around Mobile IPv6 and its extensions
  into one place, reducing the need to coordinate, and
  making it easier for new people and outsiders to see
  where this work is happening.

- The bigger group makes it easier to find reviewers,
  and have a complete picture of how the protocol is
  being extended.

- Provide a better ability to prioritize work and maybe
  add some competition for resources.

- Easier management for the ADs, needing to deal with
  one instead of three groups.

- Make room in the meeting schedule and area for BOFs
  and new groups. I have groups meeting at the same
  time in Prague, for instance.

- This is a good time for this change in the lifecycle
  of the three groups.

The detailed implementation of this change will take place
in the coming months, but we wanted to give everyone a heads-up
that this is going to happen. And an opportunity for comments,
we do appreciate feedback on this and other issues relating
to the management of the area. Speaking of comments -- this
note goes out to a number of lists, but please direct further
discussion to myself and the int-area list.

Jari and Mark



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



From mip6-bounces@ietf.org Fri Mar 16 15:05:54 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSHid-0006nq-0L; Fri, 16 Mar 2007 15:04:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSHia-0006na-Ky
	for mip6@ietf.org; Fri, 16 Mar 2007 15:04:00 -0400
Received: from neon.tcs.hut.fi ([130.233.215.20] helo=mail.tcs.hut.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSHiP-0004o0-1M
	for mip6@ietf.org; Fri, 16 Mar 2007 15:04:00 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by mail.tcs.hut.fi (Postfix) with ESMTP id 6506E2C020C75
	for <mip6@ietf.org>; Fri, 16 Mar 2007 21:03:48 +0200 (EET)
Date: Fri, 16 Mar 2007 21:03:48 +0200 (EET)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: mip6@ietf.org
Message-ID: <Pine.LNX.4.58.0703162103140.13498@rhea.tcs.hut.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [Mip6] Tunneling Optimization in Mobility Protocols
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

We've submitted a new proposal which removes IP tunneling in mobility
protocols. Please check:

http://www.ietf.org/internet-drafts/draft-haddad-mipshop-tunneling-optimization-00.txt

Comments appreciated.


Regards,

Wassim H.

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



From mip6-bounces@ietf.org Sat Mar 17 00:55:14 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSQtz-0007VX-Rx; Sat, 17 Mar 2007 00:52:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSQty-0007VS-Bj
	for mip6@ietf.org; Sat, 17 Mar 2007 00:52:22 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSQtw-0000PN-Qi
	for mip6@ietf.org; Sat, 17 Mar 2007 00:52:22 -0400
Received: OTM-MO(otm-mgo01) id l2H4pvoU001758;
	Sat, 17 Mar 2007 13:51:57 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2H4puoA041236;
	Sat, 17 Mar 2007 13:51:57 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2H4pI2t049682
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <mip6@ietf.org>; Sat, 17 Mar 2007 13:51:19 +0900 (JST)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <E1HPPYq-0007Jb-Qf@stiedprstage1.ietf.org>
References: <E1HPPYq-0007Jb-Qf@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EC22BF2F-A20C-43D2-8B97-642C11FF198C@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-04.txt 
Date: Sat, 17 Mar 2007 13:51:53 +0900
To: Mobile Mailing List IPv6 <mip6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

On 2007/03/09, at 5:50, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Mobility for IPv6 Working Group of  
> the IETF.
>
> 	Title		: Mobile IPv6 support for dual stack Hosts and Routers  
> (DSMIPv6)
> 	Author(s)	: H. Soliman
> 	Filename	: draft-ietf-mip6-nemo-v4traversal-04.txt
> 	Pages		: 23
> 	Date		: 2007-3-8
> 	
> The current Mobile IPv6 and NEMO specification support only IPv6.
>    Hence, this specification extends those standards to allow the
>    registration of IPv4 addresses and prefixes, respectively, and the
>    transport of both IPv4 and IPv6 packets over the tunnel to the HA.
>    This specification allows also the Mobile Node to roam over both  
> IPv6
>    and IPv4, including the case where Network Address Translation is
>    present on the path.


I think this question was discussed before, but I don't remember the  
final consensus on this.  If this is a duplicated question, sorry for  
that.

Why do we need to have multiple IPv4 encapsulation formats?  I wonder  
why we cannot simply use UDP encapsulation always.  What is the  
benefit of providing multiple encapsulation mechanisms?

If we can just specify the UDP encapsulation mechanism only, then  
both HA and MN don't have to implement IPv4 in IPv6 encapsulating  
process for DSMIPv6 and don't need to implement the selection  
mechanism to decide which mechanism to use.  Since IPv4 NAT is almost  
everywhere, I think simply providing UDP makes the implementation and  
operation easier.

---
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 Sat Mar 17 05:38:23 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSVKW-0001AG-Oh; Sat, 17 Mar 2007 05:36:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSVKV-0001A9-Da
	for mip6@ietf.org; Sat, 17 Mar 2007 05:36:03 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSVKT-00007U-AQ
	for mip6@ietf.org; Sat, 17 Mar 2007 05:36:03 -0400
Received: from [82.129.133.254] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HSVJv-0001LH-I4; Sat, 17 Mar 2007 20:35:28 +1100
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>,
	"'Mobile Mailing List IPv6'" <mip6@ietf.org>
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-04.txt 
Date: Sat, 17 Mar 2007 20:35:04 +1100
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.3028
In-Reply-To: <EC22BF2F-A20C-43D2-8B97-642C11FF198C@iijlab.net>
Thread-Index: AcdoUThTmGnbLdrLRSafa/WoNP358gAJcJDg
X-Spam-Score: 0.0 (/)
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
Message-Id: <E1HSVKW-0001AG-Oh@megatron.ietf.org>


 > I think this question was discussed before, but I don't 
 > remember the  
 > final consensus on this.  If this is a duplicated question, 
 > sorry for  
 > that.
 > 
 > Why do we need to have multiple IPv4 encapsulation formats?  
 > I wonder  
 > why we cannot simply use UDP encapsulation always.  What is the  
 > benefit of providing multiple encapsulation mechanisms?

=> One obvious answer is: saving bandwidth.

 > 
 > If we can just specify the UDP encapsulation mechanism only, then  
 > both HA and MN don't have to implement IPv4 in IPv6 encapsulating  
 > process for DSMIPv6 and don't need to implement the selection  
 > mechanism to decide which mechanism to use.  Since IPv4 NAT 
 > is almost  
 > everywhere, 

=> But encapsulating IPv4 in IPv6 has nothing to do with IPv4 NATs, It's a
scenario where the access network supports IPv6 and therefore you only use
IPv6 for the signalling. I don't see why we should add a UDP header. If the
tradeoff is between making an implementer's life easy by doing less work Vs
reducing bandwidth, I hope we would choose to reduce redundant bits. It
seems strange to add redundant bits just to make sure the implementer
doesn't have to implement IPv4 in IPv6 tunnels. 

Hesham

I think simply providing UDP makes the 
 > implementation and  
 > operation easier.
 > 
 > ---
 > 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
 > 



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



From mip6-bounces@ietf.org Sat Mar 17 08:30:23 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSY1J-0000YI-6R; Sat, 17 Mar 2007 08:28:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSY1I-0000YD-GM
	for mip6@ietf.org; Sat, 17 Mar 2007 08:28:24 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSY1G-0007M9-7V
	for mip6@ietf.org; Sat, 17 Mar 2007 08:28:24 -0400
Received: OTM-MO(otm-mgo01) id l2HCRiqC014260;
	Sat, 17 Mar 2007 21:27:44 +0900 (JST)
Received: OTM-MIX(otm-mix00) id l2HCRht6020508;
	Sat, 17 Mar 2007 21:27:43 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2HCR3mH051108
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 17 Mar 2007 21:27:05 +0900 (JST)
In-Reply-To: <20070317093529.D5734FB95A@sh1.iijlab.net>
References: <20070317093529.D5734FB95A@sh1.iijlab.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3008834B-B1CA-452E-AE08-A236B62A4017@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-04.txt 
Date: Sat, 17 Mar 2007 21:27:39 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: Mobile Mailing List IPv6 <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,

On 2007/03/17, at 18:35, Hesham Soliman wrote:

>> Why do we need to have multiple IPv4 encapsulation formats?
>> I wonder
>> why we cannot simply use UDP encapsulation always.  What is the
>> benefit of providing multiple encapsulation mechanisms?
>
> => One obvious answer is: saving bandwidth.

OK.  I understand there are some people requires to save the bytes,  
even if the bytes are just 8.


>> If we can just specify the UDP encapsulation mechanism only, then
>> both HA and MN don't have to implement IPv4 in IPv6 encapsulating
>> process for DSMIPv6 and don't need to implement the selection
>> mechanism to decide which mechanism to use.  Since IPv4 NAT
>> is almost
>> everywhere,
>
> => But encapsulating IPv4 in IPv6 has nothing to do with IPv4 NATs,  
> It's a
> scenario where the access network supports IPv6 and therefore you  
> only use
> IPv6 for the signalling. I don't see why we should add a UDP  
> header. If the
> tradeoff is between making an implementer's life easy by doing less  
> work Vs
> reducing bandwidth, I hope we would choose to reduce redundant  
> bits. It
> seems strange to add redundant bits just to make sure the implementer
> doesn't have to implement IPv4 in IPv6 tunnels.

Hum, I think I was not very successful to explain my idea.  I was not  
suggesting to use the UDP encap mode to save the bits.

In the current specification, a mobile node implementer must  
implement both the IPv6 in IPv4 encap mode and the IPv6 in UDPv4  
encap mode.  The mobile node uses the IPv4 encap mode normally, but  
it has to switch to the UDP encap mode, if its home agent suggests to  
use the UDP encapsulation mode.  I think if we can specify just one  
encap mode for the DSMIPv6 protocol, it helps implementors and also  
it will reduce the number of the interop test cases of the spec.

I don't have any preference between the IPv4 encap mode and the UDPv4  
encap mode, as long as it works even if the node is behind a NAT  
box.  I just wanted to simplify the operation by removing dynamic  
decision of encap mechanisms.

Regards,
---
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 Sun Mar 18 09:15:14 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSvD2-0007mF-Ci; Sun, 18 Mar 2007 09:14:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSvD1-0007mA-Ao
	for mip6@ietf.org; Sun, 18 Mar 2007 09:14:03 -0400
Received: from mail.unilim.fr ([164.81.1.45] helo=smtp.unilim.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSvCx-0000jW-Nt
	for mip6@ietf.org; Sun, 18 Mar 2007 09:14:03 -0400
Received: from [192.168.0.2] ([84.5.72.27]) (authenticated bits=0)
	by smtp.unilim.fr (8.13.1/8.13.1) with ESMTP id l2IDDnCD004495
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Sun, 18 Mar 2007 14:13:50 +0100
Message-ID: <45FD3B0C.8050209@xlim.fr>
Date: Sun, 18 Mar 2007 14:13:48 +0100
From: Damien Sauveron <damien.sauveron@xlim.fr>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Univ-Limoges-Greylist: Sender succeeded SMTP AUTH authentication, not
	delayed by milter-greylist-2.0.2 (smtp.unilim.fr [164.81.1.45]);
	Sun, 18 Mar 2007 14:13:50 +0100 (CET)
X-Univ-Limoges-MailScanner-Information: Serveur Anti-virus Please contact the
	SCI, Univ. of Limoges, for more information
X-Univ-Limoges-MailScanner: Found to be clean
X-Univ-Limoges-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (cached, score=-102.9, requis 6, autolearn=not spam,
	ALL_TRUSTED -1.80, BAYES_05 -1.11, NO_RDNS2 0.01, SMTP_AUTH -100.00)
X-Univ-Limoges-MailScanner-Envelope-From: damien.sauveron@xlim.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Subject: [Mip6] [WISTP'2007] First Call For Participation
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

*******************************************************************
We apologize in advance if you receive multiple copies of this CFP.
Please disseminate it to your colleagues that could be interested.
*******************************************************************

Workshop in Information Security Theory and Practices 2007: Smart Cards,
Mobile and Ubiquitous Computing Systems
                                  &&
A networking meeting to discuss proposals for the EU FP7

Heraklion, Crete, Greece
May 8-11, 2007

Workshop URL: http://wistp2007.xlim.fr/

Preliminary Program: http://wistp2007.xlim.fr/CFP.html#Preliminary_program

We are pleased to announce that Prof. Jean-Pierre Hubaux (LCA, EPFL,
Switzerland), Prof. Fred Piper (Information Security Group, Royal
Holloway University of London, UK), Caspar Bowden (Chief Privacy Advisor
EMEA -- Microsoft, UK), Patrick Waters (Head of Research and Development
in the Netherlands for Vodafone Group, NL) and two other speakers (to be
announced) will deliver keynote speeches.
http://wistp2007.xlim.fr/CFP.html#Keynote_Speakers

Regarding venue, hotel arrangement, workshop registration and visa
request, please visit http://wistp2007.xlim.fr/ for details.
http://wistp2007.xlim.fr/CFP/Registration_form.pdf
http://wistp2007.xlim.fr/CFP/venue_acc.html

Proceedings will be published by Springer LNCS.

*******************************************************
WISTP'2007 is:
- Co-Sponsored by IFIP TC6 Communications Systems
- Co-Sponsored by IFIP WG 8.8 Smart Cards
- Co-Sponsored by IFIP WG 11.2 Small System Security
- Co-Sponsored by The British Computer Society
- In Cooperation with the IEEE Computer Society, Technical Committee on
Security and Privacy (TCSP)
- In Cooperation with the IEEE Computer Society, Task Force on
Information Assurance (TFIA)
- In Cooperation with the IEEE Systems, Man, and Cybernetics Society,
Technical Committee on Information Assurance & Intelligent
Multimedia-Mobile Communications
- In Cooperation with the IEEE Systems, Man, and Cybernetics Society,
Technical Committee on Systems Safety and Security
- In Cooperation with the IEEE Vehicular Technology Society
- Supported by the IEEE Region 8
- Supported by the IEEE France Section
- Supported by the IEEE UKRI Section & by the IEEE UKRI Section -
Computer Society Chapter
- Supported by the IEEE Greece Section - Communications Society &
Computer Society & VT&AESS Chapters
- Supported by the ERCIM
- Supported by ACM Special Interest Group on Security, Audit and Control
(SIGSAC)
- Supported by the EuroSys (European ACM SIGOPS Chapter)
- Supported by the ASF (French ACM SIGOPS Chapter)
- Supported by the Greek Computer Society
- Supported by the ASTI
- Supported by the Institute for Systems and Technologies of
Information, Control and Communication (INSTICC)
- Supported by the SEE
- Supported by the GDR CNRS ASR
- Supported by the VDE ITG
- Supported by the Network of Excellence Euro-NGI
- Supported by the European Workshop on Industrial Computer Systems,
Technical Committee 7, Safety, Reliability and Security

*******************************************************
WISTP2007 Background and Goals:
With the rapid technological development of information technologies,
computer systems and especially embedded systems are becoming more
mobile and ubiquitous, increasingly interfacing with the physical world.
Ensuring  the security of these complex and yet, resource constraint
systems has emerged as one of the most pressing challenges.
The aim of this first workshop is to bring together researchers and
practitioners in related areas and to encourage interchange and
cooperation between the research community and the industrial/consumer
community.
The workshop will consist of technical paper presentations, one special
session for student papers and five invited talks.
To contribute to the structuring of the community, a networking meeting
to discuss EU FP7 projects proposals will take place just after the
workshop.

*******************************************************
Topics of interest include, but are not limited to:

A. Smart Cards and Trusted Devices Security

     * Biometrics, National ID cards
     * Embedded Systems Security and TPMs
     * Interplay of TPMs and Smart Cards
     * New Applications for Secure RFID Systems
     * RFID Systems Security
     * Smart Card Security
     * Smart Card Applications

B. Ad Hoc and Mobile Networks Security

     * Ad Hoc Networks Security
     * Delay-Tolerant Network Security
     * Domestic Network Security
     * Mobile Codes Security
     * Mobile Devices Security
     * Security Issues in Mobile and Ubiquitous Networks
     * Security of GSM/GPRS/UMTS Systems
     * Sensor Networks Security
     * Vehicular Network Security
     * Wireless Communication Security (WiFi, WiMAX, WiMedia, others)

C. Ubiquitous Computing Systems Security

     * Distributed Systems Security
     * Grid Computing Security
     * Intrusion Detection and Information Filtering
     * Peer-to-Peer Networks Security

D. Security Protocols, Policies and Management for Mobility

     * Critical Infrastructure (e.g. for Medical or Military
Applications) Security
     * Digital Rights Management (DRM)
     * Industrial and Multimedia  Applications
     * Information Assurance
     * Localization Systems Security (Tracking of People and Goods)
     * New Applications of Secure Systems
     * Public Administration and Governmental Services
     * Security Models and Architecture
     * Security Policies (Human-Computer Interaction and Human Behavior
Impact)
     * Security Protocols (for Identification and Authentication,
Confidentiality and Privacy, and Integrity)
     * Security Measurements
     * Trust Management

*******************************************************
Opportunities for students:
To help the students looking for a PhD thesis or a postdoctoral
position, we will propose them to add a colorized sticker on their
badge. In the same way, we will propose to persons offering these
positions to add a sticker with a different color. We hope this
mechanism will help to support the exchanges between young and senior
researchers.

*******************************************************
Thanks to our main sponsors:
http://wistp2007.xlim.fr/CFP.html#Main_sponsors
Crisp Telecom
Eurosmart
Elopsys
Limousin Expansion
Nokia
Vodafone
WILEY

*******************************************************
We hope you will be interested by this event.
For further inquiries, please contact the secretariat at
wistp2007sec@xlim.fr

Best regards,
-- 
Damien Sauveron


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



From mip6-bounces@ietf.org Sun Mar 18 09:44:02 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSvfP-0007k6-Il; Sun, 18 Mar 2007 09:43:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSvfO-0007k0-DT
	for mip6@ietf.org; Sun, 18 Mar 2007 09:43:22 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HSvfN-0003z1-3I
	for mip6@ietf.org; Sun, 18 Mar 2007 09:43:22 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-4.tower-119.messagelabs.com!1174225400!17200731!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 30243 invoked from network); 18 Mar 2007 13:43:20 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-4.tower-119.messagelabs.com with SMTP;
	18 Mar 2007 13:43:20 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2IDhBvv012649;
	Sun, 18 Mar 2007 06:43:11 -0700 (MST)
Received: from [10.129.40.16] ([10.129.40.16])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l2IDh983020597;
	Sun, 18 Mar 2007 08:43:10 -0500 (CDT)
Message-ID: <45FD41ED.1030907@gmail.com>
Date: Sun, 18 Mar 2007 14:43:09 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-04.txt
References: <20070317093529.D5734FB95A@sh1.iijlab.net>
	<3008834B-B1CA-452E-AE08-A236B62A4017@iijlab.net>
In-Reply-To: <3008834B-B1CA-452E-AE08-A236B62A4017@iijlab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: Mobile Mailing List IPv6 <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

Keiichi SHIMA wrote:
> Hi,
> 
> On 2007/03/17, at 18:35, Hesham Soliman wrote:
> 
>>> Why do we need to have multiple IPv4 encapsulation formats? I
>>> wonder why we cannot simply use UDP encapsulation always.  What
>>> is the benefit of providing multiple encapsulation mechanisms?
>> 
>> => One obvious answer is: saving bandwidth.
> 
> OK.  I understand there are some people requires to save the bytes,
> even if the bytes are just 8.
> 
> 
>>> If we can just specify the UDP encapsulation mechanism only, then
>>>  both HA and MN don't have to implement IPv4 in IPv6
>>> encapsulating process for DSMIPv6 and don't need to implement the
>>> selection mechanism to decide which mechanism to use.  Since IPv4
>>> NAT is almost everywhere,
>> 
>> => But encapsulating IPv4 in IPv6 has nothing to do with IPv4 NATs,
>>  It's a scenario where the access network supports IPv6 and
>> therefore you only use IPv6 for the signalling. I don't see why we
>> should add a UDP header. If the tradeoff is between making an
>> implementer's life easy by doing less work Vs reducing bandwidth, I
>> hope we would choose to reduce redundant bits. It seems strange to
>> add redundant bits just to make sure the implementer doesn't have
>> to implement IPv4 in IPv6 tunnels.
> 
> Hum, I think I was not very successful to explain my idea.  I was not
>  suggesting to use the UDP encap mode to save the bits.
> 
> In the current specification, a mobile node implementer must
> implement both the IPv6 in IPv4 encap mode and the IPv6 in UDPv4
> encap mode.  The mobile node uses the IPv4 encap mode normally, but
> it has to switch to the UDP encap mode, if its home agent suggests to
> use the UDP encapsulation mode.  I think if we can specify just one
> encap mode for the DSMIPv6 protocol, it helps implementors and also
> it will reduce the number of the interop test cases of the spec.
> 
> I don't have any preference between the IPv4 encap mode and the UDPv4
>  encap mode, as long as it works even if the node is behind a NAT
> box.  I just wanted to simplify the operation by removing dynamic
> decision of encap mechanisms.

I agree decision of encap mechanism is difficult to implement, deals 
with different data structures from different spaces.  I think there's 
more to this discussion.

 From protocol standpoint, it sounds strange to use UDP if not behind NAT.

It also sounds strange to use _only_ UDP even if behind NAT.  Some 
NAT/FWs allow IP-in-IP and don't allow UDP.

As implementer, IMHO, if all DS-MIPv6 control messages were exclusively 
MH, or exclusively UDP, then it would be better, IMHO, for simplifying 
implementation.

I mean I could live with control being MH/UDP and transport with 
IP-in-IP (not UDP).  Either of MH or UDP for control, but only one.

Not sure I'm clear...

Alex

> 
> Regards, --- 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
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From mip6-bounces@ietf.org Sun Mar 18 10:19:13 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSwDQ-0000WD-56; Sun, 18 Mar 2007 10:18:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSwDO-0000W3-66
	for mip6@ietf.org; Sun, 18 Mar 2007 10:18:30 -0400
Received: from mail.unilim.fr ([164.81.1.45] helo=smtp.unilim.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSwDM-00080k-Pe
	for mip6@ietf.org; Sun, 18 Mar 2007 10:18:30 -0400
Received: from [192.168.0.2] ([84.5.72.27]) (authenticated bits=0)
	by smtp.unilim.fr (8.13.1/8.13.1) with ESMTP id l2IEIQLj014446
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Sun, 18 Mar 2007 15:18:26 +0100
Message-ID: <45FD4A31.5030100@xlim.fr>
Date: Sun, 18 Mar 2007 15:18:25 +0100
From: Damien Sauveron <damien.sauveron@xlim.fr>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Univ-Limoges-Greylist: Sender succeeded SMTP AUTH authentication, not
	delayed by milter-greylist-2.0.2 (smtp.unilim.fr [164.81.1.45]);
	Sun, 18 Mar 2007 15:18:27 +0100 (CET)
X-Univ-Limoges-MailScanner-Information: Serveur Anti-virus Please contact the
	SCI, Univ. of Limoges, for more information
X-Univ-Limoges-MailScanner: Found to be clean
X-Univ-Limoges-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (cached, score=-101.789, requis 6, autolearn=not spam,
	ALL_TRUSTED -1.80, BAYES_50 0.00, NO_RDNS2 0.01, SMTP_AUTH -100.00)
X-Univ-Limoges-MailScanner-Envelope-From: damien.sauveron@xlim.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Mip6] [WISTP'2007] 4 Grants for Young Researchers sponsored by
	Nokia
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

*******************************************************************
We apologize in advance if you receive multiple copies of this CFP.
Please disseminate it to your colleagues that could be interested.
*******************************************************************

Workshop in Information Security Theory and Practices 2007: Smart Cards,
Mobile and Ubiquitous Computing Systems
                                  &&
A networking meeting to discuss proposals for the EU FP7

Heraklion, Crete, Greece
May 8-11, 2007

Workshop URL: http://wistp2007.xlim.fr/

Preliminary Program: http://wistp2007.xlim.fr/CFP.html#Preliminary_program

*******************************************************************
4 Grants for Young Researchers (PhD students or in postdoctoral
position) are sponsored by *Nokia*. These grants include accommodation
costs (3 nights in the hotel hosting the workshop) and registration fees
for the Workshop and the FP7 meeting. The travel is NOT funded.
*******************************************************************
Grant application:
  - Selection will be done by the Organizers and Chairs based on a short
CV (1 page maximum), a motivation letter (1 page maximum) and if
possible a recommendation letter
  - Send these documents to wistp2007sec@xlim.fr before the deadline
  - deadline: 6th of April 2007
  - notification of acceptance: 10th of April 2007

The selected applicants will provide one week maximum after the events a
short report (5 to 10 pages) written in english to summarize the
scientific and organizational aspects (to be discussed with the
organizers later).

*******************************************************
We hope you will be interested by this event.
For further inquiries, please contact the secretariat at
wistp2007sec@xlim.fr

Best regards,
-- 
Damien Sauveron





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



From mip6-bounces@ietf.org Mon Mar 19 14:51:35 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTMvM-0002zq-MV; Mon, 19 Mar 2007 14:49:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTMvK-0002zW-JY
	for mip6@ietf.org; Mon, 19 Mar 2007 14:49:38 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTMuc-0006Yr-TH
	for mip6@ietf.org; Mon, 19 Mar 2007 14:49:38 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 51A093570F;
	Mon, 19 Mar 2007 14:48:49 -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 F0C2B1774BC;
	Mon, 19 Mar 2007 18:48:48 +0000 (UTC)
Message-ID: <45FEDB10.2080201@hp.com>
Date: Mon, 19 Mar 2007 14:48:48 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt
References: <200703061243.l26Ch3hS013112@tao.fdupont.fr>
In-Reply-To: <200703061243.l26Ch3hS013112@tao.fdupont.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org, ietf-ipsec-failover.vpnc.org@tao.fdupont.fr,
	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 Francis,

Just re-reading emails before the WG meeting tomorrow and decided I 
should comment on this.

First, thanks for the comments, I do have a few questions.

Francis Dupont wrote:
> Comments about draft-ietf-mip6-ha-switch-03.txt:
> 
>  - I really like the draft as I believe the service it provides is needed
>   and is a major missing piece for MIPv6 in the real world but I have
>   a critical concern with it: it collides with the IPsec failover
>   activity, i.e., we could get two competiting mechanisms for the same
>   thing. So this issue must be solved before going further:
>    * obviously the basic mechanisms are the same: the server sends to the
>     client a "look-somewhere-else" message with a list of potential "better"
>     servers.
>    * when the message is delivered to the MIPv6 stack the information
>     must be propagated IKE, when it is deliveded to IKE (for instance by
>     a new notification) it must be propagated to the MIPv6 stack: in all
>     cases there must be an API between both.
>    * when the two mechanisms overlap they don't handle exactly the same
>     cases so we'll need a way to extend the coverage of the chosen one.
>    * IKE has a little advantage for the security because it has a secured
>     built-in reliable request/reply facility. At the opposite a new
>     MH message needs an extra SPD entry, retransmission policy, etc.

Sorry, I don't have any knowledge of the IPsec failover activity you 
mentioned and how it would compete with HA-switch.  Can you point me at 
a draft?  I don't follow any IETF IPsec-related WGs at the moment.

It is true that there might have to be some API between the network 
stack and IKE, but it won't be necessary in all cases (and like Hui 
mentioned, isn't a MIPv6-specific requirement).  In the HA-reliability 
case, the MN will have an SA with every HA already, so won't need to 
tell IKE to do anything during a switch.  In the non-HA-reliability case 
there will be more work for the MN to do.

I'm also not sure that trying to switch to using a different 
infrastructure (IKE) will fit in the timeframe in which a switch 
mechanism is required.

>  - 1.Introduction (comment): note the security function can be considered
>   as an integral part of the Home Agent service.

Did you want me to add some text?

>  - 4.1 Sending Home Agent Switch Messages "o A home  agent to mobile
>    node authentication option": this idle introduces a bidding down
>    security issue. I propose to say the authentication MUST use the
>    same mechanism than BU/BA (this is what we want and this should keep
>    everybody happy :-).

This issue will be on the slide at the WG meeting for discussion, I 
suppose it would make it both easier to specify and implement, and would 
support any future BU/BA security mechanism.

>  - 5.1 Receiving Home Agent Switch Messages "o The packet MUST be
>    authenticated, either...": same issue (and same proposed solution).
> 
>  - 5.1 Receiving Home Agent Switch Messages: the presentation can suggest
>    the connection to a new HA has to be done after leaving the current one
>    (obviously this is not the intended behavior).

There are two cases here:

1. Switch is from current HA - in this case you would break-before-make 
and teardown the old binding before replacing with one at the new HA. 
If we don't do this then ND-proxy could fail with the new HA, along with 
the BU.

2. Switch is from new HA - you would just send a BU to the new HA, 
assuming your current HA is dead.  This method is assumed in the 
HA-reliability case.

>  - 5.1 Receiving Home Agent Switch Messages:
>    perform home agent discovery -> perform home agent address discovery?
> 
>  - 9. Security Considerations: again...
> 
>  - 9. Security Considerations: use the home agent -> use a home agent?

Thanks for the other editorial changes, I'll fix them in -04.

-Brian

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



From mip6-bounces@ietf.org Tue Mar 20 05:02:24 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTaDQ-0001Zp-Lw; Tue, 20 Mar 2007 05:01:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTaDO-0001Zf-TU
	for mip6@ietf.org; Tue, 20 Mar 2007 05:01:10 -0400
Received: from tao.fdupont.fr ([82.236.136.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTaDL-0007zS-Qw
	for mip6@ietf.org; Tue, 20 Mar 2007 05:01:09 -0400
Received: from tao.fdupont.fr (localhost [127.0.0.1])
	by tao.fdupont.fr (8.13.5/8.13.5) with ESMTP id l2K910NV023546;
	Tue, 20 Mar 2007 10:01:01 +0100 (CET)
Received: from tao.fdupont.fr (dupont@localhost)
	by tao.fdupont.fr (8.13.5/8.13.5/Submit) with ESMTP id l2K90wSD023540; 
	Tue, 20 Mar 2007 10:00:59 +0100 (CET)
Message-Id: <200703200900.l2K90wSD023540@tao.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt 
In-reply-to: Your message of Mon, 19 Mar 2007 14:48:48 -0400.
	<45FEDB10.2080201@hp.com> 
Date: Tue, 20 Mar 2007 10:00:58 +0100
X-Spam-Score: 1.7 (+)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: mip6@ietf.org, ietf-ipsec-failover@vpnc.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

 In your previous mail you wrote:

   Hi Francis,
   
   Just re-reading emails before the WG meeting tomorrow and decided I 
   should comment on this.
   
   First, thanks for the comments, I do have a few questions.
   
   Francis Dupont wrote:
   > Comments about draft-ietf-mip6-ha-switch-03.txt:
   > 
   >  - I really like the draft as I believe the service it provides is needed
   >   and is a major missing piece for MIPv6 in the real world but I have
   >   a critical concern with it: it collides with the IPsec failover
   >   activity, i.e., we could get two competiting mechanisms for the same
   >   thing. So this issue must be solved before going further:
   >    * obviously the basic mechanisms are the same: the server sends to the
   >     client a "look-somewhere-else" message with a list of potential "better"
   >     servers.
   >    * when the message is delivered to the MIPv6 stack the information
   >     must be propagated IKE, when it is deliveded to IKE (for instance by
   >     a new notification) it must be propagated to the MIPv6 stack: in all
   >     cases there must be an API between both.
   >    * when the two mechanisms overlap they don't handle exactly the same
   >     cases so we'll need a way to extend the coverage of the chosen one.
   >    * IKE has a little advantage for the security because it has a secured
   >     built-in reliable request/reply facility. At the opposite a new
   >     MH message needs an extra SPD entry, retransmission policy, etc.
   
=> as I've fixed the IPsec failover list address I've kept this long part.

   Sorry, I don't have any knowledge of the IPsec failover activity you 
   mentioned and how it would compete with HA-switch.  Can you point me at 
   a draft?  I don't follow any IETF IPsec-related WGs at the moment.
   
=> IMHO the easiest and fastest way is to go and/or read the agenda of
the "ifare" BOF (tomorrow morning).

   It is true that there might have to be some API between the network 
   stack and IKE, but it won't be necessary in all cases (and like Hui 
   mentioned, isn't a MIPv6-specific requirement).  In the HA-reliability 
   case, the MN will have an SA with every HA already, so won't need to 
   tell IKE to do anything during a switch.

=> can I translate this into it doesn't matter to keep unused IPsec SAs
until they timeout?

   In the non-HA-reliability case  there will be more work for the MN to do.
   
   I'm also not sure that trying to switch to using a different 
   infrastructure (IKE) will fit in the timeframe in which a switch 
   mechanism is required.
   
=> collaboration can help, no collaboration is likely a source of slow down.

   >  - 1.Introduction (comment): note the security function can be considered
   >   as an integral part of the Home Agent service.
   
   Did you want me to add some text?
   
=> IMHO only on good opportunity or if someone (else) asks for this.

   >  - 4.1 Sending Home Agent Switch Messages "o A home  agent to mobile
   >    node authentication option": this idle introduces a bidding down
   >    security issue. I propose to say the authentication MUST use the
   >    same mechanism than BU/BA (this is what we want and this should keep
   >    everybody happy :-).
   
   This issue will be on the slide at the WG meeting for discussion, I 
   suppose it would make it both easier to specify and implement, and would 
   support any future BU/BA security mechanism.
   
=> what do you think about my proposal?

   >  - 5.1 Receiving Home Agent Switch Messages "o The packet MUST be
   >    authenticated, either...": same issue (and same proposed solution).
   > 
   >  - 5.1 Receiving Home Agent Switch Messages: the presentation can suggest
   >    the connection to a new HA has to be done after leaving the current one
   >    (obviously this is not the intended behavior).
   
   There are two cases here:
   
   1. Switch is from current HA - in this case you would break-before-make 
   and teardown the old binding before replacing with one at the new HA. 
   If we don't do this then ND-proxy could fail with the new HA, along with 
   the BU.
   
=> IMHO this is not so clear:
 - the current HA can be clever enough to avoid the ND-proxy issue because
  it knows exactly what should happen.
 - when you move to another home link there is not possible ND-proxy issue.
So the problem is not a wording problem as I believed, perhaps we need
an explicit "break-before-make is authorized" notification.

   2. Switch is from new HA - you would just send a BU to the new HA, 
   assuming your current HA is dead.  This method is assumed in the 
   HA-reliability case.
   
Thanks

Francis.Dupont@fdupont.fr

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



From mip6-bounces@ietf.org Tue Mar 20 05:53:04 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTb1C-0003hy-L5; Tue, 20 Mar 2007 05:52:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTb1B-0003h8-4R
	for mip6@ietf.org; Tue, 20 Mar 2007 05:52:37 -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 1HTb15-0000ts-FU
	for mip6@ietf.org; Tue, 20 Mar 2007 05:52:37 -0400
Received: (qmail 16634 invoked from network); 20 Mar 2007 18:52:12 +0900
Received: from  (HELO MIP6-236) (@) by  with SMTP; 20 Mar 2007 18:52:12 +0900
To: mip6@ietf.org, nemo@ietf.org
From: "K.Kawaguchi" <kawaguti@ysknet.co.jp>
Message-Id: <200703201852.FGE13085.UBJXLBVH@ysknet.co.jp>
X-Mailer: Winbiff [Version 2.43 PL1]
X-Accept-Language: ja,en
Date: Tue, 20 Mar 2007 18:52:12 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
Subject: [Mip6] [TAHI Test Event] Registration for the TAHI event is started!
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Dear all,

# sorry if you received multiple times of this kind of email.

Registration for the 9th TAHI IPv6 Interoperability Test event is
started today!

If you are planning to participate to the event, you can register in
	 http://www.tahi.org/inop/9thinterop.html

Note : The early registration discount is until 17:00 JST Apr. 16, 2007.

         The registration deadline is 17:00 JST Apr. 27, 2007.

And you can get detailed information about the event in the URL.

Summary information of the event.
    - Venue: Nippon Convention Center (Makuhari Messe), Chiba, Japan.
    - Date: May 14 - May 18, 2007
    - Registration & Information:
http://www.tahi.org/inop/9thinterop.html

We are waiting for your participation.

We are looking forward to see you at 9th TAHI evnet!


Best regards,
-------------------
Kiyoaki Kawaguchi


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



From mip6-bounces@ietf.org Tue Mar 20 11:33:08 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTgI8-0001e6-UW; Tue, 20 Mar 2007 11:30:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTgI7-0001dq-4V
	for mip6@ietf.org; Tue, 20 Mar 2007 11:30:27 -0400
Received: from av12-1-sn2.hy.skanova.net ([81.228.8.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTgHx-0005Wq-Fx
	for mip6@ietf.org; Tue, 20 Mar 2007 11:30:27 -0400
Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 43442382F2; Tue, 20 Mar 2007 16:29:58 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93])
	by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id 1B03E381A1
	for <mip6@ietf.org>; Tue, 20 Mar 2007 16:29:58 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 0C42937E44
	for <mip6@ietf.org>; Tue, 20 Mar 2007 16:29:57 +0100 (CET)
Received: from shiraz.local.levkowetz.com ([192.168.3.14] helo=levkowetz.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <roundup-admin@mip4.org>) id 1HTgHB-0002lc-PJ
	for mip6@ietf.org; Tue, 20 Mar 2007 16:29:57 +0100
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Keiichi SHIMA <tracker-mip6@mip4.org>
Date: Tue, 20 Mar 2007 15:29:20 +0000
MIME-Version: 1.0
Message-Id: <1174404560.07.0.659815063549.issue94@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Rcpt-To: mip6@ietf.org
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on 
	shiraz.levkowetz.com
X-Spam-Level: 
X-Spam-Status: No, score=-104.4 required=2.5 tests=ALL_TRUSTED,BAYES_00,
	USER_IN_WHITELIST autolearn=no version=3.1.7-deb
X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


New submission from Keiichi SHIMA <keiichi@iijlab.net>:

The current DSMIPv6 draft specifies two encapsulation formats, one is the I=
Pv4 encap format, the other is=20
UDPv4 encap format.  The default encapsulation format is the IPv4 format, a=
nd if the HA explicitly=20
specifies to change the encapsulation format to the UDPv4 format if there i=
s a NAT box between the HA=20
and the MN.  Because of this specification, HA and MN have to support both =
encapsulation formats and=20
have to change the format dynamically, that may increase the hurdle for imp=
lementors and may cause=20
complexity in interoperability.

Isn't it possible to fix the encapsulation format to one of these mechanism=
s described in the draft?

----------
category: Technical
draft: draft-ietf-mip6-nemo-v4traversal
messages: 338
nosy: keiichi
priority: May fix
status: No discussion
title: fixing encapsulation mechanism in IPv4 network

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

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



From mip6-bounces@ietf.org Tue Mar 20 11:56:43 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTgfQ-0006On-VW; Tue, 20 Mar 2007 11:54:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTEDA-0007K8-WC
	for mip6@ietf.org; Mon, 19 Mar 2007 05:31:29 -0400
Received: from [2001:200:180:299:202:b3ff:fe88:5b64]
	(helo=yui.nc.u-tokyo.ac.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTED7-000892-Bt
	for mip6@ietf.org; Mon, 19 Mar 2007 05:31:28 -0400
Received: from [130.129.17.213] (dhcp-11d5.ietf68.org [130.129.17.213])
	(authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	l2J9Uqrr021053; Mon, 19 Mar 2007 18:30:54 +0900
In-Reply-To: <B7ECEB1AACA1A548827BEACE75B03CB801298CC6@helios2.clb.tcfr.thales>
References: <B7ECEB1AACA1A548827BEACE75B03CB801298CC6@helios2.clb.tcfr.thales>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <15B96A91-2CBD-4633-9E8B-599B31881093@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Date: Mon, 19 Mar 2007 10:30:51 +0100
To: Tobias.HOF@fr.thalesgroup.com
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
X-Mailman-Approved-At: Tue, 20 Mar 2007 11:54:31 -0400
Cc: mip6@ietf.org, hareliability@mobileip.jp
Subject: [Mip6] Re: Questions on HA reliability draft
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Dear Tobias

Thanks for comments.
Please find my comments inline.

On 2007/03/19, at 10:10, Tobias.HOF@fr.thalesgroup.com wrote:

> Hello Ryuji,
>
> first of all, please allow me to introduce myself: I am working as  
> a networking engineer in an R&D team of Thales Communications in  
> France, where I focus on mobility and security aspects, mainly in  
> IPv6 networks.
>
> In the context of one our research projects, we are very interested  
> in HA multiplication in order to increase redundancy of the MIPv6/ 
> Nemo architecture.This is why we studied your draft describing the  
> synchronization between an Active HA and a Standby HA (Home Agent  
> Reliability).
>
> However, I still have some questions regarding the draft, I hope  
> you can answer them or give me your opinion.
>
>
> 1) Redundancy Home Agent Set = Pair or Group of HAs?
> ---------------------------------------------------------------------- 
> -------------
> From the draft, it's not clear to me if the Redundant Home Agent  
> set is a pair of one Active Home Agent and a single Standby Home  
> Agent or if there are multiple Standby Home Agents. In the  
> terminology part, you define it as a pair, however, in the  
> remainder of the draft, the descriptions always speak of multiple  
> Standby HAs per Active Home Agent (e.g. section 6.1).


Redundancy HA set is for group of HAs.

>
> In case there can be several Standby Home Agents (SHA) per Active  
> Home Agent (AHA), I see the following additional complexity for the  
> Home Agent Hello protocol:
> If the AHA has several SHAs, each of the SHAs must have a different  
> preference value, which is announced in the Hello Message.  
> Furthermore, I suppose that each SHAs is supposed to listen to the  
> AHA's heartbeats.
> But, the SHAs must also exchange Hello messages between themselves,  
> and this in a fully meshed manner, .i.e. each SHA to each of its  
> partner SHAs, in order to
>   1. discover if there are SHAs with higher preferences
>   2. detect if at least one of the SHAs with a higher preference is  
> still alive
>
> I had a look on VRRP to see how they handle this issue, but they  
> also focus on the case of a single backup router.

This is up to operation, but i can say that if SHA is deployed on a  
same link (local HA recovery).
Hello message can be sent to the all-router-multicast address. Thus,  
we can avoid meshed exchange.


>
> 2) Delegation of only a part of the bindings from the AHA to a/the SHA
> ---------------------------------------------------------------------- 
> --------------------------------
> The mechanisms you describe section 4.4 (Fig.3) show how an AHA can  
> delegate all its bindings to its SHA, e.g. in the case that it will  
> go down for maintenance. You also show how the ex-AHA can get back  
> all its bindings when it come back to live.
>
> However, I think that we should also consider the case where an AHA  
> only wants to delegate some of its bindings to a SHA. For example,  
> this can be very interesting if you think of load-balancing between  
> HAs: If the AHA starts to get saturated (e.g. going over a pre- 
> defined number of bindings or a given datarate on its outgoing  
> interface), it should start to handover new bindings to another HA.
>
> Can the current specifications do this or do you consider this out  
> of scope of the current HA reliability draft?

it depends on which switch mode you assume in your case.
If it is virtual switch case, it is impossible because only
AHA activates the HA address on its interface.
Of course, like VRRP, you can define two set of redundancy pairs
for the same HAs: each HA acts as SHA and AHA simultaneously.

However in the hard switch mode, AHA can send a HA switch message to  
a MN
in order to change AHA to one of SHA.
AHA can be defined per MN in the HA hard switch case.

The following section may imply your case.
       Since each home agent has a different address, an active home
       agent can be defined for each mobile node.  When a mobile node
       boots, it will discover home agents and create IPsec SAs with
       them.  It will then decide which one of the home agents is its
       active home agent.  For example, when two home agents serve a  
home
       network, half of the mobile nodes might register with one home
       agent and the rest of mobile nodes with another home agent.  When
       one of the home agents fails, a standby home agent, whose
       preference value is next highest than the failed home agent, can
       trigger a home agent switch by sending a Home Agent Switch  
message
       to the mobile nodes that were registered with the failed home
       agent.

One reminder is that load-balancing is out of scope in this document  
according to MIP6 charter.


>
> 3) Terminology: SwitchBack vs. SwitchOver
> ---------------------------------------------------------------
> I am curious to know how it comes that you call the initial request  
> from a AHA to a SHA "SwitchBACK" and then the request to get back  
> the bindings "SwitchOVER". Maybe I would have chosen the same  
> terms, but I think I would have assigned them the other way round,  
> as I think you can only ask to switch _back_ something which has  
> been the other way round before. So, I would propose to use  
> "SwitchOver" for the initial message (first part of fig. 3) and  
> "SwitchBack" when the inital HA comes back to life.
>

:-)
This message was introduced by one of DT.
I will discuss your comment in DT.

ryuji

> I really appreciate your opinion on these points and I thank you in  
> advance for your answers!
>
> I send this mail directly to you and no to the ML, but if you  
> consider it appropriate to discuss it there, I can post it there as  
> well.
>
> Best regards,
> Tobias
>


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



From mip6-bounces@ietf.org Tue Mar 20 12:05:00 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTgnT-00009w-KP; Tue, 20 Mar 2007 12:02:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTgnS-00008o-75
	for mip6@ietf.org; Tue, 20 Mar 2007 12:02:50 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTgnP-0001CR-SH
	for mip6@ietf.org; Tue, 20 Mar 2007 12:02:50 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 09:02:40 -0700
Message-ID: <4600059A.6010502@azairenet.com>
Date: Tue, 20 Mar 2007 09:02:34 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>, 
	Alper Yegin <alper.yegin@yegin.org>, Heejin Jang <heejin.jang@samsung.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Mar 2007 16:02:40.0614 (UTC)
	FILETIME=[2FEAC060:01C76B09]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Redundant text in the two DHCPv6-based bootstrapping
	documents
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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

There is some redundant text in the two documents that talk about using 
DHCPv6 for MIP6 bootstrapping, draft-ietf-mip6-hiopt-02.txt and 
draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt. Here are a couple 
of instances.

Mobile Node behavior for sending the DHCPv6 Information Request
---------------------------------------------------------------

 From draft-ietf-mip6-hiopt-02.txt

    In order to acquire the home network information, the mobile node
    SHALL send an Information Request to the
    All_DHCP_Relay_Agents_and_Servers multicast address.  In this message
    the mobile node (DHCP client) SHALL include the Option Code for Home
    Network Identifier option in the OPTION_ORO.  The mobile node SHALL
    also include the OPTION_CLIENTID [4] to identify itself to the DHCP
    server.

    During requesting the information, the mobile node MUST clarify the
    preference about the requested home network with the id-type in the
    Home Network Identifier option.  Even if the mobile node does not
    care about the location of the home network where the home agent to
    be assigned, it MUST clarify the fact by setting the id-type to 2.
    In this case the Home Network Identifier MUST be set to 0.

 From draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt

    (2) The mobile node sends a DHCPv6 Information Request message
    [RFC3315] to the All_DHCP_Relay_Agents_and_Servers multicast address.
    In this message the mobile node (DHCP client) SHALL include the
    Option Code for Home Network Identifier Option [HIOPT] in the
    OPTION_ORO, Home Network Identifier Option with id-type set to 1 and
    the Home Network Identifier field set to the network realm of the
    home MSP [HIOPT].  The mobile node SHALL also include the
    OPTION_CLIENTID to identify itself to the DHCP server.


NAS/DHCP relay behavior
-----------------------

 From draft-ietf-mip6-hiopt-02.txt

    Upon receiving the Information Request from the mobile node, the DHCP
    relay agent MUST forward the message to the DHCP server as per [4].
    The relay agent SHALL use the OPTION_CLIENTID to identify the mobile
    node (user).  This is required to check whether there are some
    additional information for the user that need to be appended while
    relaying the information request message to the DHCP server.  If the
    relay agent determines that the NAS has passed home network
    information for this mobile node, the relay agent MUST include the
    received home network information in the MIP6 Relay Agent option, and
    attach this option in the Relay-Forward message.  The relay agent MAY
    include the Interface-Id option [4] in the Relay-Forward message.

 From draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt

    (3) The Relay Agent intercepts the Information Request from the
    mobile node and forwards it to the DHCP server.  The Relay Agent also
    includes the received home agent information from the AAAH in the
    OPTION_MIP6-RELAY-Option [HIOPT].

I would prefer it if one document describes the protocol and the other 
just defines the options.

I also find it a bit odd that draft-ietf-mip6-hiopt-02.txt does not 
refer to draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt at all. It 
is listed among the references, but not anywhere in the text. I would 
have expected it to say that hiopt draft defines options that are used 
in the integrated scenario solution document.

Vijay

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



From mip6-bounces@ietf.org Tue Mar 20 12:31:16 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HThDg-0003Rz-Vl; Tue, 20 Mar 2007 12:29:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HThDg-0003Ru-Js
	for mip6@ietf.org; Tue, 20 Mar 2007 12:29:56 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HThDe-0005wX-5y
	for mip6@ietf.org; Tue, 20 Mar 2007 12:29:56 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-7.tower-119.messagelabs.com!1174406592!10777334!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 29778 invoked from network); 20 Mar 2007 16:03:12 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-7.tower-119.messagelabs.com with SMTP;
	20 Mar 2007 16:03:12 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2KG3Chs006437
	for <mip6@ietf.org>; Tue, 20 Mar 2007 09:03:12 -0700 (MST)
Received: from [10.129.41.39] ([10.129.41.39])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l2KG3B5f027303
	for <mip6@ietf.org>; Tue, 20 Mar 2007 11:03:11 -0500 (CDT)
Message-ID: <460005BE.4060306@gmail.com>
Date: Tue, 20 Mar 2007 17:03:10 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
CC: mip6@ietf.org
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
References: <1174404560.07.0.659815063549.issue94@mip4.org>
In-Reply-To: <1174404560.07.0.659815063549.issue94@mip4.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 only one encapsulation mechanism (for traversing IPv4) is 
something useful, as opposed to implementing always two encapsulating 
mechanisms.

I'm not sure that UDP is the right answer for that.  IPv4-in-IPv4 
mechanisms (without UDP) have their advantages: less packet overhead. 
They have inconvenients that they should be mainly in kernelspace 
(constraints).

Would it be possible to have DS-MIPv6 implementation with one big MIB 
knob that says:
-use UDP for BU signalling, traffic encap and NAT traversal.
or
-use IPv4-in-IPv4 for BU signalling, traffic encap and NAT traversal.

But I'll agree with what's suggested as already implemented.

Alex

Keiichi SHIMA wrote:
> New submission from Keiichi SHIMA <keiichi@iijlab.net>:
> 
> The current DSMIPv6 draft specifies two encapsulation formats, one is the IPv4 encap format, the other is 
> UDPv4 encap format.  The default encapsulation format is the IPv4 format, and if the HA explicitly 
> specifies to change the encapsulation format to the UDPv4 format if there is a NAT box between the HA 
> and the MN.  Because of this specification, HA and MN have to support both encapsulation formats and 
> have to change the format dynamically, that may increase the hurdle for implementors and may cause 
> complexity in interoperability.
> 
> Isn't it possible to fix the encapsulation format to one of these mechanisms described in the draft?
> 
> ----------
> category: Technical
> draft: draft-ietf-mip6-nemo-v4traversal
> messages: 338
> nosy: keiichi
> priority: May fix
> status: No discussion
> title: fixing encapsulation mechanism in IPv4 network
> 
> _________________________________________________
> Mip6 issue tracker <tracker-mip6@mip4.org>
> <http://www.mip4.org/issues/tracker/mip6/issue94>
> _________________________________________________
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From mip6-bounces@ietf.org Tue Mar 20 13:02:28 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HThhD-0006s0-NO; Tue, 20 Mar 2007 13:00:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HThhC-0006r7-Em
	for mip6@ietf.org; Tue, 20 Mar 2007 13:00:26 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HThgl-000447-UI
	for mip6@ietf.org; Tue, 20 Mar 2007 13:00:26 -0400
Received: from [127.0.0.1] ([130.129.16.59]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 09:59:59 -0700
Message-ID: <4600130A.60204@azairenet.com>
Date: Tue, 20 Mar 2007 09:59:54 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mip6 issue tracker <tracker-mip6@mip4.org>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
References: <1174404560.07.0.659815063549.issue94@mip4.org>
In-Reply-To: <1174404560.07.0.659815063549.issue94@mip4.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Mar 2007 16:59:59.0301 (UTC)
	FILETIME=[3188BF50:01C76B11]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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

Hello,

Keiichi SHIMA wrote:
> New submission from Keiichi SHIMA <keiichi@iijlab.net>:
> 
> The current DSMIPv6 draft specifies two encapsulation formats, one is the IPv4 encap format, the other is 
> UDPv4 encap format.  The default encapsulation format is the IPv4 format, and if the HA explicitly 
> specifies to change the encapsulation format to the UDPv4 format if there is a NAT box between the HA 
> and the MN.  Because of this specification, HA and MN have to support both encapsulation formats and 
> have to change the format dynamically, that may increase the hurdle for implementors and may cause 
> complexity in interoperability.

If I remember right, this was among the first few issues that
were discussed in the design team. Some folks did suggest
turning on UDP all the time when the access network is IPv4.
But this is an overhead in case there is no NAT. Thats why
we have a NAT detection mechanism in the DS-MIPv6. UDP
encapsulation is turned on only if a NAT is detected. My
preference is to still go with this.

> Isn't it possible to fix the encapsulation format to one of these mechanisms described in the draft?

If we are to pick only one encapsulation format, we clearly
can't pick "IPv4 encap format" (as you called it) because it
may not work through a NAT. It has to be UDP encapsulation
always.

Vijay

> 
> ----------
> category: Technical
> draft: draft-ietf-mip6-nemo-v4traversal
> messages: 338
> nosy: keiichi
> priority: May fix
> status: No discussion
> title: fixing encapsulation mechanism in IPv4 network
> 
> _________________________________________________
> Mip6 issue tracker <tracker-mip6@mip4.org>
> <http://www.mip4.org/issues/tracker/mip6/issue94>
> _________________________________________________
> 
> _______________________________________________
> 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 Mar 20 13:27:36 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTi6L-0007do-DQ; Tue, 20 Mar 2007 13:26:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTi6K-0007bR-HY
	for mip6@ietf.org; Tue, 20 Mar 2007 13:26:24 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTi5y-0008VY-Iq
	for mip6@ietf.org; Tue, 20 Mar 2007 13:26:24 -0400
Received: from [130.129.64.9] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HTi5X-0001n7-Vo; Wed, 21 Mar 2007 04:25:36 +1100
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Mip6 issue tracker'" <tracker-mip6@mip4.org>,
	<mip6@ietf.org>
Subject: RE: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 21 Mar 2007 04:25:12 +1100
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: <1174404560.07.0.659815063549.issue94@mip4.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdrBROHIB0pxAe9QbSvSsOJA+uhdwADxnoQ
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
Message-Id: <E1HTi6L-0007do-DQ@megatron.ietf.org>

Keiichi, 

We will have a formal concensus call on this but let's here a few opinions
first. My opinion below:
 

 > New submission from Keiichi SHIMA <keiichi@iijlab.net>:
 > 
 > The current DSMIPv6 draft specifies two encapsulation 
 > formats, one is the IPv4 encap format, the other is 
 > UDPv4 encap format.  The default encapsulation format is the 
 > IPv4 format, and if the HA explicitly 
 > specifies to change the encapsulation format to the UDPv4 
 > format if there is a NAT box between the HA 
 > and the MN.  Because of this specification, HA and MN have 
 > to support both encapsulation formats and 
 > have to change the format dynamically, that may increase the 
 > hurdle for implementors and may cause 
 > complexity in interoperability.
 > 
 > Isn't it possible to fix the encapsulation format to one of 
 > these mechanisms described in the draft?

=> So basically you're asking for UDP-only tunnelling. As I mentioned in a
previous email, this a tradeoff between reducing the implementer's work and
reducing redundant bits on the wire. I think it makes more sense to reduce
additional bits on the wire. The UDP tunnel is redundant if no NAT were
detected. So your suggestion amounts to removing NAT detection and always
using UDP tunnels. I think this is inefficient, especially when the cost of
switching between the UDP tunnel and IP n IP is very small (from an
implementation point of view). 

Hesham

 > 
 > ----------
 > category: Technical
 > draft: draft-ietf-mip6-nemo-v4traversal
 > messages: 338
 > nosy: keiichi
 > priority: May fix
 > status: No discussion
 > title: fixing encapsulation mechanism in IPv4 network
 > 
 > _________________________________________________
 > Mip6 issue tracker <tracker-mip6@mip4.org>
 > <http://www.mip4.org/issues/tracker/mip6/issue94>
 > _________________________________________________
 > 
 > _______________________________________________
 > 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 Mar 20 14:41:02 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTjF3-0004hT-4U; Tue, 20 Mar 2007 14:39:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTjF1-0004g7-RT
	for mip6@ietf.org; Tue, 20 Mar 2007 14:39:27 -0400
Received: from vms044pub.verizon.net ([206.46.252.44])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTjF0-0003oz-6v
	for mip6@ietf.org; Tue, 20 Mar 2007 14:39:27 -0400
Received: from vms168.mailsrvcs.net ([192.168.2.2])
	by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JF70057ESVDP7J5@vms044.mailsrvcs.net> for
	mip6@ietf.org; Tue, 20 Mar 2007 13:33:14 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms168.mailsrvcs.net (Verizon Webmail) with HTTP; Tue,
	20 Mar 2007 13:33:13 -0500 (CDT)
Date: Tue, 20 Mar 2007 13:33:13 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
X-Originating-IP: [129.55.200.20]
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>,
	Mip6 issue tracker <tracker-mip6@mip4.org>
Message-id: <28088593.563511174415593769.JavaMail.root@vms168.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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,

>Hello,
>
>Keiichi SHIMA wrote:
>> New submission from Keiichi SHIMA <keiichi@iijlab.net>:
>> 
>> The current DSMIPv6 draft specifies two encapsulation formats, one is the IPv4 encap format, the other is 
>> UDPv4 encap format.  The default encapsulation format is the IPv4 format, and if the HA explicitly 
>> specifies to change the encapsulation format to the UDPv4 format if there is a NAT box between the HA 
>> and the MN.  Because of this specification, HA and MN have to support both encapsulation formats and 
>> have to change the format dynamically, that may increase the hurdle for implementors and may cause 
>> complexity in interoperability.
>
>If I remember right, this was among the first few issues that
>were discussed in the design team. Some folks did suggest
>turning on UDP all the time when the access network is IPv4.
>But this is an overhead in case there is no NAT.
 Thats why
>we have a NAT detection mechanism in the DS-MIPv6. UDP
>encapsulation is turned on only if a NAT is detected. My
>preference is to still go with this.
>

FWIW, I agree that the NAT detection mechanism in DS-MIPv6 is the better way to go. 

Best Regards,

Tim Enos
Rom 8:28

<snip>

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



From mip6-bounces@ietf.org Tue Mar 20 15:10:09 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTjh8-0001fy-9C; Tue, 20 Mar 2007 15:08:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTjh7-0001fs-Ii
	for mip6@ietf.org; Tue, 20 Mar 2007 15:08:29 -0400
Received: from atlrel8.hp.com ([156.153.255.206])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTjh6-00083q-6U
	for mip6@ietf.org; Tue, 20 Mar 2007 15:08:29 -0400
Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114])
	by atlrel8.hp.com (Postfix) with ESMTP id F27D434576;
	Tue, 20 Mar 2007 15:08:16 -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 DED3317838F;
	Tue, 20 Mar 2007 19:08:11 +0000 (UTC)
Message-ID: <4600311A.4060402@hp.com>
Date: Tue, 20 Mar 2007 15:08:10 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt
References: <200703200900.l2K90wSD023540@tao.fdupont.fr>
In-Reply-To: <200703200900.l2K90wSD023540@tao.fdupont.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: mip6@ietf.org, Basavaraj Patil <basavaraj.patil@nokia.com>,
	ietf-ipsec-failover@vpnc.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>    Sorry, I don't have any knowledge of the IPsec failover activity you 
>    mentioned and how it would compete with HA-switch.  Can you point me at 
>    a draft?  I don't follow any IETF IPsec-related WGs at the moment.
>    
> => IMHO the easiest and fastest way is to go and/or read the agenda of
> the "ifare" BOF (tomorrow morning).

That's a long walk from my office in the US :)

Quoting text from VijayD on another list since it seems related:

"I am not sure how IFARE is related to this. IFARE does not address
transferring IPsec state. It is more explicitly moving a client to
another VPN gateway (load balancing, failover, etc..). So transferring
IPsec state is out of scope for IFARE also."

After reading the proposed charter that seems correct to me too.

>    It is true that there might have to be some API between the network 
>    stack and IKE, but it won't be necessary in all cases (and like Hui 
>    mentioned, isn't a MIPv6-specific requirement).  In the HA-reliability 
>    case, the MN will have an SA with every HA already, so won't need to 
>    tell IKE to do anything during a switch.
> 
> => can I translate this into it doesn't matter to keep unused IPsec SAs
> until they timeout?

Yes, in the ha-reliability case we might have unused SAs for all the 
backup HAs.

>    In the non-HA-reliability case  there will be more work for the MN to do.
>    
>    I'm also not sure that trying to switch to using a different 
>    infrastructure (IKE) will fit in the timeframe in which a switch 
>    mechanism is required.
>    
> => collaboration can help, no collaboration is likely a source of slow down.

If IFARE turns-into a WG and decides to work on HA IPsec failover that's 
great, it can specify a new protocol that supercedes HA-switch, but the 
HA-switch draft is pretty complete today.

>    >  - 4.1 Sending Home Agent Switch Messages "o A home  agent to mobile
>    >    node authentication option": this idle introduces a bidding down
>    >    security issue. I propose to say the authentication MUST use the
>    >    same mechanism than BU/BA (this is what we want and this should keep
>    >    everybody happy :-).
>    
>    This issue will be on the slide at the WG meeting for discussion, I 
>    suppose it would make it both easier to specify and implement, and would 
>    support any future BU/BA security mechanism.
>    
> => what do you think about my proposal?

I would support the change, but wanted to get the other author's and WG 
feedback.

>    >  - 5.1 Receiving Home Agent Switch Messages "o The packet MUST be
>    >    authenticated, either...": same issue (and same proposed solution).
>    > 
>    >  - 5.1 Receiving Home Agent Switch Messages: the presentation can suggest
>    >    the connection to a new HA has to be done after leaving the current one
>    >    (obviously this is not the intended behavior).
>    
>    There are two cases here:
>    
>    1. Switch is from current HA - in this case you would break-before-make 
>    and teardown the old binding before replacing with one at the new HA. 
>    If we don't do this then ND-proxy could fail with the new HA, along with 
>    the BU.
>    
> => IMHO this is not so clear:
>  - the current HA can be clever enough to avoid the ND-proxy issue because
>   it knows exactly what should happen.
>  - when you move to another home link there is not possible ND-proxy issue.
> So the problem is not a wording problem as I believed, perhaps we need
> an explicit "break-before-make is authorized" notification.

The other HA *should* be smart and not require the break, but we can't 
assume that's the case.  The only alternative right now (finding a new 
HA when yours isn't responding) behaves the same way, ha-switch is just 
a way to speed-up that process.  The ha-reliability soft switch mode is 
more desirable of course.

Thanks,

-Brian

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



From mip6-bounces@ietf.org Tue Mar 20 15:30:15 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTk0p-0005BX-Bk; Tue, 20 Mar 2007 15:28:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTk0m-00058b-Pd; Tue, 20 Mar 2007 15:28:48 -0400
Received: from mail.unilim.fr ([164.81.1.45] helo=smtp.unilim.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HTk0N-0006ll-0j; Tue, 20 Mar 2007 15:28:48 -0400
Received: from [192.168.0.2] ([84.4.81.39]) (authenticated bits=0)
	by smtp.unilim.fr (8.13.1/8.13.1) with ESMTP id l2KJS8k4015979
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 20 Mar 2007 20:28:09 +0100
Message-ID: <460035C8.9010706@xlim.fr>
Date: Tue, 20 Mar 2007 20:28:08 +0100
From: Damien Sauveron <damien.sauveron@xlim.fr>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: mip6@ietf.org, manet@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
X-Univ-Limoges-Greylist: Sender succeeded SMTP AUTH authentication, not
	delayed by milter-greylist-2.0.2 (smtp.unilim.fr [164.81.1.45]);
	Tue, 20 Mar 2007 20:28:09 +0100 (CET)
X-Univ-Limoges-MailScanner-Information: Serveur Anti-virus Please contact the
	SCI, Univ. of Limoges, for more information
X-Univ-Limoges-MailScanner: Found to be clean
X-Univ-Limoges-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (cached, score=-101.789, requis 6, autolearn=not spam,
	ALL_TRUSTED -1.80, BAYES_50 0.00, NO_RDNS2 0.01, SMTP_AUTH -100.00)
X-Univ-Limoges-MailScanner-Envelope-From: damien.sauveron@xlim.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.unilim.fr id
	l2KJS8k4015979
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: 
Subject: [Mip6] Extended Paper Submission Deadline: 5th April 2007 for the
 Third
 International Symposium on Information Assurance and Security (IAS'07)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

We apologise in advance if you have already received the following
announcement.

This is to announce that due to many requests, the IAS=9207 paper
submission deadline has now been extended to 5th April 2007.

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

Call for Papers (Extended Paper Submission Deadline: 5th April 2007)

The Third International Symposium on Information Assurance and Security
(IAS'07) http://www.ias07.org/

August 29-31, 2007, Manchester, United Kingdom

Proceedings published by IEEE CS press

Technically sponsored by ICST (http://www.icst.org/) and CREATE-NET
(http://www.create-net.it/)


Overview:
Information assurance and security has become an important research
issue in networked and distributed information sharing environments.
Finding effective ways to protect information systems, networks and
sensitive data within the critical information infrastructure is
challenging even with the most advanced technology and trained
professionals. The International Symposium on Information Assurance and
Security aims to bring together researchers, practitioners, developers,
and policy makers involved in multiple disciplines of information
security and assurance to exchange ideas and to learn the latest
development in this important field.


Topics:
Previously unpublished work offering novel research and application
contributions in any aspect of information assurance, security and
privacy are solicited for submission to the IAS=9207 symposium. Topics of
interest include, but are not limited to, the following:
- Agent and Mobile Code Security
- Anonymity and User Privacy
- Authentication and Identity Management
- Authorization and Access Control
- Biometrics Security and Applications
- Computer Forensics
- Cryptographic Protocols
- Data Integrity and Privacy
- Database Security
- Denial of Service and Intrusion Detection
- Distributed System Security
- E-Commerce and E-Government Security
- Fraud Control
- Information Warfare and Cyber-terrorism
- Intellectual Property Protection
- Internet and Web Services Security
- Key Management and Recovery
- New Ideas and Paradigms for Security
- Operating System Security
- Secure Hardware and Smartcards
- Secure Software Technologies
- Security Education and Training
- Security Management and Strategy
- Security Models and Architectures
- Security Verification, Evaluations and Measurements
- Trust Negotiation, Establishment and Management
- Ubiquitous Computing Security


Paper Submission:
Papers should be original and contain contributions of theoretical,
experimental or application nature, or be unique experience reports.
Papers must be submitted no later than April 5, 2007 and electronic
submission in PDF or Word is required. The page limit for a full-length
paper is 6 pages. Short papers describing novel research visions,
work-in-progress or less mature results are also welcome, with the limit
of 4 pages. All submissions should be in the IEEE 8.5" x 11" two-column
format. Papers should contain up to 5 keywords. Papers will be evaluated
for originality, significance, clarity, and soundness, and will be
reviewed by at least three independent reviewers. The IAS=9207 paper
submission system is available at:
http://www.ias07.org/paper_submission.php.


Conference Proceedings:
Accepted papers will be published by IEEE Computer Society Press.
Selected papers presented in the conference will be considered for
publication in a special issue of an international journal.


Best Paper Awards:
The IAS=9207 Program Committee will select one winner for the Best Paper
Award (all regular papers are eligible) and one winner for the Best
Student Paper Award (to be eligible, the student must be the sole author
of the paper, or the first author and primary contributor. A cover
letter to the General Chair/Program Chair must identify the paper as a
candidate for this competition at the time of submission). The award
winners will each be presented with an award certificate and a direct
payment of =A3200 at the conference, and an invitation to submit an
extended version of the award-winning paper for the consideration of
publication in an international journal, JIAS.


Key Deadlines:
Extended Paper Submission Deadline: April 5, 2007
Author Notification: May 10, 2007
Camera Ready Submission Deadline (6 pages): June 8, 2007
Author Registration Deadline: June 8, 2007

Panel/Tutorial Proposal Submission Deadline: April 20, 2007
Proposal Notification: May 10, 2007

Contacts:
Further enquiries regarding matters related to IAS=9207 can be sent to th=
e
Conference Local Organising Chairs:


Ms Bryony Quick; or
Mr Iain Hart;
Email: ias07@cs.man.ac.uk
Tel: +44 (0)161 275 6130
Fax: +44 (0)161 275 6204

--=20
Damien Sauveron


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



From mip6-bounces@ietf.org Tue Mar 20 20:26:57 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HToe4-0001jh-Rx; Tue, 20 Mar 2007 20:25:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HToe3-0001jZ-Az
	for mip6@ietf.org; Tue, 20 Mar 2007 20:25:39 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HToe1-0004yv-QZ
	for mip6@ietf.org; Tue, 20 Mar 2007 20:25:39 -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
	l2L0PQR5030595
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 20 Mar 2007 17:25:26 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l2L0PO54024031; Tue, 20 Mar 2007 17:25:25 -0700
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 17:25:24 -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] WG LC: draft-ietf-mip6-ha-switch-02.txt
Date: Tue, 20 Mar 2007 17:25:20 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513574F08@NAEX13.na.qualcomm.com>
In-Reply-To: <4600311A.4060402@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt
Thread-Index: AcdrJObs95bxzS+UTMOf91WNqaY9JQAKT7PQ
References: <200703200900.l2K90wSD023540@tao.fdupont.fr>
	<4600311A.4060402@hp.com>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Brian Haley" <brian.haley@hp.com>,
	"Francis Dupont" <Francis.Dupont@fdupont.fr>
X-OriginalArrivalTime: 21 Mar 2007 00:25:24.0966 (UTC)
	FILETIME=[6B459860:01C76B4F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: mip6@ietf.org, ietf-ipsec-failover@vpnc.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

So, it sounds like there is some confusion on what IFARE is proposing to
do. IFARE is very much related to failover and state transfer (even if
the client is only resuming a session with the same IPsec gateway) and
very much unrelated to load balancing.=20

Fundamentally, a failover solution must deal with state transfer. The
IFARE charter proposes dealing with both stateless and stateful modes of
operation - stateless mode implies state is stored in the client and
presented to the gateway upon session resumption; stateful mode implies
state is stored in the infrastructure.=20

The main motivation for IFARE stems from the MIP6 use case, although
there is nothing limiting the solution to that use case. If you are in
Prague, please do plan on attending the BoF tomorrow morning.=20

Thanks,
Vidya

> -----Original Message-----
> From: Brian Haley [mailto:brian.haley@hp.com]=20
> Sent: Tuesday, March 20, 2007 12:08 PM
> To: Francis Dupont
> Cc: mip6@ietf.org; Basavaraj Patil; ietf-ipsec-failover@vpnc.org
> Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt
>=20
> Francis Dupont wrote:
>=20
> >    Sorry, I don't have any knowledge of the IPsec failover=20
> activity you=20
> >    mentioned and how it would compete with HA-switch.  Can=20
> you point me at=20
> >    a draft?  I don't follow any IETF IPsec-related WGs at=20
> the moment.
> >   =20
> > =3D> IMHO the easiest and fastest way is to go and/or read=20
> the agenda of=20
> > the "ifare" BOF (tomorrow morning).
>=20
> That's a long walk from my office in the US :)
>=20
> Quoting text from VijayD on another list since it seems related:
>=20
> "I am not sure how IFARE is related to this. IFARE does not=20
> address transferring IPsec state. It is more explicitly=20
> moving a client to another VPN gateway (load balancing,=20
> failover, etc..). So transferring IPsec state is out of scope=20
> for IFARE also."
>=20
> After reading the proposed charter that seems correct to me too.
>=20
> >    It is true that there might have to be some API between=20
> the network=20
> >    stack and IKE, but it won't be necessary in all cases=20
> (and like Hui=20
> >    mentioned, isn't a MIPv6-specific requirement).  In the=20
> HA-reliability=20
> >    case, the MN will have an SA with every HA already, so=20
> won't need to=20
> >    tell IKE to do anything during a switch.
> >=20
> > =3D> can I translate this into it doesn't matter to keep unused =
IPsec=20
> > SAs until they timeout?
>=20
> Yes, in the ha-reliability case we might have unused SAs for=20
> all the backup HAs.
>=20
> >    In the non-HA-reliability case  there will be more work=20
> for the MN to do.
> >   =20
> >    I'm also not sure that trying to switch to using a different=20
> >    infrastructure (IKE) will fit in the timeframe in which a switch=20
> >    mechanism is required.
> >   =20
> > =3D> collaboration can help, no collaboration is likely a=20
> source of slow down.
>=20
> If IFARE turns-into a WG and decides to work on HA IPsec=20
> failover that's great, it can specify a new protocol that=20
> supercedes HA-switch, but the HA-switch draft is pretty=20
> complete today.
>=20
> >    >  - 4.1 Sending Home Agent Switch Messages "o A home =20
> agent to mobile
> >    >    node authentication option": this idle introduces a=20
> bidding down
> >    >    security issue. I propose to say the authentication=20
> MUST use the
> >    >    same mechanism than BU/BA (this is what we want and=20
> this should keep
> >    >    everybody happy :-).
> >   =20
> >    This issue will be on the slide at the WG meeting for=20
> discussion, I=20
> >    suppose it would make it both easier to specify and=20
> implement, and would=20
> >    support any future BU/BA security mechanism.
> >   =20
> > =3D> what do you think about my proposal?
>=20
> I would support the change, but wanted to get the other=20
> author's and WG feedback.
>=20
> >    >  - 5.1 Receiving Home Agent Switch Messages "o The=20
> packet MUST be
> >    >    authenticated, either...": same issue (and same=20
> proposed solution).
> >    >=20
> >    >  - 5.1 Receiving Home Agent Switch Messages: the=20
> presentation can suggest
> >    >    the connection to a new HA has to be done after=20
> leaving the current one
> >    >    (obviously this is not the intended behavior).
> >   =20
> >    There are two cases here:
> >   =20
> >    1. Switch is from current HA - in this case you would=20
> break-before-make=20
> >    and teardown the old binding before replacing with one=20
> at the new HA.=20
> >    If we don't do this then ND-proxy could fail with the=20
> new HA, along with=20
> >    the BU.
> >   =20
> > =3D> IMHO this is not so clear:
> >  - the current HA can be clever enough to avoid the=20
> ND-proxy issue because
> >   it knows exactly what should happen.
> >  - when you move to another home link there is not possible=20
> ND-proxy issue.
> > So the problem is not a wording problem as I believed,=20
> perhaps we need=20
> > an explicit "break-before-make is authorized" notification.
>=20
> The other HA *should* be smart and not require the break, but=20
> we can't assume that's the case.  The only alternative right=20
> now (finding a new HA when yours isn't responding) behaves=20
> the same way, ha-switch is just a way to speed-up that=20
> process.  The ha-reliability soft switch mode is more=20
> desirable of course.
>=20
> Thanks,
>=20
> -Brian
>=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 Mar 21 04:14:26 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTvx1-0006fo-Lk; Wed, 21 Mar 2007 04:13:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTvwz-0006fY-Qo
	for mip6@ietf.org; Wed, 21 Mar 2007 04:13:41 -0400
Received: from sehan001bb.han.telia.se ([131.115.18.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTvwp-0006DS-JU
	for mip6@ietf.org; Wed, 21 Mar 2007 04:13:41 -0400
Received: from SEHAN021MB.tcad.telia.se ([131.115.18.160]) by
	sehan001bb.han.telia.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Mar 2007 09:13:28 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 21 Mar 2007 09:13:27 +0100
Message-ID: <59D7431DE2527D4CB0F1EFEDA5683ED301A4016C@SEHAN021MB.tcad.telia.se>
In-Reply-To: <4600130A.60204@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Thread-Index: AcdrEczDsCdeZN9KTzup70v0M9TkdwAfYP7Q
From: <jouni.korhonen@teliasonera.com>
To: <vijay.devarapalli@azairenet.com>,
	<tracker-mip6@mip4.org>
X-OriginalArrivalTime: 21 Mar 2007 08:13:28.0412 (UTC)
	FILETIME=[CE4F61C0:01C76B90]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
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

Vijay,=20

[snip]

> If I remember right, this was among the first few issues that=20
> were discussed in the design team. Some folks did suggest=20
> turning on UDP all the time when the access network is IPv4.
> But this is an overhead in case there is no NAT. Thats why we=20
> have a NAT detection mechanism in the DS-MIPv6. UDP=20
> encapsulation is turned on only if a NAT is detected. My=20
> preference is to still go with this.

Honestly, based on our small MIP deployment experiments & experience
the NAT traversal has been kind of secondary (but a good additional)
feature. The greatest value of UDP encapsulation has been the firewall
traversal.

Cheers,
	Jouni

> > Isn't it possible to fix the encapsulation format to one of=20
> these mechanisms described in the draft?
>=20
> If we are to pick only one encapsulation format, we clearly=20
> can't pick "IPv4 encap format" (as you called it) because it=20
> may not work through a NAT. It has to be UDP encapsulation always.
>=20
> Vijay
>=20
> >=20
> > ----------
> > category: Technical
> > draft: draft-ietf-mip6-nemo-v4traversal
> > messages: 338
> > nosy: keiichi
> > priority: May fix
> > status: No discussion
> > title: fixing encapsulation mechanism in IPv4 network
> >=20
> > _________________________________________________
> > Mip6 issue tracker <tracker-mip6@mip4.org>=20
> > <http://www.mip4.org/issues/tracker/mip6/issue94>
> > _________________________________________________
> >=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 Wed Mar 21 05:21:20 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTwzb-0005Bw-Nm; Wed, 21 Mar 2007 05:20:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTwza-0005Ax-9G
	for mip6@ietf.org; Wed, 21 Mar 2007 05:20:26 -0400
Received: from tao.fdupont.fr ([82.236.136.93])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTwzY-0007Hy-N1
	for mip6@ietf.org; Wed, 21 Mar 2007 05:20:26 -0400
Received: from tao.fdupont.fr (localhost [127.0.0.1])
	by tao.fdupont.fr (8.13.5/8.13.5) with ESMTP id l2L9KGV4026970;
	Wed, 21 Mar 2007 10:20:18 +0100 (CET)
Received: from tao.fdupont.fr (dupont@localhost)
	by tao.fdupont.fr (8.13.5/8.13.5/Submit) with ESMTP id l2L9KFBL026966; 
	Wed, 21 Mar 2007 10:20:15 +0100 (CET)
Message-Id: <200703210920.l2L9KFBL026966@tao.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] WG LC: draft-ietf-mip6-ha-switch-02.txt 
In-reply-to: Your message of Tue, 20 Mar 2007 15:08:10 -0400.
	<4600311A.4060402@hp.com> 
Date: Wed, 21 Mar 2007 10:20:14 +0100
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: mip6@ietf.org, Basavaraj Patil <basavaraj.patil@nokia.com>,
	ietf-ipsec-failover@vpnc.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => IMHO the easiest and fastest way is to go and/or read the agenda of
   > the "ifare" BOF (tomorrow morning).
   
   That's a long walk from my office in the US :)
   
=> this is why I added "read the agenda..." (:-).

   Quoting text from VijayD on another list since it seems related:
   
   "I am not sure how IFARE is related to this. IFARE does not address
   transferring IPsec state. It is more explicitly moving a client to
   another VPN gateway (load balancing, failover, etc..). So transferring
   IPsec state is out of scope for IFARE also."
   
   After reading the proposed charter that seems correct to me too.
   
=> I don't know what is exactly "transferring IPsec state" but low
latency failover (something is the slide in the screen now at ifare
session) should include something at least close...

   > => collaboration can help, no collaboration is likely a source of
   > slow down.
   
   If IFARE turns-into a WG and decides to work on HA IPsec failover that's 
   great, it can specify a new protocol that supercedes HA-switch, but the 
   HA-switch draft is pretty complete today.
   
=> I believe that nobody wants two competitive protocols doing the same
thing... BTW I checked at the beginning of the session whether such
collaboration was in the agenda and the answer was yes (BTW I specified
the mobile IP cloud because of the proposed merge of mip6/nemo/monami6).

   > => IMHO this is not so clear:
   >  - the current HA can be clever enough to avoid the ND-proxy issue because
   >   it knows exactly what should happen.
   >  - when you move to another home link there is not possible ND-proxy issue.
   > So the problem is not a wording problem as I believed, perhaps we need
   > an explicit "break-before-make is authorized" notification.
   
   The other HA *should* be smart and not require the break, but we can't 
   assume that's the case.

=> but the current HA has a better knowledge of the context so IMHO
we should use it to control the way the switch could be done when
some ways can raise issues.

   The only alternative right now (finding a new 
   HA when yours isn't responding) behaves the same way, ha-switch is just 
   a way to speed-up that process.

=> in fact I don't believe it is true because the client doesn't know if
things were broken for the HA... So you can have a HA only working for
the ND-proxy part and messing the DAD from the other HA! Of course
this is not really related to the HA-switch protocol (i.e., there is
nothing we can do so nothing to put in the document).

   The ha-reliability soft switch mode is more desirable of course.
   
=> yes but the world is not (yet :-) perfect.

Thanks

Francis.Dupont@fdupont.fr

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



From mip6-bounces@ietf.org Wed Mar 21 06:14:49 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTxoy-0004np-TS; Wed, 21 Mar 2007 06:13:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTxox-0004ne-8M
	for mip6@ietf.org; Wed, 21 Mar 2007 06:13:31 -0400
Received: from otm-mgo00.iij.ad.jp ([210.138.20.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTxot-0008RD-Ik
	for mip6@ietf.org; Wed, 21 Mar 2007 06:13:31 -0400
Received: OTM-MO(otm-mgo00) id l2LADC0s088377;
	Wed, 21 Mar 2007 19:13:12 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2LADCNa020873;
	Wed, 21 Mar 2007 19:13:12 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2LACIEw084300
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 21 Mar 2007 19:12:24 +0900 (JST)
In-Reply-To: <4600130A.60204@azairenet.com>
References: <1174404560.07.0.659815063549.issue94@mip4.org>
	<4600130A.60204@azairenet.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <8CD6B032-BF47-4672-AC2E-7A40152DFF03@iijlab.net>
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 21 Mar 2007 19:12:57 +0900
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: Mip6 issue tracker <tracker-mip6@mip4.org>, mip6@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0062317052=="
Errors-To: mip6-bounces@ietf.org


--===============0062317052==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-13-743768957;
	protocol="application/pkcs7-signature"


--Apple-Mail-13-743768957
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello,

On 2007/03/21, at 1:59, Vijay Devarapalli wrote:

> Keiichi SHIMA wrote:
>> New submission from Keiichi SHIMA <keiichi@iijlab.net>:
>> The current DSMIPv6 draft specifies two encapsulation formats, one  
>> is the IPv4 encap format, the other is UDPv4 encap format.  The  
>> default encapsulation format is the IPv4 format, and if the HA  
>> explicitly specifies to change the encapsulation format to the  
>> UDPv4 format if there is a NAT box between the HA and the MN.   
>> Because of this specification, HA and MN have to support both  
>> encapsulation formats and have to change the format dynamically,  
>> that may increase the hurdle for implementors and may cause  
>> complexity in interoperability.
>
> If I remember right, this was among the first few issues that
> were discussed in the design team. Some folks did suggest
> turning on UDP all the time when the access network is IPv4.
> But this is an overhead in case there is no NAT. Thats why
> we have a NAT detection mechanism in the DS-MIPv6. UDP
> encapsulation is turned on only if a NAT is detected. My
> preference is to still go with this.

I agree that using UDP has an overhead compared to a simple IP  
encapsulation format.

My question came from the idea that 'which is the major environments  
for IPv4?  A NATed environment or a global IPv4 environment?'  If  
most of the IPv4 networks that the mobile terminals connect to is  
NATed networks, then simply using UDP seems better to me.

But my perspective may be wrong.  I want to hear some more opinions  
from who are interested in DSMIPv6 operation.

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




--Apple-Mail-13-743768957
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKbjCCBF8w
ggJHoAMCAQICAhIQMA0GCSqGSIb3DQEBBQUAMEUxCzAJBgNVBAYTAkpQMRUwEwYDVQQKEwxXSURF
IFByb2plY3QxHzAdBgNVBAMTFm1lbWJlcnMgb3JpZW50ZWQgQ0EgMDIwHhcNMDYwNjEyMDQ1NTA5
WhcNMDcwNjMwMjM1OTU5WjBkMQswCQYDVQQGFAJKUDEVMBMGA1UEChQMV0lERSBQcm9qZWN0MRsw
GQYDVQQDFBIwMzI4IEtlaWljaGkgU2hpbWExITAfBgkqhkiG9w0BCQEUEmtlaWljaGlAaWlqbGFi
Lm5ldDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAu6pTSPQTKzeSygFymRWYipFcZRaePRSU
nruo6RtpQuNgDyUKvaMOa1KuNWRPYHp28hoWYe0YBrGj5SdHH2A3wbJ2zP5cXQFgMJMxJXhcWuSu
+Foo7n9T1+yFjuc37Us9N4LoXZaM3krFqBHz2XSUCSigzTstdkIXWPwxDg+db4MCAwEAAaOBvTCB
ujAOBgNVHQ8BAQAEBAMCBLAwIAYDVR0RAQEABBYwFIESa2VpaWNoaUBpaWpsYWIubmV0MDYGA1Ud
HwEBAAQsMCowKKAmoCSGImh0dHA6Ly93d3cubW9jYS53aWRlLmFkLmpwL2NybC5jcmwwIgYDVR0j
AQEABBgwFoAUOM7FCTrTDVTyVXHmSMda90Tf6bowKgYDVR0lAQEABCAwHgYIKwYBBQUHAwQGCCsG
AQUFBwMDBggrBgEFBQcDAjANBgkqhkiG9w0BAQUFAAOCAgEAlB3DdeJJZ1gJh4sszEgoUg9DIHRG
eaotuAi5FfGkd+KmzEARKYvgfh1A8AVAoHISFvavv0OD9w9dmzGyAmNUTBUsSMeH/5XiLuWJPbjU
3bVK467oyDEFaA+XFJurRY6RuPb4afHoi+aCHtY/pmcGCCSQPKnOuN8BviNLp/haDQyPVVwA+9it
s7PwUArSkPnkBo1GXk4FSFDkijbw6zzJkXePBLHkE3QcFBYIo0woy6P2NFFYz8nPmd8M8qyT0Yh8
A9g0UVxvcWk4gUaJP0AeZ8/raNCr7eXBMByhDx5FSvparc21zEmQ5MnCVduDuM9eM8Qc8zFqzTzg
mmZza69jiiq98kL1yFqjfL4+Nu7+N9D8Q/NuaIYLd9E++s20X9Kb7dW1xqMS1E30I8ZZnIwu2Fox
ZRziQnKHkatDFBI+zuNY3+nIcE8bvzm/Y36xwk2GhN8p707CsT5i17ZCzkvriCdkE13riXNhXDOe
qGR6Kj1aZLLBxHeLvFUa72q65+ShesszO6lOxf66auFbXYsOfzIUhG3z5YmM6Lk5NtJom6F7Drob
jPjyDv2zZoGNGdIqbDbOaFkmBEYchuToVMNzYk6v6d+v4A/MrnGlexgQbzfgC0Ld32NwPlDDGFnO
LPjaEZ19bFK65rWjWwEyLsO15GD7jotBrDU5yngkhu15RKowggYHMIID76ADAgECAgIJFjANBgkq
hkiG9w0BAQUFADA+MQswCQYDVQQGEwJKUDEVMBMGA1UEChMMV0lERSBQcm9qZWN0MRgwFgYDVQQD
Ew9XSURFIFJPT1QgQ0EgMDIwHhcNMDYwNTE4MTMzNTM2WhcNMTYwNjMwMjM1OTU5WjBFMQswCQYD
VQQGEwJKUDEVMBMGA1UEChMMV0lERSBQcm9qZWN0MR8wHQYDVQQDExZtZW1iZXJzIG9yaWVudGVk
IENBIDAyMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA4BYQZ8z3YdyJUt0ZbDh0+rVf
fpf/Aw2J2GKNLy4fMIGpEhjS+OhAPC9TUH6rNVV2AR6myr94stzWhGY++bZjd7/oYYRLa+tCtUKa
Om49ibS8CHSqfeR/Yb0YHKTrHCaAu2PUw6kENGZ3bDCiMbuDPkPLVkYuN3rSRp3qHd1XJ8DZ2bTX
DbW3cwVqHFxKjVf6mdBInlL8pMs9z4T9GNpcqQO1i7Uk467KLZYbi1W1d5m23Jodr/7/y08bc078
ppWE3dP9eNEysmRxdIvKMgTHfTjtYN3ZhnfUEsYoJ6W9flc9Qoe+5UqdBt+O5ruJM3m1viWf+Rs8
xvvs9ZnodrqaxAIDwgmgpHePLCV2Qc/Fix3vkLY2Rt9KXeRCjLOzgdCYhtuJI42hY/l9dJjrRRK/
Qo5jABzbRRJzCavDlqS25q1OXenrO64nU+7T92PfFeOv1ORg5PcCSoY0dIzN9lcL51yb2PLn3cUx
ya4itIYV9MHFXaIDM4inLLmBUR/0xD4Q+Ju1Zqd5n+uK5lCrQ48+kMPKbrDyrDyvqHYTo8XRuyAU
Z1F56NJFv6umd+/m0ADC1M7Q9HNXwt8dRZyvVgH8l4teYu9We32NtZ7H8dyNaa34R2zs1bP2ftDT
Au//Bi/3u47JTSJ6M1zE6lsc7OwP6c32okaCRCwayxVYi+FgNdUCAwEAAaOCAQYwggECMA8GA1Ud
EwEB/wQFMAMBAf8wDgYDVR0PAQEABAQDAgH+MFsGA1UdIAEBAARRME8wTQYJKoMIjJwYAQECMEAw
PgYIKwYBBQUHAgEWMmh0dHA6Ly9tb2NhLndpZGUuYWQuanAvbW9jYV9ndWlkZS9tb2NhX3BvbGlj
eS5odG1sMDwGA1UdHwEBAAQyMDAwLqAsoCqGKGh0dHA6Ly93d3cud2lkZS5hZC5qcC9jYS93aWRl
cm9vdGNybC5jcmwwIAYDVR0OAQEABBYEFDjOxQk60w1U8lVx5kjHWvdE3+m6MCIGA1UdIwEBAAQY
MBaAFAzMoku5z7HsuNTr5KwJl0+xojExMA0GCSqGSIb3DQEBBQUAA4ICAQAKZpGub2X1UG9aXuAS
P1MsRJtlgcataxapi6Lbox+8/5nrLXA6M5+FSD/3wjO96KEdv+KGK4WIE6AAsGKdH0dFE8jgzGVw
uyoyXZg+UWhFrCMB3lbNfY9UsTBJfVx1TlMC1BXaT5qKCgp2N5dF6s2yeNa1kgGvR+xDkxNGDf6q
3xcN3QiC9ofyUyeRaZEacTjUp7bo4VREFtv3txyocbT6B961inhUS3PZNx6nIzJqiZA2CX/QGrlg
7uE1EoXgSJ+N77MdasX5Tl69Cb+fJCAdlbji1LAgWLEPXM0kHyYnfsLHfEXo4bCRdpN+GpPvqyhW
DOk8ZEmrzYglsK38KIIG4Mp0tUoj25nzXhHnkNt0OCLSvzPcTopabRaPl4MnvQQ1tGsKbSafUBR5
gzdjA/f/o9bQKYwZC+fP8Gu50Ib4sYc5BbXEZdUx0Pjc/1nbIuM0t1YFrfLOiWP+Ar0x/WuPrtLZ
gUyRnVBVyHm73be8T9wfE31aJw9E+2a92cjrp0lyCfWoCKjHGxdsPFvPIg1gKVG/IlgKeKEnKu1N
O4PmD//LW/7p6A5V/W1vGZn8jI9ErwVz2cMiyJJfRVaviV5TcC58vrREH6qB9LfJwA7jy4CRu1oP
GsaQRg5ZTMaV1JZ5cFBNHKcJiSDPTqVdKPkjmSUVUlYvEN+08pPGK/4KcTGCAgwwggIIAgEBMEsw
RTELMAkGA1UEBhMCSlAxFTATBgNVBAoTDFdJREUgUHJvamVjdDEfMB0GA1UEAxMWbWVtYmVycyBv
cmllbnRlZCBDQSAwMgICEhAwCQYFKw4DAhoFAKCCARcwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMDcwMzIxMTAxMjU3WjAjBgkqhkiG9w0BCQQxFgQUlR0kQHZ9Nmb7
vwSVNCQswD0hkS0wWgYJKwYBBAGCNxAEMU0wSzBFMQswCQYDVQQGEwJKUDEVMBMGA1UEChMMV0lE
RSBQcm9qZWN0MR8wHQYDVQQDExZtZW1iZXJzIG9yaWVudGVkIENBIDAyAgISEDBcBgsqhkiG9w0B
CRACCzFNoEswRTELMAkGA1UEBhMCSlAxFTATBgNVBAoTDFdJREUgUHJvamVjdDEfMB0GA1UEAxMW
bWVtYmVycyBvcmllbnRlZCBDQSAwMgICEhAwDQYJKoZIhvcNAQEBBQAEgYAgTGpK4VG5r9Bg+B4t
YdCVXc3R3fn5angEB3I1ejoIu3L2htgnc2R6y3gcSs8V0Je8XOdj3jg00DI8Ux//ZVUPBJNImIbO
TXs36yrM4q83Bhvp+4atxBm1BT6nBZ0YueqDHdSF2gUxFHtiAJhm885vUVi8iSssfwLdVwiMh55v
AwAAAAAAAA==

--Apple-Mail-13-743768957--


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

--===============0062317052==--




From mip6-bounces@ietf.org Wed Mar 21 06:21:25 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTxwI-000648-MX; Wed, 21 Mar 2007 06:21:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTxwG-00063A-Md
	for mip6@ietf.org; Wed, 21 Mar 2007 06:21:05 -0400
Received: from otm-mgo00.iij.ad.jp ([210.138.20.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTxwE-0002PT-2G
	for mip6@ietf.org; Wed, 21 Mar 2007 06:21:04 -0400
Received: OTM-MO(otm-mgo00) id l2LAKwOk088537;
	Wed, 21 Mar 2007 19:20:58 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2LAKwQY021499;
	Wed, 21 Mar 2007 19:20:58 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2LAK1Mx084327
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 21 Mar 2007 19:20:09 +0900 (JST)
In-Reply-To: <E1HTi6L-0007do-DQ@megatron.ietf.org>
References: <E1HTi6L-0007do-DQ@megatron.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <623CC63B-6E30-45B5-AA1D-8947EAD698C6@iijlab.net>
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 21 Mar 2007 19:20:46 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, mip6@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0217075337=="
Errors-To: mip6-bounces@ietf.org


--===============0217075337==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-14-744234220;
	protocol="application/pkcs7-signature"


--Apple-Mail-14-744234220
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello,

On 2007/03/21, at 2:25, Hesham Soliman wrote:

> We will have a formal concensus call on this but let's here a few  
> opinions
> first. My opinion below:

OK, thanks.


>> New submission from Keiichi SHIMA <keiichi@iijlab.net>:
>>
>> The current DSMIPv6 draft specifies two encapsulation
>> formats, one is the IPv4 encap format, the other is
>> UDPv4 encap format.  The default encapsulation format is the
>> IPv4 format, and if the HA explicitly
>> specifies to change the encapsulation format to the UDPv4
>> format if there is a NAT box between the HA
>> and the MN.  Because of this specification, HA and MN have
>> to support both encapsulation formats and
>> have to change the format dynamically, that may increase the
>> hurdle for implementors and may cause
>> complexity in interoperability.
>>
>> Isn't it possible to fix the encapsulation format to one of
>> these mechanisms described in the draft?
>
> => So basically you're asking for UDP-only tunnelling. As I  
> mentioned in a
> previous email, this a tradeoff between reducing the implementer's  
> work and
> reducing redundant bits on the wire. I think it makes more sense to  
> reduce
> additional bits on the wire. The UDP tunnel is redundant if no NAT  
> were
> detected. So your suggestion amounts to removing NAT detection and  
> always
> using UDP tunnels. I think this is inefficient, especially when the  
> cost of

About the possibility of using the UDP encap mechanism, please refer  
my mail replied to Vijay's mail.


> switching between the UDP tunnel and IP n IP is very small (from an
> implementation point of view).

I may not agree on the above point.  Since UDP is a transport  
protocol, encapsulating something in it cannot be handled by a  
*normal* packet decapsulation flow, while IPv4-in-IPv4 can be fit to  
the natural flow.  So switching from IPv4 encapsulation to UDP  
encapsulation may not be so easy as you say, especially for MIP  
stacks that are implemented in user space.

I would like to hear opinions from who have already implemented DSMIPv4.

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




--Apple-Mail-14-744234220
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKbjCCBF8w
ggJHoAMCAQICAhIQMA0GCSqGSIb3DQEBBQUAMEUxCzAJBgNVBAYTAkpQMRUwEwYDVQQKEwxXSURF
IFByb2plY3QxHzAdBgNVBAMTFm1lbWJlcnMgb3JpZW50ZWQgQ0EgMDIwHhcNMDYwNjEyMDQ1NTA5
WhcNMDcwNjMwMjM1OTU5WjBkMQswCQYDVQQGFAJKUDEVMBMGA1UEChQMV0lERSBQcm9qZWN0MRsw
GQYDVQQDFBIwMzI4IEtlaWljaGkgU2hpbWExITAfBgkqhkiG9w0BCQEUEmtlaWljaGlAaWlqbGFi
Lm5ldDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAu6pTSPQTKzeSygFymRWYipFcZRaePRSU
nruo6RtpQuNgDyUKvaMOa1KuNWRPYHp28hoWYe0YBrGj5SdHH2A3wbJ2zP5cXQFgMJMxJXhcWuSu
+Foo7n9T1+yFjuc37Us9N4LoXZaM3krFqBHz2XSUCSigzTstdkIXWPwxDg+db4MCAwEAAaOBvTCB
ujAOBgNVHQ8BAQAEBAMCBLAwIAYDVR0RAQEABBYwFIESa2VpaWNoaUBpaWpsYWIubmV0MDYGA1Ud
HwEBAAQsMCowKKAmoCSGImh0dHA6Ly93d3cubW9jYS53aWRlLmFkLmpwL2NybC5jcmwwIgYDVR0j
AQEABBgwFoAUOM7FCTrTDVTyVXHmSMda90Tf6bowKgYDVR0lAQEABCAwHgYIKwYBBQUHAwQGCCsG
AQUFBwMDBggrBgEFBQcDAjANBgkqhkiG9w0BAQUFAAOCAgEAlB3DdeJJZ1gJh4sszEgoUg9DIHRG
eaotuAi5FfGkd+KmzEARKYvgfh1A8AVAoHISFvavv0OD9w9dmzGyAmNUTBUsSMeH/5XiLuWJPbjU
3bVK467oyDEFaA+XFJurRY6RuPb4afHoi+aCHtY/pmcGCCSQPKnOuN8BviNLp/haDQyPVVwA+9it
s7PwUArSkPnkBo1GXk4FSFDkijbw6zzJkXePBLHkE3QcFBYIo0woy6P2NFFYz8nPmd8M8qyT0Yh8
A9g0UVxvcWk4gUaJP0AeZ8/raNCr7eXBMByhDx5FSvparc21zEmQ5MnCVduDuM9eM8Qc8zFqzTzg
mmZza69jiiq98kL1yFqjfL4+Nu7+N9D8Q/NuaIYLd9E++s20X9Kb7dW1xqMS1E30I8ZZnIwu2Fox
ZRziQnKHkatDFBI+zuNY3+nIcE8bvzm/Y36xwk2GhN8p707CsT5i17ZCzkvriCdkE13riXNhXDOe
qGR6Kj1aZLLBxHeLvFUa72q65+ShesszO6lOxf66auFbXYsOfzIUhG3z5YmM6Lk5NtJom6F7Drob
jPjyDv2zZoGNGdIqbDbOaFkmBEYchuToVMNzYk6v6d+v4A/MrnGlexgQbzfgC0Ld32NwPlDDGFnO
LPjaEZ19bFK65rWjWwEyLsO15GD7jotBrDU5yngkhu15RKowggYHMIID76ADAgECAgIJFjANBgkq
hkiG9w0BAQUFADA+MQswCQYDVQQGEwJKUDEVMBMGA1UEChMMV0lERSBQcm9qZWN0MRgwFgYDVQQD
Ew9XSURFIFJPT1QgQ0EgMDIwHhcNMDYwNTE4MTMzNTM2WhcNMTYwNjMwMjM1OTU5WjBFMQswCQYD
VQQGEwJKUDEVMBMGA1UEChMMV0lERSBQcm9qZWN0MR8wHQYDVQQDExZtZW1iZXJzIG9yaWVudGVk
IENBIDAyMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA4BYQZ8z3YdyJUt0ZbDh0+rVf
fpf/Aw2J2GKNLy4fMIGpEhjS+OhAPC9TUH6rNVV2AR6myr94stzWhGY++bZjd7/oYYRLa+tCtUKa
Om49ibS8CHSqfeR/Yb0YHKTrHCaAu2PUw6kENGZ3bDCiMbuDPkPLVkYuN3rSRp3qHd1XJ8DZ2bTX
DbW3cwVqHFxKjVf6mdBInlL8pMs9z4T9GNpcqQO1i7Uk467KLZYbi1W1d5m23Jodr/7/y08bc078
ppWE3dP9eNEysmRxdIvKMgTHfTjtYN3ZhnfUEsYoJ6W9flc9Qoe+5UqdBt+O5ruJM3m1viWf+Rs8
xvvs9ZnodrqaxAIDwgmgpHePLCV2Qc/Fix3vkLY2Rt9KXeRCjLOzgdCYhtuJI42hY/l9dJjrRRK/
Qo5jABzbRRJzCavDlqS25q1OXenrO64nU+7T92PfFeOv1ORg5PcCSoY0dIzN9lcL51yb2PLn3cUx
ya4itIYV9MHFXaIDM4inLLmBUR/0xD4Q+Ju1Zqd5n+uK5lCrQ48+kMPKbrDyrDyvqHYTo8XRuyAU
Z1F56NJFv6umd+/m0ADC1M7Q9HNXwt8dRZyvVgH8l4teYu9We32NtZ7H8dyNaa34R2zs1bP2ftDT
Au//Bi/3u47JTSJ6M1zE6lsc7OwP6c32okaCRCwayxVYi+FgNdUCAwEAAaOCAQYwggECMA8GA1Ud
EwEB/wQFMAMBAf8wDgYDVR0PAQEABAQDAgH+MFsGA1UdIAEBAARRME8wTQYJKoMIjJwYAQECMEAw
PgYIKwYBBQUHAgEWMmh0dHA6Ly9tb2NhLndpZGUuYWQuanAvbW9jYV9ndWlkZS9tb2NhX3BvbGlj
eS5odG1sMDwGA1UdHwEBAAQyMDAwLqAsoCqGKGh0dHA6Ly93d3cud2lkZS5hZC5qcC9jYS93aWRl
cm9vdGNybC5jcmwwIAYDVR0OAQEABBYEFDjOxQk60w1U8lVx5kjHWvdE3+m6MCIGA1UdIwEBAAQY
MBaAFAzMoku5z7HsuNTr5KwJl0+xojExMA0GCSqGSIb3DQEBBQUAA4ICAQAKZpGub2X1UG9aXuAS
P1MsRJtlgcataxapi6Lbox+8/5nrLXA6M5+FSD/3wjO96KEdv+KGK4WIE6AAsGKdH0dFE8jgzGVw
uyoyXZg+UWhFrCMB3lbNfY9UsTBJfVx1TlMC1BXaT5qKCgp2N5dF6s2yeNa1kgGvR+xDkxNGDf6q
3xcN3QiC9ofyUyeRaZEacTjUp7bo4VREFtv3txyocbT6B961inhUS3PZNx6nIzJqiZA2CX/QGrlg
7uE1EoXgSJ+N77MdasX5Tl69Cb+fJCAdlbji1LAgWLEPXM0kHyYnfsLHfEXo4bCRdpN+GpPvqyhW
DOk8ZEmrzYglsK38KIIG4Mp0tUoj25nzXhHnkNt0OCLSvzPcTopabRaPl4MnvQQ1tGsKbSafUBR5
gzdjA/f/o9bQKYwZC+fP8Gu50Ib4sYc5BbXEZdUx0Pjc/1nbIuM0t1YFrfLOiWP+Ar0x/WuPrtLZ
gUyRnVBVyHm73be8T9wfE31aJw9E+2a92cjrp0lyCfWoCKjHGxdsPFvPIg1gKVG/IlgKeKEnKu1N
O4PmD//LW/7p6A5V/W1vGZn8jI9ErwVz2cMiyJJfRVaviV5TcC58vrREH6qB9LfJwA7jy4CRu1oP
GsaQRg5ZTMaV1JZ5cFBNHKcJiSDPTqVdKPkjmSUVUlYvEN+08pPGK/4KcTGCAgwwggIIAgEBMEsw
RTELMAkGA1UEBhMCSlAxFTATBgNVBAoTDFdJREUgUHJvamVjdDEfMB0GA1UEAxMWbWVtYmVycyBv
cmllbnRlZCBDQSAwMgICEhAwCQYFKw4DAhoFAKCCARcwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMDcwMzIxMTAyMDQ2WjAjBgkqhkiG9w0BCQQxFgQUNBeitjQ13zcu
JE9D+MkakXzLb7wwWgYJKwYBBAGCNxAEMU0wSzBFMQswCQYDVQQGEwJKUDEVMBMGA1UEChMMV0lE
RSBQcm9qZWN0MR8wHQYDVQQDExZtZW1iZXJzIG9yaWVudGVkIENBIDAyAgISEDBcBgsqhkiG9w0B
CRACCzFNoEswRTELMAkGA1UEBhMCSlAxFTATBgNVBAoTDFdJREUgUHJvamVjdDEfMB0GA1UEAxMW
bWVtYmVycyBvcmllbnRlZCBDQSAwMgICEhAwDQYJKoZIhvcNAQEBBQAEgYCgYm/fMSLrJJ3QinA9
WX3Aj5Wbs0u4L7xH41X6bn8GXpLfvPPTMUCV3dF4uxaW1uep1IGhT/KjhPTTlJk7d+rsXwadviRd
DIIE8fSTPvOnnmGMHWooE5i3Uk93ozs1OtZPxkvahUJ0zQGAvhW+hX1BPay30K2NUz+uiNpgWkrs
dQAAAAAAAA==

--Apple-Mail-14-744234220--


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

--===============0217075337==--




From mip6-bounces@ietf.org Wed Mar 21 06:41:39 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTyFT-0005Hb-Vw; Wed, 21 Mar 2007 06:40:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTyFS-0005HN-Ik
	for mip6@ietf.org; Wed, 21 Mar 2007 06:40:54 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTyFP-0000GY-DK
	for mip6@ietf.org; Wed, 21 Mar 2007 06:40:54 -0400
Received: from [130.129.64.9] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HTyFB-0000HD-4A; Wed, 21 Mar 2007 21:40:37 +1100
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>
Subject: RE: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 21 Mar 2007 21:40:16 +1100
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: <623CC63B-6E30-45B5-AA1D-8947EAD698C6@iijlab.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acdroyga7pFUyTl/Q5CBCKvFyI+SgQAAHmBQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, 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
Message-Id: <E1HTyFT-0005Hb-Vw@megatron.ietf.org>


 > > switching between the UDP tunnel and IP n IP is very small (from an
 > > implementation point of view).
 > 
 > I may not agree on the above point.  Since UDP is a transport  
 > protocol, encapsulating something in it cannot be handled by a  
 > *normal* packet decapsulation flow, while IPv4-in-IPv4 can 
 > be fit to  
 > the natural flow.  So switching from IPv4 encapsulation to UDP  
 > encapsulation may not be so easy as you say, especially for MIP  
 > stacks that are implemented in user space.

=> I'm not sure I get that. If you're implementing in user space you would
still know how to handle IP n IP today because that's what MIP6 does today
and some people have already done that in user space. The UDP part is always
there because the BU is always sent on UDP. So if someone already implements
MIP6 in user space they already need to know how to handle IP n IP and if we
choose to do UDP only in DSMIP then they end up in a situation where they
have to handle both tunnelling mechanisms anyway. 

So to summarise for the user space case:

- You always need to handle IP n IP for native MIPv6 (it doesn't matter
whether it's v6 in v6 or v6 in v4, it's all IP n IP). 

- You always need to handle the UDP tunnel because the BU in DSMIP is always
sent in UDP. 

The difference in the DSMIP case is that normal traffic can also be
tunnelled in UDP, but that's the case you want to keep anyway. So you'll
always end up having to support both types of tunnels whether we remove IP n
IP from DSMIP or not. 

What am I missing? 

Hesham




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



From mip6-bounces@ietf.org Thu Mar 22 01:49:30 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUG8t-0003Uv-4d; Thu, 22 Mar 2007 01:47:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUG6q-0001iH-IM
	for mip6@ietf.org; Thu, 22 Mar 2007 01:45:12 -0400
Received: from mail.sfc.wide.ad.jp ([2001:200:0:8803:203:47ff:fedf:73a6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUG3j-0000Pp-Be
	for mip6@ietf.org; Thu, 22 Mar 2007 01:42:03 -0400
Received: from [10.0.2.111] (jules.nautilus6.org [203.178.138.2])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 725A04D930;
	Thu, 22 Mar 2007 14:41:35 +0900 (JST)
Message-ID: <46021712.9040200@sfc.wide.ad.jp>
Date: Thu, 22 Mar 2007 14:41:38 +0900
From: Romain KUNTZ <kuntz@sfc.wide.ad.jp>
Organization: The University of Tokyo
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
References: <E1HTi6L-0007do-DQ@megatron.ietf.org>
	<623CC63B-6E30-45B5-AA1D-8947EAD698C6@iijlab.net>
In-Reply-To: <623CC63B-6E30-45B5-AA1D-8947EAD698C6@iijlab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, 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 Shima-san,

Keiichi SHIMA wrote:
> I may not agree on the above point.  Since UDP is a transport protocol, 
> encapsulating something in it cannot be handled by a *normal* packet 
> decapsulation flow, while IPv4-in-IPv4 can be fit to the natural flow.  
> So switching from IPv4 encapsulation to UDP encapsulation may not be so 
> easy as you say, especially for MIP stacks that are implemented in user 
> space.
> 
> I would like to hear opinions from who have already implemented DSMIPv4.

On linux, we perform UDP encapsulation/decapsulation for signaling using 
the packet transformation framework XFRM. Encapsulation/Decapsulation is 
thus performed in the kernel space.

We can easily switch from one mode to the other from the userland 
through netlink (socket-based interface for communication between kernel 
and userland processes).

XFRM is very flexible and rather easy to extend to implement parts of 
the DSMIPv6 spec.

Regards,
-- 
Romain KUNTZ
kuntz@sfc.wide.ad.jp

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



From mip6-bounces@ietf.org Thu Mar 22 03:24:11 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUHdx-0001KI-Pu; Thu, 22 Mar 2007 03:23:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUHdw-0001KD-1d
	for mip6@ietf.org; Thu, 22 Mar 2007 03:23:28 -0400
Received: from otm-mgo00.iij.ad.jp ([210.138.20.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUHdu-0001g0-ES
	for mip6@ietf.org; Thu, 22 Mar 2007 03:23:28 -0400
Received: OTM-MO(otm-mgo00) id l2M7NBPA029360;
	Thu, 22 Mar 2007 16:23:11 +0900 (JST)
Received: OTM-MIX(otm-mix00) id l2M7NAx3021327;
	Thu, 22 Mar 2007 16:23:11 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2M7MHq4093358
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 22 Mar 2007 16:22:22 +0900 (JST)
In-Reply-To: <E1HTyFT-0005Hb-Vw@megatron.ietf.org>
References: <E1HTyFT-0005Hb-Vw@megatron.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <95000CE4-E95C-481A-B26C-54D64EC868D8@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Thu, 22 Mar 2007 16:23:00 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, mip6@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Hesham,

On 2007/03/21, at 19:40, Hesham Soliman wrote:

>>> switching between the UDP tunnel and IP n IP is very small (from an
>>> implementation point of view).
>>
>> I may not agree on the above point.  Since UDP is a transport
>> protocol, encapsulating something in it cannot be handled by a
>> *normal* packet decapsulation flow, while IPv4-in-IPv4 can
>> be fit to
>> the natural flow.  So switching from IPv4 encapsulation to UDP
>> encapsulation may not be so easy as you say, especially for MIP
>> stacks that are implemented in user space.
>
> => I'm not sure I get that. If you're implementing in user space  
> you would
> still know how to handle IP n IP today because that's what MIP6  
> does today
> and some people have already done that in user space. The UDP part  
> is always
> there because the BU is always sent on UDP. So if someone already  
> implements
> MIP6 in user space they already need to know how to handle IP n IP  
> and if we
> choose to do UDP only in DSMIP then they end up in a situation  
> where they
> have to handle both tunnelling mechanisms anyway.
>
> So to summarise for the user space case:
>
> - You always need to handle IP n IP for native MIPv6 (it doesn't  
> matter
> whether it's v6 in v6 or v6 in v4, it's all IP n IP).
>
> - You always need to handle the UDP tunnel because the BU in DSMIP  
> is always
> sent in UDP.
>
> The difference in the DSMIP case is that normal traffic can also be
> tunnelled in UDP, but that's the case you want to keep anyway. So  
> you'll
> always end up having to support both types of tunnels whether we  
> remove IP n
> IP from DSMIP or not.
>
> What am I missing?

What I wanted to remove is the switching mechanism of encapsulation  
format when a mobile node is in the IPv4 network.  Currently, our  
implementation does not support IPv* in IPv4 encapsulation mechanism  
because of course MIPv6 doesn't require that.  If we a mobile node is  
allowed to use only the UDPv4 encapsulation mechanism, then we wanted  
to implement that.

But, as Romain said in other mail, at least it seems easy to  
implement both IPv4-encap and UDPv4-encap and switching between them  
in Linux.  So it depends on the design of implementation.


So, I want to propose a compromise.  Isn't it possible to add a flag  
for a mobile node to declare that the node wants to use the UDPv4  
encapsulation mechanism when sending a binding update message to its  
home agent?   Hesham said to me in our local conversation yesterday,  
such a flag already exists in the current spec, however, I re-read  
the text and couldn't find such a flag.

There is the 'F' flag to force the UDP encap format, but it is for a  
home agent and not for a mobile node.   In the current spec, a mobile  
node doesn't have any freedom to choose the encapsulation mechanism,  
only HA can force a mobile node to use UDP encapsulation.

If a mobile node can have such a flag, then nodes that want to use  
IPv*-in-IPv4 format can still keep the current encapsulation  
mechanisms (that is, IPv*-in-IPv4 by default and switch to UDPv4  
whenever necessary), and nodes that want to support only UDPv4  
encapsulation can specify its request in a binding update message  
using the newly added flag.

Is it feasible?

We (Koshiro Mitsuya, one of the developers of our MIPv6  
implementation) will send proposed text mentioning the above  
mechanism later.

---
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 Thu Mar 22 04:05:46 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUIHV-000204-Sz; Thu, 22 Mar 2007 04:04:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUIHU-0001tt-Vi
	for mip6@ietf.org; Thu, 22 Mar 2007 04:04:20 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUIHT-0008Jg-9x
	for mip6@ietf.org; Thu, 22 Mar 2007 04:04:20 -0400
Received: OTM-MO(otm-mgo01) id l2M84F5Y032145;
	Thu, 22 Mar 2007 17:04:15 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2M84FK4086504;
	Thu, 22 Mar 2007 17:04:15 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2M83PVk093956
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 22 Mar 2007 17:03:28 +0900 (JST)
In-Reply-To: <460005BE.4060306@gmail.com>
References: <1174404560.07.0.659815063549.issue94@mip4.org>
	<460005BE.4060306@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0F94C603-1A34-4BBE-B0EF-4A24BBC8189B@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Thu, 22 Mar 2007 17:04:08 +0900
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Alex,

On 2007/03/21, at 1:03, Alexandru Petrescu wrote:

> I agree only one encapsulation mechanism (for traversing IPv4) is  
> something useful, as opposed to implementing always two  
> encapsulating mechanisms.
>
> I'm not sure that UDP is the right answer for that.  IPv4-in-IPv4  
> mechanisms (without UDP) have their advantages: less packet  
> overhead. They have inconvenients that they should be mainly in  
> kernelspace (constraints).
>
> Would it be possible to have DS-MIPv6 implementation with one big  
> MIB knob that says:
> -use UDP for BU signalling, traffic encap and NAT traversal.
> or
> -use IPv4-in-IPv4 for BU signalling, traffic encap and NAT traversal.

It should work.  But what do you think about the idea to add a flag  
to specify the encapsulation mechanism in a binding update message as  
proposed in my mail to Hesham?  With the proposal, we don't need any  
manual configuration knobs and we can still use IPv*-in-IPv4  
mechanism, but allowing nodes that want to UDPv4 encapsulation only.

Regards,
---
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 Fri Mar 23 15:51:57 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUplt-0007wv-DX; Fri, 23 Mar 2007 15:49:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUpls-0007uE-3J
	for mip6@ietf.org; Fri, 23 Mar 2007 15:49:56 -0400
Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUplq-00022d-KC
	for mip6@ietf.org; Fri, 23 Mar 2007 15:49:56 -0400
Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 4AD7F38A89; Fri, 23 Mar 2007 20:49:24 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id 397353851A
	for <mip6@ietf.org>; Fri, 23 Mar 2007 20:49:24 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 2B9EC37E42
	for <mip6@ietf.org>; Fri, 23 Mar 2007 20:49:24 +0100 (CET)
Received: from shiraz.local.levkowetz.com ([192.168.3.14] helo=levkowetz.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <roundup-admin@mip4.org>) id 1HUplJ-0001IL-5y
	for mip6@ietf.org; Fri, 23 Mar 2007 20:49:23 +0100
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Kuntal Chowdhury <tracker-mip6@mip4.org>
Date: Fri, 23 Mar 2007 19:49:18 +0000
MIME-Version: 1.0
Message-Id: <1174679358.5.0.72020915846.issue95@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Rcpt-To: mip6@ietf.org
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on 
	shiraz.levkowetz.com
X-Spam-Level: 
X-Spam-Status: No, score=-104.4 required=2.5 tests=ALL_TRUSTED,BAYES_00,
	USER_IN_WHITELIST autolearn=no version=3.1.7-deb
X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [Mip6] [issue95] Mention DHCPv6 based Home Agent discovery
	mechanism in section
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


New submission from Kuntal Chowdhury <kchowdhury@starentnetworks.com>:

This issue has been discussed on the list. The current text in section 2.1 =
needs
to cover cases when DHCPv6 can be used to discover Home Agent information. =
The
email thread on this issue:

http://www1.ietf.org/mail-archive/web/mip6/current/msg05877.html

Proposed text:
-------------
Current:

"=2E...If a mobile
   node is located in an IPv4-only foreign network, it cannot rely on
   native IPv6 routing. The preferred solution for discovering the home
   agent's IPv4 address is through the Domain Name System (DNS).
"

New:

If a mobile node is located in an IPv4-only foreign network, it cannot rely=
 on
   native IPv6 routing. In this scenario, the solution for discovering the =
home
agent's IPv4 address is through the Domain Name System (DNS).

Also add the following in this section:

If the MN is attached to an IPv6-only or it is attached to an IPv6 and IPv4=
 Dual
stack foreign network, it shall use procedures defined in
draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt [add this reference] to
discover Home Agent information.

----------
category: Technical
draft: draft-ietf-mip6-nemo-v4traversal
messages: 346
nosy: kuntal
priority: Must fix
status: Text proposed
title: Mention DHCPv6 based Home Agent discovery mechanism in section

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

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



From mip6-bounces@ietf.org Mon Mar 26 09:02:04 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HVooT-0005PN-VQ; Mon, 26 Mar 2007 09:00:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HVooS-0005Ov-4O
	for mip6@ietf.org; Mon, 26 Mar 2007 09:00:40 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HVooQ-000234-TE
	for mip6@ietf.org; Mon, 26 Mar 2007 09:00:40 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-119.messagelabs.com!1174914037!12792176!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 22199 invoked from network); 26 Mar 2007 13:00:38 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-5.tower-119.messagelabs.com with SMTP;
	26 Mar 2007 13:00:38 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id l2QD0XrR025359;
	Mon, 26 Mar 2007 06:00:33 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l2QD0UHm008436;
	Mon, 26 Mar 2007 08:00:31 -0500 (CDT)
Message-ID: <4607C3E9.2090000@gmail.com>
Date: Mon, 26 Mar 2007 15:00:25 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
References: <1174404560.07.0.659815063549.issue94@mip4.org>
	<460005BE.4060306@gmail.com>
	<0F94C603-1A34-4BBE-B0EF-4A24BBC8189B@iijlab.net>
In-Reply-To: <0F94C603-1A34-4BBE-B0EF-4A24BBC8189B@iijlab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

Keiichi SHIMA wrote:
> Hello Alex,
> 
> On 2007/03/21, at 1:03, Alexandru Petrescu wrote:
> 
>> I agree only one encapsulation mechanism (for traversing IPv4) is 
>> something useful, as opposed to implementing always two
>> encapsulating mechanisms.
>> 
>> I'm not sure that UDP is the right answer for that.  IPv4-in-IPv4 
>> mechanisms (without UDP) have their advantages: less packet
>> overhead. They have inconvenients that they should be mainly in
>> kernelspace (constraints).
>> 
>> Would it be possible to have DS-MIPv6 implementation with one big
>> MIB knob that says: -use UDP for BU signalling, traffic encap and
>> NAT traversal. or -use IPv4-in-IPv4 for BU signalling, traffic
>> encap and NAT traversal.
> 
> It should work.  But what do you think about the idea to add a flag
> to specify the encapsulation mechanism in a binding update message as
>  proposed in my mail to Hesham?  With the proposal, we don't need any
>  manual configuration knobs and we can still use IPv*-in-IPv4
> mechanism, but allowing nodes that want to UDPv4 encapsulation only.

I think it could work (flag set by MN to specify UDP or IP encapsulation).

But should be done in tandem with that 'F' flag by HA.  One wouldnt want 
the MN to request eg UDP encapsulation and the HA to force IP encapsulation.

I prefer the MN to decide which encapsulation method to use (and not the 
HA).  However, the HA is the first to know whether there's a NAT in 
between.  A MN doesn't know whether there's a NAT in between, at the 
time it sends BU.

I've always thought there should be some form of tunnelling parameters 
negotiation between MN and HA, before sending the  BU/BAck.  Also 
periodic heartbeats with re-negotiation if necessary.

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From mip6-bounces@ietf.org Mon Mar 26 11:57:29 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HVrYQ-0001wp-Dy; Mon, 26 Mar 2007 11:56:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HVrYO-0001wY-Nj
	for mip6@ietf.org; Mon, 26 Mar 2007 11:56:16 -0400
Received: from outbound-blu.frontbridge.com ([65.55.251.16]
	helo=outbound6-blu-R.bigfish.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVrY9-0005gC-B7
	for mip6@ietf.org; Mon, 26 Mar 2007 11:56:16 -0400
Received: from outbound6-blu.bigfish.com (localhost.localdomain [127.0.0.1])
	by outbound6-blu-R.bigfish.com (Postfix) with ESMTP id 149F9108F9F7;
	Mon, 26 Mar 2007 15:55:43 +0000 (UTC)
Received: from mail191-blu-R.bigfish.com (unknown [10.1.252.3])
	by outbound6-blu.bigfish.com (Postfix) with ESMTP id D94CABEAAAB;
	Mon, 26 Mar 2007 15:55:42 +0000 (UTC)
Received: from mail191-blu (localhost.localdomain [127.0.0.1])
	by mail191-blu-R.bigfish.com (Postfix) with ESMTP id 919CECB0106;
	Mon, 26 Mar 2007 15:55:42 +0000 (UTC)
X-BigFish: V
Received: by mail191-blu (MessageSwitch) id 1174924542158604_13584;
	Mon, 26 Mar 2007 15:55:42 +0000 (UCT)
Received: from smtpgw5.sprintspectrum.com (smtpgw5.sprintspectrum.com
	[207.40.188.13])
	by mail191-blu.bigfish.com (Postfix) with ESMTP id 5DC761F8073;
	Mon, 26 Mar 2007 15:55:40 +0000 (UTC)
Received: from mailhost.sprintspectrum.com (smtpgw8.it.sprintspectrum.com
	[207.40.65.56])
	by smtpgw5.sprintspectrum.com (8.12.10/8.12.8) with ESMTP id
	l2QFtaXC002476; Mon, 26 Mar 2007 10:55:36 -0500 (CDT)
Received: from pdawg06a.ad.sprint.com (PDAWG06A.corp.sprint.com [10.122.2.33])
	by mailhost.sprintspectrum.com (Switch-3.2.5/Switch-3.2.5) with
	ESMTP id l2QFtTEk023735; Mon, 26 Mar 2007 10:55:36 -0500 (CDT)
Received: from PLSWB09C.ad.sprint.com ([208.10.70.239]) by
	pdawg06a.ad.sprint.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Mar 2007 10:55:31 -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] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Mon, 26 Mar 2007 10:55:30 -0500
Message-ID: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>
In-Reply-To: <4607C3E9.2090000@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Thread-Index: Acdvp4ir24juDDX7T/W2EI/t8u6K5AAHI6bA
From: "Zhang, Qiang [NTK]" <Qiang.Zhang@sprint.com>
To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>,
	"Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 26 Mar 2007 15:55:31.0334 (UTC)
	FILETIME=[2E865260:01C76FBF]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
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,=20

>From an operation point of view, both or more tunneling options should =
be supported so to make the deployment flexible. Only HA knows whether =
the device is traversing through NAT devices, therefore the decision =
will have to be made jointly by MN and HA. I would think MN can send =
preference setting flag to mandate or option-ize the UDP tunneling,=20

If MN choose to option the UDP tunneling
	if (NAPT happened determined by HA)
		HA should set a flag inform MN to mandate the UDP tunneling
	if (NAPT does not happen determined by HA & HA mandate the UDP =
tunneling)
		HA should set a flag inform MN to mandate the UDP tunneling
      if (NAPT does not happen determined by HA & HA only option the =
tunneling)
		HA should set a flag inform MN to optionize the UDP tunneling
Else if MN choose to mandate the UDP tunneling
	if (NAPT happened)
		HA should set a flag to mandate the UDP tunneling
	else if (NAPT does not happen & HA mandate IP-IP tunneling)
		HA should set a flag to mandate IP-IP tunneling
	else if (NAPT does nto happen & HA optionize the tunneling)
		HA should set a flag to optinize tunneling

Then the MN will be able to choose from the joint decision from those =
decision logics either mandate or optinize the tunneling scheme

Also when saying NAPT, as long as there is port number change it should =
be considered that a NAPT happened and the midbox won't be friendly to =
IP-IP tunnel (well there may still be devices that are really weird they =
are out of scope I would say); keep-alive timer is a potential loophole =
in the design as there is no way to understand the timers in the NAPT =
state machine on those devices, therefore it is a system wide parameter =
to be tuned along the path.

RFC3519 should be referenced as most of the items had been discussed =
before

Thanks!
-----Original Message-----
From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]=20
Sent: Monday, March 26, 2007 8:00 AM
To: Keiichi SHIMA
Cc: mip6@ietf.org
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 =
network

Keiichi SHIMA wrote:
> Hello Alex,
>=20
> On 2007/03/21, at 1:03, Alexandru Petrescu wrote:
>=20
>> I agree only one encapsulation mechanism (for traversing IPv4) is=20
>> something useful, as opposed to implementing always two encapsulating =

>> mechanisms.
>>=20
>> I'm not sure that UDP is the right answer for that.  IPv4-in-IPv4=20
>> mechanisms (without UDP) have their advantages: less packet overhead. =

>> They have inconvenients that they should be mainly in kernelspace=20
>> (constraints).
>>=20
>> Would it be possible to have DS-MIPv6 implementation with one big MIB =

>> knob that says: -use UDP for BU signalling, traffic encap and NAT=20
>> traversal. or -use IPv4-in-IPv4 for BU signalling, traffic encap and=20
>> NAT traversal.
>=20
> It should work.  But what do you think about the idea to add a flag to =

> specify the encapsulation mechanism in a binding update message as =20
> proposed in my mail to Hesham?  With the proposal, we don't need any =20
> manual configuration knobs and we can still use IPv*-in-IPv4=20
> mechanism, but allowing nodes that want to UDPv4 encapsulation only.

I think it could work (flag set by MN to specify UDP or IP =
encapsulation).

But should be done in tandem with that 'F' flag by HA.  One wouldnt want =
the MN to request eg UDP encapsulation and the HA to force IP =
encapsulation.

I prefer the MN to decide which encapsulation method to use (and not the =
HA).  However, the HA is the first to know whether there's a NAT in =
between.  A MN doesn't know whether there's a NAT in between, at the =
time it sends BU.

I've always thought there should be some form of tunnelling parameters =
negotiation between MN and HA, before sending the  BU/BAck.  Also =
periodic heartbeats with re-negotiation if necessary.

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email =
______________________________________________________________________

_______________________________________________
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 Mar 28 00:19:31 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWPbR-0007M1-Qv; Wed, 28 Mar 2007 00:17:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWPbQ-0007Lq-2V
	for mip6@ietf.org; Wed, 28 Mar 2007 00:17:40 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWPbO-0001za-Km
	for mip6@ietf.org; Wed, 28 Mar 2007 00:17:40 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l2S4H2gv024261 for <mip6@ietf.org>; Wed, 28 Mar 2007 07:17:35 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 07:17:34 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Mar 2007 23:17:32 -0500
Received: from 10.241.58.159 ([10.241.58.159]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 28 Mar 2007 04:17:32 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Tue, 27 Mar 2007 23:17:43 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: Mobile IPv6 Mailing List <mip6@ietf.org>
Message-ID: <C22F5697.328BF%basavaraj.patil@nokia.com>
Thread-Topic: Note of confidence in Hesham as the editor for the DS-MIP6
	solution I-D
Thread-Index: Acdw8AfhRnyYg9zjEdueggARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 04:17:32.0538 (UTC)
	FILETIME=[01A4ADA0:01C770F0]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070328071735-558F9BB0-2786C5ED/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Mip6] Note of confidence in Hesham as the editor for the DS-MIP6
 solution I-D
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

For the record, the chairs would like to state that we are quite happy
with the work Hesham has been doing as the editor for the DS-MIP6
solution I-D (draft-ietf-mip6-nemo-v4traversal).

On the concern raised during the meeting in Prague about an issue not
being resolved as per consensus, I would like to say that the chairs
are to be held responsible for not following the work closely and
monitoring consensus w.r.t the issues.

We will review the mailing list and the discussion and summarize the
conclusion. Hesham in the role of editor has our confidence.

-Chairs


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



From mip6-bounces@ietf.org Wed Mar 28 03:35:30 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWSfx-0006Fd-D2; Wed, 28 Mar 2007 03:34:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWSfw-0006BJ-HB
	for mip6@ietf.org; Wed, 28 Mar 2007 03:34:32 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWSfs-0001sz-Hs
	for mip6@ietf.org; Wed, 28 Mar 2007 03:34:32 -0400
Received: from [124.191.178.123] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HWSfJ-00029e-O2; Wed, 28 Mar 2007 17:33:53 +1000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>
Date: Wed, 28 Mar 2007 17:33:25 +1000
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.3028
In-Reply-To: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>
Thread-Index: Acdvp4ir24juDDX7T/W2EI/t8u6K5AAHI6bAAFGVW+A=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mip6@ietf.org
Subject: [Mip6] concensus on [issue94] fixing encapsulation mechanism in
	IPv4 network
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org
Message-Id: <E1HWSfx-0006Fd-D2@megatron.ietf.org>

Kiichi, all, 

I think we've seen the different angles of this issue now and it's time to
close it. 
So I suggest that we choose one of the two options listed below. 

Folks, 

The "new" issue is about whether or not the MN can request one form of
tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
are:

A. Add a flag that allows the MN to request UDP tunnelling interface
(independently of the presence of a NAT) from the HA, when sending the BU.
The HA can override the MN's request. Or, 

B. Do nothing. I.e. the MN sends the BU as described in the spec today and
the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
IP. 

Please express your preference for one of the options above. Let's not make
things complicated and get into negotiating the tunnelling mechanism, one of
the two above will suffice. 

I'll leave it open till next Tuesday. 

Thanks,
Hesham



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



From mip6-bounces@ietf.org Wed Mar 28 04:09:58 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWTDH-0006cO-TU; Wed, 28 Mar 2007 04:08:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWTDH-0006cH-3F
	for mip6@ietf.org; Wed, 28 Mar 2007 04:08:59 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWTD4-0003le-7V
	for mip6@ietf.org; Wed, 28 Mar 2007 04:08:59 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l2S88dA0002431 for <mip6@ietf.org>; Wed, 28 Mar 2007 11:08:44 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 11:08:40 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 11:08:40 +0300
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] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Date: Wed, 28 Mar 2007 11:08:40 +0300
Message-ID: <58357EDC7884E24BAD684C1B2D91F96D0535D0A7@trebe101.NOE.Nokia.com>
In-Reply-To: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Thread-Index: Acdvp4ir24juDDX7T/W2EI/t8u6K5AAHI6bAAFGVW+AAAQG5cA==
References: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>
	<E1HWSfx-0006Fd-HX@megatron.ietf.org>
From: <Markku.Ala-Vannesluoma@nokia.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 28 Mar 2007 08:08:40.0674 (UTC)
	FILETIME=[4BB24C20:01C77110]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070328110844-7FAEBBB0-025AB09F/0-0/0-0
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

As was indicated in some earlier email, in some environments the problem
is not so much the NATs but the FWs that
don't allow IP-in-IP to pass. We have encountered this in our tests as
well.=20
I'd like to give the MN the choice to select whether to use UDP
tunneling or not (=3D prefer option A).

-Markku

>-----Original Message-----
>From: ext Hesham Soliman [mailto:Hesham@elevatemobile.com]=20
>Sent: 28 March, 2007 10:33
>To: 'Keiichi SHIMA'
>Cc: mip6@ietf.org
>Subject: [Mip6] concensus on [issue94] fixing encapsulation=20
>mechanism inIPv4 network
>
>Kiichi, all,=20
>
>I think we've seen the different angles of this issue now and=20
>it's time to close it.=20
>So I suggest that we choose one of the two options listed below.=20
>
>Folks,=20
>
>The "new" issue is about whether or not the MN can request one=20
>form of tunnelling (i.e. UDP) when sending a BU to the HA. The=20
>two choices we have
>are:
>
>A. Add a flag that allows the MN to request UDP tunnelling=20
>interface (independently of the presence of a NAT) from the=20
>HA, when sending the BU.
>The HA can override the MN's request. Or,=20
>
>B. Do nothing. I.e. the MN sends the BU as described in the=20
>spec today and the HA tells the MN in the BA whether it should=20
>use UDP tunnelling or IP in IP.=20
>
>Please express your preference for one of the options above.=20
>Let's not make things complicated and get into negotiating the=20
>tunnelling mechanism, one of the two above will suffice.=20
>
>I'll leave it open till next Tuesday.=20
>
>Thanks,
>Hesham
>
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Mar 28 05:13:48 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWUCz-0000JH-Jb; Wed, 28 Mar 2007 05:12:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWUCy-0000J9-Eq
	for mip6@ietf.org; Wed, 28 Mar 2007 05:12:44 -0400
Received: from av9-2-sn3.vrr.skanova.net ([81.228.9.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWUCx-0001g2-3b
	for mip6@ietf.org; Wed, 28 Mar 2007 05:12:44 -0400
Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 505CC385CB; Wed, 28 Mar 2007 11:12:40 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 0BF6A38567; Wed, 28 Mar 2007 11:12:40 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id DCD7437E4C;
	Wed, 28 Mar 2007 11:12:39 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HWUCs-0003GO-QO; Wed, 28 Mar 2007 11:12:38 +0200
Message-ID: <460A318A.1000402@levkowetz.com>
Date: Wed, 28 Mar 2007 11:12:42 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
In-Reply-To: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: Hesham@elevatemobile.com, mip6@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 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>
Errors-To: mip6-bounces@ietf.org

I prefer 'A'.

MIPv4 NAT traversal has that feature, and it is appreciated.


	Henrik

on 2007-03-28 09:33 Hesham Soliman said the following:
> Kiichi, all, 
> 
> I think we've seen the different angles of this issue now and it's time to
> close it. 
> So I suggest that we choose one of the two options listed below. 
> 
> Folks, 
> 
> The "new" issue is about whether or not the MN can request one form of
> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
> are:
> 
> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending the BU.
> The HA can override the MN's request. Or, 
> 
> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
> IP. 
> 
> Please express your preference for one of the options above. Let's not make
> things complicated and get into negotiating the tunnelling mechanism, one of
> the two above will suffice. 
> 
> I'll leave it open till next Tuesday. 
> 
> Thanks,
> Hesham
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 

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



From mip6-bounces@ietf.org Wed Mar 28 05:14:21 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWUEX-00010W-BR; Wed, 28 Mar 2007 05:14:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWUEV-00010I-Jr
	for mip6@ietf.org; Wed, 28 Mar 2007 05:14:19 -0400
Received: from av12-2-sn2.hy.skanova.net ([81.228.8.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWUET-0002D0-9y
	for mip6@ietf.org; Wed, 28 Mar 2007 05:14:19 -0400
Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id A756B38823; Wed, 28 Mar 2007 11:13:53 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id 61FDA38780
	for <mip6@ietf.org>; Wed, 28 Mar 2007 11:13:53 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 2562437E49
	for <mip6@ietf.org>; Wed, 28 Mar 2007 11:13:51 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HWUE2-0005yf-JV; Wed, 28 Mar 2007 11:13:50 +0200
Message-ID: <460A31D2.4010603@levkowetz.com>
Date: Wed, 28 Mar 2007 11:13:54 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: Re: [Mip6] Note of confidence in Hesham as the editor for the DS-MIP6
	solution I-D
References: <C22F5697.328BF%basavaraj.patil@nokia.com>
In-Reply-To: <C22F5697.328BF%basavaraj.patil@nokia.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: mip6@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 2007-03-28 06:17 Basavaraj Patil said the following:
> Hello,
> 
> For the record, the chairs would like to state that we are quite happy
> with the work Hesham has been doing as the editor for the DS-MIP6
> solution I-D (draft-ietf-mip6-nemo-v4traversal).
> 
> On the concern raised during the meeting in Prague about an issue not
> being resolved as per consensus, I would like to say that the chairs
> are to be held responsible for not following the work closely and
> monitoring consensus w.r.t the issues.
> 
> We will review the mailing list and the discussion and summarize the
> conclusion. Hesham in the role of editor has our confidence.

And mine too.


	Henrik

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



From mip6-bounces@ietf.org Wed Mar 28 05:23:15 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWUMy-00033a-Kl; Wed, 28 Mar 2007 05:23:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWUMx-00033U-N5
	for mip6@ietf.org; Wed, 28 Mar 2007 05:23:03 -0400
Received: from floor.dave.sonera.fi ([131.177.130.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWUMw-00055s-8L
	for mip6@ietf.org; Wed, 28 Mar 2007 05:23:03 -0400
Received: from floor.dave.sonera.fi (localhost [127.0.0.1]) by
	floor.dave.sonera.fi (Sendmail) with ESMTP id l2S9MofD012138
	for <mip6@ietf.org>; Wed, 28 Mar 2007 12:22:50 +0300 (EEST)
Received: from [131.177.37.116] (l50029133.pool.sonera.fi [131.177.37.116]) by
	floor.dave.sonera.fi (Sendmail) with ESMTP id l2S9MW7t012135;
	Wed, 28 Mar 2007 12:22:37 +0300 (EEST)
Message-ID: <460A33D6.2010801@teliasonera.com>
Date: Wed, 28 Mar 2007 12:22:30 +0300
From: Jouni Korhonen <jouni.korhonen@teliasonera.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4	 network
References: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
In-Reply-To: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

I prefer the option'A'.. looks like MIPv4 NAT feature that we have had 
positive experiences, with both NATs and especially traversing FWs.

Cheers,
	Jouni

Hesham Soliman kirjoitti:
> Kiichi, all, 
> 
> I think we've seen the different angles of this issue now and it's time to
> close it. 
> So I suggest that we choose one of the two options listed below. 
> 
> Folks, 
> 
> The "new" issue is about whether or not the MN can request one form of
> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
> are:
> 
> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending the BU.
> The HA can override the MN's request. Or, 
> 
> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
> IP. 
> 
> Please express your preference for one of the options above. Let's not make
> things complicated and get into negotiating the tunnelling mechanism, one of
> the two above will suffice. 
> 
> I'll leave it open till next Tuesday. 
> 
> Thanks,
> Hesham
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 

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



From mip6-bounces@ietf.org Wed Mar 28 05:29:23 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWUSS-0005wx-Kb; Wed, 28 Mar 2007 05:28:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWUSR-0005py-29
	for mip6@ietf.org; Wed, 28 Mar 2007 05:28:43 -0400
Received: from 33.106-14-84.ripe.coltfrance.com ([84.14.106.33]
	helo=proxy.6wind.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HWUSN-0006B2-U8
	for mip6@ietf.org; Wed, 28 Mar 2007 05:28:41 -0400
Received: from [127.0.0.1] (unknown [10.16.0.122])
	by proxy.6wind.com (Postfix) with ESMTP id DBB30525F84;
	Wed, 28 Mar 2007 11:28:11 +0200 (CEST)
Message-ID: <460A352D.9000508@6wind.com>
Date: Wed, 28 Mar 2007 11:28:13 +0200
From: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
Organization: 6WIND
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <200703280939185.SM06676@037f27dd816a40c>
In-Reply-To: <200703280939185.SM06676@037f27dd816a40c>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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

Sorry I miss your point in option A: HA can override it.
I thought the idea of option A is to allow MN to force UDP encap.
Do you mean that you don't want the spec to force HA to support UDP encap ?

Thanks,

Jean-Mickael



Hesham Soliman wrote:
> Kiichi, all, 
> 
> I think we've seen the different angles of this issue now and it's time to
> close it. 
> So I suggest that we choose one of the two options listed below. 
> 
> Folks, 
> 
> The "new" issue is about whether or not the MN can request one form of
> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
> are:
> 
> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending the BU.
> The HA can override the MN's request. Or, 
> 
> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
> IP. 
> 
> Please express your preference for one of the options above. Let's not make
> things complicated and get into negotiating the tunnelling mechanism, one of
> the two above will suffice. 
> 
> I'll leave it open till next Tuesday. 
> 
> Thanks,
> Hesham
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 
> 



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



From mip6-bounces@ietf.org Wed Mar 28 05:49:24 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWUlS-0001o3-26; Wed, 28 Mar 2007 05:48:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWUlR-0001nx-7H
	for mip6@ietf.org; Wed, 28 Mar 2007 05:48:21 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWUlO-0001vR-Ss
	for mip6@ietf.org; Wed, 28 Mar 2007 05:48:21 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 02:48:18 -0700
Message-ID: <460A39D9.4090201@azairenet.com>
Date: Wed, 28 Mar 2007 02:48:09 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
In-Reply-To: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 09:48:18.0353 (UTC)
	FILETIME=[36ABBA10:01C7711E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I prefer option 'B'.

The MN doesn't really know if there is a NAT on the path. It also
does not know if there is a firewall in the path blocking IP-in-IP
packets. Since it does not know any of this, I am afraid many
mobile node implementations will always be setting this flag. Then,
if the HA is allowed to override this, then aren't we basically
saying HA decides whether the MN should use UDP tunneling or not?
This means option 'B' is what is being used to decide whether UDP
tunneling is used or not.

What am I missing?

Vijay

Hesham Soliman wrote:
> Kiichi, all, 
> 
> I think we've seen the different angles of this issue now and it's time to
> close it. 
> So I suggest that we choose one of the two options listed below. 
> 
> Folks, 
> 
> The "new" issue is about whether or not the MN can request one form of
> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
> are:
> 
> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending the BU.
> The HA can override the MN's request. Or, 
> 
> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
> IP. 
> 
> Please express your preference for one of the options above. Let's not make
> things complicated and get into negotiating the tunnelling mechanism, one of
> the two above will suffice. 
> 
> I'll leave it open till next Tuesday. 
> 
> Thanks,
> Hesham
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Mar 28 05:54:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWUqj-0003FT-9V; Wed, 28 Mar 2007 05:53:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWUqh-0003FD-Eb
	for mip6@ietf.org; Wed, 28 Mar 2007 05:53:47 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWUqd-0003Ne-CQ
	for mip6@ietf.org; Wed, 28 Mar 2007 05:53:47 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 02:53:42 -0700
Message-ID: <460A3B22.30108@azairenet.com>
Date: Wed, 28 Mar 2007 02:53:38 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: mip6@ietf.org
Subject: Re: [Mip6] [issue95] Mention DHCPv6 based Home Agent
	discovery	mechanism in section
References: <1174679358.5.0.72020915846.issue95@mip4.org>
In-Reply-To: <1174679358.5.0.72020915846.issue95@mip4.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 09:53:42.0541 (UTC)
	FILETIME=[F7E6E3D0:01C7711E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Mip6 issue tracker <tracker-mip6@mip4.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Kuntal Chowdhury wrote:
> New submission from Kuntal Chowdhury <kchowdhury@starentnetworks.com>:
> 
> This issue has been discussed on the list. The current text in section 2.1 needs
> to cover cases when DHCPv6 can be used to discover Home Agent information. The
> email thread on this issue:
> 
> http://www1.ietf.org/mail-archive/web/mip6/current/msg05877.html
> 
> Proposed text:
> -------------
> Current:
> 
> "....If a mobile
>    node is located in an IPv4-only foreign network, it cannot rely on
>    native IPv6 routing. The preferred solution for discovering the home
>    agent's IPv4 address is through the Domain Name System (DNS).
> "
> 
> New:
> 
> If a mobile node is located in an IPv4-only foreign network, it cannot rely on
>    native IPv6 routing. In this scenario, the solution for discovering the home
> agent's IPv4 address is through the Domain Name System (DNS).

This is fine.

> Also add the following in this section:
> 
> If the MN is attached to an IPv6-only or it is attached to an IPv6 and IPv4 Dual
> stack foreign network, it shall use procedures defined in
> draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt [add this reference] to
> discover Home Agent information.

I have issues with the use of word "shall". In the first place
the MN could still use DNS for HA discovery. So, at the most
it can only be a "MAY". Second,
draft-ietf-mip6-bootstrapping-integrated-dhc does not have
extensions to return an IPv4 address of the home agent in
addition to the IPv6 address of the home agent. So the solution
described in draft-ietf-mip6-bootstrapping-integrated-dhc is not
sufficient for DS-MIPv6 even when the mobile node is attached to
an IPv6 access network.

Vijay

> 
> ----------
> category: Technical
> draft: draft-ietf-mip6-nemo-v4traversal
> messages: 346
> nosy: kuntal
> priority: Must fix
> status: Text proposed
> title: Mention DHCPv6 based Home Agent discovery mechanism in section
> 
> _________________________________________________
> Mip6 issue tracker <tracker-mip6@mip4.org>
> <http://www.mip4.org/issues/tracker/mip6/issue95>
> _________________________________________________
> 
> _______________________________________________
> 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 Mar 28 06:07:48 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWV3Q-0003pV-RH; Wed, 28 Mar 2007 06:06:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWV3P-0003pO-V3
	for mip6@ietf.org; Wed, 28 Mar 2007 06:06:55 -0400
Received: from otm-mgo00.iij.ad.jp ([210.138.20.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWV3O-0007Ce-E7
	for mip6@ietf.org; Wed, 28 Mar 2007 06:06:55 -0400
Received: OTM-MO(otm-mgo00) id l2SA6bLh027556;
	Wed, 28 Mar 2007 19:06:38 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2SA6bRr005538;
	Wed, 28 Mar 2007 19:06:37 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2SA5gik055478
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 28 Mar 2007 19:05:43 +0900 (JST)
In-Reply-To: <20070328073355.B105DFB956@sh1.iijlab.net>
References: <20070328073355.B105DFB956@sh1.iijlab.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Date: Wed, 28 Mar 2007 19:06:37 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
Subject: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism in
	IPv4 network
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 Hesham,

I think the text explaining the option 'A' is not exactly what I  
proposed in my previous mail.  Please let me clarify the text about  
the option 'A'.


On 2007/03/28, at 16:33, Hesham Soliman wrote:

> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending  
> the BU.
> The HA can override the MN's request. Or,

The idea is to introduce a new flag for MN to request the UDP tunnel  
mode.  Let's call it as the 'U (requesting UDP tunnel)' flag.  If the  
MN doesn't specify the 'U' flag, the behavior is exactly the same as  
the current specification.  The HA can decide what kind of tunneling  
mechanism (IP-in-IP or UDP-in-IP).

When the MN sets the 'U' flag on, the HA always replies with the 'F  
(Force UDP tunnel)' flag.  This is a new behavior what I want to  
propose.

The HA shouldn't override the 'U' flag.  If we allow overriding the  
'U' flag, then there is no difference between the option 'A' and 'B'.

Regards,
---
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 Wed Mar 28 06:14:15 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWV9s-0006uo-MB; Wed, 28 Mar 2007 06:13:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWV9r-0006ui-Ky
	for mip6@ietf.org; Wed, 28 Mar 2007 06:13:35 -0400
Received: from smtp.netregistry.net ([202.124.241.204]
	helo=smtp-1.servers.netregistry.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWV9q-0000TF-5h
	for mip6@ietf.org; Wed, 28 Mar 2007 06:13:35 -0400
Received: from [124.191.178.123] (helo=PC20005)
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.50 #1
	(Debian)) id 1HWV9e-0005yk-MR
	for <mip6@ietf.org>; Wed, 28 Mar 2007 20:13:22 +1000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>
Date: Wed, 28 Mar 2007 20:13:03 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdxIMkXhQMSx8BfQ7WiZsaEnQSNBQAAD61Q
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: mip6@ietf.org
Subject: [Mip6] RE: concensus on [issue94] fixing encapsulation mechanism in
	IPv4 network
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org
Message-Id: <E1HWV9s-0006uo-MB@megatron.ietf.org>


 > The idea is to introduce a new flag for MN to request the 
 > UDP tunnel  
 > mode.  Let's call it as the 'U (requesting UDP tunnel)' 
 > flag.  If the  
 > MN doesn't specify the 'U' flag, the behavior is exactly the 
 > same as  
 > the current specification.  The HA can decide what kind of 
 > tunneling  
 > mechanism (IP-in-IP or UDP-in-IP).
 > 
 > When the MN sets the 'U' flag on, the HA always replies with the 'F  
 > (Force UDP tunnel)' flag.  This is a new behavior what I want to  
 > propose.
 > 
 > The HA shouldn't override the 'U' flag.  If we allow overriding the  
 > 'U' flag, then there is no difference between the option 'A' and 'B'.

=> There is a difference between A and B of course. The difference is that
in B the MN can't request anything and is either told to use UDP or told to
use IP in IP. In A, the MN can request UDP tunnels. Like any other request
in MIPv6 (e.g. BU lifetime, HoA ....etc) the HA always has the upper hand
and decides whether the request is acceptable or not. I simply followed the
same rule here. For instance, the HA/MAP might think UDP tunnelling is not
acceptable for policy reasons (e.g. an operator doesn't want the MN to waste
BW when UDP is not needed). I don't have an exhaustive list of scenarios so
I just erred on the conservative side of keeping with the current approach
in MIPv6. 

Hesham


 > 
 > Regards,
 > ---
 > 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 Wed Mar 28 06:30:53 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWVQ2-0007Kc-56; Wed, 28 Mar 2007 06:30:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWVQ0-0007KK-AN
	for mip6@ietf.org; Wed, 28 Mar 2007 06:30:16 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWVPy-0003OD-0s
	for mip6@ietf.org; Wed, 28 Mar 2007 06:30:16 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l2SATri29168; Wed, 28 Mar 2007 10:29:53 GMT
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: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
Date: Wed, 28 Mar 2007 05:29:49 -0500
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA4371136B508D@zrc2hxm2.corp.nortel.com>
In-Reply-To: <3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
thread-index: AcdxIUM9g+7I4hDSQPixxfdFIJrcvwAAj41w
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Keiichi SHIMA" <keiichi@iijlab.net>,
	"Hesham Soliman" <Hesham@elevatemobile.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
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

All,

Sorry for jumping in without previously being involved in the
discussion. However, in my mind, HA should have the upper hand of
deciding whatever the MN is requesting. If the HA has the right to
reject MN BU, it has the right to deny UDP encapsulation.

I believe that should be the correct approach.

Regards,
Ahmad
=20

> -----Original Message-----
> From: Keiichi SHIMA [mailto:keiichi@iijlab.net]=20
> Sent: Wednesday, March 28, 2007 6:07 AM
> To: Hesham Soliman
> Cc: mip6@ietf.org; Keiichi SHIMA
> Subject: [Mip6] Re: concensus on [issue94] fixing=20
> encapsulation mechanism in IPv4 network
>=20
> Hello Hesham,
>=20
> I think the text explaining the option 'A' is not exactly=20
> what I proposed in my previous mail.  Please let me clarify=20
> the text about the option 'A'.
>=20
>=20
> On 2007/03/28, at 16:33, Hesham Soliman wrote:
>=20
> > A. Add a flag that allows the MN to request UDP tunnelling=20
> interface=20
> > (independently of the presence of a NAT) from the HA, when=20
> sending the=20
> > BU.
> > The HA can override the MN's request. Or,
>=20
> The idea is to introduce a new flag for MN to request the UDP=20
> tunnel mode.  Let's call it as the 'U (requesting UDP=20
> tunnel)' flag.  If the MN doesn't specify the 'U' flag, the=20
> behavior is exactly the same as the current specification. =20
> The HA can decide what kind of tunneling mechanism (IP-in-IP=20
> or UDP-in-IP).
>=20
> When the MN sets the 'U' flag on, the HA always replies with=20
> the 'F (Force UDP tunnel)' flag.  This is a new behavior what=20
> I want to propose.
>=20
> The HA shouldn't override the 'U' flag.  If we allow=20
> overriding the 'U' flag, then there is no difference between=20
> the option 'A' and 'B'.
>=20
> Regards,
> ---
> Keiichi SHIMA
> IIJ Research Laboratory <keiichi@iijlab.net> WIDE Project=20
> <shima@wide.ad.jp>
>=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 Mar 28 06:33:00 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWVSe-0008GW-AJ; Wed, 28 Mar 2007 06:33:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWVSd-0008GN-0z
	for mip6@ietf.org; Wed, 28 Mar 2007 06:32:59 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWVSb-0003ma-Mm
	for mip6@ietf.org; Wed, 28 Mar 2007 06:32:59 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 03:32:45 -0700
Message-ID: <460A4448.1050507@azairenet.com>
Date: Wed, 28 Mar 2007 03:32:40 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
In-Reply-To: <3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 10:32:45.0462 (UTC)
	FILETIME=[6C644360:01C77124]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
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

Keiichi SHIMA wrote:
> Hello Hesham,
> 
> I think the text explaining the option 'A' is not exactly what I 
> proposed in my previous mail.  Please let me clarify the text about the 
> option 'A'.
> 
> 
> On 2007/03/28, at 16:33, Hesham Soliman wrote:
> 
>> A. Add a flag that allows the MN to request UDP tunnelling interface
>> (independently of the presence of a NAT) from the HA, when sending the 
>> BU.
>> The HA can override the MN's request. Or,
> 
> The idea is to introduce a new flag for MN to request the UDP tunnel 
> mode.  Let's call it as the 'U (requesting UDP tunnel)' flag.  If the MN 
> doesn't specify the 'U' flag, the behavior is exactly the same as the 
> current specification.  The HA can decide what kind of tunneling 
> mechanism (IP-in-IP or UDP-in-IP).
> 
> When the MN sets the 'U' flag on, the HA always replies with the 'F 
> (Force UDP tunnel)' flag.  This is a new behavior what I want to propose.

We would also need to mention when the MN would be setting this
flag. Is it when it wants to use UDP encapsulation due to
implementation related considerations? I guess you want to use
the 'U' flag for this.

But there are others who have expressed that this flag can be
used for firewall traversal. Since the MN wouldn't know if
there is a  firewall on the path, it would end up setting the
'U' flag all the time. If the HA can't override it, then
providing a NAT detection mechanism is useless, IMO.

Vijay

> 
> The HA shouldn't override the 'U' flag.  If we allow overriding the 'U' 
> flag, then there is no difference between the option 'A' and 'B'.
> 
> Regards,
> ---
> 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


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



From mip6-bounces@ietf.org Wed Mar 28 06:35:22 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWVUk-0000XF-To; Wed, 28 Mar 2007 06:35:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWVUj-0000XA-13
	for mip6@ietf.org; Wed, 28 Mar 2007 06:35:09 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWVUh-0003zX-FA
	for mip6@ietf.org; Wed, 28 Mar 2007 06:35:09 -0400
Received: OTM-MO(otm-mgo01) id l2SAZ2Xh029172;
	Wed, 28 Mar 2007 19:35:02 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2SAZ1FO010351;
	Wed, 28 Mar 2007 19:35:02 +0900 (JST)
Received: from [127.0.0.1] (jc-ssh00.iij.ad.jp [192.168.174.22])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2SAY6qL055818
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 28 Mar 2007 19:34:07 +0900 (JST)
In-Reply-To: <4607C3E9.2090000@gmail.com>
References: <1174404560.07.0.659815063549.issue94@mip4.org>
	<460005BE.4060306@gmail.com>
	<0F94C603-1A34-4BBE-B0EF-4A24BBC8189B@iijlab.net>
	<4607C3E9.2090000@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A7DF3AF3-A37E-4AA0-98B1-31161026CE2F@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 28 Mar 2007 19:35:01 +0900
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

On 2007/03/26, at 22:00, Alexandru Petrescu wrote:

> But should be done in tandem with that 'F' flag by HA.  One wouldnt  
> want the MN to request eg UDP encapsulation and the HA to force IP  
> encapsulation.

I think there is no such flag to force IP-in-IP encapsulation in the  
current text.  The only specified flag is to force the IP-in-UDP  
encapsulation flag, if I read the spec correctly.  So I think we  
don't need to worry about the above case you pointed out.


> I prefer the MN to decide which encapsulation method to use (and  
> not the HA).  However, the HA is the first to know whether there's  
> a NAT in between.  A MN doesn't know whether there's a NAT in  
> between, at the time it sends BU.

The protocol I expect is as follows.


Pattern 1) when MN doesn't have any preference

1-1) MN send a BU without any flag

1-2) HA receives the BU and checks if UDP encapsulation is necessary  
or not

1-3a) If UDP is necessary, the HA replies with a BA with the 'F' flag  
to force the MN to use UDP encapsulation

1-3b) If UDP is not necessary, the HA replies with a BA without any  
flag, that results in using IP-in-IP encapsulation


Pattern 2) when MN has UDP tunnel preference

2-1) MN sends a BU message with the newly defined flag (let's call it  
as the 'U' flag).

2-2) HA receives the BU and replies with a BA message with the 'F'  
flag to force UDP encapsulation, because the MN has requested UDP  
encapsulation mode.  There is no need to detect NATs.  The HA simply  
use UDP because the MN requests it.


The pattern 1 is the behavior specified in the current  
specification.  That is, the default tunneling mechanism is IP-in-IP,  
but UDP encapsulation is used when the HA detects its necessity.  All  
implementors can implement this way.

The pattern 2 is a new action introduced by the new flag.  This  
allows the MN to prefer the UDP encapsulation mode, with minimum spec  
changes.  What the HA need to do is simply to check the new flag  
(say, 'U' flag), and to reply with a BA message with the 'F' flag if  
an incoming BU message contains the 'U' flag.



> I've always thought there should be some form of tunnelling  
> parameters negotiation between MN and HA, before sending the  BU/ 
> BAck.  Also periodic heartbeats with re-negotiation if necessary.

I'm not sure what kind of tunneling parameters you are thinking  
about, but I prefer to reduce the number of tunneling mechanisms.  I  
want to provide less number of tunneling mechanisms, rather than to  
provide freedom to choose a tunneling mechanism from a number of  
various tunneling mechanisms.  It may make implementors confusing and  
may make interoperability more difficult.

Regards,
---
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 Wed Mar 28 08:12:31 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWWzp-00010n-SC; Wed, 28 Mar 2007 08:11:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWWzo-00010I-Od
	for mip6@ietf.org; Wed, 28 Mar 2007 08:11:20 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HWWzl-0003GN-At
	for mip6@ietf.org; Wed, 28 Mar 2007 08:11:20 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-15.tower-128.messagelabs.com!1175083876!5783231!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 25225 invoked from network); 28 Mar 2007 12:11:16 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-15.tower-128.messagelabs.com with SMTP;
	28 Mar 2007 12:11:16 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2SCBBQR000528;
	Wed, 28 Mar 2007 05:11:11 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l2SCBAwd008619;
	Wed, 28 Mar 2007 07:11:10 -0500 (CDT)
Message-ID: <460A5B55.1070206@gmail.com>
Date: Wed, 28 Mar 2007 14:11:01 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
References: <1174404560.07.0.659815063549.issue94@mip4.org>
	<460005BE.4060306@gmail.com>
	<0F94C603-1A34-4BBE-B0EF-4A24BBC8189B@iijlab.net>
	<4607C3E9.2090000@gmail.com>
	<A7DF3AF3-A37E-4AA0-98B1-31161026CE2F@iijlab.net>
In-Reply-To: <A7DF3AF3-A37E-4AA0-98B1-31161026CE2F@iijlab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
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

Keiichi SHIMA wrote:
> Hi,
> 
> On 2007/03/26, at 22:00, Alexandru Petrescu wrote:
> 
>> But should be done in tandem with that 'F' flag by HA.  One wouldnt
>>  want the MN to request eg UDP encapsulation and the HA to force IP
>>  encapsulation.
> 
> I think there is no such flag to force IP-in-IP encapsulation in the 
> current text.  The only specified flag is to force the IP-in-UDP 
> encapsulation flag, if I read the spec correctly.  So I think we 
> don't need to worry about the above case you pointed out.

I think that's right, 'F' flag forces UDP encapsulation, and I'm not
aware of a flag to force IP-in-IP encapsulation.

Remark there's an incoherency between rfc3519 and DS-MIPv6 with respect
to who sets that 'F' flag.  RFC3519 says MN sets it while DS-MIPv6 says
HA sets it.

rfc3519:
> 3.1 UDP Tunnel Request Extension
> 
> F                   F (Force) flag.  Indicates that the mobile node
> wants to force MIP UDP tunnelling to be established.

DS-MIPv6:
> If no NAT device was detected in the path between the mobile node and
>  the home agent then IPv6 packets are tunneled in an IPv4 header, 
> unless the home agent forces UDP encapsulation using the F flag.



>> I prefer the MN to decide which encapsulation method to use (and 
>> not the HA).  However, the HA is the first to know whether there's 
>> a NAT in between.  A MN doesn't know whether there's a NAT in 
>> between, at the time it sends BU.
> 
> The protocol I expect is as follows.
> 
> 
> Pattern 1) when MN doesn't have any preference
> 
> 1-1) MN send a BU without any flag
> 
> 1-2) HA receives the BU and checks if UDP encapsulation is necessary 
> or not
> 
> 1-3a) If UDP is necessary, the HA replies with a BA with the 'F' flag
>  to force the MN to use UDP encapsulation
> 
> 1-3b) If UDP is not necessary, the HA replies with a BA without any 
> flag, that results in using IP-in-IP encapsulation

Ok.

> Pattern 2) when MN has UDP tunnel preference
> 
> 2-1) MN sends a BU message with the newly defined flag (let's call it
>  as the 'U' flag).
> 
> 2-2) HA receives the BU and replies with a BA message with the 'F' 
> flag to force UDP encapsulation, because the MN has requested UDP 
> encapsulation mode.  There is no need to detect NATs.  The HA simply 
> use UDP because the MN requests it.

Ok.

> The pattern 1 is the behavior specified in the current specification.
>  That is, the default tunneling mechanism is IP-in-IP, but UDP 
> encapsulation is used when the HA detects its necessity.  All 
> implementors can implement this way.
> 
> The pattern 2 is a new action introduced by the new flag.  This 
> allows the MN to prefer the UDP encapsulation mode, with minimum spec
>  changes. What the HA need to do is simply to check the new flag
> (say, 'U' flag), and to reply with a BA message with the 'F' flag if
> an incoming BU message contains the 'U' flag.

Yes, provided we're clear of that 'F' flag.  As mentioned above, its
definition and use is different between rfc3519 and DS-MIPv6.

>> I've always thought there should be some form of tunnelling 
>> parameters negotiation between MN and HA, before sending the 
>> BU/BAck.  Also periodic heartbeats with re-negotiation if 
>> necessary.
> 
> I'm not sure what kind of tunneling parameters you are thinking 
> about, but I prefer to reduce the number of tunneling mechanisms.

Yes, I prefer to reduce the number of tunnelling mechanisms too.

If the UDP encapsulation is implemented as a virtual tunnel interface 
then that interface needs to have an IPv4 address on it.  That IPv4 
address can be the IPv4 address assigned on the real interface.  But 
this leads to having same IP address on two interfaces.  I think this is 
not good.

> I want to provide less number of tunneling mechanisms, rather than to
>  provide freedom to choose a tunneling mechanism from a number of 
> various tunneling mechanisms.  It may make implementors confusing and
>  may make interoperability more difficult.

I think a first implementation that prefers UDP for data encapsulation 
and signalling is a good idea.

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From mip6-bounces@ietf.org Wed Mar 28 09:56:35 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWYcf-0007Cp-12; Wed, 28 Mar 2007 09:55:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWYcc-0007Bo-V1
	for mip6@ietf.org; Wed, 28 Mar 2007 09:55:30 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWYcW-0007uZ-Qu
	for mip6@ietf.org; Wed, 28 Mar 2007 09:55:30 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 28 Mar 2007 06:55:25 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l2SDtOXL010041; 
	Wed, 28 Mar 2007 06:55:24 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l2SDsqAC028446;
	Wed, 28 Mar 2007 13:55:17 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 06:54:53 -0700
Received: from sgundavewxp ([10.32.246.211]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 06:54:52 -0700
From: "Sri Gundavelli" <sgundave@cisco.com>
To: "'Hesham Soliman'" <Hesham@elevatemobile.com>,
	"'Keiichi SHIMA'" <keiichi@iijlab.net>
References: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>
	<E1HWSfx-0006Fd-HX@megatron.ietf.org>
Subject: RE: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Date: Wed, 28 Mar 2007 06:54:53 -0700
Message-ID: <005901c77140$a94167b0$d3f6200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acdvp4ir24juDDX7T/W2EI/t8u6K5AAHI6bAAFGVW+AADNhnMA==
In-Reply-To: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-OriginalArrivalTime: 28 Mar 2007 13:54:52.0850 (UTC)
	FILETIME=[A8E0D120:01C77140]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2463; t=1175090124;
	x=1175954124; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:=20=22Sri=20Gundavelli=22=20<sgundave@cisco.com>
	|Subject:=20RE=3A=20[Mip6]=20concensus=20on=20[issue94]=20fixing=20encaps
	ulation=20mechanism=20inIPv4=20network |Sender:=20;
	bh=yPTTsVjN1lPF2ZQmK3MdbIjZJPoylV5R72/3q0ZwpAg=;
	b=NY/1YDbhY4d0ThjZuHBYU2gUm2oEXEPRxu6gf9Jw6FL+ARoCWiU/s+TaCmt9Spmie4tRQXya
	fSGWUXvhLi7XX+D84gNsGVyTwBt8FZWdFYguW8p3hoHG7iLtSN+RqreH;
Authentication-Results: sj-dkim-7; header.From=sgundave@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
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 prefer option "A". 

Reason:
>From the MIP4 experience, many times and for various reasons,
deployments choose UDP Tunneling even in the absence of NAT. The
ability for the client to hint that choice from any connected
network is important. I remember at least in one case, the UDP
tunneling was required by the client over satellite link, for some
reason, using RBSCP ..., there was no NAT in the path. So, the
negotiation logic in 3519 works quite well, IMO. We should probably
go with the same logic.



HA (Forced Accept)
==================
a.) NAT Present

Always enable UDP tunneling

b.) NAT not present

Enable UDP tunneling if the MN sets the bit



HA (Forced Reject)
==================

a.) NAT Present

Always enable UDP tunneling


b.) NAT not present

Do not accept UDP tunneling, even if the client requests it.


Besides the "U" bit in the request, the HA should have some
config policy on to accept "forced" UDP tunneling or not. So,
the final control can be given to the HA in the form of policy, 
but the client should be able to specify its preferences.


Sri



-----Original Message-----
From: Hesham Soliman [mailto:Hesham@elevatemobile.com] 
Sent: Wednesday, March 28, 2007 12:33 AM
To: 'Keiichi SHIMA'
Cc: mip6@ietf.org
Subject: [Mip6] concensus on [issue94] fixing encapsulation mechanism inIPv4
network

Kiichi, all, 

I think we've seen the different angles of this issue now and it's time to
close it. 
So I suggest that we choose one of the two options listed below. 

Folks, 

The "new" issue is about whether or not the MN can request one form of
tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
are:

A. Add a flag that allows the MN to request UDP tunnelling interface
(independently of the presence of a NAT) from the HA, when sending the BU.
The HA can override the MN's request. Or, 

B. Do nothing. I.e. the MN sends the BU as described in the spec today and
the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
IP. 

Please express your preference for one of the options above. Let's not make
things complicated and get into negotiating the tunnelling mechanism, one of
the two above will suffice. 

I'll leave it open till next Tuesday. 

Thanks,
Hesham



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

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



From mip6-bounces@ietf.org Wed Mar 28 09:58:41 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWYfd-00008b-7D; Wed, 28 Mar 2007 09:58:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWYfb-0008WU-Jd
	for mip6@ietf.org; Wed, 28 Mar 2007 09:58:35 -0400
Received: from omta05ps.mx.bigpond.com ([144.140.83.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWYfZ-0008R5-3S
	for mip6@ietf.org; Wed, 28 Mar 2007 09:58:35 -0400
Received: from oaamta05ps.mx.bigpond.com ([124.191.178.123])
	by omta05ps.mx.bigpond.com with ESMTP id
	<20070328135820.ZDR23363.omta05ps.mx.bigpond.com@oaamta05ps.mx.bigpond.com>;
	Wed, 28 Mar 2007 13:58:20 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta05ps.mx.bigpond.com
	with ESMTP
	id <20070328135819.FFWS14664.oaamta05ps.mx.bigpond.com@PC20005>;
	Wed, 28 Mar 2007 13:58:19 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Mip6 issue tracker'" <tracker-mip6@mip4.org>,
	<mip6@ietf.org>
Date: Wed, 28 Mar 2007 23:58:16 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdthSMURGWmZPbsQ+KWVHV73j689QDusETQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <1174679358.5.0.72020915846.issue95@mip4.org>
Message-Id: <20070328135819.FFWS14664.oaamta05ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 
Subject: [Mip6] Concensus on text for [issue95] Mention DHCPv6 based Home
	Agent discoverymechanism in section
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Folks,

This is a straighforward issue that needs a small editorial change. Please
see Kuntal's issue text and my suggestion below:

 > This issue has been discussed on the list. The current text 
 > in section 2.1 needs
 > to cover cases when DHCPv6 can be used to discover Home 
 > Agent information. The
 > email thread on this issue:
 > 
 > http://www1.ietf.org/mail-archive/web/mip6/current/msg05877.html
 > 
 > Proposed text:
 > -------------
 > Current:
 > 
 > "....If a mobile
 >    node is located in an IPv4-only foreign network, it cannot rely on
 >    native IPv6 routing. The preferred solution for 
 > discovering the home
 >    agent's IPv4 address is through the Domain Name System (DNS).
 > "
 > 
 > New:
 > 
 > If a mobile node is located in an IPv4-only foreign network, 
 > it cannot rely on
 >    native IPv6 routing. In this scenario, the solution for 
 > discovering the home
 > agent's IPv4 address is through the Domain Name System (DNS).
 > 
 > Also add the following in this section:
 > 
 > If the MN is attached to an IPv6-only or it is attached to 
 > an IPv6 and IPv4 Dual
 > stack foreign network, it shall use procedures defined in
 > draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt [add 
 > this reference] to
 > discover Home Agent information.


I suggest modifying the text above to:

If a mobile node is located in an IPv4-only foreign network, 
it cannot rely on native IPv6 routing. In this scenario, the solution for 
discovering the home agent's IPv4 address is through the Domain Name System
(DNS). If the MN is attached to an IPv6-only or dual stack network, it may
also use procedures defined in [INTBOOT] to discover Home Agent information.
Note that the use of [INTBOOT] cannot give the mobile node information that
allows it to continue to communicate with the Home Agent if, for example,
the mobile node moved from an IPv6-enabled network to an IPv4-only network.
In such scenario, the mobile node would need to discover the IPv4 address of
its home agent through the DNS. 



[INTBOOT] draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt


I think it's important to make sure that the consequences of the choice are
clear to the implementer, that's why I added the last two sentences.




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



From mip6-bounces@ietf.org Wed Mar 28 10:13:13 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWYsz-0003Ba-Ba; Wed, 28 Mar 2007 10:12:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWYsx-0003BV-TE
	for mip6@ietf.org; Wed, 28 Mar 2007 10:12:23 -0400
Received: from vms040pub.verizon.net ([206.46.252.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWYsw-0002ih-KN
	for mip6@ietf.org; Wed, 28 Mar 2007 10:12:23 -0400
Received: from vms076.mailsrvcs.net ([192.168.1.2])
	by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JFM008GKA4G4Y05@vms040.mailsrvcs.net> for
	mip6@ietf.org; Wed, 28 Mar 2007 09:12:18 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms076.mailsrvcs.net (Verizon Webmail) with HTTP; Wed,
	28 Mar 2007 09:12:16 -0500 (CDT)
Date: Wed, 28 Mar 2007 09:12:16 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism in
	IPv4 network
X-Originating-IP: [129.55.200.20]
To: Hesham Soliman <Hesham@elevatemobile.com>,
	'Keiichi SHIMA' <keiichi@iijlab.net>
Message-id: <18663842.5386911175091136916.JavaMail.root@vms076.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.5 (/)
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>
Errors-To: mip6-bounces@ietf.org

I also prefer option 'A'.

>From: Hesham Soliman <Hesham@elevatemobile.com>
>Date: 2007/03/28 Wed AM 02:33:25 CDT
>To: 'Keiichi SHIMA' <keiichi@iijlab.net>
>Cc: mip6@ietf.org
>Subject: [Mip6] concensus on [issue94] fixing encapsulation mechanism in	IPv4 network

>Kiichi, all, 
>
>I think we've seen the different angles of this issue now and it's time to
>close it. 
>So I suggest that we choose one of the two options listed below. 
>
>Folks, 
>
>The "new" issue is about whether or not the MN can request one form of
>tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
>are:
>
>A. Add a flag that allows the MN to request UDP tunnelling interface
>(independently of the presence of a NAT) from the HA, when sending the BU.
>The HA can override the MN's request. Or, 
>
>B. Do nothing. I.e. the MN sends the BU as described in the spec today and
>the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
>IP. 
>
>Please express your preference for one of the options above. Let's not make
>things complicated and get into negotiating the tunnelling mechanism, one of
>the two above will suffice. 
>
>I'll leave it open till next Tuesday. 
>
>Thanks,
>Hesham
>
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Mar 28 10:21:39 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWZ1c-0004lP-Pz; Wed, 28 Mar 2007 10:21:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZ1b-0004lK-Cp
	for mip6@ietf.org; Wed, 28 Mar 2007 10:21:19 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZ1Y-0003j2-MF
	for mip6@ietf.org; Wed, 28 Mar 2007 10:21:19 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 28 Mar 2007 16:21:16 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l2SELFut018079; 
	Wed, 28 Mar 2007 16:21:15 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2SEL9lZ002718; 
	Wed, 28 Mar 2007 14:21:10 GMT
Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 16:21:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Date: Wed, 28 Mar 2007 16:19:35 +0200
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC01182506@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Thread-Index: AcdxQ0SPNblk/GeUSLq0zXxOwY/u1wAANfXY
References: <18663842.5386911175091136916.JavaMail.root@vms076.mailsrvcs.net>
From: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
To: "Tim Enos" <timbeck04@verizon.net>,
	"Hesham Soliman" <Hesham@elevatemobile.com>,
	"Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 28 Mar 2007 14:21:09.0614 (UTC)
	FILETIME=[54B3E8E0:01C77144]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5791; t=1175091675;
	x=1175955675; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pthubert@cisco.com;
	z=From:=20=22Pascal=20Thubert=20\(pthubert\)=22=20<pthubert@cisco.com>
	|Subject:=20RE=3A=20[Mip6]=20concensus=20on=20[issue94]=20fixing=20encaps
	ulation=20mechanism=20inIPv4=20network |Sender:=20;
	bh=hVbz1FMZFjzg4zFnqfLO+btO2b58Buzpx0OhROU0e+s=;
	b=eyjDLqSpvxGmf2NQtLIFPayHaeZk2iHIPtGVPWLV1bALzOPjFpcmVTETvb3pBf4kstcB+vMc
	CRnCP/QygsQIH1TWNzLLeEoE3bsorpg5jc/fTpWrhUGuGK2f2PWybA0N;
Authentication-Results: ams-dkim-2; header.From=pthubert@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1602625264=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1602625264==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77144.548AA2B0"

This is a multi-part message in MIME format.

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

Same here, A. It's more open. Seems to me that if the MN demands it, the =
HA should not refuse...=20
This would enable a simpler MN implementation that does UDP all the =
time.
=20
Pascal

________________________________

From: Tim Enos [mailto:timbeck04@verizon.net]
Sent: Wed 3/28/2007 3:12 PM
To: Hesham Soliman; 'Keiichi SHIMA'
Cc: mip6@ietf.org
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation =
mechanism inIPv4 network



I also prefer option 'A'.

>From: Hesham Soliman <Hesham@elevatemobile.com>
>Date: 2007/03/28 Wed AM 02:33:25 CDT
>To: 'Keiichi SHIMA' <keiichi@iijlab.net>
>Cc: mip6@ietf.org
>Subject: [Mip6] concensus on [issue94] fixing encapsulation mechanism =
in       IPv4 network

>Kiichi, all,
>
>I think we've seen the different angles of this issue now and it's time =
to
>close it.
>So I suggest that we choose one of the two options listed below.
>
>Folks,
>
>The "new" issue is about whether or not the MN can request one form of
>tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we =
have
>are:
>
>A. Add a flag that allows the MN to request UDP tunnelling interface
>(independently of the presence of a NAT) from the HA, when sending the =
BU.
>The HA can override the MN's request. Or,
>
>B. Do nothing. I.e. the MN sends the BU as described in the spec today =
and
>the HA tells the MN in the BA whether it should use UDP tunnelling or =
IP in
>IP.
>
>Please express your preference for one of the options above. Let's not =
make
>things complicated and get into negotiating the tunnelling mechanism, =
one of
>the two above will suffice.
>
>I'll leave it open till next Tuesday.
>
>Thanks,
>Hesham
>
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6


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



------_=_NextPart_001_01C77144.548AA2B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">=0A=
<TITLE>Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism =
inIPv4 network</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText8604 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Same here, A. =
It's more open. =0A=
Seems to me that if the MN demands it, the HA should not refuse... =
</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>This would =
enable a simpler =0A=
MN implementation that does UDP all the time.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Pascal</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Tim Enos =0A=
[mailto:timbeck04@verizon.net]<BR><B>Sent:</B> Wed 3/28/2007 3:12 =0A=
PM<BR><B>To:</B> Hesham Soliman; 'Keiichi SHIMA'<BR><B>Cc:</B> =0A=
mip6@ietf.org<BR><B>Subject:</B> Re: [Mip6] concensus on [issue94] =
fixing =0A=
encapsulation mechanism inIPv4 network<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I also prefer option 'A'.<BR><BR>&gt;From: Hesham =
Soliman =0A=
&lt;Hesham@elevatemobile.com&gt;<BR>&gt;Date: 2007/03/28 Wed AM 02:33:25 =0A=
CDT<BR>&gt;To: 'Keiichi SHIMA' &lt;keiichi@iijlab.net&gt;<BR>&gt;Cc: =0A=
mip6@ietf.org<BR>&gt;Subject: [Mip6] concensus on [issue94] fixing =
encapsulation =0A=
mechanism in&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv4 =
network<BR><BR>&gt;Kiichi, =0A=
all,<BR>&gt;<BR>&gt;I think we've seen the different angles of this =
issue now =0A=
and it's time to<BR>&gt;close it.<BR>&gt;So I suggest that we choose one =
of the =0A=
two options listed below.<BR>&gt;<BR>&gt;Folks,<BR>&gt;<BR>&gt;The "new" =
issue =0A=
is about whether or not the MN can request one form of<BR>&gt;tunnelling =
(i.e. =0A=
UDP) when sending a BU to the HA. The two choices we =0A=
have<BR>&gt;are:<BR>&gt;<BR>&gt;A. Add a flag that allows the MN to =
request UDP =0A=
tunnelling interface<BR>&gt;(independently of the presence of a NAT) =
from the =0A=
HA, when sending the BU.<BR>&gt;The HA can override the MN's request. =0A=
Or,<BR>&gt;<BR>&gt;B. Do nothing. I.e. the MN sends the BU as described =
in the =0A=
spec today and<BR>&gt;the HA tells the MN in the BA whether it should =
use UDP =0A=
tunnelling or IP in<BR>&gt;IP.<BR>&gt;<BR>&gt;Please express your =
preference for =0A=
one of the options above. Let's not make<BR>&gt;things complicated and =
get into =0A=
negotiating the tunnelling mechanism, one of<BR>&gt;the two above will =0A=
suffice.<BR>&gt;<BR>&gt;I'll leave it open till next =0A=
Tuesday.<BR>&gt;<BR>&gt;Thanks,<BR>&gt;Hesham<BR>&gt;<BR>&gt;<BR>&gt;<BR>=
&gt;_______________________________________________<BR>&gt;Mip6 =0A=
mailing list<BR>&gt;Mip6@ietf.org<BR>&gt;<A =0A=
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR><BR><BR>__________________________________=
_____________<BR>Mip6 =0A=
mailing list<BR>Mip6@ietf.org<BR><A =0A=
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C77144.548AA2B0--


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

--===============1602625264==--




From mip6-bounces@ietf.org Wed Mar 28 10:32:33 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWZBq-0002uc-Vg; Wed, 28 Mar 2007 10:31:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZBp-0002uW-HV
	for mip6@ietf.org; Wed, 28 Mar 2007 10:31:53 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZBd-0005Pr-Cs
	for mip6@ietf.org; Wed, 28 Mar 2007 10:31:53 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 07:31:40 -0700
Message-ID: <460A7C4C.7060503@azairenet.com>
Date: Wed, 28 Mar 2007 07:31:40 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
References: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>	<E1HWSfx-0006Fd-HX@megatron.ietf.org>
	<005901c77140$a94167b0$d3f6200a@amer.cisco.com>
In-Reply-To: <005901c77140$a94167b0$d3f6200a@amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 14:31:40.0461 (UTC)
	FILETIME=[CCB785D0:01C77145]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Sri Gundavelli wrote:
> I prefer option "A". 
> 
> Reason:
>>From the MIP4 experience, many times and for various reasons,
> deployments choose UDP Tunneling even in the absence of NAT. The
> ability for the client to hint that choice from any connected
> network is important. 

The problem is that the client may not know. It might be
setting the flag all the time. Do we have a mechanism to
say when the MN should be setting this bit?

> Besides the "U" bit in the request, the HA should have some
> config policy on to accept "forced" UDP tunneling or not. 

Agree on this.

Vijay

So,
> the final control can be given to the HA in the form of policy, 
> but the client should be able to specify its preferences.
> 
> 
> Sri
> 
> 
> 
> -----Original Message-----
> From: Hesham Soliman [mailto:Hesham@elevatemobile.com] 
> Sent: Wednesday, March 28, 2007 12:33 AM
> To: 'Keiichi SHIMA'
> Cc: mip6@ietf.org
> Subject: [Mip6] concensus on [issue94] fixing encapsulation mechanism inIPv4
> network
> 
> Kiichi, all, 
> 
> I think we've seen the different angles of this issue now and it's time to
> close it. 
> So I suggest that we choose one of the two options listed below. 
> 
> Folks, 
> 
> The "new" issue is about whether or not the MN can request one form of
> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
> are:
> 
> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending the BU.
> The HA can override the MN's request. Or, 
> 
> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
> IP. 
> 
> Please express your preference for one of the options above. Let's not make
> things complicated and get into negotiating the tunnelling mechanism, one of
> the two above will suffice. 
> 
> I'll leave it open till next Tuesday. 
> 
> Thanks,
> Hesham
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Mar 28 10:38:07 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWZHo-0004LX-Oj; Wed, 28 Mar 2007 10:38:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZHl-0004L7-U8
	for mip6@ietf.org; Wed, 28 Mar 2007 10:38:01 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZHk-0006rk-Ix
	for mip6@ietf.org; Wed, 28 Mar 2007 10:38:01 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 07:37:59 -0700
Message-ID: <460A7DC9.4060207@azairenet.com>
Date: Wed, 28 Mar 2007 07:38:01 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] Concensus on text for [issue95] Mention DHCPv6 based Home
	Agent discoverymechanism in section
References: <20070328135819.FFWS14664.oaamta05ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070328135819.FFWS14664.oaamta05ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 14:37:59.0769 (UTC)
	FILETIME=[AECD5490:01C77146]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, 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

Hesham Soliman wrote:

> I suggest modifying the text above to:
> 
> If a mobile node is located in an IPv4-only foreign network, 
> it cannot rely on native IPv6 routing. In this scenario, the solution for 
> discovering the home agent's IPv4 address is through the Domain Name System
> (DNS). If the MN is attached to an IPv6-only or dual stack network, it may
> also use procedures defined in [INTBOOT] to discover Home Agent information.
> Note that the use of [INTBOOT] cannot give the mobile node information that
> allows it to continue to communicate with the Home Agent if, for example,
> the mobile node moved from an IPv6-enabled network to an IPv4-only network.

This is kind of odd since [INTBOOT] today cannot return the
IPv4 address of the HA. So you end up using DNS all the time.
But I can live with it with the following modification.

    Note that the use of [INTBOOT] cannot give the mobile node
    information that allows it to continue to communicate with the
    Home Agent if, for example, the mobile node moved from an
    IPv6-enabled network to an IPv4-only network or the extensions
    required to return the IPv4 address of the home agent are not
    available.

> In such scenario, the mobile node would need to discover the IPv4 address of
> its home agent through the DNS. 

So the new paragraph would be

    If a mobile node is located in an IPv4-only foreign network, it
    cannot rely on native IPv6 routing. In this scenario, the solution
    for discovering the home agent's IPv4 address is through the Domain
    Name System (DNS). If the MN is attached to an IPv6-only or dual
    stack network, it may also use procedures defined in [INTBOOT] to
    discover Home Agent information. Note that the use of [INTBOOT]
    cannot give the mobile node information that allows it to continue to
    communicate with the Home Agent if, for example, the mobile node
    moved from an IPv6-enabled network to an IPv4-only network or the
    extensions required to return the IPv4 address of the home agent are
    not available. In such scenario, the mobile node would need to
    discover the IPv4 address of its home agent through the DNS.

Vijay

> 
> 
> 
> [INTBOOT] draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt
> 
> 
> I think it's important to make sure that the consequences of the choice are
> clear to the implementer, that's why I added the last two sentences.
> 
> 
> 
> 
> _______________________________________________
> 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 Mar 28 10:39:58 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWZJS-0004wW-IM; Wed, 28 Mar 2007 10:39:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZJS-0004wR-09
	for mip6@ietf.org; Wed, 28 Mar 2007 10:39:46 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZJP-0007Kf-MG
	for mip6@ietf.org; Wed, 28 Mar 2007 10:39:45 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 28 Mar 2007 07:39:43 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l2SEdg8S001983; 
	Wed, 28 Mar 2007 07:39:42 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l2SEdaxB000309;
	Wed, 28 Mar 2007 14:39:42 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 07:39:42 -0700
Received: from sgundavewxp ([10.32.246.211]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 07:39:41 -0700
From: "Sri Gundavelli" <sgundave@cisco.com>
To: "'Vijay Devarapalli'" <vijay.devarapalli@AzaireNet.com>
References: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>	<E1HWSfx-0006Fd-HX@megatron.ietf.org>
	<005901c77140$a94167b0$d3f6200a@amer.cisco.com>
	<460A7C4C.7060503@azairenet.com>
Subject: RE: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Date: Wed, 28 Mar 2007 07:39:42 -0700
Message-ID: <006101c77146$ec113ab0$d3f6200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcdxRc0JhR05H9TRTkOj0p1sM9dyqQAACk4g
In-Reply-To: <460A7C4C.7060503@azairenet.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-OriginalArrivalTime: 28 Mar 2007 14:39:41.0660 (UTC)
	FILETIME=[EB88A9C0:01C77146]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1149; t=1175092782;
	x=1175956782; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:=20=22Sri=20Gundavelli=22=20<sgundave@cisco.com>
	|Subject:=20RE=3A=20[Mip6]=20concensus=20on=20[issue94]=20fixing=20encaps
	ulation=20mechanism=20inIPv4=20network |Sender:=20;
	bh=BWFOUMAQJtdj+4jd4E2OlfRi2tvpD2dfCqPgj8MlLYI=;
	b=HlDP2Ob+r/yz5WbVGVStYEKvzt0n6npcTLmslb0GQy9bE0DULtDqcP46VC819rdAcwwnyUWk
	kY6pgSTtyYFK4ubepv93PwLE27HFeR9LTERTirue27M3yBaIrv0zTUXV;
Authentication-Results: sj-dkim-5; header.From=sgundave@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 

-----Original Message-----
From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
Sent: Wednesday, March 28, 2007 7:32 AM
To: Sri Gundavelli
Cc: 'Hesham Soliman'; 'Keiichi SHIMA'; mip6@ietf.org
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
inIPv4 network

>> Reason:
>>From the MIP4 experience, many times and for various reasons,
>> deployments choose UDP Tunneling even in the absence of NAT. The
>> ability for the client to hint that choice from any connected
>> network is important. 

>The problem is that the client may not know. It might be
>setting the flag all the time. Do we have a mechanism to
>say when the MN should be setting this bit?

The preference comes from the type of connected access network
and other characteristics local to that network. So, the mobile
node is in a better position to make that choice. Off course,
the home agent always has the final say, in the form of configured
policy. 

But, sure, the logic as when to enable this on the mobile is
difficult. Mostly, it might be an operator initiated explicit
setting, on a need basis.
 

Sri

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



From mip6-bounces@ietf.org Wed Mar 28 10:45:33 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWZP3-0000tO-K2; Wed, 28 Mar 2007 10:45:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZP2-0000t8-OU
	for mip6@ietf.org; Wed, 28 Mar 2007 10:45:32 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZOx-0000B2-QR
	for mip6@ietf.org; Wed, 28 Mar 2007 10:45:32 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 07:45:26 -0700
Message-ID: <460A7F83.5020909@azairenet.com>
Date: Wed, 28 Mar 2007 07:45:23 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
References: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>	<E1HWSfx-0006Fd-HX@megatron.ietf.org>
	<005901c77140$a94167b0$d3f6200a@amer.cisco.com>
	<460A7C4C.7060503@azairenet.com>
	<006101c77146$ec113ab0$d3f6200a@amer.cisco.com>
In-Reply-To: <006101c77146$ec113ab0$d3f6200a@amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 14:45:27.0026 (UTC)
	FILETIME=[B9635520:01C77147]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Sri Gundavelli wrote:
>  
> 
> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
> Sent: Wednesday, March 28, 2007 7:32 AM
> To: Sri Gundavelli
> Cc: 'Hesham Soliman'; 'Keiichi SHIMA'; mip6@ietf.org
> Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
> inIPv4 network
> 
>>> Reason:
>> >From the MIP4 experience, many times and for various reasons,
>>> deployments choose UDP Tunneling even in the absence of NAT. The
>>> ability for the client to hint that choice from any connected
>>> network is important. 
> 
>> The problem is that the client may not know. It might be
>> setting the flag all the time. Do we have a mechanism to
>> say when the MN should be setting this bit?
> 
> The preference comes from the type of connected access network
> and other characteristics local to that network. So, the mobile
> node is in a better position to make that choice. Off course,
> the home agent always has the final say, in the form of configured
> policy. 

So can we then add a sentence saying

   It is recommended that the mobile node SHOULD NOT set the 'U'
   flag by default, since using UDP encapsulation when not
   required introduces an unnecessary overhead for all data traffic. :)

My preference is still for 'B' though.

Vijay

> 
> But, sure, the logic as when to enable this on the mobile is
> difficult. Mostly, it might be an operator initiated explicit
> setting, on a need basis.
>  
> 
> Sri


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



From mip6-bounces@ietf.org Wed Mar 28 10:48:13 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWZRT-0001yg-1g; Wed, 28 Mar 2007 10:48:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZRS-0001yT-0j
	for mip6@ietf.org; Wed, 28 Mar 2007 10:48:02 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZRQ-0000pu-Mr
	for mip6@ietf.org; Wed, 28 Mar 2007 10:48:02 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l2SElwF04748 for <mip6@ietf.org>; Wed, 28 Mar 2007 14:47:58 GMT
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] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
Date: Wed, 28 Mar 2007 09:47:52 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F6A6B@zrc2hxm2.corp.nortel.com>
In-Reply-To: <58357EDC7884E24BAD684C1B2D91F96D0535D0A7@trebe101.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	inIPv4 network
thread-index: Acdvp4ir24juDDX7T/W2EI/t8u6K5AAHI6bAAFGVW+AAAQG5cAAOUAIw
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 believe we should do the following:

1- MN should be able to set a request for UDP tunneling.
2- the default behavior for MN is not to set the request.
3- The HA should be able to accept or reject.


>Folks,
>
>The "new" issue is about whether or not the MN can request one
>form of tunnelling (i.e. UDP) when sending a BU to the HA. The=20
>two choices we have
>are:
>
>A. Add a flag that allows the MN to request UDP tunnelling
>interface (independently of the presence of a NAT) from the=20
>HA, when sending the BU.
>The HA can override the MN's request. Or,=20
>
>B. Do nothing. I.e. the MN sends the BU as described in the
>spec today and the HA tells the MN in the BA whether it should=20
>use UDP tunnelling or IP in IP.=20
>
>Please express your preference for one of the options above.
>Let's not make things complicated and get into negotiating the=20
>tunnelling mechanism, one of the two above will suffice.=20
>
>I'll leave it open till next Tuesday.
>
>Thanks,
>Hesham
>
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6
>

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

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



From mip6-bounces@ietf.org Wed Mar 28 12:51:20 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWbLg-0006r8-8H; Wed, 28 Mar 2007 12:50:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWbLe-0006r2-Oc
	for mip6@ietf.org; Wed, 28 Mar 2007 12:50:10 -0400
Received: from av7-2-sn3.vrr.skanova.net ([81.228.9.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWbLc-0008BE-8B
	for mip6@ietf.org; Wed, 28 Mar 2007 12:50:10 -0400
Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 353143887B; Wed, 28 Mar 2007 18:49:32 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id E71AF386A6; Wed, 28 Mar 2007 18:49:31 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id B795B37E49;
	Wed, 28 Mar 2007 18:50:05 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HWbLZ-0000pr-CD; Wed, 28 Mar 2007 18:50:05 +0200
Message-ID: <460A9CC1.7070508@levkowetz.com>
Date: Wed, 28 Mar 2007 18:50:09 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <E1HWSfx-0006Fd-HX@megatron.ietf.org>
	<460A39D9.4090201@azairenet.com>
In-Reply-To: <460A39D9.4090201@azairenet.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vijay.devarapalli@azairenet.com, Hesham@elevatemobile.com,
	mip6@ietf.org, keiichi@iijlab.net, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay

on 2007-03-28 11:48 Vijay Devarapalli said the following:
> I prefer option 'B'.
> 
> The MN doesn't really know if there is a NAT on the path. It also
> does not know if there is a firewall in the path blocking IP-in-IP
> packets. Since it does not know any of this, I am afraid many
> mobile node implementations will always be setting this flag. Then,
> if the HA is allowed to override this, then aren't we basically
> saying HA decides whether the MN should use UDP tunneling or not?
> This means option 'B' is what is being used to decide whether UDP
> tunneling is used or not.
> 
> What am I missing?

HA override should not be a dynamic thing, rather a matter of whether
UDP tunnelling is configured as permitted on the HA at all.

Having the UDP tunnelling request flag makes it possible for a client
to detect an anomalous situation and try to fall back to UDP tunnelling
if IP-in-IP just doesn't work.  Not having the flag deprives the system
of this fallback option.

In MIPv4 we've repeatedly seen that it's useful to have this flag.


	Henrik

> Vijay
> 
> Hesham Soliman wrote:
>> Kiichi, all, 
>> 
>> I think we've seen the different angles of this issue now and it's time to
>> close it. 
>> So I suggest that we choose one of the two options listed below. 
>> 
>> Folks, 
>> 
>> The "new" issue is about whether or not the MN can request one form of
>> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
>> are:
>> 
>> A. Add a flag that allows the MN to request UDP tunnelling interface
>> (independently of the presence of a NAT) from the HA, when sending the BU.
>> The HA can override the MN's request. Or, 
>> 
>> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
>> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
>> IP. 
>> 
>> Please express your preference for one of the options above. Let's not make
>> things complicated and get into negotiating the tunnelling mechanism, one of
>> the two above will suffice. 
>> 
>> I'll leave it open till next Tuesday. 
>> 
>> Thanks,
>> Hesham
>> 
>> 
>> 
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 

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



From mip6-bounces@ietf.org Wed Mar 28 12:55:42 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWbQv-0001h1-5W; Wed, 28 Mar 2007 12:55:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWbQt-0001g0-Nw
	for mip6@ietf.org; Wed, 28 Mar 2007 12:55:35 -0400
Received: from av10-2-sn2.hy.skanova.net ([81.228.8.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWbOx-0000ad-GP
	for mip6@ietf.org; Wed, 28 Mar 2007 12:53:38 -0400
Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 9897839389; Wed, 28 Mar 2007 18:53:30 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 7D44F380F9; Wed, 28 Mar 2007 18:53:30 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id EB37E37E54;
	Wed, 28 Mar 2007 18:53:29 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HWbOq-0000zY-RO; Wed, 28 Mar 2007 18:53:28 +0200
Message-ID: <460A9D8D.2010302@levkowetz.com>
Date: Wed, 28 Mar 2007 18:53:33 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
In-Reply-To: <3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: keiichi@iijlab.net, Hesham@elevatemobile.com, mip6@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: 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 2007-03-28 12:06 Keiichi SHIMA said the following:
> Hello Hesham,
> 
> I think the text explaining the option 'A' is not exactly what I  
> proposed in my previous mail.  Please let me clarify the text about  
> the option 'A'.
> 
> 
> On 2007/03/28, at 16:33, Hesham Soliman wrote:
> 
>> A. Add a flag that allows the MN to request UDP tunnelling interface
>> (independently of the presence of a NAT) from the HA, when sending  
>> the BU.
>> The HA can override the MN's request. Or,
> 
> The idea is to introduce a new flag for MN to request the UDP tunnel  
> mode.  Let's call it as the 'U (requesting UDP tunnel)' flag.  If the  
> MN doesn't specify the 'U' flag, the behavior is exactly the same as  
> the current specification.  The HA can decide what kind of tunneling  
> mechanism (IP-in-IP or UDP-in-IP).
> 
> When the MN sets the 'U' flag on, the HA always replies with the 'F  
> (Force UDP tunnel)' flag.  This is a new behavior what I want to  
> propose.
> 
> The HA shouldn't override the 'U' flag.  If we allow overriding the  
> 'U' flag, then there is no difference between the option 'A' and 'B'.

Umm.  

I hope we're not in "Not Invented Here" mode.

Is there any reason to deviate from the specification of this flag,
and the way the HA handles it, which is given in the MIPv4 NAT traversal
specification?

See http://tools.ietf.org/html/rfc3519#section-3.1.1


	Henrik


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



From mip6-bounces@ietf.org Wed Mar 28 12:55:44 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWbQr-0001fJ-F0; Wed, 28 Mar 2007 12:55:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWbQo-0001dF-Jd
	for mip6@ietf.org; Wed, 28 Mar 2007 12:55:30 -0400
Received: from av8-1-sn3.vrr.skanova.net ([81.228.9.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWbPs-00013s-HH
	for mip6@ietf.org; Wed, 28 Mar 2007 12:54:37 -0400
Received: by av8-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id C16F038648; Wed, 28 Mar 2007 18:54:31 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av8-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 87C85382A3; Wed, 28 Mar 2007 18:54:31 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 7393537E42;
	Wed, 28 Mar 2007 18:54:31 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HWbPr-00011F-08; Wed, 28 Mar 2007 18:54:31 +0200
Message-ID: <460A9DCB.9050502@levkowetz.com>
Date: Wed, 28 Mar 2007 18:54:35 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip6] RE: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <E1HWV9s-0006uo-QB@megatron.ietf.org>
In-Reply-To: <E1HWV9s-0006uo-QB@megatron.ietf.org>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: Hesham@elevatemobile.com, keiichi@iijlab.net, mip6@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: mip6@ietf.org, 'Keiichi SHIMA' <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



on 2007-03-28 12:13 Hesham Soliman said the following:
>> The idea is to introduce a new flag for MN to request the 
>> UDP tunnel  
>> mode.  Let's call it as the 'U (requesting UDP tunnel)' 
>> flag.  If the  
>> MN doesn't specify the 'U' flag, the behavior is exactly the 
>> same as  
>> the current specification.  The HA can decide what kind of 
>> tunneling  
>> mechanism (IP-in-IP or UDP-in-IP).
>> 
>> When the MN sets the 'U' flag on, the HA always replies with the 'F  
>> (Force UDP tunnel)' flag.  This is a new behavior what I want to  
>> propose.
>> 
>> The HA shouldn't override the 'U' flag.  If we allow overriding the  
>> 'U' flag, then there is no difference between the option 'A' and 'B'.
> 
> There is a difference between A and B of course. The difference is that
> in B the MN can't request anything and is either told to use UDP or told to
> use IP in IP. In A, the MN can request UDP tunnels. Like any other request
> in MIPv6 (e.g. BU lifetime, HoA ....etc) the HA always has the upper hand
> and decides whether the request is acceptable or not. I simply followed the
> same rule here. For instance, the HA/MAP might think UDP tunnelling is not
> acceptable for policy reasons (e.g. an operator doesn't want the MN to waste
> BW when UDP is not needed). I don't have an exhaustive list of scenarios so
> I just erred on the conservative side of keeping with the current approach
> in MIPv6. 

Right.  

This explanation matches http://tools.ietf.org/html/rfc3519#section-3.1.1


	Henrik

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



From mip6-bounces@ietf.org Wed Mar 28 13:06:45 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWbb3-0006SQ-VU; Wed, 28 Mar 2007 13:06:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWbb2-0006SF-Lz
	for mip6@ietf.org; Wed, 28 Mar 2007 13:06:04 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWbb1-0003q9-4o
	for mip6@ietf.org; Wed, 28 Mar 2007 13:06:04 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l2SH5lSw030193; Wed, 28 Mar 2007 20:05:51 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 20:05:40 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Mar 2007 12:05:37 -0500
Received: from 172.19.244.111 ([172.19.244.111]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 28 Mar 2007 17:05:37 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 28 Mar 2007 12:05:48 -0500
Subject: Re: [Mip6] Concensus on text for [issue95] Mention DHCPv6 based
	Home Agent discoverymechanism in section
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>,
	Hesham Soliman <Hesham@elevatemobile.com>
Message-ID: <C2300A9C.329F2%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Concensus on text for [issue95] Mention DHCPv6 based
	Home Agent discoverymechanism in section
Thread-Index: AcdxW1Stk4dtCt1OEdueggARJNUNiA==
In-Reply-To: <460A7DC9.4060207@azairenet.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 17:05:37.0758 (UTC)
	FILETIME=[4E932FE0:01C7715B]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070328200552-74665BB0-2B6D4C8D/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 'Mip6 issue tracker' <tracker-mip6@mip4.org>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


I am fine with the proposed text in this email (by Vijay). We can close it
if this is acceptable.

-Raj


On 3/28/07 9:38 AM, "ext Vijay Devarapalli"
<vijay.devarapalli@azairenet.com> wrote:

~snip~

> 
> So the new paragraph would be
> 
>     If a mobile node is located in an IPv4-only foreign network, it
>     cannot rely on native IPv6 routing. In this scenario, the solution
>     for discovering the home agent's IPv4 address is through the Domain
>     Name System (DNS). If the MN is attached to an IPv6-only or dual
>     stack network, it may also use procedures defined in [INTBOOT] to
>     discover Home Agent information. Note that the use of [INTBOOT]
>     cannot give the mobile node information that allows it to continue to
>     communicate with the Home Agent if, for example, the mobile node
>     moved from an IPv6-enabled network to an IPv4-only network or the
>     extensions required to return the IPv4 address of the home agent are
>     not available. In such scenario, the mobile node would need to
>     discover the IPv4 address of its home agent through the DNS.
> 
> Vijay
> 


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



From mip6-bounces@ietf.org Thu Mar 29 01:21:43 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWn30-0003on-1a; Thu, 29 Mar 2007 01:19:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWn2y-0003l5-3R
	for mip6@ietf.org; Thu, 29 Mar 2007 01:19:40 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWn2w-0003Yy-HA
	for mip6@ietf.org; Thu, 29 Mar 2007 01:19:40 -0400
Received: OTM-MO(otm-mgo01) id l2T5GQSH067351;
	Thu, 29 Mar 2007 14:16:26 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2T5GQn3056125;
	Thu, 29 Mar 2007 14:16:26 +0900 (JST)
Received: from [127.0.0.1] (keiichi00-4.osaka.iij.ad.jp [192.168.64.45])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2T5FT1e063761
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 29 Mar 2007 14:15:30 +0900 (JST)
In-Reply-To: <460A4448.1050507@azairenet.com>
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
	<460A4448.1050507@azairenet.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E36633CF-97CE-49C8-A69F-F957925D40B6@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
Date: Thu, 29 Mar 2007 14:16:25 +0900
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello,


On 2007/03/28, at 19:32, Vijay Devarapalli wrote:

> Keiichi SHIMA wrote:
>> Hello Hesham,
>> I think the text explaining the option 'A' is not exactly what I  
>> proposed in my previous mail.  Please let me clarify the text  
>> about the option 'A'.
>> On 2007/03/28, at 16:33, Hesham Soliman wrote:
>>> A. Add a flag that allows the MN to request UDP tunnelling interface
>>> (independently of the presence of a NAT) from the HA, when  
>>> sending the BU.
>>> The HA can override the MN's request. Or,
>> The idea is to introduce a new flag for MN to request the UDP  
>> tunnel mode.  Let's call it as the 'U (requesting UDP tunnel)'  
>> flag.  If the MN doesn't specify the 'U' flag, the behavior is  
>> exactly the same as the current specification.  The HA can decide  
>> what kind of tunneling mechanism (IP-in-IP or UDP-in-IP).
>> When the MN sets the 'U' flag on, the HA always replies with the  
>> 'F (Force UDP tunnel)' flag.  This is a new behavior what I want  
>> to propose.
>
> We would also need to mention when the MN would be setting this
> flag. Is it when it wants to use UDP encapsulation due to
> implementation related considerations? I guess you want to use
> the 'U' flag for this.
>
> But there are others who have expressed that this flag can be
> used for firewall traversal. Since the MN wouldn't know if
> there is a  firewall on the path, it would end up setting the
> 'U' flag all the time. If the HA can't override it, then
> providing a NAT detection mechanism is useless, IMO.

I think my idea was not well explained...  (or I am missing  
something...)

If a mobile node doesn't know anything about NAT nor FW, and if the  
mobile node supports both IP-in-IP mode and IP-in-UDP mode, then the  
node doesn't need to specify the 'U' flag.  In that case, the HA will  
decide whether the IP-in-UDP mode is necessary or not, and replies  
with a BA message with the 'F' flag if needed.  There is no need to  
put the 'U' flag for mobile nodes that supports both encapsulation  
modes.

What I wanted to add was the support for mobile nodes that wanted  
simpler (I mean, supporting only IP-in-UDP mode) implementation.   
Only such nodes will set the 'U' flag.

Hope I could make myself clear...

---
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 Thu Mar 29 01:26:27 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWn9M-0007CY-5V; Thu, 29 Mar 2007 01:26:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWn9L-0007CP-Ow
	for mip6@ietf.org; Thu, 29 Mar 2007 01:26:15 -0400
Received: from omta04ps.mx.bigpond.com ([144.140.83.156])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWn9J-00055B-9p
	for mip6@ietf.org; Thu, 29 Mar 2007 01:26:15 -0400
Received: from oaamta04ps.mx.bigpond.com ([124.191.178.123])
	by omta04ps.mx.bigpond.com with ESMTP id
	<20070329052551.RWMM15631.omta04ps.mx.bigpond.com@oaamta04ps.mx.bigpond.com>;
	Thu, 29 Mar 2007 05:25:51 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta04ps.mx.bigpond.com
	with ESMTP
	id <20070329052551.HNI14698.oaamta04ps.mx.bigpond.com@PC20005>;
	Thu, 29 Mar 2007 05:25:51 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>,
	"'Vijay Devarapalli'" <vijay.devarapalli@azairenet.com>
Subject: RE: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
Date: Thu, 29 Mar 2007 15:25:46 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdxwcwWFdGlPDkPS/iTqOxVsoQhlgAAEUFg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <E36633CF-97CE-49C8-A69F-F957925D40B6@iijlab.net>
Message-Id: <20070329052551.HNI14698.oaamta04ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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


 > What I wanted to add was the support for mobile nodes that wanted  
 > simpler (I mean, supporting only IP-in-UDP mode) implementation.   
 > Only such nodes will set the 'U' flag.
 > 
 > Hope I could make myself clear...

=> I know that's what you originally wanted but you then asked for this
compromise approach. There was (and still is) a lot of resistance to the
rationale you suggested, which is to reduce the implementer's work in favour
of always using one tunnelling mechanism. The logic behind it is not really
acceptable, so we can settle for this approach, under the assumption that
the HA should accept the MN's request unless there is a reason (i.e. it is
configured) for not accepting it. Mandating one tunnelling approach is just
not a good idea.It's not supported technically (as I mentioned before you
have to support both in all cases) or by previous specs. 

Hesham

 > 
 > ---
 > 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 Thu Mar 29 01:42:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWnO4-0007LK-Jc; Thu, 29 Mar 2007 01:41:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWnO2-0007LF-SX
	for mip6@ietf.org; Thu, 29 Mar 2007 01:41:26 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWnO1-0000L6-9h
	for mip6@ietf.org; Thu, 29 Mar 2007 01:41:26 -0400
Received: OTM-MO(otm-mgo01) id l2T5fLmi068770;
	Thu, 29 Mar 2007 14:41:21 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2T5fKr0060371;
	Thu, 29 Mar 2007 14:41:21 +0900 (JST)
Received: from [127.0.0.1] (keiichi00-4.osaka.iij.ad.jp [192.168.64.45])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2T5eOhg064108
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 29 Mar 2007 14:40:25 +0900 (JST)
In-Reply-To: <E1HWV9s-0006uo-MB@megatron.ietf.org>
References: <E1HWV9s-0006uo-MB@megatron.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DA39668B-ECCF-4DF3-B15B-02D11FE44BF8@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] RE: concensus on [issue94] fixing encapsulation mechanism
	in IPv4 network
Date: Thu, 29 Mar 2007 14:41:20 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello,

On 2007/03/28, at 19:13, Hesham Soliman wrote:

>> The idea is to introduce a new flag for MN to request the
>> UDP tunnel
>> mode.  Let's call it as the 'U (requesting UDP tunnel)'
>> flag.  If the
>> MN doesn't specify the 'U' flag, the behavior is exactly the
>> same as
>> the current specification.  The HA can decide what kind of
>> tunneling
>> mechanism (IP-in-IP or UDP-in-IP).
>>
>> When the MN sets the 'U' flag on, the HA always replies with the 'F
>> (Force UDP tunnel)' flag.  This is a new behavior what I want to
>> propose.
>>
>> The HA shouldn't override the 'U' flag.  If we allow overriding the
>> 'U' flag, then there is no difference between the option 'A' and 'B'.
>
> => There is a difference between A and B of course. The difference  
> is that
> in B the MN can't request anything and is either told to use UDP or  
> told to
> use IP in IP. In A, the MN can request UDP tunnels. Like any other  
> request

I don't understand if there is any meaning to allow a mobile node to  
request UDP encap when the HA can ignore the request...  (maybe I'm  
missing something?)


> in MIPv6 (e.g. BU lifetime, HoA ....etc) the HA always has the  
> upper hand
> and decides whether the request is acceptable or not. I simply  
> followed the

These are OK because even the HA rejects the MN's request. e.g. when  
the MN request 1000 seconds lifetime, but the HA allows 100 seconds,  
there is no interoperability problem here.  Because the MN can work  
with 100 seconds lifetime in this case.

> same rule here. For instance, the HA/MAP might think UDP tunnelling  
> is not
> acceptable for policy reasons (e.g. an operator doesn't want the MN  
> to waste
> BW when UDP is not needed). I don't have an exhaustive list of  
> scenarios so
> I just erred on the conservative side of keeping with the current  
> approach
> in MIPv6.

As I talked to you at the last IETF, my intension is to allow mobile  
nodes that implement only the UDP tunnel mode for v4 traversal  
purpose.  Since such nodes don't decapsulate IPvX-in-IPv4 packets for  
DS-MIPv6, replying with a BA message rejecting UDP encapsulation and  
forcing IPvX-in-IPv4 mode doesn't work.


I think you are implicitly assuming IPvX-in-IPv4 is a must feature.   
So you only allow MN and HA that support both IPvX-in-IPv4 and IPvx- 
in-UDPv4 modes.  But I think we can also allow UDP only operation.   
There is no technical reason to reject the possibility, is it?  If we  
can introduce the flag (the 'U' flag from the MN), then we can allow  
HA and MN that only support the UDP tunnel mode keeping  
interoperability between all of them.  There are 4 cases:

HA (UDP mode, IP mode) - MN (UDP mode, IP mode)
   => works as specified in the current spec

HA (UDP mode) - MN (UDP mode, IP mode)
   => HA always replies with the 'F' flag and works with UDP mode

HA (UDP mode, IP mode) - MN (UDP mode)
   => MN always sets the 'U' flag and works with UDP mode

HA (UDP mode) - MN (UDP mode)
   => MN always sets the 'U' flag and works with UDP mode

There is no drawback, I think.

Regards,
---
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 Thu Mar 29 01:45:06 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWnRM-0000IN-OZ; Thu, 29 Mar 2007 01:44:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWnRK-0000Gm-Jb
	for mip6@ietf.org; Thu, 29 Mar 2007 01:44:50 -0400
Received: from otm-mgo00.iij.ad.jp ([210.138.20.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWnRJ-0002IN-2n
	for mip6@ietf.org; Thu, 29 Mar 2007 01:44:50 -0400
Received: OTM-MO(otm-mgo00) id l2T5iQEX068632;
	Thu, 29 Mar 2007 14:44:26 +0900 (JST)
Received: OTM-MIX(otm-mix00) id l2T5iP1k001216;
	Thu, 29 Mar 2007 14:44:26 +0900 (JST)
Received: from [127.0.0.1] (keiichi00-4.osaka.iij.ad.jp [192.168.64.45])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2T5hTte064141
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 29 Mar 2007 14:43:30 +0900 (JST)
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA4371136B508D@zrc2hxm2.corp.nortel.com>
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
	<6FC4416DDE56C44DA0AEE67BC7CA4371136B508D@zrc2hxm2.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E1CB97DC-CBCF-4DA7-8F7C-A89B1B0805C4@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
Date: Thu, 29 Mar 2007 14:44:26 +0900
To: Ahmad Muhanna <amuhanna@nortel.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello,

On 2007/03/28, at 19:29, Ahmad Muhanna wrote:

> Sorry for jumping in without previously being involved in the
> discussion. However, in my mind, HA should have the upper hand of
> deciding whatever the MN is requesting. If the HA has the right to
> reject MN BU, it has the right to deny UDP encapsulation.
>
> I believe that should be the correct approach.

Yes, as long as both nodes have the same features.

But I am now talking about a mobile node that only supports the UDP  
tunnel mode.  In this case, forcing the IP-in-IP tunnel mode by the  
HA has no meaning because the MN doesn't support the mode.

Regards,
---
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 Thu Mar 29 01:51:51 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HWnXs-0006J5-Qm; Thu, 29 Mar 2007 01:51:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWnXr-0006Ih-1Y
	for mip6@ietf.org; Thu, 29 Mar 2007 01:51:35 -0400
Received: from omta04ps.mx.bigpond.com ([144.140.83.156])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWnXp-0003zo-GI
	for mip6@ietf.org; Thu, 29 Mar 2007 01:51:34 -0400
Received: from oaamta08ps.mx.bigpond.com ([124.191.178.123])
	by omta04ps.mx.bigpond.com with ESMTP id
	<20070329055121.TNLD15631.omta04ps.mx.bigpond.com@oaamta08ps.mx.bigpond.com>;
	Thu, 29 Mar 2007 05:51:21 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta08ps.mx.bigpond.com
	with ESMTP
	id <20070329055121.MTLZ8812.oaamta08ps.mx.bigpond.com@PC20005>;
	Thu, 29 Mar 2007 05:51:21 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>
Subject: RE: [Mip6] RE: concensus on [issue94] fixing encapsulation mechanism
	in IPv4 network
Date: Thu, 29 Mar 2007 15:51:17 +1000
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0041_01C7721A.17258700"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdxxXR6Yvy9OTILT1qv0XfTPd0MdwAAAwDA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <DA39668B-ECCF-4DF3-B15B-02D11FE44BF8@iijlab.net>
Message-Id: <20070329055121.MTLZ8812.oaamta08ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

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


 > As I talked to you at the last IETF, my intension is to 
 > allow mobile  
 > nodes that implement only the UDP tunnel mode for v4 traversal  
 > purpose.  Since such nodes don't decapsulate IPvX-in-IPv4 
 > packets for  
 > DS-MIPv6, replying with a BA message rejecting UDP 
 > encapsulation and  
 > forcing IPvX-in-IPv4 mode doesn't work.
 > 
 > 
 > I think you are implicitly assuming IPvX-in-IPv4 is a must 
 > feature.   
 > So you only allow MN and HA that support both IPvX-in-IPv4 and IPvx- 
 > in-UDPv4 modes.  But I think we can also allow UDP only operation.   
 > There is no technical reason to reject the possibility, is 
 > it?  

=> Yes there is, I explained it during our discussion and on the mailing
list. Others also explained it on the list. I'm attaching one of my emails
again. The idea that you can only support one tunnelling protocol is *not*
technically possible as you request it. Please read my email attached again.


Hesham 





If we  
 > can introduce the flag (the 'U' flag from the MN), then we 
 > can allow  
 > HA and MN that only support the UDP tunnel mode keeping  
 > interoperability between all of them.  There are 4 cases:
 > 
 > HA (UDP mode, IP mode) - MN (UDP mode, IP mode)
 >    => works as specified in the current spec
 > 
 > HA (UDP mode) - MN (UDP mode, IP mode)
 >    => HA always replies with the 'F' flag and works with UDP mode
 > 
 > HA (UDP mode, IP mode) - MN (UDP mode)
 >    => MN always sets the 'U' flag and works with UDP mode
 > 
 > HA (UDP mode) - MN (UDP mode)
 >    => MN always sets the 'U' flag and works with UDP mode
 > 
 > There is no drawback, I think.
 > 
 > Regards,
 > ---
 > Keiichi SHIMA
 > IIJ Research Laboratory <keiichi@iijlab.net>
 > WIDE Project <shima@wide.ad.jp>
 > 
 > 
 > 
 > 

------=_NextPart_000_0041_01C7721A.17258700
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment

From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>
Cc: "'Mip6 issue tracker'" <tracker-mip6@mip4.org>,
	<mip6@ietf.org>
Subject: RE: [Mip6] [issue94] fixing encapsulation mechanism in IPv4 network
Date: Wed, 21 Mar 2007 20:40:16 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Acdroyga7pFUyTl/Q5CBCKvFyI+SgQAAHmBQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <623CC63B-6E30-45B5-AA1D-8947EAD698C6@iijlab.net>


 > > switching between the UDP tunnel and IP n IP is very small (from an
 > > implementation point of view).
 > 
 > I may not agree on the above point.  Since UDP is a transport  
 > protocol, encapsulating something in it cannot be handled by a  
 > *normal* packet decapsulation flow, while IPv4-in-IPv4 can 
 > be fit to  
 > the natural flow.  So switching from IPv4 encapsulation to UDP  
 > encapsulation may not be so easy as you say, especially for MIP  
 > stacks that are implemented in user space.

=> I'm not sure I get that. If you're implementing in user space you would
still know how to handle IP n IP today because that's what MIP6 does today
and some people have already done that in user space. The UDP part is always
there because the BU is always sent on UDP. So if someone already implements
MIP6 in user space they already need to know how to handle IP n IP and if we
choose to do UDP only in DSMIP then they end up in a situation where they
have to handle both tunnelling mechanisms anyway. 

So to summarise for the user space case:

- You always need to handle IP n IP for native MIPv6 (it doesn't matter
whether it's v6 in v6 or v6 in v4, it's all IP n IP). 

- You always need to handle the UDP tunnel because the BU in DSMIP is always
sent in UDP. 

The difference in the DSMIP case is that normal traffic can also be
tunnelled in UDP, but that's the case you want to keep anyway. So you'll
always end up having to support both types of tunnels whether we remove IP n
IP from DSMIP or not. 

What am I missing? 

Hesham


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

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

------=_NextPart_000_0041_01C7721A.17258700--






From mip6-bounces@ietf.org Fri Mar 30 04:23:45 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXCNd-0001dO-OD; Fri, 30 Mar 2007 04:22:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXCNb-0001Zy-SC
	for mip6@ietf.org; Fri, 30 Mar 2007 04:22:39 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXCNa-0001cR-7K
	for mip6@ietf.org; Fri, 30 Mar 2007 04:22:39 -0400
Received: from ep_ms5_bk (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 <0JFP00LYTJ9OEI@mailout3.samsung.com> for mip6@ietf.org;
	Fri, 30 Mar 2007 17:22:36 +0900 (KST)
Received: from ep_spt03 (ms5.samsung.com [203.254.225.113])
	by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTP id <0JFP0072YJ9OYX@ms5.samsung.com> for mip6@ietf.org; Fri,
	30 Mar 2007 17:22:36 +0900 (KST)
Content-return: prohibited
Date: Fri, 30 Mar 2007 08:22:36 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Message-id: <24145557.784621175242956455.JavaMail.weblogic@ep_ml24>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070330082236454@heejin.jang
X-MTR: 20070330082236454@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.1 (++)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: Redundant text in the two DHCPv6-based bootstrapping
	documents
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: heejin.jang@samsung.com
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0624692315=="
Errors-To: mip6-bounces@ietf.org

--===============0624692315==
Content-return: prohibited
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: base64

SGksIFZpamF5Lg0KQXMgeW91IHBvaW50ZWQgb3V0LCB0aGVyZSBpcyBzb21lIHJlZHVuZGFuY2Ug
YmV0d2VlbiBib290c3RyYXBwaW5nLWludGVncmF0ZWQgJiBkcmFmdC1pZXRmLW1pcDYtaGlvcHQt
MDIudHh0Lg0KVGhlIGhpb3B0LTAyIGRyYWZ0IHdpbGwgYmUgdXBkYXRlZCB0byByZW1vdmUgdGhl
IGR1cGxpY2F0ZWQgcGFydCBieSByZWZlcnJpbmcgdGhlIGJvb3RzdHJhcHBpbmctaW50ZWdyYXRl
ZCBkcmFmdA0KZXhjZXB0IHRoZSBtaW5pbWFsIGR1cGxpY2F0aW9uIHdoaWNoIGlzIG5lY2Vzc2Fy
eSBmb3IgdGhlIGRlc2NyaXB0aW9uIG9mIHRoZSBvcHRpb24gdXNhZ2UuDQpUaGFua3MgZm9yIHlv
dXIgY29tbWVudHMuDQoNCi0gUmVnYXJkcywgDQpIZWVqaW4uDQogDQogDQoNCi0tLS0tLS0gT3Jp
Z2luYWwgTWVzc2FnZSAtLS0tLS0tDQpTZW5kZXIgOiBWaWpheSBEZXZhcmFwYWxsaTx2aWpheS5k
ZXZhcmFwYWxsaUBhemFpcmVuZXQuY29tPg0KRGF0ZSAgIDogMjAwNy0wMy0yMSAwMTowMg0KVGl0
bGUgIDogUmVkdW5kYW50IHRleHQgaW4gdGhlIHR3byBESENQdjYtYmFzZWQgYm9vdHN0cmFwcGlu
ZyBkb2N1bWVudHMNCg0KSGVsbG8NCg0KVGhlcmUgaXMgc29tZSByZWR1bmRhbnQgdGV4dCBpbiB0
aGUgdHdvIGRvY3VtZW50cyB0aGF0IHRhbGsgYWJvdXQgdXNpbmcgDQpESENQdjYgZm9yIE1JUDYg
Ym9vdHN0cmFwcGluZywgZHJhZnQtaWV0Zi1taXA2LWhpb3B0LTAyLnR4dCBhbmQgDQpkcmFmdC1p
ZXRmLW1pcDYtYm9vdHN0cmFwcGluZy1pbnRlZ3JhdGVkLWRoYy0wMi50eHQuIEhlcmUgYXJlIGEg
Y291cGxlIA0Kb2YgaW5zdGFuY2VzLg0KDQpNb2JpbGUgTm9kZSBiZWhhdmlvciBmb3Igc2VuZGlu
ZyB0aGUgREhDUHY2IEluZm9ybWF0aW9uIFJlcXVlc3QNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQogRnJvbSBkcmFmdC1p
ZXRmLW1pcDYtaGlvcHQtMDIudHh0DQoNCiAgICBJbiBvcmRlciB0byBhY3F1aXJlIHRoZSBob21l
IG5ldHdvcmsgaW5mb3JtYXRpb24sIHRoZSBtb2JpbGUgbm9kZQ0KICAgIFNIQUxMIHNlbmQgYW4g
SW5mb3JtYXRpb24gUmVxdWVzdCB0byB0aGUNCiAgICBBbGxfREhDUF9SZWxheV9BZ2VudHNfYW5k
X1NlcnZlcnMgbXVsdGljYXN0IGFkZHJlc3MuICBJbiB0aGlzIG1lc3NhZ2UNCiAgICB0aGUgbW9i
aWxlIG5vZGUgKERIQ1AgY2xpZW50KSBTSEFMTCBpbmNsdWRlIHRoZSBPcHRpb24gQ29kZSBmb3Ig
SG9tZQ0KICAgIE5ldHdvcmsgSWRlbnRpZmllciBvcHRpb24gaW4gdGhlIE9QVElPTl9PUk8uICBU
aGUgbW9iaWxlIG5vZGUgU0hBTEwNCiAgICBhbHNvIGluY2x1ZGUgdGhlIE9QVElPTl9DTElFTlRJ
RCBbNF0gdG8gaWRlbnRpZnkgaXRzZWxmIHRvIHRoZSBESENQDQogICAgc2VydmVyLg0KDQogICAg
RHVyaW5nIHJlcXVlc3RpbmcgdGhlIGluZm9ybWF0aW9uLCB0aGUgbW9iaWxlIG5vZGUgTVVTVCBj
bGFyaWZ5IHRoZQ0KICAgIHByZWZlcmVuY2UgYWJvdXQgdGhlIHJlcXVlc3RlZCBob21lIG5ldHdv
cmsgd2l0aCB0aGUgaWQtdHlwZSBpbiB0aGUNCiAgICBIb21lIE5ldHdvcmsgSWRlbnRpZmllciBv
cHRpb24uICBFdmVuIGlmIHRoZSBtb2JpbGUgbm9kZSBkb2VzIG5vdA0KICAgIGNhcmUgYWJvdXQg
dGhlIGxvY2F0aW9uIG9mIHRoZSBob21lIG5ldHdvcmsgd2hlcmUgdGhlIGhvbWUgYWdlbnQgdG8N
CiAgICBiZSBhc3NpZ25lZCwgaXQgTVVTVCBjbGFyaWZ5IHRoZSBmYWN0IGJ5IHNldHRpbmcgdGhl
IGlkLXR5cGUgdG8gMi4NCiAgICBJbiB0aGlzIGNhc2UgdGhlIEhvbWUgTmV0d29yayBJZGVudGlm
aWVyIE1VU1QgYmUgc2V0IHRvIDAuDQoNCiBGcm9tIGRyYWZ0LWlldGYtbWlwNi1ib290c3RyYXBw
aW5nLWludGVncmF0ZWQtZGhjLTAyLnR4dA0KDQogICAgKDIpIFRoZSBtb2JpbGUgbm9kZSBzZW5k
cyBhIERIQ1B2NiBJbmZvcm1hdGlvbiBSZXF1ZXN0IG1lc3NhZ2UNCiAgICBbUkZDMzMxNV0gdG8g
dGhlIEFsbF9ESENQX1JlbGF5X0FnZW50c19hbmRfU2VydmVycyBtdWx0aWNhc3QgYWRkcmVzcy4N
CiAgICBJbiB0aGlzIG1lc3NhZ2UgdGhlIG1vYmlsZSBub2RlIChESENQIGNsaWVudCkgU0hBTEwg
aW5jbHVkZSB0aGUNCiAgICBPcHRpb24gQ29kZSBmb3IgSG9tZSBOZXR3b3JrIElkZW50aWZpZXIg
T3B0aW9uIFtISU9QVF0gaW4gdGhlDQogICAgT1BUSU9OX09STywgSG9tZSBOZXR3b3JrIElkZW50
aWZpZXIgT3B0aW9uIHdpdGggaWQtdHlwZSBzZXQgdG8gMSBhbmQNCiAgICB0aGUgSG9tZSBOZXR3
b3JrIElkZW50aWZpZXIgZmllbGQgc2V0IHRvIHRoZSBuZXR3b3JrIHJlYWxtIG9mIHRoZQ0KICAg
IGhvbWUgTVNQIFtISU9QVF0uICBUaGUgbW9iaWxlIG5vZGUgU0hBTEwgYWxzbyBpbmNsdWRlIHRo
ZQ0KICAgIE9QVElPTl9DTElFTlRJRCB0byBpZGVudGlmeSBpdHNlbGYgdG8gdGhlIERIQ1Agc2Vy
dmVyLg0KDQoNCk5BUy9ESENQIHJlbGF5IGJlaGF2aW9yDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KDQogRnJvbSBkcmFmdC1pZXRmLW1pcDYtaGlvcHQtMDIudHh0DQoNCiAgICBVcG9uIHJlY2Vp
dmluZyB0aGUgSW5mb3JtYXRpb24gUmVxdWVzdCBmcm9tIHRoZSBtb2JpbGUgbm9kZSwgdGhlIERI
Q1ANCiAgICByZWxheSBhZ2VudCBNVVNUIGZvcndhcmQgdGhlIG1lc3NhZ2UgdG8gdGhlIERIQ1Ag
c2VydmVyIGFzIHBlciBbNF0uDQogICAgVGhlIHJlbGF5IGFnZW50IFNIQUxMIHVzZSB0aGUgT1BU
SU9OX0NMSUVOVElEIHRvIGlkZW50aWZ5IHRoZSBtb2JpbGUNCiAgICBub2RlICh1c2VyKS4gIFRo
aXMgaXMgcmVxdWlyZWQgdG8gY2hlY2sgd2hldGhlciB0aGVyZSBhcmUgc29tZQ0KICAgIGFkZGl0
aW9uYWwgaW5mb3JtYXRpb24gZm9yIHRoZSB1c2VyIHRoYXQgbmVlZCB0byBiZSBhcHBlbmRlZCB3
aGlsZQ0KICAgIHJlbGF5aW5nIHRoZSBpbmZvcm1hdGlvbiByZXF1ZXN0IG1lc3NhZ2UgdG8gdGhl
IERIQ1Agc2VydmVyLiAgSWYgdGhlDQogICAgcmVsYXkgYWdlbnQgZGV0ZXJtaW5lcyB0aGF0IHRo
ZSBOQVMgaGFzIHBhc3NlZCBob21lIG5ldHdvcmsNCiAgICBpbmZvcm1hdGlvbiBmb3IgdGhpcyBt
b2JpbGUgbm9kZSwgdGhlIHJlbGF5IGFnZW50IE1VU1QgaW5jbHVkZSB0aGUNCiAgICByZWNlaXZl
ZCBob21lIG5ldHdvcmsgaW5mb3JtYXRpb24gaW4gdGhlIE1JUDYgUmVsYXkgQWdlbnQgb3B0aW9u
LCBhbmQNCiAgICBhdHRhY2ggdGhpcyBvcHRpb24gaW4gdGhlIFJlbGF5LUZvcndhcmQgbWVzc2Fn
ZS4gIFRoZSByZWxheSBhZ2VudCBNQVkNCiAgICBpbmNsdWRlIHRoZSBJbnRlcmZhY2UtSWQgb3B0
aW9uIFs0XSBpbiB0aGUgUmVsYXktRm9yd2FyZCBtZXNzYWdlLg0KDQogRnJvbSBkcmFmdC1pZXRm
LW1pcDYtYm9vdHN0cmFwcGluZy1pbnRlZ3JhdGVkLWRoYy0wMi50eHQNCg0KICAgICgzKSBUaGUg
UmVsYXkgQWdlbnQgaW50ZXJjZXB0cyB0aGUgSW5mb3JtYXRpb24gUmVxdWVzdCBmcm9tIHRoZQ0K
ICAgIG1vYmlsZSBub2RlIGFuZCBmb3J3YXJkcyBpdCB0byB0aGUgREhDUCBzZXJ2ZXIuICBUaGUg
UmVsYXkgQWdlbnQgYWxzbw0KICAgIGluY2x1ZGVzIHRoZSByZWNlaXZlZCBob21lIGFnZW50IGlu
Zm9ybWF0aW9uIGZyb20gdGhlIEFBQUggaW4gdGhlDQogICAgT1BUSU9OX01JUDYtUkVMQVktT3B0
aW9uIFtISU9QVF0uDQoNCkkgd291bGQgcHJlZmVyIGl0IGlmIG9uZSBkb2N1bWVudCBkZXNjcmli
ZXMgdGhlIHByb3RvY29sIGFuZCB0aGUgb3RoZXIgDQpqdXN0IGRlZmluZXMgdGhlIG9wdGlvbnMu
DQoNCkkgYWxzbyBmaW5kIGl0IGEgYml0IG9kZCB0aGF0IGRyYWZ0LWlldGYtbWlwNi1oaW9wdC0w
Mi50eHQgZG9lcyBub3QgDQpyZWZlciB0byBkcmFmdC1pZXRmLW1pcDYtYm9vdHN0cmFwcGluZy1p
bnRlZ3JhdGVkLWRoYy0wMi50eHQgYXQgYWxsLiBJdCANCmlzIGxpc3RlZCBhbW9uZyB0aGUgcmVm
ZXJlbmNlcywgYnV0IG5vdCBhbnl3aGVyZSBpbiB0aGUgdGV4dC4gSSB3b3VsZCANCmhhdmUgZXhw
ZWN0ZWQgaXQgdG8gc2F5IHRoYXQgaGlvcHQgZHJhZnQgZGVmaW5lcyBvcHRpb25zIHRoYXQgYXJl
IHVzZWQgDQppbiB0aGUgaW50ZWdyYXRlZCBzY2VuYXJpbyBzb2x1dGlvbiBkb2N1bWVudC4NCg0K
VmlqYXkNCg0KDQog




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

--===============0624692315==--



From mip6-bounces@ietf.org Fri Mar 30 05:22:10 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXDIy-00050J-Fu; Fri, 30 Mar 2007 05:21:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXDIw-0004ze-T4
	for mip6@ietf.org; Fri, 30 Mar 2007 05:21:54 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXDIv-000380-Hj
	for mip6@ietf.org; Fri, 30 Mar 2007 05:21:54 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Mar 2007 02:21:40 -0700
Message-ID: <460CD6A0.3030307@azairenet.com>
Date: Fri, 30 Mar 2007 02:21:36 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: heejin.jang@samsung.com
References: <24145557.784621175242956455.JavaMail.weblogic@ep_ml24>
In-Reply-To: <24145557.784621175242956455.JavaMail.weblogic@ep_ml24>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Mar 2007 09:21:40.0508 (UTC)
	FILETIME=[D31B6DC0:01C772AC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: Redundant text in the two DHCPv6-based bootstrapping
	documents
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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:
> Hi, Vijay.
> As you pointed out, there is some redundance between bootstrapping-integrated & draft-ietf-mip6-hiopt-02.txt.
> The hiopt-02 draft will be updated to remove the duplicated part by referring the bootstrapping-integrated draft
> except the minimal duplication which is necessary for the description of the option usage.
> Thanks for your comments.

Thanks.

Also draft-ietf-mip6-bootstrapping-integrated-dhc is listed in the 
references of draft-ietf-mip6-hiopt without actually referring to it 
anywhere in the text. Such references are typically removed by the RFC 
Editor.

Vijay

> 
> - Regards, 
> Heejin.
>  
>  
> 
> ------- Original Message -------
> Sender : Vijay Devarapalli<vijay.devarapalli@azairenet.com>
> Date   : 2007-03-21 01:02
> Title  : Redundant text in the two DHCPv6-based bootstrapping documents
> 
> Hello
> 
> There is some redundant text in the two documents that talk about using 
> DHCPv6 for MIP6 bootstrapping, draft-ietf-mip6-hiopt-02.txt and 
> draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt. Here are a couple 
> of instances.
> 
> Mobile Node behavior for sending the DHCPv6 Information Request
> ---------------------------------------------------------------
> 
>  From draft-ietf-mip6-hiopt-02.txt
> 
>     In order to acquire the home network information, the mobile node
>     SHALL send an Information Request to the
>     All_DHCP_Relay_Agents_and_Servers multicast address.  In this message
>     the mobile node (DHCP client) SHALL include the Option Code for Home
>     Network Identifier option in the OPTION_ORO.  The mobile node SHALL
>     also include the OPTION_CLIENTID [4] to identify itself to the DHCP
>     server.
> 
>     During requesting the information, the mobile node MUST clarify the
>     preference about the requested home network with the id-type in the
>     Home Network Identifier option.  Even if the mobile node does not
>     care about the location of the home network where the home agent to
>     be assigned, it MUST clarify the fact by setting the id-type to 2.
>     In this case the Home Network Identifier MUST be set to 0.
> 
>  From draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt
> 
>     (2) The mobile node sends a DHCPv6 Information Request message
>     [RFC3315] to the All_DHCP_Relay_Agents_and_Servers multicast address.
>     In this message the mobile node (DHCP client) SHALL include the
>     Option Code for Home Network Identifier Option [HIOPT] in the
>     OPTION_ORO, Home Network Identifier Option with id-type set to 1 and
>     the Home Network Identifier field set to the network realm of the
>     home MSP [HIOPT].  The mobile node SHALL also include the
>     OPTION_CLIENTID to identify itself to the DHCP server.
> 
> 
> NAS/DHCP relay behavior
> -----------------------
> 
>  From draft-ietf-mip6-hiopt-02.txt
> 
>     Upon receiving the Information Request from the mobile node, the DHCP
>     relay agent MUST forward the message to the DHCP server as per [4].
>     The relay agent SHALL use the OPTION_CLIENTID to identify the mobile
>     node (user).  This is required to check whether there are some
>     additional information for the user that need to be appended while
>     relaying the information request message to the DHCP server.  If the
>     relay agent determines that the NAS has passed home network
>     information for this mobile node, the relay agent MUST include the
>     received home network information in the MIP6 Relay Agent option, and
>     attach this option in the Relay-Forward message.  The relay agent MAY
>     include the Interface-Id option [4] in the Relay-Forward message.
> 
>  From draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt
> 
>     (3) The Relay Agent intercepts the Information Request from the
>     mobile node and forwards it to the DHCP server.  The Relay Agent also
>     includes the received home agent information from the AAAH in the
>     OPTION_MIP6-RELAY-Option [HIOPT].
> 
> I would prefer it if one document describes the protocol and the other 
> just defines the options.
> 
> I also find it a bit odd that draft-ietf-mip6-hiopt-02.txt does not 
> refer to draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt at all. It 
> is listed among the references, but not anywhere in the text. I would 
> have expected it to say that hiopt draft defines options that are used 
> in the integrated scenario solution document.
> 
> Vijay
> 
> 
>  


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



From mip6-bounces@ietf.org Fri Mar 30 05:22:26 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXDJS-0005CO-Qy; Fri, 30 Mar 2007 05:22:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXDJR-0005CI-9L
	for mip6@ietf.org; Fri, 30 Mar 2007 05:22:25 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXDJP-0003Cf-MC
	for mip6@ietf.org; Fri, 30 Mar 2007 05:22:25 -0400
Received: OTM-MO(otm-mgo01) id l2U9M5xb029451;
	Fri, 30 Mar 2007 18:22:05 +0900 (JST)
Received: OTM-MIX(otm-mix00) id l2U9M4GY031871;
	Fri, 30 Mar 2007 18:22:05 +0900 (JST)
Received: from [127.0.0.1] (keiichi00-4.osaka.iij.ad.jp [192.168.64.45])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id l2U9L6aQ080278
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 30 Mar 2007 18:21:07 +0900 (JST)
In-Reply-To: <460A9D8D.2010302@levkowetz.com>
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
	<460A9D8D.2010302@levkowetz.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <56834D20-93BA-4020-8EA6-6ECA4AFCE446@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
Date: Fri, 30 Mar 2007 18:22:03 +0900
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Henrik,

On 2007/03/29, at 1:53, Henrik Levkowetz wrote:

> on 2007-03-28 12:06 Keiichi SHIMA said the following:
>>
>> I think the text explaining the option 'A' is not exactly what I
>> proposed in my previous mail.  Please let me clarify the text about
>> the option 'A'.
>>
>>
>> On 2007/03/28, at 16:33, Hesham Soliman wrote:
>>
>>> A. Add a flag that allows the MN to request UDP tunnelling interface
>>> (independently of the presence of a NAT) from the HA, when sending
>>> the BU.
>>> The HA can override the MN's request. Or,
>>
>> The idea is to introduce a new flag for MN to request the UDP tunnel
>> mode.  Let's call it as the 'U (requesting UDP tunnel)' flag.  If the
>> MN doesn't specify the 'U' flag, the behavior is exactly the same as
>> the current specification.  The HA can decide what kind of tunneling
>> mechanism (IP-in-IP or UDP-in-IP).
>>
>> When the MN sets the 'U' flag on, the HA always replies with the 'F
>> (Force UDP tunnel)' flag.  This is a new behavior what I want to
>> propose.
>>
>> The HA shouldn't override the 'U' flag.  If we allow overriding the
>> 'U' flag, then there is no difference between the option 'A' and 'B'.
>
> Umm.
>
> I hope we're not in "Not Invented Here" mode.
>
> Is there any reason to deviate from the specification of this flag,
> and the way the HA handles it, which is given in the MIPv4 NAT  
> traversal
> specification?
>
> See http://tools.ietf.org/html/rfc3519#section-3.1.1

I'm not sure I understand the 'F' flag defined in RFC3519, but let me  
clarify my understanding.

The 'F' flag in RFC3519 is a flag sent from a mobile node to request  
its home agent to use UDP tunneling mode.  If the home agent  
understand the RFC3519 'F' flag, then it either 'accepts the UDP  
tunnel' or 'rejects the binding update'.

Is my understanding correct?

I think the action is different from the Hesham's proposal.  His  
proposal allows to override the RFC3519 style 'F' flag at the HA.   
Thus, the HA may accept the BU message with the RFC3519 style 'F'  
flag even the HA doesn't allow UDP tunnel.  Since the mobile node is  
forcing UDP tunnel, replying with a BA message requesting not to use  
UDP is not correct way I think.  (Rejecting the request is  
understandable as described in RFC3519)

So let me rephrase the option A.

A. Add a flag that allows the MN to request UDP tunnelling interface  
(independently of the presence of a NAT) from the HA, when sending  
the BU.  If the HA accepts the request then the HA replies the BU  
with a BA with the 'F (Force UDP)' flag.  Otherwise the HA rejects  
the BU with status code "administratively prohibited".

Does it make sense?

---
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 Fri Mar 30 05:33:18 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXDTI-0005JX-FP; Fri, 30 Mar 2007 05:32:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXDTG-0005JS-QO
	for mip6@ietf.org; Fri, 30 Mar 2007 05:32:34 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXDTF-0004Y9-90
	for mip6@ietf.org; Fri, 30 Mar 2007 05:32:34 -0400
Received: OTM-MO(otm-mgo01) id l2U9WVPJ029873;
	Fri, 30 Mar 2007 18:32:31 +0900 (JST)
Received: OTM-MIX(otm-mix01) id l2U9WUVQ094788;
	Fri, 30 Mar 2007 18:32:30 +0900 (JST)
Received: from [127.0.0.1] (keiichi00-4.osaka.iij.ad.jp [192.168.64.45])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp00) id l2U9WT0L071547
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 30 Mar 2007 18:32:30 +0900 (JST)
In-Reply-To: <20070329055121.MTLZ8812.oaamta08ps.mx.bigpond.com@PC20005>
References: <20070329055121.MTLZ8812.oaamta08ps.mx.bigpond.com@PC20005>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <66A793F9-B3CD-4613-81B8-CAD436871287@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] RE: concensus on [issue94] fixing encapsulation mechanism
	in IPv4 network
Date: Fri, 30 Mar 2007 18:32:31 +0900
To: Hesham Soliman <Hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Hesham,

On 2007/03/29, at 14:51, Hesham Soliman wrote:

>> As I talked to you at the last IETF, my intension is to
>> allow mobile
>> nodes that implement only the UDP tunnel mode for v4 traversal
>> purpose.  Since such nodes don't decapsulate IPvX-in-IPv4
>> packets for
>> DS-MIPv6, replying with a BA message rejecting UDP
>> encapsulation and
>> forcing IPvX-in-IPv4 mode doesn't work.
>>
>>
>> I think you are implicitly assuming IPvX-in-IPv4 is a must
>> feature.
>> So you only allow MN and HA that support both IPvX-in-IPv4 and IPvx-
>> in-UDPv4 modes.  But I think we can also allow UDP only operation.
>> There is no technical reason to reject the possibility, is
>> it?
>
> => Yes there is, I explained it during our discussion and on the  
> mailing
> list. Others also explained it on the list. I'm attaching one of my  
> emails
> again. The idea that you can only support one tunnelling protocol  
> is *not*
> technically possible as you request it. Please read my email  
> attached again.

I think you are explaining the reason why we can allow IP-in-IP  
tunnel mode.  I have never said to disallow IP-in-IP mode.  Your  
implementation can still use both IP-in-IP, IP-in-UDP of course.

What I was asking was the technical reason why you want to reject UDP  
tunnel only mode.

As I said, introducing the 'U' flag (or in other words, RFC3519 style  
'F' flag) allows some limited implementation (UDP only  
implementation).  Such implementations are still interoperable with  
full (both IP tunnel and UDP tunnel) implementations.

I simply don't understand why we cannot allow such implementation.   
I'm proposing to keep the current functions completely, and  
requesting to allow some limited implementation which is still  
interoperable.

Regards,
---
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 Fri Mar 30 06:17:07 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXE9J-0008M8-7r; Fri, 30 Mar 2007 06:16:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXE9H-0008Lt-9I
	for mip6@ietf.org; Fri, 30 Mar 2007 06:15:59 -0400
Received: from omta04ps.mx.bigpond.com ([144.140.83.156])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXE9E-0002G8-BA
	for mip6@ietf.org; Fri, 30 Mar 2007 06:15:59 -0400
Received: from oaamta04ps.mx.bigpond.com ([124.191.178.123])
	by omta04ps.mx.bigpond.com with ESMTP id
	<20070330101554.FBLE15631.omta04ps.mx.bigpond.com@oaamta04ps.mx.bigpond.com>;
	Fri, 30 Mar 2007 10:15:54 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta04ps.mx.bigpond.com
	with ESMTP
	id <20070330101553.OLRE14698.oaamta04ps.mx.bigpond.com@PC20005>;
	Fri, 30 Mar 2007 10:15:53 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Keiichi SHIMA'" <keiichi@iijlab.net>
Subject: RE: [Mip6] RE: concensus on [issue94] fixing encapsulation mechanism
	in IPv4 network
Date: Fri, 30 Mar 2007 20:15:50 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdyrldtJK/qTdAYR2CUpZfYbIMJTQABKL/A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <66A793F9-B3CD-4613-81B8-CAD436871287@iijlab.net>
Message-Id: <20070330101553.OLRE14698.oaamta04ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


 > > => Yes there is, I explained it during our discussion and on the  
 > > mailing
 > > list. Others also explained it on the list. I'm attaching 
 > one of my  
 > > emails
 > > again. The idea that you can only support one tunnelling protocol  
 > > is *not*
 > > technically possible as you request it. Please read my email  
 > > attached again.
 > 
 > I think you are explaining the reason why we can allow IP-in-IP  
 > tunnel mode.  I have never said to disallow IP-in-IP mode.  Your  
 > implementation can still use both IP-in-IP, IP-in-UDP of course.
 > 
 > What I was asking was the technical reason why you want to 
 > reject UDP  
 > tunnel only mode.

=> I'm not sure how those two conclusions were made. Your initial suggestion
was to
remove IP in IP, which we won't go over again, now your own compromise
approach was to allow the MN to request UDP only. I'm not sure what I'm
allowing or disallowing but this is a WG concensus call. 

 > 
 > As I said, introducing the 'U' flag (or in other words, 
 > RFC3519 style  
 > 'F' flag) allows some limited implementation (UDP only  
 > implementation).  Such implementations are still interoperable with  
 > full (both IP tunnel and UDP tunnel) implementations.

=> Quoting your comments to Henrik:
  The 'F' flag in RFC3519 is a flag sent from a mobile node to request  
  its home agent to use UDP tunneling mode.  If the home agent  
  understand the RFC3519 'F' flag, then it either 'accepts the UDP  
  tunnel' or 'rejects the binding update'.

If you want option A to suggest that the HA rejects the BU instead of
Accepting it and telling the MN to use IP in IP, I don't have an opinion on
that. But neither this modification, nor option A as I sent it before will
guarantee that the MN will always use UDP *only* because they both depend on
the HA's acceptance. So what is it that you are suggesting we do? and why? 



 > 
 > I simply don't understand why we cannot allow such implementation.   

=> Please explain how your suggestion above makes any difference to the MN.
If the MN only implements UDP then in both cases (whether the BU is rejected
or the HA forces IP in IP) the MN will not be able to communicate with the
HA. Please explain clearly what you're trying to do. I think there is an
issue with trying to fit the standard around a particular implementation
here....

Hesham

 > I'm proposing to keep the current functions completely, and  
 > requesting to allow some limited implementation which is still  
 > interoperable.

=> 

 > 
 > Regards,
 > ---
 > 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 Fri Mar 30 07:28:24 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXFFh-0002WP-K0; Fri, 30 Mar 2007 07:26:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXFFg-0002WG-2Q
	for mip6@ietf.org; Fri, 30 Mar 2007 07:26:40 -0400
Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXFFe-0007Ax-JA
	for mip6@ietf.org; Fri, 30 Mar 2007 07:26:40 -0400
Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 285E537ECA; Fri, 30 Mar 2007 13:25:50 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id D612637E75; Fri, 30 Mar 2007 13:25:49 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id AE06837E52;
	Fri, 30 Mar 2007 13:26:23 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HXFFP-0003xT-4Z; Fri, 30 Mar 2007 13:26:23 +0200
Message-ID: <460CF3E1.1040201@levkowetz.com>
Date: Fri, 30 Mar 2007 13:26:25 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation mechanism
	in	IPv4 network
References: <20070328073355.B105DFB956@sh1.iijlab.net>
	<3738B0C4-E0BE-4BE3-93BB-50FAD8D9CFED@iijlab.net>
	<460A9D8D.2010302@levkowetz.com>
	<56834D20-93BA-4020-8EA6-6ECA4AFCE446@iijlab.net>
In-Reply-To: <56834D20-93BA-4020-8EA6-6ECA4AFCE446@iijlab.net>
X-Enigmail-Version: 0.94.2.0
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: keiichi@iijlab.net, Hesham@elevatemobile.com, mip6@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
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="===============2030424643=="
Errors-To: mip6-bounces@ietf.org

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

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

Hi Keiichi,

on 2007-03-30 11:22 Keiichi SHIMA said the following:
> Hello Henrik,
=2E..
>> See http://tools.ietf.org/html/rfc3519#section-3.1.1
>=20
> I'm not sure I understand the 'F' flag defined in RFC3519, but let me  =

> clarify my understanding.
>=20
> The 'F' flag in RFC3519 is a flag sent from a mobile node to request =20
> its home agent to use UDP tunneling mode.  If the home agent =20
> understand the RFC3519 'F' flag, then it either 'accepts the UDP =20
> tunnel' or 'rejects the binding update'.
>=20
> Is my understanding correct?

Seems so, yes.  But as it also says in the text, if the HA knows
how to do UDP tunnelling, it SHOULD accept it, unless it has been
administratively prohibited (configured to not use it).

> I think the action is different from the Hesham's proposal.  His =20
> proposal allows to override the RFC3519 style 'F' flag at the HA.  =20
> Thus, the HA may accept the BU message with the RFC3519 style 'F' =20
> flag even the HA doesn't allow UDP tunnel.  Since the mobile node is =20
> forcing UDP tunnel, replying with a BA message requesting not to use =20
> UDP is not correct way I think.  (Rejecting the request is =20
> understandable as described in RFC3519)
>=20
> So let me rephrase the option A.
>=20
> A. Add a flag that allows the MN to request UDP tunnelling interface =20
> (independently of the presence of a NAT) from the HA, when sending =20
> the BU.  If the HA accepts the request then the HA replies the BU =20
> with a BA with the 'F (Force UDP)' flag.  Otherwise the HA rejects =20
> the BU with status code "administratively prohibited".

This is the understanding I already had of the meaning of Hesham's
proposal A.

I don't however, understand why we have to use different flag logic
in MIPv4 and MIPv6 -- why not let the BU have a 'Force' flag and the
BA be flag-less and either accept or reject the BU?


	Henrik


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

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

iD8DBQFGDPPheVhrtTJkXCMRAvsUAKDYdZI7uaMd1POrs8Ih4fU5CXxsTgCfTBcl
ihUPlHtFMjgc1/aMPsZtils=
=lvTG
-----END PGP SIGNATURE-----

--------------enig4C41F54CDA4B3822059A9DAF--


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

--===============2030424643==--




From mip6-bounces@ietf.org Fri Mar 30 09:06:56 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXGnb-0005AB-Se; Fri, 30 Mar 2007 09:05:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXGna-0005A5-Ig
	for mip6@ietf.org; Fri, 30 Mar 2007 09:05:46 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXGnY-0000IO-4m
	for mip6@ietf.org; Fri, 30 Mar 2007 09:05:46 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l2UD5enI005092
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 30 Mar 2007 06:05:41 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l2UD5YSr001892;
	Fri, 30 Mar 2007 06:05:39 -0700 (PDT)
Received: from NAEX16.na.qualcomm.com ([10.47.6.157]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Mar 2007 06:04:47 -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] concensus on [issue94] fixing encapsulation
	mechanisminIPv4 network
Date: Fri, 30 Mar 2007 06:04:48 -0700
Message-ID: <2309978910A6A6478C2C7585692B0AF439BF09@NAEX16.na.qualcomm.com>
In-Reply-To: <460A7F83.5020909@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus on [issue94] fixing encapsulation
	mechanisminIPv4 network
thread-index: AcdxSIQo/2v4MO2GTbuL2Gxqqw65FwBgfj/A
References: <F17E4C92F3397E409CCE96C2F16EC7E00E176119@PLSWB09C.ad.sprint.com>	<E1HWSfx-0006Fd-HX@megatron.ietf.org><005901c77140$a94167b0$d3f6200a@amer.cisco.com><460A7C4C.7060503@azairenet.com><006101c77146$ec113ab0$d3f6200a@amer.cisco.com>
	<460A7F83.5020909@azairenet.com>
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Sri Gundavelli" <sgundave@cisco.com>
X-OriginalArrivalTime: 30 Mar 2007 13:04:47.0301 (UTC)
	FILETIME=[FE41EF50:01C772CB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I prefer A, since I think it is good to allow the mobile to request UDP
tunneling for whatever reason.

I agree with Vijay that it is not clear how the MN should decide to make
such request. Indicating that the MN SHOULD NOT be setting the U flag by
default is a good idea. Another BCP type text could instruct
implementers to try setting the U flag if things are failing with no
apparent reason...e.g., registration apparently works but no data are
ever received... maybe due to a FW on the path.

There is also an almost parallel discussion on whether the HA should be
able to override a request or not. I do not think you can "force" an HA
to do anything...this is why such things are called "requests" and not
"commands". I think the correct thing to do here is to allow the HA to
reject the BU with an error code set to something like "UDP Tunneling
not allowed". It is then up to the MN to try to reregister with U flag
set to "0" or to give up.

Thoughts?
George

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Wednesday, March 28, 2007 3:45 PM
> To: Sri Gundavelli
> Cc: mip6@ietf.org; 'Keiichi SHIMA'
> Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation
> mechanisminIPv4 network
>=20
> Sri Gundavelli wrote:
> >
> >
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
> > Sent: Wednesday, March 28, 2007 7:32 AM
> > To: Sri Gundavelli
> > Cc: 'Hesham Soliman'; 'Keiichi SHIMA'; mip6@ietf.org
> > Subject: Re: [Mip6] concensus on [issue94] fixing encapsulation
> mechanism
> > inIPv4 network
> >
> >>> Reason:
> >> >From the MIP4 experience, many times and for various reasons,
> >>> deployments choose UDP Tunneling even in the absence of NAT. The
> >>> ability for the client to hint that choice from any connected
> >>> network is important.
> >
> >> The problem is that the client may not know. It might be
> >> setting the flag all the time. Do we have a mechanism to
> >> say when the MN should be setting this bit?
> >
> > The preference comes from the type of connected access network
> > and other characteristics local to that network. So, the mobile
> > node is in a better position to make that choice. Off course,
> > the home agent always has the final say, in the form of configured
> > policy.
>=20
> So can we then add a sentence saying
>=20
>    It is recommended that the mobile node SHOULD NOT set the 'U'
>    flag by default, since using UDP encapsulation when not
>    required introduces an unnecessary overhead for all data traffic.
:)
>=20
> My preference is still for 'B' though.
>=20
> Vijay
>=20
> >
> > But, sure, the logic as when to enable this on the mobile is
> > difficult. Mostly, it might be an operator initiated explicit
> > setting, on a need basis.
> >
> >
> > Sri
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Fri Mar 30 11:47:16 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXJJD-0007Mc-7A; Fri, 30 Mar 2007 11:46:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXJJC-0007MU-NL
	for mip6@ietf.org; Fri, 30 Mar 2007 11:46:34 -0400
Received: from mail.unilim.fr ([164.81.1.45] helo=smtp.unilim.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXJJB-0002th-Ar
	for mip6@ietf.org; Fri, 30 Mar 2007 11:46:34 -0400
Received: from [164.81.60.82] (sauveron-port.msi.unilim.fr [164.81.60.82])
	(authenticated bits=0)
	by smtp.unilim.fr (8.13.1/8.13.1) with ESMTP id l2UFkTSB019659
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Fri, 30 Mar 2007 17:46:29 +0200
Message-ID: <460D30D5.8040004@xlim.fr>
Date: Fri, 30 Mar 2007 17:46:29 +0200
From: Damien Sauveron <damien.sauveron@xlim.fr>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Univ-Limoges-Greylist: Sender succeeded SMTP AUTH authentication, not
	delayed by milter-greylist-2.0.2 (smtp.unilim.fr [164.81.1.45]);
	Fri, 30 Mar 2007 17:46:29 +0200 (CEST)
X-Univ-Limoges-MailScanner-Information: Serveur Anti-virus Please contact the
	SCI, Univ. of Limoges, for more information
X-Univ-Limoges-MailScanner: Found to be clean
X-Univ-Limoges-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (cached, score=-101.785, requis 6, autolearn=not spam,
	ALL_TRUSTED -1.80, BAYES_40 -0.18, MR_NOT_ATTRIBUTED_IP 0.20,
	SMTP_AUTH -100.00)
X-Univ-Limoges-MailScanner-Envelope-From: damien.sauveron@xlim.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Mip6] [WISTP'2007] 4 Grants for Young Researchers sponsored by
	Nokia
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

*******************************************************************
We apologize in advance if you receive multiple copies of this CFP.
Please disseminate it to your colleagues that could be interested.
*******************************************************************

Workshop in Information Security Theory and Practices 2007: Smart Cards,
Mobile and Ubiquitous Computing Systems
                                  &&
A networking meeting to discuss proposals for the EU FP7

Heraklion, Crete, Greece
May 8-11, 2007

Workshop URL: http://wistp2007.xlim.fr/

Preliminary Program: http://wistp2007.xlim.fr/CFP.html#Preliminary_program

*******************************************************************
4 Grants for Young Researchers (PhD students or in postdoctoral
position) are sponsored by *Nokia*. These grants include accommodation
costs (3 nights in the hotel hosting the workshop) and registration fees
for the Workshop and the FP7 meeting. The travel is NOT funded.
*******************************************************************
Grant application:
  - Selection will be done by the Organizers and Chairs based on a short
CV (1 page maximum), a motivation letter (1 page maximum) and if
possible a recommendation letter
  - Send these documents to wistp2007sec@xlim.fr before the deadline
  - deadline: 6th of April 2007
  - notification of acceptance: 10th of April 2007

The selected applicants will provide one week maximum after the events a
short report (5 to 10 pages) written in english to summarize the
scientific and organizational aspects (to be discussed with the
organizers later).

*******************************************************
We hope you will be interested by this event.
For further inquiries, please contact the secretariat at
wistp2007sec@xlim.fr

Best regards,
-- 
Damien Sauveron





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



From mip6-bounces@ietf.org Fri Mar 30 16:15:09 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXNTK-0002JY-5I; Fri, 30 Mar 2007 16:13:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXNTJ-0002JF-G5
	for mip6@ietf.org; Fri, 30 Mar 2007 16:13:17 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXNTI-0001GQ-1q
	for mip6@ietf.org; Fri, 30 Mar 2007 16:13:17 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l2UKD9db012340; Fri, 30 Mar 2007 23:13:13 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Mar 2007 23:12:50 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Mar 2007 15:12:43 -0500
Received: from 172.19.244.103 ([172.19.244.103]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 30 Mar 2007 20:12:43 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 30 Mar 2007 15:12:57 -0500
Subject: Re: [Mip6] Re: concensus on [issue94] fixing encapsulation
	mechanism in IPv4 network
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Keiichi SHIMA <keiichi@iijlab.net>, Ahmad Muhanna <amuhanna@nortel.com>
Message-ID: <C232D979.32DED%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Re: concensus on [issue94] fixing encapsulation
	mechanism in IPv4 network
Thread-Index: AcdzB86CDVCMSt77EduwYwARJNUNiA==
In-Reply-To: <E1CB97DC-CBCF-4DA7-8F7C-A89B1B0805C4@iijlab.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Mar 2007 20:12:43.0607 (UTC)
	FILETIME=[C6874E70:01C77307]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070330231314-2D978BB0-06F7A6E8/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
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


Hi Keiichi,


On 3/29/07 12:44 AM, "ext Keiichi SHIMA" <keiichi@iijlab.net> wrote:

> Hello,
> 
> On 2007/03/28, at 19:29, Ahmad Muhanna wrote:
> 
>> Sorry for jumping in without previously being involved in the
>> discussion. However, in my mind, HA should have the upper hand of
>> deciding whatever the MN is requesting. If the HA has the right to
>> reject MN BU, it has the right to deny UDP encapsulation.
>> 
>> I believe that should be the correct approach.
> 
> Yes, as long as both nodes have the same features.
> 
> But I am now talking about a mobile node that only supports the UDP
> tunnel mode.  In this case, forcing the IP-in-IP tunnel mode by the
> HA has no meaning because the MN doesn't support the mode.

Only supporting "UDP tunnel mode" by the MN is not an acceptable option.

-Raj

> 
> Regards,
> ---
> 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


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



From mip6-bounces@ietf.org Fri Mar 30 16:29:18 2007
Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXNiG-0005a5-VK; Fri, 30 Mar 2007 16:28:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HXNiF-0005Zj-6h
	for mip6@ietf.org; Fri, 30 Mar 2007 16:28:43 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXNiC-00040N-4G
	for mip6@ietf.org; Fri, 30 Mar 2007 16:28:41 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l2UKS6Ys023770; Fri, 30 Mar 2007 23:28:16 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Mar 2007 23:28:06 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Mar 2007 15:27:54 -0500
Received: from 172.19.244.103 ([172.19.244.103]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 30 Mar 2007 20:27:53 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 30 Mar 2007 15:28:09 -0500
Subject: Re: [Mip6] RE: concensus on [issue94] fixing encapsulation
	mechanism in IPv4 network
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Keiichi SHIMA <keiichi@iijlab.net>,
	Hesham Soliman <Hesham@elevatemobile.com>
Message-ID: <C232DD09.32DF4%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] RE: concensus on [issue94] fixing encapsulation
	mechanism in IPv4 network
Thread-Index: AcdzCe4bLGJRq979EduwYwARJNUNiA==
In-Reply-To: <66A793F9-B3CD-4613-81B8-CAD436871287@iijlab.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Mar 2007 20:27:54.0446 (UTC)
	FILETIME=[E56E4EE0:01C77309]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070330232817-55E5FBB0-2907B82A/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi Keiichi,


On 3/30/07 4:32 AM, "ext Keiichi SHIMA" <keiichi@iijlab.net> wrote:

> Hello Hesham,
> 
> On 2007/03/29, at 14:51, Hesham Soliman wrote:
> 
>>> As I talked to you at the last IETF, my intension is to
>>> allow mobile
>>> nodes that implement only the UDP tunnel mode for v4 traversal
>>> purpose.  Since such nodes don't decapsulate IPvX-in-IPv4
>>> packets for
>>> DS-MIPv6, replying with a BA message rejecting UDP
>>> encapsulation and
>>> forcing IPvX-in-IPv4 mode doesn't work.
>>> 
>>> 
>>> I think you are implicitly assuming IPvX-in-IPv4 is a must
>>> feature.
>>> So you only allow MN and HA that support both IPvX-in-IPv4 and IPvx-
>>> in-UDPv4 modes.  But I think we can also allow UDP only operation.
>>> There is no technical reason to reject the possibility, is
>>> it?
>> 
>> => Yes there is, I explained it during our discussion and on the
>> mailing
>> list. Others also explained it on the list. I'm attaching one of my
>> emails
>> again. The idea that you can only support one tunnelling protocol
>> is *not*
>> technically possible as you request it. Please read my email
>> attached again.
> 
> I think you are explaining the reason why we can allow IP-in-IP
> tunnel mode.  I have never said to disallow IP-in-IP mode.  Your
> implementation can still use both IP-in-IP, IP-in-UDP of course.

Okay... So you agree that depending on the scenario you could use either
IP-in-IP or IP-in-UDP, right?

> 
> What I was asking was the technical reason why you want to reject UDP
> tunnel only mode.

UDP tunnel only mode is less optimal than IP-in-IP.
The MN should (or MUST) be able to support both tunnelling schemes. Why
would you restrict the MN to only using IP-in-UDP in all cases?

> 
> As I said, introducing the 'U' flag (or in other words, RFC3519 style
> 'F' flag) allows some limited implementation (UDP only
> implementation).  Such implementations are still interoperable with
> full (both IP tunnel and UDP tunnel) implementations.

And so far at least the consensus from what I can tell is to have the HA
decide what encapsulation mode to use. Hence if you have an MN that only
implements IP-in-UDP and the HA rejects such encapsulation mode, the MN is
pretty much out-of-luck. And as has been mentioned the MN cannot command the
HA to honor its request for IP-in-UDP encapsulation. The decision point is
the HA and lets stick with that design approach.

> 
> I simply don't understand why we cannot allow such implementation.
> I'm proposing to keep the current functions completely, and
> requesting to allow some limited implementation which is still
> interoperable.

What you are requesting is that if the MN were to request IP-in-UDP
encapsulation, the HA MUST honor it. Otherwise there is no interoperability
with the HA since the MN does not implement IP-in-IP encapsulation.

What is your main argument about or use-case/scenario where you have this
limited implementation (IP-in-UDP only encapsulation) MN?

I guess you do actually have limited interoperability because if the MN
requests IP-in-UDP encapsulation you have a 0.5 probability that the HA will
accept it. So you have interoperability possibility 50% of the time and when
the HA rejects it, well... No connectivity.

-Raj

> 
> Regards,
> ---
> 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


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



