From mip6-bounces@ietf.org Sun Oct 01 11:26:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GU3BD-0007Su-Ht; Sun, 01 Oct 2006 11:24:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GU3BC-0007So-3A
	for mip6@ietf.org; Sun, 01 Oct 2006 11:24:34 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GU3BA-00053s-L7
	for mip6@ietf.org; Sun, 01 Oct 2006 11:24:34 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k91FOTmm023968
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Sun, 1 Oct 2006 08:24:29 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.na.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k91FOS9t011900
	for <mip6@ietf.org>; Sun, 1 Oct 2006 08:24:28 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Oct 2006 08:24:27 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 1 Oct 2006 08:24:25 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A1E9449@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: issue 76: Alt CoA should not be used when traversing IPv4 NAT
thread-index: Acbda5g0mI0GGLabQR+W8+zUxINRfQFjw9ggAJy0kRA=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 01 Oct 2006 15:24:27.0749 (UTC)
	FILETIME=[AF09D150:01C6E56D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Subject: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,=20

This issue will be closed on Tuesday with the text suggested below.=20

Thanks,
Hesham=20

 > -----Original Message-----
 > From: Soliman, Hesham=20
 > Sent: Thursday, September 28, 2006 11:52 PM
 > To: 'mip6@ietf.org'
 > Subject: RE: issue 76: Alt CoA should not be used when=20
 > traversing IPv4 NAT
 >=20
 > Suggested text below to update this issue. I think this=20
 > issue is ready to be closed as accepted with the text below.=20
 > =20
 > Issue description:
 > ------------------
 >=20
 > The draft implicitly reuses altCoA as specified in RFC 3775.
 >=20
 > As a result, in an IPv4 NAT traversal situation, the altCoA=20
 > option will be
 > present with the mapped address containing the IPv4 address=20
 > on the MN side of
 > the NAT.
 >=20
 > And the HA will use that address as opposed to the source of=20
 > the packet to
 > respond, as mandated by MIP6.
 >=20
 > We need to make sure that the HA answers to the IPv4 address=20
 > that is found as
 > source of the BU regardless of the altCoA option.=20
 >=20
 > It might be better to completely omit the option in an IPv4=20
 > traversal situation.
 >=20
 > Analysis:
 > ---------
 >=20
 > The text above requests the relaxation of the requirements=20
 > on the BU message, which currently mandates the use of the=20
 > alt-CoA option when ESP is used, for a BU sent to the HA.=20
 > RFC 3775 does not require the alt-CoA for BUs protected by=20
 > AH as the protection covers the entire packet.=20
 >=20
 > Unfortunately, the Checksum field in the MH does not cover=20
 > the CoA either :(, which would have offered some protection.=20
 >=20
 > Conclusion (Accept issue):
 > --------------------------
 >=20
 > During the last meeting at least 3 people spoke in favour of=20
 > the suggestion in this issue. Both Ryuji and Vijay agreed=20
 > that RFC 3775 should be relaxed for the BU, in addition to=20
 > Pascal, who raised the issue.=20
 >=20
 > The removal of the Alt-CoA poses a threat: a MITM could=20
 > modify the src address which would result in stealing the=20
 > MN's traffic. In order to relax the requirements in 3775,=20
 > while maintaining adequate security we can proceed as follows:
 >=20
 > We remove the alt-CoA in the BU, but add another checksum=20
 > field that can be  =20
 > used to verfiy the CoA in the src address. This field can be=20
 > included in one of the new   =20
 > options in the draft or in a new option. Obviously we would=20
 > still allow the use of AH as in=20
 > 3775.
 >=20
 > Suggested text:
 >=20
 > Add the following section to the spec:
 >=20
 > X.X The Checksum option
 >=20
 > The Checksum option is included in any binding update=20
 > message sent from the mobile
 > node to the home agent while the mobile node is located in=20
 > an IPv4-only network and protects
 > the binding update with IPsec ESP. This option should not be=20
 > used when the binding update
 > is protected with IPsec AH. This option is needed to ensure=20
 > the integrity of the care-of address in the absence of the=20
 > Alternate care-of address option.=20
 >=20
 >        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=20
 > 7 8 9 0 1
 >      =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >       |Option Type    |  Option Len   |             =20
 > Checksum         |
 >      =20
 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 >=20
 > Type TBD
 >=20
 > Length
 >=20
 >=20
 > Checksum=20
 >=20
 >       16-bit unsigned integer.  This field contains the=20
 > checksum of the
 >       Mobility Header.  The checksum is calculated from the=20
 > octet string
 >       consisting of a "pseudo-header" followed by the entire Mobility
 >       Header starting with the Payload Proto field.  The=20
 > checksum is the
 >       16-bit one's complement of the one's complement sum of this
 >       string.
 >=20
 >       The pseudo-header contains IPv6 header fields, as specified in
 >       Section 8.1 of RFC 2460.  The Next Header value used in the
 >       pseudo-header is 2.  The addresses used in the=20
 > pseudo-header are
 >       the addresses that appear in the Source and Destination Address
 >       fields in the IPv6 packet carrying the Mobility Header.
 >=20
 >       Note that while the mobile node is away from home, the=20
 > source address
 >       used for the calculation of the checksum MUST be the=20
 > IPv6 Care-of address
 >       in the IPv6 header.=20
 >=20
 > We also need to add text in sections 4.3 and 4.4 (mobile=20
 > node and HA operation) to require the MN to add this option=20
 > and require the HA to verify it for BUs protected with ESP.=20
 >=20
 > Comments?
 >=20
 > Hesham
 >=20

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



From mip6-bounces@ietf.org Sun Oct 01 17:06:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GU8VM-0002NA-18; Sun, 01 Oct 2006 17:05:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GU8VK-0002Mm-Ko
	for mip6@ietf.org; Sun, 01 Oct 2006 17:05:42 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GU8VJ-0003FA-5c
	for mip6@ietf.org; Sun, 01 Oct 2006 17:05:42 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id B47D78984E;
	Mon,  2 Oct 2006 00:05:37 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 6B4E389808;
	Mon,  2 Oct 2006 00:05:37 +0300 (EEST)
Message-ID: <45202D8A.2080206@piuha.net>
Date: Mon, 02 Oct 2006 00:05:14 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060921)
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: [Mip6] On a network-mobility solution based on Mobile IPv6
References: <451BE2C5.4050602@yahoo.com>
In-Reply-To: <451BE2C5.4050602@yahoo.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: 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

Behcet,
> Have you read
> draft-soliman-netlmm-harmful-00.txt?
> Some people say this is an IAB quality draft.
>
> BTW I am not a member of int-area ML, so I do not know if you already
> commented on this draft in int-area. Maybe you could kindly share your
> views (possibly again) on this ML?
The discussion went on the internet area mailing list
(http://www1.ietf.org/mail-archive/web/int-area/current/mail11.html
-- feel free to subscribe!) and a few other lists as I recall.
It was largely a back and forth discussion between Hesham
and netlmm defenders, and, unsurprisingly, they did not
agree at the end. There was, however, support for the
notion that local and global mobility in can co-exist.

My own opinion? I also believe local and global mobility
management can (and should) co-exist. And I worry about
the economics of the security needed to set up lmm when
the  host is involved. (In fairness I want to say that I also keep
worrying about NETLMM's security model until I see their
mobile node interface draft in front of me.)

I have some sympathy for Hesham's arguments in Section 3.
But its not clear to me that these problems exist in the actual
NETLMM protocol, or at least not all of them. For instance,
all of the network-control related issues appear to assume
that NETLMM is in charge of handover decisions. This is
not the case in the design that the NETLMM WG is working
on; it only attempts to retain the IP environment if the mobile
node decides to use another access link. Of course, there
are L2 control mechanisms but that seems orthogonal
to whatever we do in upper layers.

Anyway, I would like to repeat my request for getting
back to the requirements and problems that we want
to solve. Are the functional or architectural requirements
that cannot be handled by existing protocols or ongoing
work?

--Jari


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



From mip6-bounces@ietf.org Sun Oct 01 20:57:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUC6c-0002I1-HD; Sun, 01 Oct 2006 20:56:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GTaEC-0006fF-5u
	for mip6@ietf.org; Sat, 30 Sep 2006 04:29:44 -0400
Received: from smtp102.biz.mail.re2.yahoo.com ([68.142.229.216])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GTaE7-0000C1-Fz
	for mip6@ietf.org; Sat, 30 Sep 2006 04:29:44 -0400
Received: (qmail 96109 invoked from network); 30 Sep 2006 08:29:38 -0000
Received: from unknown (HELO YEOBS)
	(boonsain.yeo@sensimesh.com@218.186.172.126 with login)
	by smtp102.biz.mail.re2.yahoo.com with SMTP; 30 Sep 2006 08:29:37 -0000
Message-ID: <004201c6e46a$874c03d0$8001a8c0@YEOBS>
From: "Boon Sain YEO" <boonyeo@ieee.org>
To: <Undisclosed-Recipient:;>
Date: Sat, 30 Sep 2006 16:29:10 +0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
X-Mailman-Approved-At: Sun, 01 Oct 2006 20:56:24 -0400
Cc: 
Subject: [Mip6] WCNC 2007 deadeline Fast Approaching
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============1651672293=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1651672293==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003F_01C6E4AD.8EB5EBC0"

This is a multi-part message in MIME format.

------=_NextPart_000_003F_01C6E4AD.8EB5EBC0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

(Apologies for multiple copies received)


Final Call for Papers:      3 October 2006!!!

IEEE Wireless Communications & Networking Conference (WCNC 2007)
11 =96 15 March 2007 /Hong Kong
Make sure you are a part of the first WCNC conference outside North =
America =96 held in Asia=92s world city, Hong Kong , China , The WCNC is =
the one of the world=92s foremost international technical conference for =
engineers and researchers at the forefront of development and deployment =
of wireless technologies.=20
IMPORTANT DATES
Full paper submissions:                     3 October 2006     =20
Notification of acceptance:                 8 December 2006
Camera ready submission:                5 January 2007

ORGANIZATION

General Chairs                                             Technical =
Program Chair
Khaled B. Letaief, Chih-Lin I                        Ross D. Murch

For more WCNC 2007 details & updates please visit:  =
http://www.ieee-wcnc.org







To unsubscribe from this IEEE Communications Society WCNC 2005 CFP =
mailing list=20
send a blank email message to wcnccfp-remove@comsoc.org.=20

You can also request removal by mail. Please send a note with your email =
address=20
and the list name (wcnccfp@comsoc.org) to=20

ComSoc List Removal - IT=20
3 Park Avenue, 17th Floor=20
New York, NY 10016 USA 
------=_NextPart_000_003F_01C6E4AD.8EB5EBC0
Content-Type: text/html;
	charset="Windows-1252"
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=3DWindows-1252">
<STYLE></STYLE>

<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>(Apologies for multiple copies=20
received)</FONT><BR></DIV>
<DIV><IMG alt=3D"" hspace=3D0 =
src=3D"http://www.comsoc.org/confs/email/wcnc2007HK.jpg"=20
align=3Dbaseline border=3D0></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma size=3D5><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 18pt; FONT-FAMILY: Tahoma">Final=20
Call&nbsp;for Papers:&nbsp;&nbsp; &nbsp;<FONT color=3Dnavy><SPAN=20
style=3D"COLOR: navy">&nbsp;&nbsp;3 October=20
2006!!!</SPAN></FONT></SPAN></FONT></B></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><B><FONT =

face=3DArial color=3Dpurple size=3D5><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 18pt; COLOR: purple; FONT-FAMILY: =
Arial">IEEE=20
Wireless Communications &amp; Networking Conference (WCNC=20
2007)<BR></SPAN></FONT></B><B><FONT face=3DArial color=3Dpurple><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: purple; FONT-FAMILY: Arial">11 =96 15 =
March 2007=20
/<U2:PLACE u3:st=3D"on"><U2:PLACE u4:st=3D"on"><ST1:PLACE =
w:st=3D"on">Hong=20
Kong</U2:PLACE></ST1:PLACE></SPAN></FONT></B><BR><B><FONT face=3DArial=20
color=3D#993366><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: #993366; FONT-FAMILY: =
Arial"></U2:PLACE></SPAN></FONT></B><B><I><FONT=20
face=3DArial color=3D#993366 size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; FONT-STYLE: =
italic; FONT-FAMILY: Arial">Make=20
sure you are a part of the first WCNC conference outside North America =
=96 held in=20
Asia=92s world city, <U2:PLACE u5:st=3D"on"><U2:CITY u5:st=3D"on">Hong =
Kong=20
</U2:CITY>, <U2:COUNTRY-REGION u5:st=3D"on">China =
</U2:COUNTRY-REGION></U2:PLACE>,=20
The WCNC is the one of the world=92s foremost international technical =
conference=20
for engineers and researchers at the forefront of development and =
deployment of=20
wireless technologies. </SPAN></FONT></I></B><BR><B><U><FONT =
face=3DArial=20
color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 11pt; COLOR: navy; FONT-FAMILY: =
Arial">IMPORTANT=20
DATES</SPAN></FONT></U></B><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 11pt; COLOR: navy; FONT-FAMILY: =
Arial"><BR></SPAN></FONT></B><FONT=20
face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 11pt; COLOR: navy; FONT-FAMILY: Arial">Full paper=20
submissions:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3 October 2006&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;<BR></SPAN></B>Notification of acceptance:<B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; 8 December 2006<BR></SPAN></B>Camera =
ready=20
submission:<B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
&nbsp;&nbsp; 5 January 2007</SPAN></B></SPAN></FONT><B><FONT =
color=3Dnavy=20
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 11pt; COLOR: =
navy"></SPAN></FONT></B></P>
<P><B><U><FONT face=3DArial color=3Dpurple size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: =
Arial">ORGANIZATION</SPAN></FONT></U></B><B><U><FONT=20
face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT></U></B></P>
<P><EM><B><I><FONT face=3DArial color=3D#993366 size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial">General=20
Chairs &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
Technical Program Chair</SPAN></FONT></I></B></EM><B><FONT face=3DArial=20
color=3D#993366 size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial"><BR><SPAN=20
class=3Dtext-a>Khaled B. Letaief, Chih-Lin=20
I&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;Ross D. Murch</SPAN></SPAN></FONT></B><B><FONT face=3DArial=20
color=3D#993366 size=3D4><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 14pt; COLOR: #993366; =
FONT-FAMILY: Arial"></SPAN></FONT></B></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><B><FONT =

face=3DArial color=3D#993366 size=3D3><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 12pt; COLOR: #993366; =
FONT-FAMILY: Arial">For=20
more WCNC 2007 details &amp; updates</SPAN></FONT></B><B><FONT =
face=3DArial=20
color=3Dnavy><SPAN style=3D"FONT-WEIGHT: bold; COLOR: navy; FONT-FAMILY: =
Arial">=20
</SPAN></FONT></B><B><FONT face=3DArial color=3Dpurple><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: purple; FONT-FAMILY: =
Arial">please</SPAN></FONT></B><B><FONT=20
face=3DArial color=3Dnavy><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: navy; FONT-FAMILY: Arial">=20
</SPAN></FONT></B><B><FONT face=3DArial color=3D#993366><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: #993366; FONT-FAMILY: =
Arial">visit</SPAN></FONT></B><B><FONT=20
face=3DArial color=3Dpurple><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: purple; FONT-FAMILY: Arial">:&nbsp;=20
</SPAN></FONT></B><B><FONT face=3DArial color=3D#993366><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: #993366; FONT-FAMILY: Arial"><A=20
title=3Dhttp://www.ieee-wcnc.org/=20
href=3D"http://www.ieee-wcnc.org/">http://www.ieee-wcnc.org</A></SPAN></F=
ONT><FONT=20
color=3D#993366><SPAN style=3D"COLOR: #993366"></SPAN></FONT></B></P>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><B><FONT =

face=3DArial color=3D#993366 size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial"></SPAN></FONT><FONT=20
color=3D#993366><SPAN=20
style=3D"COLOR: =
#993366"></SPAN></FONT></B>&nbsp;</P></DIV><BR><BR><BR><BR>To=20
unsubscribe from this IEEE Communications Society WCNC 2005 CFP mailing =
list=20
<BR>send a blank email message to wcnccfp-remove@comsoc.org. <BR><BR>You =
can=20
also request removal by mail. Please send a note with your email address =
<BR>and=20
the list name (wcnccfp@comsoc.org) to <BR><BR>ComSoc List Removal - IT =
<BR>3=20
Park Avenue, 17th Floor <BR>New York, NY 10016 USA </BODY></HTML>

------=_NextPart_000_003F_01C6E4AD.8EB5EBC0--



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

--===============1651672293==--





From mip6-bounces@ietf.org Mon Oct 02 08:28:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUMsh-0003Al-Ml; Mon, 02 Oct 2006 08:26:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUMsg-0003Ag-QN
	for mip6@ietf.org; Mon, 02 Oct 2006 08:26:46 -0400
Received: from nf-out-0910.google.com ([64.233.182.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUMsb-0006is-ET
	for mip6@ietf.org; Mon, 02 Oct 2006 08:26:46 -0400
Received: by nf-out-0910.google.com with SMTP id n15so1597925nfc
	for <mip6@ietf.org>; Mon, 02 Oct 2006 05:26:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:subject:user-agent:cc:references:in-reply-to:mime-version:content-disposition:date:content-type:content-transfer-encoding:message-id:sender;
	b=tnLfvFxpdUtlhb9wjjWisRhrw6cq/XwApj52hQM2Qpxwzmhi21Nv313qHmhvAGWHzrh3AUdONTXfNjB0XKXe3UZx310eBMbPBqRlVknioTJQH2/THLrAqhSh6YATFzEyOAEjSvsop+wbmCzDPKLPfyU9EGzbszKHc2pbwieNb5k=
Received: by 10.49.36.6 with SMTP id o6mr9198621nfj;
	Mon, 02 Oct 2006 05:26:40 -0700 (PDT)
Received: from ?192.168.1.106? ( [212.119.9.178])
	by mx.gmail.com with ESMTP id m16sm14997474nfc.2006.10.02.05.26.39;
	Mon, 02 Oct 2006 05:26:39 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: mip6@ietf.org
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review:
	Recharter of Mobility for IPv6 (mip6))
User-Agent: KMail/1.8.2
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>
	<451AE494.8010600@piuha.net> <451D9613.6060106@azairenet.com>
In-Reply-To: <451D9613.6060106@azairenet.com>
MIME-Version: 1.0
Content-Disposition: inline
Date: Mon, 2 Oct 2006 14:27:25 +0200
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <200610021427.26123.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

Some thoughts below:

On Friday 29 September 2006 23:54, Vijay Devarapalli wrote:
> Hi Jari and Dave,
>
> Jari Arkko wrote:
> >
> >> can you send us more information on this? specifically
> >> on what we are supposed to look for. document problems
> >> that we might encounter when MIPv6 is run over multilink
> >> subnets?
> >
> > The basic reference is the new IAB draft,
> > draft-iab-multilink-subnet-issues-00.txt.
>
> I went through this document.
>
> first I was surprised when I saw the following
> text
>
> >    However, other WGs continued to allow for this concept even
> > though it had been rejected in the IPv6 WG.  Mobile IPv6
> > [RFC3775] allows tunnels to mobile nodes to use the same subnet
> > as a home link, with the Home Agent doing layer 3 forwarding
> > between them.
>
> I was surprised to see the MIPv6 home link and the
> tunnels to each mobile node being compared to a
> multi-link subnet. its not a multi-link subnet as
> described in draft-ietf-ipv6-multilink-subnets-00.txt.
> the home agent does not bridge and forward link-scope
> traffic onto the tunnels.

My (perhaps flawed) understanding is that a multilink subnet occurs 
when a subnet prefix is used to number interfaces on different links, 
and an entity forward traffic between those two links. It is not only 
about forwarding link-scope traffic.

If you look at MIPv6 as described per section 8.4. of RFC 3775 this 
AFAICS exactly what happens: The MN numbers its tunnel interface with 
an address in the same subnet prefix that the one used on the home 
link (which is different from the tunnel interface.), and the HA 
forwards traffic:

> 8.4.  IPv6 Home Agents
> 
> [...] 
>
>   o  Every home agent MUST be able to intercept packets (using proxy
>      Neighbor Discovery [12]) addressed to a mobile node for which
>      it is currently serving as the home agent, on that mobile
>      node's home link, while the mobile node is away from home
>      (Section 10.4.1). 
>
>   o  Every home agent MUST be able to encapsulate [15] such
>      intercepted packets in order to tunnel them to the primary
>      care-of address for the mobile node indicated in its binding in
>      the home agent's Binding Cache (Section 10.4.2).

Regarding your observation that link-scope traffic is not forwarded in 
MIPv6, I think that not forwarding link-scope traffic is exactly the 
problem with multilink subnets: lot of applications assume that if 
two nodes share a same subnet prefix, then it means they share a 
link, and they can therefore communicate with link-scope traffic, and 
TTL won't get decremented. This assumption is broken when you have a 
multilink subnet but you do not forward link-scoped traffic.

> the draft later on says
>
> >    A multilink subnet model SHOULD NOT be used.  IETF WG's using,
> > or considering using, multilink subnets today should investigate
> > moving to one of the other models.  For example, Mobile IPv6
> > should investigate having the Home Agent not decrement the Hop
> > Limit, and forward multicast traffic.
>
> currently no link local traffic sent on the home
> link is forwarded over the Mobile IP tunnel to the
> mobile node.

I think that is exactly one of the issue of multilink subnets as used 
in MIPv6 (see above.)

> [...]
>
> the current use of Mobile IP tunnels as an
> extension of the home links does not introduce the
> issues described with multi-link subnets in
> draft-iab-multilink-subnet-issues. or I might be
> missing something big.

IMHO MIPv6 introduce the issues described in the multilink subnet 
draft. 

--julien


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



From mip6-bounces@ietf.org Mon Oct 02 10:47:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUP4x-0000ar-8p; Mon, 02 Oct 2006 10:47:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP4v-0000ab-TR
	for mip6@ietf.org; Mon, 02 Oct 2006 10:47:33 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUP4s-0002dI-Sx
	for mip6@ietf.org; Mon, 02 Oct 2006 10:47:33 -0400
Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 881DF36732;
	Mon,  2 Oct 2006 10:47:28 -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 0625C90408;
	Mon,  2 Oct 2006 14:47:27 +0000 (UTC)
Message-ID: <4521267E.4040907@hp.com>
Date: Mon, 02 Oct 2006 10:47:26 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Julien Laganier <julien.IETF@laposte.net>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	Review:	Recharter of Mobility for IPv6 (mip6))
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<451AE494.8010600@piuha.net>
	<451D9613.6060106@azairenet.com>
	<200610021427.26123.julien.IETF@laposte.net>
In-Reply-To: <200610021427.26123.julien.IETF@laposte.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: mip6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Julien,

Julien Laganier wrote:
> My (perhaps flawed) understanding is that a multilink subnet occurs 
> when a subnet prefix is used to number interfaces on different links, 
> and an entity forward traffic between those two links. It is not only 
> about forwarding link-scope traffic.
> 
> If you look at MIPv6 as described per section 8.4. of RFC 3775 this 
> AFAICS exactly what happens: The MN numbers its tunnel interface with 
> an address in the same subnet prefix that the one used on the home 
> link (which is different from the tunnel interface.), and the HA 
> forwards traffic:

No, the tunnel endpoint on the MN is it's Care-of address, and the other 
end of the tunnel is the HA's address.  It's Home address is configured 
somewhere else, either on its primary nic or on the loopback interface, 
but that's implementation-dependent.

>> 8.4.  IPv6 Home Agents
>>
>> [...] 
>>
>>   o  Every home agent MUST be able to intercept packets (using proxy
>>      Neighbor Discovery [12]) addressed to a mobile node for which
>>      it is currently serving as the home agent, on that mobile
>>      node's home link, while the mobile node is away from home
>>      (Section 10.4.1). 
>>
>>   o  Every home agent MUST be able to encapsulate [15] such
>>      intercepted packets in order to tunnel them to the primary
>>      care-of address for the mobile node indicated in its binding in
>>      the home agent's Binding Cache (Section 10.4.2).
> 
> Regarding your observation that link-scope traffic is not forwarded in 
> MIPv6, I think that not forwarding link-scope traffic is exactly the 
> problem with multilink subnets: lot of applications assume that if 
> two nodes share a same subnet prefix, then it means they share a 
> link, and they can therefore communicate with link-scope traffic, and 
> TTL won't get decremented. This assumption is broken when you have a 
> multilink subnet but you do not forward link-scoped traffic.

I disagree that the MN-HA tunnel is a multilink subnet, it's simply a 
point-to-point tunnel.  The proxying function the HA is doing is 
different from all-out forwarding since it only certain traffic gets 
forwarded, and none of this traffic is forwarded out of the MN onto the 
care-of link, it's just extending the home link to the MN.

-Brian

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



From mip6-bounces@ietf.org Mon Oct 02 11:28:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUPi2-0005YT-9t; Mon, 02 Oct 2006 11:27:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUPi1-0005YO-Gk
	for mip6@ietf.org; Mon, 02 Oct 2006 11:27:57 -0400
Received: from nf-out-0910.google.com ([64.233.182.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUPhw-0008RA-5z
	for mip6@ietf.org; Mon, 02 Oct 2006 11:27:57 -0400
Received: by nf-out-0910.google.com with SMTP id n15so1645138nfc
	for <mip6@ietf.org>; Mon, 02 Oct 2006 08:27:51 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=ZoFQXfHMwRWSuSC0AyRDWcOMI/Rvj+2CkLmlpezEigiaSSas2IopcdwoV38FVACNIZ5Xr2kYp6HLxVSk6T58N5Gt2q37Oeft2DlOjvE2VygfUz6iJezVOY3G61gFbe7AwgnGFbj7ygaGPQQRvmFIyyuILFmeqYH+k/SxRZ6P15w=
Received: by 10.49.29.3 with SMTP id g3mr5839921nfj;
	Mon, 02 Oct 2006 08:27:51 -0700 (PDT)
Received: from ?192.168.1.106? ( [212.119.9.178])
	by mx.gmail.com with ESMTP id z73sm15249596nfb.2006.10.02.08.27.49;
	Mon, 02 Oct 2006 08:27:49 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: Brian Haley <brian.haley@hp.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	=?utf-8?q?Review=3A=09Recharter_of_Mobility_for_IPv6?= (mip6))
Date: Mon, 2 Oct 2006 17:28:35 +0200
User-Agent: KMail/1.8.2
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>
	<200610021427.26123.julien.IETF@laposte.net>
	<4521267E.4040907@hp.com>
In-Reply-To: <4521267E.4040907@hp.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610021728.35965.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: mip6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 Brian,

On Monday 02 October 2006 16:47, Brian Haley wrote:
>
> Julien Laganier wrote:
> > My (perhaps flawed) understanding is that a
> > multilink subnet occurs when a subnet prefix is
> > used to number interfaces on different links, and
> > an entity forward traffic between those two links.
> > It is not only about forwarding link-scope
> > traffic.
> >
> > If you look at MIPv6 as described per section 8.4.
> > of RFC 3775 this AFAICS exactly what happens: The
> > MN numbers its tunnel interface with an address in
> > the same subnet prefix that the one used on the
> > home link (which is different from the tunnel
> > interface.), and the HA forwards traffic:
>
> No, the tunnel endpoint on the MN is it's Care-of
> address, and the other end of the tunnel is the HA's
> address.  It's Home address is configured somewhere
> else, either on its primary nic or on the loopback
> interface, but that's implementation-dependent.

Ok it seems I confused thing -- What I wanted to say 
is: the MN configures an address within a subnet 
prefix used on the home link. When the MN is away from 
home, that address is on a different link (e.g. 
loopback interface) than the home link. Hence the 
subnet is multilink (scattered on multiple links.)

> [...]
> 
> Regarding your observation that link-scope traffic
> > is not forwarded in MIPv6, I think that not
> > forwarding link-scope traffic is exactly the
> > problem with multilink subnets: lot of
> > applications assume that if two nodes share a same
> > subnet prefix, then it means they share a link,
> > and they can therefore communicate with link-scope
> > traffic, and TTL won't get decremented. This
> > assumption is broken when you have a multilink
> > subnet but you do not forward link-scoped traffic.
>
> I disagree that the MN-HA tunnel is a multilink
> subnet, it's simply a point-to-point tunnel.  

See above: I probably failed to express myself clearly 
-- I wasn't saying the MN-HA tunnel is a multilink 
subnet.

> The proxying function the HA is doing is different
> from all-out forwarding since it only certain traffic
> gets forwarded, and none of this traffic is
> forwarded out of the MN onto the care-of link, it's
> just extending the home link to the MN.

I think this "extension" is indeed what causes a 
multilink subnet: the assumption that a subnet does 
not span more than one link is broken, since the same 
subnet span the home link, *and* a virtual link on the 
MN (e.g. a loopback link, a mip interface link, ...) 
Hence the multilink subnet term.

--julien

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



From mip6-bounces@ietf.org Mon Oct 02 11:45:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUPyH-00087s-IJ; Mon, 02 Oct 2006 11:44:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUPyF-00087W-Qo
	for mip6@ietf.org; Mon, 02 Oct 2006 11:44:43 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUPyE-0002Ds-Fm
	for mip6@ietf.org; Mon, 02 Oct 2006 11:44:43 -0400
Received: from [10.1.210.9] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 08:42:42 -0700
Message-ID: <4521337B.9030000@azairenet.com>
Date: Mon, 02 Oct 2006 08:42:51 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Julien Laganier <julien.IETF@laposte.net>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review:
	Recharter of Mobility for IPv6 (mip6))
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<200610021427.26123.julien.IETF@laposte.net>	<4521267E.4040907@hp.com>
	<200610021728.35965.julien.IETF@laposte.net>
In-Reply-To: <200610021728.35965.julien.IETF@laposte.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2006 15:42:42.0419 (UTC)
	FILETIME=[65ECF430:01C6E639]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Julien Laganier wrote:
> See above: I probably failed to express myself clearly 
> -- I wasn't saying the MN-HA tunnel is a multilink 
> subnet.
> 
>> The proxying function the HA is doing is different
>> from all-out forwarding since it only certain traffic
>> gets forwarded, and none of this traffic is
>> forwarded out of the MN onto the care-of link, it's
>> just extending the home link to the MN.
> 
> I think this "extension" is indeed what causes a 
> multilink subnet: the assumption that a subnet does 
> not span more than one link is broken, since the same 
> subnet span the home link, *and* a virtual link on the 
> MN (e.g. a loopback link, a mip interface link, ...) 
> Hence the multilink subnet term.

thats different from saying the issues caused by
multi-link subnets are there for MIPv6 also. please
be more specific.

Vijay

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


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



From mip6-bounces@ietf.org Mon Oct 02 12:07:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUQJz-0000yq-Vt; Mon, 02 Oct 2006 12:07:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQJz-0000yk-1z
	for mip6@ietf.org; Mon, 02 Oct 2006 12:07:11 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUQJw-0005FL-K3
	for mip6@ietf.org; Mon, 02 Oct 2006 12:07:11 -0400
Message-ID: <0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Julien Laganier" <julien.IETF@laposte.net>
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<200610021427.26123.julien.IETF@laposte.net>	<4521267E.4040907@hp.com><200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	Review:Recharter of Mobility for IPv6 (mip6))
Date: Mon, 2 Oct 2006 09:08:42 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 about ND proxying for home address DAD?  I agree that the tunnel is a 
point to point link, but wouldn't the traffic need to be forwarded down the 
tunnel? A quick search of RFC 3775 indicates that nothing is said about the 
TTL, but it could not be decremented on the relayed  DAD traffic because of 
ND security. This isn't like a normal point to point link between a router 
and a host, because there are other hosts on the same link.

             jak

----- Original Message ----- 
From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
To: "Julien Laganier" <julien.IETF@laposte.net>
Cc: <mip6@ietf.org>; "Brian Haley" <brian.haley@hp.com>; "Dave Thaler" 
<dthaler@windows.microsoft.com>
Sent: Monday, October 02, 2006 8:42 AM
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG 
Review:Recharter of Mobility for IPv6 (mip6))


> Julien Laganier wrote:
>> See above: I probably failed to express myself clearly -- I wasn't saying 
>> the MN-HA tunnel is a multilink subnet.
>>
>>> The proxying function the HA is doing is different
>>> from all-out forwarding since it only certain traffic
>>> gets forwarded, and none of this traffic is
>>> forwarded out of the MN onto the care-of link, it's
>>> just extending the home link to the MN.
>>
>> I think this "extension" is indeed what causes a multilink subnet: the 
>> assumption that a subnet does not span more than one link is broken, 
>> since the same subnet span the home link, *and* a virtual link on the MN 
>> (e.g. a loopback link, a mip interface link, ...) Hence the multilink 
>> subnet term.
>
> thats different from saying the issues caused by
> multi-link subnets are there for MIPv6 also. please
> be more specific.
>
> Vijay
>
>>
>> --julien
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6 


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



From mip6-bounces@ietf.org Mon Oct 02 12:29:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUQf6-0008TZ-Hk; Mon, 02 Oct 2006 12:29:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQf5-0008SB-5N
	for mip6@ietf.org; Mon, 02 Oct 2006 12:28:59 -0400
Received: from py-out-1112.google.com ([64.233.166.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUQey-0000Mc-Ri
	for mip6@ietf.org; Mon, 02 Oct 2006 12:28:59 -0400
Received: by py-out-1112.google.com with SMTP id w49so1290386pyg
	for <mip6@ietf.org>; Mon, 02 Oct 2006 09:28:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=hZPVFFFnCoTs7cTbIg3R2NfpsqE6BuIV1j8tmWcmF7drB3EFFVPVfIAX0yUxuCIqC2CUq6cXLyKXj4pfKQuLdBzqZ9OvAipKofRZGI14ovTzJO8mOkE9hFZLhUWpfk0GhXTxKbkrqgMLJ2Bmdm5CpgOKBwfpZZNzdy5bK2OHgic=
Received: by 10.35.95.1 with SMTP id x1mr8046317pyl;
	Mon, 02 Oct 2006 09:28:52 -0700 (PDT)
Received: from ?192.168.1.106? ( [212.119.9.178])
	by mx.gmail.com with ESMTP id 15sm2255251nzn.2006.10.02.09.28.51;
	Mon, 02 Oct 2006 09:28:52 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: "James Kempf" <kempf@docomolabs-usa.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	Review:Recharter of Mobility for IPv6 (mip6))
Date: Mon, 2 Oct 2006 18:29:34 +0200
User-Agent: KMail/1.8.2
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
In-Reply-To: <0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610021829.34993.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 Monday 02 October 2006 18:08, James Kempf wrote:
> What about ND proxying for home address DAD?  I
> agree that the tunnel is a point to point link, but
> wouldn't the traffic need to be forwarded down the
> tunnel? A quick search of RFC 3775 indicates that 
> nothing is said about the TTL, but it could not be
> decremented on the relayed  DAD traffic because of
> ND security.

I don't think the issue is specific to DAD, it's rather 
generic to SEND: CGA ownership has an intrinsic 
conflict with proxying.

When the MN is off-link the HA can't proxy ND by 
replying directly with a NA to a NS sent by an on-link 
host because it doesn't own the MN IP address (i.e. it 
doesn't know the public key generating the MN's CGA)

The alternative would be that the HA proxy ND by 
relaying NSs sent by on-link hosts to the MN, and NAs 
replied by the MN to those hosts while rewriting the 
target link-layer address. This wouldn't work either, 
as the HA cannot rewrite the link-layer address since 
it is signed by the MN.

> This isn't like a normal point to point 
> link between a router and a host, because there are
> other hosts on the same link.

I'd rather say: This isn't like a normal subnet used to 
number a pt-2-pt link between a router and a host, 
because there are other hosts on the same subnet.

--julien

> ----- Original Message -----
> From: "Vijay Devarapalli"
> <vijay.devarapalli@azairenet.com> To: "Julien
> Laganier" <julien.IETF@laposte.net> Cc:
> <mip6@ietf.org>; "Brian Haley" <brian.haley@hp.com>;
> "Dave Thaler" <dthaler@windows.microsoft.com>
> Sent: Monday, October 02, 2006 8:42 AM
> Subject: Re: Multi-link subnets and MIPv6 (was Re:
> [Mip6] Re: WG Review:Recharter of Mobility for IPv6
> (mip6))
>
> > Julien Laganier wrote:
> >> See above: I probably failed to express myself
> >> clearly -- I wasn't saying the MN-HA tunnel is a
> >> multilink subnet.
> >>
> >>> The proxying function the HA is doing is
> >>> different from all-out forwarding since it only
> >>> certain traffic gets forwarded, and none of this
> >>> traffic is forwarded out of the MN onto the
> >>> care-of link, it's just extending the home link
> >>> to the MN.
> >>
> >> I think this "extension" is indeed what causes a
> >> multilink subnet: the assumption that a subnet
> >> does not span more than one link is broken, since
> >> the same subnet span the home link, *and* a
> >> virtual link on the MN (e.g. a loopback link, a
> >> mip interface link, ...) Hence the multilink
> >> subnet term.
> >
> > thats different from saying the issues caused by
> > multi-link subnets are there for MIPv6 also.
> > please be more specific.
> >
> > Vijay
> >
> >> --julien
> >>
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Mon Oct 02 12:32:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUQie-0002f4-NN; Mon, 02 Oct 2006 12:32:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQid-0002eV-IG
	for mip6@ietf.org; Mon, 02 Oct 2006 12:32:39 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUQic-0001b4-9j
	for mip6@ietf.org; Mon, 02 Oct 2006 12:32:39 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel6.hp.com (Postfix) with ESMTP id 96370355C6;
	Mon,  2 Oct 2006 12:32:35 -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 CAC3F90552;
	Mon,  2 Oct 2006 16:32:34 +0000 (UTC)
Message-ID: <45213F20.6040005@hp.com>
Date: Mon, 02 Oct 2006 12:32:32 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	Review:Recharter of Mobility for IPv6 (mip6))
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<200610021427.26123.julien.IETF@laposte.net>	<4521267E.4040907@hp.com><200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
In-Reply-To: <0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: mip6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> What about ND proxying for home address DAD?  I agree that the tunnel is 
> a point to point link, but wouldn't the traffic need to be forwarded 
> down the tunnel? A quick search of RFC 3775 indicates that nothing is 
> said about the TTL, but it could not be decremented on the relayed  DAD 
> traffic because of ND security.

HA does DAD (and all ND on home link) for MN when it's not home, this 
traffic is never forwarded.  The hoplimit on "normal" IPv6 traffic is 
decremented on traffic entering the tunnel, at least in my implementation.

> This isn't like a normal point to point 
> link between a router and a host, because there are other hosts on the 
> same link.

I don't understand... on the tunnel?  There's only one host at the end 
of the tunnel.

-Brian

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



From mip6-bounces@ietf.org Mon Oct 02 12:58:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUR72-0005BV-T3; Mon, 02 Oct 2006 12:57:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUR71-00056o-Oa
	for mip6@ietf.org; Mon, 02 Oct 2006 12:57:51 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUR70-0008UI-Bi
	for mip6@ietf.org; Mon, 02 Oct 2006 12:57:51 -0400
Message-ID: <0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Brian Haley" <brian.haley@hp.com>
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<200610021427.26123.julien.IETF@laposte.net>	<4521267E.4040907@hp.com><200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
	<45213F20.6040005@hp.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	Review:Recharter of Mobility for IPv6 (mip6))
Date: Mon, 2 Oct 2006 09:59:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: mip6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


> James Kempf wrote:
>> What about ND proxying for home address DAD?  I agree that the tunnel is 
>> a point to point link, but wouldn't the traffic need to be forwarded down 
>> the tunnel? A quick search of RFC 3775 indicates that nothing is said 
>> about the TTL, but it could not be decremented on the relayed  DAD 
>> traffic because of ND security.
>
> HA does DAD (and all ND on home link) for MN when it's not home, this 
> traffic is never forwarded.  The hoplimit on "normal" IPv6 traffic is 
> decremented on traffic entering the tunnel, at least in my implementation.
>

Right, that would solve the problem.

>> This isn't like a normal point to point link between a router and a host, 
>> because there are other hosts on the same link.
>
> I don't understand... on the tunnel?  There's only one host at the end of 
> the tunnel.
>

I was thinking of the case where the HA forwards the ND traffic from an MN 
to other MNs through tunnels, but, as you point out, this isn't necessary.

There is still the issue of secure proxying, though, as Julien has pointed 
out. This topic has come up now and then over the years, and we had a BAR 
BOF the last time IETF was in San Diego to discuss it. Greg Daley did a 
draft (probably expired now) describing solutions that do not require 
protocol changes, I did a draft for MOBOPTS about something more 
sophisticated but requiring more protocol changes.

Do people care about this issue? The easiest way to solve it is to put 
something in RFC 3775bis that says: "if you are concerned about proxy ND 
security, don't configure a home link in a way that allows nodes to directly 
attach to it."  But maybe that's too restrictive.

            jak 


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



From mip6-bounces@ietf.org Mon Oct 02 13:13:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GURMW-0008Lk-51; Mon, 02 Oct 2006 13:13:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GURMU-0008LG-EF
	for mip6@ietf.org; Mon, 02 Oct 2006 13:13:50 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURMT-0005Ox-0r
	for mip6@ietf.org; Mon, 02 Oct 2006 13:13:50 -0400
Received: from [10.1.201.19] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 10:11:47 -0700
Message-ID: <45214851.30602@azairenet.com>
Date: Mon, 02 Oct 2006 10:11:45 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review:
	Recharter of Mobility for IPv6 (mip6))
References: <20061002165744.23466.qmail@web60325.mail.yahoo.com>
In-Reply-To: <20061002165744.23466.qmail@web60325.mail.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2006 17:11:48.0018 (UTC)
	FILETIME=[D826A120:01C6E645]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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

Behcet Sarikaya wrote:
> Hello Vijay,
>   I could not see the second quote
>  >    A multilink subnet model SHOULD NOT be used.  IETF WG's using, or
>  >    considering using, multilink subnets today should investigate moving  
>  >    to one of the other models.  For example, Mobile IPv6 should
>  >    investigate having the Home Agent not decrement the Hop Limit, and
>  >    forward multicast traffic.
> 
> in Dave's draft, how did you get this? Is there a new version (-01)?

in section 4.1

Vijay

>  
> Behcet
> ----- Original Message ----
> From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
> To: Jari Arkko <jari.arkko@piuha.net>
> Cc: mip6@ietf.org; Dave Thaler <dthaler@windows.microsoft.com>
> Sent: Friday, September 29, 2006 4:54:27 PM
> Subject: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review: 
> Recharter of Mobility for IPv6 (mip6))
> 
> Hi Jari and Dave,
> 
> Jari Arkko wrote:
>  > Hi Vijay,
>  >> can you send us more information on this? specifically
>  >> on what we are supposed to look for. document problems
>  >> that we might encounter when MIPv6 is run over multilink
>  >> subnets?
> 
>  > The basic reference is the new IAB draft,
>  > draft-iab-multilink-subnet-issues-00.txt.
> 
> I went through this document.
> 
> first I was surprised when I saw the following
> text
> 
>  >    However, other WGs continued to allow for this concept even though
>  >    it had been rejected in the IPv6 WG.  Mobile IPv6 [RFC3775] allows
>  >    tunnels to mobile nodes to use the same subnet as a home link, with
>  >    the Home Agent doing layer 3 forwarding between them.
> 
> I was surprised to see the MIPv6 home link and the
> tunnels to each mobile node being compared to a
> multi-link subnet. its not a multi-link subnet as
> described in draft-ietf-ipv6-multilink-subnets-00.txt.
> the home agent does not bridge and forward link-scope
> traffic onto the tunnels.
> 
> the draft later on says
> 
>  >    A multilink subnet model SHOULD NOT be used.  IETF WG's using, or
>  >    considering using, multilink subnets today should investigate moving  
>  >    to one of the other models.  For example, Mobile IPv6 should
>  >    investigate having the Home Agent not decrement the Hop Limit, and
>  >    forward multicast traffic.
> 
> currently no link local traffic sent on the home
> link is forwarded over the Mobile IP tunnel to the
> mobile node.
> 
> regarding forwarding multicast traffic RFC 3775
> says the following.
> 
>     Interception and tunneling of the following multicast addressed
>     packets on the home network are only done if the home agent supports
>     multicast group membership control messages from the mobile node as
>     described in the next section.  Tunneling of multicast packets to a
>     mobile node follows similar limitations to those defined above for
>     unicast packets addressed to the mobile node's link-local and site-
>     local addresses.  Multicast packets addressed to a multicast address
>     with link-local scope [3], to which the mobile node is subscribed,
>     MUST NOT be tunneled to the mobile node.  These packets SHOULD be
>     silently discarded (after delivering to other local multicast
>     recipients).  Multicast packets addressed to a multicast address with
>     a scope larger than link-local, but smaller than global (e.g., site-
>     local and organization-local [3], to which the mobile node is
>     subscribed, SHOULD NOT be tunneled to the mobile node.  Multicast
>     packets addressed with a global scope, to which the mobile node has
>     successfully subscribed, MUST be tunneled to the mobile node.
> 
>  > I would like to see documentation of how
>  > Mobile IPv6 is affected, and possibly, a short
>  > RFC that updates RFC 3775 to remove or
>  > reduce the problems.
> 
> the current use of Mobile IP tunnels as an
> extension of the home links does not introduce the
> issues described with multi-link subnets in
> draft-iab-multilink-subnet-issues. or I might be
> missing something big.
> 
> comments?
> 
> 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 Mon Oct 02 13:15:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GURNz-0000x7-JC; Mon, 02 Oct 2006 13:15:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GURNy-0000x2-TM
	for mip6@ietf.org; Mon, 02 Oct 2006 13:15:22 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURNx-0005bH-Io
	for mip6@ietf.org; Mon, 02 Oct 2006 13:15:22 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k92HFJvu006859
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 2 Oct 2006 10:15:20 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k92HF0ls027542; Mon, 2 Oct 2006 10:15:18 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Oct 2006 10:14:27 -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: Multi-link subnets and MIPv6 (was Re: [Mip6] Re:
	WGReview:Recharter of Mobility for IPv6 (mip6))
Date: Mon, 2 Oct 2006 10:14:22 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A1E94A9@NAEX14.na.qualcomm.com>
In-Reply-To: <200610021829.34993.julien.IETF@laposte.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Multi-link subnets and MIPv6 (was Re: [Mip6] Re:
	WGReview:Recharter of Mobility for IPv6 (mip6))
thread-index: AcbmQdE2lIYNso14Qs+KdYewUcoXkwAAwG8A
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 02 Oct 2006 17:14:27.0949 (UTC)
	FILETIME=[377A29D0:01C6E646]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I think we might need to distinguish between ND-related issues with
multi-link subnets (and the consequent relay/proxy of ND messages) and
the situation in MIPv6.=20

There are two slightly different threads that I think are being
discussed on the list:=20

1. Defining multi-link subnets in general and deciding whether MIPv6
falls under such category and therefore comes with all the issues
related to multi-link subnet?

2. Addressing multi-link subnet issues in MIPv6 and investigating
whether there are problems in the *context of MIPv6*.=20

Of course addressing 2) implies that we agree the MIPv6 as a concept
creates a multi-link subnet. It would be useful IMO to address 1)
without worrying about the consequences ;)

Another related question to 1) above: If we assume the p2p tunnel
created by MIPv6 is effectively a multi-link subnet, can we also make
that assumption about VPN technologies out there? I'm just interested in
scoping this discussion to the issues that matter to this WG rather than
taking potentially larger issues related to all technologies that
introduce a model that would fall under the multi-link umbrella.=20

So, I guess my question is, what are the problematic multi-link aspects
that we want to discuss here? ND seems to be a large component, should
we start with that?=20

Sorry for putting more questions than answers!=20

Hesham
=20

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



From mip6-bounces@ietf.org Mon Oct 02 13:16:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUROv-0001gk-QL; Mon, 02 Oct 2006 13:16:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUROv-0001gf-9z
	for mip6@ietf.org; Mon, 02 Oct 2006 13:16:21 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUROo-0005c0-CT
	for mip6@ietf.org; Mon, 02 Oct 2006 13:16:21 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6I000HEQSNCS@szxga01-in.huawei.com> for
	mip6@ietf.org; Tue, 03 Oct 2006 01:19:35 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6I008UHQSM63@szxga01-in.huawei.com> for
	mip6@ietf.org; Tue, 03 Oct 2006 01:19:35 +0800 (CST)
Received: from [127.0.0.1] ([10.124.12.208])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J6I00CHZR7GUW@szxml04-in.huawei.com> for
	mip6@ietf.org; Tue, 03 Oct 2006 01:28:32 +0800 (CST)
Date: Mon, 02 Oct 2006 12:15:21 -0500
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review:
	Recharter of Mobility for IPv6 (mip6))
To: mip6@ietf.org
Message-id: <45214929.8080609@yahoo.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
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>
Errors-To: mip6-bounces@ietf.org

Hello Vijay,
  I could not see the second quote

 >    A multilink subnet model SHOULD NOT be used.  IETF WG's using, or
 >    considering using, multilink subnets today should investigate moving  
 >    to one of the other models.  For example, Mobile IPv6 should
 >    investigate having the Home Agent not decrement the Hop Limit, and
 >    forward multicast traffic.

in Dave's draft, how did you get this? Is there a new version (-01)?
 
Behcet
----- Original Message ----
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: mip6@ietf.org; Dave Thaler <dthaler@windows.microsoft.com>
Sent: Friday, September 29, 2006 4:54:27 PM
Subject: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review: 
Recharter of Mobility for IPv6 (mip6))

Hi Jari and Dave,

Jari Arkko wrote:
 > Hi Vijay,
 >> can you send us more information on this? specifically
 >> on what we are supposed to look for. document problems
 >> that we might encounter when MIPv6 is run over multilink
 >> subnets?

 > The basic reference is the new IAB draft,
 > draft-iab-multilink-subnet-issues-00.txt.

I went through this document.

first I was surprised when I saw the following
text

 >    However, other WGs continued to allow for this concept even though
 >    it had been rejected in the IPv6 WG.  Mobile IPv6 [RFC3775] allows
 >    tunnels to mobile nodes to use the same subnet as a home link, with
 >    the Home Agent doing layer 3 forwarding between them.

I was surprised to see the MIPv6 home link and the
tunnels to each mobile node being compared to a
multi-link subnet. its not a multi-link subnet as
described in draft-ietf-ipv6-multilink-subnets-00.txt.
the home agent does not bridge and forward link-scope
traffic onto the tunnels.

the draft later on says

 >    A multilink subnet model SHOULD NOT be used.  IETF WG's using, or
 >    considering using, multilink subnets today should investigate moving  
 >    to one of the other models.  For example, Mobile IPv6 should
 >    investigate having the Home Agent not decrement the Hop Limit, and
 >    forward multicast traffic.

currently no link local traffic sent on the home
link is forwarded over the Mobile IP tunnel to the
mobile node.

regarding forwarding multicast traffic RFC 3775
says the following.

    Interception and tunneling of the following multicast addressed
    packets on the home network are only done if the home agent supports
    multicast group membership control messages from the mobile node as
    described in the next section.  Tunneling of multicast packets to a
    mobile node follows similar limitations to those defined above for
    unicast packets addressed to the mobile node's link-local and site-
    local addresses.  Multicast packets addressed to a multicast address
    with link-local scope [3], to which the mobile node is subscribed,
    MUST NOT be tunneled to the mobile node.  These packets SHOULD be
    silently discarded (after delivering to other local multicast
    recipients).  Multicast packets addressed to a multicast address with
    a scope larger than link-local, but smaller than global (e.g., site-
    local and organization-local [3], to which the mobile node is
    subscribed, SHOULD NOT be tunneled to the mobile node.  Multicast
    packets addressed with a global scope, to which the mobile node has
    successfully subscribed, MUST be tunneled to the mobile node.

 > I would like to see documentation of how
 > Mobile IPv6 is affected, and possibly, a short
 > RFC that updates RFC 3775 to remove or
 > reduce the problems.

the current use of Mobile IP tunnels as an
extension of the home links does not introduce the
issues described with multi-link subnets in
draft-iab-multilink-subnet-issues. or I might be
missing something big.

comments?

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 Mon Oct 02 13:23:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GURWD-0008Cv-FO; Mon, 02 Oct 2006 13:23:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GURWC-0008Cq-DT
	for mip6@ietf.org; Mon, 02 Oct 2006 13:23:52 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURWB-0001Er-3S
	for mip6@ietf.org; Mon, 02 Oct 2006 13:23:52 -0400
Received: from [10.1.201.19] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 10:21:50 -0700
Message-ID: <45214AB0.7050905@azairenet.com>
Date: Mon, 02 Oct 2006 10:21:52 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<200610021427.26123.julien.IETF@laposte.net>	<4521267E.4040907@hp.com><200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
	<45213F20.6040005@hp.com>
	<0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
In-Reply-To: <0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2006 17:21:50.0874 (UTC)
	FILETIME=[3F7B27A0:01C6E647]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: [Mip6] SeND and proxy ND (was Re: Multi-link subnets and MIPv6)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:

> There is still the issue of secure proxying, 

its a separate issue. so I changed the subject.

though, as Julien has
> pointed out. This topic has come up now and then over the years, and we 
> had a BAR BOF the last time IETF was in San Diego to discuss it. Greg 
> Daley did a draft (probably expired now) describing solutions that do 
> not require protocol changes, I did a draft for MOBOPTS about something 
> more sophisticated but requiring more protocol changes.
> 
> Do people care about this issue? 

nope, not yet. nobody yet is using SeND and proxy
ND together on the MIP6 home link.

 > The easiest way to solve it is to put
> something in RFC 3775bis that says: "if you are concerned about proxy ND 
> security, don't configure a home link in a way that allows nodes to 
> directly attach to it."  But maybe that's too restrictive.

I don't see SeND being used on the MIPv6 home link
anywhere.

however, its true that additional work is needed
to make SeND and proxy ND work together. its not
specific to MIPv6 only.

Vijay

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



From mip6-bounces@ietf.org Mon Oct 02 14:00:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUS5P-0000uf-3s; Mon, 02 Oct 2006 14:00:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUS5N-0000j9-3W
	for mip6@ietf.org; Mon, 02 Oct 2006 14:00:13 -0400
Received: from py-out-1112.google.com ([64.233.166.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURvv-0000Qp-Ea
	for mip6@ietf.org; Mon, 02 Oct 2006 13:50:28 -0400
Received: by py-out-1112.google.com with SMTP id w49so1311261pyg
	for <mip6@ietf.org>; Mon, 02 Oct 2006 10:50:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=BYxUGIopDEYxy7dMlbbTsy7dMmJhqDtyGuT+d0oNhGZGe2qikMYInWbildbENZvnPtEUWf3Jyr1jEvbAo1EUTsR5OD/6fHlKZGsw/B5CBU13Doqa8YzMnHWjXQlhLsXuXeavE3/rs3B6sYY352isZg4OC8CGZ64IFF9pkVZKMP4=
Received: by 10.35.34.20 with SMTP id m20mr13575718pyj;
	Mon, 02 Oct 2006 10:50:26 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Mon, 2 Oct 2006 10:50:26 -0700 (PDT)
Message-ID: <729b68be0610021050x21b4a884m473986de66b9c6b3@mail.gmail.com>
Date: Mon, 2 Oct 2006 19:50:26 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG
	Review:Recharter of Mobility for IPv6 (mip6))
In-Reply-To: <0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>
	<200610021427.26123.julien.IETF@laposte.net> <4521267E.4040907@hp.com>
	<200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
	<45213F20.6040005@hp.com>
	<0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

IMHO, maybe, it would be time to re-active SEND WG. The different reasons I see:
o the main one, to re-work on the RFC 3971
- to reduce or to solve the issue regarding the fact that SEND only
secures the IP address of a SEND node and not the link "IP address -
link address" which, IIRC, was one of the initial goal of this WG.
- to integrate feedbacks from SEND implementors (even if, personally,
I only know one: the NTT's public implementation)
o to re-work on the RFC 3972
- to have a better/suited place for the work on draft-bagnulo-multiple-hash-cga
o to work on ND proxy used in conjunction with SEND

Comments?

Sorry if this reply is out of scope the initial thread.

Best regards.

JMC.

2006/10/2, James Kempf <kempf@docomolabs-usa.com>:
>
> > James Kempf wrote:
> >> What about ND proxying for home address DAD?  I agree that the tunnel is
> >> a point to point link, but wouldn't the traffic need to be forwarded down
> >> the tunnel? A quick search of RFC 3775 indicates that nothing is said
> >> about the TTL, but it could not be decremented on the relayed  DAD
> >> traffic because of ND security.
> >
> > HA does DAD (and all ND on home link) for MN when it's not home, this
> > traffic is never forwarded.  The hoplimit on "normal" IPv6 traffic is
> > decremented on traffic entering the tunnel, at least in my implementation.
> >
>
> Right, that would solve the problem.
>
> >> This isn't like a normal point to point link between a router and a host,
> >> because there are other hosts on the same link.
> >
> > I don't understand... on the tunnel?  There's only one host at the end of
> > the tunnel.
> >
>
> I was thinking of the case where the HA forwards the ND traffic from an MN
> to other MNs through tunnels, but, as you point out, this isn't necessary.
>
> There is still the issue of secure proxying, though, as Julien has pointed
> out. This topic has come up now and then over the years, and we had a BAR
> BOF the last time IETF was in San Diego to discuss it. Greg Daley did a
> draft (probably expired now) describing solutions that do not require
> protocol changes, I did a draft for MOBOPTS about something more
> sophisticated but requiring more protocol changes.
>
> Do people care about this issue? The easiest way to solve it is to put
> something in RFC 3775bis that says: "if you are concerned about proxy ND
> security, don't configure a home link in a way that allows nodes to directly
> attach to it."  But maybe that's too restrictive.
>
>             jak
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Mon Oct 02 14:00:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUS5T-00015h-PV; Mon, 02 Oct 2006 14:00:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUS5T-00014Z-5W
	for mip6@ietf.org; Mon, 02 Oct 2006 14:00:19 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURtd-00008a-4V
	for mip6@ietf.org; Mon, 02 Oct 2006 13:48:07 -0400
Received: from [10.1.201.19] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 10:46:04 -0700
Message-ID: <4521505B.5070002@azairenet.com>
Date: Mon, 02 Oct 2006 10:46:03 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6]
	Re:	WGReview:Recharter of Mobility for IPv6 (mip6))
References: <7EB20EA0938B4D42A2D82689365C9B7A1E94A9@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A1E94A9@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2006 17:46:04.0837 (UTC)
	FILETIME=[A21C4D50:01C6E64A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mip6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> I think we might need to distinguish between ND-related issues with
> multi-link subnets (and the consequent relay/proxy of ND messages) and
> the situation in MIPv6. 
> 
> There are two slightly different threads that I think are being
> discussed on the list: 
> 
> 1. Defining multi-link subnets in general and deciding whether MIPv6
> falls under such category and therefore comes with all the issues
> related to multi-link subnet?

agree. this is what we should focus on.

> Another related question to 1) above: If we assume the p2p tunnel
> created by MIPv6 is effectively a multi-link subnet, can we also make
> that assumption about VPN technologies out there? 

I would like to second this.

Vijay

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



From mip6-bounces@ietf.org Mon Oct 02 14:00:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUS5J-0000YE-7i; Mon, 02 Oct 2006 14:00:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUS5H-0000PZ-Sv
	for mip6@ietf.org; Mon, 02 Oct 2006 14:00:08 -0400
Received: from py-out-1112.google.com ([64.233.166.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURxv-0000fZ-5t
	for mip6@ietf.org; Mon, 02 Oct 2006 13:52:32 -0400
Received: by py-out-1112.google.com with SMTP id w49so1311777pyg
	for <mip6@ietf.org>; Mon, 02 Oct 2006 10:52:29 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=osykPhrYh5nDBA6TGfgRNxoxahabaEv6QukAuDtUoJcp8uoxpqL48zf2XNiU0WliyiqILWfoDgTuUPe+pj/fkvTyQScUDnEEzby2qM5Xv6Jc3omMVZOd26tmkzJW9DaQohrjeGIBw6xT6JE34mWOO+QdB4McMzQ6OcVamHNjKhk=
Received: by 10.35.48.15 with SMTP id a15mr7929794pyk;
	Mon, 02 Oct 2006 10:52:29 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Mon, 2 Oct 2006 10:52:29 -0700 (PDT)
Message-ID: <729b68be0610021052x4aa5df4dl851bf7880fecfadc@mail.gmail.com>
Date: Mon, 2 Oct 2006 19:52:29 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] SeND and proxy ND (was Re: Multi-link subnets and MIPv6)
In-Reply-To: <45214AB0.7050905@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>
	<200610021427.26123.julien.IETF@laposte.net> <4521267E.4040907@hp.com>
	<200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
	<45213F20.6040005@hp.com>
	<0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
	<45214AB0.7050905@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	James Kempf <kempf@docomolabs-usa.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi again,

copy/past of my previous mail in the right thread this time :)

"Hi,

IMHO, maybe, it would be time to re-active SEND WG. The different reasons I see:
o the main one, to re-work on the RFC 3971
- to reduce or to solve the issue regarding the fact that SEND only
secures the IP address of a SEND node and not the link "IP address -
link address" which, IIRC, was one of the initial goal of this WG.
- to integrate feedbacks from SEND implementors (even if, personally,
I only know one: the NTT's public implementation)
o to re-work on the RFC 3972
- to have a better/suited place for the work on draft-bagnulo-multiple-hash-cga
o to work on ND proxy used in conjunction with SEND

Comments?

Sorry if this reply is out of scope the initial thread.

Best regards.

JMC."

2006/10/2, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
> James Kempf wrote:
>
> > There is still the issue of secure proxying,
>
> its a separate issue. so I changed the subject.
>
> though, as Julien has
> > pointed out. This topic has come up now and then over the years, and we
> > had a BAR BOF the last time IETF was in San Diego to discuss it. Greg
> > Daley did a draft (probably expired now) describing solutions that do
> > not require protocol changes, I did a draft for MOBOPTS about something
> > more sophisticated but requiring more protocol changes.
> >
> > Do people care about this issue?
>
> nope, not yet. nobody yet is using SeND and proxy
> ND together on the MIP6 home link.
>
>  > The easiest way to solve it is to put
> > something in RFC 3775bis that says: "if you are concerned about proxy ND
> > security, don't configure a home link in a way that allows nodes to
> > directly attach to it."  But maybe that's too restrictive.
>
> I don't see SeND being used on the MIPv6 home link
> anywhere.
>
> however, its true that additional work is needed
> to make SeND and proxy ND work together. its not
> specific to MIPv6 only.
>
> 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 Mon Oct 02 14:00:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUS4u-0007a8-Qc; Mon, 02 Oct 2006 13:59:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUS4t-0007WI-Rr
	for mip6@ietf.org; Mon, 02 Oct 2006 13:59:43 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUS2n-0001TC-Rp
	for mip6@ietf.org; Mon, 02 Oct 2006 13:57:35 -0400
Message-ID: <0f5001c6e64c$752fd5d0$5a6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>
	<200610021427.26123.julien.IETF@laposte.net>
	<4521267E.4040907@hp.com>
	<200610021728.35965.julien.IETF@laposte.net>
	<4521337B.9030000@azairenet.com>
	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>
	<45213F20.6040005@hp.com>
	<0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
	<729b68be0610021050x21b4a884m473986de66b9c6b3@mail.gmail.com>
Subject: Reactivating SEND (was: Re: Multi-link subnets and MIPv6 (was Re:
	[Mip6] Re: WG Review:Recharter of Mobility for IPv6 (mip6)))
Date: Mon, 2 Oct 2006 10:59:08 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: mip6@ietf.org, Brian Haley <brian.haley@hp.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 changed the subject again to reflect the change in thread topic.

I've had some reports of interoperability issues with Docomo's 
implementation of SEND so it's possible there is a need for an update of the 
spec. I know of other implementations, but they are not being publically 
distributed.

But the question has always been whether there is enough interest in 
implementation and energy to address lingering issues to restart the WG. 
Vijay's opinion on whether proxy SEND is an issue for MIPv6 is typical of 
the reaction one gets, in my experience. So far, I've not seen strong 
interest in getting the lingering issues addressed.

            jak

----- Original Message ----- 
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Brian Haley" <brian.haley@hp.com>; <mip6@ietf.org>; "Dave Thaler" 
<dthaler@windows.microsoft.com>
Sent: Monday, October 02, 2006 10:50 AM
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG 
Review:Recharter of Mobility for IPv6 (mip6))


> Hi,
>
> IMHO, maybe, it would be time to re-active SEND WG. The different reasons 
> I see:
> o the main one, to re-work on the RFC 3971
> - to reduce or to solve the issue regarding the fact that SEND only
> secures the IP address of a SEND node and not the link "IP address -
> link address" which, IIRC, was one of the initial goal of this WG.
> - to integrate feedbacks from SEND implementors (even if, personally,
> I only know one: the NTT's public implementation)
> o to re-work on the RFC 3972
> - to have a better/suited place for the work on 
> draft-bagnulo-multiple-hash-cga
> o to work on ND proxy used in conjunction with SEND
>
> Comments?
>
> Sorry if this reply is out of scope the initial thread.
>
> Best regards.
>
> JMC.
>
> 2006/10/2, James Kempf <kempf@docomolabs-usa.com>:
>>
>> > James Kempf wrote:
>> >> What about ND proxying for home address DAD?  I agree that the tunnel 
>> >> is
>> >> a point to point link, but wouldn't the traffic need to be forwarded 
>> >> down
>> >> the tunnel? A quick search of RFC 3775 indicates that nothing is said
>> >> about the TTL, but it could not be decremented on the relayed  DAD
>> >> traffic because of ND security.
>> >
>> > HA does DAD (and all ND on home link) for MN when it's not home, this
>> > traffic is never forwarded.  The hoplimit on "normal" IPv6 traffic is
>> > decremented on traffic entering the tunnel, at least in my 
>> > implementation.
>> >
>>
>> Right, that would solve the problem.
>>
>> >> This isn't like a normal point to point link between a router and a 
>> >> host,
>> >> because there are other hosts on the same link.
>> >
>> > I don't understand... on the tunnel?  There's only one host at the end 
>> > of
>> > the tunnel.
>> >
>>
>> I was thinking of the case where the HA forwards the ND traffic from an 
>> MN
>> to other MNs through tunnels, but, as you point out, this isn't 
>> necessary.
>>
>> There is still the issue of secure proxying, though, as Julien has 
>> pointed
>> out. This topic has come up now and then over the years, and we had a BAR
>> BOF the last time IETF was in San Diego to discuss it. Greg Daley did a
>> draft (probably expired now) describing solutions that do not require
>> protocol changes, I did a draft for MOBOPTS about something more
>> sophisticated but requiring more protocol changes.
>>
>> Do people care about this issue? The easiest way to solve it is to put
>> something in RFC 3775bis that says: "if you are concerned about proxy ND
>> security, don't configure a home link in a way that allows nodes to 
>> directly
>> attach to it."  But maybe that's too restrictive.
>>
>>             jak
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>> 


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



From mip6-bounces@ietf.org Mon Oct 02 14:36:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUSeH-0002kT-CG; Mon, 02 Oct 2006 14:36:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUSeG-0002kN-0Z
	for mip6@ietf.org; Mon, 02 Oct 2006 14:36:16 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUSeE-0007BK-K6
	for mip6@ietf.org; Mon, 02 Oct 2006 14:36:15 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k92IaCYP022444
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 2 Oct 2006 11:36:13 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k92Ia6od001258; Mon, 2 Oct 2006 11:36:11 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Oct 2006 11:35:49 -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: Multi-link subnets and MIPv6 (was Re: [Mip6]
	Re:WGReview:Recharter of Mobility for IPv6 (mip6))
Date: Mon, 2 Oct 2006 11:34:59 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325131A2F27@NAEX13.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A1E94A9@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Multi-link subnets and MIPv6 (was Re: [Mip6]
	Re:WGReview:Recharter of Mobility for IPv6 (mip6))
thread-index: AcbmQdE2lIYNso14Qs+KdYewUcoXkwAAwG8AAAMKXAA=
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 02 Oct 2006 18:35:49.0318 (UTC)
	FILETIME=[94FFF660:01C6E651]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 tend to agree with Hesham here. I am not sure why multi-link subnets
is any more an issue for MIP6 than it is for remote access VPNs such as
tunnel-mode IPsec.=20

I think focusing on 1 below makes sense to determine what models,
including MIP6 and tunnel-mode ESP, fall under this category. I would
say this is a cross-area activity rather than something that goes into
the MIP6 charter.=20

Vidya=20

> -----Original Message-----
> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
> Sent: Monday, October 02, 2006 10:14 AM
> To: mip6@ietf.org
> Cc: Dave Thaler
> Subject: RE: Multi-link subnets and MIPv6 (was Re: [Mip6]=20
> Re:WGReview:Recharter of Mobility for IPv6 (mip6))
>=20
> I think we might need to distinguish between ND-related=20
> issues with multi-link subnets (and the consequent=20
> relay/proxy of ND messages) and the situation in MIPv6.=20
>=20
> There are two slightly different threads that I think are=20
> being discussed on the list:=20
>=20
> 1. Defining multi-link subnets in general and deciding=20
> whether MIPv6 falls under such category and therefore comes=20
> with all the issues related to multi-link subnet?
>=20
> 2. Addressing multi-link subnet issues in MIPv6 and=20
> investigating whether there are problems in the *context of MIPv6*.=20
>=20
> Of course addressing 2) implies that we agree the MIPv6 as a=20
> concept creates a multi-link subnet. It would be useful IMO=20
> to address 1) without worrying about the consequences ;)
>=20
> Another related question to 1) above: If we assume the p2p=20
> tunnel created by MIPv6 is effectively a multi-link subnet,=20
> can we also make that assumption about VPN technologies out=20
> there? I'm just interested in scoping this discussion to the=20
> issues that matter to this WG rather than taking potentially=20
> larger issues related to all technologies that introduce a=20
> model that would fall under the multi-link umbrella.=20
>=20
> So, I guess my question is, what are the problematic=20
> multi-link aspects that we want to discuss here? ND seems to=20
> be a large component, should we start with that?=20
>=20
> Sorry for putting more questions than answers!=20
>=20
> Hesham
> =20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Mon Oct 02 15:03:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUT3c-0004nN-0l; Mon, 02 Oct 2006 15:02:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUT3a-0004nF-Oj
	for mip6@ietf.org; Mon, 02 Oct 2006 15:02:26 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUT3Z-0001oT-Cl
	for mip6@ietf.org; Mon, 02 Oct 2006 15:02:26 -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: Multi-link subnets and MIPv6 (was Re: [Mip6]Re:WGReview:Recharter
	of Mobility for IPv6 (mip6))
Date: Mon, 2 Oct 2006 12:00:22 -0700
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C218B3D9@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Multi-link subnets and MIPv6 (was Re:
	[Mip6]Re:WGReview:Recharter of Mobility for IPv6 (mip6))
Thread-Index: AcbmQdE2lIYNso14Qs+KdYewUcoXkwAAwG8AAAMKXAAAAPCYYA==
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

FWIW, I don't think the point-to-point links you setup
between a mobile node and a gateway (whether IPsec VPNs
or MIPv6) is a multi-link subnet.=20

we need to better define what a multi-link subnet is=20
in draft-iab-multilink-subnet-issues.

Vijay=20

> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]=20
> Sent: Monday, October 02, 2006 11:35 AM
> To: Soliman, Hesham; mip6@ietf.org
> Cc: Dave Thaler
> Subject: RE: Multi-link subnets and MIPv6 (was Re:=20
> [Mip6]Re:WGReview:Recharter of Mobility for IPv6 (mip6))
>=20
> I tend to agree with Hesham here. I am not sure why multi-link subnets
> is any more an issue for MIP6 than it is for remote access=20
> VPNs such as
> tunnel-mode IPsec.=20
>=20
> I think focusing on 1 below makes sense to determine what models,
> including MIP6 and tunnel-mode ESP, fall under this category. I would
> say this is a cross-area activity rather than something that goes into
> the MIP6 charter.=20
>=20
> Vidya=20
>=20
> > -----Original Message-----
> > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
> > Sent: Monday, October 02, 2006 10:14 AM
> > To: mip6@ietf.org
> > Cc: Dave Thaler
> > Subject: RE: Multi-link subnets and MIPv6 (was Re: [Mip6]=20
> > Re:WGReview:Recharter of Mobility for IPv6 (mip6))
> >=20
> > I think we might need to distinguish between ND-related=20
> > issues with multi-link subnets (and the consequent=20
> > relay/proxy of ND messages) and the situation in MIPv6.=20
> >=20
> > There are two slightly different threads that I think are=20
> > being discussed on the list:=20
> >=20
> > 1. Defining multi-link subnets in general and deciding=20
> > whether MIPv6 falls under such category and therefore comes=20
> > with all the issues related to multi-link subnet?
> >=20
> > 2. Addressing multi-link subnet issues in MIPv6 and=20
> > investigating whether there are problems in the *context of MIPv6*.=20
> >=20
> > Of course addressing 2) implies that we agree the MIPv6 as a=20
> > concept creates a multi-link subnet. It would be useful IMO=20
> > to address 1) without worrying about the consequences ;)
> >=20
> > Another related question to 1) above: If we assume the p2p=20
> > tunnel created by MIPv6 is effectively a multi-link subnet,=20
> > can we also make that assumption about VPN technologies out=20
> > there? I'm just interested in scoping this discussion to the=20
> > issues that matter to this WG rather than taking potentially=20
> > larger issues related to all technologies that introduce a=20
> > model that would fall under the multi-link umbrella.=20
> >=20
> > So, I guess my question is, what are the problematic=20
> > multi-link aspects that we want to discuss here? ND seems to=20
> > be a large component, should we start with that?=20
> >=20
> > Sorry for putting more questions than answers!=20
> >=20
> > Hesham
> > =20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Mon Oct 02 15:12:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUTCo-0004By-JM; Mon, 02 Oct 2006 15:11:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUTCn-0004AZ-1T
	for mip6@ietf.org; Mon, 02 Oct 2006 15:11:57 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUTCm-0002nq-JO
	for mip6@ietf.org; Mon, 02 Oct 2006 15:11:57 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id k92JBopW030232; 
	Mon, 2 Oct 2006 22:11:50 +0300
Date: Mon, 2 Oct 2006 22:11:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: RE: Multi-link subnets and MIPv6 (was Re: [Mip6] Re:WGReview:Recharter
	of Mobility for IPv6 (mip6))
In-Reply-To: <C24CB51D5AA800449982D9BCB90325131A2F27@NAEX13.na.qualcomm.com>
Message-ID: <Pine.LNX.4.64.0610022208190.30030@netcore.fi>
References: <C24CB51D5AA800449982D9BCB90325131A2F27@NAEX13.na.qualcomm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.88.4/1956/Mon Oct 2 01:56:15 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL, BAYES_00,
	NO_RELAYS autolearn=ham version=3.1.4
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On Mon, 2 Oct 2006, Narayanan, Vidya wrote:
> I tend to agree with Hesham here. I am not sure why multi-link subnets
> is any more an issue for MIP6 than it is for remote access VPNs such as
> tunnel-mode IPsec.

MIPv6 includes the concept of a "home link" from which the home 
address is taken.  In case this is a physical link, this is distinctly 
different from how VPNs operate.  If it would be only a logical link, 
you're quite right that the scenario is very close to a regular VPN.

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

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



From mip6-bounces@ietf.org Mon Oct 02 16:06:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUU3Q-0002EF-IA; Mon, 02 Oct 2006 16:06:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUU3O-0002E5-Mc
	for mip6@ietf.org; Mon, 02 Oct 2006 16:06:18 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUU3N-0008VR-DQ
	for mip6@ietf.org; Mon, 02 Oct 2006 16:06:18 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id B07928984E;
	Mon,  2 Oct 2006 23:06:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 6772189808;
	Mon,  2 Oct 2006 23:06:16 +0300 (EEST)
Message-ID: <45217121.2060602@piuha.net>
Date: Mon, 02 Oct 2006 23:05:53 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060921)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] SeND and proxy ND (was Re: Multi-link subnets and MIPv6)
References: <E1GPoPh-0001wa-Ph@stiedprstage1.ietf.org>	<200610021427.26123.julien.IETF@laposte.net>	<4521267E.4040907@hp.com><200610021728.35965.julien.IETF@laposte.net>	<4521337B.9030000@azairenet.com>	<0ee001c6e63d$0828e850$5a6015ac@dcml.docomolabsusa.com>	<45213F20.6040005@hp.com>	<0f0501c6e644$1f7713e0$5a6015ac@dcml.docomolabsusa.com>
	<45214AB0.7050905@azairenet.com>
In-Reply-To: <45214AB0.7050905@azairenet.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>,
	Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Proxy ND / SEND interoperability is one part of this
problem space.

But just to clarify what I expect from the WG regarding
this work item: while a proxy SEND solution would
be useful, I would like to address that, if needed, in
another context outside the MIP6 WG. There's been
occasional questions on creating a SEND++ WG
to deal with various issues that have come up.
(However, I'm not sure we should do that before
we see some deployment of base SEND
mechanisms.)

Anyway, from a MIP6 WG perspective this means that
you should focus on other aspects of the problem.

--Jari


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



From mip6-bounces@ietf.org Mon Oct 02 17:33:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUVP4-000146-GP; Mon, 02 Oct 2006 17:32:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUVP3-000141-I6
	for mip6@ietf.org; Mon, 02 Oct 2006 17:32:45 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUVP1-00067w-Ub
	for mip6@ietf.org; Mon, 02 Oct 2006 17:32:45 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6J0055C3D7FH@szxga02-in.huawei.com> for
	mip6@ietf.org; Tue, 03 Oct 2006 05:51:08 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6J008183D7YE@szxga02-in.huawei.com> for
	mip6@ietf.org; Tue, 03 Oct 2006 05:51:07 +0800 (CST)
Received: from [127.0.0.1] ([10.124.12.208])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J6J00C4W338UW@szxml04-in.huawei.com> for
	mip6@ietf.org; Tue, 03 Oct 2006 05:45:11 +0800 (CST)
Date: Mon, 02 Oct 2006 16:32:02 -0500
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review:
	Recharter of Mobility for IPv6 (mip6))
To: mip6@ietf.org
Message-id: <45218552.8010404@yahoo.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
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>
Errors-To: mip6-bounces@ietf.org

IMHO, IPsec VPN does not create a multi-link subnet but MIPv6 tunnel does.
My question is what happens if MN is in a p2p link where there can be 
only two nodes?

--behcet
----- Original Message ----
From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>; "Soliman, Hesham" 
<hsoliman@qualcomm.com>; mip6@ietf.org
Cc: Dave Thaler <dthaler@windows.microsoft.com>
Sent: Monday, October 2, 2006 2:00:22 PM
Subject: RE: Multi-link subnets and MIPv6 (was Re: 
[Mip6]Re:WGReview:Recharter of Mobility for IPv6 (mip6))


FWIW, I don't think the point-to-point links you setup
between a mobile node and a gateway (whether IPsec VPNs
or MIPv6) is a multi-link subnet.

we need to better define what a multi-link subnet is
in draft-iab-multilink-subnet-issues.

Vijay

 > -----Original Message-----
 > From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
 > Sent: Monday, October 02, 2006 11:35 AM
 > To: Soliman, Hesham; mip6@ietf.org
 > Cc: Dave Thaler
 > Subject: RE: Multi-link subnets and MIPv6 (was Re:
 > [Mip6]Re:WGReview:Recharter of Mobility for IPv6 (mip6))
 >
 > I tend to agree with Hesham here. I am not sure why multi-link subnets
 > is any more an issue for MIP6 than it is for remote access
 > VPNs such as
 > tunnel-mode IPsec.
 >
 > I think focusing on 1 below makes sense to determine what models,
 > including MIP6 and tunnel-mode ESP, fall under this category. I would
 > say this is a cross-area activity rather than something that goes into
 > the MIP6 charter.
 >
 > Vidya
 >
 > > -----Original Message-----
 > > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > > Sent: Monday, October 02, 2006 10:14 AM
 > > To: mip6@ietf.org
 > > Cc: Dave Thaler
 > > Subject: RE: Multi-link subnets and MIPv6 (was Re: [Mip6]
 > > Re:WGReview:Recharter of Mobility for IPv6 (mip6))
 > >
 > > I think we might need to distinguish between ND-related
 > > issues with multi-link subnets (and the consequent
 > > relay/proxy of ND messages) and the situation in MIPv6.
 > >
 > > There are two slightly different threads that I think are
 > > being discussed on the list:
 > >
 > > 1. Defining multi-link subnets in general and deciding
 > > whether MIPv6 falls under such category and therefore comes
 > > with all the issues related to multi-link subnet?
 > >
 > > 2. Addressing multi-link subnet issues in MIPv6 and
 > > investigating whether there are problems in the *context of MIPv6*.
 > >
 > > Of course addressing 2) implies that we agree the MIPv6 as a
 > > concept creates a multi-link subnet. It would be useful IMO
 > > to address 1) without worrying about the consequences ;)
 > >
 > > Another related question to 1) above: If we assume the p2p
 > > tunnel created by MIPv6 is effectively a multi-link subnet,
 > > can we also make that assumption about VPN technologies out
 > > there? I'm just interested in scoping this discussion to the
 > > issues that matter to this WG rather than taking potentially
 > > larger issues related to all technologies that introduce a
 > > model that would fall under the multi-link umbrella.
 > >
 > > So, I guess my question is, what are the problematic
 > > multi-link aspects that we want to discuss here? ND seems to
 > > be a large component, should we start with that?
 > >
 > > Sorry for putting more questions than answers!
 > >
 > > 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


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



From mip6-bounces@ietf.org Mon Oct 02 21:20:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUYwI-0000K0-CW; Mon, 02 Oct 2006 21:19:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUYwH-0000Jv-D9
	for mip6@ietf.org; Mon, 02 Oct 2006 21:19:17 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUYwF-0002rY-TH
	for mip6@ietf.org; Mon, 02 Oct 2006 21:19:17 -0400
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	k931JAbx033157; Mon, 2 Oct 2006 21:19:11 -0400 (EDT)
	(envelope-from yohba@tari.toshiba.com)
Date: Mon, 2 Oct 2006 21:19:13 -0400
To: "Faccin, Stefano M" <stefano.m.faccin@intel.com>
Subject: Re: [Mip6] On a network-mobility solution based on Mobile IPv6
Message-ID: <20061003011913.GE16683@steelhead>
References: <255498EAB77FB240B3951466AD2340D5DDA655@scsmsx414.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <255498EAB77FB240B3951466AD2340D5DDA655@scsmsx414.amr.corp.intel.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 91
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
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 Stefano,

I understand the performance benefit of PMIPv6 (i.e., eliminating one
IP encapsulation at MN), but it seems that security implications of
changing the SA termination points from "HA and MN" to "HA and a set
of ARs" are quite substantial especially from key management
perspective.  I would suggest doing deep security analysis before
taking any decision on this matter.

Best regards,
Yoshihiro Ohba


On Wed, Sep 20, 2006 at 06:59:18PM -0700, Faccin, Stefano M wrote:
> Hello all,
> 
> I'm sending this e-mail to start a thread of discussion on the need and
> opportunities for a network-mobility solution based on Mobile IPv6. 
> 
> As a result of offline discussions between interested parties, we would
> like to submit the following to begin a discussion on this mailing list.
> 
> =================================================================
> Recent developments in network architectures in SDOs such as WiMAX forum
> and 3GPP2 have identified a need to support IP mobility for hosts
> without the host playing a role in managing mobility. Significant
> interest exists for a network based IP mobility solution based on Mobile
> IPv6. The choice of Mobile IPv6 as the mobility protocol for IPv6 is
> driving the need to have a solution for network based mobility that is
> also based on or derived from MIPv6. One of the key benefits that been
> identified for a network based MIP6 solution (referred to as Proxy MIP6)
> is the optimized use of the air interface resulting from no MIP6
> signaling and no tunneling of packets over the air interface.
> 
> The WiMAX network architecture currently supports Proxy MIP4 for
> enabling mobility for hosts that may not have a MIP4 client. MIPv6 has
> been adopted as the mobility solution for IPv6. There exists a
> requirement to support mobility for IPv6 hosts without having any
> explicit expectations of the host IPv6 capability. Proxy MIP6 is a
> solution that is aligned with the architectural direction of WiMAX,
> given the specification of Proxy MIP4 for IPv4 mobility and hence a
> similar approach for IPv6 mobility.
> 
> In 3GPP, there has been some degree of interest in Proxy MIPv6 as well,
> primarily in the SAE (System Architecture Evolution) work item. No
> decision or protocol choices have been made yet.
> 
> 3GPP2 has expressed some interest in pursuing a network-based IP
> mobility protocol in order to support hosts with no mobility stack
> (those that use Simple IP) to take advantage of some form of mobility
> provided by the same entities that handle host-based (MIPv6-based)
> mobility. No decision on the specific protocol has been finalized yet,
> although a network-based IP mobility solution based on MIP6 has been
> identified as a viable option.
> 
> There are several key benefits to using PMIPv6 as the network-based
> mobility management protocol: 
> - The same MIPv6 home agent can be used be used at the same time with
> little or no modifications for clients that support MIPv6 and for
> clients that don't have host mobility software and would like the
> network to handle mobility for them.
> - Re-use of supporting work that has been done for MIPv6. This includes
> the ability to establish security associations, RADIUS and Diameter
> extensions, bootstrapping, dual stack support, reliability, fail over
> and HA switching.
> 
> So we would like to propose adding a new item to the MIP6 WG charter to
> standardize proxy MIPv6. The goal of this work would be to specify a
> simple extension to MIPv6 that would support network based mobility for
> IPv6 hosts and reuses MIP6 signaling and features. It is not intended to
> be a new network-based mobility protocol solution.
> 
> A couple of I-Ds specifying network-based mobility management protocol
> derived from MIPv6 exist today and can be used as the baseline for the
> work.
> 
> In conclusion, we think that the MIP6 WG should take on this work in
> order to meet a requirement of networks that will be deployed in the
> near future.
> 
> ========================================================================
> 
> Comments are welcome.
> Stefano
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 
> 

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



From mip6-bounces@ietf.org Tue Oct 03 10:59:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUliP-00059a-6d; Tue, 03 Oct 2006 10:57:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUliO-000588-DM
	for mip6@ietf.org; Tue, 03 Oct 2006 10:57:48 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUlYT-0001Cx-Rw
	for mip6@ietf.org; Tue, 03 Oct 2006 10:47:35 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k93ElR9R009000 for <mip6@ietf.org>; Tue, 3 Oct 2006 17:47:33 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Oct 2006 17:47:31 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Oct 2006 09:47:29 -0500
Received: from 172.19.244.112 ([172.19.244.112]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue,  3 Oct 2006 14:47:29 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 03 Oct 2006 09:49:08 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C147E294.257AE%basavaraj.patil@nokia.com>
Thread-Topic: WG LC for I-d: draft-ietf-mip6-aaa-ha-goals-03
Thread-Index: Acbm+xRlUsbSjFLuEduFIgARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 03 Oct 2006 14:47:29.0887 (UTC)
	FILETIME=[D9EA6EF0:01C6E6FA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [Mip6] WG LC for I-d: draft-ietf-mip6-aaa-ha-goals-03
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

This is a Working group last call for the WG I-D: AAA Goals for Mobile
IPv6 (draft-ietf-mip6-aaa-ha-goals-03). The draft is intended to serve
as the AAA requirements for Mobile IPv6.

Please review the I-D and submit your comments to the authors or to
the list directly.

The WGLC expires on Oct 18th, 06.

The I-D is intended to be published as an Informational RFC.

-Raj


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



From mip6-bounces@ietf.org Tue Oct 03 10:59:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GUlk0-0005hV-1x; Tue, 03 Oct 2006 10:59:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GUljx-0005hE-28
	for mip6@ietf.org; Tue, 03 Oct 2006 10:59:25 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUljv-00031v-Mw
	for mip6@ietf.org; Tue, 03 Oct 2006 10:59:25 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k93ExM2M024626
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Tue, 3 Oct 2006 07:59:23 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k93ExLL5029790
	for <mip6@ietf.org>; Tue, 3 Oct 2006 07:59:22 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Oct 2006 07:59:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 3 Oct 2006 07:59:31 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A1E95BD@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issue 66: Setting up forwarding for IPv4 HoA
thread-index: Acbm/IgOrrlpbnD8RRWkajOaULavpg==
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 03 Oct 2006 14:59:21.0535 (UTC)
	FILETIME=[82174CF0:01C6E6FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Subject: [Mip6] Issue 66: Setting up forwarding for IPv4 HoA
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Issue text:
-----------

we shouldnt have specific language about creating
a binding cache entry for the IPv4 HoA. The language
should suggest setting up forwarding for the traffic
meant for the IPv4 HoA over the mip6trans tunnel.

Pascal responded:

Do you mean a second BCE? I thought that the idea was to have a single
BCE, indexed by the IPv6 HoA, and then allow to register various things
against that BCE, including addresses and prefixes from both AFs, and
maybe later DNS names and more...

Vijay responded:

 Vijay: the current drafts suggests a BCE for the IPv4
        HoA in addition to BCE for the IPv6 HoA.


        >I thought that the idea was to have a single
        >BCE, indexed by the IPv6 HoA, and then allow to register
various things
        >against that BCE, including addresses and prefixes from both
AFs, and
        >maybe later DNS names and more...

 Vijay: I agree. but thats no what is there in version 00.
        it explicity talks about a BCE for the IPv4 HoA.

Analysis:
---------

Several IETF specifications describe conceptual data as part of
documenting a protocol. This is typically done for additional
clarification. Examples of such specifications include IPsec, ND, and
MIP (v4 and v6). MIPv6 described the binding cache as a mechanism for
storing bindings. However, this does not in anyway force implementers to
implement MIPv6 exactly as described in the document, as long as the
external behaviour is consistent with the specification. Since this
specification is an extension to MIPv6, it is appropriate to describe
the conceptual data structure in a manner consistent with RFC 3775.=20

RFC 3775 maintains that there is a separate Binding Cache entry for each
home address. As we are extending MIPv6 to support another address
family (IPv4), we still maintain the same philosophy of one binding
cache entry per home address, regardless of the type of HoA.=20
Similar to MIPv6, this does not require implementers to do it exactly in
this manner, hence the term "conceptual data structure". One may choose
to implement the v4 entry in the routing table for instance (the same
can be said for the v6 entry). But in all cases, the entries will need
to be maintained (refreshed/deleted ...etc) as per the BU.=20

Conclusion:
-----------

Keeping with the conceptual data structures in MIPv6 makes the spec
clear and does not limit implementers. There is no harm or bugs
introduced by the current text. Therefore the issue should be rejected.=20

Comments?

Hesham=20

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



From mip6-bounces@ietf.org Wed Oct 04 09:49:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GV774-0001os-LZ; Wed, 04 Oct 2006 09:48:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GV75c-0000dN-Us
	for mip6@ietf.org; Wed, 04 Oct 2006 09:47:12 -0400
Received: from nf-out-0910.google.com ([64.233.182.191])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GV6qX-000742-6c
	for mip6@ietf.org; Wed, 04 Oct 2006 09:31:41 -0400
Received: by nf-out-0910.google.com with SMTP id l23so500881nfc
	for <mip6@ietf.org>; Wed, 04 Oct 2006 06:31:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:content-class:from:to:subject:date:user-agent:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=VGG9ZcjpC8ro6TypORpKEgVXUy160cJ8FTCdjrP/gosPUWH8MiofYTpyx+JNqW8JURIoN1aRuN8rdwnlYwO6kSjnZOyjlA5m4fAdpO69XiHiw/e9E4N/Vb4vFbTnRGAySzYn7C5akQtgEgp1hkyN3X7CUHjoqzLtMXKVMPNKoJk=
Received: by 10.49.75.2 with SMTP id c2mr2306320nfl;
	Wed, 04 Oct 2006 06:31:35 -0700 (PDT)
Received: from ?192.168.1.106? ( [212.119.9.178])
	by mx.google.com with ESMTP id c1sm1189242nfe.2006.10.04.06.31.35;
	Wed, 04 Oct 2006 06:31:35 -0700 (PDT)
Content-Class: urn:content-classes:message
From: Julien Laganier <julien.IETF@laposte.net>
To: mip6@ietf.org
Subject: Fwd: RE: Multi-link subnets and MIPv6 (was Re: [Mip6] Re: WG Review:
	Recharter of Mobility for IPv6 (mip6))
Date: Wed, 4 Oct 2006 15:32:17 +0200
User-Agent: KMail/1.8.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610041532.18583.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Cc: Dave Thaler <dthaler@windows.microsoft.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Forwarding Dave's note as it seems it didn't make it to 
the mailing list.

--julien

----------  Forwarded Message  ----------

Subject: RE: Multi-link subnets and MIPv6 (was Re: 
[Mip6] Re: WG Review: Recharter of Mobility for IPv6 
(mip6))
Date: Tuesday 03 October 2006 19:42
From: Dave Thaler
To: Julien Laganier, mip6@ietf.org
Cc: Vijay Devarapalli, Jari Arkko

Just catching up on this thread. I agree with Julian's 
email below, and Pekka's later email.

MIPv6 defines a multilink subnet in the case where you 
have a home link with a subnet prefix. When you are 
away from home, and using a point-to-point tunnel to 
the home agent, the fact that the home agent 
decrements the TTL between the tunnel and other nodes 
on the home link, and the fact that the home agent 
does not forward link-scoped multicast between the 
two, is precisely the cause of the problems as Julian 
notes.

MIPv6 implementations do decrement TTL (as Brian Haley 
noted in his response), and do not forward link-scoped 
multicast (as Vijay noted in his email).

Regarding the discussion of VPNs, the same problem can 
occur with VPNs if the VPN server shares a prefix with 
a subnet (e.g., Ethernet) on the back end and some VPN 
servers are capable of doing this. Similarly, the same 
problem could occur if all the point-to-point links 
share a common subnet mask/prefix and the VPN server 
decrements TTL and/or doesn't forward link-scoped 
multicast between two VPN clients in the same subnet 
prefix. However, I'm not aware of an RFC that 
specifically recommends this behavior, which is the 
main reason why MIPv6 is more problematic than VPNs in 
general.

-Dave

> -----Original Message-----
> From: julien laganier
> [mailto:julien.laganier@gmail.com] On Behalf Of
> Julien Laganier
> Sent: Monday, October 02, 2006 4:53 AM
> To: mip6@ietf.org
> Cc: Vijay Devarapalli; Jari Arkko; Dave Thaler
> Subject: Re: Multi-link subnets and MIPv6 (was Re:
> [Mip6] Re: WG

Review:
> Recharter of Mobility for IPv6 (mip6))
>
> Hi Vijay,
>
> Some thoughts below:
>
> On Friday 29 September 2006 23:54, Vijay Devarapalli 
wrote:
> > Hi Jari and Dave,
> >
> > Jari Arkko wrote:
> > >> can you send us more information on this?
> > >> specifically on what we are supposed to look
> > >> for. document problems that we might encounter
> > >> when MIPv6 is run over multilink subnets?
> > >
> > > The basic reference is the new IAB draft,
> > > draft-iab-multilink-subnet-issues-00.txt.
> >
> > I went through this document.
> >
> > first I was surprised when I saw the following
> > text
> >
> > >    However, other WGs continued to allow for
> > > this concept even though it had been rejected in
> > > the IPv6 WG.  Mobile IPv6 [RFC3775] allows
> > > tunnels to mobile nodes to use the same subnet
> > > as a home link, with the Home Agent doing layer
> > > 3 forwarding between them.
> >
> > I was surprised to see the MIPv6 home link and the
> > tunnels to each mobile node being compared to a
> > multi-link subnet. its not a multi-link subnet as
> > described in
> > draft-ietf-ipv6-multilink-subnets-00.txt. the home
> > agent does not bridge and forward link-scope
> > traffic onto the tunnels.
>
> My (perhaps flawed) understanding is that a
> multilink subnet occurs when a subnet prefix is used
> to number interfaces on different links, and an
> entity forward traffic between those two links. It
> is not only about forwarding link-scope traffic.
>
> If you look at MIPv6 as described per section 8.4.
> of RFC 3775 this AFAICS exactly what happens: The MN
> numbers its tunnel interface with an address in the
> same subnet prefix that the one used on the home
> link (which is different from the tunnel
> interface.), and the HA
>
> forwards traffic:
> > 8.4.  IPv6 Home Agents
> >
> > [...]
> >
> >   o  Every home agent MUST be able to intercept
> > packets (using proxy Neighbor Discovery [12])
> > addressed to a mobile node for which it is
> > currently serving as the home agent, on that
> > mobile node's home link, while the mobile node is
> > away from home (Section 10.4.1).
> >
> >   o  Every home agent MUST be able to encapsulate
> > [15] such intercepted packets in order to tunnel
> > them to the primary care-of address for the mobile
> > node indicated in its binding in the home agent's
> > Binding Cache (Section 10.4.2).
>
> Regarding your observation that link-scope traffic
> is not forwarded in MIPv6, I think that not
> forwarding link-scope traffic is exactly the problem
> with multilink subnets: lot of applications assume
> that if two nodes share a same subnet prefix, then
> it means they share a link, and they can therefore
> communicate with link-scope traffic, and TTL won't
> get decremented. This assumption is broken when you
> have a multilink subnet but you do not forward
> link-scoped traffic.
>
> > the draft later on says
> >
> > >    A multilink subnet model SHOULD NOT be used. 
> > > IETF WG's using, or considering using, multilink
> > > subnets today should investigate moving to one
> > > of the other models.  For example, Mobile IPv6
> > > should investigate having the Home Agent not
> > > decrement the Hop Limit, and forward multicast
> > > traffic.
> >
> > currently no link local traffic sent on the home
> > link is forwarded over the Mobile IP tunnel to the
> > mobile node.
>
> I think that is exactly one of the issue of
> multilink subnets as used in MIPv6 (see above.)
>
> > [...]
> >
> > the current use of Mobile IP tunnels as an
> > extension of the home links does not introduce the
> > issues described with multi-link subnets in
> > draft-iab-multilink-subnet-issues. or I might be
> > missing something big.
>
> IMHO MIPv6 introduce the issues described in the
> multilink subnet draft.
>
> --julien

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

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



From mip6-bounces@ietf.org Thu Oct 05 10:59:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVUgT-0000DD-Qi; Thu, 05 Oct 2006 10:58:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVUgE-0007xQ-5L; Thu, 05 Oct 2006 10:58:34 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GVUYS-0002zN-97; Thu, 05 Oct 2006 10:50:32 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GVUYR-0002sF-Rh; Thu, 05 Oct 2006 10:50:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id BFB272AC8B;
	Thu,  5 Oct 2006 14:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GVUXx-0004JM-HJ; Thu, 05 Oct 2006 10:50:01 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1GVUXx-0004JM-HJ@stiedprstage1.ietf.org>
Date: Thu, 05 Oct 2006 10:50:01 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Cc: gdommety@cisco.com, mip6@ietf.org, basavaraj.patil@nokia.com
Subject: [Mip6] WG Action: RECHARTER: Mobility for IPv6 (mip6) 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 Mobility for IPv6 (mip6) working group in the Internet Area of the 
IETF has been rechartered. For additional information, please contact 
the Area Directors or the working group Chairs.

+++

Mobility for IPv6 (mip6)
==========================

Current Status: Active Working Group

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

Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
General Discussion: mip6@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
Archive: http://www.ietf.org/mail-archive/web/mip6/index.html

Description of Working Group:

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

o RFC 3775
o RFC 3776

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

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

Work items related to base specification maintenance include:

- Create and maintain an issue list that is generated on the basis of
implementation and interoperability experience. Address specific
issues with specific updates or revisions of the base
specification. One specific area of concern that should
be analyzed and addressed relates to multilink subnets.

This work item relates only to corrections and
clarifications. The working group shall not revisit design
decisions or change the protocol.

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

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

Work items related to large scale deployment include:

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

Work on the problem statement and the solutions needed for various
deployment scenarios. Work with other WGs such as DHC for defining
the options needed for bootstrapping.

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

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

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

- A mechanism to force an MN to switch the HA that is currently
serving it. This is required in deployments where the HA may need
to be taken offline for maintenance.

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

Work items related to informational documentation include:

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

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

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

Milestones:

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

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

Oct 2006 Submit I-D 'Mobility management for Dual stack mobile nodes:
A Problem Statement' to IESG for publication as Informational.

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

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

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

Nov 2006 Submit I-D 'DHCP Options for Home Information Discovery in
MIPv6' for publication as a proposed standard.

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

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

Dec 2006 Submit I-D 'Mobility Header Home Agent Switch Message' to
IESG for publication as a Proposed Standard.

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

Apr 2007 Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
publication as a proposed standard.

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

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

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



From mip6-bounces@ietf.org Thu Oct 05 11:43:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVVNH-00078S-UT; Thu, 05 Oct 2006 11:43:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GVVNG-00078M-7j
	for mip6@ietf.org; Thu, 05 Oct 2006 11:43:02 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVVNF-0004Fl-2p
	for mip6@ietf.org; Thu, 05 Oct 2006 11:43:02 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Oct 2006 17:42:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [Mip6] Issue 66: Setting up forwarding for IPv4 HoA
Date: Thu, 5 Oct 2006 17:42:57 +0200
Message-ID: <49E7012A614B024B80A7D175CB9A64EC0B89A914@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Issue 66: Setting up forwarding for IPv4 HoA
Thread-Index: AcbolO5Pmkf+VYT5S46y8jFf8R5RVA==
From: "GRIMAULT Jean-Luc RD-CORE-CAE" <jeanluc.grimault@orange-ft.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 05 Oct 2006 15:42:58.0181 (UTC)
	FILETIME=[EE8F4B50:01C6E894]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b0ea7984e9e2d84601de65ae5960f32c
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============0717163660=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0717163660==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6E894.EEEFB9B0"

This is a multi-part message in MIME format.

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

Hello,

=20

In DSMIPv6, I wonder if the requirement "the home agent MUST create two =
separate binding cache entries, one for each home address" (IPv6 home =
address and IPv4 home address) might not be misleading because of mobile =
Network prefixes.=20

Logically in the HA's Binding cache, mobile network prefixes are bound =
to the IPv6 home address. The (IPv6 or IPv4) Care of address is also =
bound to the IPv6 home address.=20

=20

If it occurs that the Mobile Router has also an IPv4 home address (for =
its own IPv4 applications), the requirement for two separate binding =
cache entries, one for each home address, may imply that all (IPv6 and =
IPv4) mobile network prefixes need to be bound in the HA's binding cache =
to the IPv6 home address entry *and* also to the IPv4 home address =
entry.=20

Firstly it may not be adequate because it implies  data duplication in =
the binding cache (especially when the MR serves many mobile network =
prefixes). Secondly, there is a doubt on what entry is used to forward =
the packets towards a mobile node served by the MR.  =20

=20

More generally that may raise questions relative to the relationship =
between the IPv4 home address and the mobile network prefixes.=20

For example, if the HA receives a BU with the IPv6 home address, the =
IPv4 home address, and mobile network prefixes included in the BU =
message (explicit mode in NEMO) and later the HA receives a new BU with =
the IPv6 home address and mobile network prefixes but without the IPv4 =
home address, the consequence on the IPv4 home address cache entry might =
be unclear.=20

Another example is the position of the IPv4 home address with regard to =
the prefix table quoted in =A7 6.1.2 of NEMO Basic support; this may be =
unclear because =A7 6.1.2 quotes only "Home Address" and not "IPv6 Home =
Address" or "IPv4 Home Address". Another example is in =A7 6.2 NEMO BS : =
"If the Lifetime specified in the Binding Update is 0 or the specified =
Care-of Address matches the Home Address in the Binding Update .." ; in =
this case which Home Address; IPv4 or IPv6 ?

=20

To solve these issues, is it not conceivable to state in the text of =
DSMIPv6 that, in case of a Mobile Router, the mobile network prefixes =
(IPv6 and IPv4) are bound uniquely to the IPv6 home address entry in the =
binding cache and that they are independent of the IPv4 home address?

=20

Jean-Luc

=20

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

Mip6] Issue 66: Setting up forwarding for IPv4 HoA

Issue text:

-----------

=20

we shouldnt have specific language about creating

a binding cache entry for the IPv4 HoA. The language

should suggest setting up forwarding for the traffic

meant for the IPv4 HoA over the mip6trans tunnel.

=20

Pascal responded:

=20

Do you mean a second BCE? I thought that the idea was to have a single

BCE, indexed by the IPv6 HoA, and then allow to register various things

against that BCE, including addresses and prefixes from both AFs, and

maybe later DNS names and more...

=20

Vijay responded:

=20

 Vijay: the current drafts suggests a BCE for the IPv4

        HoA in addition to BCE for the IPv6 HoA.

=20

=20

        >I thought that the idea was to have a single

        >BCE, indexed by the IPv6 HoA, and then allow to register

various things

        >against that BCE, including addresses and prefixes from both

AFs, and

        >maybe later DNS names and more...

=20

 Vijay: I agree. but thats no what is there in version 00.

        it explicity talks about a BCE for the IPv4 HoA.

=20

Analysis:

---------

=20

Several IETF specifications describe conceptual data as part of

documenting a protocol. This is typically done for additional

clarification. Examples of such specifications include IPsec, ND, and

MIP (v4 and v6). MIPv6 described the binding cache as a mechanism for

storing bindings. However, this does not in anyway force implementers to

implement MIPv6 exactly as described in the document, as long as the

external behaviour is consistent with the specification. Since this

specification is an extension to MIPv6, it is appropriate to describe

the conceptual data structure in a manner consistent with RFC 3775.=20

=20

RFC 3775 maintains that there is a separate Binding Cache entry for each

home address. As we are extending MIPv6 to support another address

family (IPv4), we still maintain the same philosophy of one binding

cache entry per home address, regardless of the type of HoA.=20

Similar to MIPv6, this does not require implementers to do it exactly in

this manner, hence the term "conceptual data structure". One may choose

to implement the v4 entry in the routing table for instance (the same

can be said for the v6 entry). But in all cases, the entries will need

to be maintained (refreshed/deleted ...etc) as per the BU.=20

=20

Conclusion:

-----------

=20

Keeping with the conceptual data structures in MIPv6 makes the spec

clear and does not limit implementers. There is no harm or bugs

introduced by the current text. Therefore the issue should be rejected.=20

=20

Comments?

=20

Hesham=20

=20


------_=_NextPart_001_01C6E894.EEEFB9B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">Hello,<?xml:namespace=20
prefix =3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">In=20
DSMIPv6, I wonder if the requirement "the home agent MUST create two =
separate=20
binding cache entries, one for each home address" (IPv6 home address and =
IPv4=20
home address) might not be misleading because of mobile Network=20
prefixes</SPAN><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">.&nbsp;</SPAN><SPAN=20
style=3D"mso-bidi-font-size: 12.0pt; mso-fareast-language: =
ZH-CN"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Logically=20
in the HA's Binding cache,&nbsp;mobile network prefixes are bound to the =
IPv6=20
home address. The (IPv6 or IPv4) Care of address&nbsp;is also bound to =
the IPv6=20
home address. <o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">If=20
it occurs that the Mobile Router has also an IPv4 home address (for its =
own IPv4=20
applications), the requirement for&nbsp;two separate binding cache =
entries, one=20
for each home address, may imply that all&nbsp;(IPv6 and IPv4) mobile =
network=20
prefixes&nbsp;need to be bound in the HA's binding cache to the IPv6 =
home=20
address entry *and* also to the IPv4 home address entry. =
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Firstly=20
it may not be adequate because it implies </SPAN><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">&nbsp;</SPAN><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">data=20
duplication in the binding cache (especially when the MR serves many =
mobile=20
network prefixes). Secondly, there is&nbsp;a doubt on what entry is used =

to&nbsp;forward the packets towards a mobile node served by the MR.<SPAN =

style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">More=20
generally that may raise questions relative to the relationship between =
the IPv4=20
home address and the mobile network prefixes. <o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">For=20
example, if the HA receives a BU with the IPv6 home address, the IPv4 =
home=20
address, and mobile network prefixes included in the BU message =
(explicit mode=20
in NEMO) and later the HA receives a new BU with the IPv6 home address =
and=20
mobile network prefixes but without the IPv4 home address, the =
consequence on=20
the IPv4 home address cache entry might be unclear. =
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Another=20
example is the position of the IPv4 home address with regard to the =
prefix table=20
quoted in =A7 6.1.2 of NEMO Basic support; this may be unclear because =
=A7 6.1.2=20
quotes only "Home Address" and not "IPv6 Home Address" or "IPv4 Home =
Address".=20
Another example is in =A7 6.2 NEMO BS : "If the Lifetime specified in =
the Binding=20
Update is 0 or the specified Care-of Address matches the Home Address in =
the=20
Binding Update .." ; in this case which Home Address; IPv4 or IPv6=20
?<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">To=20
solve these issues, is it not conceivable to state in the text of =
DSMIPv6 that,=20
in case of a Mobile Router, the mobile network prefixes (IPv6 and IPv4) =
are=20
bound uniquely to the IPv6&nbsp;home address&nbsp;entry in the binding =
cache and=20
that they are independent of the IPv4 home =
address?<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-ansi-language: EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-ansi-language: EN-US">Jean-Luc<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-ansi-language: EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-bidi-font-size: =
10.0pt; mso-ansi-language: =
EN-US">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-outline-level: 1"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-bidi-font-size: 24.0pt; mso-fareast-language: ZH-CN; =
mso-ansi-language: EN-US; mso-bidi-font-weight: bold">Mip6]=20
Issue 66: Setting up forwarding for IPv4 HoA<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Issue=20
text:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">-----------<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">we=20
shouldnt have specific language about creating<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">a=20
binding cache entry for the IPv4 HoA. The language<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">should=20
suggest setting up forwarding for the traffic<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">meant=20
for the IPv4 HoA over the mip6trans tunnel.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Pascal=20
responded:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Do=20
you mean a second BCE? I thought that the idea was to have a=20
single<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">BCE,=20
indexed by the IPv6 HoA, and then allow to register various=20
things<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">against=20
that BCE, including addresses and prefixes from both AFs,=20
and<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">maybe=20
later DNS names and more...<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Vijay=20
responded:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;</SPAN>Vijay: the current drafts =
suggests a BCE=20
for the IPv4<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>HoA=20
in addition to BCE for the IPv6 HoA.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>&gt;I thought that the idea was to have a =
single<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>&gt;BCE, indexed by the IPv6 HoA, and then allow to=20
register<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">various=20
things<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>&gt;against that BCE, including addresses and prefixes from=20
both<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">AFs,=20
and<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>&gt;maybe later DNS names and more...<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;</SPAN>Vijay: I agree. but thats no =
what is=20
there in version 00.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>it=20
explicity talks about a BCE for the IPv4 HoA.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">Analysis:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">---------<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Several=20
IETF specifications describe conceptual data as part =
of<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">documenting=20
a protocol. This is typically done for additional<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">clarification.=20
Examples of such specifications include <?xml:namespace prefix =3D st1 =
ns =3D=20
"urn:schemas-microsoft-com:office:smarttags" /><st1:place =
w:st=3D"on"><st1:City=20
w:st=3D"on">IPsec</st1:City>, <st1:State =
w:st=3D"on">ND</st1:State></st1:place>,=20
and<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">MIP=20
(v4 and v6). MIPv6 described the binding cache as a mechanism=20
for<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">storing=20
bindings. However, this does not in anyway force implementers=20
to<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">implement=20
MIPv6 exactly as described in the document, as long as =
the<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">external=20
behaviour is consistent with the specification. Since =
this<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">specification=20
is an extension to MIPv6, it is appropriate to =
describe<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">the=20
conceptual data structure in a manner consistent with RFC 3775.=20
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">RFC=20
3775 maintains that there is a separate Binding Cache entry for=20
each<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">home=20
address. As we are extending MIPv6 to support another=20
address<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">family=20
(IPv4), we still maintain the same philosophy of one=20
binding<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">cache=20
entry per home address, regardless of the type of HoA. =
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Similar=20
to MIPv6, this does not require implementers to do it exactly=20
in<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">this=20
manner, hence the term "conceptual data structure". One may=20
choose<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">to=20
implement the v4 entry in the routing table for instance (the=20
same<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">can=20
be said for the v6 entry). But in all cases, the entries will=20
need<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">to=20
be maintained (refreshed/deleted ...etc) as per the BU. =
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">Conclusion:<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">-----------<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Keeping=20
with the conceptual data structures in MIPv6 makes the=20
spec<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">clear=20
and does not limit implementers. There is no harm or =
bugs<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">introduced=20
by the current text. Therefore the issue should be rejected.=20
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">Comments?<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Hesham=20
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt =
229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt =
641.2pt 687.0pt 732.8pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US"><o:p>&nbsp;</o:p></SPAN></P></DIV></BODY></HTML>

------_=_NextPart_001_01C6E894.EEEFB9B0--


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

--===============0717163660==--




From mip6-bounces@ietf.org Thu Oct 05 18:52:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVc4F-0007ut-OB; Thu, 05 Oct 2006 18:51:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVc4E-0007sX-K6; Thu, 05 Oct 2006 18:51:50 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GVc4C-0003z8-DO; Thu, 05 Oct 2006 18:51:50 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k95MpiY4009599
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 5 Oct 2006 15:51:45 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k95MhwN6006537; Thu, 5 Oct 2006 15:51:43 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Oct 2006 15:51:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 5 Oct 2006 15:51:00 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241972@NAEX13.na.qualcomm.com>
In-Reply-To: <05ee01c6e89a$25728e70$456015ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NETLMM and PMIPv6 (RE: [netlmm] Consensus call to
	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
thread-index: AcboncP8GJB+HX4AQqOS7NfcSTn7GAAJfyVg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>, <netlmm@ietf.org>
X-OriginalArrivalTime: 05 Oct 2006 22:51:02.0212 (UTC)
	FILETIME=[BB6F6840:01C6E8D0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: mip6@ietf.org
Subject: [Mip6] NETLMM and PMIPv6 (RE: [netlmm] Consensus call to
	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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


(Cross-posting to MIP6)

All,
I would like to understand how making this document a WG document
impacts any Proxy MIP6 solution that may be standardized at the IETF.
Jari's email on the MIP6 ML indicated that he would like to see this
discussion happen before a decision is made about the NETLMM DT
document.=20

Personally, I think that the fundamental requirements are almost
identical in both cases. I think summarizing the differences in
requirements and discussing whether standardizing both solutions makes
sense would be worthwhile at this time.=20

Thoughts?=20

Vidya=20

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
> Sent: Thursday, October 05, 2006 9:20 AM
> To: netlmm@ietf.org
> Subject: [netlmm] Consensus call to=20
> makedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft
>=20
> Folks,
>=20
> Henrik has done a super job in editing the results of the=20
> interim meeting into the DT draft, keeping the list informed=20
> all the while. So, now it's time to consider whether to make=20
> the draft a WG draft. Please take a look at the draft and=20
> send a posting to the list with your opinion. You can find=20
> the draft here:
>=20
> http://www1.tools.ietf.org/wg/netlmm/dt-draft/draft-giaretta-n
etlmm-dt-protocol-02.txt
>=20
> until it is posted in the Internet Drafts repository.
>=20
> Please remember that this consensus call is only whether or=20
> not to make the draft a WG draft, and that this decision does=20
> not lock in the current text.=20
> After a draft becomes a WG draft, it is still subject to=20
> discussion and modification based on WG consensus; in fact,=20
> it is expected that WG members take the time and make the=20
> effort to review the draft and make sure there are no=20
> technical problems.
>=20
> The consenus call will remain open for a week until next=20
> Thurs. Oct. 12.=20
> Please try to post your opinion before then.
>=20
>             jak=20
>=20
>=20
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm
>=20

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



From mip6-bounces@ietf.org Fri Oct 06 07:36:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVnzZ-0005My-Lw; Fri, 06 Oct 2006 07:35:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GVnzX-0005LU-T1
	for mip6@ietf.org; Fri, 06 Oct 2006 07:35:47 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GVnzW-0002xs-HZ
	for mip6@ietf.org; Fri, 06 Oct 2006 07:35:47 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-15.tower-128.messagelabs.com!1160134545!2085841!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 26675 invoked from network); 6 Oct 2006 11:35:45 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-15.tower-128.messagelabs.com with SMTP;
	6 Oct 2006 11:35:45 -0000
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k96BZeSB016050;
	Fri, 6 Oct 2006 04:35:44 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k96BZcav028279;
	Fri, 6 Oct 2006 06:35:39 -0500 (CDT)
Message-ID: <45263F89.8060106@motorola.com>
Date: Fri, 06 Oct 2006 13:35:37 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: GRIMAULT Jean-Luc RD-CORE-CAE <jeanluc.grimault@orange-ft.com>
Subject: Re: [Mip6] Issue 66: Setting up forwarding for IPv4 HoA
References: <49E7012A614B024B80A7D175CB9A64EC0B89A914@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <49E7012A614B024B80A7D175CB9A64EC0B89A914@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
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

GRIMAULT Jean-Luc RD-CORE-CAE wrote:
> Hello,
> 
> In DSMIPv6, I wonder if the requirement "the home agent MUST create 
> two separate binding cache entries, one for each home address" (IPv6 
> home address and IPv4 home address) might not be misleading because 
> of mobile Network prefixes.
> 
> Logically in the HA's Binding cache, mobile network prefixes are 
> bound to the IPv6 home address. The (IPv6 or IPv4) Care of address is
>  also bound to the IPv6 home address.
> 
> If it occurs that the Mobile Router has also an IPv4 home address 
> (for its own IPv4 applications), the requirement for two separate 
> binding cache entries, one for each home address, may imply that all 
> (IPv6 and IPv4) mobile network prefixes need to be bound in the HA's 
> binding cache to the IPv6 home address entry *and* also to the IPv4 
> home address entry.
> 
> Firstly it may not be adequate because it implies  data duplication 
> in the binding cache (especially when the MR serves many mobile 
> network prefixes). Secondly, there is a doubt on what entry is used 
> to forward the packets towards a mobile node served by the MR.
> 
> More generally that may raise questions relative to the relationship 
> between the IPv4 home address and the mobile network prefixes.
> 
> For example, if the HA receives a BU with the IPv6 home address, the 
> IPv4 home address, and mobile network prefixes included in the BU 
> message (explicit mode in NEMO) and later the HA receives a new BU 
> with the IPv6 home address and mobile network prefixes but without 
> the IPv4 home address, the consequence on the IPv4 home address cache
>  entry might be unclear.

Right.

> Another example is the position of the IPv4 home address with regard 
> to the prefix table quoted in § 6.1.2 of NEMO Basic support; this may
>  be unclear because § 6.1.2 quotes only "Home Address" and not "IPv6 
> Home Address" or "IPv4 Home Address". Another example is in § 6.2 
> NEMO BS : "If the Lifetime specified in the Binding Update is 0 or 
> the specified Care-of Address matches the Home Address in the Binding
>  Update .." ; in this case which Home Address; IPv4 or IPv6 ?

I think this distinction needs to be made.  I think it should be noted
down for future NEMOv6 rfc3963 updating.  I think the text should say
"IPv6 Home Address" instead of just "Home Address".

This is something I will try to take into account in the NEMOv4 proposed
draft as well - use "IPv4 Home Address" instead of just "Home Address".

> To solve these issues, is it not conceivable to state in the text of 
> DSMIPv6 that, in case of a Mobile Router, the mobile network prefixes
> (IPv6 and IPv4) are bound uniquely to the IPv6 home address entry in
> the binding cache and that they are independent of the IPv4 home
> address?

I support this suggestion.  I have stated several times that DS-MIPv6
should target continuity of _only_ IPv6 sessions (while accessing IPv4
networks or IPv6 networks).

Alex

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



From mip6-bounces@ietf.org Fri Oct 06 08:33:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVotN-00042V-7I; Fri, 06 Oct 2006 08:33:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVotK-00040f-Um; Fri, 06 Oct 2006 08:33:26 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1GVotJ-0004is-KM; Fri, 06 Oct 2006 08:33:26 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-12.tower-128.messagelabs.com!1160138000!1245169!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 15044 invoked from network); 6 Oct 2006 12:33:20 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-12.tower-128.messagelabs.com with SMTP;
	6 Oct 2006 12:33:20 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k96CXFsK001000;
	Fri, 6 Oct 2006 05:33:15 -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 k96CXEZv001231;
	Fri, 6 Oct 2006 07:33:15 -0500 (CDT)
Message-ID: <45264D09.8030300@motorola.com>
Date: Fri, 06 Oct 2006 14:33:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
References: <C24CB51D5AA800449982D9BCB9032513241972@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB9032513241972@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>, netlmm@ietf.org
Subject: [Mip6] Re: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
 to	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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

Narayanan, Vidya wrote:
> (Cross-posting to MIP6)
> 
> All, I would like to understand how making this document a WG 
> document impacts any Proxy MIP6 solution that may be standardized at 
> the IETF. Jari's email on the MIP6 ML indicated that he would like to
> see this discussion happen before a decision is made about the NETLMM
> DT document.
> 
> Personally, I think that the fundamental requirements are almost 
> identical in both cases.

Except that reqs/ps and security context is precisely described in
netlmm WG items while for PMIPv6 we have no other reqs.

The netlmm problem statement document discusses problems with existing
(at that time) approaches to "netlmm" concepts - h/fmipv6, cellular IP,
gtp.  At the time of that writing the PMIPv6 documents did not yet exist
(draft-chowdhury-netmip6-00.txt and
draft-gundavelli-netlmm-mip6-proxy-00.txt)

Do you think the netlmm PS document should be updated to discuss issues
with netmip6 and with netlmm-mip6-proxy protocols?

I have some ideas in that space.  For example,
draft-gundavelli-netlmm-mip6-proxy-00.txt states that it improves
handover performance (because MN "just" does "normal" IPv6 attachment,
instead of mobility-related messaging).  Later on it states that MN uses
DHCP.  Using DHCP is known to be a strong bottleneck for handover
performance, with many implementations.  The DHCP issues for "netlmm"
concepts have been largely discussed here, and documented here.

> I think summarizing the differences in requirements and discussing 
> whether standardizing both solutions makes sense would be worthwhile
>  at this time.

Do you mean we should standardize PMIPv6 just because netlmm protocol is 
being pursued?

Alex


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



From mip6-bounces@ietf.org Fri Oct 06 09:07:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVpPw-0005gV-RA; Fri, 06 Oct 2006 09:07:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GVpPu-0005gM-Io
	for mip6@ietf.org; Fri, 06 Oct 2006 09:07:06 -0400
Received: from py-out-1112.google.com ([64.233.166.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVpPp-0000u3-9g
	for mip6@ietf.org; Fri, 06 Oct 2006 09:07:06 -0400
Received: by py-out-1112.google.com with SMTP id w49so983129pyg
	for <mip6@ietf.org>; Fri, 06 Oct 2006 06:07:00 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=Tl8Rv1iaWcCz900u1YNqszsP27J43274Bak44Qv97TBaFRWCz3GMJcdsEPqsEYrDuxcg/ZTFvv6vNpMBfIk5lzCJJHQvZ5xlLhbJrPMU+6pLgqWfqWJ9TbL3YjCL0h+kRr8uPz8+D3sgtiPTh7yIsNRUTOsPRyFGgWTy5qfx1sc=
Received: by 10.35.61.17 with SMTP id o17mr5873677pyk;
	Fri, 06 Oct 2006 06:07:00 -0700 (PDT)
Received: from ?192.168.1.106? ( [212.119.9.178])
	by mx.google.com with ESMTP id 38sm3432297nzk.2006.10.06.06.06.59;
	Fri, 06 Oct 2006 06:07:00 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: netlmm@ietf.org
Date: Fri, 6 Oct 2006 15:07:42 +0200
User-Agent: KMail/1.8.2
References: <C24CB51D5AA800449982D9BCB9032513241972@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB9032513241972@NAEX13.na.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610061507.43194.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
Subject: [Mip6] Re: NETLMM and PMIPv6 (RE: [netlmm] Consensus call to
	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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

Hi Vidya,

On Friday 06 October 2006 00:51, Narayanan, Vidya 
wrote:
> (Cross-posting to MIP6)

[ Perhaps this discussion should happen on a single
  ML? I am not though. ]

> All,
> I would like to understand how making this document
> a WG document impacts any Proxy MIP6 solution that
> may be standardized at the IETF. Jari's email on the 
> MIP6 ML indicated that he would like to see this
> discussion happen before a decision is made about
> the NETLMM DT document.

My understanding of Jari's note was slighty different. 
I understood that amongst other things he asked:

 - what are the requirements that are not fullfiled
   with today's solutions?

 - people interested in PMIP6 to talk to NetLMM WG 
   *now* if their requirements are close to what
   NetLMM does.

> Personally, I think that the fundamental
> requirements are almost identical in both cases.

Agree.

> I think summarizing the differences in requirements
> and discussing whether standardizing both solutions
> makes sense would be worthwhile at this time.

Discussing differences in requirements would definitely 
make sense. 

However, because as you noted they seems to be almost 
identical I do not think it makes sense to standardize 
both solutions -- that wouldn't be good from a 
standardization point of view.

Rather, those (supposedly few) requirements that are 
presently not fullfilled by a NetLMM solution should 
be worked on so that we satisfies all of them with a 
single protocol.

Best regards,

--julien

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



From mip6-bounces@ietf.org Fri Oct 06 09:59:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVqDZ-0001rl-IJ; Fri, 06 Oct 2006 09:58:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVqDO-0001ZY-Or; Fri, 06 Oct 2006 09:58:14 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GVq0N-0007Du-F3; Fri, 06 Oct 2006 09:44:48 -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
	k96Dijvh031422
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Oct 2006 06:44:46 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k96Dih5D027732; Fri, 6 Oct 2006 06:44:44 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 06:44:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 06:44:24 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A249EC7@NAEX14.na.qualcomm.com>
In-Reply-To: <200610061507.43194.julien.IETF@laposte.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
	tomakedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
thread-index: AcbpSHGQ0JHnACz9Rw6Gduv6MAfVcAAALdUQ
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Julien Laganier" <julien.IETF@laposte.net>, <netlmm@ietf.org>
X-OriginalArrivalTime: 06 Oct 2006 13:44:14.0214 (UTC)
	FILETIME=[82C1F260:01C6E94D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: mip6@ietf.org
Subject: [Mip6] RE: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
	tomakedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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

It is well known that I do not like NETLMM at all, whether it is done in
NETLMM or MIPv6 WG. Putting my personal opinion aside, however, I would
like to say this:

Let's assume that the requirements for NETLMM and PMIPv6 are virtually
identical, which I think is a reasonable assumption.

NETLMM is currently attempting to address these requirements by
designing a protocol from scratch.

A PMIPv6 based design would presumably define the delta from the
standard MIPv6 solution required. The solution should also be able to
re-use at least some of the extensions already defined in MIPv6 and
maybe even allow for MIPv6 and PMIPv6 mobiles and networks to coexist.
Such assumptions should, however, be scrutinized if/when PMIPv6 design
is done, to make sure they still whole water.

Redesigning things from scratch is some times a good thing but the new
design has to be significantly better to counteract the risk inherent
with any new approach. Green field designs are also best done by small
groups of people and they come with running code, rather than design by
committees (no offence to NETLMM).
Extending an existing protocol is always an easier and more palpable
approach. Arguably, when the delta between the old and the new approach
is not that significant, extending an existing protocol is highly
preferable. This way, it is easy for everyone to come up to speed with
the changes and gives everyone a warm fuzzy feeling about the whole
thing (whether such feeling is justified or not is another story).

I think proponents of PMIPv6 are making a mistake by pretending that
PMIPv6 will somehow be different from NETLMM. Instead there should be a
discussion about the benefits of extending the existing approach vs the
perceived risks involved with reinventing the wheel. If the majority of
the NETLMM crowed is willing to take the risk then I do not think you
can do much about it.

I still think that having two competing solutions in the IETF is a bad
idea, unless one of them becomes "experimental" so that the effort is
captured but it is clear that the IETF has only fully defined one thing!

In fact what I think is that the IETF does not need a solution to any of
this but I guess I have said this already :-)

Regards
George


> -----Original Message-----
> From: Julien Laganier [mailto:julien.IETF@laposte.net]
> Sent: Friday, October 06, 2006 9:08 AM
> To: netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: Re: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
tomakedraft-
> giaretta-netlmm-dt-protocol-02.txt a WG draft)
>=20
> Hi Vidya,
>=20
> On Friday 06 October 2006 00:51, Narayanan, Vidya
> wrote:
> > (Cross-posting to MIP6)
>=20
> [ Perhaps this discussion should happen on a single
>   ML? I am not though. ]
>=20
> > All,
> > I would like to understand how making this document
> > a WG document impacts any Proxy MIP6 solution that
> > may be standardized at the IETF. Jari's email on the
> > MIP6 ML indicated that he would like to see this
> > discussion happen before a decision is made about
> > the NETLMM DT document.
>=20
> My understanding of Jari's note was slighty different.
> I understood that amongst other things he asked:
>=20
>  - what are the requirements that are not fullfiled
>    with today's solutions?
>=20
>  - people interested in PMIP6 to talk to NetLMM WG
>    *now* if their requirements are close to what
>    NetLMM does.
>=20
> > Personally, I think that the fundamental
> > requirements are almost identical in both cases.
>=20
> Agree.
>=20
> > I think summarizing the differences in requirements
> > and discussing whether standardizing both solutions
> > makes sense would be worthwhile at this time.
>=20
> Discussing differences in requirements would definitely
> make sense.
>=20
> However, because as you noted they seems to be almost
> identical I do not think it makes sense to standardize
> both solutions -- that wouldn't be good from a
> standardization point of view.
>=20
> Rather, those (supposedly few) requirements that are
> presently not fullfilled by a NetLMM solution should
> be worked on so that we satisfies all of them with a
> single protocol.
>=20
> Best regards,
>=20
> --julien
>=20
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm

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



From mip6-bounces@ietf.org Fri Oct 06 12:02:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GVs8Y-0004ok-5x; Fri, 06 Oct 2006 12:01:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GVs8W-0004oe-VH
	for mip6@ietf.org; Fri, 06 Oct 2006 12:01:20 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVs8V-00082C-I3
	for mip6@ietf.org; Fri, 06 Oct 2006 12:01:20 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k96G1C0h024495 for <mip6@ietf.org>; Fri, 6 Oct 2006 19:01:18 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 19:01:12 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 11:01:08 -0500
Received: from 172.19.244.112 ([172.19.244.112]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri,  6 Oct 2006 16:01:08 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Fri, 06 Oct 2006 11:02:49 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C14BE859.25CF4%basavaraj.patil@nokia.com>
Thread-Topic: Requests for timeslots at the IETF67 MIP6 WG meeting
Thread-Index: AcbpYN7BHQYKslVUEduDbgARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 06 Oct 2006 16:01:08.0938 (UTC)
	FILETIME=[A31D5AA0:01C6E960]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [Mip6] Requests for timeslots at the IETF67 MIP6 WG meeting
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

MIP6 WG is scheduled to meet at IETF67 on Monday, Nov 6th from 1-3 PM.
If you need a timeslot, please send a request with the following details:

1. I-D name
2. Amount of time needed
3. If not a WG I-D, provide justification

-Chairs


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



From mip6-bounces@ietf.org Fri Oct 06 22:53:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2IZ-0002ZZ-1D; Fri, 06 Oct 2006 22:52:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2IX-0002ZI-QN; Fri, 06 Oct 2006 22:52:21 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GW2IU-0000yp-8l; Fri, 06 Oct 2006 22:52:21 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k972qGcm020838
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Oct 2006 19:52:17 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k972q9mk010255; Fri, 6 Oct 2006 19:52:15 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 19:52:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 19:52:15 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241A7D@NAEX13.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A249EC7@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NETLMM and PMIPv6 (RE: [netlmm] Consensus
	calltomakedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
thread-index: AcbpSHGQ0JHnACz9Rw6Gduv6MAfVcAAALdUQABx3FEA=
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Julien Laganier" <julien.IETF@laposte.net>, <netlmm@ietf.org>
X-OriginalArrivalTime: 07 Oct 2006 02:52:14.0889 (UTC)
	FILETIME=[983C6990:01C6E9BB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: mip6@ietf.org
Subject: [Mip6] RE: NETLMM and PMIPv6 (RE: [netlmm] Consensus
	calltomakedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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

Putting the fact that George dislikes any kind of network-based mobility
aside :), I have to agree with a few of his points in the email below.=20

Specifically, we should be having the discussion on what we can re-use
with a network-based mobility solution based on MIP6 vs. a total
re-design.

I will try to get a thread going on that topic shortly and hopefully, we
can make some progress in figuring this out and getting consensus.=20

Vidya

> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]=20
> Sent: Friday, October 06, 2006 6:44 AM
> To: Julien Laganier; netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: RE: NETLMM and PMIPv6 (RE: [netlmm] Consensus=20
> calltomakedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
>=20
> It is well known that I do not like NETLMM at all, whether it=20
> is done in NETLMM or MIPv6 WG. Putting my personal opinion=20
> aside, however, I would like to say this:
>=20
> Let's assume that the requirements for NETLMM and PMIPv6 are=20
> virtually identical, which I think is a reasonable assumption.
>=20
> NETLMM is currently attempting to address these requirements=20
> by designing a protocol from scratch.
>=20
> A PMIPv6 based design would presumably define the delta from=20
> the standard MIPv6 solution required. The solution should=20
> also be able to re-use at least some of the extensions=20
> already defined in MIPv6 and maybe even allow for MIPv6 and=20
> PMIPv6 mobiles and networks to coexist.
> Such assumptions should, however, be scrutinized if/when=20
> PMIPv6 design is done, to make sure they still whole water.
>=20
> Redesigning things from scratch is some times a good thing=20
> but the new design has to be significantly better to=20
> counteract the risk inherent with any new approach. Green=20
> field designs are also best done by small groups of people=20
> and they come with running code, rather than design by=20
> committees (no offence to NETLMM).
> Extending an existing protocol is always an easier and more=20
> palpable approach. Arguably, when the delta between the old=20
> and the new approach is not that significant, extending an=20
> existing protocol is highly preferable. This way, it is easy=20
> for everyone to come up to speed with the changes and gives=20
> everyone a warm fuzzy feeling about the whole thing (whether=20
> such feeling is justified or not is another story).
>=20
> I think proponents of PMIPv6 are making a mistake by pretending that
> PMIPv6 will somehow be different from NETLMM. Instead there=20
> should be a discussion about the benefits of extending the=20
> existing approach vs the perceived risks involved with=20
> reinventing the wheel. If the majority of the NETLMM crowed=20
> is willing to take the risk then I do not think you can do=20
> much about it.
>=20
> I still think that having two competing solutions in the IETF=20
> is a bad idea, unless one of them becomes "experimental" so=20
> that the effort is captured but it is clear that the IETF has=20
> only fully defined one thing!
>=20
> In fact what I think is that the IETF does not need a=20
> solution to any of this but I guess I have said this already :-)
>=20
> Regards
> George
>=20
>=20
> > -----Original Message-----
> > From: Julien Laganier [mailto:julien.IETF@laposte.net]
> > Sent: Friday, October 06, 2006 9:08 AM
> > To: netlmm@ietf.org
> > Cc: mip6@ietf.org
> > Subject: Re: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
> tomakedraft-
> > giaretta-netlmm-dt-protocol-02.txt a WG draft)
> >=20
> > Hi Vidya,
> >=20
> > On Friday 06 October 2006 00:51, Narayanan, Vidya
> > wrote:
> > > (Cross-posting to MIP6)
> >=20
> > [ Perhaps this discussion should happen on a single
> >   ML? I am not though. ]
> >=20
> > > All,
> > > I would like to understand how making this document a WG document=20
> > > impacts any Proxy MIP6 solution that may be standardized at the=20
> > > IETF. Jari's email on the
> > > MIP6 ML indicated that he would like to see this=20
> discussion happen=20
> > > before a decision is made about the NETLMM DT document.
> >=20
> > My understanding of Jari's note was slighty different.
> > I understood that amongst other things he asked:
> >=20
> >  - what are the requirements that are not fullfiled
> >    with today's solutions?
> >=20
> >  - people interested in PMIP6 to talk to NetLMM WG
> >    *now* if their requirements are close to what
> >    NetLMM does.
> >=20
> > > Personally, I think that the fundamental requirements are almost=20
> > > identical in both cases.
> >=20
> > Agree.
> >=20
> > > I think summarizing the differences in requirements and=20
> discussing=20
> > > whether standardizing both solutions makes sense would be=20
> worthwhile=20
> > > at this time.
> >=20
> > Discussing differences in requirements would definitely make sense.
> >=20
> > However, because as you noted they seems to be almost=20
> identical I do=20
> > not think it makes sense to standardize both solutions -- that=20
> > wouldn't be good from a standardization point of view.
> >=20
> > Rather, those (supposedly few) requirements that are presently not=20
> > fullfilled by a NetLMM solution should be worked on so that we=20
> > satisfies all of them with a single protocol.
> >=20
> > Best regards,
> >=20
> > --julien
> >=20
> > _______________________________________________
> > netlmm mailing list
> > netlmm@ietf.org
> > https://www1.ietf.org/mailman/listinfo/netlmm
>=20
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm
>=20

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



From mip6-bounces@ietf.org Fri Oct 06 23:02:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2Rx-0000nm-6e; Fri, 06 Oct 2006 23:02:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2Rv-0000nV-Jr; Fri, 06 Oct 2006 23:02:03 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GW2Rt-00024N-62; Fri, 06 Oct 2006 23:02:03 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9731vVh021701
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Oct 2006 20:01:58 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9731t8x017051; Fri, 6 Oct 2006 20:01:57 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 20:01:55 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 20:01:54 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241A7E@NAEX13.na.qualcomm.com>
In-Reply-To: <45264D09.8030300@motorola.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
	to	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
thread-index: AcbpRKeaLy3Jw+GwRmyAeZdckZ83vgAdvW4w
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 07 Oct 2006 03:01:55.0550 (UTC)
	FILETIME=[F2563FE0:01C6E9BC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>, netlmm@ietf.org
Subject: [Mip6] RE: NETLMM and PMIPv6 (RE: [netlmm] Consensus call
	to	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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

Hi Alex,
=20

> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]=20
> Sent: Friday, October 06, 2006 5:33 AM
> To: Narayanan, Vidya
> Cc: James Kempf; netlmm@ietf.org; mip6@ietf.org
> Subject: Re: NETLMM and PMIPv6 (RE: [netlmm] Consensus call=20
> to makedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
>=20
> Narayanan, Vidya wrote:
> > (Cross-posting to MIP6)
> >=20
> > All, I would like to understand how making this document a=20
> WG document=20
> > impacts any Proxy MIP6 solution that may be standardized at=20
> the IETF.=20
> > Jari's email on the MIP6 ML indicated that he would like to=20
> see this=20
> > discussion happen before a decision is made about the NETLMM DT=20
> > document.
> >=20
> > Personally, I think that the fundamental requirements are almost=20
> > identical in both cases.
>=20
> Except that reqs/ps and security context is precisely=20
> described in netlmm WG items while for PMIPv6 we have no other reqs.
>=20

I don't believe we need a separate requirements document. As I said, the
requirements in my view are the same as those that drove NETLMM in the
first place. In addition, I think PMIPv6 is aiming at a solution that
can provide maximum re-use of already defined functionality. While that
is a goal in NETLMM, it has not been realized in the DT protocol. Also,
there seem to be multiple interpretations of that goal - so, there is
not a high degree of clarity to the re-use goal.=20

> The netlmm problem statement document discusses problems with=20
> existing (at that time) approaches to "netlmm" concepts -=20
> h/fmipv6, cellular IP, gtp.  At the time of that writing the=20
> PMIPv6 documents did not yet exist (draft-chowdhury-netmip6-00.txt and
> draft-gundavelli-netlmm-mip6-proxy-00.txt)
>=20

The latter document did exist and was taken as input by the DT. I have
to believe that the DT had a discussion about this approach vs a totally
new protocol - but, I can't speak for it, as I have not seen the DT
archives.=20


> Do you think the netlmm PS document should be updated to=20
> discuss issues with netmip6 and with netlmm-mip6-proxy protocols?
>=20

No. Rather, we should be evaluating a solution that allows maximum
re-use of functionality defined for MIP6, as that is what seems to be
gaining momentum in the industry.=20

> I have some ideas in that space.  For example,=20
> draft-gundavelli-netlmm-mip6-proxy-00.txt states that it=20
> improves handover performance (because MN "just" does=20
> "normal" IPv6 attachment, instead of mobility-related=20
> messaging).  Later on it states that MN uses DHCP.  Using=20
> DHCP is known to be a strong bottleneck for handover=20
> performance, with many implementations.  The DHCP issues for "netlmm"
> concepts have been largely discussed here, and documented here.
>=20

The discussion is not specifically about the solution in that draft. It
is about how much re-use of existing protocols and functionality should
be feasible from the protocol defined for network-based mobility -
re-use allows faster deployment and hence the interest in the industry.
OTOH, if we do an analysis and find that such a re-use is inefficient
and will hurt us in the long run, it is another story. In this case, I
think a number of people believe that the re-use is practical.=20

> > I think summarizing the differences in requirements and discussing=20
> > whether standardizing both solutions makes sense would be=20
> worthwhile =20
> > at this time.
>=20
> Do you mean we should standardize PMIPv6 just because netlmm=20
> protocol is being pursued?
>=20

No. It is a question of whether we want to allow a PMIPv6 solution to be
designed the right way, in a manner that can be used by multiple SDOs or
let each SDO define its own flavor of it. Otherwise, the onus is on us
to prove that the right solution for network-based mobility is in fact
what is described in draft-giaretta-netlmm-dt-protocol-02. This study
needs to occur for any concrete proof of that - as of now, many people
are not seeing that.=20

Vidya

> Alex
>=20
>=20

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



From mip6-bounces@ietf.org Fri Oct 06 23:07:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2Wr-0003dW-LZ; Fri, 06 Oct 2006 23:07:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2Wq-0003dF-7E; Fri, 06 Oct 2006 23:07:08 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GW2Wo-0002J2-RJ; Fri, 06 Oct 2006 23:07:08 -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
	k9737322021640
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Oct 2006 20:07:03 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k97371Te013580; Fri, 6 Oct 2006 20:07:02 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 20:07:01 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 20:06:58 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241A7F@NAEX13.na.qualcomm.com>
In-Reply-To: <200610061507.43194.julien.IETF@laposte.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NETLMM and PMIPv6 (RE: [netlmm] Consensus call to
	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
thread-index: AcbpSUXWZOKrmX1ITPqEmAOpUtkB7gAc7qVA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Julien Laganier" <julien.IETF@laposte.net>, <netlmm@ietf.org>
X-OriginalArrivalTime: 07 Oct 2006 03:07:01.0787 (UTC)
	FILETIME=[A8DE4EB0:01C6E9BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
Subject: [Mip6] RE: NETLMM and PMIPv6 (RE: [netlmm] Consensus call to
	makedraft-giaretta-netlmm-dt-protocol-02.txt a WG 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

Hi Julien,=20

> -----Original Message-----
> From: julien laganier [mailto:julien.laganier@gmail.com] On=20
> Behalf Of Julien Laganier
> Sent: Friday, October 06, 2006 6:08 AM
> To: netlmm@ietf.org
> Cc: Narayanan, Vidya; James Kempf; mip6@ietf.org
> Subject: Re: NETLMM and PMIPv6 (RE: [netlmm] Consensus call=20
> to makedraft-giaretta-netlmm-dt-protocol-02.txt a WG draft)
>=20
> Hi Vidya,
>=20
> On Friday 06 October 2006 00:51, Narayanan, Vidya
> wrote:
> > (Cross-posting to MIP6)
>=20
> [ Perhaps this discussion should happen on a single
>   ML? I am not though. ]
>=20

I cross-posted, since the discussion on PMIPv6 was ongoing on MIP6. If
all the interested people are on both lists, I can limit this to just
NETLMM. But, I am not sure of that.=20

> > All,
> > I would like to understand how making this document
> > a WG document impacts any Proxy MIP6 solution that
> > may be standardized at the IETF. Jari's email on the=20
> > MIP6 ML indicated that he would like to see this
> > discussion happen before a decision is made about
> > the NETLMM DT document.
>=20
> My understanding of Jari's note was slighty different.=20
> I understood that amongst other things he asked:
>=20
>  - what are the requirements that are not fullfiled
>    with today's solutions?
>=20
>  - people interested in PMIP6 to talk to NetLMM WG=20
>    *now* if their requirements are close to what
>    NetLMM does.
>=20

Quoting from Jari's email - "They (NETLMM) do not have an official WG
solution specification yet, but they will soon and I don't think they
expect to keep in the WG process for too long after that. If you want to
have an effect the time to voice your opinion is now."=20

That seems to imply the dependency. In any case, we should be having
this discussion.=20

> > Personally, I think that the fundamental
> > requirements are almost identical in both cases.
>=20
> Agree.
>=20
> > I think summarizing the differences in requirements
> > and discussing whether standardizing both solutions
> > makes sense would be worthwhile at this time.
>=20
> Discussing differences in requirements would definitely=20
> make sense.=20
>=20
> However, because as you noted they seems to be almost=20
> identical I do not think it makes sense to standardize=20
> both solutions -- that wouldn't be good from a=20
> standardization point of view.
>=20
> Rather, those (supposedly few) requirements that are=20
> presently not fullfilled by a NetLMM solution should=20
> be worked on so that we satisfies all of them with a=20
> single protocol.
>

Ideally, I would agree with you. But, we should look at the differences
in requirements and make a decision. I hope we can hash this all out
among all the people working on NETLMM and PMIPv6 respectively.=20

Regards,
Vidya=20
=20
> Best regards,
>=20
> --julien
>=20

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



From mip6-bounces@ietf.org Fri Oct 06 23:24:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2nl-0005fI-GQ; Fri, 06 Oct 2006 23:24:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GW2nj-0005eD-SA; Fri, 06 Oct 2006 23:24:35 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GW2nN-0004KH-9w; Fri, 06 Oct 2006 23:24:15 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k973OBG7022456
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Oct 2006 20:24:12 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k973OBGx006225; 
	Fri, 6 Oct 2006 20:24:11 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Oct 2006 20:24:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 20:24:04 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241A80@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Network-based mobility - NETLMM DT Solution Vs A solution based
	on MIP6 
thread-index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniA==
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: <netlmm@ietf.org>
X-OriginalArrivalTime: 07 Oct 2006 03:24:10.0922 (UTC)
	FILETIME=[0E47D8A0:01C6E9C0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: mip6@ietf.org
Subject: [Mip6] Network-based mobility - NETLMM DT Solution Vs A solution
	based on MIP6 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,
This is an effort to kick start a discussion of the merits of each
approach and reach an agreement on the deltas and the importance of the
deltas. I have purposely avoided the use of the term "PMIPv6", since
there appears to be multiple interpretations of that among different
people. The comparison here is between the proposed NETLMM DT solution
(as in draft-giaretta-netlmm-dt-protocol-02) vs a solution that would be
based on using the Mobility Header (and hence be closely aligned to
MIP6). This is not intended to get into the degree of closeness to MIP6.


What does the NETLMM DT Solution bring, by being totally different from
MIP6?
------------------------------------------------------------------------
------=20

1. The protocol can be evolved to using a reliable transport protocol
like SCTP at some point.=20
2. The protocol can run over IPv4 without changes.=20

While these seem like good goals, what is the practical need for the
above goals? For instance, is IPv4 signaling a necessity for a NETLMM
solution?=20


What does a solution based on MIP6 bring?=20
------------------------------------------
A solution that uses the Mobility Header can re-use a number of already
defined options, some of them directly and some with minor changes. The
industry is seeking a network-based local mobility solution that can
still provide a number of features that a host-based mobility solution
can provide. So, over time, we will find ourselves addressing these
requirements and re-inventing these for NETLMM.=20

Mobility options that can be re-used with an MH-based protocol like
PMIPv6:=20

1. MN ID Mobility Option

This option can pretty much be used with no changes.=20

2. DNS-based HA lookup

While some scenarios may not need this mechanism, it may make sense in
some deployments to use DNS for this purpose, even with PMIP6.=20

3. DHCP-based HA lookup=20
- Home Network Identifier Option
- Home Network Information Option
- DHCP Relay Agent MIP6 Option, MIP6 HA sub-option

Same as 2.=20

4. DNS Update Mobility Option

This can be used to update the DNS server with the address assigned to
the MN within the domain in which PMIP is deployed.=20

5. DSMIP6 Options
- IPv4 HoA Mobility Option
- IPv4 address acknowledgement Mobility Option
- NAT Detection Mobility Option

These options can be used without changes.=20

5. HA Switch message

Also useful for the same purpose as in MIP6 and can be used without
changes.=20

6. Other HA reliability messages

We need to wait for this work to stabilize a bit more before we can
tell, but we must be able to leverage off a lot of this work.=20

7. Multiple CoA Registration=20
- BID Mobility Option

Can be used to signal the addition of a location of the MN, rather than
a replace of location.=20

8. Flow bindings support
- Flow ID Option

When the edge is aware of the QoS needs of the MN (can happen via
out-of-band mechanisms), flow bindings can be conveyed to the HA using
the same mechanism as in MIP6.=20

9. NEMO Support
- Prefix registration
- Prefix Assignment

The extensions defined for NEMO support can largely be re-used to
register prefixes for the end node.=20

Other points:=20
-------------

1. Mechanisms such as the association phase for MAG-LMA discovery
described in the NELTMM DT protocol are potentially useful in certain
deployments of a network-based mobility solution. However, this should
be feasible to do in either approach.=20

Thoughts?=20

Regards,
Vidya


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



From mip6-bounces@ietf.org Sat Oct 07 09:42:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GWCQL-0002Oc-ET; Sat, 07 Oct 2006 09:41:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GWCQJ-0002HG-Ul
	for mip6@ietf.org; Sat, 07 Oct 2006 09:41:03 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GWCQJ-0000Ek-3t
	for mip6@ietf.org; Sat, 07 Oct 2006 09:41:03 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k97Df1Oo023136
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Sat, 7 Oct 2006 06:41:02 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k97Dex5n024456; Sat, 7 Oct 2006 06:40:59 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 7 Oct 2006 06:40:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip6] Issue 66: Setting up forwarding for IPv4 HoA
Date: Sat, 7 Oct 2006 06:40:54 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A249FCA@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Issue 66: Setting up forwarding for IPv4 HoA
thread-index: AcbolO5Pmkf+VYT5S46y8jFf8R5RVAA1YzIwACrpucA=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "GRIMAULT Jean-Luc RD-CORE-CAE" <jeanluc.grimault@orange-ft.com>,
	<mip6@ietf.org>
X-OriginalArrivalTime: 07 Oct 2006 13:40:58.0979 (UTC)
	FILETIME=[38CD3330:01C6EA16]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7191030d885084e634ab0f488bcd9d53
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0807531875=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0807531875==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6EA16.38A6C756"

This is a multi-part message in MIME format.

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

Resending, the first one was too large. =20

=20

 In DSMIPv6, I wonder if the requirement "the home agent MUST create two =
separate binding cache entries, one for each home address" =20

=20

=3D> Are you actually quoting the draft here? I'd like to know that =
because I think we decided not to use MUSTs for implementation issues, =
so if a MUST is there it should be removed.=20

=20

 (  IPv6 home address and IPv4 home address) might not be misleading =
because of mobile Network prefixes.=20

Logically in the HA's Binding cache, mobile network prefixes are bound =
to the IPv6 home address. The (IPv6 or IPv4) Care of address is also =
bound to the IPv6 home address.=20

=20

If it occurs that the Mobile Router has also an IPv4 home address (for =
its own IPv4 applications), the requirement for two separate binding =
cache entries, one for each home address, may imply that all (IPv6 and =
IPv4) mobile network prefixes need to be bound in the HA's binding cache =
to the IPv6 home address entry *and* also to the IPv4 home address =
entry. =20

=20

=3D> They certainly need to be linked regardless of the implementation. =
Let's understand first what the BC is used for. The BC is like a routing =
table. So when the HA receives a packet that needs to be tunnelled, it =
has to look up the BC to find the right entry. Now, how do you suppose =
an HA receiving an IPv4 packet would look up the BC?? What would it look =
for to find the entry? If the BC is implemented in the routing table =
then it looks up the IPv4 dst address. If the BC is separate from the =
routing table then it needs to find the right entry, either by looking =
up the IPv4 dst as a HoA or by introducing another level of indirection: =
i.e. lookup the corresponding IPv6 addr, then look up the BC using that =
IPv6 HoA. The latter means that all entries are tied to the IPv6 HoA, =
the former means that each HoA has a separate entry, and of course you =
can link those entries belonging to one MN. What is the problem?

=20

Firstly it may not be adequate because it implies  data duplication in =
the binding cache (especially when the MR serves many mobile network =
prefixes). Secondly, there is a doubt on what entry is used to forward =
the packets towards a mobile node served by the MR.   =20

=20

=3D> As I said earlier, this is only a *conceptual data structure*. You =
can implement it anyway you want. =20

=20

More generally that may raise questions relative to the relationship =
between the IPv4 home address and the mobile network prefixes. =20

=20

=3D> You mean the IPv4 home address and the IPv6 MNPs ? Why ?

=20

For example, if the HA receives a BU with the IPv6 home address, the =
IPv4 home address, and mobile network prefixes included in the BU =
message (explicit mode in NEMO) and later the HA receives a new BU with =
the IPv6 home address and mobile network prefixes but without the IPv4 =
home address, the consequence on the IPv4 home address cache entry might =
be unclear. =20

=20

=3D> Why is it unclear? you'd remove the IPv4 entry in this case.=20

=20

Another example is the position of the IPv4 home address with regard to =
the prefix table quoted in =A7 6.1.2 of NEMO Basic support; this may be =
unclear because =A7 6.1.2 quotes only "Home Address" and not "IPv6 Home =
Address" or "IPv4 Home Address". =20

=20

=3D> NEMO basic support is exclusively IPv6, so it doesn't need to say =
the "IPv6 home address". Just like 3775 doesn't say the "IPv6 home =
address".

=20

 Another example is in =A7 6.2 NEMO BS : "If the Lifetime specified in =
the Binding Update is 0 or the specified Care-of Address matches the =
Home Address in the Binding Update .." ; in this case which Home =
Address; IPv4 or IPv6 ?=20

=20

=3D> you're quoting the IPv6 only RFC right? it's the IPv6 HoA. It is =
our responsibility to clarify this in DSMIP, not in NEMO.

=20

=20

To solve these issues, is it not conceivable to state in the text of =
DSMIPv6 that, in case of a Mobile Router, the mobile network prefixes =
(IPv6 and IPv4) are bound uniquely to the IPv6 home address entry in the =
binding cache and that they are independent of the IPv4 home address?=20

=20

=3D> As I said earlier it is not something we should mandate at all. We =
could clarify the consequences of implementation choices of the BC and =
MNP, but we certainly shouldn't require one way of implementing it.=20

=20

Hesham=20

=20

Jean-Luc


------_=_NextPart_001_01C6EA16.38A6C756
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office" xmlns:st1 =
=3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D732204013-07102006><FONT face=3DArial color=3D#0000ff>Resending, =
the first one=20
was too large. &nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D732204013-07102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D732204013-07102006>&nbsp;</SPAN>In DSMIPv6, I wonder if the =
requirement=20
"the home agent MUST create two separate binding cache entries, one for =
each=20
home address"&nbsp;<SPAN class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>=3D&gt; Are you actually quoting the draft =
here? I'd like=20
to know that because I think we decided not to use MUSTs for =
implementation=20
issues, so if a MUST is there it should be removed. </SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN>(<SPAN =
class=3D794361117-06102006><FONT=20
face=3DArial color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN>IPv6 home address and IPv4 home =
address)=20
might not be misleading because of mobile Network prefixes</SPAN><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">.&nbsp;</SPAN><SPAN=20
style=3D"mso-fareast-language: ZH-CN; mso-bidi-font-size: =
12.0pt"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Logically=20
in the HA's Binding cache,&nbsp;mobile network prefixes are bound to the =
IPv6=20
home address. The (IPv6 or IPv4) Care of address&nbsp;is also bound to =
the IPv6=20
home address. <o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US; =
mso-bidi-font-size: 10.0pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">If=20
it occurs that the Mobile Router has also an IPv4 home address (for its =
own IPv4=20
applications), the requirement for&nbsp;two separate binding cache =
entries, one=20
for each home address, may imply that all&nbsp;(IPv6 and IPv4) mobile =
network=20
prefixes&nbsp;need to be bound in the HA's binding cache to the IPv6 =
home=20
address entry *and* also to the IPv4 home address entry.&nbsp;<SPAN=20
class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>=3D&gt; They certainly need to be linked =
regardless of=20
the implementation. Let's understand first what the BC is used for. The =
BC is=20
like a routing table. So when the HA receives a packet that needs to be=20
tunnelled, it has to look up the BC to find the right entry. Now, how=20
do&nbsp;you suppose an HA receiving an IPv4 packet would look up the =
BC?? What=20
would it look for to find the entry? If the BC is implemented in the =
routing=20
table then it looks up the IPv4 dst address. If the BC is separate from =
the=20
routing table then it needs to find the right entry, either by looking =
up the=20
IPv4 dst as a HoA or by introducing another level of indirection: i.e. =
lookup=20
the corresponding IPv6 addr, then look up the BC using that IPv6 HoA. =
The latter=20
means that all entries are tied to the IPv6 HoA, the former means that =
each HoA=20
has a separate entry, and of course you can link those entries belonging =
to one=20
MN. What is the problem?</SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none; tab-stops: =
404.0pt"><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Firstly=20
it may not be adequate because it implies </SPAN><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; =
mso-fareast-language: ZH-CN; mso-ansi-language: =
EN-US">&nbsp;</SPAN><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">data=20
duplication in the binding cache (especially when the MR serves many =
mobile=20
network prefixes). Secondly, there is&nbsp;a doubt on what entry is used =

to&nbsp;forward the packets towards a mobile node served by the MR.<SPAN =

style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;<SPAN =
class=3D794361117-06102006><FONT=20
face=3DArial color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
style=3D"mso-spacerun: yes"><SPAN class=3D794361117-06102006><FONT =
face=3DArial=20
color=3D#0000ff>=3D&gt; As I said earlier, this is only a *conceptual =
data=20
structure*. You can implement it anyway you want.=20
</FONT>&nbsp;</SPAN></SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US; =
mso-bidi-font-size: 10.0pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">More=20
generally that may raise questions relative to the relationship between =
the IPv4=20
home address and the mobile network prefixes.&nbsp;<SPAN=20
class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>=3D&gt; You mean the IPv4 home address and =
the IPv6 MNPs=20
? Why ?</SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">For=20
example, if the HA receives a BU with the IPv6 home address, the IPv4 =
home=20
address, and mobile network prefixes included in the BU message =
(explicit mode=20
in NEMO) and later the HA receives a new BU with the IPv6 home address =
and=20
mobile network prefixes but without the IPv4 home address, the =
consequence on=20
the IPv4 home address cache entry might be unclear.&nbsp;<SPAN=20
class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>=3D&gt; Why is it unclear? you'd remove the =
IPv4 entry in=20
this case. </SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">Another=20
example is the position of the IPv4 home address with regard to the =
prefix table=20
quoted in =A7 6.1.2 of NEMO Basic support; this may be unclear because =
=A7 6.1.2=20
quotes only "Home Address" and not "IPv6 Home Address" or "IPv4 Home=20
Address".&nbsp;<SPAN class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>=3D&gt; NEMO basic support is exclusively =
IPv6, so it=20
doesn't need to say the "IPv6 home address". Just like 3775 doesn't say =
the=20
"IPv6 home address".</SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN>Another example is in =A7 6.2 =
NEMO BS : "If=20
the Lifetime specified in the Binding Update is 0 or the specified =
Care-of=20
Address matches the Home Address in the Binding Update .." ; in this =
case which=20
Home Address; IPv4 or IPv6 ?<SPAN class=3D794361117-06102006><FONT =
face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>=3D&gt; you're quoting the IPv6 only RFC =
right? it's the=20
IPv6 HoA. It is our responsibility to clarify this in DSMIP, not in=20
NEMO.</SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006>&nbsp;</SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US; =
mso-bidi-font-size: 10.0pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US">To=20
solve these issues, is it not conceivable to state in the text of =
DSMIPv6 that,=20
in case of a Mobile Router, the mobile network prefixes (IPv6 and IPv4) =
are=20
bound uniquely to the IPv6&nbsp;home address&nbsp;entry in the binding =
cache and=20
that they are independent of the IPv4 home address?<SPAN=20
class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006><FONT face=3DArial =
color=3D#0000ff>=3D&gt;&nbsp;As I said=20
earlier it is not something we should mandate at all. We could clarify =
the=20
consequences of implementation choices of the BC and MNP, but we =
certainly=20
shouldn't require one way of implementing =
it.&nbsp;</FONT></SPAN></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006></SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; =
mso-fareast-language: ZH-CN; mso-ansi-language: EN-US"><SPAN=20
class=3D794361117-06102006><FONT face=3DArial=20
color=3D#0000ff>Hesham</FONT>&nbsp;</SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-ansi-language: =
EN-US; mso-bidi-font-size: 10.0pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; mso-layout-grid-align: none"><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: 'Courier New'; mso-ansi-language: =
EN-US; mso-bidi-font-size: =
10.0pt">Jean-Luc<o:p></o:p></SPAN></P></DIV></BODY></HTML>

------_=_NextPart_001_01C6EA16.38A6C756--


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

--===============0807531875==--




From mip6-bounces@ietf.org Mon Oct 09 15:50:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GX18b-00083t-8Z; Mon, 09 Oct 2006 15:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GX18U-0007yf-D7; Mon, 09 Oct 2006 15:50:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GX18U-0005UT-5P; Mon, 09 Oct 2006 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 21C203293A;
	Mon,  9 Oct 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GX18U-0007QV-0S; Mon, 09 Oct 2006 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GX18U-0007QV-0S@stiedprstage1.ietf.org>
Date: Mon, 09 Oct 2006 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-radius-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
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-00.txt
	Pages		: 28
	Date		: 2006-10-9
	
   A Mobile IPv6 node requires a home agent address, a home address, and
   IPsec security association with its home agent before it can start
   utilizing Mobile IPv6 service.  RFC 3775 requires that some or all of
   these parameters are statically configured.  Ongoing work aims to
   make this information dynamically available to the mobile node.  An
   important aspect of the Mobile IPv6 bootstrapping solution is to
   support interworking with existing authentication, authorization and
   accounting infrastructure.  This document defines the new attributes
   to facilitate Mobile IPv6 bootstrapping via a RADIUS infrastructure.
   This information exchange may take place as part of the initial
   network access authentication procedure or as part of a separate
   protocol exchange between the mobile node, the home agent and the AAA
   infrastructure.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-radius-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-radius-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-radius-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-9113259.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-10-9113259.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 Tue Oct 10 01:23:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXA4Z-00085n-Ky; Tue, 10 Oct 2006 01:22:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXA4X-00085i-Qe
	for mip6@ietf.org; Tue, 10 Oct 2006 01:22:33 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXA4U-0004aN-3H
	for mip6@ietf.org; Tue, 10 Oct 2006 01:22:33 -0400
Received: from c2-vpn07.isi.edu (c2-vpn07.isi.edu [128.9.176.224])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9A5Lpmr015812
	for <mip6@ietf.org>; Mon, 9 Oct 2006 22:21:51 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Mon, 09 Oct 2006 22:21:52 -0700
Message-Id: <1160457713.2864.18.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k9A5Lpmr015812
X-Spam-Score: 0.6 (/)
X-Scan-Signature: af2aae76ea468dc53420d9ba52ca6045
Subject: [Mip6] ACM SenSys'06 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

Our apologies if you have received multiple copies.

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

The cut-off date for ACM SenSys 2006 hotels is extended to=20
*Friday October 13*. Rooms are now only available at the=20
conference rates at:=20

The Hotel Boulderado

http://www.boulderado.com/

The Boulderado is located next to the Perl Street walking mall=20
in the heart of Boulder.

Rate: $129/night

Address:
2115 13th Street
Boulder, CO, USA 80302
Tel:800.433.4344
303.442.4344

The St Julien Hotel http://www.stjulien.com/

The St Julien is located next to the Pearl Street walking mall in=20
the heart of Boulder; the hotel has a view of the Flatiron Mountains.

Rate: $185/night

Address:
900 Walnut Street
Boulder, CO, USA 80302-6899
Tel: 720.406.9696
877.303.0900

---------------
ACM SenSys 2006 - Call for Participation

The 4th ACM Conference on Embedded Networked Sensor Systems

http://sensys.acm.org/2006/

Boulder, Colorado, USA
October 31 - November 3, 2006

In the short period since its inception in Los Angeles in 2003,
SenSys has risen to become the leading
forum for reporting on new, exciting, and technically important
research in the field of sensor networks.

Please note that the cut off dates for the conference hotels and
early registration are September 29 and October 30, respectively.

This year we have a stellar conference for you that includes:

* A keynote by David Carlson
   Director, International Polar Year Program Office, and formally,
   Director of the Atmospheric Technology Division of the US National
   Centre for Atmospheric Research (NCAR).

* 24 technical papers

* 29 Sensor network demos

* 19 Posters - representing early results and work-in-progress

* 2 one day workshops on emerging and important new topics in sensor
   networks. The workshops will be held the day prior to the main
   technical program

   + First Workshop on World-Sensor-Web: Mobile Device Centric Sensory
     Networks and Applications
     http://www.sensorplanet.org/wsw2006/

   + First Workshop on Distributed Smart Cameras
     http://www.iti.tugraz.at/dsc06/

Registration is now open:

http://www.regonline.com/Checkin.asp?EventId=3D97157

Important Dates:

Cut off date for reduced hotel rates is *September 29, 2006*

Cut off date for early registration is *October 30, 2006*

Please book and register today to guarantee the best rates.

One behalf of the whole organizing team we very much look forward to
seeing you at SenSys in Boulder!

Best regards,

Andrew T. Campbell
SenSys 2006 General Chair

Thanks to our sponsors:

ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS, SIGBED

NSF, NCAR, ISTS, Crossbow, Intel, Microsoft Research, Moteiv, Nokia

Below you'll find the technical program. Please go to
http://sensys.acm.org/2006/ for more information.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
**Technical Program, Demos, and Posters**
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Wednesday, November 1

08:15-08:30 Opening announcements

08:30-10:00 Keynote

David Carlson
Director, International Polar Year Program Office

10:00-10:30 Break

10:30-12:00 Operating Systems

t-kernel: Providing Reliable OS Support to Wireless Sensor Networks
Lin Gu, John A. Stankovic (University of Virginia)

Run-time Dynamic Linking for Reprogramming Wireless Sensor Networks
Adam Dunkels, Niclas Finne, Joakim Eriksson, Thiemo Voigt (Swedish
Institute of Computer Science)

Protothreads: Simplifying Event-Driven Programming of Memory-
Constrained Embedded Systems
Adam Dunkels, Oliver Schmidt, Thiemo Voigt (Swedish Institute of
Computer Science), Muneeb Ali (TU Delft)

12:00-13:30 Lunch

13:30-14:30 Sensing

Capturing High-Frequency Phenomena Using a Bandwidth-Limited Sensor
Network
Ben Greenstein, Christopher Mar, Alex Pesterev, Shahin Farshchi,
Eddie Kohler, Jack Judy, Deborah Estrin (UCLA)

Virtual High-resolution for Sensor Networks
Aman Kansal, William J. Kaiser, Gregory J. Pottie, Mani B. Srivastava
(UCLA) and Gaurav Sukhatme (USC)

14:30-15:00 Break

15:00 -16:30 Routing and Dissemination

RBP: Robust Broadcast Propagation in Wireless Networks
Fred Stann (Amgen), John Heidemann, Rajesh Shroff, Muhammad Zaki
Murtaza (USC/ISI)

Interest Dissemination with Directional Antenna for Wireless Sensor
Networks with Mobile Sinks
Yihong Wu, Xiaobo Chen, Lin Zhang, Zhisheng Niu (Tsinghua University)

Lazy Cross-Link Removal for Geographic Routing
Young-Jin Kim, Ramesh Govindan (USC), Brad Karp (University Colledge
London), Scott Shenker (UCB)

**19.00 Banquet at the Walnut Brewery Boulder's Original Brew Pub
1123 Walnut Street**

Thursday, November 2

09:00-10:00 Configuration

StarDust: A Flexible Architecture for Passive Localization in
Wireless Sensor Networks
Radu Stoleru, Pascal Vicaire, Tian He, John A. Stankovic (University
of Virginia)

The Design and Implementation of a Self-Calibrating Distributed
Acoustic Sensing Platform
Lewis Girod (MIT/CSAIL), Martin Lukac, Vlad Trifa, Deborah Estrin (UCLA)

10:00-10:30 Break

10:30-11:30 In-network Processing

Target Tracking with Binary Proximity Sensors: Fundamental Limits,
Minimal Descriptions, and Algorithms
Nisheeth Shrivastava, Raghuraman Mudumbai, Upamanyu Madhow, Subhash
Suri (UCSB)

Data Compression Algorithms for Energy-Constrained Devices in Delay
Tolerant Networks
Christopher M. Sadler, Margaret Martonosi (Princeton University)

11:30-13:00 Lunch

13:00-14:30 Radio Propagation and Transport

Datalink Streaming in Wireless Sensor Networks
Raghu K. Ganti, Praveen Jayachandran, Tarek F. Abdelzaher, and Haiyun
Luo (UIUC)

ATPC: Adaptive Transmission Power Control for Wireless Sensor
Shan Lin (University of Virginia), Tian He (University of Minnesota),
Jingbin Zhang, Gang Zhou, Lin Gu, John A. Stankovic (University of
Virginia)

Experimental Study of Concurrent Transmission in Wireless Sensor
Networks
Dongjin Son, Bhaskar Krishnamachari (USC), John Heidemann (USC/ISI)

14:30-15:00 Break

15:00-16:30 Storage and Abstractions

Abstractions for Safe Concurrent Programming in Networked Embedded
Systems
William P. McCartney, Nigamanth Sridhar (Cleveland State University)

Scalable Data Aggregation for Dynamic Events in Sensor Networks
Kai-Wei Fan, Sha Liu, Prasun Sinha (The Ohio State University)

An Energy-Optimized Object Storage System for Memory-Constrained
Sensor Devices
Gaurav Mathur, Peter Desnoyers, Deepak Ganesan, Prashant Shenoy
(University of Massachusetts, Amherst)

16:30-20:00 Demonstration and poster session

List of accepted demonstrations and posters

http://sensys.acm.org/2006/demo_poster.html

20:00-21:00 TinyOS Alliance BoF

Friday, November 3

08:30-10:00 Architecture

CarTel: A Distributed Mobile Sensor Computing System
Bret Hull, Vladimir Bychkovsky, Yang Zhang, Kevin Chen, Michel
Goraczko, Allen Miu, Eugene Shih, Hari Balakrishnan, Samuel Madden
(MIT/CSAIL)

MELETE: Supporting Concurrent Applications in Wireless Sensor Networks
Yang Yu, Loren Rittle (Motorola Labs), Jason LeBrun (UCD), Vartika
Bhandari (UIUC)

The Tenet Architecture for Tiered Sensor Networks
Omprakash Gnawali (USC), Ben Greenstein (UCLA), Ki-Young Jang (USC),
August Joki (UCLA), Jeongyeup Paek, Marcos Vieira (USC), Deborah
Estrin (UCLA), Ramesh Govindan (USC), Eddie Kohler (UCLA)

10:00-10:30 Break

10:30-12:00 Media Access Control

Funneling-MAC: A Localized, Sink-Oriented MAC for Boosting Fidelity
in Sensor Networks
Gahng-Seop Ahn (Columbia University), Emiliano Miluzzo, Andrew T.
Campbell (Dartmouth College), Se Gi Hong (Columbia University),
Francesca Cuomo (University of Rome "La Sapienza")

X-MAC: A Short Preamble MAC Protocol for Duty-Cycled Wireless Sensor
Networks
Michael Buettner, Gary V. Yee, Eric Anderson, Richard Han (University
of Colorado, Boulder)

Ultra-Low Duty Cycle MAC with Scheduled Channel Polling
Wei Ye, Fabio Silva, John Heidemann (USC/ISI)

12:00-12:15 Best Talk Award and Closing

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
***************DEMOS*********************
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

SignetLab: Deployable Sensor Network Testbed and Management Tool
Riccardo Crepaldi, Albert F Harris III, Alberto Scarpa, Andrea
Zanella, Michele Zorzi (University of Padova)

An Eventual Consistent Wireless Light Control System
Jeonghoon Kang (Korea Electronics Technology Institute), Alec Woo
(Arch Rock), Junejae Yoo, Myunghyun Yoon (Korea Electronics
Technology Institute)

Data Analysis Tools for Sensor-Based Science
Stuart Ozer (Microsoft Research), Alex Szalay (Johns Hopkins
University), Jim Gray (Microsoft Research), Andreas Terzis, Razvan
Musaloiu-E., Katalin Szlavecz, Josh Cogan, Randal Burns (Johns
Hopkins University)

Data Collection in Delay Tolerant Mobile Sensor Networks using SCAR
Cecilia Mascolo, Mirco Musolesi, Bence Pasztor (University College
London)

cCAM: Ultra Compact, High Data-Rate Wireless Sensor Node with a
Miniature Camera
Chulsung Park, Pai H. Chou (UCI)

Using Grid Technologies to Optimise a Wireless Sensor Network for
Flood Management
Danny Hughes, Phil Greenwood, Geoff Coulson, Gordon Blair, Barry
Porter, Paul Grace, Florian Pappenberger, Paul Smith, Keith Beven
(Lancaster University)

A Funneling-MAC for High Performance Data Collection in Sensor Networks
Gahng-Seop Ahn (Columbia University) Emiliano Miluzzo, Andrew T.
Campbell (Dartmouth College)

A Storage-centric Camera Sensor Network
Gaurav Mathur, Paul Chukiu, Peter Desnoyers, Deepak Ganesan, Prashant
Shenoy (University of Massachusetts)

Real-Time Volcanic Earthquake Localization
Geoffrey Werner-Allen, Patrick Swieskowski, Matt Welsh (Harvard
University)

Low Power, Low Cost, Wireless Camera Sensor Nodes For Human Detection
Jason Schlessman, Jaechang Shim, Ikdong Kim, Yun Cheol Baek, Wayne
Wolf (Princeton University)

A Unified Architecture for Flexible Radio Power Management in
Wireless Sensor Networks
Kevin Klues, Guoliang Xing, Chenyang Lu (Washington University)

A Self-Calibrating Distributed Acoustic Sensing Platform
Lewis D Girod (MIT/CSAIL), Martin Lukac (UCLA), Vladimir Trifa
(EPFL), Deborah Estrin (UCLA)

A Virtualizing OS Kernel for Wireless Sensor Networks
Lin Gu, John A Stankovic (University of Virginia)

Flexible Hardware/Software Platform for Tracking Applications
Junaid Ansari, Jos=C3=83=C2=A9 S=C3=83=C2=A1nchez, Marina Petrova, Janne =
Riihij=C3=83=C2=A4rvi,
Ossi Raivio, Krisakorn Rerkrai, Chirstine Jardak, Frank Oldewurtel,
Mathias
Wellens, Lili Wu, Petri M=C3=83=C2=A4h=C3=83=C2=B6nen (RWTH Aachen Univer=
sity)

Simple Sensor Syndiciation
Michael Colagrosso, Wade Simmons, Marianne Graham (Colorado School of
Mines)

Responsive and Energy-Efficient Sensor Networking for Real Time
Location Tracking
Henoc Agbota, Mike Hazas (Lancaster University)

Demonstrating Distributed Signal Strength Location Estimation
Neal Patwari (University of Utah), Alfred O. Hero (University of
Michigan)

Sensing and Reproducing the Shapes of 3D Objects Using Claytronics
Padmanabhan Pillai, Jason Campbell (Intel Research Pittsburgh)

Cascades: An Extensible Heterogeneous Sensor Networking Framework
Phillip Sitbon, Nirupama Bulusu, Wu-Chi Feng (Portland State University)

LiteOS - A Lightweight Operating System for C++ Software Development
in Sensor Networks
Qing Cao, Tarek Abdelzaher (UIUC)

GRAIL: General Real-Time Adaptable Indoor Localization
Yingying Chen (Rutgers University), Eiman Elnahrawy (Kordinate LLC),
John-Austen Francisco, Konstantinos Kleisouris (Rutgers University),
Xiaoyan Li (Lafayette College), Hongyi Xue (Rutgers University),
Richard P. Martin (Rutgers University and Kordinate LLC)

A Hierarchical Location Directory Service Across Sensor and IP Networks
Sangeeta Bhattacharya, Chien-Liang Fok, Chenyang Lu, Gruia-Catalin
Roman (Washington University)

Software Radio Implementation of Short-range
Wireless Standards for Sensor Networking
Thomas Schmid, Tad Dreier, Mani B. Srivastava (UCLA)

The CarTel Mobile Sensor Computing System
Vladimir L Bychkovsky, Kevin Chen, Michel Goraczko, Hongyi Hu, Bret W
Hull, Allen K Miu, Eugene I Shih, Yang Zhang (MIT)

TOSDev: A Rapid Development Environment for TinyOS
William P McCartney, Nigamanth Sridhar (Cleveland State University)

Step-wise Context Extraction in AoK Mule System
Yuichi Uehara, Masato Mori, Nayuta Ishii (Tokyo Denki University),
Yoh Shiraishi (The University of Tokyo) Yoshito Tobe (Tokyo Denki
University)

SensorMap: A Web Site for Sensors World-Wide
Suman Nath, Jie Liu, Jessica Miller, Feng Zhao (Microsoft Research),
Andre Santanche (UNICAMP)

Mobility Centric Campus Area Sensor Network for Locality Specific
Applications
Mukundan Sridharan, Anish Arora, Rajiv Ramnath, Emre Ertin (The Ohio
State University)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
***************Posters*******************
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Routing and Processing Multiple Aggregate Queries in Sensor Networks
Niki Trigoni, Alexandre Guitton, Antonios Skordylis (University of
London)

Rateless Codes for Data Dissemination in Sensor Networks
Andrew Hagedorn, David Starobinski, Ari Trachtenberg (Boston University)

AMSecure: Secure Link-Layer Communication in TinyOS for IEEE 802.15.4-
based Wireless Sensor Networks
Anthony D Wood, John A Stankovic (University of Virginia)

Virtual Sensing Range
Emiliano Miluzzo, Nicholas D Lane, Andrew T Campbell (Dartmouth College)

uScan: A Lightweight Two-Tier Global Sensing CoverageDesign
Yu Gu, Tian He (University of Minnesota)

SkiScape Sensing
Shane B. Eisenman (Columbia University), Andrew T. Campbell
(Dartmouth College)

Channel Surfing: Defending WirelessSensor Networks from Jamming and
Interference
Wenyuan Xu, Wade Trappe, Yanyong Zhang (Rutgers University)

Energy Adaptation Techniques to Optimize Data Delivery in Store-and-
Forward Sensor Networks
Pei Zhang, Margaret Martonosi (Princeton Unviersity)

A Distributed Reliable Data Transport Strategy for Event Based
Wireless Sensor Networks
Yuyan Xue, Byrav Ramamurthy, Ying Lu (University of Nebraska - Lincoln)

Lowering Radio Duty Cycle Through Temperature Compensated Timing
Joakim Arfvidsson, Eric Park, Philip Levis (Stanford University)

Collaborative Scheduling of Event Types and Allocation of Rates for
Wireless Sensor Nodes with Multiple Sensing Units
Hidayet Ozgur Sanli, Hasan Cam (Arizona State University)

Kaizen: Improving Sensor Network Operating Systems
James Horey, Jean-Charles Tournier, Arthur B Maccabe (University of
New Mexico)

Achieving Realistic Sensing Area Modeling
Joengmin Hwang, Tian He, Yongdae Kim (University of Minnesota)

Is Data-Centric Storage and Querying Scalable?
Joon Ahn, Bhaskar Krishnamachari (USC)

Understanding the Causes of Packet Delivery Success and Failure in
Dense Wireless Sensor Networks
Kannan Srinivasan (Stanford University), Prabal Dutta, Arsalan
Tavakoli (UCB), Philip Levis (Stanford University)

WaveScope: A Signal-Oriented Data Stream Management System
Lewis Girod, Kyle Jamieson, Yuan Mei, Ryan Newton, Stanislav Rost,
Arvind Thiagarajan, Hari Balakrishnan, Samuel Madden (MIT/CSAIL)

Comprehensive Monitoring of CO2 Sequestration in Subalpine Forest
Ecosystems and its Relation to Global Warming
Lynette L. Laffea, Russ K. Monson, Ryan Manning, Ashly Glasser,
Richard Han (University of Colorado, Boulder), Steve Oncley, Jielun
Sun, Sean Burns, Steve Semmer, John Militzer (NCAR)

TINX A Tiny Index Design for Flash Memory on Wireless Sensor Devices
Ajay Mani, Manjunath B Rajashekhar, Philip Levis (Stanford University)

Wireless Sensor Networks for Structural Health Monitoring
Sukun Kim, Shamim Pakzad, David Culler, James Demmel, Gregory Fenves,
Steve Glaser (UCB), Martin Turon (Crossbow)




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



From mip6-bounces@ietf.org Tue Oct 10 09:37:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXHmM-0004pd-V0; Tue, 10 Oct 2006 09:36:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXHmL-0004oi-8S
	for mip6@ietf.org; Tue, 10 Oct 2006 09:36:17 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXHmJ-0005w0-W0
	for mip6@ietf.org; Tue, 10 Oct 2006 09:36:17 -0400
Received: from ipv6-3.int-evry.fr (ipv6-3.int-evry.fr [157.159.100.76])
	by smtp2.int-evry.fr (Postfix) with ESMTP id E40982FD6E;
	Tue, 10 Oct 2006 15:36:08 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1GXHoA-0000Jr-Oe; Tue, 10 Oct 2006 15:38:10 +0200
Date: Tue, 10 Oct 2006 15:38:10 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] WG LC: Yoshihiro Ohba's review
Message-ID: <20061010133810.GA1208@ipv6-3.int-evry.fr>
References: <C147E294.257AE%basavaraj.patil@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C147E294.257AE%basavaraj.patil@nokia.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a6ea8837e8866a83aa68ed7cf9155ec9
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,

   please find below a review of Yoshihiro Obha for the document
   draft-ietf-mip6-aaa-ha-goals-03.txt.

   Thanks a lot yoshi for this review.


Mobile IPv6 WG                                               G. Giaretta
Internet-Draft                                               I. Guardini
Intended status: Standards Track                              E. Demaria
Expires: March 16, 2007                                   Telecom Italia
                                                            J. Bournelle
                                                                 GET/INT
                                                                R. Lopez
                                                         Univ. of Murcia
                                                      September 12, 2006


                       AAA Goals for Mobile IPv6
                    draft-ietf-mip6-aaa-ha-goals-03

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 March 16, 2007.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   In commercial deployments Mobile IPv6 can be a service offered by a
   Mobility Services Provider (MSP).  In this case all protocol

YO: Why just for commercial deployments?  I think it is also useful
for other AAA deployments such as enterprise usage.


   operations may need to be explicitly authorized and traced, requiring



Giaretta, et al.         Expires March 16, 2007                 [Page 1]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   the interaction between Mobile IPv6 and the AAA infrastructure.
   Integrating the AAA infrastructure offers also a solution component
   for Mobile IPv6 bootstrapping in integrated and split scenarios.

YO: I believe readers do not understand the above sentence without
explaining what integrated and split scenarios are.  Can we simply
remove the above sentence from Abstract?

   This document describes various scenarios where a AAA interface for
   Mobile IPv6 is actually required.  Additionally, it lists design
   goals and requirements for such an interface.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Bootstrapping Scenarios  . . . . . . . . . . . . . . . . . . .  4
     4.1.  Split Scenario . . . . . . . . . . . . . . . . . . . . . .  4
     4.2.  Integrated Scenario  . . . . . . . . . . . . . . . . . . .  5
   5.  Goals for the Split Scenario . . . . . . . . . . . . . . . . .  6
     5.1.  General goals  . . . . . . . . . . . . . . . . . . . . . .  6
     5.2.  Service Authorization  . . . . . . . . . . . . . . . . . .  7
     5.3.  Accounting . . . . . . . . . . . . . . . . . . . . . . . .  7
     5.4.  Mobile Node Authentication . . . . . . . . . . . . . . . .  8
     5.5.  Provisioning of Configuration Parameters . . . . . . . . .  8
   6.  Goals for the Integrated Scenario  . . . . . . . . . . . . . .  8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     10.1. Normative References . . . . . . . . . . . . . . . . . . .  9
     10.2. Informative References . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
   Intellectual Property and Copyright Statements . . . . . . . . . . 12



















Giaretta, et al.         Expires March 16, 2007                 [Page 2]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


1.  Introduction

   Mobile IPv6 [1] was originally designed as a protocol without any
   integration with the AAA infrastructure.  Nonetheless, in some
   environments it might be desirable to authenticate the user based on
   existing credentials stored at the AAA server to authorize protocol
   operations, to enable accounting and credit control.  Due to this
   requirement, Mobile IPv6 might require the interaction with the AAA
   infrastructure.  Integrating the AAA infrastructure offers also a
   solution component for Mobile IPv6 bootstrapping [2] in split [3] and
   integrated [4] scenarios.

YO: The first sentence may give an impression that we are going to
modifiy Mobile IPv6 protocol to interface with AAA, which is not true.
I think what we should probably convey here is something like:

"
   Mobile IPv6 [1] provides the basic IP mobility functionality for
   IPv6.  When Mobile IPv6 is used in tightly managed environments
   with the use of the AAA (Authentication, Authorization and
   Accounting) infrastructure, an interface between Mobile IPv6 and
   AAA protocols needs to be defined.  Also, two scenarios for
   bootstrapping Mobile IPv6 service [2], i.e., split [3] and
   integrated [4] scenarios, must be supported by such an interface.
"

   This document describes various scenarios where a AAA interface is
   required.  Additionally, it lists design goals and requirements for
   such an interface.

   This document only describes requirements, goals and scenarios.  It
   does not provide solutions.

   Notice that this document builds on the security model of the AAA
   infrastructure.  As such, the end host/user shares credentials with
   the home AAA server and the communication between the AAA server and
   the AAA client may be protected.  If the AAA server and the AAA
   client are not part of the same administrative domain, then some sort
   of contractual relationship between the involved administrative
   domains is typically in place in form of roaming agreements.

YO: This document seems to assume the use of IPsec between MN and HA
for securing Mobile IPv6 signaling.  But the AAA interface could also
be used for RFC 4285.  So I think it might be good to mention in this
section that the document may not preclude the use of alternative
methods for securing Mobile IPv6 signaling between MN and HA while
this document focuses on the use of IPsec between MN and HA.

2.  Terminology

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

   Some of the terms are also extracted from [2].


3.  Motivation

YO: I think that most of the contents of this section is already
described in RFC 4680.  Can we simply remove this section and just
refer to RFC 4680 in the Introduction?


   Mobile IPv6 specification [1] requires that Mobile Nodes (MNs) are
   provisioned with a set of configuration parameters, namely the Home
   Address and the Home Agent Address, in order to accomplish a home
   registration.  Moreover, MNs and Home Agents (HAs) must share the
   cryptographic material needed in order to setup IPsec security
   associations to protect Mobile IPv6 signaling (e.g. shared keys or
   certificates).

   One approach is to statically provision the necessary configuration



Giaretta, et al.         Expires March 16, 2007                 [Page 3]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   parameters at MNs and HAs.  This solution is sub-optimal from a
   deployment perspective, especially in large networks with a lot of
   users (e.g., a mobile operator network).  For this reason the Mobile
   IPv6 bootstrapping problem was investigated and is described in [2].
   Based on the analysed scenarios, two solutions were developed.  The
   solution for the split scenario is described in [3] and the one for
   the integrated scenario can be found at [4].  A key point behind
   these scenarios is that, whenever static provisioning is not
   feasible, the AAA infrastructure of the MSP can be used as the
   central element to enable dynamic Mobile IPv6 bootstrapping.  In this
   case the AAA infrastructure can be exploited to offload the end
   host's authentication to the AAA server as well as to deliver the
   necessary configuration parameters to the HA.

   Moreover, in case Mobile IPv6 is a service offered by a Mobility
   Service Provider (MSP), all protocol operations (e.g., home
   registrations) may need to be explicitly authorized and monitored
   (e.g., for accounting purposes).  This can be accomplished relying on
   the AAA infrastructure of the MSP that stores user profiles and
   credentials.

   In the split scenario, the deployment of this service model requires
   the availability of an interface between the Home Agent and the AAA
   infrastructure.  The core capabilities that should be supported by
   this interface include Mobile IPv6 service authorization and
   maintenance (e.g. asynchronous service termination) as well as the
   exchange of accounting data.  This basic set of features is needed in
   any Mobile IPv6 bootstrapping scenario.  In the integrated scenario,
   the AAA server also delivers some Mobile IPv6 parameters to the NAS.


4.  Bootstrapping Scenarios

   This section describes some bootstrapping scenarios in which a
   communication between the AAA infrastructure of the Mobility Service
   Provider and the Home Agent is needed.

YO: Section 4.2 also discusses communication between NAS and the AAA
infrastructure of ASP.


4.1.  Split Scenario

   In the split scenario [3], there is the assumption that the mobility
   service and network access service are not provided by the same
   administrative entity.  This implies that the mobility service can be
   authorized by a different entity deploying its own AAA
   infrastructure.  The entity offering the mobility service is called
   Mobility Service Provider (MSP) while the entity authorizing the
   service is the Mobility Service Authorizer (MSA).

YO: Can we define MSP, MSA, ASP and ASP in Section 2?  I know those
terms are defined in [2], but we can reiterate the definition in this
document.  Once the terms are defined, we can remove the last
sentence.


   In this scenario, the Mobile Node discovers the Home Agent Address



Giaretta, et al.         Expires March 16, 2007                 [Page 4]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   using the Domain Name Service (DNS).  It queries the address based on
   the Home Agent name or by service name.  In the former case, the
   Mobile Node is configured with the Fully Qualified Domain Name (FDQN)
   of the Home Agent.  In the latter case, [3] defines a new service
   resource record (SRV RR).

   Then the Mobile Node performs an IKEv2 [6] exchange with the HA to
   setup IPsec SAs (to protect Mobile IPv6 signaling) and to configure
   its Home Address (HoA).  The IKEv2 Mobile Node to Home Agent
   authentication can be done using either public key signatures or the
   Extensible Authentication Protocol (EAP).

YO: I think this authentication must be mutually done, not one
one-way.  Also public key may be used within EAP methods as described
in the next paragraph.  So I think the above sentence can be revised
as follows:

"
Mutual authentication for IKEv2 between Mobile Node and Home Agent can
be done with or without use of Extensible Authentication Protocol
(EAP).
"

   If EAP is used for authentication, the operator can choose any
   available EAP methods.  Note that even if EAP is used, the MN
   authenticates the HA using public key based authentication.  Based on

YO: I don't see a significance of mentioning public key based
authentication in this section.  This note can be removed.

   IKEv2, the HA may rely on a remote EAP server.  In this case, a AAA
   protocol such as RADIUS EAP [7]/Diameter EAP [8] must be used between
   the HA and the home EAP server.  This allows a pool of HAs to rely on
   the same EAP server to authenticate Mobile Nodes.   In this case, a AAA 
   protocol such as RADIUS EAP [7]/Diameter EAP [8] must be used between
   the HA and the home EAP server.  This allows a pool of HAs to rely on
   the same EAP server to authenticate Mobile Nodes.  It also allows the
   roaming mobility case in which the Mobile Node obtains the mobility
   service in a different administrative domain (MSP != MSA).

Probably the above paragraph can be simplified something like:

"
   If EAP is used for authentication, the operator can choose any
   available EAP methods.  Use of EAP with the AAA infrastructure
   allows the HA for not necessarily maintaining authentication
   credentials for each Mobile Node by itself.  It also allows roaming
   in terms of Mobile IPv6 service where MSP and MSA belong to
   different administrative domains.
"

   The Mobile Node may also want to update its FQDN in the DNS with the
   newly allocated Home Address. [3] recommends that the HA performs the
   DNS entry update on behalf of the Mobile Node.  For that purpose, the
   Mobile Node indicates its FDQN in the IKEv2 exchange (IDii field in
   IKE_AUTH) and adds a DNS Update Option in the Binding Update message
   sent to the HA.

   When the Mobile Node uses a Home Agent belonging to a different
   administrative domain (MSP != MSA), the local HA may not share a
   security association with the home DNS server.  In this case, [3]
   suggests that the home AAA server is responsible for the update.
   Thus, the HA should send to the home AAA server the (FDQN, HoA) pair.

   Note that the AAA exchange between the HA and the AAA server is
   normally terminated before the HA receives the Binding Update
   message.  The reason is that the authentication has succeeded if the
   Mobile Node is able to send the BU.

YO: What is the siginificance of having this note in this section?
Can we simply remove this note?


4.2.  Integrated Scenario

   In the integrated scenario [4], the assumption is that the user is
   authenticated and authorized by the same authorizer than network
   access service.  The Mobility Service Authorizer (MSA) and the Access
   Service Authorizer (ASA) are the same entity.

YO: The above text may be changed to:

"
   In the integrated scenario [4], the user is authenticated and
   authorized for both network access service and mobility service by
   the same administrative domain.  In this case, the Mobility Service
   Authorizer (MSA) and the Access Service Authorizer (ASA) are the
   same entity.
"

   Two scenarios are possible.  In the first case, the Home Agent is
   allocated by the user's home domain.  In the second case it is



Giaretta, et al.         Expires March 16, 2007                 [Page 5]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   allocated by an entity in the visited domain.  In both cases, it is

s/by an entity in the visited domain/by the visited domain/.

   assumed that the AAA server in the home domain (AAAH) authorizes both
   network access service and mobility service.

YO: The context of the last sentence is already covered in the first
paragraph and can be removed.


   In this scenario, Mobile Node discovers the Home Agent Address using
   DHCPv6.  During network access service authentication and
   authorization, AAAH also verifies if authenticating user is
   authorized to use mobility service.  In affirmative case, the AAAH
   sends the information about the assigned home agent to the Network
   Access Server (NAS) where the Mobile Node is currently attached.
   Then, the NAS stores the received information.  To request home agent
   data, the Mobile Node sends a DHCPv6 Information Request to the
   All_DHCP_Relay_Agents_and_Servers multicast address.  With this
   request, the Mobile Node can specify if it wants a home agent
   provided by the visited domain (ASP/MSP) or by the home domain (ASA/
   MSA).  In both cases, the NAS acts a DHCPv6 relay.  When the NAS
   receives the DHCPv6 Information Request then it sends home agent
   information received from AAAH in a new DHC Relay Agent Option as
   defined in [9].

   In case the Mobile Node cannot acquire home agent information via
   DHCPv6, it can try the default mechanism based on DNS described in
   [3].  After the Mobile Node has acquired the home agent information,
   the mechanism used to bootstrap the HoA, IPsec Security Association,
   and Authentication and Authorization with the MSA is the same
   described in the bootstrapping solution for split scenario [3].


5.  Goals for the Split Scenario

   Section 4 raises the need to define extensions for the AAA protocol
   used between the AAAH server and the HA.  The following sections list
   a set of goals.

5.1.  General goals

YO: If the intent is to describe general AAA goals in this document,
the current set of goals described in this section is insufficient.
You may take a look at Section 2.1 of RFC 2989 for more detailed list.

   G1.1  The AAAH server and the HA MUST be able to authenticate each
      other (mutual authentication) in order to prevent the installation
      of unauthorized state on the HA.  In some deployment scenarios, it
      may not be feasible for HA and AAAH to mutually authenticate each
      other.  For example, let us consider the case where MSP is not the
      MSA.  In such a case, several AAA intermediate proxies could
      forward MIP6 bootstrapping information back and forth between HA
      and AAA.  Thus, to prevent the installation of unauthorized state
      on the HA, the path between HA and AAAH should be trustworthy>/


Giaretta, et al.         Expires March 16, 2007                 [Page 6]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   G1.2  The AAA-HA interface MUST provide integrity protection in order
      to prevent any alteration of exchanged data (e.g., Mobile IPv6
      configuration parameters).

   G1.3  The AAA-HA interface MUST provide replay protection.

   G1.4  The AAA-HA interface SHOULD provide confidentiality since it
      may be used to transfer keying material (e.g., shared key
      generated during EAP method authentication).

   G1.5  The AAA-HA interface SHOULD support inactive peer detection.
      This functionality can be used by the AAAH server to maintain a
      list of active HAs.

YO: This can be done outside of AAA protocols.  AAAH server can just
ping to HAs.  I don't think this requiremet is a AAA requirement.


5.2.  Service Authorization

   G2.1  The AAA-HA interface SHOULD allow the use of Network Access
      Identifier (NAI) to identify the user.

YO: Why this is not "MUST allow"?


   G2.2  The HA SHOULD be able to query the AAAH server to verify Mobile
      IPv6 service authorization for the mobile node.

YO: I don't understand what "verify Mobile IPv6 service authorization
for the mobile node " means.  Please elaborate more on this goal.

   G2.3  The AAAH server MAY assign explicit operational limitations and
      authorization restrictions on the HA (e.g., packet filters, QoS
      parameters).

   G2.4  The AAAH server MUST be able to send an authorization lifetime
      to the HA to limit Mobile IPv6 session duration for the MN.

   G2.5  The HA MUST be able to request to the AAAH server an extension
      of the authorization lifetime granted to the MN.

   G2.6  The AAAH server MUST be able to force the HA to terminate an
      active Mobile IPv6 session for authorization policy reasons (e.g.,
      credit exhaustion).


5.3.  Accounting

   G3.1  The AAA-HA interface MUST support the transfer of accounting
      records needed for service control and charging.  These include
      (but may not be limited to): time of binding cache entry creation
      and deletion, octets sent and received by the mobile node in bi-
      directional tunneling, etc.




Giaretta, et al.         Expires March 16, 2007                 [Page 7]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


5.4.  Mobile Node Authentication

   G4.1  The AAA-HA interface MUST support pass-through EAP
      authentication with the HA working as EAP authenticator operating
      in pass-through mode and the AAAH server working as back-end
      authentication server.

YO: We can simplify the text something like:

"
   G4.1  The AAA-HA interface MUST allow the HA to act as a pass-through EAP
      authenticator.
"


5.5.  Provisioning of Configuration Parameters

   G5.1  The HA SHOULD be able to communicate to the AAAH server the
      Home Address allocated to the MN (e.g., for allowing the AAAH
      server to perform a DNS update on behalf of the MN).

YO: FQDN is missing here.

YO: Also, I am wondering if there is an option in which AAAH assigns a
home address or a home address prefix and communicate the assignment
to the HA.

   G5.2  The AAAH SHOULD be able to indicate to the HA if the MN is
      authorized to autoconfigure its Home Address.

YO: Why this is not "MUST be able to"? 



6.  Goals for the Integrated Scenario

   In the integrated scenario, the AAA server provides the HA
   information to the NAS as part of the whole AAA operations for
   network access.  Next goals are considered in addition to those
   described in section Section 5.

   G6.1  The AAAH server MUST be able to communicate the Home Agent
      Information (IP Address or FQDN) to the NAS.

   G6.2  The NAS SHOULD be able to notify that it supports the
      functionalities described in [4].

YO: The NAS notifies to whom?  I guess the NAS notifies AAAH server of
the functionalities.  If so, please explicitly mention it.  Also why
this is not "MUST be able to"?


   G6.3  The ASP/MSP SHOULD be able to indicate to the MSA if it can
      allocate a Home Agent to the MN.

YO: Why MSP is mentioned here?  Also why this is not "MUST be able to"?


   G6.4  The AAA server of the MSA MUST be able to indicate to the NAS
      whether the MN is authorized to use a local Home Agent (i.e. a
      Home Agent in the ASP/MSP)

YO: "MSA" should read "ASA/MSA".  Also "ASP/MSP" should read "MSP".

YO: Also, I would like to see the following discussions in this section:

- Whether the AAA-HA interface as well as AAA-NAS interface allow
authentication and authorization messages to be processed by different
AAA servers.

- In the integrated case, whether the AAA server for the AAA-HA
interface and the AAA server for the AAA-NAS interface can be
different.




7.  IANA Considerations

   This document does not require actions by IANA.







Giaretta, et al.         Expires March 16, 2007                 [Page 8]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


8.  Security Considerations

   As stated in Section 5.1 the AAA-HA interface must provide mutual
   authentication, integrity and replay protection.  Furthermore, if
   security parameters (e.g., IKE pre-shared key) are transferred
   through this interface, confidentiality is strongly recommended to be
   supported.  However note that AAA protocols does not support this
   unless it exists a direct connection between corresponding entities.

YO: Is there any scenario in which security parameters are not
transferred through this interface?




9.  Acknowledgements

   The authors would like to thank James Kempf, Alper Yegin, Vijay
   Devarapalli, Basavaraj Patil, Gopal Dommety and Madjid Nakhjiri for
   their comments and feedback.  Moreover the authors would like to
   thank Hannes Tschofenig for his deep technical and editorial review
   of the draft.


10.  References

10.1.  Normative References

   [1]  Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
        IPv6", RFC 3775, June 2004.

   [2]  Giaretta, G. and A. Patel, "Problem Statement for bootstrapping
        Mobile IPv6", draft-ietf-mip6-bootstrap-ps-05 (work in
        progress), May 2006.

YO: Replace the reference with RFC 4640.


   [3]  Giaretta, G., "Mobile IPv6 bootstrapping in split scenario",
        draft-ietf-mip6-bootstrapping-split-02 (work in progress),
        March 2006.

YO: The draft seems to be expired.

   [4]  Chowdhury, K. and A. Yegin, "MIP6-bootstrapping via DHCPv6 for
        the Integrated Scenario",
        draft-ietf-mip6-bootstrapping-integrated-dhc-01 (work in
        progress), June 2006.

   [5]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

10.2.  Informative References

   [6]   Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
         RFC 4306, December 2005.

   [7]   Aboba, B. and P. Calhoun, "RADIUS (Remote Authentication Dial



Giaretta, et al.         Expires March 16, 2007                 [Page 9]

Internet-Draft          AAA Goals for Mobile IPv6         September 2006


         In User Service) Support For Extensible Authentication Protocol
         (EAP)", RFC 3579, September 2003.

   [8]   Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
         Authentication Protocol (EAP) Application", RFC 4072,
         August 2005.

   [9]   Yegin, A., "DHCP Option for Home Agent Discovery in MIPv6",
         draft-jang-dhc-haopt-02 (work in progress), March 2006.

   [10]  Chowdhury, K. and A. Lior, "RADIUS Attributes for Mobile IPv6
         bootstrapping", draft-chowdhury-mip6-bootstrap-radius-01 (work
         in progress), November 2004.

YO: This draft seems to be expired.

   [11]  Giaretta, G., "MIPv6 Authorization and Configuration based on
         EAP", draft-giaretta-mip6-authorization-eap-03 (work in
         progress), March 2006.

YO: This draft seems to be expired.

(snip)



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



From mip6-bounces@ietf.org Tue Oct 10 11:16:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXJKi-0001IL-J6; Tue, 10 Oct 2006 11:15:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXJKg-0001I9-Me
	for mip6@ietf.org; Tue, 10 Oct 2006 11:15:50 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXJKf-0008N4-DD
	for mip6@ietf.org; Tue, 10 Oct 2006 11:15:50 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9AFFltW013020
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Tue, 10 Oct 2006 08:15:48 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9AFFWip017973
	for <mip6@ietf.org>; Tue, 10 Oct 2006 08:15:47 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Oct 2006 08:12:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Oct 2006 08:12:00 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A109@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: issue 75: Authors on the front page should be less than 6
thread-index: Acbsfm82hfu8jy+GT3y3AmTrsdHBhw==
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 10 Oct 2006 15:12:02.0392 (UTC)
	FILETIME=[707D1D80:01C6EC7E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [Mip6] issue 75: Authors on the front page should be less than 6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Issue text:
-----------
According to a guideline the number of authors on frontpage should be 5
or less.
Propose to keep an editor and list the co-authors in a different
section.

Conclusion:
-----------

We haven't discussed this in the DT, so I'd like to ask the WG to
express opinions on this. Please suggest on of the following options:

1. reject: implies keeping the authors list as is.
2. accept: implies keeping the editor on the front page and moving the
rest to an "Additional Authors" section.=20

Hesham

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



From mip6-bounces@ietf.org Tue Oct 10 12:43:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXKgi-0005L1-3I; Tue, 10 Oct 2006 12:42:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXKgg-0005JS-Nn
	for mip6@ietf.org; Tue, 10 Oct 2006 12:42:38 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXKge-0005BG-A8
	for mip6@ietf.org; Tue, 10 Oct 2006 12:42:38 -0400
Message-ID: <043901c6ec8b$59b21490$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
References: <7EB20EA0938B4D42A2D82689365C9B7A24A109@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
Date: Tue, 10 Oct 2006 09:44:27 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I'm fine with listing Hesham as the editor and putting other co-authors in 
the Contributor's section. He's done most of the work on this draft. BTW, 
I'm a co-author.

            jak

----- Original Message ----- 
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
Sent: Tuesday, October 10, 2006 8:12 AM
Subject: [Mip6] issue 75: Authors on the front page should be less than 6


Issue text:
-----------
According to a guideline the number of authors on frontpage should be 5
or less.
Propose to keep an editor and list the co-authors in a different
section.

Conclusion:
-----------

We haven't discussed this in the DT, so I'd like to ask the WG to
express opinions on this. Please suggest on of the following options:

1. reject: implies keeping the authors list as is.
2. accept: implies keeping the editor on the front page and moving the
rest to an "Additional Authors" section.

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 Tue Oct 10 13:42:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXLca-0000YF-20; Tue, 10 Oct 2006 13:42:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXLcY-0000YA-Qr
	for mip6@ietf.org; Tue, 10 Oct 2006 13:42:26 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXLcW-0000Bf-Fl
	for mip6@ietf.org; Tue, 10 Oct 2006 13:42:26 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6X00CHXL1A5N@usaga01-in.huawei.com> for
	mip6@ietf.org; Tue, 10 Oct 2006 10:39:10 -0700 (PDT)
Received: from huawei6cc10c70
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J6X00FI9L16LK@usaga01-in.huawei.com> for mip6@ietf.org;
	Tue, 10 Oct 2006 10:39:10 -0700 (PDT)
Date: Tue, 10 Oct 2006 10:42:12 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6
In-reply-to: <043901c6ec8b$59b21490$596015ac@dcml.docomolabsusa.com>
To: mip6@ietf.org
Message-id: <001801c6ec93$6b6a6400$2f01a8c0@huawei6cc10c70>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcbsjYhs/zD7+tUtTgK4Mx0R/oNyJgABFCkA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I have a new suggestion and it is not related to this document, just in
general. This would be a 3rd option.

XYZ 
editor
Additional authors

Along with list of additional authors in the back or like IEEE does, list
the authors in a second page. Although I think the former is easier with the
XML format.

Just putting the editor name on the front is not fair, especially since I
had cases where the editor came in at the very last. And I agree that
documents with long list of authors on the front page send a specific
message that is not desired. I did not know 6 was the magic number.

R,

Madjid

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com] 
Sent: Tuesday, October 10, 2006 9:44 AM
To: Soliman, Hesham; mip6@ietf.org
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than
6

I'm fine with listing Hesham as the editor and putting other co-authors in 
the Contributor's section. He's done most of the work on this draft. BTW, 
I'm a co-author.

            jak

----- Original Message ----- 
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
Sent: Tuesday, October 10, 2006 8:12 AM
Subject: [Mip6] issue 75: Authors on the front page should be less than 6


Issue text:
-----------
According to a guideline the number of authors on frontpage should be 5
or less.
Propose to keep an editor and list the co-authors in a different
section.

Conclusion:
-----------

We haven't discussed this in the DT, so I'd like to ask the WG to
express opinions on this. Please suggest on of the following options:

1. reject: implies keeping the authors list as is.
2. accept: implies keeping the editor on the front page and moving the
rest to an "Additional Authors" section.

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 Tue Oct 10 14:25:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXMIA-0004mx-Ib; Tue, 10 Oct 2006 14:25:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXMI9-0004mr-LT
	for mip6@ietf.org; Tue, 10 Oct 2006 14:25:25 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXMI8-0001Hd-BA
	for mip6@ietf.org; Tue, 10 Oct 2006 14:25:25 -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] issue 75: Authors on the front page should be less than 6
Date: Tue, 10 Oct 2006 11:25:23 -0700
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C221AAB9@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] issue 75: Authors on the front page should be less than 6
Thread-Index: Acbsfm82hfu8jy+GT3y3AmTrsdHBhwAGlgog
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	<mip6@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

well, the guideline was put in when folks started having
a long list of authors to show how many companies support =20
a particular proposal. and it is just a guideline.=20
exceptions are allowed. a person's name appearing on the
front page depends on how much each person has contributed=20
to the draft.

(I am one of the listed authors. I would be fine if my
name is not listed on the front page for this particular
draft, but in general I think it is not fair).

Vijay

> -----Original Message-----
> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
> Sent: Tuesday, October 10, 2006 8:12 AM
> To: mip6@ietf.org
> Subject: [Mip6] issue 75: Authors on the front page should be=20
> less than 6
>=20
> Issue text:
> -----------
> According to a guideline the number of authors on frontpage=20
> should be 5
> or less.
> Propose to keep an editor and list the co-authors in a different
> section.
>=20
> Conclusion:
> -----------
>=20
> We haven't discussed this in the DT, so I'd like to ask the WG to
> express opinions on this. Please suggest on of the following options:
>=20
> 1. reject: implies keeping the authors list as is.
> 2. accept: implies keeping the editor on the front page and moving the
> rest to an "Additional Authors" section.=20
>=20
> Hesham
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Tue Oct 10 15:27:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXNGO-0002t9-N5; Tue, 10 Oct 2006 15:27:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXNGM-0002sP-LI; Tue, 10 Oct 2006 15:27:38 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GXNGL-0004z4-Nh; Tue, 10 Oct 2006 15:27:38 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6X00EG2PWVG9@usaga01-in.huawei.com>; Tue,
	10 Oct 2006 12:24:31 -0700 (PDT)
Received: from huawei6cc10c70
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J6X00FL9PWOL4@usaga01-in.huawei.com>; Tue,
	10 Oct 2006 12:24:31 -0700 (PDT)
Date: Tue, 10 Oct 2006 12:27:30 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: [Dime] Fwd: [Mip6]  WG LC for I-d: draft-ietf-mip6-aaa-ha-goals-03
In-reply-to: <eaa74a7e0610030812j15d36cc2i1c0eb77181b1eae8@mail.gmail.com>
To: 'Gerardo Giaretta' <gerardo.giaretta@gmail.com>, dime@ietf.org,
	mip6@ietf.org
Message-id: <001c01c6eca2$215232d0$2f01a8c0@huawei6cc10c70>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acbm/x6JOiS47psmR8qr340RUmeLWAFojryQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2d1100b36d83fed07afbc292d8848e10
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 folks, 

I was asked to review and comment on the MIP6-AAA-HA-goals-03.
Please find the comments below, I cut out the sections I did not have
comments on.

Hope this helps,
Regards,

Madjid
                       AAA Goals for Mobile IPv6
                    draft-ietf-mip6-aaa-ha-goals-03

Status of this Memo



Giaretta, et al.         Expires March 16, 2007                 [Page 2]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


1.  Introduction

   Mobile IPv6 [1] was originally designed as a protocol without any
   integration with the AAA infrastructure.  Nonetheless, in some
   environments it might be desirable to authenticate the user based on
   existing credentials stored at the AAA server to authorize protocol
   operations, to enable accounting and credit control.  

Madjid>>I would suggest rewording:
/Nonetheless, in some environment it might be desirable to refer to the AAA
infrastructure and servers for 

authentication of user identity, authorization of Mobile IPv6 service to the
user, bootstrapping Mobile IPv6 

parameters, and accounting and credit control services. 

Due to this
   requirement, Mobile IPv6 might require the interaction with the AAA
   infrastructure.

Madjid>>"requirement" is a strong word here. We know 3775 stands on its own.
Suggestion: 
Therefore, it is desired that the interaction of Mobile IPv6 with the AAA
infrastructure to obtain these 

services is designed in a more structured manner.


 Integrating the AAA infrastructure offers also a
   solution component for Mobile IPv6 bootstrapping [2] in split [3] and
   integrated [4] scenarios.

   This document describes various scenarios where a AAA interface is
   required.  Additionally, it lists design goals and requirements for
   such an interface.

   This document only describes requirements, goals and scenarios.  It
   does not provide solutions.

   Notice that this document builds on the security model of the AAA
   infrastructure.  As such, the end host/user shares credentials with
   the home AAA server and the communication between the AAA server and
   the AAA client may be protected. 

Madjid>>the notion of home server needs to be explained better. I am
guessing this is the AAA server of the 

home MSP. (and when we go into authn versus authz, then you even may have
AAA_EAP for authentication 

purposes, while its MIP-AAA for authorization, both with MSP I guess).
Also "may" in "may be protected" is a bit too weak, given that this is a
"goal/requirement" doc.

 If the AAA server and the AAA
   client are not part of the same administrative domain, then some sort
   of contractual relationship between the involved administrative
   domains is typically in place in form of roaming agreements.

Madjid>> I hope these agreements are between AAA servers of the two domains.


2.  Terminology

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

   Some of the terms are also extracted from [2].


3.  Motivation

   Mobile IPv6 specification [1] requires that Mobile Nodes (MNs) are
   provisioned with a set of configuration parameters, namely the Home
   Address and the Home Agent Address, in order to accomplish a home
   registration.  Moreover, MNs and Home Agents (HAs) must share the
   cryptographic material needed in order to setup IPsec security
   associations to protect Mobile IPv6 signaling (e.g. shared keys or
   certificates).

   One approach is to statically provision the necessary configuration



Giaretta, et al.         Expires March 16, 2007                 [Page 3]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   parameters at MNs and HAs.  This solution is sub-optimal from a
   deployment perspective, especially in large networks with a lot of
   users (e.g., a mobile operator network).  For this reason the Mobile
   IPv6 bootstrapping problem was investigated and is described in [2].
   Based on the analysed scenarios, two solutions were developed.  The
   solution for the split scenario is described in [3] and the one for
   the integrated scenario can be found at [4].  A key point behind
   these scenarios is that, whenever static provisioning is not
   feasible, the AAA infrastructure of the MSP can be used as the
   central element to enable dynamic Mobile IPv6 bootstrapping.  In this
   case the AAA infrastructure can be exploited to offload the end
   host's authentication to the AAA server as well as to deliver the
   necessary configuration parameters to the HA.

   Moreover, in case Mobile IPv6 is a service offered by a Mobility
   Service Provider (MSP), all protocol operations (e.g., home
   registrations) may need to be explicitly authorized and monitored
   (e.g., for accounting purposes).  This can be accomplished relying on
   the AAA infrastructure of the MSP that stores user profiles and
   credentials.

   In the split scenario, the deployment of this service model requires
   the availability of an interface between the Home Agent and the AAA
   infrastructure.  The core capabilities that should be supported by
   this interface include Mobile IPv6 service authorization and
   maintenance (e.g. asynchronous service termination) as well as the
   exchange of accounting data.  This basic set of features is needed in
   any Mobile IPv6 bootstrapping scenario.  In the integrated scenario,
   the AAA server also delivers some Mobile IPv6 parameters to the NAS.

Madjid>>This is an editorial/organizational comment: I don't think the
paragraph above belong here for two 

reasons: 1) it comes before description of bootstrapping scenarios, while
making very key statements about 

those 2) I don't see this as "motivation".
I don't have a good suggestion, but it seems that beginning of section 5 is
better place for this.
Finally, there seems to be an explicit assumption about taking the
authentication out of the AAA function 

for split case. The way I understand it, split case does have an
authentication with the MSP-AAAH, it is 

just not part of the Diameter-MIP6 application. So this text should explain
why all of the sudden from the 

text in the intro (including all 3 As in AAA) we are down to two.


4.  Bootstrapping Scenarios

   This section describes some bootstrapping scenarios in which a
   communication between the AAA infrastructure of the Mobility Service
   Provider and the Home Agent is needed.

4.1.  Split Scenario

   In the split scenario [3], there is the assumption that the mobility
   service and network access service are not provided by the same
   administrative entity.  This implies that the mobility service can be
   authorized by a different entity deploying its own AAA
   infrastructure.  The entity offering the mobility service is called
   Mobility Service Provider (MSP) while the entity authorizing the
   service is the Mobility Service Authorizer (MSA).

Madjid>>Again, the text above is very confusing. It talks about MSP and ASP
and their AAA server without 

showing any of the acronyms. Then it goes into MSP versus MSA and looses the
mention of AAA server again. If 

this document is about HA-AAA goals, then we should really be clear about
where the AAA servers are, for 

instance say that MSA is home MIP-AAA server.
Here is my suggestion for rewording (still not perfect, but less confusing):

In the split scenario [3], there is the assumption that the mobility
   service and network access service are not provided by the same
   administrative entity. This implies that the mobility service can be
   provided by a provider (MSP) that is different from the operator
providing access service (ASP).
Each of the MSP and ASP may be deploying its own AAA infrastructure, and
authorizers (MSA and ASA, 

respectively). Furthermore, the entity offering the mobility service
(Mobility Service Provider, MSP) may be 

different from the user's home mobility service provider (home-MSP). Since
user's home mobility service 

provider is the entity authorizing the Mobility service for the user
(performing home AAA function for the 

user's Mobile IP functions), this entity is seen as the Mobility Service
Authorizer (MSA).


   In this scenario, the Mobile Node discovers the Home Agent Address



Giaretta, et al.         Expires March 16, 2007                 [Page 4]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   using the Domain Name Service (DNS).  It queries the address based on
   the Home Agent name or by service name.  In the former case, the
   Mobile Node is configured with the Fully Qualified Domain Name (FDQN)
   of the Home Agent.  In the latter case, [3] defines a new service
   resource record (SRV RR).

   Then the Mobile Node performs an IKEv2 [6] exchange with the HA to
   setup IPsec SAs (to protect Mobile IPv6 signaling) and to configure
   its Home Address (HoA).  The IKEv2 Mobile Node to Home Agent
   authentication can be done using either public key signatures or the
   Extensible Authentication Protocol (EAP).

   If EAP is used for authentication, the operator can choose any
   available EAP methods.  Note that even if EAP is used, the MN
   authenticates the HA using public key based authentication.  

Madjid>>I believe you need to say "MN may authenticate the HA using public
key..."
Or are you saying that MN always authenticates HA with public keys.


Based on
   IKEv2, the HA may rely on a remote EAP server.  In this case, a AAA
   protocol such as RADIUS EAP [7]/Diameter EAP [8] must be used between
   the HA and the home EAP server.  This allows a pool of HAs to rely on
   the same EAP server to authenticate Mobile Nodes.  It also allows the
   roaming mobility case in which the Mobile Node obtains the mobility
   service in a different administrative domain (MSP != MSA).

   The Mobile Node may also want to update its FQDN in the DNS with the
   newly allocated Home Address. [3] recommends that the HA performs the
   DNS entry update on behalf of the Mobile Node.  For that purpose, the
   Mobile Node indicates its FDQN in the IKEv2 exchange (IDii field in
   IKE_AUTH) and adds a DNS Update Option in the Binding Update message
   sent to the HA.

   When the Mobile Node uses a Home Agent belonging to a different
   administrative domain (MSP != MSA), the local HA may not share a
   security association with the home DNS server.  

Madjid>>Administrative domain refers to AAAs. Again, the text above is
confusing MSP=!MSA is very confusing, 

since it mixes several orthogonal concepts: 1) operators and their AAA/
admin domain 2) home and visited 

concepts.

The introduced terminology is simply replacing well known AAA terms:
 
in AAA terminology this is simply called Home versus visited operators and
home versus visited AAAs.
I would simply say that the HA belongs to a visited MSP, while MIP service
to MN is authorized by home 

MSP-AAA.

In this case, [3]
   suggests that the home AAA server is responsible for the update.
   Thus, the HA should send to the home AAA server the (FDQN, HoA) pair.
   Note that the AAA exchange between the HA and the AAA server is
   normally terminated before the HA receives the Binding Update
   message.  The reason is that the authentication has succeeded if the
   Mobile Node is able to send the BU.

4.2.  Integrated Scenario

   In the integrated scenario [4], the assumption is that the user is
   authenticated and authorized by the same authorizer than network
   access service. 

Madjid>>suggestion for rewording: 
"user is authenticated and authorized for Mobility service by the same
authorizer (AAA server/ 

infrastructure) that used for network access service. In other words, "

 The Mobility Service Authorizer (MSA) and the Access
   Service Authorizer (ASA) are the same entity.

   Two scenarios are possible.  In the first case, the Home Agent is
   allocated by the user's home domain.  In the second case it is



Giaretta, et al.         Expires March 16, 2007                 [Page 5]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   allocated by an entity in the visited domain.  In both cases, it is
   assumed that the AAA server in the home domain (AAAH) authorizes both
   network access service and mobility service.

Madjid>> the last sentence above, should be moved to the end of the first
paragraph for this section.

   In this scenario, Mobile Node discovers the Home Agent Address using
   DHCPv6.  During network access service authentication and
   authorization, AAAH also verifies if authenticating user is
   authorized to use mobility service.  In affirmative case, the AAAH
   sends the information about the assigned home agent to the Network
   Access Server (NAS) where the Mobile Node is currently attached.
   Then, the NAS stores the received information.  To request home agent
   data, the Mobile Node sends a DHCPv6 Information Request to the
   All_DHCP_Relay_Agents_and_Servers multicast address.  With this
   request, the Mobile Node can specify if it wants a home agent
   provided by the visited domain (ASP/MSP) or by the home domain (ASA/
   MSA). 

Madjid>>again this should say "visited domain (visited ASP/MSP) or by the
home domain (home ASA/MSA).
The text is confusing domains/ providers/AAA servers...


 In both cases, the NAS acts a DHCPv6 relay.  When the NAS
   receives the DHCPv6 Information Request then it sends home agent
   information received from AAAH in a new DHC Relay Agent Option as
   defined in [9].

   In case the Mobile Node cannot acquire home agent information via
   DHCPv6, it can try the default mechanism based on DNS described in
   [3].  After the Mobile Node has acquired the home agent information,
   the mechanism used to bootstrap the HoA, IPsec Security Association,
   and Authentication and Authorization with the MSA is the same
   described in the bootstrapping solution for split scenario [3].


5.  Goals for the Split Scenario

   Section 4 raises the need to define extensions for the AAA protocol
   used between the AAAH server and the HA.  The following sections list
   a set of goals.

5.1.  General goals

   G1.1  The AAAH server and the HA MUST be able to authenticate each
      other (mutual authentication) in order to prevent the installation
      of unauthorized state on the HA.  In some deployment scenarios, it
      may not be feasible for HA and AAAH to mutually authenticate each
      other.  For example, let us consider the case where MSP is not the
      MSA.  In such a case, several AAA intermediate proxies could
      forward MIP6 bootstrapping information back and forth between HA
      and AAA.  Thus, to prevent the installation of unauthorized state
      on the HA, the path between HA and AAAH should be trustworthy>/


Madjid>>again MSP versus MSA terminology issue. Plus the text is venturing
into something that is more of a 

AAA infrastructure issue than an HA-AAAH issue. Also the text is mixing end
point authentication and AAA 

signaling security all in one requirement. Mutual authentication of HA and
home AAA is one thing, protecting 

bootstrapping info over AAA messaging is another. This should be broken into
two requirements. I believe you 

have text on confidentiality in G1.4. The AAA signaling security issue is
that of a AAA client in visited 

AAA domain dealing with a home AAA domain are well known. for instance if
you don't like the transitive 

trust provided by the hop by hop security in RADIUS, so you need external
ways to cure the transitive trust 

problem. On the other hand providing a mutual authentication procedure
between HA and home AAA server 

without intervention of AAA intermediaries in a whole different problem. So
we need to be careful, otherwise 

we may end up ruling RADIUS out of here. Is that the intention?

I would simply state the well known issues in the security consideration
section.


Giaretta, et al.         Expires March 16, 2007                 [Page 6]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


   G1.2  The AAA-HA interface MUST provide integrity protection in order
      to prevent any alteration of exchanged data (e.g., Mobile IPv6
      configuration parameters).

   G1.3  The AAA-HA interface MUST provide replay protection.

   G1.4  The AAA-HA interface SHOULD provide confidentiality since it
      may be used to transfer keying material (e.g., shared key
      generated during EAP method authentication).

Madjid>>same comment as that on security in G1.1.

   G1.5  The AAA-HA interface SHOULD support inactive peer detection.
      This functionality can be used by the AAAH server to maintain a
      list of active HAs.


5.2.  Service Authorization

Madjid>>Typically authorization follows a successful authentication. It
seems that the burden of the making 

sure the MN is authenticated falls into the lap of the HA, should we not
have a requirement on this?

   G2.1  The AAA-HA interface SHOULD allow the use of Network Access
      Identifier (NAI) to identify the user.

Madjid>>I believe for the split scenario. We were saying that the
Diameter_EAP and Diameter-MIP need to use 

the same ID. does this cover that? Is NAI always the ID used for EAP?

   G2.2  The HA SHOULD be able to query the AAAH server to verify Mobile
      IPv6 service authorization for the mobile node.

   G2.3  The AAAH server MAY assign explicit operational limitations and
      authorization restrictions on the HA (e.g., packet filters, QoS
      parameters).

   G2.4  The AAAH server MUST be able to send an authorization lifetime
      to the HA to limit Mobile IPv6 session duration for the MN.

   G2.5  The HA MUST be able to request to the AAAH server an extension
      of the authorization lifetime granted to the MN.

   G2.6  The AAAH server MUST be able to force the HA to terminate an
      active Mobile IPv6 session for authorization policy reasons (e.g.,
      credit exhaustion).


5.3.  Accounting

   G3.1  The AAA-HA interface MUST support the transfer of accounting
      records needed for service control and charging.  These include
      (but may not be limited to): time of binding cache entry creation
      and deletion, octets sent and received by the mobile node in bi-
      directional tunneling, etc.






Giaretta, et al.         Expires March 16, 2007                 [Page 7]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


5.4.  Mobile Node Authentication

   G4.1  The AAA-HA interface MUST support pass-through EAP
      authentication with the HA working as EAP authenticator operating
      in pass-through mode and the AAAH server working as back-end
      authentication server.

Madjid>>Does this really have to be a MUST?

5.5.  Provisioning of Configuration Parameters

   G5.1  The HA SHOULD be able to communicate to the AAAH server the
      Home Address allocated to the MN (e.g., for allowing the AAAH
      server to perform a DNS update on behalf of the MN).

   G5.2  The AAAH SHOULD be able to indicate to the HA if the MN is
      authorized to autoconfigure its Home Address.



6.  Goals for the Integrated Scenario

   In the integrated scenario, the AAA server provides the HA
   information to the NAS as part of the whole AAA operations for
   network access.  Next goals are considered in addition to those
   described in section Section 5.

   G6.1  The AAAH server MUST be able to communicate the Home Agent
      Information (IP Address or FQDN) to the NAS.

   G6.2  The NAS SHOULD be able to notify that it supports the
      functionalities described in [4].

   G6.3  The ASP/MSP SHOULD be able to indicate to the MSA if it can
      allocate a Home Agent to the MN.

   G6.4  The AAA server of the MSA MUST be able to indicate to the NAS
      whether the MN is authorized to use a local Home Agent (i.e. a
      Home Agent in the ASP/MSP)



Giaretta, et al.         Expires March 16, 2007                 [Page 8]


Internet-Draft          AAA Goals for Mobile IPv6         September 2006


8.  Security Considerations

   As stated in Section 5.1 the AAA-HA interface must provide mutual
   authentication, integrity and replay protection.  Furthermore, if
   security parameters (e.g., IKE pre-shared key) are transferred
   through this interface, confidentiality is strongly recommended to be
   supported.  However note that AAA protocols does not support this
   unless it exists a direct connection between corresponding entities.

Madjid>> Diameter supports this. should say "some AAA protocols".



-----Original Message-----
From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com] 
Sent: Tuesday, October 03, 2006 8:13 AM
To: dime@ietf.org
Subject: [Dime] Fwd: [Mip6] WG LC for I-d: draft-ietf-mip6-aaa-ha-goals-03

FYI, please review the document.

--Gerardo

---------- Forwarded message ----------
From: Basavaraj Patil <basavaraj.patil@nokia.com>
Date: Oct 3, 2006 4:49 PM
Subject: [Mip6] WG LC for I-d: draft-ietf-mip6-aaa-ha-goals-03
To: mip6@ietf.org



Hello,

This is a Working group last call for the WG I-D: AAA Goals for Mobile
IPv6 (draft-ietf-mip6-aaa-ha-goals-03). The draft is intended to serve
as the AAA requirements for Mobile IPv6.

Please review the I-D and submit your comments to the authors or to
the list directly.

The WGLC expires on Oct 18th, 06.

The I-D is intended to be published as an Informational RFC.

-Raj


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

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



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



From mip6-bounces@ietf.org Tue Oct 10 18:01:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXPdu-0001MC-Hs; Tue, 10 Oct 2006 18:00:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXPdt-0001M7-7d
	for mip6@ietf.org; Tue, 10 Oct 2006 18:00:05 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXPdr-0005uK-S3
	for mip6@ietf.org; Tue, 10 Oct 2006 18:00:05 -0400
Received: from [10.1.201.21] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 14:57:34 -0700
Message-ID: <452C17E0.8010107@azairenet.com>
Date: Tue, 10 Oct 2006 15:00:00 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Oct 2006 21:57:35.0041 (UTC)
	FILETIME=[17E0B310:01C6ECB7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Subject: [Mip6] [Fwd: Fwd: I-D ACTION:draft-devarapalli-mip6-vsm-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

hello,

here is the revised version of the vendor specific
message document. the earlier version had both a
vendor specific mobility header message and a vendor
specific mobility option. at the last IETF, there
was some discussion on how it can be dangerous
(interoperability reasons) to have a vendor specific
mobility header message. so thats been removed.

comments are welcome.

Vijay

---------- Forwarded message ----------
From: Internet-Drafts@ietf.org <Internet-Drafts@ietf.org>
Date: Oct 9, 2006 12:50 PM
Subject: I-D ACTION:draft-devarapalli-mip6-vsm-01.txt
To: i-d-announce@ietf.org


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


        Title           : Mobile IPv6 Vendor Specific Messages
        Author(s)       : V. Devarapalli
        Filename        : draft-devarapalli-mip6-vsm-01.txt
        Pages           : 6
        Date            : 2006-10-9

There is a need for vendor specific extensions to Mobility Header
   messages so that Mobile IPv6 vendors are able to extend the protocol
   for research or deployment purposes.  This document defines a new
   vendor specific mobility option.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-devarapalli-mip6-vsm-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-devarapalli-mip6-vsm-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-devarapalli-mip6-vsm-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.




_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

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



From mip6-bounces@ietf.org Wed Oct 11 12:13:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXghz-00036u-Iy; Wed, 11 Oct 2006 12:13:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXghy-00033v-L4; Wed, 11 Oct 2006 12:13:26 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GXghx-0004cU-Gw; Wed, 11 Oct 2006 12:13:26 -0400
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 <0J6Z00DZ2C0046@szxga03-in.huawei.com>; Thu,
	12 Oct 2006 00:19:12 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J6Z00F92BZZ3Q@szxga03-in.huawei.com>; Thu,
	12 Oct 2006 00:19:12 +0800 (CST)
Received: from [127.0.0.1] ([10.124.12.208])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J6Z002Y0C33R5@szxml04-in.huawei.com>; Thu,
	12 Oct 2006 00:21:07 +0800 (CST)
Date: Wed, 11 Oct 2006 11:07:47 -0500
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: mip6@ietf.org, netlmm@ietf.org
Message-id: <452D16D3.6050800@yahoo.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: 
Subject: [Mip6] Re: [netlmm] Network-based mobility - NETLMM DT Solution Vs
 A solution based on MIP6
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>
Errors-To: mip6-bounces@ietf.org

Hi Marco,
  I was surprised to see you as a co-author in the netlmm DT solution 
(draft-giaretta) which has 8 authors!
  netlmm DT solution is addressing a network layer problem. I do not buy 
the arguments that we found a transport level solution and our solution 
is thus IP version agnostic. First of all if you are designing a new 
transport protocol you are in the wrong WG, you should go to the 
transport area. Secondly transport protocols are end-to-end.
  netlmm DT solution is a network layer protocol, just look at sections 
that talk about link local addresses, forwarding broadcast packets, etc. 
It just combines IPv6 and IPv4 operation in one document.
 
Regards,
 
--behcet

----- Original Message ----
From: Marco Liebsch <marco.liebsch@netlab.nec.de>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Cc: mip6@ietf.org; netlmm@ietf.org
Sent: Wednesday, October 11, 2006 4:35:36 AM
Subject: Re: [netlmm] Network-based mobility - NETLMM DT Solution Vs A 
solution based on MIP6

Hi Vidya,

I see that a MIPv6-based solution could suit some scenarios. However,
we should also consider extensions to very basic NetLMM, in particular
to support route optimization.
MIPv6 provides complex support for end-to-end route optimization,
which might not be appropriate for a NetLMM setup in some scenarios,
where the LMA might play some role in coordinating RO. Regarding your
points 2 and 3, I don't see any reason why DNS and DHCP cannot
be used to support LMA assignment in the DT solution.

In general, I see some advantage in a transport-based protocol for
NetLMM, such as the DT protocol draft; in particular regarding
extensions for optimization to suit all deployment scenarios.

I'd like to see one solution that suits various scenarios, neither
a single solution with limited support, nor multiple solutions for
various scenarios.

marco

Narayanan, Vidya wrote:

 >All,
 >This is an effort to kick start a discussion of the merits of each
 >approach and reach an agreement on the deltas and the importance of the
 >deltas. I have purposely avoided the use of the term "PMIPv6", since
 >there appears to be multiple interpretations of that among different
 >people. The comparison here is between the proposed NETLMM DT solution
 >(as in draft-giaretta-netlmm-dt-protocol-02) vs a solution that would be
 >based on using the Mobility Header (and hence be closely aligned to
 >MIP6). This is not intended to get into the degree of closeness to MIP6.
 >
 >
 >What does the NETLMM DT Solution bring, by being totally different from
 >MIP6?
 >------------------------------------------------------------------------
 >------
 >
 >1. The protocol can be evolved to using a reliable transport protocol
 >like SCTP at some point.
 >2. The protocol can run over IPv4 without changes.
 >
 >While these seem like good goals, what is the practical need for the
 >above goals? For instance, is IPv4 signaling a necessity for a NETLMM
 >solution?
 >
 >
 >What does a solution based on MIP6 bring?
 >------------------------------------------
 >A solution that uses the Mobility Header can re-use a number of already
 >defined options, some of them directly and some with minor changes. The
 >industry is seeking a network-based local mobility solution that can
 >still provide a number of features that a host-based mobility solution
 >can provide. So, over time, we will find ourselves addressing these
 >requirements and re-inventing these for NETLMM.
 >
 >Mobility options that can be re-used with an MH-based protocol like
 >PMIPv6:
 >
 >1. MN ID Mobility Option
 >
 >This option can pretty much be used with no changes.
 >
 >2. DNS-based HA lookup
 >
 >While some scenarios may not need this mechanism, it may make sense in
 >some deployments to use DNS for this purpose, even with PMIP6.
 >
 >3. DHCP-based HA lookup
 >- Home Network Identifier Option
 >- Home Network Information Option
 >- DHCP Relay Agent MIP6 Option, MIP6 HA sub-option
 >
 >Same as 2.
 >
 >4. DNS Update Mobility Option
 >
 >This can be used to update the DNS server with the address assigned to
 >the MN within the domain in which PMIP is deployed.
 >
 >5. DSMIP6 Options
 >- IPv4 HoA Mobility Option
 >- IPv4 address acknowledgement Mobility Option
 >- NAT Detection Mobility Option
 >
 >These options can be used without changes.
 >
 >5. HA Switch message
 >
 >Also useful for the same purpose as in MIP6 and can be used without
 >changes.
 >
 >6. Other HA reliability messages
 >
 >We need to wait for this work to stabilize a bit more before we can
 >tell, but we must be able to leverage off a lot of this work.
 >
 >7. Multiple CoA Registration
 >- BID Mobility Option
 >
 >Can be used to signal the addition of a location of the MN, rather than
 >a replace of location.
 >
 >8. Flow bindings support
 >- Flow ID Option
 >
 >When the edge is aware of the QoS needs of the MN (can happen via
 >out-of-band mechanisms), flow bindings can be conveyed to the HA using
 >the same mechanism as in MIP6.
 >
 >9. NEMO Support
 >- Prefix registration
 >- Prefix Assignment
 >
 >The extensions defined for NEMO support can largely be re-used to
 >register prefixes for the end node.
 >
 >Other points:
 >-------------
 >
 >1. Mechanisms such as the association phase for MAG-LMA discovery
 >described in the NELTMM DT protocol are potentially useful in certain
 >deployments of a network-based mobility solution. However, this should
 >be feasible to do in either approach.
 >
 >Thoughts?
 >
 >Regards,
 >Vidya

<https://www1.ietf.org/mailman/listinfo/netlmm>


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



From mip6-bounces@ietf.org Wed Oct 11 12:19:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXgnw-0005Y7-04; Wed, 11 Oct 2006 12:19:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXgnv-0005Xz-2H; Wed, 11 Oct 2006 12:19:35 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1GXgnt-0005L9-Nk; Wed, 11 Oct 2006 12:19:35 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-14.tower-128.messagelabs.com!1160583572!2304557!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 3705 invoked from network); 11 Oct 2006 16:19:32 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102)
	by server-14.tower-128.messagelabs.com with SMTP;
	11 Oct 2006 16:19:32 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id k9BGJRGW002494;
	Wed, 11 Oct 2006 09:19:31 -0700 (MST)
Received: from [10.161.201.117] ([10.161.201.117])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k9BGJPMG025148;
	Wed, 11 Oct 2006 11:19:26 -0500 (CDT)
Message-ID: <452D198C.8050004@motorola.com>
Date: Wed, 11 Oct 2006 18:19:24 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
References: <452D16D3.6050800@yahoo.com>
In-Reply-To: <452D16D3.6050800@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: mip6@ietf.org, netlmm@ietf.org
Subject: [Mip6] Re: [netlmm] Network-based mobility - NETLMM DT Solution Vs
 A solution based on MIP6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Behcet Sarikaya wrote:
> Hi Marco, I was surprised to see you as a co-author in the netlmm DT
> solution (draft-giaretta) which has 8 authors! netlmm DT solution is
> addressing a network layer problem. I do not buy the arguments that
> we found a transport level solution and our solution is thus IP
> version agnostic. First of all if you are designing a new transport
> protocol you are in the wrong WG, you should go to the transport
> area. Secondly transport protocols are end-to-end. netlmm DT solution
> is a network layer protocol, just look at sections that talk about
> link local addresses, forwarding broadcast packets, etc. It just
> combines IPv6 and IPv4 operation in one document.

Is MIP4 a network-layer or a transport layer protocol?  It uses UDP.

Is DS-MIPv6 network-layer or transport layer?  It uses UDP when
traversing NAT or IPv4.

Alex

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



From mip6-bounces@ietf.org Wed Oct 11 12:36:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXh4R-0006Qo-EL; Wed, 11 Oct 2006 12:36:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXh4P-0006Em-LW; Wed, 11 Oct 2006 12:36:37 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GXh4O-0007MT-2H; Wed, 11 Oct 2006 12:36:37 -0400
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 <0J6Z00D6TDAT46@szxga03-in.huawei.com>; Thu,
	12 Oct 2006 00:47:17 +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 <0J6Z00IA8DATEM@szxga03-in.huawei.com>; Thu,
	12 Oct 2006 00:47:17 +0800 (CST)
Received: from [127.0.0.1] ([10.124.12.208])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J6Z002UXD1H9O@szxml03-in.huawei.com>; Thu,
	12 Oct 2006 00:41:45 +0800 (CST)
Date: Wed, 11 Oct 2006 11:35:34 -0500
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Message-id: <452D1D56.8080804@yahoo.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
X-Spam-Score: 2.2 (++)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: mip6@ietf.org, netlmm@ietf.org
Subject: [Mip6] Re: [netlmm] Network-based mobility - NETLMM DT Solution Vs
 A solution based on MIP6
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>
Errors-To: mip6-bounces@ietf.org


Strictly speaking, they are layer 3.5.


From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: mip6@ietf.org; netlmm@ietf.org
Sent: Wednesday, October 11, 2006 11:19:24 AM
Subject: [Mip6] Re: [netlmm] Network-based mobility - NETLMM DT Solution 
Vs A solution based on MIP6

Is MIP4 a network-layer or a transport layer protocol?  It uses UDP.

Is DS-MIPv6 network-layer or transport layer?  It uses UDP when
traversing NAT or IPv4.

Alex



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



From mip6-bounces@ietf.org Wed Oct 11 12:52:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXhJ2-0005uk-NR; Wed, 11 Oct 2006 12:51:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXhJ0-0005uK-NC; Wed, 11 Oct 2006 12:51:42 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GXhIz-0001Ht-9a; Wed, 11 Oct 2006 12:51:42 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 11 Oct 2006 09:51:40 -0700
X-IronPort-AV: i="4.09,295,1157353200"; 
	d="scan'208"; a="330559821:sNHT60204776"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9BGpdUR007343; Wed, 11 Oct 2006 09:51:39 -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 k9BGpJbT022469;
	Wed, 11 Oct 2006 09:51:39 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Oct 2006 09:51:19 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Oct 2006 09:51:18 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202AF53C6@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [netlmm] Network-based mobility - NETLMM DT Solution Vs A
	solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0g
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>, <netlmm@ietf.org>
X-OriginalArrivalTime: 11 Oct 2006 16:51:19.0119 (UTC)
	FILETIME=[796345F0:01C6ED55]
DKIM-Signature: a=rsa-sha1; q=dns; l=987; t=1160585499; x=1161449499;
	c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[netlmm]=20Network-based=20mobility=20-=20NETLMM=20DT=20Solution
	=20Vs=20A=20solutionbased=20on=20MIP6=20;
	X=v=3Dcisco.com=3B=20h=3DoYWffwKZevjmQ7o9FxO8BkJJeh4=3D;
	b=Pe9PS1ywCV5X/hc5H3okMqMWuCOhEY1qiejNqyCAor/zvxTLUINorn2wXjhxkNU8TXL/3Owc
	5RB5pFFDmC/UIMSMenTXSrLNYE2Tr2DfhOupTjJxk3iAm3OUgpeof37k;
Authentication-Results: sj-dkim-5.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mip6@ietf.org
Subject: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution Vs
	A solutionbased on MIP6 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 don't see why running NetLMM signaling over IPv4 should be
precluded by design?  Having such flexibility is a valuable asset for a
standards based network-control mobility management protocol, IMHO.

Kent=20

-----Original Message-----
From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]=20
Sent: Friday, October 06, 2006 8:24 PM
To: netlmm@ietf.org
Cc: mip6@ietf.org
Subject: [netlmm] Network-based mobility - NETLMM DT Solution Vs A
solutionbased on MIP6=20


<snip>
What does the NETLMM DT Solution bring, by being totally different from
MIP6?
------------------------------------------------------------------------
------=20

1. The protocol can be evolved to using a reliable transport protocol
like SCTP at some point.=20
2. The protocol can run over IPv4 without changes.=20

While these seem like good goals, what is the practical need for the
above goals? For instance, is IPv4 signaling a necessity for a NETLMM
solution?=20

<snip>

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



From mip6-bounces@ietf.org Wed Oct 11 21:42:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXpZt-0007k7-Mf; Wed, 11 Oct 2006 21:41:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXpZs-0007fi-A6; Wed, 11 Oct 2006 21:41:40 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GXpZp-0005iF-JX; Wed, 11 Oct 2006 21:41:39 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9C1falS024607
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 11 Oct 2006 18:41:36 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9C1fYPX007927; Wed, 11 Oct 2006 18:41:35 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Oct 2006 18:41:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Oct 2006 18:41:30 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241D56@NAEX13.na.qualcomm.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202AF53C6@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [netlmm] Network-based mobility - NETLMM DT Solution Vs A
	solutionbased on MIP6 
thread-index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7A=
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Kent Leung \(kleung\)" <kleung@cisco.com>, <netlmm@ietf.org>
X-OriginalArrivalTime: 12 Oct 2006 01:41:34.0576 (UTC)
	FILETIME=[8CE0BF00:01C6ED9F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: mip6@ietf.org
Subject: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution Vs
	A solutionbased on MIP6 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 Kent,
If there is a need for IPv4 signaling usage, I agree with you. But, I'm
not so sure that there is a need for that, practically speaking. I think
many of those who want v4-signaled network-based mobility have gone a
non-standard PMIPv4 route already - is that not true?=20

If we have a real need for IPv4 signaling, then we could potentially say
that there is a need for two different standards in this space - one
that allows for running over IPv4 and another that allows maximum re-use
of already defined mobility options.=20

But, if the industry adopted the latter solution today for sake of
re-use, do we ever expect the former one being deployed? Or, would the
world simply do v6-in-v4 tunneling or the non-standard PMIPv4 when a
solution over v4 is needed?=20

I don't know the answer :)=20

Vidya

> -----Original Message-----
> From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
> Sent: Wednesday, October 11, 2006 9:51 AM
> To: Narayanan, Vidya; netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: RE: [netlmm] Network-based mobility - NETLMM DT=20
> Solution Vs A solutionbased on MIP6=20
>=20
> Hi Vidya.  I don't see why running NetLMM signaling over IPv4=20
> should be precluded by design?  Having such flexibility is a=20
> valuable asset for a standards based network-control mobility=20
> management protocol, IMHO.
>=20
> Kent=20
>=20
> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> Sent: Friday, October 06, 2006 8:24 PM
> To: netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: [netlmm] Network-based mobility - NETLMM DT Solution=20
> Vs A solutionbased on MIP6=20
>=20
>=20
> <snip>
> What does the NETLMM DT Solution bring, by being totally=20
> different from
> MIP6?
> --------------------------------------------------------------
> ----------
> ------=20
>=20
> 1. The protocol can be evolved to using a reliable transport protocol
> like SCTP at some point.=20
> 2. The protocol can run over IPv4 without changes.=20
>=20
> While these seem like good goals, what is the practical need for the
> above goals? For instance, is IPv4 signaling a necessity for a NETLMM
> solution?=20
>=20
> <snip>
>=20

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



From mip6-bounces@ietf.org Thu Oct 12 02:25:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXtzT-0002oN-AM; Thu, 12 Oct 2006 02:24:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXtzR-0002oC-9T
	for mip6@ietf.org; Thu, 12 Oct 2006 02:24:21 -0400
Received: from vms040pub.verizon.net ([206.46.252.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXtzM-000613-UN
	for mip6@ietf.org; Thu, 12 Oct 2006 02:24:21 -0400
Received: from vms071.mailsrvcs.net ([192.168.1.4])
	by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02
	(built Sep
	9 2005)) with ESMTPA id <0J70007BXF43FPX0@vms040.mailsrvcs.net> for
	mip6@ietf.org; Thu, 12 Oct 2006 01:24:03 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms071.mailsrvcs.net (Verizon Webmail) with HTTP; Thu,
	12 Oct 2006 01:24:03 -0500 (CDT)
Date: Thu, 12 Oct 2006 01:24:03 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6
X-Originating-IP: [129.55.200.20]
To: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
Message-id: <20799227.253201160634243563.JavaMail.root@vms071.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: e8a67952aa972b528dd04570d58ad8fe
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I'd like to suggest that the list of authors be kept as it is (i.e. I reject the proposal). I trust the authors put the names on the front page because their consensus was that each contributed substantially to the draft. Of course if WG consensus is that the proposal is to be accepted, then perhaps as many as five names (including the editor) could be placed on the front page. I'd be fine with the authors taking that route as well.

Best Regards,

Tim Enos
Rom 8:28

>From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
>Date: 2006/10/10 Tue PM 01:25:23 CDT
>To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
>Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6

>well, the guideline was put in when folks started having
>a long list of authors to show how many companies support  
>a particular proposal. and it is just a guideline. 
>exceptions are allowed. a person's name appearing on the
>front page depends on how much each person has contributed 
>to the draft.
>
>(I am one of the listed authors. I would be fine if my
>name is not listed on the front page for this particular
>draft, but in general I think it is not fair).
>
>Vijay
>
>> -----Original Message-----
>> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com] 
>> Sent: Tuesday, October 10, 2006 8:12 AM
>> To: mip6@ietf.org
>> Subject: [Mip6] issue 75: Authors on the front page should be 
>> less than 6
>> 
>> Issue text:
>> -----------
>> According to a guideline the number of authors on frontpage 
>> should be 5
>> or less.
>> Propose to keep an editor and list the co-authors in a different
>> section.
>> 
>> Conclusion:
>> -----------
>> 
>> We haven't discussed this in the DT, so I'd like to ask the WG to
>> express opinions on this. Please suggest on of the following options:
>> 
>> 1. reject: implies keeping the authors list as is.
>> 2. accept: implies keeping the editor on the front page and moving the
>> rest to an "Additional Authors" section. 
>> 
>> 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 Thu Oct 12 06:27:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXxme-0004DZ-V5; Thu, 12 Oct 2006 06:27:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXxmd-0004CQ-Mp
	for mip6@ietf.org; Thu, 12 Oct 2006 06:27:23 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXxmb-0001hJ-A1
	for mip6@ietf.org; Thu, 12 Oct 2006 06:27:23 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9CARIpx012322
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 12 Oct 2006 03:27:18 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9CARG8k001842; Thu, 12 Oct 2006 03:27:17 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 03:27:16 -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] issue 75: Authors on the front page should be less than 6
Date: Thu, 12 Oct 2006 03:27:08 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A335@NAEX14.na.qualcomm.com>
In-Reply-To: <20799227.253201160634243563.JavaMail.root@vms071.mailsrvcs.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] issue 75: Authors on the front page should be less than 6
thread-index: Acbtxw8Phkb2g8YlRRu5lt7w1SZhpQAIXlXQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Tim Enos" <timbeck04@verizon.net>,
	"Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 12 Oct 2006 10:27:16.0515 (UTC)
	FILETIME=[FD56AF30:01C6EDE8]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


 > I'd like to suggest that the list of authors be kept as it=20
 > is (i.e. I reject the proposal). I trust the authors put the=20
 > names on the front page because their consensus was that=20
 > each contributed substantially to the draft.=20

=3D> As I said in the conclusion we never discussed this issue.=20

   Of course if WG=20
 > consensus is that the proposal is to be accepted, then=20
 > perhaps as many as five names (including the editor) could=20
 > be placed on the front page. I'd be fine with the authors=20
 > taking that route as well.

=3D> I hope we don't do that. It's difficult to remove names selectively
and it could cause some people to be unhappy. I think we either keep all
or keep editor and list the rest later. Keeping 5 names and removing two
would suggest that those two didn't contribute as much. I'm
uncomfortable suggesting any two names to be removed from the list.=20

Hesham

 >=20
 > Best Regards,
 >=20
 > Tim Enos
 > Rom 8:28
 >=20
 > >From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
 > >Date: 2006/10/10 Tue PM 01:25:23 CDT
 > >To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
 > >Subject: RE: [Mip6] issue 75: Authors on the front page=20
 > should be less than 6
 >=20
 > >well, the guideline was put in when folks started having
 > >a long list of authors to show how many companies support =20
 > >a particular proposal. and it is just a guideline.=20
 > >exceptions are allowed. a person's name appearing on the
 > >front page depends on how much each person has contributed=20
 > >to the draft.
 > >
 > >(I am one of the listed authors. I would be fine if my
 > >name is not listed on the front page for this particular
 > >draft, but in general I think it is not fair).
 > >
 > >Vijay
 > >
 > >> -----Original Message-----
 > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
 > >> Sent: Tuesday, October 10, 2006 8:12 AM
 > >> To: mip6@ietf.org
 > >> Subject: [Mip6] issue 75: Authors on the front page should be=20
 > >> less than 6
 > >>=20
 > >> Issue text:
 > >> -----------
 > >> According to a guideline the number of authors on frontpage=20
 > >> should be 5
 > >> or less.
 > >> Propose to keep an editor and list the co-authors in a different
 > >> section.
 > >>=20
 > >> Conclusion:
 > >> -----------
 > >>=20
 > >> We haven't discussed this in the DT, so I'd like to ask the WG to
 > >> express opinions on this. Please suggest on of the=20
 > following options:
 > >>=20
 > >> 1. reject: implies keeping the authors list as is.
 > >> 2. accept: implies keeping the editor on the front page=20
 > and moving the
 > >> rest to an "Additional Authors" section.=20
 > >>=20
 > >> Hesham
 > >>=20
 > >> _______________________________________________
 > >> Mip6 mailing list
 > >> Mip6@ietf.org
 > >> https://www1.ietf.org/mailman/listinfo/mip6
 > >>=20
 > >
 > >_______________________________________________
 > >Mip6 mailing list
 > >Mip6@ietf.org
 > >https://www1.ietf.org/mailman/listinfo/mip6
 >=20
 >=20

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



From mip6-bounces@ietf.org Thu Oct 12 08:01:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXzFb-0001nt-2J; Thu, 12 Oct 2006 08:01:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXzFZ-0001nA-Ht
	for mip6@ietf.org; Thu, 12 Oct 2006 08:01:21 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXzFY-0003Zx-4v
	for mip6@ietf.org; Thu, 12 Oct 2006 08:01:21 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9CC1I19001784
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Thu, 12 Oct 2006 05:01:19 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9CC1G5r019649
	for <mip6@ietf.org>; Thu, 12 Oct 2006 05:01:18 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 05:01:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Oct 2006 05:01:17 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A33D@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issue 71: Avoid configuration at the HA about port forwarder
thread-index: Acbt9h/hXR7v1dLaTkOQKCbqzLWwzg==
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 12 Oct 2006 12:01:17.0140 (UTC)
	FILETIME=[1F69C140:01C6EDF6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Subject: [Mip6] Issue 71: Avoid configuration at the HA about port forwarder
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Issue description:
------------------

When a HA is placed within a private network, the HA must enforce UDP
encapsulation whether or not the MN/MR owns a public address.

The draft does not enable the HA to discover that situation; implicitly,
there
must be some configuration in the HA to let it know that it is behind a
NAT, so
that the HA sends a NAT detection option.

Configuration is a hassle for customers, and it is error prone:
- There is a way to automate the NAT discovery and remove the manual
configuration
- There is also a way to make it symmetrical, so that both ends reach a
same
conclusion without the need to introduce an additional NAT detection
option

If we decide to automate the discovery of the reverse NAT (=3D=3D port
forwarder)
then we might consider two alternatives:

option 1) Extends what is already done in 4.1 with the mapped address,
by
modifying the format of the mapped address to include all the needed
parameters
(IP and ports). This is what the doors proposal suggests, in order to
leave most
of the HA code and data structures unchanged.=20

option 2) add an option in the BU and BA where the sender exposes the IP
addresses and port as he sees them.=20

A discrepancy can be found on the receiver and interpreted as a presence
of a
NAT box on the way.

The drawback of the automation is that it can not detect a transparent
device
such as a load balancer placed in front of a cluster of HAs. This might
not be a
big issue if there is an optional config to force the UDP at all times,
which
should be there anyway to enable faster roaming.

Issue analysis
--------------
The issue suggests adding an automated mechanism to the draft to allow
the HA to discover that it is located in a private IPv4 domain (i.e.
behind the NAT). The issue correctly describes the current assumption in
the draft that the HA is configured with such knowledge. Regardless of
whether this issue is accepted or rejected, this assumption must be
clarified in the draft.=20

In principle, (i.e. focussing on the technical requirement in this
issue) I don't recall a strong objection. However, there were several
concerns raised about the scenario described in this issue and some
non-technical issues described below:

- Concerns against the scenario: Some concerns were raised about the
importance of the scenario described above. Generally speaking, it is
expected that HAs are manually configured with several parameters like
security paramaters and mapping them to allocated addresses. Therefore,
if configuration has to be done manually anyway, why is this particular
parameter a problem? One answer to this question is that network
conditions may change resulting in the HA being behind a NAT. In this
case other configuration parameters would not change, but this
particular parameter will need to be added.=20

Another concern about the reality of this scenario is related to the
difficulty of allocating a public address to the HA. Some people did not
agree that IPv4 addresses would be so scarce. However, such concern is
clearly difficult to verify one way or another as it is very specific to
the deployment scenario.=20

- IPR concerns: We were made aware of the existence of IPR that may well
cover potential solutions to this issue. This has raised concerns in the
DT about whether a solution to this issue should be handled in the base
spec or done later as an optional add-on.=20

Conclusion
----------

There was no clear concensus in the DT one way or another, altough more
people were in favour of rejecting this issue than those who were
willing to accept it.=20
Please provide input on this issue. The options we have are either :

1. Accept issue: This does not imply any particular solution, it simply
means that this issue is worth solving in the base spec.=20

2. Reject issue: This means that this issue is not worth solving in the
base spec. Of course it can be done later in a different doc but this is
outside the scope of this discussion.

Folks, please give some reasons for accepting or rejecting because I
have a feeling that the rationale might be helpful here in order to
break the tie.=20

Hesham




Conclusion
-----------

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



From mip6-bounces@ietf.org Thu Oct 12 08:09:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXzNm-0005Vp-P7; Thu, 12 Oct 2006 08:09:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXzNk-0005VW-Fw
	for mip6@ietf.org; Thu, 12 Oct 2006 08:09:48 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXzNj-00047S-3u
	for mip6@ietf.org; Thu, 12 Oct 2006 08:09:48 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9CC9h4O018540
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 12 Oct 2006 05:09:44 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9CC9IdV026559; Thu, 12 Oct 2006 05:09:43 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 05:09:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6
Date: Thu, 12 Oct 2006 05:09:22 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A33E@NAEX14.na.qualcomm.com>
In-Reply-To: <D4AE20519DDD544A98B3AE9235C8A4C221AAB9@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] issue 75: Authors on the front page should be less than 6
thread-index: Acbsfm82hfu8jy+GT3y3AmTrsdHBhwAGlgogAFdutIA=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 12 Oct 2006 12:09:21.0422 (UTC)
	FILETIME=[401152E0:01C6EDF7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay,=20

I won't give an opinion on this issue at all within the context of this
draft because I don't want to support either option. However, I do agree
with you that having a hard limit on numbers of authors is not a good
thing. I think it was a reactionary thing to unfortunate behaviour by
some people/companies in IETF. I think that authors should decide for
themselves whether they contributed enough or not. I've worked with
people that withdrew their names unilaterally and others that kept their
names as they saw fit. It shouldn't be a top-down decision IMO.=20

Hesham

PS: I hope no one takes this as supporting option 1 or 2 below.

 > well, the guideline was put in when folks started having
 > a long list of authors to show how many companies support =20
 > a particular proposal. and it is just a guideline.=20
 > exceptions are allowed. a person's name appearing on the
 > front page depends on how much each person has contributed=20
 > to the draft.
 >=20
 > (I am one of the listed authors. I would be fine if my
 > name is not listed on the front page for this particular
 > draft, but in general I think it is not fair).
 >=20
 > Vijay
 >=20
 > > -----Original Message-----
 > > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
 > > Sent: Tuesday, October 10, 2006 8:12 AM
 > > To: mip6@ietf.org
 > > Subject: [Mip6] issue 75: Authors on the front page should be=20
 > > less than 6
 > >=20
 > > Issue text:
 > > -----------
 > > According to a guideline the number of authors on frontpage=20
 > > should be 5
 > > or less.
 > > Propose to keep an editor and list the co-authors in a different
 > > section.
 > >=20
 > > Conclusion:
 > > -----------
 > >=20
 > > We haven't discussed this in the DT, so I'd like to ask the WG to
 > > express opinions on this. Please suggest on of the=20
 > following options:
 > >=20
 > > 1. reject: implies keeping the authors list as is.
 > > 2. accept: implies keeping the editor on the front page=20
 > and moving the
 > > rest to an "Additional Authors" section.=20
 > >=20
 > > Hesham
 > >=20
 > > _______________________________________________
 > > Mip6 mailing list
 > > Mip6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/mip6
 > >=20
 >=20

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



From mip6-bounces@ietf.org Thu Oct 12 09:06:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY0G1-0005Jn-Tf; Thu, 12 Oct 2006 09:05:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY0G0-0005Jd-Dm
	for mip6@ietf.org; Thu, 12 Oct 2006 09:05:52 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY0Fy-0002d3-TA
	for mip6@ietf.org; Thu, 12 Oct 2006 09:05:52 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9CD5ifU028944; Thu, 12 Oct 2006 16:05:47 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 16:05:15 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 08:05:12 -0500
Received: from [10.162.62.171] ([10.162.62.171]) by daebe101.NOE.Nokia.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 08:05:11 -0500
Message-ID: <452E3D84.6050302@nokia.com>
Date: Thu, 12 Oct 2006 06:05:08 -0700
From: "Charles E. Perkins" <charles.perkins@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "ext Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
References: <7EB20EA0938B4D42A2D82689365C9B7A24A33E@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A33E@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2006 13:05:11.0584 (UTC)
	FILETIME=[0CEB7A00:01C6EDFF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: mip6@ietf.org, Vijay Devarapalli <Vijay.Devarapalli@azairenet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hello folks,

I support Hesham's opinion entirely in this matter.  I would add, however,
one additional reason for limiting the number of authors.  Typically, during
the final phase of publication, the RFC editor has to await the approval
of every author listed on the front page.  Sometimes, that approval (which
is supposed to take 48 hours), takes months.  This is just the way it is.

If there are a lot of authors, it's almost guaranteed that the final phase
of approvals will take too long.

Nevertheless, I fully agree that all significant authorship should be
represented.  I know myself that when my name is on the front page
of a document, I work a lot harder to try to make it right.  I think that
for many people it is naturally that way.

Regards,
Charlie P.


ext Soliman, Hesham wrote:
> Vijay, 
>
> I won't give an opinion on this issue at all within the context of this
> draft because I don't want to support either option. However, I do agree
> with you that having a hard limit on numbers of authors is not a good
> thing. I think it was a reactionary thing to unfortunate behaviour by
> some people/companies in IETF. I think that authors should decide for
> themselves whether they contributed enough or not. I've worked with
> people that withdrew their names unilaterally and others that kept their
> names as they saw fit. It shouldn't be a top-down decision IMO. 
>
> Hesham
>
> PS: I hope no one takes this as supporting option 1 or 2 below.
>
>  > well, the guideline was put in when folks started having
>  > a long list of authors to show how many companies support  
>  > a particular proposal. and it is just a guideline. 
>  > exceptions are allowed. a person's name appearing on the
>  > front page depends on how much each person has contributed 
>  > to the draft.
>  > 
>  > (I am one of the listed authors. I would be fine if my
>  > name is not listed on the front page for this particular
>  > draft, but in general I think it is not fair).
>  > 
>  > Vijay
>  > 
>  > > -----Original Message-----
>  > > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com] 
>  > > Sent: Tuesday, October 10, 2006 8:12 AM
>  > > To: mip6@ietf.org
>  > > Subject: [Mip6] issue 75: Authors on the front page should be 
>  > > less than 6
>  > > 
>  > > Issue text:
>  > > -----------
>  > > According to a guideline the number of authors on frontpage 
>  > > should be 5
>  > > or less.
>  > > Propose to keep an editor and list the co-authors in a different
>  > > section.
>  > > 
>  > > Conclusion:
>  > > -----------
>  > > 
>  > > We haven't discussed this in the DT, so I'd like to ask the WG to
>  > > express opinions on this. Please suggest on of the 
>  > following options:
>  > > 
>  > > 1. reject: implies keeping the authors list as is.
>  > > 2. accept: implies keeping the editor on the front page 
>  > and moving the
>  > > rest to an "Additional Authors" section. 
>  > > 
>  > > 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
>   


-- 
Please address return e-mail to charles.perkins@nokia.com


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



From mip6-bounces@ietf.org Thu Oct 12 09:24:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY0Xg-0005bv-0r; Thu, 12 Oct 2006 09:24:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY0Xd-0005ax-VH
	for mip6@ietf.org; Thu, 12 Oct 2006 09:24:05 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GY0QJ-0003nh-Op
	for mip6@ietf.org; Thu, 12 Oct 2006 09:16:34 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-13.tower-128.messagelabs.com!1160658920!2835678!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.7]
Received: (qmail 29943 invoked from network); 12 Oct 2006 13:15:20 -0000
Received: from motgate7.mot.com (HELO motgate7.mot.com) (129.188.136.7)
	by server-13.tower-128.messagelabs.com with SMTP;
	12 Oct 2006 13:15:20 -0000
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate7.mot.com (8.12.11/Motorola) with ESMTP id k9CDAGcb006090;
	Thu, 12 Oct 2006 06:10:16 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k9CDAEIF009947;
	Thu, 12 Oct 2006 08:10:15 -0500 (CDT)
Message-ID: <452E3EB5.9020103@motorola.com>
Date: Thu, 12 Oct 2006 15:10:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] Issue 71: Avoid configuration at the HA about port
	forwarder
References: <7EB20EA0938B4D42A2D82689365C9B7A24A33D@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A33D@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Thanks for the description.

I think rejecting the issue is a good choice - don't treat about HA
behind NAT, keep the DS-MIPv6 spec simpler.

MIP deployments seem to favour MN-together-with-HA in same
administrative domain (no NAT between HA and MN), or otherwise HA with a
publicly routable address (no HA behind NAT, but MN behind NAT).

If we talk HA behind NAT then there are two possibilities, not just one:
either there is port forwarder on HA's NAT, or there is a RDV point on
the publicly routable Internet, that both  MN and HA contact to
detect their positions.  For a complete NAT solution one would have to
design both the detection with port forwarder and detection with a RDV
point.

(the need of having an IPv4 publicly routable address for HA is moot if
we separate the IPv6-only HA from the NAT that may be in front of it.
But this separation is impossible by current DS-MIPv6 design, which
forces HA to run both IPv4 and IPv6.)

Alex

Soliman, Hesham wrote:
> Issue description: ------------------
> 
> When a HA is placed within a private network, the HA must enforce UDP
>  encapsulation whether or not the MN/MR owns a public address.
> 
> The draft does not enable the HA to discover that situation; 
> implicitly, there must be some configuration in the HA to let it know
>  that it is behind a NAT, so that the HA sends a NAT detection 
> option.
> 
> 
> Configuration is a hassle for customers, and it is error prone: - 
> There is a way to automate the NAT discovery and remove the manual 
> configuration - There is also a way to make it symmetrical, so that 
> both ends reach a same conclusion without the need to introduce an 
> additional NAT detection option
> 
> If we decide to automate the discovery of the reverse NAT (== port 
> forwarder) then we might consider two alternatives:
> 
> option 1) Extends what is already done in 4.1 with the mapped 
> address, by modifying the format of the mapped address to include all
>  the needed parameters (IP and ports). This is what the doors 
> proposal suggests, in order to leave most of the HA code and data 
> structures unchanged.
> 
> option 2) add an option in the BU and BA where the sender exposes the
>  IP addresses and port as he sees them.
> 
> A discrepancy can be found on the receiver and interpreted as a 
> presence of a NAT box on the way.
> 
> The drawback of the automation is that it can not detect a 
> transparent device such as a load balancer placed in front of a 
> cluster of HAs. This might not be a big issue if there is an optional
>  config to force the UDP at all times, which should be there anyway 
> to enable faster roaming.
> 
> Issue analysis -------------- The issue suggests adding an automated 
> mechanism to the draft to allow the HA to discover that it is located
> in a private IPv4 domain (i.e. behind the NAT). The issue correctly
> describes the current assumption in the draft that the HA is
> configured with such knowledge. Regardless of whether this issue is
> accepted or rejected, this assumption must be clarified in the draft.
> 
> 
> 
> 
> In principle, (i.e. focussing on the technical requirement in this 
> issue) I don't recall a strong objection. However, there were several
>  concerns raised about the scenario described in this issue and some
>  non-technical issues described below:
> 
> - Concerns against the scenario: Some concerns were raised about the
>  importance of the scenario described above. Generally speaking, it
> is expected that HAs are manually configured with several parameters
>  like security paramaters and mapping them to allocated addresses. 
> Therefore, if configuration has to be done manually anyway, why is 
> this particular parameter a problem? One answer to this question is 
> that network conditions may change resulting in the HA being behind a
>  NAT. In this case other configuration parameters would not change, 
> but this particular parameter will need to be added.
> 
> Another concern about the reality of this scenario is related to the
>  difficulty of allocating a public address to the HA. Some people did
>  not agree that IPv4 addresses would be so scarce. However, such 
> concern is clearly difficult to verify one way or another as it is 
> very specific to the deployment scenario.
> 
> - IPR concerns: We were made aware of the existence of IPR that may 
> well cover potential solutions to this issue. This has raised 
> concerns in the DT about whether a solution to this issue should be 
> handled in the base spec or done later as an optional add-on.
> 
> Conclusion ----------
> 
> There was no clear concensus in the DT one way or another, altough 
> more people were in favour of rejecting this issue than those who 
> were willing to accept it. Please provide input on this issue. The 
> options we have are either :
> 
> 1. Accept issue: This does not imply any particular solution, it 
> simply means that this issue is worth solving in the base spec.
> 
> 2. Reject issue: This means that this issue is not worth solving in 
> the base spec. Of course it can be done later in a different doc but 
> this is outside the scope of this discussion.
> 
> Folks, please give some reasons for accepting or rejecting because I
>  have a feeling that the rationale might be helpful here in order to
>  break the tie.
> 
> Hesham
> 
> 
> 
> 
> Conclusion -----------
> 
> _______________________________________________ Mip6 mailing list 
> Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Thu Oct 12 12:05:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY32o-0008V5-PY; Thu, 12 Oct 2006 12:04:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY32n-0008R3-Bd
	for mip6@ietf.org; Thu, 12 Oct 2006 12:04:25 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY32l-0004br-SF
	for mip6@ietf.org; Thu, 12 Oct 2006 12:04:25 -0400
Message-ID: <014d01c6ee18$5a0c9e40$626015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Tim Enos" <timbeck04@verizon.net>,
	"Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>, <mip6@ietf.org>
References: <7EB20EA0938B4D42A2D82689365C9B7A24A335@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
Date: Thu, 12 Oct 2006 09:06:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
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

Yes, I agree. We faced this same issue in the NETLMM PS and REQ drafts. All 
the co-authors contributed a considerable amount of work to the documents, 
and it would have been really unfair to selectively remove names. Since I 
was acting as editor, I proposed that we list me as editor, and that we put 
the Contributors section up front with a notice saying that we were removing 
the other author's names because of the RFC Editor policy and that it had 
nothing to do with effort. Then, we listed their names in the author's 
section at the end, just as if they had been listed on the first page as 
authors. This raised a couple of eyebrows on the WG list but seemed 
acceptable in the end. I don't know if the position of the Contributors 
section and the text therein will survive the RFC editing process, however. 
:-)

Personally, I think if the IETF allows author's names on documents, then the 
RFC Editor really should allow all authors who contributed on the document. 
If the IETF weren't so wedded to its archaic ASCII text format, we could 
have documents with proper title pages where the number of authors wouldn't 
matter stylistically. Contributions by single individuals that make it 
through the IETF WG process and are published as RFCs are rare these days, 
most work is done by teams and the team members have a reasonable 
expectation that their names will appear prominently to acknowledge their 
contribution.

            jak


----- Original Message ----- 
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Tim Enos" <timbeck04@verizon.net>; "Vijay Devarapalli" 
<Vijay.Devarapalli@azairenet.com>; <mip6@ietf.org>
Sent: Thursday, October 12, 2006 3:27 AM
Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 
6



 > I'd like to suggest that the list of authors be kept as it
 > is (i.e. I reject the proposal). I trust the authors put the
 > names on the front page because their consensus was that
 > each contributed substantially to the draft.

=> As I said in the conclusion we never discussed this issue.

   Of course if WG
 > consensus is that the proposal is to be accepted, then
 > perhaps as many as five names (including the editor) could
 > be placed on the front page. I'd be fine with the authors
 > taking that route as well.

=> I hope we don't do that. It's difficult to remove names selectively
and it could cause some people to be unhappy. I think we either keep all
or keep editor and list the rest later. Keeping 5 names and removing two
would suggest that those two didn't contribute as much. I'm
uncomfortable suggesting any two names to be removed from the list.

Hesham

 >
 > Best Regards,
 >
 > Tim Enos
 > Rom 8:28
 >
 > >From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
 > >Date: 2006/10/10 Tue PM 01:25:23 CDT
 > >To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
 > >Subject: RE: [Mip6] issue 75: Authors on the front page
 > should be less than 6
 >
 > >well, the guideline was put in when folks started having
 > >a long list of authors to show how many companies support
 > >a particular proposal. and it is just a guideline.
 > >exceptions are allowed. a person's name appearing on the
 > >front page depends on how much each person has contributed
 > >to the draft.
 > >
 > >(I am one of the listed authors. I would be fine if my
 > >name is not listed on the front page for this particular
 > >draft, but in general I think it is not fair).
 > >
 > >Vijay
 > >
 > >> -----Original Message-----
 > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > >> Sent: Tuesday, October 10, 2006 8:12 AM
 > >> To: mip6@ietf.org
 > >> Subject: [Mip6] issue 75: Authors on the front page should be
 > >> less than 6
 > >>
 > >> Issue text:
 > >> -----------
 > >> According to a guideline the number of authors on frontpage
 > >> should be 5
 > >> or less.
 > >> Propose to keep an editor and list the co-authors in a different
 > >> section.
 > >>
 > >> Conclusion:
 > >> -----------
 > >>
 > >> We haven't discussed this in the DT, so I'd like to ask the WG to
 > >> express opinions on this. Please suggest on of the
 > following options:
 > >>
 > >> 1. reject: implies keeping the authors list as is.
 > >> 2. accept: implies keeping the editor on the front page
 > and moving the
 > >> rest to an "Additional Authors" section.
 > >>
 > >> 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 


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



From mip6-bounces@ietf.org Thu Oct 12 13:20:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4ET-0005QG-GM; Thu, 12 Oct 2006 13:20:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4ES-0005QB-7U
	for mip6@ietf.org; Thu, 12 Oct 2006 13:20:32 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4EQ-000053-OY
	for mip6@ietf.org; Thu, 12 Oct 2006 13:20:32 -0400
Message-ID: <005601c6ee22$fdd39b00$626015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
References: <7EB20EA0938B4D42A2D82689365C9B7A24A33D@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] Issue 71: Avoid configuration at the HA about port
	forwarder
Date: Thu, 12 Oct 2006 10:22:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I agree that the issue should be rejected. HAs are in managed networks, so I 
believe one can make the reasonable assumption that they can be configured 
to properly do NAT traversal.

            jak

----- Original Message ----- 
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
Sent: Thursday, October 12, 2006 5:01 AM
Subject: [Mip6] Issue 71: Avoid configuration at the HA about port forwarder



Issue description:
------------------

When a HA is placed within a private network, the HA must enforce UDP
encapsulation whether or not the MN/MR owns a public address.

The draft does not enable the HA to discover that situation; implicitly,
there
must be some configuration in the HA to let it know that it is behind a
NAT, so
that the HA sends a NAT detection option.

Configuration is a hassle for customers, and it is error prone:
- There is a way to automate the NAT discovery and remove the manual
configuration
- There is also a way to make it symmetrical, so that both ends reach a
same
conclusion without the need to introduce an additional NAT detection
option

If we decide to automate the discovery of the reverse NAT (== port
forwarder)
then we might consider two alternatives:

option 1) Extends what is already done in 4.1 with the mapped address,
by
modifying the format of the mapped address to include all the needed
parameters
(IP and ports). This is what the doors proposal suggests, in order to
leave most
of the HA code and data structures unchanged.

option 2) add an option in the BU and BA where the sender exposes the IP
addresses and port as he sees them.

A discrepancy can be found on the receiver and interpreted as a presence
of a
NAT box on the way.

The drawback of the automation is that it can not detect a transparent
device
such as a load balancer placed in front of a cluster of HAs. This might
not be a
big issue if there is an optional config to force the UDP at all times,
which
should be there anyway to enable faster roaming.

Issue analysis
--------------
The issue suggests adding an automated mechanism to the draft to allow
the HA to discover that it is located in a private IPv4 domain (i.e.
behind the NAT). The issue correctly describes the current assumption in
the draft that the HA is configured with such knowledge. Regardless of
whether this issue is accepted or rejected, this assumption must be
clarified in the draft.

In principle, (i.e. focussing on the technical requirement in this
issue) I don't recall a strong objection. However, there were several
concerns raised about the scenario described in this issue and some
non-technical issues described below:

- Concerns against the scenario: Some concerns were raised about the
importance of the scenario described above. Generally speaking, it is
expected that HAs are manually configured with several parameters like
security paramaters and mapping them to allocated addresses. Therefore,
if configuration has to be done manually anyway, why is this particular
parameter a problem? One answer to this question is that network
conditions may change resulting in the HA being behind a NAT. In this
case other configuration parameters would not change, but this
particular parameter will need to be added.

Another concern about the reality of this scenario is related to the
difficulty of allocating a public address to the HA. Some people did not
agree that IPv4 addresses would be so scarce. However, such concern is
clearly difficult to verify one way or another as it is very specific to
the deployment scenario.

- IPR concerns: We were made aware of the existence of IPR that may well
cover potential solutions to this issue. This has raised concerns in the
DT about whether a solution to this issue should be handled in the base
spec or done later as an optional add-on.

Conclusion
----------

There was no clear concensus in the DT one way or another, altough more
people were in favour of rejecting this issue than those who were
willing to accept it.
Please provide input on this issue. The options we have are either :

1. Accept issue: This does not imply any particular solution, it simply
means that this issue is worth solving in the base spec.

2. Reject issue: This means that this issue is not worth solving in the
base spec. Of course it can be done later in a different doc but this is
outside the scope of this discussion.

Folks, please give some reasons for accepting or rejecting because I
have a feeling that the rationale might be helpful here in order to
break the tie.

Hesham




Conclusion
-----------

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


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



From mip6-bounces@ietf.org Thu Oct 12 13:56:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4nT-0002Ze-VH; Thu, 12 Oct 2006 13:56:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4nR-0002ZX-VM
	for mip6@ietf.org; Thu, 12 Oct 2006 13:56:41 -0400
Received: from vms048pub.verizon.net ([206.46.252.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4nQ-0007sq-Ks
	for mip6@ietf.org; Thu, 12 Oct 2006 13:56:41 -0400
Received: from vms061.mailsrvcs.net ([192.168.1.2])
	by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02
	(built Sep
	9 2005)) with ESMTPA id <0J710032KB52NSH0@vms048.mailsrvcs.net> for
	mip6@ietf.org; Thu, 12 Oct 2006 12:55:51 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms061.mailsrvcs.net (Verizon Webmail) with HTTP; Thu,
	12 Oct 2006 12:55:50 -0500 (CDT)
Date: Thu, 12 Oct 2006 12:55:50 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6
X-Originating-IP: [129.55.200.20]
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	Tim Enos <timbeck04@verizon.net>,
	Vijay Devarapalli <Vijay.Devarapalli@azairenet.com>, mip6@ietf.org
Message-id: <28204141.2941611160675750827.JavaMail.root@vms061.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
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

>From: Tim Enos <timbeck04@verizon.net>
>Date: 2006/10/12 Thu AM 05:27:08 CDT
>To: "Soliman, Hesham" <hsoliman@qualcomm.com>, Tim Enos <timbeck04@verizon.net>, 
	Vijay Devarapalli <Vijay.Devarapalli@azairenet.com>, mip6@ietf.org
>Subject: Re: RE: [Mip6] issue 75: Authors on the front page should be less than 6

>
>>From: "Soliman, Hesham" <hsoliman@qualcomm.com>
>>Date: 2006/10/12 Thu AM 05:27:08 CDT
>>To: Tim Enos <timbeck04@verizon.net>, 
>	Vijay Devarapalli <Vijay.Devarapalli@azairenet.com>, mip6@ietf.org
>>Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6
>
>>
>> > I'd like to suggest that the list of authors be kept as it 
>> > is (i.e. I reject the proposal). I trust the authors put the 
>> > names on the front page because their consensus was that 
>> > each contributed substantially to the draft. 
>>
>>=> As I said in the conclusion we never discussed this issue.

Right. We can discuss it now.
 
>>
>>   Of course if WG 
>> > consensus is that the proposal is to be accepted, then 
>> > perhaps as many as five names (including the editor) could 
>> > be placed on the front page. I'd be fine with the authors 
>> > taking that route as well.
>>
>>=> I hope we don't do that. It's difficult to remove names selectively
>>and it could cause some people to be unhappy. I think we either keep all
>>or keep editor and list the rest later. Keeping 5 names and removing two
>>would suggest that those two didn't contribute as much.

I couldn't disagree more. Presuming exactly equal contributions by all authors, and WG requirement that there only be five names, the authors themselves could reach consensus regarding which names are moved.

 I'm
>>uncomfortable suggesting any two names to be removed from the list. 

So am I. If anyone is to decide such a thing, let it be the authors. All this said, my vote is that the names remain as they are, thus rejecting the proposal. Just my two cents.

>>
>>Hesham
>>
>> > 
>> > Best Regards,
>> > 
>> > Tim Enos
>> > Rom 8:28
>> > 
>> > >From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
>> > >Date: 2006/10/10 Tue PM 01:25:23 CDT
>> > >To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
>> > >Subject: RE: [Mip6] issue 75: Authors on the front page 
>> > should be less than 6
>> > 
>> > >well, the guideline was put in when folks started having
>> > >a long list of authors to show how many companies support  
>> > >a particular proposal. and it is just a guideline. 
>> > >exceptions are allowed. a person's name appearing on the
>> > >front page depends on how much each person has contributed 
>> > >to the draft.
>> > >
>> > >(I am one of the listed authors. I would be fine if my
>> > >name is not listed on the front page for this particular
>> > >draft, but in general I think it is not fair).
>> > >
>> > >Vijay
>> > >
>> > >> -----Original Message-----
>> > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com] 
>> > >> Sent: Tuesday, October 10, 2006 8:12 AM
>> > >> To: mip6@ietf.org
>> > >> Subject: [Mip6] issue 75: Authors on the front page should be 
>> > >> less than 6
>> > >> 
>> > >> Issue text:
>> > >> -----------
>> > >> According to a guideline the number of authors on frontpage 
>> > >> should be 5
>> > >> or less.
>> > >> Propose to keep an editor and list the co-authors in a different
>> > >> section.
>> > >> 
>> > >> Conclusion:
>> > >> -----------
>> > >> 
>> > >> We haven't discussed this in the DT, so I'd like to ask the WG to
>> > >> express opinions on this. Please suggest on of the 
>> > following options:
>> > >> 
>> > >> 1. reject: implies keeping the authors list as is.
>> > >> 2. accept: implies keeping the editor on the front page 
>> > and moving the
>> > >> rest to an "Additional Authors" section. 
>> > >> 
>> > >> 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 Thu Oct 12 14:00:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4rR-0004jI-7M; Thu, 12 Oct 2006 14:00:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4rQ-0004j8-1R
	for mip6@ietf.org; Thu, 12 Oct 2006 14:00:48 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4rO-0000Yg-Kw
	for mip6@ietf.org; Thu, 12 Oct 2006 14:00:48 -0400
Received: from wee.isi.edu (wee.isi.edu [128.9.168.112])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9CI0Lgq015546
	for <mip6@ietf.org>; Thu, 12 Oct 2006 11:00:21 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Thu, 12 Oct 2006 11:00:21 -0700
Message-Id: <1160676021.22612.46.camel@wee.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k9CI0Lgq015546
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Subject: [Mip6] Call for participation: Workshop on World-Sensor-Web
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our apologies if you have received multiple copies.

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

WSW'2006 Workshop Program

First Workshop on World-Sensor-Web: Mobile Device Centric Sensory =20
Networks and Applications
Held in conjunction with ACM SenSys 2006

October 31, 2006
Boulder, Colorado, USA

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

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

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

Online Registration:

http://www.regonline.com/Checkin.asp?EventId=3D97157

WORKSHOP CO-ORGANIZERS

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

TECHNICAL PROGRAM COMMITTEE

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


Provisional WORKSHOP SCHEDULE

8:30-9:00am Registration

9:00-9:05am Welcome

Position papers (20 min each followed by a 15 minutes discussion)


9:05-10:00am

Participatory sensing Jeff Burke (UCLA)

MetroSense Project: People-Centric Sensing at Scale Shane B. Eisenman =20
(Columbia University)

Short papers (15 min each, discussion in the end of the session)


10:00am-12:00pm

Relevance Metrics for Coverage Extension Using Community Collected =20
Cell-Phone Camera Imagery
Aman Kansal (Microsoft)


Challenges in Building a Portal for Sensors World-Wide
Suman Nath (Microsoft)

Indoor Positioning with a WLAN Access Point List on a Mobile Device
Marion Hermersdorf (Nokia Research Center)

Discussion

12:00-1:45pm
Lunch

1:45-2:45pm

Panel: "Grand challanges of mobile device-centric wireless sensor =20
networks"
Participants: tba
Short Papers (15 min each)


2:45-4:45pm

Sensing in Rich Bluetooth Environments
Jukka Perki=C3=B6 (HIIT / Nokia Research Center)

Hash-based Secure Sensor Network Programming Method without Public =20
Key Cryptography
Sokjoon Lee (Electronics and Telecommunications Research Institute, =20
Korea)

Energy-Efficient Single-Hop Clustering in Mobile Wireless Sensor =20
Networks
Chen Canfeng (Nokia Research Center)
(3:30-4:00pm
Coffee break)

4:45-6:00pm

Locality Helps Sleep Scheduling
Jukka Suomela (Helsinki University)

The Case for Mobile Devices in Environmental Observing systems
Sameer Tilak (UC San Diego)

SensorPlanet update: the first islands
Boda P=C3=A9ter P=C3=A1l (Nokia Research Center)

Discussions, Follow-up, Closing the Workshop




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



From mip6-bounces@ietf.org Thu Oct 12 14:04:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4uy-0006lA-5N; Thu, 12 Oct 2006 14:04:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4uw-0006jZ-UU
	for mip6@ietf.org; Thu, 12 Oct 2006 14:04:26 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4uv-0002nG-De
	for mip6@ietf.org; Thu, 12 Oct 2006 14:04:26 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9CI4JiL026957
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 12 Oct 2006 11:04:22 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9CI2Z2w015722; Thu, 12 Oct 2006 11:04:18 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 11:04:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Issue 71: Avoid configuration at the HA about portforwarder
Date: Thu, 12 Oct 2006 11:04:12 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A392@NAEX14.na.qualcomm.com>
In-Reply-To: <005601c6ee22$fdd39b00$626015ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Issue 71: Avoid configuration at the HA about
	portforwarder
thread-index: AcbuJMi2oZfG+w1MSmqoVGm31ag/IAAA15sw
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 12 Oct 2006 18:04:14.0929 (UTC)
	FILETIME=[D3FCA410:01C6EE28]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I second that. Although IPv4 addresses are a limited resource, it seems
that it is not unreasonable to require one public IPv4 address for the
operation of an HA that will service a large numbers of mobiles (all of
which can happily be using private IPv4 addresses). Manual port-mappings
can also be used for smaller deployments (e.g., home networks)

In any case, if and when that becomes a problem for someone, an
appropriate mechanism can be defined at that time.

George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Thursday, October 12, 2006 1:22 PM
> To: Soliman, Hesham; mip6@ietf.org
> Subject: Re: [Mip6] Issue 71: Avoid configuration at the HA about
> portforwarder
>=20
> I agree that the issue should be rejected. HAs are in managed
networks, so
> I
> believe one can make the reasonable assumption that they can be
configured
> to properly do NAT traversal.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Soliman, Hesham" <hsoliman@qualcomm.com>
> To: <mip6@ietf.org>
> Sent: Thursday, October 12, 2006 5:01 AM
> Subject: [Mip6] Issue 71: Avoid configuration at the HA about port
> forwarder
>=20
>=20
>=20
> Issue description:
> ------------------
>=20
> When a HA is placed within a private network, the HA must enforce UDP
> encapsulation whether or not the MN/MR owns a public address.
>=20
> The draft does not enable the HA to discover that situation;
implicitly,
> there
> must be some configuration in the HA to let it know that it is behind
a
> NAT, so
> that the HA sends a NAT detection option.
>=20
> Configuration is a hassle for customers, and it is error prone:
> - There is a way to automate the NAT discovery and remove the manual
> configuration
> - There is also a way to make it symmetrical, so that both ends reach
a
> same
> conclusion without the need to introduce an additional NAT detection
> option
>=20
> If we decide to automate the discovery of the reverse NAT (=3D=3D port
> forwarder)
> then we might consider two alternatives:
>=20
> option 1) Extends what is already done in 4.1 with the mapped address,
> by
> modifying the format of the mapped address to include all the needed
> parameters
> (IP and ports). This is what the doors proposal suggests, in order to
> leave most
> of the HA code and data structures unchanged.
>=20
> option 2) add an option in the BU and BA where the sender exposes the
IP
> addresses and port as he sees them.
>=20
> A discrepancy can be found on the receiver and interpreted as a
presence
> of a
> NAT box on the way.
>=20
> The drawback of the automation is that it can not detect a transparent
> device
> such as a load balancer placed in front of a cluster of HAs. This
might
> not be a
> big issue if there is an optional config to force the UDP at all
times,
> which
> should be there anyway to enable faster roaming.
>=20
> Issue analysis
> --------------
> The issue suggests adding an automated mechanism to the draft to allow
> the HA to discover that it is located in a private IPv4 domain (i.e.
> behind the NAT). The issue correctly describes the current assumption
in
> the draft that the HA is configured with such knowledge. Regardless of
> whether this issue is accepted or rejected, this assumption must be
> clarified in the draft.
>=20
> In principle, (i.e. focussing on the technical requirement in this
> issue) I don't recall a strong objection. However, there were several
> concerns raised about the scenario described in this issue and some
> non-technical issues described below:
>=20
> - Concerns against the scenario: Some concerns were raised about the
> importance of the scenario described above. Generally speaking, it is
> expected that HAs are manually configured with several parameters like
> security paramaters and mapping them to allocated addresses.
Therefore,
> if configuration has to be done manually anyway, why is this
particular
> parameter a problem? One answer to this question is that network
> conditions may change resulting in the HA being behind a NAT. In this
> case other configuration parameters would not change, but this
> particular parameter will need to be added.
>=20
> Another concern about the reality of this scenario is related to the
> difficulty of allocating a public address to the HA. Some people did
not
> agree that IPv4 addresses would be so scarce. However, such concern is
> clearly difficult to verify one way or another as it is very specific
to
> the deployment scenario.
>=20
> - IPR concerns: We were made aware of the existence of IPR that may
well
> cover potential solutions to this issue. This has raised concerns in
the
> DT about whether a solution to this issue should be handled in the
base
> spec or done later as an optional add-on.
>=20
> Conclusion
> ----------
>=20
> There was no clear concensus in the DT one way or another, altough
more
> people were in favour of rejecting this issue than those who were
> willing to accept it.
> Please provide input on this issue. The options we have are either :
>=20
> 1. Accept issue: This does not imply any particular solution, it
simply
> means that this issue is worth solving in the base spec.
>=20
> 2. Reject issue: This means that this issue is not worth solving in
the
> base spec. Of course it can be done later in a different doc but this
is
> outside the scope of this discussion.
>=20
> Folks, please give some reasons for accepting or rejecting because I
> have a feeling that the rationale might be helpful here in order to
> break the tie.
>=20
> Hesham
>=20
>=20
>=20
>=20
> Conclusion
> -----------
>=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

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



From mip6-bounces@ietf.org Thu Oct 12 14:05:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4wI-0007XG-OY; Thu, 12 Oct 2006 14:05:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4wH-0007Up-BW
	for mip6@ietf.org; Thu, 12 Oct 2006 14:05:49 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4wF-0003Ko-1w
	for mip6@ietf.org; Thu, 12 Oct 2006 14:05:49 -0400
Received: from [10.1.201.0] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Oct 2006 11:05:45 -0700
Message-ID: <452E82FD.4020500@azairenet.com>
Date: Thu, 12 Oct 2006 11:01:33 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A1E91F8@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A1E91F8@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2006 18:05:45.0661 (UTC)
	FILETIME=[0A113ED0:01C6EE29]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hesham,

sorry for the late reply.

I agree with relaxing the requirement in RFC 3775 to
include an Alt CoA option all the time.

but I don't understand how the checksum option helps.

lets take the following packet

IPv4 hdr (src=ipv4-CoA, dst=ipv4-HA)
IPv6 hdr (src=ipv4-mapped-ipv6-CoA, dst=ipv6-HA)
ESP hdr
Mobility Hdr
     Binding Update
     Checksum option

the checksum option protects the source in the IPv6
hdr. but if there is a NAT on the path, the HA needs
to take the IPv4 CoA in the source address of the
outer IPv4 header as the correct CoA. the NAT would
modify the IPv4 CoA anyway. how does the checksum
option protect the IPv4 Co?

let me know if I missing something obvious.

Soliman, Hesham wrote:

> We also need to add text in sections 4.3 and 4.4 (mobile node and HA
> operation) to require the MN to add this option and require the HA to
> verify it for BUs protected with ESP. 

I am definitely opposed to mandating this new option.

Vijay

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



From mip6-bounces@ietf.org Thu Oct 12 14:06:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4wn-0007ya-0c; Thu, 12 Oct 2006 14:06:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4wl-0007yV-O1
	for mip6@ietf.org; Thu, 12 Oct 2006 14:06:19 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4wk-0003YI-9z
	for mip6@ietf.org; Thu, 12 Oct 2006 14:06:19 -0400
Received: from wee.isi.edu (wee.isi.edu [128.9.168.112])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9CI5ojH017299
	for <mip6@ietf.org>; Thu, 12 Oct 2006 11:05:50 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Thu, 12 Oct 2006 11:05:50 -0700
Message-Id: <1160676350.22612.67.camel@wee.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k9CI5ojH017299
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Subject: [Mip6] Call for participation: Workshop on Distributed Smart Cameras
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our apologies if you have received multiple copies.

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

Workshop on Distributed Smart Cameras (DSC 2006) Program
Held in conjunction with ACM SenSys 2006

October 31, 2006
Boulder, CO, USA

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

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

Several groups are now working on distributed smart cameras, but =20
generally pursuing them in different research communities. This =20
meeting is the first event to bring together all the research groups =20
working on this problem

Online Registration:

http://www.regonline.com/Checkin.asp?EventId=3D97157

Workshop Co-Chairs

B. Rinner, Graz University of Technology, Austria
W. Wolf, Princeton University, USA
Program Committee

F. Berry, Univ. Clermont-Ferrand, France
S. Bhattacharyya, U. Maryland, USA (email)
M. Bove, MIT Media Lab, USA
H. Garn, ARCS, Austria
C. Guestrin, CMU, USA
R. Kleihorst, Philips Research, The Netherlands
X. Koutsoukos, Vanderbilt U., USA
C. Regazzoni, Univ. Genova, Italy
M. Srivastava, UCLA, USA
W. Strasser, Univ. T=C3=BCbingen, Germany

Program

08:30 - 09:00 Registration

09:00 - 09:15 Welcome

09:15 - 10:30 Session 1: Architectures

Paul Nadrag, Antoine Manzanera, Nicolas Burrus
Smart retina as a contour-based visual interface

Stephan Hengstler, Hamid Aghajan
A Smart Camera Mote Architecture for Distributed Intelligent =20
Surveillance

Terrance E. Boult, R.C. Johnson, Tracy Pietre, R. Woodworth, Tao Zhang
A Decade of Networked Intelligent Video Surveillance

Richard Kleihorst, Ben Schueler, Alexander Danilin, Marc Heijligers
SMART CAMERA MOTE WITH HIGH PERFORMANCE VISION SYSTEM

Erik Ljung, Erik Simmons, Alexander Danilin, Richard Kleihorst, Ben =20
Schueler
802.15.4 Powered Distributed Wireless Smart Cameras Network

Cintia B. Margi, Xiaoye Lu, Gefan Zhang, Roberto Manduchi, Katia =20
Obraczka
Meerkats: A Power-Aware, Self-Managing Wireless Camera Network for =20
Wide Area Monitoring

Pushkar Sambhoos, Ahmad Bilal, Richard Han, Tom Lookabaugh, Jane =20
Mulligan
WeebleVideo \u2013 Wide Angle Field-of-View Video Sensor Networks

10:30 - 11:00 Coffee Break

11:00 - 12:15 Session 2: Localization & Calibration

A.O. Ercan, A. El Gamal, L.J. Guibas
Camera Network Node Selection for Target Localization in the Presence =20
of Occlusions

Gurminder Singh and Mathias K=C3=B6lsch
Resource Aggregation in Smart Sensor Systems

Camillo J. Taylor, Babak Shirmohammadi
Self Localizing Smart Camera Networks and their Applications to 3D =20
Modeling

Dilip Sundarraj, Phillip B. Gibbons, Padmanabhan S. Pillai
Ensuring Spatio-Temporal Consistency in Distributed Networks of Smart =20
Cameras

John Jannotti, Jie Mao
Distributed Calibration of Smart Cameras

12:15 - 14:00 Lunch Break

14:00 - 15:30 Session 3: Services

Faisal Qureshi, Demetri Terzopoulos
Virtual Vision and Smart Camera Networks

Erik Simmons, Erik Ljung, Richard Kleihorst
Distributed Vision with Multiple Uncalibrated Smart Cameras

Johnny Park, Priya C. Bhat and Avinash C. Kak
A Look-up Table Based Approach for Solving the Camera Selection =20
Problem in Large Camera Networks

Mohammad Rahimi, Shaun Ahmadian, David Zats, Rafael Laufer, Deborah =20
Estrin
Magic of Numbers in Network of Wireless Image Sensors

Cheng-Yao Chen, Wayne Wolf
An Activity Model of Distributed Smart Cameras

Andreas Savvides, Eugenio Culurciello, Yiannis Aloimonos

Demo presentation

15:30 - 16:00 Coffee Break

16:00 - 17:30 Session 4: Applications


Thomas Haenselmann, Marcel Busse, Stephan Kopf, Thomas King, Wolfgang =20
Effelsberg
Image Fusion from uncalibrated Video Sensor Arrays

M. Quaritsch, M. Kreuzthaler, B. Rinner, B. Strobl
Decentralized Object Tracking in a Network of Embedded Smart Cameras

Arezou Keshavarz, Ali Maleki Tabar, Hamid Aghajan
Distributed Vision-Based Reasoning for Smart Home Care

Chen Wu, Hamid Aghajan
Collaborative Gesture Analysis in Multi-Camera Networks

Chung-Ching Chang, Hamid Aghajan
Collaborative Face Orientation Detection in Wireless Image Sensor =20
Networks

Vincent Jeanne, Francois-Xavier Jegaden, Richard Kleihorst, Alexander =20
Danilin, Ben Schueler
REAL-TIME FACE DETECTION ON A \u201cDUAL-SENSOR\u201d SMART CAMERA USING
SMOOTH =20
EDGES TECHNIQUE

Ikdong Kim, Jaechang Shim, Jason Schlessman, Wayne Wolf
Remote Wireless Face Recognition Employing ZigBee

Adam Williams, Dan Xie, Shichao Ou, Roderic Grupen, Allen Hanson, and =20
Edward Riseman

Distributed Smart Cameras for Aging in Place
17:30 - 18:15 Session 5: Panel




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



From mip6-bounces@ietf.org Thu Oct 12 14:14:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY54v-0006AB-EF; Thu, 12 Oct 2006 14:14:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY54u-0006A5-Kn
	for mip6@ietf.org; Thu, 12 Oct 2006 14:14:44 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY54r-00054T-2r
	for mip6@ietf.org; Thu, 12 Oct 2006 14:14:44 -0400
Received: from [10.1.201.0] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Oct 2006 11:14:40 -0700
Message-ID: <452E8518.1090404@azairenet.com>
Date: Thu, 12 Oct 2006 11:10:32 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] Issue 71: Avoid configuration at the HA about
	port	forwarder
References: <7EB20EA0938B4D42A2D82689365C9B7A24A33D@NAEX14.na.qualcomm.com>
	<005601c6ee22$fdd39b00$626015ac@dcml.docomolabsusa.com>
In-Reply-To: <005601c6ee22$fdd39b00$626015ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2006 18:14:40.0502 (UTC)
	FILETIME=[48DB8160:01C6EE2A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> I agree that the issue should be rejected. HAs are in managed networks, 
> so I believe one can make the reasonable assumption that they can be 
> configured to properly do NAT traversal.

+1

Vijay

> 
>            jak
> 
> ----- Original Message ----- From: "Soliman, Hesham" 
> <hsoliman@qualcomm.com>
> To: <mip6@ietf.org>
> Sent: Thursday, October 12, 2006 5:01 AM
> Subject: [Mip6] Issue 71: Avoid configuration at the HA about port 
> forwarder
> 
> 
> 
> Issue description:
> ------------------
> 
> When a HA is placed within a private network, the HA must enforce UDP
> encapsulation whether or not the MN/MR owns a public address.
> 
> The draft does not enable the HA to discover that situation; implicitly,
> there
> must be some configuration in the HA to let it know that it is behind a
> NAT, so
> that the HA sends a NAT detection option.
> 
> Configuration is a hassle for customers, and it is error prone:
> - There is a way to automate the NAT discovery and remove the manual
> configuration
> - There is also a way to make it symmetrical, so that both ends reach a
> same
> conclusion without the need to introduce an additional NAT detection
> option
> 
> If we decide to automate the discovery of the reverse NAT (== port
> forwarder)
> then we might consider two alternatives:
> 
> option 1) Extends what is already done in 4.1 with the mapped address,
> by
> modifying the format of the mapped address to include all the needed
> parameters
> (IP and ports). This is what the doors proposal suggests, in order to
> leave most
> of the HA code and data structures unchanged.
> 
> option 2) add an option in the BU and BA where the sender exposes the IP
> addresses and port as he sees them.
> 
> A discrepancy can be found on the receiver and interpreted as a presence
> of a
> NAT box on the way.
> 
> The drawback of the automation is that it can not detect a transparent
> device
> such as a load balancer placed in front of a cluster of HAs. This might
> not be a
> big issue if there is an optional config to force the UDP at all times,
> which
> should be there anyway to enable faster roaming.
> 
> Issue analysis
> --------------
> The issue suggests adding an automated mechanism to the draft to allow
> the HA to discover that it is located in a private IPv4 domain (i.e.
> behind the NAT). The issue correctly describes the current assumption in
> the draft that the HA is configured with such knowledge. Regardless of
> whether this issue is accepted or rejected, this assumption must be
> clarified in the draft.
> 
> In principle, (i.e. focussing on the technical requirement in this
> issue) I don't recall a strong objection. However, there were several
> concerns raised about the scenario described in this issue and some
> non-technical issues described below:
> 
> - Concerns against the scenario: Some concerns were raised about the
> importance of the scenario described above. Generally speaking, it is
> expected that HAs are manually configured with several parameters like
> security paramaters and mapping them to allocated addresses. Therefore,
> if configuration has to be done manually anyway, why is this particular
> parameter a problem? One answer to this question is that network
> conditions may change resulting in the HA being behind a NAT. In this
> case other configuration parameters would not change, but this
> particular parameter will need to be added.
> 
> Another concern about the reality of this scenario is related to the
> difficulty of allocating a public address to the HA. Some people did not
> agree that IPv4 addresses would be so scarce. However, such concern is
> clearly difficult to verify one way or another as it is very specific to
> the deployment scenario.
> 
> - IPR concerns: We were made aware of the existence of IPR that may well
> cover potential solutions to this issue. This has raised concerns in the
> DT about whether a solution to this issue should be handled in the base
> spec or done later as an optional add-on.
> 
> Conclusion
> ----------
> 
> There was no clear concensus in the DT one way or another, altough more
> people were in favour of rejecting this issue than those who were
> willing to accept it.
> Please provide input on this issue. The options we have are either :
> 
> 1. Accept issue: This does not imply any particular solution, it simply
> means that this issue is worth solving in the base spec.
> 
> 2. Reject issue: This means that this issue is not worth solving in the
> base spec. Of course it can be done later in a different doc but this is
> outside the scope of this discussion.
> 
> Folks, please give some reasons for accepting or rejecting because I
> have a feeling that the rationale might be helpful here in order to
> break the tie.
> 
> Hesham
> 
> 
> 
> 
> Conclusion
> -----------
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Thu Oct 12 14:19:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY59N-0007sF-K8; Thu, 12 Oct 2006 14:19:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY59M-0007s3-76; Thu, 12 Oct 2006 14:19:20 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GY59K-00062i-UG; Thu, 12 Oct 2006 14:19:20 -0400
Received: from [10.1.201.0] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Oct 2006 11:19:18 -0700
Message-ID: <452E862E.7010809@azairenet.com>
Date: Thu, 12 Oct 2006 11:15:10 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
References: <451B7EC0.70801@gmx.net>
In-Reply-To: <451B7EC0.70801@gmx.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2006 18:19:18.0229 (UTC)
	FILETIME=[EE654850:01C6EE2A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip6@ietf.org, dime@ietf.org
Subject: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

looks like nobody replied to this email. :)

Hannes Tschofenig wrote:
> Hi all,
> 
> in the DIME working group we are currently producing documents that 
> relate to the backend solution of the
> 
> * Integrated Scenario
>   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> 
> * Split Scenario
>   draft-ietf-mip6-bootstrapping-split-02
> 
> Now, the question came up whether we have to consider RFC 4285 
> ('Authentication Protocol for Mobile IPv6') for our work as well.

currently it is not clear if we are going to do any
further work on RFC 4285 in the MIP6 WG. so my
suggestion is to assume only the use of IKEv2 (with
and without EAP).

but it would be good to keep the solution flexible
so that it can be extended later for 4285 if required.

Vijay

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



From mip6-bounces@ietf.org Thu Oct 12 14:26:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY5GM-0004V9-B6; Thu, 12 Oct 2006 14:26:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY5GL-0004Tu-37
	for mip6@ietf.org; Thu, 12 Oct 2006 14:26:33 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY5GJ-0007ed-Ox
	for mip6@ietf.org; Thu, 12 Oct 2006 14:26:33 -0400
Received: from [10.1.201.0] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Oct 2006 11:26:30 -0700
Message-ID: <452E87DE.2000100@azairenet.com>
Date: Thu, 12 Oct 2006 11:22:22 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To: adnan khalid <adnan_kh79@hotmail.com>
Subject: Re: [Mip6] HoA failures in MIPv6
References: <BAY106-F2713F73F767FF47A03F46F9240@phx.gbl>
In-Reply-To: <BAY106-F2713F73F767FF47A03F46F9240@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2006 18:26:30.0954 (UTC)
	FILETIME=[F051E0A0:01C6EE2B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Adnan,

please take a look at the HA Reliability work.
http://www.ietf.org/internet-drafts/draft-ietf-mip6-hareliability-00.txt

adnan khalid wrote:
> Hello All,
>  I have a scenario which I am working on and I would be grateful if 
> someone can answer a question for me.
> If an MN exists in heterogeneous network environment and is using Home 
> Network HN1 with HoA1 to communicate with CN. Say, this HoA1 or HN1 as a 
> whole goes down due to HA going down,

you should have a backup HA that can take over when the
HA fails

> an  ISP going down, an edge router 
> or any network entity going down. 

these are not handled by the draft I mentioned above.
anyway, I don't think we need new protocol mechanisms to
handle this. this is common to any service that an ISP
might provide.

this can be done in many ways, though. you can have
redundancy for the HA, for any switch on the HA network,
for any routers in the ISP network. you can also have
the service at a different geographic location so that
it comes online when the entire site goes down. this
would mean you would geographically distribute the home
agents.

Vijay

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



From mip6-bounces@ietf.org Thu Oct 12 17:51:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY8RN-0004S3-Ds; Thu, 12 Oct 2006 17:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY8RM-0004Ru-9D; Thu, 12 Oct 2006 17:50:08 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GY8RK-0001LS-St; Thu, 12 Oct 2006 17:50:08 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9CLo19t024772
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 12 Oct 2006 14:50:03 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9CLnFFA003368; 
	Thu, 12 Oct 2006 14:50:00 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 14:49:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter
	MIP6Bootstrapping Work
Date: Thu, 12 Oct 2006 14:49:49 -0700
Message-ID: <C24CB51D5AA800449982D9BCB9032513241E0F@NAEX13.na.qualcomm.com>
In-Reply-To: <452E862E.7010809@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter
	MIP6Bootstrapping Work
thread-index: AcbuLMkGrcgnDUezQ66T/cTkvzBFHwAG345Q
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
X-OriginalArrivalTime: 12 Oct 2006 21:49:58.0128 (UTC)
	FILETIME=[5C5CCF00:01C6EE48]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: mip6@ietf.org, dime@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 missed this email earlier too :) =20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
> Sent: Thursday, October 12, 2006 11:15 AM
> To: Hannes Tschofenig
> Cc: mip6@ietf.org; dime@ietf.org
> Subject: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter=20
> MIP6Bootstrapping Work
>=20
> looks like nobody replied to this email. :)
>=20
> Hannes Tschofenig wrote:
> > Hi all,
> >=20
> > in the DIME working group we are currently producing documents that=20
> > relate to the backend solution of the
> >=20
> > * Integrated Scenario
> >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> >=20
> > * Split Scenario
> >   draft-ietf-mip6-bootstrapping-split-02
> >=20
> > Now, the question came up whether we have to consider RFC 4285=20
> > ('Authentication Protocol for Mobile IPv6') for our work as well.
>=20
> currently it is not clear if we are going to do any further=20
> work on RFC 4285 in the MIP6 WG. so my suggestion is to=20
> assume only the use of IKEv2 (with and without EAP).
>=20

Agree on the above with Vijay.=20

Vidya

> but it would be good to keep the solution flexible so that it=20
> can be extended later for 4285 if required.
>=20
> Vijay
>=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 Thu Oct 12 18:10:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY8l3-0007oX-KI; Thu, 12 Oct 2006 18:10:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY8l3-0007oP-0s
	for mip6@ietf.org; Thu, 12 Oct 2006 18:10:29 -0400
Received: from discorde.inria.fr ([192.93.2.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY8l1-00063r-IO
	for mip6@ietf.org; Thu, 12 Oct 2006 18:10:28 -0400
Received: from iseran-2.local (host81-129-176-112.range81-129.btcentralplus.com
	[81.129.176.112]) (authenticated bits=0)
	by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id k9CMAIto030264
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Fri, 13 Oct 2006 00:10:20 +0200
Date: Fri, 13 Oct 2006 00:10:18 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
To: mip6@ietf.org
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
Message-Id: <20061013001018.70289479.thierry.ernst@inria.fr>
In-Reply-To: <014d01c6ee18$5a0c9e40$626015ac@dcml.docomolabsusa.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A24A335@NAEX14.na.qualcomm.com>
	<014d01c6ee18$5a0c9e40$626015ac@dcml.docomolabsusa.com>
Organization: INRIA
X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; powerpc-apple-darwin7.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Miltered: at discorde with ID 452EBD4A.001 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Just wondering, why do we need author name in the first place ? Can't we
simply add the name of the WG as the author ? 

Thierry



On Thu, 12 Oct 2006 09:06:18 -0700
"James Kempf" <kempf@docomolabs-usa.com> wrote:

> Yes, I agree. We faced this same issue in the NETLMM PS and REQ drafts. All 
> the co-authors contributed a considerable amount of work to the documents, 
> and it would have been really unfair to selectively remove names. Since I 
> was acting as editor, I proposed that we list me as editor, and that we put 
> the Contributors section up front with a notice saying that we were removing 
> the other author's names because of the RFC Editor policy and that it had 
> nothing to do with effort. Then, we listed their names in the author's 
> section at the end, just as if they had been listed on the first page as 
> authors. This raised a couple of eyebrows on the WG list but seemed 
> acceptable in the end. I don't know if the position of the Contributors 
> section and the text therein will survive the RFC editing process, however. 
> :-)
> 
> Personally, I think if the IETF allows author's names on documents, then the 
> RFC Editor really should allow all authors who contributed on the document. 
> If the IETF weren't so wedded to its archaic ASCII text format, we could 
> have documents with proper title pages where the number of authors wouldn't 
> matter stylistically. Contributions by single individuals that make it 
> through the IETF WG process and are published as RFCs are rare these days, 
> most work is done by teams and the team members have a reasonable 
> expectation that their names will appear prominently to acknowledge their 
> contribution.
> 
>             jak
> 
> 
> ----- Original Message ----- 
> From: "Soliman, Hesham" <hsoliman@qualcomm.com>
> To: "Tim Enos" <timbeck04@verizon.net>; "Vijay Devarapalli" 
> <Vijay.Devarapalli@azairenet.com>; <mip6@ietf.org>
> Sent: Thursday, October 12, 2006 3:27 AM
> Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 
> 6
> 
> 
> 
>  > I'd like to suggest that the list of authors be kept as it
>  > is (i.e. I reject the proposal). I trust the authors put the
>  > names on the front page because their consensus was that
>  > each contributed substantially to the draft.
> 
> => As I said in the conclusion we never discussed this issue.
> 
>    Of course if WG
>  > consensus is that the proposal is to be accepted, then
>  > perhaps as many as five names (including the editor) could
>  > be placed on the front page. I'd be fine with the authors
>  > taking that route as well.
> 
> => I hope we don't do that. It's difficult to remove names selectively
> and it could cause some people to be unhappy. I think we either keep all
> or keep editor and list the rest later. Keeping 5 names and removing two
> would suggest that those two didn't contribute as much. I'm
> uncomfortable suggesting any two names to be removed from the list.
> 
> Hesham
> 
>  >
>  > Best Regards,
>  >
>  > Tim Enos
>  > Rom 8:28
>  >
>  > >From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
>  > >Date: 2006/10/10 Tue PM 01:25:23 CDT
>  > >To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
>  > >Subject: RE: [Mip6] issue 75: Authors on the front page
>  > should be less than 6
>  >
>  > >well, the guideline was put in when folks started having
>  > >a long list of authors to show how many companies support
>  > >a particular proposal. and it is just a guideline.
>  > >exceptions are allowed. a person's name appearing on the
>  > >front page depends on how much each person has contributed
>  > >to the draft.
>  > >
>  > >(I am one of the listed authors. I would be fine if my
>  > >name is not listed on the front page for this particular
>  > >draft, but in general I think it is not fair).
>  > >
>  > >Vijay
>  > >
>  > >> -----Original Message-----
>  > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>  > >> Sent: Tuesday, October 10, 2006 8:12 AM
>  > >> To: mip6@ietf.org
>  > >> Subject: [Mip6] issue 75: Authors on the front page should be
>  > >> less than 6
>  > >>
>  > >> Issue text:
>  > >> -----------
>  > >> According to a guideline the number of authors on frontpage
>  > >> should be 5
>  > >> or less.
>  > >> Propose to keep an editor and list the co-authors in a different
>  > >> section.
>  > >>
>  > >> Conclusion:
>  > >> -----------
>  > >>
>  > >> We haven't discussed this in the DT, so I'd like to ask the WG to
>  > >> express opinions on this. Please suggest on of the
>  > following options:
>  > >>
>  > >> 1. reject: implies keeping the authors list as is.
>  > >> 2. accept: implies keeping the editor on the front page
>  > and moving the
>  > >> rest to an "Additional Authors" section.
>  > >>
>  > >> Hesham
>  > >>

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



From mip6-bounces@ietf.org Thu Oct 12 18:36:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY9AI-0007JK-2d; Thu, 12 Oct 2006 18:36:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY9AG-0007J4-RQ
	for mip6@ietf.org; Thu, 12 Oct 2006 18:36:32 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY9AF-0001fm-3Q
	for mip6@ietf.org; Thu, 12 Oct 2006 18:36:32 -0400
Message-ID: <009201c6ee4f$2016f3c0$5a6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Thierry Ernst" <thierry.ernst@inria.fr>, <mip6@ietf.org>
References: <7EB20EA0938B4D42A2D82689365C9B7A24A335@NAEX14.na.qualcomm.com><014d01c6ee18$5a0c9e40$626015ac@dcml.docomolabsusa.com>
	<20061013001018.70289479.thierry.ernst@inria.fr>
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
Date: Thu, 12 Oct 2006 15:38:20 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
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

That idea has been floated in the past. The counterargument is, as Charlie 
says, people whose names are on the draft tend to work harder to get it 
done.

            jak

----- Original Message ----- 
From: "Thierry Ernst" <thierry.ernst@inria.fr>
To: <mip6@ietf.org>
Sent: Thursday, October 12, 2006 3:10 PM
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 
6


>
> Just wondering, why do we need author name in the first place ? Can't we
> simply add the name of the WG as the author ?
>
> Thierry
>
>
>
> On Thu, 12 Oct 2006 09:06:18 -0700
> "James Kempf" <kempf@docomolabs-usa.com> wrote:
>
>> Yes, I agree. We faced this same issue in the NETLMM PS and REQ drafts. 
>> All
>> the co-authors contributed a considerable amount of work to the 
>> documents,
>> and it would have been really unfair to selectively remove names. Since I
>> was acting as editor, I proposed that we list me as editor, and that we 
>> put
>> the Contributors section up front with a notice saying that we were 
>> removing
>> the other author's names because of the RFC Editor policy and that it had
>> nothing to do with effort. Then, we listed their names in the author's
>> section at the end, just as if they had been listed on the first page as
>> authors. This raised a couple of eyebrows on the WG list but seemed
>> acceptable in the end. I don't know if the position of the Contributors
>> section and the text therein will survive the RFC editing process, 
>> however.
>> :-)
>>
>> Personally, I think if the IETF allows author's names on documents, then 
>> the
>> RFC Editor really should allow all authors who contributed on the 
>> document.
>> If the IETF weren't so wedded to its archaic ASCII text format, we could
>> have documents with proper title pages where the number of authors 
>> wouldn't
>> matter stylistically. Contributions by single individuals that make it
>> through the IETF WG process and are published as RFCs are rare these 
>> days,
>> most work is done by teams and the team members have a reasonable
>> expectation that their names will appear prominently to acknowledge their
>> contribution.
>>
>>             jak
>>
>>
>> ----- Original Message ----- 
>> From: "Soliman, Hesham" <hsoliman@qualcomm.com>
>> To: "Tim Enos" <timbeck04@verizon.net>; "Vijay Devarapalli"
>> <Vijay.Devarapalli@azairenet.com>; <mip6@ietf.org>
>> Sent: Thursday, October 12, 2006 3:27 AM
>> Subject: RE: [Mip6] issue 75: Authors on the front page should be less 
>> than
>> 6
>>
>>
>>
>>  > I'd like to suggest that the list of authors be kept as it
>>  > is (i.e. I reject the proposal). I trust the authors put the
>>  > names on the front page because their consensus was that
>>  > each contributed substantially to the draft.
>>
>> => As I said in the conclusion we never discussed this issue.
>>
>>    Of course if WG
>>  > consensus is that the proposal is to be accepted, then
>>  > perhaps as many as five names (including the editor) could
>>  > be placed on the front page. I'd be fine with the authors
>>  > taking that route as well.
>>
>> => I hope we don't do that. It's difficult to remove names selectively
>> and it could cause some people to be unhappy. I think we either keep all
>> or keep editor and list the rest later. Keeping 5 names and removing two
>> would suggest that those two didn't contribute as much. I'm
>> uncomfortable suggesting any two names to be removed from the list.
>>
>> Hesham
>>
>>  >
>>  > Best Regards,
>>  >
>>  > Tim Enos
>>  > Rom 8:28
>>  >
>>  > >From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
>>  > >Date: 2006/10/10 Tue PM 01:25:23 CDT
>>  > >To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
>>  > >Subject: RE: [Mip6] issue 75: Authors on the front page
>>  > should be less than 6
>>  >
>>  > >well, the guideline was put in when folks started having
>>  > >a long list of authors to show how many companies support
>>  > >a particular proposal. and it is just a guideline.
>>  > >exceptions are allowed. a person's name appearing on the
>>  > >front page depends on how much each person has contributed
>>  > >to the draft.
>>  > >
>>  > >(I am one of the listed authors. I would be fine if my
>>  > >name is not listed on the front page for this particular
>>  > >draft, but in general I think it is not fair).
>>  > >
>>  > >Vijay
>>  > >
>>  > >> -----Original Message-----
>>  > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>>  > >> Sent: Tuesday, October 10, 2006 8:12 AM
>>  > >> To: mip6@ietf.org
>>  > >> Subject: [Mip6] issue 75: Authors on the front page should be
>>  > >> less than 6
>>  > >>
>>  > >> Issue text:
>>  > >> -----------
>>  > >> According to a guideline the number of authors on frontpage
>>  > >> should be 5
>>  > >> or less.
>>  > >> Propose to keep an editor and list the co-authors in a different
>>  > >> section.
>>  > >>
>>  > >> Conclusion:
>>  > >> -----------
>>  > >>
>>  > >> We haven't discussed this in the DT, so I'd like to ask the WG to
>>  > >> express opinions on this. Please suggest on of the
>>  > following options:
>>  > >>
>>  > >> 1. reject: implies keeping the authors list as is.
>>  > >> 2. accept: implies keeping the editor on the front page
>>  > and moving the
>>  > >> rest to an "Additional Authors" section.
>>  > >>
>>  > >> 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 Fri Oct 13 02:43:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYGkt-0001W3-J2; Fri, 13 Oct 2006 02:42:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYGks-0001UW-1o
	for mip6@ietf.org; Fri, 13 Oct 2006 02:42:50 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYGkq-0000GJ-Ms
	for mip6@ietf.org; Fri, 13 Oct 2006 02:42:50 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9D6gk1N025930
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 12 Oct 2006 23:42:47 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9D6gjkw025985; Thu, 12 Oct 2006 23:42:46 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Oct 2006 23:42:44 -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] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Thu, 12 Oct 2006 23:42:41 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A44E@NAEX14.na.qualcomm.com>
In-Reply-To: <452E82FD.4020500@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
thread-index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXA
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 13 Oct 2006 06:42:44.0862 (UTC)
	FILETIME=[CA0551E0:01C6EE92]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20
 > sorry for the late reply.
 >=20
 > I agree with relaxing the requirement in RFC 3775 to
 > include an Alt CoA option all the time.
 >=20
 > but I don't understand how the checksum option helps.
 >=20
 > lets take the following packet
 >=20
 > IPv4 hdr (src=3Dipv4-CoA, dst=3Dipv4-HA)
 > IPv6 hdr (src=3Dipv4-mapped-ipv6-CoA, dst=3Dipv6-HA)
 > ESP hdr
 > Mobility Hdr
 >      Binding Update
 >      Checksum option
 >=20
 > the checksum option protects the source in the IPv6
 > hdr. but if there is a NAT on the path, the HA needs
 > to take the IPv4 CoA in the source address of the
 > outer IPv4 header as the correct CoA.=20

=3D> No, it only takes that outer address as the dst address of its =
outer
header, the CoA is still the inner address. In other words, the packet
received at the HA (through the NAT) would look like this:=20

  IPv4 hdr (src=3Dipv4-natted, dst=3Dipv4-HA)
  IPv6 hdr (src=3Dipv4-CoA-mapped, dst=3Dipv6-HA)
  ESP hdr
  Mobility Hdr
       Binding Update
       Checksum option

Where ipv4-natted is the modified IPv4 CoA after the packet went through
the NAT.

the packets sent from the HA to the MN, after a NAT is detected would
look like this:

  IPv4 hdr (src=3Dipv4-HA, dst=3Dipv4-natted)
  IPv6 hdr (src=3D ipv6-HA, dst=3D ipv4-CoA-mapped)
  .....etc

Am I missing something ?

   the NAT would
 > modify the IPv4 CoA anyway. how does the checksum
 > option protect the IPv4 Co?

=3D> It only protects the inner address. Remember that the inner address
(the one in the v4-mapped address) is still required as the CoA in the
IPv6 packet. The problem with modifying the outer IPv4 address is of
course valid, but that's the problem with NATs and there is not much we
can do about that.

Hesham

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



From mip6-bounces@ietf.org Fri Oct 13 02:54:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYGwJ-0000F7-Ic; Fri, 13 Oct 2006 02:54:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYGwI-0000Ez-1B
	for mip6@ietf.org; Fri, 13 Oct 2006 02:54:38 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYGwG-0002NV-L6
	for mip6@ietf.org; Fri, 13 Oct 2006 02:54:38 -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] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Thu, 12 Oct 2006 23:51:59 -0700
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C221AF0F@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAABwFpA=
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

hi Hesham,

question is, if the NAT is modifying the outer address
IPv4 anyway, and the HA is going to use the outer IPv4
address as the CoA, what is the point in protecting the
source address on the inner IPv6 header using the new
checksum option?

why don't we instead in the security considerations say
that with RFC 3775 we had integrity protection for the
CoA, but with DS-MIPv6, since a NAT could modify the=20
outer source address, and the outer source address is=20
what is considered as the CoA, we don't get integrity
protection for the CoA.

Vijay

> -----Original Message-----
> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
> Sent: Thursday, October 12, 2006 11:43 PM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used=20
> when traversing IPv4 NAT
>=20
> =20
>  > sorry for the late reply.
>  >=20
>  > I agree with relaxing the requirement in RFC 3775 to
>  > include an Alt CoA option all the time.
>  >=20
>  > but I don't understand how the checksum option helps.
>  >=20
>  > lets take the following packet
>  >=20
>  > IPv4 hdr (src=3Dipv4-CoA, dst=3Dipv4-HA)
>  > IPv6 hdr (src=3Dipv4-mapped-ipv6-CoA, dst=3Dipv6-HA)
>  > ESP hdr
>  > Mobility Hdr
>  >      Binding Update
>  >      Checksum option
>  >=20
>  > the checksum option protects the source in the IPv6
>  > hdr. but if there is a NAT on the path, the HA needs
>  > to take the IPv4 CoA in the source address of the
>  > outer IPv4 header as the correct CoA.=20
>=20
> =3D> No, it only takes that outer address as the dst address of=20
> its outer
> header, the CoA is still the inner address. In other words, the packet
> received at the HA (through the NAT) would look like this:=20
>=20
>   IPv4 hdr (src=3Dipv4-natted, dst=3Dipv4-HA)
>   IPv6 hdr (src=3Dipv4-CoA-mapped, dst=3Dipv6-HA)
>   ESP hdr
>   Mobility Hdr
>        Binding Update
>        Checksum option
>=20
> Where ipv4-natted is the modified IPv4 CoA after the packet=20
> went through
> the NAT.
>=20
> the packets sent from the HA to the MN, after a NAT is detected would
> look like this:
>=20
>   IPv4 hdr (src=3Dipv4-HA, dst=3Dipv4-natted)
>   IPv6 hdr (src=3D ipv6-HA, dst=3D ipv4-CoA-mapped)
>   .....etc
>=20
> Am I missing something ?
>=20
>    the NAT would
>  > modify the IPv4 CoA anyway. how does the checksum
>  > option protect the IPv4 Co?
>=20
> =3D> It only protects the inner address. Remember that the inner =
address
> (the one in the v4-mapped address) is still required as the CoA in the
> IPv6 packet. The problem with modifying the outer IPv4 address is of
> course valid, but that's the problem with NATs and there is=20
> not much we
> can do about that.
>=20
> Hesham
>=20

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



From mip6-bounces@ietf.org Fri Oct 13 03:37:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYHav-0004Me-0T; Fri, 13 Oct 2006 03:36:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYHat-0004H8-PL
	for mip6@ietf.org; Fri, 13 Oct 2006 03:36:35 -0400
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYHas-0003Mn-Eh
	for mip6@ietf.org; Fri, 13 Oct 2006 03:36:35 -0400
Received: by ug-out-1314.google.com with SMTP id 72so380429ugd
	for <mip6@ietf.org>; Fri, 13 Oct 2006 00:36:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=FaF0OOdCMT5OIuFXVGcinmsfZXMUovGbJyvsp0FlM7QwQVzYdhV04ijFGkBXsiJuNwMaU1WXnt4Ro6j/nd/+5LYTHnDVsJry/fDkE8tui7wWypSsacXDoeByS/Baul+vsdF6zFL6O06e5cn5KfmgmlxoWevEdErLY24pL0To5GM=
Received: by 10.67.100.12 with SMTP id c12mr3953512ugm;
	Fri, 13 Oct 2006 00:36:33 -0700 (PDT)
Received: by 10.66.243.16 with HTTP; Fri, 13 Oct 2006 00:36:33 -0700 (PDT)
Message-ID: <eaa74a7e0610130036r75db5182ta4549ebcb4d26e97@mail.gmail.com>
Date: Fri, 13 Oct 2006 09:36:33 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
In-Reply-To: <452E862E.7010809@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <451B7EC0.70801@gmx.net> <452E862E.7010809@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: mip6@ietf.org, dime@ietf.org
Subject: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> > in the DIME working group we are currently producing documents that
> > relate to the backend solution of the
> >
> > * Integrated Scenario
> >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> >
> > * Split Scenario
> >   draft-ietf-mip6-bootstrapping-split-02
> >
> > Now, the question came up whether we have to consider RFC 4285
> > ('Authentication Protocol for Mobile IPv6') for our work as well.
>
> currently it is not clear if we are going to do any
> further work on RFC 4285 in the MIP6 WG. so my
> suggestion is to assume only the use of IKEv2 (with
> and without EAP).
>

Agree with Vijay, this is also the assumption for the AAA goals draft.

--Gerardo

> but it would be good to keep the solution flexible
> so that it can be extended later for 4285 if required.
>
> Vijay
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
>

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



From mip6-bounces@ietf.org Fri Oct 13 03:41:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYHfU-0007Ji-Ip; Fri, 13 Oct 2006 03:41:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYHfS-0007JY-TD
	for mip6@ietf.org; Fri, 13 Oct 2006 03:41:18 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYHfR-00041q-Fu
	for mip6@ietf.org; Fri, 13 Oct 2006 03:41:18 -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
	k9D7fFwx013578
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 13 Oct 2006 00:41:15 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9D7fECY009383; Fri, 13 Oct 2006 00:41:14 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Oct 2006 00:41:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Date: Fri, 13 Oct 2006 00:41:09 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A44F@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A44E@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
thread-index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAAJF84A=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 13 Oct 2006 07:41:13.0612 (UTC)
	FILETIME=[F56614C0:01C6EE9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
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

One more thing, I guess we both forgot the UDP hdr between the IPv4 and
IPv6 headers.=20

Hesham=20

 > -----Original Message-----
 > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
 > Sent: Friday, October 13, 2006 4:43 PM
 > To: Vijay Devarapalli
 > Cc: mip6@ietf.org
 > Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used=20
 > when traversingIPv4 NAT
 >=20
 > =20
 >  > sorry for the late reply.
 >  >=20
 >  > I agree with relaxing the requirement in RFC 3775 to
 >  > include an Alt CoA option all the time.
 >  >=20
 >  > but I don't understand how the checksum option helps.
 >  >=20
 >  > lets take the following packet
 >  >=20
 >  > IPv4 hdr (src=3Dipv4-CoA, dst=3Dipv4-HA)
 >  > IPv6 hdr (src=3Dipv4-mapped-ipv6-CoA, dst=3Dipv6-HA)
 >  > ESP hdr
 >  > Mobility Hdr
 >  >      Binding Update
 >  >      Checksum option
 >  >=20
 >  > the checksum option protects the source in the IPv6
 >  > hdr. but if there is a NAT on the path, the HA needs
 >  > to take the IPv4 CoA in the source address of the
 >  > outer IPv4 header as the correct CoA.=20
 >=20
 > =3D> No, it only takes that outer address as the dst address=20
 > of its outer
 > header, the CoA is still the inner address. In other words,=20
 > the packet
 > received at the HA (through the NAT) would look like this:=20
 >=20
 >   IPv4 hdr (src=3Dipv4-natted, dst=3Dipv4-HA)
 >   IPv6 hdr (src=3Dipv4-CoA-mapped, dst=3Dipv6-HA)
 >   ESP hdr
 >   Mobility Hdr
 >        Binding Update
 >        Checksum option
 >=20
 > Where ipv4-natted is the modified IPv4 CoA after the packet=20
 > went through
 > the NAT.
 >=20
 > the packets sent from the HA to the MN, after a NAT is detected would
 > look like this:
 >=20
 >   IPv4 hdr (src=3Dipv4-HA, dst=3Dipv4-natted)
 >   IPv6 hdr (src=3D ipv6-HA, dst=3D ipv4-CoA-mapped)
 >   .....etc
 >=20
 > Am I missing something ?
 >=20
 >    the NAT would
 >  > modify the IPv4 CoA anyway. how does the checksum
 >  > option protect the IPv4 Co?
 >=20
 > =3D> It only protects the inner address. Remember that the=20
 > inner address
 > (the one in the v4-mapped address) is still required as the=20
 > CoA in the
 > IPv6 packet. The problem with modifying the outer IPv4 address is of
 > course valid, but that's the problem with NATs and there is=20
 > not much we
 > can do about that.
 >=20
 > Hesham
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

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



From mip6-bounces@ietf.org Fri Oct 13 03:48:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYHmH-00039l-IK; Fri, 13 Oct 2006 03:48:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYHmG-000386-Mp
	for mip6@ietf.org; Fri, 13 Oct 2006 03:48:20 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYHmF-0004u6-9N
	for mip6@ietf.org; Fri, 13 Oct 2006 03:48:20 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9D7mHOv014271
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 13 Oct 2006 00:48:17 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.na.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9D7mGH0028827; 
	Fri, 13 Oct 2006 00:48:16 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Oct 2006 00:48:15 -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] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Fri, 13 Oct 2006 00:48:07 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A450@NAEX14.na.qualcomm.com>
In-Reply-To: <D4AE20519DDD544A98B3AE9235C8A4C221AF0F@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
thread-index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAABwFpAAAed4QA==
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>
X-OriginalArrivalTime: 13 Oct 2006 07:48:15.0292 (UTC)
	FILETIME=[F0BD57C0:01C6EE9B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
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



 > question is, if the NAT is modifying the outer address
 > IPv4 anyway, and the HA is going to use the outer IPv4
 > address as the CoA, what is the point in protecting the
 > source address on the inner IPv6 header using the new
 > checksum option?

=3D> Well, we're type to keep the integrity of the BU equivalent to =
3775.
I know what you mean, evidently, the NAT will be the weakest link and it
will push the entire security level down. I agree.=20

 >=20
 > why don't we instead in the security considerations say
 > that with RFC 3775 we had integrity protection for the
 > CoA, but with DS-MIPv6, since a NAT could modify the=20
 > outer source address, and the outer source address is=20
 > what is considered as the CoA, we don't get integrity
 > protection for the CoA.

=3D> That's possible of course, but at lease with the checksum option we
know that one address is correct for sure (i.e. CoA in the v6 header). I
don't know if that reduces the number of potential attacks overall, my
aim was to keep it equivalent to 3775 so we don't have to worry about
re-analysing the threats. But may be it's a good exercise to do that.
Can you think of any attacks that would be reduced if the attacker could
not successfully modify the CoA in the v6 packet? This is a question for
anyone BTW. I'll think about it a bit more to see if it makes a
difference.=20

Hesham

 >=20
 > Vijay
 >=20
 > > -----Original Message-----
 > > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
 > > Sent: Thursday, October 12, 2006 11:43 PM
 > > To: Vijay Devarapalli
 > > Cc: mip6@ietf.org
 > > Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used=20
 > > when traversing IPv4 NAT
 > >=20
 > > =20
 > >  > sorry for the late reply.
 > >  >=20
 > >  > I agree with relaxing the requirement in RFC 3775 to
 > >  > include an Alt CoA option all the time.
 > >  >=20
 > >  > but I don't understand how the checksum option helps.
 > >  >=20
 > >  > lets take the following packet
 > >  >=20
 > >  > IPv4 hdr (src=3Dipv4-CoA, dst=3Dipv4-HA)
 > >  > IPv6 hdr (src=3Dipv4-mapped-ipv6-CoA, dst=3Dipv6-HA)
 > >  > ESP hdr
 > >  > Mobility Hdr
 > >  >      Binding Update
 > >  >      Checksum option
 > >  >=20
 > >  > the checksum option protects the source in the IPv6
 > >  > hdr. but if there is a NAT on the path, the HA needs
 > >  > to take the IPv4 CoA in the source address of the
 > >  > outer IPv4 header as the correct CoA.=20
 > >=20
 > > =3D> No, it only takes that outer address as the dst address of=20
 > > its outer
 > > header, the CoA is still the inner address. In other=20
 > words, the packet
 > > received at the HA (through the NAT) would look like this:=20
 > >=20
 > >   IPv4 hdr (src=3Dipv4-natted, dst=3Dipv4-HA)
 > >   IPv6 hdr (src=3Dipv4-CoA-mapped, dst=3Dipv6-HA)
 > >   ESP hdr
 > >   Mobility Hdr
 > >        Binding Update
 > >        Checksum option
 > >=20
 > > Where ipv4-natted is the modified IPv4 CoA after the packet=20
 > > went through
 > > the NAT.
 > >=20
 > > the packets sent from the HA to the MN, after a NAT is=20
 > detected would
 > > look like this:
 > >=20
 > >   IPv4 hdr (src=3Dipv4-HA, dst=3Dipv4-natted)
 > >   IPv6 hdr (src=3D ipv6-HA, dst=3D ipv4-CoA-mapped)
 > >   .....etc
 > >=20
 > > Am I missing something ?
 > >=20
 > >    the NAT would
 > >  > modify the IPv4 CoA anyway. how does the checksum
 > >  > option protect the IPv4 Co?
 > >=20
 > > =3D> It only protects the inner address. Remember that the=20
 > inner address
 > > (the one in the v4-mapped address) is still required as=20
 > the CoA in the
 > > IPv6 packet. The problem with modifying the outer IPv4=20
 > address is of
 > > course valid, but that's the problem with NATs and there is=20
 > > not much we
 > > can do about that.
 > >=20
 > > Hesham
 > >=20
 >=20

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



From mip6-bounces@ietf.org Fri Oct 13 10:29:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYO2e-0000JJ-M5; Fri, 13 Oct 2006 10:29:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYNyB-00066f-Ot
	for mip6@ietf.org; Fri, 13 Oct 2006 10:25:03 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYNtd-00015t-4f
	for mip6@ietf.org; Fri, 13 Oct 2006 10:20:25 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9DEKEVt013743; Fri, 13 Oct 2006 17:20:20 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Oct 2006 17:19:13 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Oct 2006 17:19:13 +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] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Date: Fri, 13 Oct 2006 17:19:12 +0300
Message-ID: <58357EDC7884E24BAD684C1B2D91F96D041D2C2E@trebe101.NOE.Nokia.com>
In-Reply-To: <452E82FD.4020500@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Thread-Index: AcbuKxjhkdcYVwTdTtusR4nPSsILogApd0yg
From: <Markku.Ala-Vannesluoma@nokia.com>
To: <hsoliman@qualcomm.com>
X-OriginalArrivalTime: 13 Oct 2006 14:19:13.0382 (UTC)
	FILETIME=[8ED9D060:01C6EED2]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Also, sorry for commenting this so late.

The original issue was to make sure that the HA sends the BA back
to the right IPv4 address. The way I see this is that the (DS)MIPv6
protocol still creates the BA with the destination set to the
ipv4-mapped-ipv6-CoA, whether from IPv6 src address or altCoa option.

Isn't this whole issue more of an implementation detail of how the HA
does the UDP+IPv4 tunneling internally (=3Dnot an issue at all)?

Thoughts?

Markku

>-----Original Message-----
>From: ext Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
>Sent: 12 October, 2006 21:02
>To: Soliman, Hesham
>Cc: mip6@ietf.org
>Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used=20
>when traversingIPv4 NAT
>
>Hesham,
>
>sorry for the late reply.
>
>I agree with relaxing the requirement in RFC 3775 to include=20
>an Alt CoA option all the time.
>
>but I don't understand how the checksum option helps.
>
>lets take the following packet
>
>IPv4 hdr (src=3Dipv4-CoA, dst=3Dipv4-HA)
>IPv6 hdr (src=3Dipv4-mapped-ipv6-CoA, dst=3Dipv6-HA) ESP hdr Mobility =
Hdr
>     Binding Update
>     Checksum option
>
>the checksum option protects the source in the IPv6 hdr. but=20
>if there is a NAT on the path, the HA needs to take the IPv4=20
>CoA in the source address of the outer IPv4 header as the=20
>correct CoA. the NAT would modify the IPv4 CoA anyway. how=20
>does the checksum option protect the IPv4 Co?
>
>let me know if I missing something obvious.
>
>Soliman, Hesham wrote:
>
>> We also need to add text in sections 4.3 and 4.4 (mobile node and HA
>> operation) to require the MN to add this option and require=20
>the HA to=20
>> verify it for BUs protected with ESP.
>
>I am definitely opposed to mandating this new option.
>
>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 Fri Oct 13 12:08:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYPa3-0005s3-GM; Fri, 13 Oct 2006 12:08:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYPa2-0005jm-9v
	for mip6@ietf.org; Fri, 13 Oct 2006 12:08:14 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYPZy-0002Wq-Sm
	for mip6@ietf.org; Fri, 13 Oct 2006 12:08:14 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9DG89L4017245
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 13 Oct 2006 09:08:09 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9DG83hF013181; Fri, 13 Oct 2006 09:08:07 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Oct 2006 09:08:04 -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] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Date: Fri, 13 Oct 2006 09:07:55 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A49F@NAEX14.na.qualcomm.com>
In-Reply-To: <58357EDC7884E24BAD684C1B2D91F96D041D2C2E@trebe101.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
thread-index: AcbuKxjhkdcYVwTdTtusR4nPSsILogApd0ygAAQds9A=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <Markku.Ala-Vannesluoma@nokia.com>
X-OriginalArrivalTime: 13 Oct 2006 16:08:04.0131 (UTC)
	FILETIME=[C37B0730:01C6EEE1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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



 > Also, sorry for commenting this so late.
 >=20
 > The original issue was to make sure that the HA sends the BA back
 > to the right IPv4 address.=20

=3D> No that's not the issue. The issue is really about the consequence =
of
removing the alt-coa. We all agree it shouldn't be used in this case,
now the question is whether we need to maintain the integrity of the BU
when we don't use the alt-cao. Hence the checksum suggestion.

   The way I see this is that the (DS)MIPv6
 > protocol still creates the BA with the destination set to the
 > ipv4-mapped-ipv6-CoA, whether from IPv6 src address or altCoa option.

=3D> Yes. But this is not what we're discussing.

 >=20
 > Isn't this whole issue more of an implementation detail of how the HA
 > does the UDP+IPv4 tunneling internally (=3Dnot an issue at all)?

=3D> No. See above.

Hesham

 >=20
 > Thoughts?
 >=20
 > Markku
 >=20
 > >-----Original Message-----
 > >From: ext Vijay Devarapalli=20
 > [mailto:vijay.devarapalli@azairenet.com]=20
 > >Sent: 12 October, 2006 21:02
 > >To: Soliman, Hesham
 > >Cc: mip6@ietf.org
 > >Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used=20
 > >when traversingIPv4 NAT
 > >
 > >Hesham,
 > >
 > >sorry for the late reply.
 > >
 > >I agree with relaxing the requirement in RFC 3775 to include=20
 > >an Alt CoA option all the time.
 > >
 > >but I don't understand how the checksum option helps.
 > >
 > >lets take the following packet
 > >
 > >IPv4 hdr (src=3Dipv4-CoA, dst=3Dipv4-HA)
 > >IPv6 hdr (src=3Dipv4-mapped-ipv6-CoA, dst=3Dipv6-HA) ESP hdr=20
 > Mobility Hdr
 > >     Binding Update
 > >     Checksum option
 > >
 > >the checksum option protects the source in the IPv6 hdr. but=20
 > >if there is a NAT on the path, the HA needs to take the IPv4=20
 > >CoA in the source address of the outer IPv4 header as the=20
 > >correct CoA. the NAT would modify the IPv4 CoA anyway. how=20
 > >does the checksum option protect the IPv4 Co?
 > >
 > >let me know if I missing something obvious.
 > >
 > >Soliman, Hesham wrote:
 > >
 > >> We also need to add text in sections 4.3 and 4.4 (mobile=20
 > node and HA
 > >> operation) to require the MN to add this option and require=20
 > >the HA to=20
 > >> verify it for BUs protected with ESP.
 > >
 > >I am definitely opposed to mandating this new option.
 > >
 > >Vijay
 > >
 > >_______________________________________________
 > >Mip6 mailing list
 > >Mip6@ietf.org
 > >https://www1.ietf.org/mailman/listinfo/mip6
 > >
 >=20

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



From mip6-bounces@ietf.org Fri Oct 13 13:48:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYR8n-0007vW-Rt; Fri, 13 Oct 2006 13:48:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYR8m-0007vQ-6n
	for mip6@ietf.org; Fri, 13 Oct 2006 13:48:12 -0400
Received: from prufrock.cs.umd.edu ([128.8.128.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYR8k-0005Bl-Uj
	for mip6@ietf.org; Fri, 13 Oct 2006 13:48:12 -0400
Received: (from sharno@localhost)
	by prufrock.cs.umd.edu (8.12.10/8.12.5) id k9DHmAIH022719
	for mip6@ietf.org; Fri, 13 Oct 2006 13:48:10 -0400 (EDT)
Date: Fri, 13 Oct 2006 13:48:10 -0400 (EDT)
From: Tamer Elsharnouby <sharno@cs.umd.edu>
Message-Id: <200610131748.k9DHmAIH022719@prufrock.cs.umd.edu>
To: mip6@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: [Mip6] IEEE NetCri 2007: Call for papers
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

**     Apologies if you receive multiple copies of this call for papers      **
===============================================================================

                                Call for Papers
                                   NetCri 07

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

                       http://www.cs.umd.edu/~sharno/NetCri

                            In Conjunction with 

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

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


Paper Submission

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

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



Important Dates

   Submission deadline:         November 30, 2006
   Notification of acceptance:  January 5, 2007
   Camera ready version:        January 26, 2007


Workshop Organizing Committee

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

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

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



From mip6-bounces@ietf.org Fri Oct 13 14:21:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYRei-0004vH-VR; Fri, 13 Oct 2006 14:21:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYReh-0004ql-46
	for mip6@ietf.org; Fri, 13 Oct 2006 14:21:11 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYRee-0001Xf-Gy
	for mip6@ietf.org; Fri, 13 Oct 2006 14:21:11 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9DIL3P4005167
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 13 Oct 2006 11:21:05 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9DIKqZK010489; Fri, 13 Oct 2006 11:21:00 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Oct 2006 11:20:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] issue 75: Authors on the front page should be less than 6
Date: Fri, 13 Oct 2006 11:20:57 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A4F2@NAEX14.na.qualcomm.com>
In-Reply-To: <009201c6ee4f$2016f3c0$5a6015ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] issue 75: Authors on the front page should be less than 6
thread-index: AcbuULnAXmYT+vDzTeGmTLh5IXfVaAAoT0Mg
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Thierry Ernst" <thierry.ernst@inria.fr>, <mip6@ietf.org>
X-OriginalArrivalTime: 13 Oct 2006 18:20:58.0858 (UTC)
	FILETIME=[54C9CCA0:01C6EEF4]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bc6181926481d86059e678c9f7cb8b34
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I think it is a shame that the bad behavior of the few affects all of us
in this way. It reminds me of the ban on water bottles in the airplanes
because someone built a liquid bomb. Although I am not trying to equate
the level of seriousness of the two issues, even the airplane industry
managed to get a lift on that ban after a while :-)

I think that people who contributed design ideas and actual text to a
specification should make up the authors list. People who contributed
only in smaller way should be acknowledged in the acks section. People
who contributed nothing should not be in the document.

In general I would discourage the idea of large numbers of authors since
in practice it is unlikely many people actively work on any one
document. This is hard to do though, when the WGs set-up design teams to
get something done.=20

The WG chairs should have the power to request the authors list to be
cut down, if they thing it is unreasonably large or if they thing that
some people are trying to abuse the system. People that find themselves
in a design team and then for whatever reason never got to do any work
should feel obliged to get themselves off the list.

In general I like to think that people do the right thing most of the
times and that any system can be abused. For example, if you mandate
that only one person can be in the front page we might have people
trying to become editors for all the wrong reasons.

George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Thursday, October 12, 2006 6:38 PM
> To: Thierry Ernst; mip6@ietf.org
> Subject: Re: [Mip6] issue 75: Authors on the front page should be less
> than 6
>=20
> That idea has been floated in the past. The counterargument is, as
Charlie
> says, people whose names are on the draft tend to work harder to get
it
> done.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Thierry Ernst" <thierry.ernst@inria.fr>
> To: <mip6@ietf.org>
> Sent: Thursday, October 12, 2006 3:10 PM
> Subject: Re: [Mip6] issue 75: Authors on the front page should be less
> than
> 6
>=20
>=20
> >
> > Just wondering, why do we need author name in the first place ?
Can't we
> > simply add the name of the WG as the author ?
> >
> > Thierry
> >
> >
> >
> > On Thu, 12 Oct 2006 09:06:18 -0700
> > "James Kempf" <kempf@docomolabs-usa.com> wrote:
> >
> >> Yes, I agree. We faced this same issue in the NETLMM PS and REQ
drafts.
> >> All
> >> the co-authors contributed a considerable amount of work to the
> >> documents,
> >> and it would have been really unfair to selectively remove names.
Since
> I
> >> was acting as editor, I proposed that we list me as editor, and
that we
> >> put
> >> the Contributors section up front with a notice saying that we were
> >> removing
> >> the other author's names because of the RFC Editor policy and that
it
> had
> >> nothing to do with effort. Then, we listed their names in the
author's
> >> section at the end, just as if they had been listed on the first
page
> as
> >> authors. This raised a couple of eyebrows on the WG list but seemed
> >> acceptable in the end. I don't know if the position of the
Contributors
> >> section and the text therein will survive the RFC editing process,
> >> however.
> >> :-)
> >>
> >> Personally, I think if the IETF allows author's names on documents,
> then
> >> the
> >> RFC Editor really should allow all authors who contributed on the
> >> document.
> >> If the IETF weren't so wedded to its archaic ASCII text format, we
> could
> >> have documents with proper title pages where the number of authors
> >> wouldn't
> >> matter stylistically. Contributions by single individuals that make
it
> >> through the IETF WG process and are published as RFCs are rare
these
> >> days,
> >> most work is done by teams and the team members have a reasonable
> >> expectation that their names will appear prominently to acknowledge
> their
> >> contribution.
> >>
> >>             jak
> >>
> >>
> >> ----- Original Message -----
> >> From: "Soliman, Hesham" <hsoliman@qualcomm.com>
> >> To: "Tim Enos" <timbeck04@verizon.net>; "Vijay Devarapalli"
> >> <Vijay.Devarapalli@azairenet.com>; <mip6@ietf.org>
> >> Sent: Thursday, October 12, 2006 3:27 AM
> >> Subject: RE: [Mip6] issue 75: Authors on the front page should be
less
> >> than
> >> 6
> >>
> >>
> >>
> >>  > I'd like to suggest that the list of authors be kept as it
> >>  > is (i.e. I reject the proposal). I trust the authors put the
> >>  > names on the front page because their consensus was that
> >>  > each contributed substantially to the draft.
> >>
> >> =3D> As I said in the conclusion we never discussed this issue.
> >>
> >>    Of course if WG
> >>  > consensus is that the proposal is to be accepted, then
> >>  > perhaps as many as five names (including the editor) could
> >>  > be placed on the front page. I'd be fine with the authors
> >>  > taking that route as well.
> >>
> >> =3D> I hope we don't do that. It's difficult to remove names
selectively
> >> and it could cause some people to be unhappy. I think we either
keep
> all
> >> or keep editor and list the rest later. Keeping 5 names and
removing
> two
> >> would suggest that those two didn't contribute as much. I'm
> >> uncomfortable suggesting any two names to be removed from the list.
> >>
> >> Hesham
> >>
> >>  >
> >>  > Best Regards,
> >>  >
> >>  > Tim Enos
> >>  > Rom 8:28
> >>  >
> >>  > >From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
> >>  > >Date: 2006/10/10 Tue PM 01:25:23 CDT
> >>  > >To: "Soliman, Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
> >>  > >Subject: RE: [Mip6] issue 75: Authors on the front page
> >>  > should be less than 6
> >>  >
> >>  > >well, the guideline was put in when folks started having
> >>  > >a long list of authors to show how many companies support
> >>  > >a particular proposal. and it is just a guideline.
> >>  > >exceptions are allowed. a person's name appearing on the
> >>  > >front page depends on how much each person has contributed
> >>  > >to the draft.
> >>  > >
> >>  > >(I am one of the listed authors. I would be fine if my
> >>  > >name is not listed on the front page for this particular
> >>  > >draft, but in general I think it is not fair).
> >>  > >
> >>  > >Vijay
> >>  > >
> >>  > >> -----Original Message-----
> >>  > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
> >>  > >> Sent: Tuesday, October 10, 2006 8:12 AM
> >>  > >> To: mip6@ietf.org
> >>  > >> Subject: [Mip6] issue 75: Authors on the front page should be
> >>  > >> less than 6
> >>  > >>
> >>  > >> Issue text:
> >>  > >> -----------
> >>  > >> According to a guideline the number of authors on frontpage
> >>  > >> should be 5
> >>  > >> or less.
> >>  > >> Propose to keep an editor and list the co-authors in a
different
> >>  > >> section.
> >>  > >>
> >>  > >> Conclusion:
> >>  > >> -----------
> >>  > >>
> >>  > >> We haven't discussed this in the DT, so I'd like to ask the
WG to
> >>  > >> express opinions on this. Please suggest on of the
> >>  > following options:
> >>  > >>
> >>  > >> 1. reject: implies keeping the authors list as is.
> >>  > >> 2. accept: implies keeping the editor on the front page
> >>  > and moving the
> >>  > >> rest to an "Additional Authors" section.
> >>  > >>
> >>  > >> Hesham
> >>  > >>
> >
> > _______________________________________________
> > 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

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



From mip6-bounces@ietf.org Sat Oct 14 14:23:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GYo93-0006d3-RU; Sat, 14 Oct 2006 14:22:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GYo91-0006b6-7c
	for mip6@ietf.org; Sat, 14 Oct 2006 14:21:59 -0400
Received: from mail125.messagelabs.com ([85.158.136.35])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GYo4n-0004PE-Hp
	for mip6@ietf.org; Sat, 14 Oct 2006 14:17:39 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-10.tower-125.messagelabs.com!1160849855!16164268!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 9335 invoked from network); 14 Oct 2006 18:17:35 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-10.tower-125.messagelabs.com with SMTP;
	14 Oct 2006 18:17:35 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k9EIHVWF010442;
	Sat, 14 Oct 2006 11:17:31 -0700 (MST)
Received: from [10.129.40.42] ([10.129.40.42])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id k9EIHTUO028810;
	Sat, 14 Oct 2006 13:17:29 -0500 (CDT)
Message-ID: <453129B8.1060909@motorola.com>
Date: Sat, 14 Oct 2006 20:17:28 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
References: <7EB20EA0938B4D42A2D82689365C9B7A24A4F2@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A4F2@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Cc: mip6@ietf.org, Thierry Ernst <thierry.ernst@inria.fr>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Tsirtsis, George wrote:
> I think it is a shame that the bad behavior of the few affects all of
>  us in this way. It reminds me of the ban on water bottles in the 
> airplanes because someone built a liquid bomb. Although I am not 
> trying to equate the level of seriousness of the two issues, even the
>  airplane industry managed to get a lift on that ban after a while 
> :-)

Nice

> I think that people who contributed design ideas and actual text to a
>  specification should make up the authors list. People who 
> contributed only in smaller way should be acknowledged in the acks 
> section. People who contributed nothing should not be in the 
> document.

How about people who first implemented the protocol, without
contributing any new idea, just implement.  Too rarely I see
implementers even acknowledged.

> In general I would discourage the idea of large numbers of authors 
> since in practice it is unlikely many people actively work on any one
>  document. This is hard to do though, when the WGs set-up design 
> teams to get something done.

I strongly support the idea of small number of authors on the frontpage,
and small number of people working on one particular document.  BEtter
more documents, each innerly coherent, that interface well, than fewer
large documents whose implementers scratch their heads for _years_
wondering what the authors _really_ meant.

I don't see an IETF document as a visionary breakthrough invention, on
which someone wants to put their name to safeguard their reputation -
there are articles, books and patents for that.

> The WG chairs should have the power to request the authors list to be
>  cut down, if they thing it is unreasonably large or if they thing 
> that some people are trying to abuse the system. People that find 
> themselves in a design team and then for whatever reason never got to
>  do any work should feel obliged to get themselves off the list.

I think this seldom happens - an author that found themselves by a
certain circumstance on an IETF document author list will seldom request
removal if that circumstance changed, and if their text contribution is nil.

> In general I like to think that people do the right thing most of the
>  times and that any system can be abused. For example, if you mandate
>  that only one person can be in the front page we might have people 
> trying to become editors for all the wrong reasons.

I'd put a requirement on the quality of an "Editor" in that s/he has to
have no textual contribution in the draft, no personal idea about a
mechanism, just like a Chair.  I do respect a lot a good Editor work and
that is very needed.  But choosing an Editor as the person who floated
first the idea is not good, leads to biased drafts.

A good test to identify the best Editor of a document is to provide the
pre-draft to Editor and ask him/her to write the Introduction and the
Conclusion.  The Editor who can write that very good, and that best
reflects the contents, is very good.

Alex

> 
> George
> 
>> -----Original Message----- From: James Kempf 
>> [mailto:kempf@docomolabs-usa.com] Sent: Thursday, October 12, 2006 
>> 6:38 PM To: Thierry Ernst; mip6@ietf.org Subject: Re: [Mip6] issue 
>> 75: Authors on the front page should be less than 6
>> 
>> That idea has been floated in the past. The counterargument is, as
> Charlie
>> says, people whose names are on the draft tend to work harder to 
>> get
> it
>> done.
>> 
>> jak
>> 
>> ----- Original Message ----- From: "Thierry Ernst" 
>> <thierry.ernst@inria.fr> To: <mip6@ietf.org> Sent: Thursday, 
>> October 12, 2006 3:10 PM Subject: Re: [Mip6] issue 75: Authors on 
>> the front page should be less than 6
>> 
>> 
>>> Just wondering, why do we need author name in the first place ?
> Can't we
>>> simply add the name of the WG as the author ?
>>> 
>>> Thierry
>>> 
>>> 
>>> 
>>> On Thu, 12 Oct 2006 09:06:18 -0700 "James Kempf" 
>>> <kempf@docomolabs-usa.com> wrote:
>>> 
>>>> Yes, I agree. We faced this same issue in the NETLMM PS and REQ
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
> drafts.
>>>> All the co-authors contributed a considerable amount of work to
>>>>  the documents, and it would have been really unfair to 
>>>> selectively remove names.
> Since
>> I
>>>> was acting as editor, I proposed that we list me as editor, and
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
> that we
>>>> put the Contributors section up front with a notice saying that
>>>>  we were removing the other author's names because of the RFC 
>>>> Editor policy and that
> it
>> had
>>>> nothing to do with effort. Then, we listed their names in the
> author's
>>>> section at the end, just as if they had been listed on the 
>>>> first
> page
>> as
>>>> authors. This raised a couple of eyebrows on the WG list but 
>>>> seemed acceptable in the end. I don't know if the position of 
>>>> the
> Contributors
>>>> section and the text therein will survive the RFC editing 
>>>> process, however. :-)
>>>> 
>>>> Personally, I think if the IETF allows author's names on 
>>>> documents,
>> then
>>>> the RFC Editor really should allow all authors who contributed 
>>>> on the document. If the IETF weren't so wedded to its archaic 
>>>> ASCII text format, we
>> could
>>>> have documents with proper title pages where the number of 
>>>> authors wouldn't matter stylistically. Contributions by single 
>>>> individuals that make
> it
>>>> through the IETF WG process and are published as RFCs are rare
> these
>>>> days, most work is done by teams and the team members have a 
>>>> reasonable expectation that their names will appear prominently
>>>>  to acknowledge
>> their
>>>> contribution.
>>>> 
>>>> jak
>>>> 
>>>> 
>>>> ----- Original Message ----- From: "Soliman, Hesham" 
>>>> <hsoliman@qualcomm.com> To: "Tim Enos" <timbeck04@verizon.net>;
>>>>  "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>; 
>>>> <mip6@ietf.org> Sent: Thursday, October 12, 2006 3:27 AM 
>>>> Subject: RE: [Mip6] issue 75: Authors on the front page should 
>>>> be
> less
>>>> than 6
>>>> 
>>>> 
>>>> 
>>>>> I'd like to suggest that the list of authors be kept as it is
>>>>>  (i.e. I reject the proposal). I trust the authors put the 
>>>>> names on the front page because their consensus was that each
>>>>>  contributed substantially to the draft.
>>>> 
>>>> => As I said in the conclusion we never discussed this issue.
>>>> 
>>>> Of course if WG
>>>>> consensus is that the proposal is to be accepted, then 
>>>>> perhaps as many as five names (including the editor) could be
>>>>>  placed on the front page. I'd be fine with the authors 
>>>>> taking that route as well.
>>>> 
>>>> => I hope we don't do that. It's difficult to remove names
> selectively
>>>> and it could cause some people to be unhappy. I think we either
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
> keep
>> all
>>>> or keep editor and list the rest later. Keeping 5 names and
> removing
>> two
>>>> would suggest that those two didn't contribute as much. I'm 
>>>> uncomfortable suggesting any two names to be removed from the 
>>>> list.
>>>> 
>>>> Hesham
>>>> 
>>>>> 
>>>>> Best Regards,
>>>>> 
>>>>> Tim Enos Rom 8:28
>>>>> 
>>>>>> From: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com> 
>>>>>> Date: 2006/10/10 Tue PM 01:25:23 CDT To: "Soliman, Hesham" 
>>>>>> <hsoliman@qualcomm.com>, mip6@ietf.org Subject: RE: [Mip6] 
>>>>>> issue 75: Authors on the front page
>>>>> should be less than 6
>>>>> 
>>>>>> well, the guideline was put in when folks started having a 
>>>>>> long list of authors to show how many companies support a 
>>>>>> particular proposal. and it is just a guideline. exceptions
>>>>>> are allowed. a person's name appearing on the front page
>>>>>> depends on how much each person has contributed to the
>>>>>> draft.
>>>>>> 
>>>>>> (I am one of the listed authors. I would be fine if my name
>>>>>>  is not listed on the front page for this particular draft,
>>>>>>  but in general I think it is not fair).
>>>>>> 
>>>>>> Vijay
>>>>>> 
>>>>>>> -----Original Message----- From: Soliman, Hesham 
>>>>>>> [mailto:hsoliman@qualcomm.com] Sent: Tuesday, October 10,
>>>>>>>  2006 8:12 AM To: mip6@ietf.org Subject: [Mip6] issue 75:
>>>>>>>  Authors on the front page should be less than 6
>>>>>>> 
>>>>>>> Issue text: ----------- According to a guideline the 
>>>>>>> number of authors on frontpage should be 5 or less. 
>>>>>>> Propose to keep an editor and list the co-authors in a
> different
>>>>>>> section.
>>>>>>> 
>>>>>>> Conclusion: -----------
>>>>>>> 
>>>>>>> We haven't discussed this in the DT, so I'd like to ask 
>>>>>>> the
> WG to
>>>>>>> express opinions on this. Please suggest on of the
>>>>> following options:
>>>>>>> 
>>>>>>> 1. reject: implies keeping the authors list as is. 2. 
>>>>>>> accept: implies keeping the editor on the front page
>>>>> and moving the
>>>>>>> rest to an "Additional Authors" section.
>>>>>>> 
>>>>>>> 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
> 


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



From mip6-bounces@ietf.org Mon Oct 16 20:16:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZccq-0002tN-0F; Mon, 16 Oct 2006 20:16:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZRi4-0002V6-4q
	for mip6@ietf.org; Mon, 16 Oct 2006 08:36:48 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZRi1-0006Ep-6s
	for mip6@ietf.org; Mon, 16 Oct 2006 08:36:48 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 16 Oct 2006 05:36:44 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9GCaibI015157; Mon, 16 Oct 2006 05:36:44 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9GCaiin025782;
	Mon, 16 Oct 2006 05:36:44 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Oct 2006 05:36:44 -0700
Received: from cisco.com ([10.32.246.211]) by xfe-sjc-212.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Oct 2006 05:36:42 -0700
Message-ID: <45337CD9.5060500@cisco.com>
Date: Mon, 16 Oct 2006 05:36:41 -0700
From: Sri Gundavelli <sgundave@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.2) Gecko/20030208 Netscape/7
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: multipart/mixed; boundary="------------070202000009020907060500"
X-OriginalArrivalTime: 16 Oct 2006 12:36:42.0157 (UTC)
	FILETIME=[BBAC9DD0:01C6F11F]
DKIM-Signature: a=rsa-sha1; q=dns; l=51094; t=1161002204; x=1161866204;
	c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Proxy=20Mobile=20IPv6=20-=20I-D=20Submission;
	X=v=3Dcisco.com=3B=20h=3D7toNAR11mmvpoQE+N34xd3yUDGQ=3D;
	b=Lp+p5M59ShIDfkScOLC6ckJnHLTkmkil3z3luazGwhXoUeq696TTWhGIMAJZVyZFelF8j6ez
	KeV8OYTrd/jCwXzOPcJSUQJ7atDUshMCdJsadpF++m+OB9G67czcYbbb;
Authentication-Results: sj-dkim-1.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass (
	44 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 357ebc7cf4b4412c052977434485f95c
X-Mailman-Approved-At: Mon, 16 Oct 2006 20:16:07 -0400
Cc: "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: [Mip6] Proxy Mobile IPv6 - I-D Submission
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.
--------------070202000009020907060500
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Attached is the draft on Proxy Mobile IPv6 that we have
posted today. Please review and comment on this work.

Regards
Sri

-------- Original Message --------
Subject: I-D Submission: draft-sgundave-mip6-proxymip6-00.txt
Date: Mon, 16 Oct 2006 05:25:39 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: internet-drafts@ietf.org

Hi,

Please find the attached internet-draft

   draft-sgundave-mip6-proxymip6-00.txt

This is an individual submission for the Mobile IPv6 working group.
Please post this to the archives.

Thanks
Sri


--------------070202000009020907060500
Content-Type: text/plain;
 name="draft-sgundave-mip6-proxymip6-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="draft-sgundave-mip6-proxymip6-00.txt"




MIP6 WG                                                    S. Gundavelli
Internet-Draft                                                  K. Leung
Expires: April 19, 2007                                    Cisco Systems
                                                          V. Devarapalli
                                                         Azaire Networks
                                                        October 16, 2006


                           Proxy Mobile IPv6
                   draft-sgundave-mipv6-proxymipv6-00

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 April 19, 2007.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This specification describes a network-based mobility management
   protocol.  It is called Proxy Mobile IPv6 (PMIPv6) and is based on
   Mobile IPv6.  This protocol is for enabling any IPv6 host to achieve
   protocol mobility with out requiring the host to participate in any
   mobility related signaling.




Gundavelli, et al.       Expires April 19, 2007                 [Page 1]

Internet-Draft              Proxy Mobile IPv6               October 2006


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions used in this document  . . . . . . . . . . . . . .  3
   3.  Proxy Mobile IPv6 Protocol Overview  . . . . . . . . . . . . .  4
   4.  Message Formats  . . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  Proxy Binding Update . . . . . . . . . . . . . . . . . . .  9
     4.2.  Proxy Binding Acknowledgment . . . . . . . . . . . . . . .  9
     4.3.  Home Network Prefix Option . . . . . . . . . . . . . . . . 10
     4.4.  Error Codes  . . . . . . . . . . . . . . . . . . . . . . . 11
   5.  Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 11
     5.1.  Extensions to conceptual data structures . . . . . . . . . 11
     5.2.  Processing a Proxy Binding Update Request  . . . . . . . . 12
     5.3.  Packet Routing . . . . . . . . . . . . . . . . . . . . . . 12
   6.  Proxy Mobile Agent Operation . . . . . . . . . . . . . . . . . 13
     6.1.  Conceptual Data Structures . . . . . . . . . . . . . . . . 13
     6.2.  Access Authentication and obtaining the profile  . . . . . 14
     6.3.  Sending Proxy Binding Update request to the home agent . . 14
     6.4.  Processing Proxy Binding Acknowledgment message  . . . . . 14
     6.5.  Emulating the Mobile Station's home link . . . . . . . . . 15
     6.6.  Tunnel Lifetime Management . . . . . . . . . . . . . . . . 15
     6.7.  Packet Routing . . . . . . . . . . . . . . . . . . . . . . 15
   7.  Mobile Station Operation . . . . . . . . . . . . . . . . . . . 16
     7.1.  Booting for the first time . . . . . . . . . . . . . . . . 16
     7.2.  Roaming in the Network . . . . . . . . . . . . . . . . . . 17
     7.3.  IPv6 Host Protocol Parameters  . . . . . . . . . . . . . . 17
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 19
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 20
   11. Normative References . . . . . . . . . . . . . . . . . . . . . 20
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
   Intellectual Property and Copyright Statements . . . . . . . . . . 22



















Gundavelli, et al.       Expires April 19, 2007                 [Page 2]

Internet-Draft              Proxy Mobile IPv6               October 2006


1.  Introduction

   The IP Mobility protocols designed in the IETF so far involve the
   host in mobility management.  There are some deployment scenarios
   where a network-based mobility management protocol is considered
   appropriate.  The advantages to using a network-based mobility
   protocol include avoiding tunneling overhead over the air and support
   for hosts that do not implement any mobility management protocol.

   The document describes a network-based mobility management protocol
   based on Mobile IPv6. it is called Proxy Mobile IPv6 (PMIPv6).  One
   of the most important design considerations behind PMIPv6 has been to
   re-use as much as possible from the existing mobility protocols.

   There are many advantages to develop a protocol based on Mobile IPv6.
   Mobile IPv6 is a very mature mobility protocol for IPv6.  There have
   been many implementations and inter-operability events where Mobile
   IPv6 has been tested.  There also numerous specifications enhancing
   Mobile IPv6 that can be re-used.  Further, the Proxy MIPv6 solution
   described in this document allows the same Home Agent to provide
   mobility to hosts that use Mobile IPv6 and hosts that do not use any
   mobility management protocol.  Proxy Mobile IPv6 provides solution to
   a real deployment problem.



2.  Conventions used in this document

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

      The following new terminology and abbreviations are introduced in
      this document and all other general mobility related terms as
      defined in Mobile IPv6 specification [2].

      Proxy Mobile Agent (PMA)

         The proxy mobile agent is a functional element on the access
         router.  This is the entity that makes the mobile station
         believe it is at its home link, by emulating the home link
         properties.  It registers the location of the mobile station to
         the home agent and establishes a tunnel for receiving packets
         sent to the mobile station's home address.

      Mobility Station (MS)





Gundavelli, et al.       Expires April 19, 2007                 [Page 3]

Internet-Draft              Proxy Mobile IPv6               October 2006


         Any IPv6 host that has the ability to physically roam across
         different networks.  A Mobile Station is not required to have
         the Mobile IPv6 protocol stack.



3.  Proxy Mobile IPv6 Protocol Overview

   Every mobile station that roams in a PMIPv6 network, would typically
   be identified by an identifier, such as NAI and that identifier will
   have an associated policy profile that identifies the mobile's home
   network prefix, permitted address configuration modes, roaming policy
   and other parameters that are essential for providing mobility
   services.  This information is typically configured in a policy
   store, such as AAA.  It is possible the home network prefix is
   dynamically allocated for the mobile station when it boots up for the
   first time in the network, or it could be a statically configured
   value on per mobile station basis.  However, for all practical
   purposes, the PMIP network entities while serving a mobile station
   will have access to its profile.

   Once a mobile station enters its PMIPv6 network and performs the
   access authentication, the network will ensure the mobile station is
   always on its home network and further ensures it always gets its
   home address when using any of the address configuration procedures.
   In other words, there is home address/prefix that is specifically
   assigned for a mobile station and that prefix always follows the
   node, where ever it goes with in that PMIP domain.  From the
   perspective of the mobile station, the entire PMIP domain appears as
   a home link.

   When the mobile station attaches to a link on the access router
   running proxy mobile agent, the mobile station will present its
   identity to the network in the form of NAI as part of the access
   authentication procedure.  After a successful authentication, the
   proxy mobile agent will have the mobile station's profile.  The proxy
   mobile agent will have enough information to ensure the mobile
   station is at its home link.  It sends Router Advertisements with
   parameters that are specified for the mobile station's home link.  It
   is possible, this Router Advertisement may be in result to Router
   Solicitation message that the mobile proxy agent received from that
   mobile station.  The parameters in the Router Advertisement,
   including Link Prefix, MTU, Hop Limit, .etc., will be consistent with
   what the mobile station saw, when it previously attached to the
   network.  However, the link local address in the received Router
   Advertisement will be different from the link local address in the
   previously received Router Advertisement, making the mobile station
   believe that there is a new default router on the home link.  The



Gundavelli, et al.       Expires April 19, 2007                 [Page 4]

Internet-Draft              Proxy Mobile IPv6               October 2006


   Neighbor unreachability detection procedures will kick-in and the
   previous default Router entry will be removed from the mobile
   station's cache.  As explained in the later sections of the document,
   the mobile proxy agent can apply certain techniques to remove the
   previous default router entry from the mobile station's cache.

   The proxy mobile agent tries to register the mobile station's new
   point of attachment with its home agent.  In the PMIPv6 model, the
   home interface is a virtual interface and thus there is only one home
   agent that is anchoring the home prefix and so the mobile proxy agent
   can predictably locate the home agent that is anchoring the mobile
   station's home prefix, typically this would be the configured
   information in the mobile's policy profile.

   The proxy mobile agent sends a Proxy Binding Update message to the
   mobile station's home agent.  The message will have the mobile node's
   NAI identifier option.  The source address of that message will be
   the IPv6 address of the proxy mobile agent on the out going
   interface.  The contents of the message include the Mobile Node NAI
   option, Alternate Care-of Address option (optionally) and a NAI
   identifier of the proxy mobile node that is sending this request.
   After validating the request and upon accepting this binding update
   request, the home agent sets up a tunnel with encapsulation of Ipv6/
   IPv6 and with the source address of the tunnel fixed to its own
   address and the destination address of the proxy mobile agent,
   obtained from the Binding Update message.  This step of tunnel
   creation is not required, if there is an existing tunnel to the same
   mobile proxy agent.

   Further, the home agent will create a route entry pointing the home
   prefix of the mobile agent as reachable over the tunnel to the proxy
   mobile agent.  This route is not redistributed in the IGP.  The home
   agent will also send a Binding Acknowledgment accepting the binding
   update request.  The proxy mobile agent on receiving this Binding
   Acknowledgment will create a tunnel pointing to the home agent and
   will add a default route over the tunnel to the home agent.  All
   traffic from the mobile station that the proxy mobile agent receives
   in the role of a default router will route the traffic to the home
   agent over the tunnel.

   The mobile station on receiving this Router Advertisement will try to
   configure its interface either using stateful or stateless address
   configuration modes.  Either way, the mobile station will be able to
   obtain its home address for configuring on the interface.

   When using stateful address configuration, the proxy mobile agent
   will function as a DHCP relay agent.  It will set the giaddr field in
   the DHCP request from the mobile station to a random address in the



Gundavelli, et al.       Expires April 19, 2007                 [Page 5]

Internet-Draft              Proxy Mobile IPv6               October 2006


   mobile station's home prefix, forcing the DHCP server to allocate an
   address from that prefix and the tunnel route entry at the home agent
   will ensure the DHCP reply packet will get routed correctly to the
   proxy mobile agent.

   At this point, the mobile station has a valid home address at the
   point of current attachment, the serving proxy mobile agent and the
   home agent have proper routing states for handling the traffic sent
   by the mobile node and also for the incoming traffic to the mobile
   station.


   Call flow detailing the PMIPv6 protocol operation




      Mobile       Proxy       Home       Policy
     Station    Mobile Agent   Agent      Store (AAA)
        +           +           +           +
        |           |           |           |
        |Access     |           |           |
        |Initiation |           |           |
      1)o---------->|           |           |
        |           |           |           |
        |           |      AAA request      |
      2)|           o---------------------->|
        |           |           |           | Mobile Station
      3)|           |           |           o Authenticated
        |           |           |           |
        |           |       AAA reply       |
      4)|           |<----------------------o
        |           |           |           |
        |           |PMA obtains|           |
      5)|           | mobile's  |           |
        | Access    | profile   |           |
        | Auth      |           |           |
        | Complete  |           |           |
      6)|<----------o           |           |
        |           | Proxy     |           |
        |           | Binding   |           |
        |           | Update    |           |
      7)|           o---------->|           |
        |           |           |           |
        |           |           | AAA Query |
        |           |           |---------->|
        |           |           |           |
        |           |           | AAA Reply |



Gundavelli, et al.       Expires April 19, 2007                 [Page 6]

Internet-Draft              Proxy Mobile IPv6               October 2006


        |           |           |<----------|
        |           |           |           |
      8)|           |           o HA has the|
        |           |           | MS profile|
        |           |           |           |
        |           |           |           |
      9)|           |           o Creates   |
        |           |           | the HA-PMA|
        |           |           | routing   |
        |           |           | context   |
        |           |           | for the MS|
        |           |           | home prefx|
        |           |           |           |
        |           |           |           |
        |           | Proxy     |           |
        |           | Binding   |           |
        |           | Ack       |           |
     10)|           o<----------|           |
        |           |           |           |
        |           | Emulates  |           |
        |           | the mobile|           |
     11)|           o station's |           |
        |           | home link,|           |
        |           | if BU     |           |
        |           | accepted  |           |
        |           |           |           |
     12)o MS does   |           |           |
        | address   |           |           |
        | config    |           |           |
        |           |           |           |
     13)o  Mobile station can now use its   |
        |  home address for all protocol    |
        |  communication                    |
        |                                   |
        +                                   +





   Figure 1: PMIPv6 Protocol Operation



   Access Authentication:

   The network access authentication and authorization procedure ensures
   a valid mobile station is connected to the network.  Upon successful



Gundavelli, et al.       Expires April 19, 2007                 [Page 7]

Internet-Draft              Proxy Mobile IPv6               October 2006


   authentication by the policy server, the proxy mobile agent retrieves
   the mobile station's profile using the presented NAI.

   Proxy Binding Update:

   The proxy mobile agent sends a binding update request to the home
   agent on behalf of the mobile station registering the current anchor
   point and for creating a binding cache entry and a tunnel route for
   the mobile station's home prefix.

   Binding State at the Home Agent:

   The home agent creates a binding cache entry, tunnel towards the
   proxy mobile agent, a route for the mobile station's home prefix as
   reachable over the tunnel.

   Home Link Emulation:

   The proxy mobile agent emulates the mobile station's home interface
   on the access interface, making the mobile believe that it is
   connected to its home link.  The proxy mobile agent sends Router
   Advertisements with the mobile's home prefix and other attributes
   that are defined for the mobile station's home link.

   Address Configuration:

   Based on the flags specified in the Router Advertisements, the mobile
   station will use stateful or stateless address configuration methods
   for configuring its interface.  If stateful mode is chosen for
   address configuration, the proxy mobile agent on the access link will
   function as a relay agent and will set the giaddr field to the mobile
   station's home prefix.  Further, the proxy mobile agent will act as a
   default router for the mobile station.

   Packet Routing:

   The home agent is the anchor point for the mobile station's home
   prefix and thus it will receive all packets sent to the mobile
   station's home address/prefix.  The home agent will route all the
   received packets over the tunnel to the mobile proxy agent and in
   turn will route it on the access link.  For the packets originating
   from the mobile station, the proxy mobile agent will act as a default
   router and will route all the received packets over the tunnel to the
   home agent and in turn will route it to the destination.


4.  Message Formats




Gundavelli, et al.       Expires April 19, 2007                 [Page 8]

Internet-Draft              Proxy Mobile IPv6               October 2006


   This section defines extensions to the MIPv6 Binding Update message.

4.1.  Proxy Binding Update



       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
                                      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                      |            Sequence #         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |A|H|L|K|M|R|P|  Reserved       |            Lifetime           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




   Figure 2: Proxy Binding Update Message



   A new flag, the 'P' flag, is added to the Binding Update message.
   The P flag indicates that the registration is a Proxy registration.
   When a proxy mobile agent sends a registration to the home agent, the
   P flag MUST be set to 1 indicate to the home agent that this
   registration is a proxy registration sent by a proxy mobile agent on
   behalf of a mobile station.


4.2.  Proxy Binding Acknowledgment



       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
                                      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                      |   Status      |K|R|P|Reserved |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Sequence #            |           Lifetime            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+





Gundavelli, et al.       Expires April 19, 2007                 [Page 9]

Internet-Draft              Proxy Mobile IPv6               October 2006


   Figure 3: Proxy Binding Acknowledgment Message



   Proxy Registration Flag (P)

   The Proxy Registration Flag is set to indicate that the home agent
   that processed the Proxy Binding Update supports Proxy Registration.
   It is set to 1 only if the corresponding Proxy Binding Update had the
   Proxy Registration Flag set to 1.


4.3.  Home Network Prefix Option

   A new option, Home Network Prefix Option is defined for using it in
   the Binding Acknowledgment sent from the home agent to the proxy
   mobile agent.  This option can be used for notifying the assigned
   Home network prefix for the mobile station.  The proxy mobile agent
   can use this prefix information in Router Advertisements sent to the
   mobile station and also in the Address Pool Identifier option in the
   DHCP messages sent to the DHCP Server.

   The Home Network Prefix Option is only valid in the Proxy Binding
   Acknowledgments that are sent from the proxy mobile agent to the home
   agent in reply to a Proxy Binding Update request.  The home network
   prefix Option has an alignment requirement of 8n+4.  Its format is as
   follows:



       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     |   Length      |   Reserved    | Prefix Length |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +                                                               +
      |                                                               |
      +                   Local Network Prefix                        +
      |                                                               |
      +                                                               +
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



   Figure 4: Home Network Prefix Option




Gundavelli, et al.       Expires April 19, 2007                [Page 10]

Internet-Draft              Proxy Mobile IPv6               October 2006


4.4.  Error Codes

   Binding Acknowledgment Status Values

   The following status code values are defined for using them in the
   Binding Acknowledgment message when using PMIPv6 protocol.

   140: Proxy Registration not supported

   141: Proxy Registration from this proxy mobile agent not allowed

   The value allocation for this usage needs to be approved by the IANA
   and must be updated in the IANA registry.



5.  Home Agent Operation

   For supporting this scheme, the home agent MUST satisfy all the
   requirements listed in Section 8.4 of [1].  The key differences of
   this scheme when compared to the base protocol is as follows:


   o  The mobile station is not anchored on any physical interface on
      the home agent.  Thus the home agent is not required to perform
      any proxy ND operations for defending the home address on the home
      link.  The home agent is required to manage a binding cache entry
      for managing the session state and a routing state for properly
      routing the packets destined to the mobile station.

   o  Each mobile station has a home address in a prefix that is created
      exclusively for that mobile station and no other mobile station
      will share its home address from this prefix.

   o  The route entry specifying that the mobile station's home prefix
      is reachable via the tunnel is created as supposed to creating an
      route entry just for the mobile node's home address.

   o  If multiple mobile stations are currently visiting the same proxy
      mobile agent, all the binding updates will share the same care-of
      address and possibly the same tunnel.


5.1.  Extensions to conceptual data structures

   The home agent maintains a binding cache entry for each currently
   registered mobile node.  The Binding Cache is a conceptual data
   structure described in detail in [1].  For supporting this



Gundavelli, et al.       Expires April 19, 2007                [Page 11]

Internet-Draft              Proxy Mobile IPv6               October 2006


   specification, the home agent will continue to create binding cache
   entries for each mobile station that gets proxy registered by a proxy
   mobile agent.  In addition, the home agent may have to add an
   additional flag to this conceptual data structure indicating that the
   entry is a proxy registration.  This proxy registration flag may be
   turned off for all the usual direct registrations.


5.2.  Processing a Proxy Binding Update Request

   After receiving a Proxy Binding Update request from a proxy mobile
   agent on behalf of a mobile station, the home agent must process the
   request as defined Section 10, of the base Mobile IPv6 specification
   [1], with one exception that this request is a proxy request and
   proper authorization checks have to be enforced.

   The home agent has to verify the policy to ensure the proxy mobile
   agent that is sending this request has the right to do so, else it
   MUST reject the request and send a Proxy Binding Acknowledgment with
   the proper status code.

   Upon accepting this request, the home agent must create a Binding
   Cache entry, a tunnel to the proxy mobile agent adding the mobile
   station's home prefix route over the tunnel and should send a Binding
   Acknowledgment with the successful status code.


5.3.  Packet Routing

   After sending a successful Proxy Binding Acknowledgment for the Proxy
   Binding Acknowledgment reply, the home agent must set up a tunnel to
   the proxy mobile agent serving the mobile station.

   The bi-directional tunnel between the home agent and the proxy mobile
   agent is used for routing the packets sent by the mobile station and
   also for routing the packets that are sent to the mobile station.


   The following are the details of the tunnel.


   o  Tunnel Source Address is the home agent's address

   o  Tunnel Destination Address is the proxy mobile agent's address

   o  Tunnel Encapsulation Mode is IPv6/IPv6





Gundavelli, et al.       Expires April 19, 2007                [Page 12]

Internet-Draft              Proxy Mobile IPv6               October 2006


   The home agent functions as an anchor point for the mobile station's
   home prefix.  When the home agent receives a data packet destined for
   the mobile station's home prefix, it MUST forward the packet to the
   mobile station through the bi-directional tunnel established between
   itself and the serving proxy mobile agent.  The home agent typically
   can use the routing table for routing the packet to the mobile
   station through the established tunnel.

   All the reverse tunneled packets that the home agent receives from
   the tunnel, after removing the tunnel encapsulation should route them
   the destination specified in the inner packet header.  These routed
   packets will have the source address field set to the mobile
   station's home address.



6.  Proxy Mobile Agent Operation

   The Proxy Mobile Agent has the following functional roles.  It will
   emulate the mobile station's home network on the access link, will
   update the home agent about the current location of the mobile
   station, will setup data path for enabling the mobile station to use
   its home address for communication and to some extent the role of the
   proxy mobile agent is comparable to that of the foreign agent in
   Mobile IPv4.

   The link connecting the proxy mobile agent and the mobile station
   should be considered as a multicast enabled point to point link.  It
   is not a shared link and hence any neighbor discovery messages with
   link scope are seen only by the specific mobile station and the proxy
   mobile agent.


6.1.  Conceptual Data Structures

   Every proxy mobile agent must maintain a Visitor List.  It is a list
   of mobile stations that the proxy mobile agent is currently serving.
   This MAY be implemented in any manner keeping the consistency with
   the external behaviour described in this section.


   The Visitor List entry has the following fields:


   o  The NAI of the mobile station.  This is obtained as part of the
      network access authentication procedure.  This identifier is
      required for downloading the mobile station's profile from the
      policy store.



Gundavelli, et al.       Expires April 19, 2007                [Page 13]

Internet-Draft              Proxy Mobile IPv6               October 2006


   o  The home address of the mobile station.  This MAY be a configured
      parameter in the mobile station's profile.  This MAY also be an
      address assigned by the DHCP server when the mobile station uses
      stateful address configuration mode for configuring the interface.
      The proxy mobile agent must implement DHCP relay agent function
      and should have the ability to learn the address leased to the
      mobile node for supporting the address allocation modes using DHCP
      server.

   o  The home prefix of the mobile station.  This MUST be a configured
      parameter in the mobile station's profile.

   o  The last sequence number that was sent in the Proxy Binding Update
      request.


6.2.  Access Authentication and obtaining the profile

   When the mobile station attaches to a link on the access router
   running proxy mobile agent, it will present its identity to the
   network in the form of NAI as part of the access authentication
   procedure.  The proxy mobile agent should be able fetch the mobile
   station's profile using the presented NAI.


6.3.  Sending Proxy Binding Update request to the home agent

   After a successful access authentication, the proxy mobile agent
   sends a Proxy Binding Update request to the home agent.  The rules
   around constructing this message will be as defined in the base
   Mobile IPv6 specification [1].  The proxy mobile agent sends a Proxy
   Binding Update to the home agent.  The source address of this message
   will be the configured IPv6 address on the egress interface.  The
   contents of the message include the Mobile Node NAI option, Alternate
   Care-of Address option (optionally) and a NAI identifier of the proxy
   mobile node that is sending this request.  The NAI option for the
   proxy mobile node MAY NOT be required, in some deployments, if the
   home agent has mechanisms to identify the proxy mobile agent and for
   the verification of the mobile station's roaming policy.


6.4.  Processing Proxy Binding Acknowledgment message

   After receiving a Proxy Binding Acknowledgment with the status code
   indicating the acceptance of the Binding Acknowledgment, the proxy
   mobile agent can set up the tunnel to the home agent and add a
   default route to the home agent.




Gundavelli, et al.       Expires April 19, 2007                [Page 14]

Internet-Draft              Proxy Mobile IPv6               October 2006


   If the home agent denies the Proxy Binding Update request, the proxy
   mobile agent MUST NOT advertise the mobile station's home prefix on
   the link and there by denying the mobility service to the mobile
   station.


6.5.  Emulating the Mobile Station's home link

   The mobile proxy agent on the access link emulates the mobile
   station's home link behaviour.  It makes the mobile station believe
   it is on its home link.  The Router Advertisements that the mobile
   proxy agent sends on the access link will contain the mobile
   station's home link prefix.  The other parameters in the Router
   Advertisement with respect to address configuration should be policy
   driven and may be present in the mobile station's profile.


6.6.  Tunnel Lifetime Management

   In the traditional MIPv6 model, there is a separate tunnel from the
   home agent to each mobile node that has a binding entry.  The tunnel
   end-point of each these tunnels is the respective mobile node's
   care-of address and that is unique to that mobile node.  In the
   current context, the care-of address or the tunnel end-point is the
   address of the proxy mobile agent and there could be multiple mobile
   stations attached to the same proxy mobile agent and hence the tunnel
   is a fat tunnel serving multiple mobile stations.  This is identical
   to the Mobile IPv4 model, where a tunnel between the foreign agent
   and the home agent is shared by many visiting mobile nodes.

   The life cycle of the tunnels should not be based on a single binding
   entry.  A tunnel may get created due to a single binding entry and
   later may be shared by many other nodes.  So, the tearing down logic
   of the tunnel has to be based on the number of visitors over that
   tunnel.  Implementations are free to pre-establish tunnels between
   every home agent and every proxy mobile station in the network and
   with out creating and destroying the tunnels on a need basis.


6.7.  Packet Routing

   After receiving a successful Proxy Binding Acknowledgment for the
   Proxy Binding Update request, the proxy mobile agent sets up a tunnel
   to the mobile station's home agent.

   The bi-directional tunnel between the proxy mobile agent and the home
   agent is used for routing the packets sent by the mobile station and
   also the packets that are sent to the mobile station.



Gundavelli, et al.       Expires April 19, 2007                [Page 15]

Internet-Draft              Proxy Mobile IPv6               October 2006


   The following are the details of the tunnel.

   o  Tunnel Source Address is the IPv6 Address on the egress interface

   o  Tunnel Destination Address is the home agent's address

   o  Tunnel Encapsulation Mode is IPv6/IPv6

   The proxy mobile agent functions as a default router to the mobile
   station on the access link.  Any packets that the mobile station
   sends, it will simply route them to the home agent over the tunnel.
   Any packets that the proxy mobile agent receives from this tunnel, it
   will forward them on the access link.




7.  Mobile Station Operation


7.1.  Booting for the first time


   When the mobile station attaches to a link on the access router
   running proxy mobile agent, it will present its identity to the
   network in the form of NAI as part of the access authentication
   procedure.  After performing the required access authentication
   procedures, the mobile station would be assigned a Home Network
   prefix.  Once a prefix is allocated to the mobile station, the prefix
   just follows the mobile as it moves within the network.  The network
   will ensure, the mobile station retains its home prefix and home
   address, and the reachability using its home address, and thus
   providing the required network mobility with in that portion of that
   managed network with deployed proxy mobile agents.

   After a successful access authentication, the mobile station will
   send a Router Solicitation message.  The proxy mobile agent on the
   link will respond to the Router Solicitation message with a Router
   Advertisement.  The Router Advertisement will have the mobile
   station's home prefix, default router and other address configuration
   parameters.  The address configuration parameters such as Managed
   Address Configuration, Stateful Configuration flag values will be
   consistent with the home link policy.

   If the Router Advertisement has the Managed Address Configuration
   flag set, the mobile station, as it would normally do, will send a
   DHCP Request and again the proxy mobile agent on that link will
   ensure, the mobile station gets its home address as a lease from the



Gundavelli, et al.       Expires April 19, 2007                [Page 16]

Internet-Draft              Proxy Mobile IPv6               October 2006


   DHCP server.

   If the Router Advertisement does not have the Managed Address
   Configuration flag set, the mobile station can autoconfigure itself
   by appending its link-layer address (EUI-64 format) to the advertised
   local home network prefix.

   Once the address configuration is complete, the mobile station will
   always be able to use that IPv6 address anywhere with in that managed
   network where proxy mobile agents are deployed.  Further, the mobile
   station will always get the same Address even after a reboot.


7.2.  Roaming in the Network


   As the mobile station roams with in the network, moving from one link
   to the other, it always detects its home prefix.  The proxy mobile
   agent on the attached link emulates the home link behaviour for the
   mobile station.  It makes the mobile station believe it is on its
   home link.  The Router Solicitation messages will result in a Router
   Advertisement with its home prefix, default router and other
   configuration parameters remain consistent with the home link
   properties.


7.3.  IPv6 Host Protocol Parameters


   The specification assumes the mobile station to be a normal IPv6
   host, with its protocol operation consistent with the base IPv6
   specification [1].  All aspects of Neighbor Discovery Protocol,
   including Router Discovery, Neighbor Discovery, Address Configuration
   procedures will just remain the same as to the base IPv6 ND
   Specification [1].  However, the protocol recommends the mobile
   station to adjust the following IPv6 operating parameters to the
   below recommended values for protocol efficiency and for achieving
   faster hand-offs.


   Disabling Duplicate Address Detection:

   As per this specification, the mobile station and the proxy mobile
   agent share a point to point link.  All messages including multicast
   messages with link-local scope scope sent by the mobile station or
   the proxy mobile agent are seen only by those two entities.  Further,
   the prefix that is advertised on this shared link is specific to that
   mobile station and no other node will be on this link.  Thus, the DAD



Gundavelli, et al.       Expires April 19, 2007                [Page 17]

Internet-Draft              Proxy Mobile IPv6               October 2006


   procedures in this operating environment carry very little value and
   MAY NOT be required at all.  The mobile station MAY disable Duplicate
   Address Detection (DAD) procedure on the access link, if it does not
   violate any other specification.


   Lower Default Router List Cache Time-out:

   As per the base IPv6 specification [1], each IPv6 host will maintain
   certain host data structures including a Default Router list.  This
   is the list of on-link routers that have sent Router Advertisement
   messages and are eligible to be a default routers on that link.  The
   Router Lifetime field in the received Router Advertisement defines
   the life of this entry.

   In the current operational scenario, when the mobile station moves
   from one link to another, a new proxy mobile agent will advertise the
   prefix that is assigned for that visiting mobile station.  The mobile
   station thus believes its still on the same link and with the same
   on-link prefix as before.  However, the received Router Advertisement
   messages are from a different link-local address and thus making it
   believe there is a new default router on the link.  It is important
   that the mobile station uses the newly learnt default router as
   supposed to the previous default router.  The mobile station must
   update its default-router list with the new default router entry and
   must age out the previosly default router entry from its cache, just
   as specified in Section 6.3.5 of the base IPv6 ND specification [1].
   This action is critical for minimizing packet losses during a hand
   off period.

   On detecting a reachability problem, the mobile station will
   certainly detect the neighbor or the default router unreachability by
   performing a Neighbor Unreachability Detection procedure, but it is
   important that the mobile station times out the previous default
   router entry at the earliest.  If a given IPv6 host implementation
   has the provision to adjust these flush timers, still conforming to
   the base IPv6 ND specification, it is desirable to keep the flush-
   timers to suit the above consideration.

   However, if the proxy mobile agent has the ability to with draw the
   previous router entry, by multicasting a Router Advertisement using
   the link-local address that of the previous mobility proxy agent and
   with the Router Lifetime field set to zero, then it is possible to
   force the flush out of the Previous Default Router entry from the
   mobile station's cache.  This certainly requires the proxy mobile
   agent to notify its link-local address to the home agent as part of
   the binding update and the home agent to associate this opaque data
   with the binding cache entry so that a new proxy mobile agent can



Gundavelli, et al.       Expires April 19, 2007                [Page 18]

Internet-Draft              Proxy Mobile IPv6               October 2006


   learn the link-local address of the previous router and send a Router
   Advertisement with that link-local address.

   There are other solutions possible for this problem, including the
   usage of a virtual MAC address and a fixed link-local address for all
   the deployed proxy mobile agents in the network.  In any case, this
   is very much implementation dependent and has no bearing on the
   protocol specification.





8.  IANA Considerations

   This document defines a new flag (P) to the Binding Update message
   specified in [1].

   This document also defines new Binding Acknowledgment status values
   as described in Section 4.5.  The status values MUST be assigned from
   the same space used for Binding Acknowledgment status values in [1].



9.  Security Considerations

   The Mobile IPv6 base specification [1] requires the signaling
   messages between the home agent and the mobile node to be secured by
   the use of IPsec extension headers.

   This document introduces a new functional entity, proxy mobile agent,
   a function that will be implemented in the access routers.  This
   entity is responsible for performing the Mobile IPv6 signaling on
   behalf of the mobile station, also called as Proxy MIPv6 Signaling.

   As described in the base Mobile IPv6 specification [3], Section 5.1
   both the mobile client (in this case, its the proxy mobile agent) and
   the home agent MUST support and SHOULD use the Encapsulating Security
   Payload (ESP) header in transport mode and MUST use a non-NULL
   payload authentication algorithm to provide data origin
   authentication, data integrity and optional anti-replay protection.

   This document does not cover the security requirements for
   authorizing the mobile station for the use of the access link.  It is
   assumed that there are proper Layer-2 based authentication
   procedures, such as EAP, in place and will ensure the mobile station
   is properly identified and authorized before permitting it to access
   the network.  It is further assumed that the same security mechanism



Gundavelli, et al.       Expires April 19, 2007                [Page 19]

Internet-Draft              Proxy Mobile IPv6               October 2006


   will ensure the mobile session is not hijacked by malicious nodes on
   the access link.

   The proxy solution allows one device creating a routing state for
   some other device at the home agent.  It is important that the home
   agent has proper authorization services in place to ensure a given
   proxy mobile agent is permitted to be a proxy for a specific mobile
   station.  If proper security checks are not in place, a malicious
   node may be able to hijack a session or may do a denial-of-service
   attacks.



10.  Acknowledgments



11.  Normative References

   [1] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
   Specification", RFC 2460, December 1998.

   [2] Narten, T., Nordmark, E., Simpson, W., "Neighbor Discovery for IP
   Version 6 (IPv6)", RFC 2461, December 1998.

   [3] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
   IPv6", RFC 3775, June 2004.

   [4] Arkko, J., Devarapalli, V., and F. Dupont, "Using IPsec to
   Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents",
   RFC 3776, June 2004.




















Gundavelli, et al.       Expires April 19, 2007                [Page 20]

Internet-Draft              Proxy Mobile IPv6               October 2006


Authors' Addresses

   Sri Gundavelli
   Cisco Systems
   170 West Tasman Drive
   San Jose, CA  95134
   USA

   Email: sgundave@cisco.com


   Kent Leung
   Cisco Systems
   170 West Tasman Drive
   San Jose, CA  95134
   USA

   Email: kleung@cisco.com


   Vijay Devarapalli
   Azaire Networks
   4800 Great America Pkwy
   Santa Clara, CA  95054
   USA

   Email: vijay.devarapalli@azairenet.com
























Gundavelli, et al.       Expires April 19, 2007                [Page 21]

Internet-Draft              Proxy Mobile IPv6               October 2006


Intellectual Property Statement

   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.


Disclaimer of Validity

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


Copyright Statement

   Copyright (C) The Internet Society (2006).  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.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Gundavelli, et al.       Expires April 19, 2007                [Page 22]



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

--------------070202000009020907060500--




From mip6-bounces@ietf.org Tue Oct 17 00:48:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZgsA-0000zu-Kd; Tue, 17 Oct 2006 00:48:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZgs9-0000zP-5o; Tue, 17 Oct 2006 00:48:13 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GZgs7-0006mu-Po; Tue, 17 Oct 2006 00:48:13 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 16 Oct 2006 21:48:12 -0700
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.20060308/8.12.11) with ESMTP id
	k9H4mBst002780; Mon, 16 Oct 2006 21:48:11 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9H4mBAo027868;
	Mon, 16 Oct 2006 21:48:11 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Oct 2006 21:48:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution
	VsA solutionbased on MIP6 
Date: Mon, 16 Oct 2006 21:48:09 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B53DFF@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution
	VsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AA==
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>, <netlmm@ietf.org>
X-OriginalArrivalTime: 17 Oct 2006 04:48:10.0907 (UTC)
	FILETIME=[727A06B0:01C6F1A7]
DKIM-Signature: a=rsa-sha1; q=dns; l=3079; t=1161060491; x=1161924491;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[Mip6]=20RE=3A=20[netlmm]=20Network-based=20mobility=20-=20NETLM
	M=20DT=20Solution=20VsA=20solutionbased=20on=20MIP6=20;
	X=v=3Dcisco.com=3B=20h=3DiHtlxYnuVERrR2Iz174T7liTaHI=3D;
	b=mJJzP0veUCZfW81YlEYItAlKQ5/MLmPWBX/CM/UGL0RGoZiv11sn1zVpk80gpq2g6bX2iQ5n
	W4MmLcf2CFukYIxghVeU24zM6SlgxRO77njjlJ3xG9I98/VkXXwNe22m;
Authentication-Results: sj-dkim-2.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vidya.  Sorry for the delay.

Some SDOs have adopted PMIPv4 but not for localized MM within the access
network (which is the scope of NetLMM). =20

I think we should clarify the difference between non-MIPv6 mobility
option re-use vs. re-usable MIPv6 Home Agent.  Maybe this is something
the PMIPv6 camp should sort out first? ;)
I believe this is part of the questions posed by Phil on the consensus
call results.

Kent



-----Original Message-----
From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]=20
Sent: Wednesday, October 11, 2006 6:42 PM
To: Kent Leung (kleung); netlmm@ietf.org
Cc: mip6@ietf.org
Subject: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution
VsA solutionbased on MIP6=20

Hi Kent,
If there is a need for IPv4 signaling usage, I agree with you. But, I'm
not so sure that there is a need for that, practically speaking. I think
many of those who want v4-signaled network-based mobility have gone a
non-standard PMIPv4 route already - is that not true?=20

If we have a real need for IPv4 signaling, then we could potentially say
that there is a need for two different standards in this space - one
that allows for running over IPv4 and another that allows maximum re-use
of already defined mobility options.=20

But, if the industry adopted the latter solution today for sake of
re-use, do we ever expect the former one being deployed? Or, would the
world simply do v6-in-v4 tunneling or the non-standard PMIPv4 when a
solution over v4 is needed?=20

I don't know the answer :)=20

Vidya

> -----Original Message-----
> From: Kent Leung (kleung) [mailto:kleung@cisco.com]
> Sent: Wednesday, October 11, 2006 9:51 AM
> To: Narayanan, Vidya; netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: RE: [netlmm] Network-based mobility - NETLMM DT Solution Vs A

> solutionbased on MIP6
>=20
> Hi Vidya.  I don't see why running NetLMM signaling over IPv4 should=20
> be precluded by design?  Having such flexibility is a valuable asset=20
> for a standards based network-control mobility management protocol,=20
> IMHO.
>=20
> Kent
>=20
> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> Sent: Friday, October 06, 2006 8:24 PM
> To: netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: [netlmm] Network-based mobility - NETLMM DT Solution Vs A=20
> solutionbased on MIP6
>=20
>=20
> <snip>
> What does the NETLMM DT Solution bring, by being totally different=20
> from MIP6?
> --------------------------------------------------------------
> ----------
> ------
>=20
> 1. The protocol can be evolved to using a reliable transport protocol=20
> like SCTP at some point.
> 2. The protocol can run over IPv4 without changes.=20
>=20
> While these seem like good goals, what is the practical need for the=20
> above goals? For instance, is IPv4 signaling a necessity for a NETLMM=20
> solution?
>=20
> <snip>
>=20

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

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



From mip6-bounces@ietf.org Tue Oct 17 13:23:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZse4-0007Vc-Q4; Tue, 17 Oct 2006 13:22:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZse2-0007VW-V9
	for mip6@ietf.org; Tue, 17 Oct 2006 13:22:26 -0400
Received: from mail125.messagelabs.com ([85.158.136.35])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZse1-0002r0-GL
	for mip6@ietf.org; Tue, 17 Oct 2006 13:22:26 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-7.tower-125.messagelabs.com!1161105729!18021742!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 14516 invoked from network); 17 Oct 2006 17:22:09 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-7.tower-125.messagelabs.com with SMTP;
	17 Oct 2006 17:22:09 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k9HHM3DF029068;
	Tue, 17 Oct 2006 10:22:08 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k9HHM2nZ017468;
	Tue, 17 Oct 2006 12:22:02 -0500 (CDT)
Message-ID: <45351139.7090800@motorola.com>
Date: Tue, 17 Oct 2006 19:22:01 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <45337CD9.5060500@cisco.com>
In-Reply-To: <45337CD9.5060500@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Sri Gundavelli wrote:
> Attached is the draft on Proxy Mobile IPv6 that we have posted today.
>  Please review and comment on this work.

Hi, thanks for the draft.  I have some comments.

> 4.3.  Home Network Prefix Option [in BAck]
> 
> A new option, Home Network Prefix Option is defined for using it in 
> the Binding Acknowledgment sent from the home agent to the proxy 
> mobile agent.  This option can be used for notifying the assigned 
> Home network prefix for the mobile station.  The proxy mobile agent 
> can use this prefix information in Router Advertisements sent to the
>  mobile station and also in the Address Pool Identifier option in the
>  DHCP messages sent to the DHCP Server.

Why isn't the home network prefix sent by the HA to the proxy mobile
agent with 'proxy' Mobile Prefix Discovery, instead of BAck?

If the PMA (Proxy Mobile Agent) sends proxy BU and interprets proxy
BAcks it can also send proxy Mobile Prefix Solicitation and interpret a
proxy Mobile Prefix Advertisement, no?

> After receiving a Proxy Binding Acknowledgment with the status code 
> indicating the acceptance of the Binding Acknowledgment, the proxy 
> mobile agent can set up the tunnel to the home agent and add a 
> default route to the home agent.

If the PMA adds a default route each time it receives a proxy BAck it
may end up with many default routes - there should be only one (only
one is taken into account anyways).

That default route is practically a route for encapsulated packets
coming from the MN for which this proxy BAck corresponds - involves
traffic shaping or IP filters; not default route.  The default route
linking of PMA to HA should be there regardless of mobiles visiting it.

> Implementations are free to pre-establish tunnels between every home
>  agent and every proxy mobile station in the network and with out 
> creating and destroying the tunnels on a need basis.

The routes that should be pre-established (independent of MN movements)
are routes for straight traffic (not tunnel).  I don't think the tunnel
routes should be pre-established, nor post-established, should be
independent of an MN being attached to a PMA.

> The following are the details of the tunnel [on PMA].
> 
> o  Tunnel Source Address is the IPv6 Address on the egress interface
> 
> o  Tunnel Destination Address is the home agent's address
> 
> o  Tunnel Encapsulation Mode is IPv6/IPv6

And the routing table entr(y)(ies) corresponding to this tunnel?  It's
illustrative to mention it here.

> Any packets that the mobile station sends, it [PMA] will simply route
>  them to the home agent over the tunnel.

How does PMA know to route packets coming from a mobile, to the HA?

> As described in the base Mobile IPv6 specification [3], Section 5.1 
> both the mobile client (in this case, its the proxy mobile agent) and
>  the home agent MUST support and SHOULD use the Encapsulating 
> Security Payload (ESP) header in transport mode and MUST use a 
> non-NULL payload authentication algorithm to provide data origin 
> authentication, data integrity and optional anti-replay protection.

Is it feasible that a secure connection PMA-HA offers security to MN
whose Home Address is not in these SAs?   Is there any security between
MN and PMA?

Alex

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



From mip6-bounces@ietf.org Tue Oct 17 14:02:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZtH0-0005dy-LH; Tue, 17 Oct 2006 14:02:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtGz-0005cq-83
	for mip6@ietf.org; Tue, 17 Oct 2006 14:02:41 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GZtGw-0007vR-KX
	for mip6@ietf.org; Tue, 17 Oct 2006 14:02:41 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 17 Oct 2006 11:02:38 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9HI2bdA024342; Tue, 17 Oct 2006 11:02:37 -0700
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9HI2bio013022;
	Tue, 17 Oct 2006 11:02:37 -0700 (PDT)
Date: Tue, 17 Oct 2006 11:02:37 -0700 (PDT)
From: Sri Gundavelli <sgundave@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
In-Reply-To: <45351139.7090800@motorola.com>
Message-ID: <Pine.GSO.4.63.0610171033150.5867@irp-view7.cisco.com>
References: <45337CD9.5060500@cisco.com> <45351139.7090800@motorola.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=6496; t=1161108158; x=1161972158;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DXGn6skthNznVb6BceIKNv9Z4nis=3D;
	b=ufwZMXdRHu6ynuZ14rJuZ4050UrppjLmJ4qYmguGlNJE7nXGhcTez4Hz0DMeGOxodHA9XvEL
	LErl4t1OyXuJOazAXsFb8GdjLLE30NkNk9+tDkqnwQvHUAKQlOh1C6og;
Authentication-Results: sj-dkim-4.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex,

Thanks for the review comments .. please see inline ..

On Tue, 17 Oct 2006, Alexandru Petrescu wrote:

> Sri Gundavelli wrote:
>>  Attached is the draft on Proxy Mobile IPv6 that we have posted today.
>>   Please review and comment on this work.
>
> Hi, thanks for the draft.  I have some comments.
>
>>  4.3.  Home Network Prefix Option [in BAck]
>>
>>  A new option, Home Network Prefix Option is defined for using it in the
>>  Binding Acknowledgment sent from the home agent to the proxy mobile agent.
>>  This option can be used for notifying the assigned Home network prefix for
>>  the mobile station.  The proxy mobile agent can use this prefix
>>  information in Router Advertisements sent to the
>>   mobile station and also in the Address Pool Identifier option in the
>>   DHCP messages sent to the DHCP Server.
>
> Why isn't the home network prefix sent by the HA to the proxy mobile
> agent with 'proxy' Mobile Prefix Discovery, instead of BAck?
>

There is no state at the home agent for the proxy mobile agent. In this
PMIP model, there is a pre-assigned prefix on per MN basis, configured
in the policy store or at the HA. The proxy locates the HA using a AAA
query for the visiting mobile using NAI, sends a proxy binding update
to the HA. The reply has the assigned home prefix that is given for that
mobile.



> If the PMA (Proxy Mobile Agent) sends proxy BU and interprets proxy
> BAcks it can also send proxy Mobile Prefix Solicitation and interpret a
> proxy Mobile Prefix Advertisement, no?
>


Sure. The proxy mobile agent is emulating the mobile's home link on
the access link. The home link is physically at the access link and
the home prefix is following the mobile as it roams in the network.
The designated owner of that prefix is the proxy and so I dont see
a need for this message. But, if we want the home agent to control
the life time of this prefix, we can certainly add these messages.


>>  After receiving a Proxy Binding Acknowledgment with the status code
>>  indicating the acceptance of the Binding Acknowledgment, the proxy mobile
>>  agent can set up the tunnel to the home agent and add a default route to
>>  the home agent.
>
> If the PMA adds a default route each time it receives a proxy BAck it
> may end up with many default routes - there should be only one (only
> one is taken into account anyways).
>
> That default route is practically a route for encapsulated packets
> coming from the MN for which this proxy BAck corresponds - involves
> traffic shaping or IP filters; not default route.  The default route
> linking of PMA to HA should be there regardless of mobiles visiting it.
>

There is a tunnel between the home agent and the proxy mobile agent.
At the home agent, the mobile prefix is reachable via this tunnel.
When the mobile to a different link, the proxy mobile agent on that
link will establish a tunnel with the home agent. The home agent will
delete the prefix route from the prev tunnel and add it to the new
tunnel.

>From the proxy routing point of view, the tunnel is the default route.
The proxy is functioning as a default router on the access link
connecting the mobile, any traffic it receives on that link, it just
routes them on the tunnel to the home agent. The home agent after
decaps, will route the packet. So, there should be only one default
route at the proxy for each mobile.




>>  Implementations are free to pre-establish tunnels between every home
>>  agent and every proxy mobile station in the network and with out creating
>>  and destroying the tunnels on a need basis.
>
> The routes that should be pre-established (independent of MN movements)
> are routes for straight traffic (not tunnel).  I don't think the tunnel
> routes should be pre-established, nor post-established, should be
> independent of an MN being attached to a PMA.
>

Having pre-established tunnels in a closely managed network, avoids the
need for creating/deleting tunnel each time a mobile comes in. These are
fat tunnels supporting many mobiles as in MIPv4, so in some cases it
might be ok to pre-create the tunnel. But, adding a route over that
tunnel is based on MN's visit. But, you raised the issue of default
route, I agree we need to be clear on this as what the defaulr route
means when there are multiple MN's from different HA's.



>>  The following are the details of the tunnel [on PMA].
>>
>>  o  Tunnel Source Address is the IPv6 Address on the egress interface
>>
>>  o  Tunnel Destination Address is the home agent's address
>>
>>  o  Tunnel Encapsulation Mode is IPv6/IPv6
>
> And the routing table entr(y)(ies) corresponding to this tunnel?  It's
> illustrative to mention it here.
>

Ok.


>>  Any packets that the mobile station sends, it [PMA] will simply route
>>   them to the home agent over the tunnel.
>
> How does PMA know to route packets coming from a mobile, to the HA?
>

There is a tunnel from PMA to the HA for each mobile. The routing
state that the PMA creates can be based on the source prefix.

- All traffic from this source prefix, route this over the tunnel t0, with
the destination as the home agent.

or

The link connecting the proxy and the mobile is a point to point link.
Adding a simple VRF for this link and on the tunnel to the home agent,
with a default route over the tunnel, will route all packets from
that link on to the tunnel.




>>  As described in the base Mobile IPv6 specification [3], Section 5.1 both
>>  the mobile client (in this case, its the proxy mobile agent) and
>>  the home agent MUST support and SHOULD use the Encapsulating Security
>>  Payload (ESP) header in transport mode and MUST use a non-NULL payload
>>  authentication algorithm to provide data origin authentication, data
>>  integrity and optional anti-replay protection.
>
> Is it feasible that a secure connection PMA-HA offers security to MN
> whose Home Address is not in these SAs?   Is there any security between
> MN and PMA?

The messages that the HA and PMA exchange can be secured. So, the MN's
home address is not relevant here. If there is a SA betwen the HA and
PMA, it is sufficient to secure all proxy registration messages.


Access link security is based on Layer-2 mechanisms and this doc does
not cover that. Security Considerations has covered this.


Thanks for the feedback.
>
> Alex
>
>

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



From mip6-bounces@ietf.org Tue Oct 17 14:27:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZtf5-0004sy-VB; Tue, 17 Oct 2006 14:27:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZtf4-0004sf-TA; Tue, 17 Oct 2006 14:27:34 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GZtf0-0002Hn-BZ; Tue, 17 Oct 2006 14:27:34 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9HIRRKv024719
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 17 Oct 2006 11:27:28 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9HIRBbS010903; Tue, 17 Oct 2006 11:27:27 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Oct 2006 11:27:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution
	VsA solutionbased on MIP6 
Date: Tue, 17 Oct 2006 11:27:15 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325132420C7@NAEX13.na.qualcomm.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202B53DFF@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT Solution
	VsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAD86uyQ
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Kent Leung \(kleung\)" <kleung@cisco.com>, <netlmm@ietf.org>
X-OriginalArrivalTime: 17 Oct 2006 18:27:18.0329 (UTC)
	FILETIME=[E09F7A90:01C6F219]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kent,=20

> -----Original Message-----
> From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
> Sent: Monday, October 16, 2006 9:48 PM
> To: Narayanan, Vidya; netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] RE: [netlmm] Network-based mobility -=20
> NETLMM DT Solution VsA solutionbased on MIP6=20
>=20
> Hi Vidya.  Sorry for the delay.
>=20
> Some SDOs have adopted PMIPv4 but not for localized MM within=20
> the access network (which is the scope of NetLMM). =20
>=20

That is true. But, the question I have is whether their solution for
localized MM will be any different. As far as I know, a v6 protocol that
also allows support for v4 hosts seems to be the use case - but, I see
the point that this may not be universally true. So, it would help to
understand the real world use cases.=20

> I think we should clarify the difference between non-MIPv6=20
> mobility option re-use vs. re-usable MIPv6 Home Agent.  Maybe=20
> this is something the PMIPv6 camp should sort out first? ;) I=20
> believe this is part of the questions posed by Phil on the=20
> consensus call results.
>=20

I think this would be a good thing to sort out first. A full MIP6 HA
re-use is an unrealistic goal IMHO, given that it will lead to a
sub-optimal protocol with patches to MIP6 - but, it would be good to
have that discussion at this time.=20

Vidya

> Kent
>=20
>=20
>=20
> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> Sent: Wednesday, October 11, 2006 6:42 PM
> To: Kent Leung (kleung); netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: [Mip6] RE: [netlmm] Network-based mobility - NETLMM=20
> DT Solution VsA solutionbased on MIP6=20
>=20
> Hi Kent,
> If there is a need for IPv4 signaling usage, I agree with=20
> you. But, I'm not so sure that there is a need for that,=20
> practically speaking. I think many of those who want=20
> v4-signaled network-based mobility have gone a non-standard=20
> PMIPv4 route already - is that not true?=20
>=20
> If we have a real need for IPv4 signaling, then we could=20
> potentially say that there is a need for two different=20
> standards in this space - one that allows for running over=20
> IPv4 and another that allows maximum re-use of already=20
> defined mobility options.=20
>=20
> But, if the industry adopted the latter solution today for=20
> sake of re-use, do we ever expect the former one being=20
> deployed? Or, would the world simply do v6-in-v4 tunneling or=20
> the non-standard PMIPv4 when a solution over v4 is needed?=20
>=20
> I don't know the answer :)=20
>=20
> Vidya
>=20
> > -----Original Message-----
> > From: Kent Leung (kleung) [mailto:kleung@cisco.com]
> > Sent: Wednesday, October 11, 2006 9:51 AM
> > To: Narayanan, Vidya; netlmm@ietf.org
> > Cc: mip6@ietf.org
> > Subject: RE: [netlmm] Network-based mobility - NETLMM DT=20
> Solution Vs A
>=20
> > solutionbased on MIP6
> >=20
> > Hi Vidya.  I don't see why running NetLMM signaling over=20
> IPv4 should=20
> > be precluded by design?  Having such flexibility is a=20
> valuable asset=20
> > for a standards based network-control mobility management protocol,=20
> > IMHO.
> >=20
> > Kent
> >=20
> > -----Original Message-----
> > From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> > Sent: Friday, October 06, 2006 8:24 PM
> > To: netlmm@ietf.org
> > Cc: mip6@ietf.org
> > Subject: [netlmm] Network-based mobility - NETLMM DT Solution Vs A=20
> > solutionbased on MIP6
> >=20
> >=20
> > <snip>
> > What does the NETLMM DT Solution bring, by being totally different=20
> > from MIP6?
> > --------------------------------------------------------------
> > ----------
> > ------
> >=20
> > 1. The protocol can be evolved to using a reliable=20
> transport protocol=20
> > like SCTP at some point.
> > 2. The protocol can run over IPv4 without changes.=20
> >=20
> > While these seem like good goals, what is the practical=20
> need for the=20
> > above goals? For instance, is IPv4 signaling a necessity=20
> for a NETLMM=20
> > solution?
> >=20
> > <snip>
> >=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Tue Oct 17 14:52:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZu2W-0002pD-Qk; Tue, 17 Oct 2006 14:51:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZu2V-0002p8-JW
	for mip6@ietf.org; Tue, 17 Oct 2006 14:51:47 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZu2T-0004nW-3p
	for mip6@ietf.org; Tue, 17 Oct 2006 14:51:47 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 17 Oct 2006 11:51:44 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9HIpilS032136; Tue, 17 Oct 2006 11:51:44 -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 k9HIpYOh021754;
	Tue, 17 Oct 2006 11:51:44 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 17 Oct 2006 11:51:42 -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] Proxy Mobile IPv6 - I-D Submission
Date: Tue, 17 Oct 2006 11:51:41 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B5403E@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Proxy Mobile IPv6 - I-D Submission
Thread-Index: AcbyFm6ainVznJ5bRKm265YvQHUwkgABQb+g
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Sri Gundavelli \(sgundave\)" <sgundave@cisco.com>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 17 Oct 2006 18:51:42.0676 (UTC)
	FILETIME=[49711940:01C6F21D]
DKIM-Signature: a=rsa-sha1; q=dns; l=4429; t=1161111104; x=1161975104;
	c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DkpqBRJQ+uDkH9skQfvWFZdB2zlw=3D;
	b=i5THQICmsQSwbI6SLDfpimkfg9e2nSBaIOMaWr4Vnne/Wq3wRAIXu7ZO9KXBYd7nHbJD2RO0
	LbgK9mPu/w2tMfYWRujejlqA0607OrM7g2tv3Gg+2Kvx8e6r6jzG10c7;
Authentication-Results: sj-dkim-6.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: mip6@ietf.org, Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex and Sri.

I think we can avoid the specifics of default route, IP filter, VRF,
etc. in the forwarding of packets that came from the MN.  This is an
implementation choice since any of the methods will work (so you're both
right :).  No problem of using a method as an example for clarifications
though.  The gist is that packets from the MN and received on the MPA
will be tunneled to the HA.  The internal mechanism on the MPA is set up
by the signaling.

Kent

-----Original Message-----
From: Sri Gundavelli (sgundave)=20
Sent: Tuesday, October 17, 2006 11:03 AM
To: Alexandru Petrescu
Cc: mip6@ietf.org; Kent Leung (kleung); Vijay Devarapalli
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission

Hi Alex,

Thanks for the review comments .. please see inline ..

On Tue, 17 Oct 2006, Alexandru Petrescu wrote:

<snip>

>>  After receiving a Proxy Binding Acknowledgment with the status code

>> indicating the acceptance of the Binding Acknowledgment, the proxy=20
>> mobile  agent can set up the tunnel to the home agent and add a=20
>> default route to  the home agent.
>
> If the PMA adds a default route each time it receives a proxy BAck it=20
> may end up with many default routes - there should be only one (only=20
> one is taken into account anyways).
>
> That default route is practically a route for encapsulated packets=20
> coming from the MN for which this proxy BAck corresponds - involves=20
> traffic shaping or IP filters; not default route.  The default route=20
> linking of PMA to HA should be there regardless of mobiles visiting
it.
>

There is a tunnel between the home agent and the proxy mobile agent.
At the home agent, the mobile prefix is reachable via this tunnel.
When the mobile to a different link, the proxy mobile agent on that link
will establish a tunnel with the home agent. The home agent will delete
the prefix route from the prev tunnel and add it to the new tunnel.

>From the proxy routing point of view, the tunnel is the default route.
The proxy is functioning as a default router on the access link
connecting the mobile, any traffic it receives on that link, it just
routes them on the tunnel to the home agent. The home agent after
decaps, will route the packet. So, there should be only one default
route at the proxy for each mobile.




>>  Implementations are free to pre-establish tunnels between every home

>> agent and every proxy mobile station in the network and with out=20
>> creating  and destroying the tunnels on a need basis.
>
> The routes that should be pre-established (independent of MN=20
> movements) are routes for straight traffic (not tunnel).  I don't=20
> think the tunnel routes should be pre-established, nor=20
> post-established, should be independent of an MN being attached to a
PMA.
>

Having pre-established tunnels in a closely managed network, avoids the
need for creating/deleting tunnel each time a mobile comes in. These are
fat tunnels supporting many mobiles as in MIPv4, so in some cases it
might be ok to pre-create the tunnel. But, adding a route over that
tunnel is based on MN's visit. But, you raised the issue of default
route, I agree we need to be clear on this as what the defaulr route
means when there are multiple MN's from different HA's.



>>  The following are the details of the tunnel [on PMA].
>>
>>  o  Tunnel Source Address is the IPv6 Address on the egress interface
>>
>>  o  Tunnel Destination Address is the home agent's address
>>
>>  o  Tunnel Encapsulation Mode is IPv6/IPv6
>
> And the routing table entr(y)(ies) corresponding to this tunnel?  It's

> illustrative to mention it here.
>

Ok.


>>  Any packets that the mobile station sends, it [PMA] will simply
route
>>   them to the home agent over the tunnel.
>
> How does PMA know to route packets coming from a mobile, to the HA?
>

There is a tunnel from PMA to the HA for each mobile. The routing state
that the PMA creates can be based on the source prefix.

- All traffic from this source prefix, route this over the tunnel t0,
with the destination as the home agent.

or

The link connecting the proxy and the mobile is a point to point link.
Adding a simple VRF for this link and on the tunnel to the home agent,
with a default route over the tunnel, will route all packets from that
link on to the tunnel.


<snip>

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



From mip6-bounces@ietf.org Tue Oct 17 15:19:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZuSf-0004hH-L3; Tue, 17 Oct 2006 15:18:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZuSd-0004fA-Vn
	for mip6@ietf.org; Tue, 17 Oct 2006 15:18:47 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZuNO-0007RN-Ml
	for mip6@ietf.org; Tue, 17 Oct 2006 15:13:25 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-4.tower-128.messagelabs.com!1161112396!3591896!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.7]
Received: (qmail 5976 invoked from network); 17 Oct 2006 19:13:16 -0000
Received: from motgate7.mot.com (HELO motgate7.mot.com) (129.188.136.7)
	by server-4.tower-128.messagelabs.com with SMTP;
	17 Oct 2006 19:13:16 -0000
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate7.mot.com (8.12.11/Motorola) with ESMTP id k9HJDFoL022032;
	Tue, 17 Oct 2006 12:13:15 -0700 (MST)
Received: from [10.129.40.99] ([10.129.40.99])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k9HJCwm8020497;
	Tue, 17 Oct 2006 14:12:59 -0500 (CDT)
Message-ID: <45352B39.2080407@motorola.com>
Date: Tue, 17 Oct 2006 21:12:57 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <45337CD9.5060500@cisco.com> <45351139.7090800@motorola.com>
	<Pine.GSO.4.63.0610171033150.5867@irp-view7.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0610171033150.5867@irp-view7.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Sri, thanks for the response.

Sri Gundavelli wrote:
>> Why isn't the home network prefix sent by the HA to the proxy 
>> mobile agent with 'proxy' Mobile Prefix Discovery, instead of BAck?
>> 
>> 
>> 
>> 
> 
> There is no state at the home agent for the proxy mobile agent. In 
> this PMIP model, there is a pre-assigned prefix on per MN basis,

Does PMIPv6 work only with a per-MN prefix model?  Does it work when
there is a home prefix covering several MNs' home addresses?

> configured in the policy store or at the HA. The proxy locates the HA
>  using a AAA query for the visiting mobile using NAI, sends a proxy 
> binding update to the HA. The reply has the assigned home prefix that
>  is given for that mobile.

Does PMIPv6 work when the MN does _not_ use NAI for access control?
Many WiFi deployments and cellular deployments don't use NAI for access
control.

>> If the PMA (Proxy Mobile Agent) sends proxy BU and interprets proxy
>>  BAcks it can also send proxy Mobile Prefix Solicitation and 
>> interpret a proxy Mobile Prefix Advertisement, no?
>> 
> 
> Sure. The proxy mobile agent is emulating the mobile's home link on 
> the access link. The home link is physically at the access link and 
> the home prefix is following the mobile as it roams in the network. 
> The designated owner of that prefix is the proxy and so I dont see a 
> need for this message.

Uh?  I was tempted to think the owner of that prefix is the HA and
temporarily by a certain PMA.

>> That default route is practically a route for encapsulated packets
>>  coming from the MN for which this proxy BAck corresponds -
>> involves traffic shaping or IP filters; not default route.  The
>> default route linking of PMA to HA should be there regardless of
>> mobiles visiting it.
>> 
> There is a tunnel between the home agent and the proxy mobile agent.
>  At the home agent, the mobile prefix is reachable via this tunnel. 
> When the mobile to a different link, the proxy mobile agent on that 
> link will establish a tunnel with the home agent. The home agent will
>  delete the prefix route from the prev tunnel and add it to the new 
> tunnel.

Makes sense.

>> From the proxy routing point of view, the tunnel is the default 
>> route.
> The proxy is functioning as a default router on the access link 
> connecting the mobile, any traffic it receives on that link, it just
>  routes them on the tunnel to the home agent.

I see, so PMA's default route points to the tunnel interface, and there
is no default route pointing to the egress interface.  There is a
specific route to the HA through PMA's next-hop.

Now, if there are several mobiles under PMA there would be several such
tunnel interfaces, right?  Which one should be the default?

Saying "any traffic PMA receives on its ingress link it forwards to the
tunnel to the home agent" makes probably little sense because normal
simple routing does not happen based on the src address, only on the
destination address.  No?

>>> Implementations are free to pre-establish tunnels between every 
>>> home agent and every proxy mobile station in the network and with
>>>  out creating and destroying the tunnels on a need basis.
>> 
>> The routes that should be pre-established (independent of MN 
>> movements) are routes for straight traffic (not tunnel).  I don't 
>> think the tunnel routes should be pre-established, nor 
>> post-established, should be independent of an MN being attached to 
>> a PMA.
>> 
> 
> Having pre-established tunnels in a closely managed network, avoids 
> the need for creating/deleting tunnel each time a mobile comes in.

I don't understand... the PMA-HA tunnel should exist _only_ when the MN
is under that PMA.  And, since this is prefix-per-mobile there are as
many tunnels as there are mobiles.

> These are fat tunnels supporting many mobiles as in MIPv4,

But you said there is one prefix per mobile?  There should be one tunnel
per mobile no?  No fat tunnels, no?

In MIP4 there isn't this concept of replicating the home link prefix at
each FA MN may visit.

> so in some cases it might be ok to pre-create the tunnel. But, adding
>  a route over that tunnel is based on MN's visit. But, you raised the
>  issue of default route, I agree we need to be clear on this as what 
> the defaulr route means when there are multiple MN's from different 
> HA's.

Yes, I'm interested to understand how the prototype testbed can look,
thanks, ready to read it.

>>> Any packets that the mobile station sends, it [PMA] will simply 
>>> route them to the home agent over the tunnel.
>> 
>> How does PMA know to route packets coming from a mobile, to the HA?
>> 
>> 
>> 
>> 
>> 
> 
> There is a tunnel from PMA to the HA for each mobile. The routing 
> state that the PMA creates can be based on the source prefix.

Ok, so there is prefix per mobile.  What is the PMA routing state based
on the source prefix?  Is it IP filters?  (netfilter?).   Is it traffic
shaping?

> - All traffic from this source prefix, route this over the tunnel t0,
>  with the destination as the home agent.
> 
> or
> 
> The link connecting the proxy and the mobile is a point to point 
> link. Adding a simple VRF for this link and on the tunnel to the home
>  agent, with a default route over the tunnel, will route all packets 
> from that link on to the tunnel.

What is VRF?

Is the point-to-point link an IPv6 PPP link?

>> Is it feasible that a secure connection PMA-HA offers security to 
>> MN whose Home Address is not in these SAs?   Is there any security 
>> between MN and PMA?
> 
> The messages that the HA and PMA exchange can be secured. So, the 
> MN's home address is not relevant here. If there is a SA betwen the 
> HA and PMA, it is sufficient to secure all proxy registration 
> messages.
> 
> 
> Access link security is based on Layer-2 mechanisms and this doc does
>  not cover that. Security Considerations has covered this.

Ok.  I understand PMIPv6 security itself offers no layer3 security to
the mobile node on the wireless access, and that it relies on AAA
completely to offer that.

Alex

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



From mip6-bounces@ietf.org Tue Oct 17 15:21:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZuVC-0007K5-VB; Tue, 17 Oct 2006 15:21:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZuVB-0007Jz-G5
	for mip6@ietf.org; Tue, 17 Oct 2006 15:21:25 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZuV8-0000So-5I
	for mip6@ietf.org; Tue, 17 Oct 2006 15:21:25 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-5.tower-119.messagelabs.com!1161112835!8513829!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 28551 invoked from network); 17 Oct 2006 19:20:35 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-5.tower-119.messagelabs.com with SMTP;
	17 Oct 2006 19:20:35 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id k9HJKXXb004395;
	Tue, 17 Oct 2006 12:20:34 -0700 (MST)
Received: from [10.129.40.99] ([10.129.40.99])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k9HJKVlS022925;
	Tue, 17 Oct 2006 14:20:32 -0500 (CDT)
Message-ID: <45352CFE.2070004@motorola.com>
Date: Tue, 17 Oct 2006 21:20:30 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <2979E38DD6FC6544B789C8DAD7BAFC5202B5403E@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202B5403E@xmb-sjc-235.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: mip6@ietf.org, Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>,
	"Sri Gundavelli \(sgundave\)" <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

Kent Leung (kleung) wrote:
> Hi Alex and Sri.
> 
> I think we can avoid the specifics of default route, IP filter, VRF, 
> etc. in the forwarding of packets that came from the MN.  This is an 
> implementation choice since any of the methods will work (so you're
> both right :).  No problem of using a method as an example for
> clarifications though.  The gist is that packets from the MN and
> received on the MPA will be tunneled to the HA.

Sounds good, and an example is often relevant for illustrative purposes.

> The internal mechanism on the MPA is set up by the signaling.

Yes, I understand you mean PBU-PBAck signalling, combined eventually 
with profile retrieving based on AAA.

I'm wondering what can happen when the MR is allocated (via PMA) a 
prefix in PBAck.  Can MR use the prefix it's allocated in PBAck to 
distribute further in its moving network?  Or should it obtain the 
prefix from DHCP PD?

Alex

> 
> Kent
> 
> -----Original Message----- From: Sri Gundavelli (sgundave) Sent:
> Tuesday, October 17, 2006 11:03 AM To: Alexandru Petrescu Cc:
> mip6@ietf.org; Kent Leung (kleung); Vijay Devarapalli Subject: Re:
> [Mip6] Proxy Mobile IPv6 - I-D Submission
> 
> Hi Alex,
> 
> Thanks for the review comments .. please see inline ..
> 
> On Tue, 17 Oct 2006, Alexandru Petrescu wrote:
> 
> <snip>
> 
>>> After receiving a Proxy Binding Acknowledgment with the status
>>> code
> 
>>> indicating the acceptance of the Binding Acknowledgment, the
>>> proxy mobile  agent can set up the tunnel to the home agent and
>>> add a default route to  the home agent.
>> If the PMA adds a default route each time it receives a proxy BAck
>> it may end up with many default routes - there should be only one
>> (only one is taken into account anyways).
>> 
>> That default route is practically a route for encapsulated packets
>>  coming from the MN for which this proxy BAck corresponds -
>> involves traffic shaping or IP filters; not default route.  The
>> default route linking of PMA to HA should be there regardless of
>> mobiles visiting
> it.
> 
> There is a tunnel between the home agent and the proxy mobile agent. 
> At the home agent, the mobile prefix is reachable via this tunnel. 
> When the mobile to a different link, the proxy mobile agent on that
> link will establish a tunnel with the home agent. The home agent will
> delete the prefix route from the prev tunnel and add it to the new
> tunnel.
> 
>> From the proxy routing point of view, the tunnel is the default
>> route.
> The proxy is functioning as a default router on the access link 
> connecting the mobile, any traffic it receives on that link, it just 
> routes them on the tunnel to the home agent. The home agent after 
> decaps, will route the packet. So, there should be only one default 
> route at the proxy for each mobile.
> 
> 
> 
> 
>>> Implementations are free to pre-establish tunnels between every
>>> home
> 
>>> agent and every proxy mobile station in the network and with out
>>>  creating  and destroying the tunnels on a need basis.
>> The routes that should be pre-established (independent of MN 
>> movements) are routes for straight traffic (not tunnel).  I don't 
>> think the tunnel routes should be pre-established, nor 
>> post-established, should be independent of an MN being attached to
>> a
> PMA.
> 
> Having pre-established tunnels in a closely managed network, avoids
> the need for creating/deleting tunnel each time a mobile comes in.
> These are fat tunnels supporting many mobiles as in MIPv4, so in some
> cases it might be ok to pre-create the tunnel. But, adding a route
> over that tunnel is based on MN's visit. But, you raised the issue of
> default route, I agree we need to be clear on this as what the
> defaulr route means when there are multiple MN's from different HA's.
> 
> 
> 
> 
>>> The following are the details of the tunnel [on PMA].
>>> 
>>> o  Tunnel Source Address is the IPv6 Address on the egress
>>> interface
>>> 
>>> o  Tunnel Destination Address is the home agent's address
>>> 
>>> o  Tunnel Encapsulation Mode is IPv6/IPv6
>> And the routing table entr(y)(ies) corresponding to this tunnel?
>> It's
> 
>> illustrative to mention it here.
>> 
> 
> Ok.
> 
> 
>>> Any packets that the mobile station sends, it [PMA] will simply
> route
>>> them to the home agent over the tunnel.
>> How does PMA know to route packets coming from a mobile, to the HA?
>> 
>> 
> 
> There is a tunnel from PMA to the HA for each mobile. The routing
> state that the PMA creates can be based on the source prefix.
> 
> - All traffic from this source prefix, route this over the tunnel t0,
>  with the destination as the home agent.
> 
> or
> 
> The link connecting the proxy and the mobile is a point to point
> link. Adding a simple VRF for this link and on the tunnel to the home
> agent, with a default route over the tunnel, will route all packets
> from that link on to the tunnel.
> 
> 
> <snip>
> 


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



From mip6-bounces@ietf.org Tue Oct 17 15:28:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZubM-0003ZT-0f; Tue, 17 Oct 2006 15:27:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZubK-0003ZN-Qy
	for mip6@ietf.org; Tue, 17 Oct 2006 15:27:46 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZubI-00013z-F6
	for mip6@ietf.org; Tue, 17 Oct 2006 15:27:46 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 17 Oct 2006 12:27:44 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9HJRhWZ000756; Tue, 17 Oct 2006 12:27:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k9HJRhW4003160;
	Tue, 17 Oct 2006 12:27:43 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Oct 2006 12:27:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Proxy Mobile IPv6 - I-D Submission
Date: Tue, 17 Oct 2006 12:27:42 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B54084@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Proxy Mobile IPv6 - I-D Submission
Thread-Index: AcbyIW8jO44fVmaFQqSo9oT+J70adQAAEyOQ
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 17 Oct 2006 19:27:43.0725 (UTC)
	FILETIME=[518701D0:01C6F222]
DKIM-Signature: a=rsa-sha1; q=dns; l=494; t=1161113263; x=1161977263;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DkpqBRJQ+uDkH9skQfvWFZdB2zlw=3D;
	b=gSP1cARMAYhCMNMQ44uXndAbrwlHTY4flP9TW8gqRcrmN1sSIe6GXh+Sj483Q4okSr2LY+cN
	cDSI3beM1Mu4Mil3UP1Fcr65FyoeMWRYcHScLNl713nsbeYX8jlwpgyM;
Authentication-Results: sj-dkim-4.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: mip6@ietf.org, Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>,
	"Sri Gundavelli \(sgundave\)" <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

=20
<snip>

> The internal mechanism on the MPA is set up by the signaling.

Yes, I understand you mean PBU-PBAck signalling, combined eventually
with profile retrieving based on AAA.

I'm wondering what can happen when the MR is allocated (via PMA) a
prefix in PBAck.  Can MR use the prefix it's allocated in PBAck to
distribute further in its moving network?  Or should it obtain the
prefix from DHCP PD?

Alex

KL> Prefix delegation should be done via DHCP PD, IMHO.

Kent

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



From mip6-bounces@ietf.org Tue Oct 17 17:41:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZwgA-0007JX-0B; Tue, 17 Oct 2006 17:40:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GZwg8-0007JS-Bp
	for mip6@ietf.org; Tue, 17 Oct 2006 17:40:52 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GZwg6-0007Ej-Mf
	for mip6@ietf.org; Tue, 17 Oct 2006 17:40:52 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 17 Oct 2006 14:40:50 -0700
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.20060308/8.12.11) with ESMTP id
	k9HLeocG001366; Tue, 17 Oct 2006 14:40:50 -0700
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9HLenAp018007;
	Tue, 17 Oct 2006 14:40:49 -0700 (PDT)
Date: Tue, 17 Oct 2006 14:40:49 -0700 (PDT)
From: Sri Gundavelli <sgundave@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
In-Reply-To: <45352B39.2080407@motorola.com>
Message-ID: <Pine.GSO.4.63.0610171417010.5867@irp-view7.cisco.com>
References: <45337CD9.5060500@cisco.com> <45351139.7090800@motorola.com>
	<Pine.GSO.4.63.0610171033150.5867@irp-view7.cisco.com>
	<45352B39.2080407@motorola.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=8974; t=1161121250; x=1161985250;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DXGn6skthNznVb6BceIKNv9Z4nis=3D;
	b=X6GuQo6g5aKY8rlquGLA9SeZP/4wMEs/Ss4FZUBOBpjHiQuLuM2nqL8KMr2V8twJRcryhlUf
	6FsRS6Ja+97ZYmPS+SIGOqtTu2NcZs0Snw/fVlL8tu6AoRdU/TVAjkaJ;
Authentication-Results: sj-dkim-2.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 187ae6c2eea74946c0ab707161f6256d
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex,


On Tue, 17 Oct 2006, Alexandru Petrescu wrote:

> Hi Sri, thanks for the response.
>
> Sri Gundavelli wrote:
>> >  Why isn't the home network prefix sent by the HA to the proxy mobile 
>> >  agent with 'proxy' Mobile Prefix Discovery, instead of BAck?
>> > 
>> > 
>> > 
>> >
>>
>>  There is no state at the home agent for the proxy mobile agent. In this
>>  PMIP model, there is a pre-assigned prefix on per MN basis,
>
> Does PMIPv6 work only with a per-MN prefix model?  Does it work when
> there is a home prefix covering several MNs' home addresses?
>

[Sri]
Per prefix model simplifies lot of things. We can relieve the home agent
from all the ND related issues and just make it to deal with the data
path setup. Almost like a NEMO model, imagine access router (Proxy Agent)
as the mobile router and the MN home prefix as a MNP.

However, we can certainly extend this to cover the shared prefix model.
If there is enough interest, we can certainly cover that.



>>  configured in the policy store or at the HA. The proxy locates the HA
>>  using a AAA query for the visiting mobile using NAI, sends a proxy binding
>>  update to the HA. The reply has the assigned home prefix that
>>   is given for that mobile.
>
> Does PMIPv6 work when the MN does _not_ use NAI for access control?
> Many WiFi deployments and cellular deployments don't use NAI for access
> control.
>

[Sri] There should be a mechanism for the access router (PMA) to identify
the node. It could be NAI, MAC or other identifier. If there is a way to
pull out the profile, it should be sufficient for this protocol to work.



>> >  If the PMA (Proxy Mobile Agent) sends proxy BU and interprets proxy
>> >  BAcks it can also send proxy Mobile Prefix Solicitation and interpret a 
>> >  proxy Mobile Prefix Advertisement, no?
>> >
>>
>>  Sure. The proxy mobile agent is emulating the mobile's home link on the
>>  access link. The home link is physically at the access link and the home
>>  prefix is following the mobile as it roams in the network. The designated
>>  owner of that prefix is the proxy and so I dont see a need for this
>>  message.
>
> Uh?  I was tempted to think the owner of that prefix is the HA and
> temporarily by a certain PMA.
>

[Sri] Sure. HA is the prefix aggregation point. But, its deployed in the
access network. So, the life of the prefix should be managed by that
PMA. However, I see your point. We can certainly let the HA manage the
life of the prefix.



>> >  That default route is practically a route for encapsulated packets
>> >  coming from the MN for which this proxy BAck corresponds -
>> >  involves traffic shaping or IP filters; not default route.  The
>> >  default route linking of PMA to HA should be there regardless of
>> >  mobiles visiting it.
>> >
>>  There is a tunnel between the home agent and the proxy mobile agent.
>>  At the home agent, the mobile prefix is reachable via this tunnel. When
>>  the mobile to a different link, the proxy mobile agent on that link will
>>  establish a tunnel with the home agent. The home agent will
>>  delete the prefix route from the prev tunnel and add it to the new tunnel.
>
> Makes sense.
>
>> >  From the proxy routing point of view, the tunnel is the default route.
>>  The proxy is functioning as a default router on the access link connecting
>>  the mobile, any traffic it receives on that link, it just
>>   routes them on the tunnel to the home agent.
>
> I see, so PMA's default route points to the tunnel interface, and there
> is no default route pointing to the egress interface.  There is a
> specific route to the HA through PMA's next-hop.
>

[Sri] Sure.


> Now, if there are several mobiles under PMA there would be several such
> tunnel interfaces, right?  Which one should be the default?
>
> Saying "any traffic PMA receives on its ingress link it forwards to the
> tunnel to the home agent" makes probably little sense because normal
> simple routing does not happen based on the src address, only on the
> destination address.  No?
>

[Sri]
We just need to create a routing state, that says, for packets
from this prefix, this is the default route i.e tunnel interface
as the out going interface and the next hop being the home agent.

Ex: MN1 with prefix P1 as the home prefix and HA1 as the home agent
and t0 as the tunnel. MN2 with prefix P2 as the home prefix and HA2
as the home agent and t1 as the tunnel interface.

Routing will say, for all packets:

from P1 use t0 as the interface and
next hop HA1.

from P2 use t1 as the interface and
next hop HA2.



We can also create a routing state using VRF tables.
Almost all routing platforms support this.

But, as Kent says, route setup is implementation specific.


>> > >  Implementations are free to pre-establish tunnels between every home 
>> > >  agent and every proxy mobile station in the network and with
>> > >   out creating and destroying the tunnels on a need basis.
>> > 
>> >  The routes that should be pre-established (independent of MN movements) 
>> >  are routes for straight traffic (not tunnel).  I don't think the tunnel 
>> >  routes should be pre-established, nor post-established, should be 
>> >  independent of an MN being attached to a PMA.
>> >
>>
>>  Having pre-established tunnels in a closely managed network, avoids the
>>  need for creating/deleting tunnel each time a mobile comes in.
>
> I don't understand... the PMA-HA tunnel should exist _only_ when the MN
> is under that PMA.  And, since this is prefix-per-mobile there are as
> many tunnels as there are mobiles.

[Sri]
Prefix is per mobile. But a given PMA may have many visitors and so many
prefixes on its interfaces. There could multiple visitors from the
prefixes belonging to the same home agent, in that case, we just need
one tunnel. Tunnel is a shared tunnel as in MIP4.


>
>>  These are fat tunnels supporting many mobiles as in MIPv4,
>
> But you said there is one prefix per mobile?  There should be one tunnel
> per mobile no?  No fat tunnels, no?
>

Why not ? Prefix is per mobile. Take the nemo case. There could be
multiple  MNP's on a given MR. Still there is one tunnel. Just
as you wrote in 3963


> In MIP4 there isn't this concept of replicating the home link prefix at
> each FA MN may visit.
>
>>  so in some cases it might be ok to pre-create the tunnel. But, adding
>>   a route over that tunnel is based on MN's visit. But, you raised the
>>   issue of default route, I agree we need to be clear on this as what
>>  the defaulr route means when there are multiple MN's from different HA's.
>
> Yes, I'm interested to understand how the prototype testbed can look,
> thanks, ready to read it.
>

[Sri]
We can certainly add more examples.


>> > >  Any packets that the mobile station sends, it [PMA] will simply route 
>> > >  them to the home agent over the tunnel.
>> > 
>> >  How does PMA know to route packets coming from a mobile, to the HA?
>> > 
>> > 
>> > 
>> > 
>> >
>>
>>  There is a tunnel from PMA to the HA for each mobile. The routing state
>>  that the PMA creates can be based on the source prefix.
>
> Ok, so there is prefix per mobile.  What is the PMA routing state based
> on the source prefix?  Is it IP filters?  (netfilter?).   Is it traffic
> shaping?


[Sri]
Yes. Routing is based on source prefix or again using VRF's.


>
>>  - All traffic from this source prefix, route this over the tunnel t0,
>>   with the destination as the home agent.
>>
>>  or
>>
>>  The link connecting the proxy and the mobile is a point to point link.
>>  Adding a simple VRF for this link and on the tunnel to the home
>>  agent, with a default route over the tunnel, will route all packets from
>>  that link on to the tunnel.
>
> What is VRF?

Virtual Route Forwarding. I'm sure, the terminology could be different
in different implementations. But, routing can always be divided into
domains, a specific route is always in the context of that routing domain.
Ex: MPLS.


>
> Is the point-to-point link an IPv6 PPP link?
>
>> >  Is it feasible that a secure connection PMA-HA offers security to MN 
>> >  whose Home Address is not in these SAs?   Is there any security between 
>> >  MN and PMA?
>>
>>  The messages that the HA and PMA exchange can be secured. So, the MN's
>>  home address is not relevant here. If there is a SA betwen the HA and PMA,
>>  it is sufficient to secure all proxy registration messages.
>>
>>
>>  Access link security is based on Layer-2 mechanisms and this doc does
>>   not cover that. Security Considerations has covered this.
>
> Ok.  I understand PMIPv6 security itself offers no layer3 security to
> the mobile node on the wireless access, and that it relies on AAA
> completely to offer that.
>
> Alex
>
>

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



From mip6-bounces@ietf.org Tue Oct 17 20:46:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZzYu-0004Bh-NH; Tue, 17 Oct 2006 20:45:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZzYt-00047Q-FV; Tue, 17 Oct 2006 20:45:35 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GZzYq-0005f0-0m; Tue, 17 Oct 2006 20:45:35 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id CE232900BA;
	Tue, 17 Oct 2006 20:45:27 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 31793-01; Tue, 17 Oct 2006 20:45:26 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 17 Oct 2006 20:45:26 -0400 (EDT)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 17 Oct 2006 20:45:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
	SolutionVsA solutionbased on MIP6 
Date: Tue, 17 Oct 2006 20:45:26 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD3EB@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
	SolutionVsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAEKBePA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>
X-OriginalArrivalTime: 18 Oct 2006 00:45:27.0015 (UTC)
	FILETIME=[B4223770:01C6F24E]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: mip6@ietf.org, netlmm@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: Kent Leung (kleung) [mailto:kleung@cisco.com]
> Sent: Monday, October 16, 2006 11:48 PM
> To: Narayanan, Vidya; netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
> SolutionVsA solutionbased on MIP6
>=20
> Hi Vidya.  Sorry for the delay.
>=20
> Some SDOs have adopted PMIPv4 but not for localized MM within the
access
> network (which is the scope of NetLMM).
>=20
[KC>] PMIP (4 and 6) is used for network based mobility management for
simple IP sessions. Whether the scope is NOT localized is a subjective
discussion.


> I think we should clarify the difference between non-MIPv6 mobility
> option re-use vs. re-usable MIPv6 Home Agent.  Maybe this is something
> the PMIPv6 camp should sort out first? ;)

[KC>] Aren't you also in that camp now? Ref, your newly revived I-D on
pmip6. So, why don't you answer your own question?

> I believe this is part of the questions posed by Phil on the consensus
> call results.
>=20
> Kent
>=20
>=20
>=20
> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> Sent: Wednesday, October 11, 2006 6:42 PM
> To: Kent Leung (kleung); netlmm@ietf.org
> Cc: mip6@ietf.org
> Subject: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
Solution
> VsA solutionbased on MIP6
>=20
> Hi Kent,
> If there is a need for IPv4 signaling usage, I agree with you. But,
I'm
> not so sure that there is a need for that, practically speaking. I
think
> many of those who want v4-signaled network-based mobility have gone a
> non-standard PMIPv4 route already - is that not true?
>=20
> If we have a real need for IPv4 signaling, then we could potentially
say
> that there is a need for two different standards in this space - one
> that allows for running over IPv4 and another that allows maximum
re-use
> of already defined mobility options.
>=20
> But, if the industry adopted the latter solution today for sake of
> re-use, do we ever expect the former one being deployed? Or, would the
> world simply do v6-in-v4 tunneling or the non-standard PMIPv4 when a
> solution over v4 is needed?
>=20
> I don't know the answer :)
>=20
> Vidya
>=20
> > -----Original Message-----
> > From: Kent Leung (kleung) [mailto:kleung@cisco.com]
> > Sent: Wednesday, October 11, 2006 9:51 AM
> > To: Narayanan, Vidya; netlmm@ietf.org
> > Cc: mip6@ietf.org
> > Subject: RE: [netlmm] Network-based mobility - NETLMM DT Solution Vs
A
>=20
> > solutionbased on MIP6
> >
> > Hi Vidya.  I don't see why running NetLMM signaling over IPv4 should
> > be precluded by design?  Having such flexibility is a valuable asset
> > for a standards based network-control mobility management protocol,
> > IMHO.
> >
> > Kent
> >
> > -----Original Message-----
> > From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> > Sent: Friday, October 06, 2006 8:24 PM
> > To: netlmm@ietf.org
> > Cc: mip6@ietf.org
> > Subject: [netlmm] Network-based mobility - NETLMM DT Solution Vs A
> > solutionbased on MIP6
> >
> >
> > <snip>
> > What does the NETLMM DT Solution bring, by being totally different
> > from MIP6?
> > --------------------------------------------------------------
> > ----------
> > ------
> >
> > 1. The protocol can be evolved to using a reliable transport
protocol
> > like SCTP at some point.
> > 2. The protocol can run over IPv4 without changes.
> >
> > While these seem like good goals, what is the practical need for the
> > above goals? For instance, is IPv4 signaling a necessity for a
NETLMM
> > solution?
> >
> > <snip>
> >
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm

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



From mip6-bounces@ietf.org Tue Oct 17 21:04:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZzqr-0000TJ-R6; Tue, 17 Oct 2006 21:04:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GZzpM-0008Sd-W4; Tue, 17 Oct 2006 21:02:36 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GZzgD-00063e-Df; Tue, 17 Oct 2006 20:53:10 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 17 Oct 2006 17:53:09 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9I0r8T1012555; Tue, 17 Oct 2006 17:53:08 -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 k9I0r4OV023728;
	Tue, 17 Oct 2006 17:53:08 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 17 Oct 2006 17:53:04 -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] RE: [netlmm] Network-based mobility - NETLMM DT
	SolutionVsA solutionbased on MIP6 
Date: Tue, 17 Oct 2006 17:53:03 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B542B7@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
	SolutionVsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAEKBePAAACDNzA=
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
X-OriginalArrivalTime: 18 Oct 2006 00:53:04.0173 (UTC)
	FILETIME=[C49EFDD0:01C6F24F]
DKIM-Signature: a=rsa-sha1; q=dns; l=787; t=1161132788; x=1161996788;
	c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[Mip6]=20RE=3A=20[netlmm]=20Network-based=20mobility=20-=20NETLM
	M=20DT=20SolutionVsA=20solutionbased=20on=20MIP6=20;
	X=v=3Dcisco.com=3B=20h=3Du8xxKn/1R63rK/MkDdvUECctoJk=3D;
	b=tOglVmgQBoWZim5cpzHcRZKWXWwb1BsXl/wVWG3szyObkm2c8cOEi7EHx/32dQDGfk9LdG+6
	kZU5ckgwIIoD9NIm+rLBifLUjf6gkYGRdCzDvb5HLgBQnQNkO9gwV2ev;
Authentication-Results: sj-dkim-8.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip6@ietf.org, netlmm@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 Kuntal.
<snip>
>=20
> Some SDOs have adopted PMIPv4 but not for localized MM within the
access
> network (which is the scope of NetLMM).
>=20
[KC>] PMIP (4 and 6) is used for network based mobility management for
simple IP sessions. Whether the scope is NOT localized is a subjective
discussion.

KL> An objective way to look at it is from the reference interface
perspective.


> I think we should clarify the difference between non-MIPv6 mobility=20
> option re-use vs. re-usable MIPv6 Home Agent.  Maybe this is something

> the PMIPv6 camp should sort out first? ;)

[KC>] Aren't you also in that camp now? Ref, your newly revived I-D on
pmip6. So, why don't you answer your own question?

KL> The answer is in the draft. :)  Do you have an opinion?

Kent

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



From mip6-bounces@ietf.org Tue Oct 17 21:27:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga0D5-00032C-Nb; Tue, 17 Oct 2006 21:27:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga0D3-0002xd-SI; Tue, 17 Oct 2006 21:27:05 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ga0D1-0000wD-IQ; Tue, 17 Oct 2006 21:27:05 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-4.cisco.com with ESMTP; 17 Oct 2006 18:27:03 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9I1R2Mu026473; Tue, 17 Oct 2006 18:27:02 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9I1QwOV010265;
	Tue, 17 Oct 2006 18:27:02 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Oct 2006 18:26:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DTSolutionVsA
	solutionbased on MIP6 
Date: Tue, 17 Oct 2006 18:26:57 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B542D9@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM
	DTSolutionVsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAEKBePAAAEgzIA=
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
X-OriginalArrivalTime: 18 Oct 2006 01:26:58.0490 (UTC)
	FILETIME=[812B21A0:01C6F254]
DKIM-Signature: a=rsa-sha1; q=dns; l=550; t=1161134822; x=1161998822;
	c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[Mip6]=20RE=3A=20[netlmm]=20Network-based=20mobility=20-=20NETLM
	M=20DTSolutionVsA=20solutionbased=20on=20MIP6=20;
	X=v=3Dcisco.com=3B=20h=3DuUh3DmTVM9S+lQok/oZtMNGhsO0=3D;
	b=sNVsiDIOHKmoqNIuScY42IGgnC4PbNH2gSMOxmUFhh5zjFK1QYPBg+emlnxazBGM+h0m4+tO
	B/JMmUfn1vYxUncP1mtFsshIrhD3Xyw0a+VI9xCNur11IO/zvwsMOTkW;
Authentication-Results: sj-dkim-8.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org, netlmm@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

BTW, I believe the DT document is the right solution for network-based
localized MM.  It's a clean protocol that's designed for network node
signaling, without having excess baggage of a protocol used for host
control.  However, there's interest to revive PMIPv6 too.  Depending on
the application, one can choose the right fit, IMHO.  IPv6 over PMIPv4
might be another option to debate.   =20

Kent


<snip>

[KC>] Aren't you also in that camp now? Ref, your newly revived I-D on
pmip6. So, why don't you answer your own question?

<snip>

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



From mip6-bounces@ietf.org Tue Oct 17 21:38:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga0OM-0002En-Cl; Tue, 17 Oct 2006 21:38:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga0OK-0002ED-NY; Tue, 17 Oct 2006 21:38:44 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ga0OH-0001pR-A7; Tue, 17 Oct 2006 21:38:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id CE981900C2;
	Tue, 17 Oct 2006 21:38:37 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 32592-07; Tue, 17 Oct 2006 21:38:37 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 17 Oct 2006 21:38:37 -0400 (EDT)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 17 Oct 2006 21:38:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
	SolutionVsA solutionbased on MIP6 
Date: Tue, 17 Oct 2006 21:38:36 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD3EE@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
	SolutionVsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAEKBePAAACDNzAAAOziUA==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>
X-OriginalArrivalTime: 18 Oct 2006 01:38:37.0199 (UTC)
	FILETIME=[21A1A9F0:01C6F256]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: mip6@ietf.org, netlmm@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 Kent,

See inline....

-Kuntal

> -----Original Message-----
> From: Kent Leung (kleung) [mailto:kleung@cisco.com]
> Sent: Tuesday, October 17, 2006 7:53 PM
> To: Chowdhury, Kuntal
> Cc: mip6@ietf.org; netlmm@ietf.org
> Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT
> SolutionVsA solutionbased on MIP6
>=20
> Hi Kuntal.
> <snip>
> >
> > Some SDOs have adopted PMIPv4 but not for localized MM within the
> access
> > network (which is the scope of NetLMM).
> >
> [KC>] PMIP (4 and 6) is used for network based mobility management for
> simple IP sessions. Whether the scope is NOT localized is a subjective
> discussion.
>=20
> KL> An objective way to look at it is from the reference interface
> perspective.
>=20
[KC>] If the discussion gets too SDO specific (which I believe is going
to happen), I would suggest we take this offline. MIP4 is used for
inter-RNC mobility management in the radio access network in an SDO.
What do you call that? NOT global mobility I guess :-)

>=20
> > I think we should clarify the difference between non-MIPv6 mobility
> > option re-use vs. re-usable MIPv6 Home Agent.  Maybe this is
something
>=20
> > the PMIPv6 camp should sort out first? ;)
>=20
> [KC>] Aren't you also in that camp now? Ref, your newly revived I-D on
> pmip6. So, why don't you answer your own question?
>=20
> KL> The answer is in the draft. :)  Do you have an opinion?
>=20
[KC>] You can get a hint of my opinion in the I-D that we (Ajoy and I)
submitted. FYI...we have an I-D on pmip6 (aka netmip6) which we are
pursing all along w/o shifting position. The I-D is :
http://www.ietf.org/internet-drafts/draft-chowdhury-netmip6-01.txt

We do not propose non-MIP6 MO for *mobility management* in this I-D. The
essence of pmip6 is the compatibility with mip6. Maximum reuse of mip6
MO should be the guideline and re-inventing the wheel for the heck of it
should be avoided. So, the approach that introduces NEW MO for pmip6
seems to defeat the very purpose i.e. reuse mip6 protocol for proxy mip6
operation, IMHO.

=20
> Kent

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



From mip6-bounces@ietf.org Wed Oct 18 00:59:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga3VR-0007ap-4Q; Wed, 18 Oct 2006 00:58:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga3VQ-0007Re-21; Wed, 18 Oct 2006 00:58:16 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ga3VL-0004vl-N1; Wed, 18 Oct 2006 00:58:16 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 696CF900C8;
	Wed, 18 Oct 2006 00:58:08 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 03522-01; Wed, 18 Oct 2006 00:58:07 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 18 Oct 2006 00:58:07 -0400 (EDT)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 00:58:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DTSolutionVsA
	solutionbased on MIP6 
Date: Wed, 18 Oct 2006 00:58:07 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD3EF@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM
	DTSolutionVsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAEKBePAAAEgzIAAAQ51oA==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>
X-OriginalArrivalTime: 18 Oct 2006 04:58:07.0726 (UTC)
	FILETIME=[009F20E0:01C6F272]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mip6@ietf.org, netlmm@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: Kent Leung (kleung) [mailto:kleung@cisco.com]
> Sent: Tuesday, October 17, 2006 8:27 PM
> To: Chowdhury, Kuntal
> Cc: mip6@ietf.org; netlmm@ietf.org
> Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM
> DTSolutionVsA solutionbased on MIP6
>=20
> BTW, I believe the DT document is the right solution for network-based
> localized MM.  It's a clean protocol that's designed for network node
> signaling, without having excess baggage of a protocol used for host
> control.  However, there's interest to revive PMIPv6 too.  Depending
on
> the application, one can choose the right fit, IMHO.  IPv6 over PMIPv4
> might be another option to debate.
>=20
[KC>] There is interest in v6 over PMIPv4 too. There are two I-Ds
already:

http://www.join.uni-muenster.de/Dokumente/drafts/draft-navali-ip6-over-n
etmip4-00.txt

http://www.ietf.org/internet-drafts/draft-premec-mip4-ip6-proxy-mip4-00.
txt



> Kent
>=20
>=20
> <snip>
>=20
> [KC>] Aren't you also in that camp now? Ref, your newly revived I-D on
> pmip6. So, why don't you answer your own question?
>=20
> <snip>

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



From mip6-bounces@ietf.org Wed Oct 18 05:36:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ga7oY-0005LI-KZ; Wed, 18 Oct 2006 05:34:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga7oX-0005H7-Cj
	for mip6@ietf.org; Wed, 18 Oct 2006 05:34:17 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ga7em-0004aP-B5
	for mip6@ietf.org; Wed, 18 Oct 2006 05:24:13 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7B00ENMRB51Y@usaga01-in.huawei.com> for
	mip6@ietf.org; Wed, 18 Oct 2006 02:21:06 -0700 (PDT)
Received: from huawei.com ([172.17.1.218])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7B00JLPRB4QR@usaga01-in.huawei.com> for
	mip6@ietf.org; Wed, 18 Oct 2006 02:21:05 -0700 (PDT)
Received: from [172.24.1.3] (Forwarded-For: [218.80.168.246])
	by szxmc02-in.huawei.com (mshttpd); Wed, 18 Oct 2006 17:24:10 +0800
Date: Wed, 18 Oct 2006 17:24:10 +0800
From: huangzhigang 50541 <hpanda@huawei.com>
Subject: =?gb2312?B?u9i4tA==?=:[Mip6] Proxy Mobile IPv6 - I-D Submission
To: Sri Gundavelli <sgundave@cisco.com>
Message-id: <2e30b1c2e2d9e1.2e2d9e12e30b1c@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar  3 2004)
Content-type: multipart/mixed; boundary="Boundary_(ID_3upG9fiE8Xo/riuHbcO81w)"
Content-language: zh-CN
X-Accept-Language: zh-CN
Priority: normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_3upG9fiE8Xo/riuHbcO81w)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Content-disposition: inline

Hi all=2C

I have some questions about the draft=3A
1=2E There is no HA address in the Visitor List=2C how can PMA get to kno=
w HA address when it encapsulate the packets from MN=3F =

2=2E When MN moves to a new PMA=2C does the old PMA need to remove the MN=
 from the Visitor List=3F and how=3F
3=2E I think the case of the response to RS with multicast RA should be d=
escribed in the draft=2E



----- =D4=AD=D3=CA=BC=FE -----
=B7=A2=BC=FE=C8=CB=3A Sri Gundavelli =3Csgundave=40cisco=2Ecom=3E
=C8=D5=C6=DA=3A =D0=C7=C6=DA=D2=BB=2C =CA=AE=D4=C2 16=C8=D5=2C 2006 =CF=C2=
=CE=E78=3A36
=D6=F7=CC=E2=3A =5BMip6=5D Proxy Mobile IPv6 - I-D Submission

=3E Attached is the draft on Proxy Mobile IPv6 that we have
=3E posted today=2E Please review and comment on this work=2E
=3E =

=3E Regards
=3E Sri
=3E =

=3E -------- Original Message --------
=3E Subject=3A I-D Submission=3A draft-sgundave-mip6-proxymip6-00=2Etxt
=3E Date=3A Mon=2C 16 Oct 2006 05=3A25=3A39 -0700
=3E From=3A Sri Gundavelli =3Csgundave=40cisco=2Ecom=3E
=3E To=3A internet-drafts=40ietf=2Eorg
=3E =

=3E Hi=2C
=3E =

=3E Please find the attached internet-draft
=3E =

=3E   draft-sgundave-mip6-proxymip6-00=2Etxt
=3E =

=3E This is an individual submission for the Mobile IPv6 working group=2E=

=3E Please post this to the archives=2E
=3E =

=3E Thanks
=3E Sri
=3E =

=3E 

--Boundary_(ID_3upG9fiE8Xo/riuHbcO81w)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

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

--Boundary_(ID_3upG9fiE8Xo/riuHbcO81w)
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

--Boundary_(ID_3upG9fiE8Xo/riuHbcO81w)--




From mip6-bounces@ietf.org Wed Oct 18 10:00:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaBx3-0002jA-F4; Wed, 18 Oct 2006 09:59:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaBx2-0002j2-3W
	for mip6@ietf.org; Wed, 18 Oct 2006 09:59:20 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaBwz-0003lu-5F
	for mip6@ietf.org; Wed, 18 Oct 2006 09:59:20 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 18 Oct 2006 06:59:16 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9IDxGb2020698; Wed, 18 Oct 2006 06:59:16 -0700
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9IDxGAp008503;
	Wed, 18 Oct 2006 06:59:16 -0700 (PDT)
Date: Wed, 18 Oct 2006 06:59:16 -0700 (PDT)
From: Sri Gundavelli <sgundave@cisco.com>
To: huangzhigang 50541 <hpanda@huawei.com>
Subject: Re: =?gb2312?B?u9i4tA==?=:[Mip6] Proxy Mobile IPv6 - I-D Submission
In-Reply-To: <2e30b1c2e2d9e1.2e2d9e12e30b1c@huawei.com>
Message-ID: <Pine.GSO.4.63.0610180647580.5867@irp-view7.cisco.com>
References: <2e30b1c2e2d9e1.2e2d9e12e30b1c@huawei.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-15952070-1161179956=:5867"
DKIM-Signature: a=rsa-sha1; q=dns; l=2953; t=1161179956; x=1162043956;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20=3D?gb2312?B?u9i4tA=3D=3D?=3D=3A[Mip6]=20Proxy=20Mobile=20IPv6=2
	0-=20I-D=20Submission;
	X=v=3Dcisco.com=3B=20h=3D4QsnZA2cf6DaswnGDNEcv7F+VBo=3D;
	b=cMVwLYutVzfxlZVvCLNe5u7uQXnjeuvVOhxSqS+iw4RY3aehRatgJ/OFAk0HbrIoi53dbMvR
	i5eBDY+P9URoIf6IYCYcmc75xHlxog1zsM/o5P0VWYSkn1KVM44L+pGq;
Authentication-Results: sj-dkim-4.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass (
	40 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-15952070-1161179956=:5867
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi Huang,

Thanks for the review. Please see inline ..


On Wed, 18 Oct 2006, huangzhigang 50541 wrote:

> Hi all,
>
> I have some questions about the draft:
> 1. There is no HA address in the Visitor List, how can PMA get to know HA=
 address when it encapsulate the packets from MN?

When the mobile station attaches to the access link, the access
authentication procedures kick in and as part of this procedure,
the access router (proxy mobile agent) identifies the mobile station
and pulls out its profile from a policy store such as AAA. The
policy would have the home agent/home prefix attribute and that
will be used for sending the proxy binding update. Later in the
data path, the injected source based route, over the tunnel with
the home agent as the destination would handle the packet routing.


> 2. When MN moves to a new PMA, does the old PMA need to remove the MN fro=
m the Visitor List? and how?

Good point.

Registration revocation as in the base MIP6, is enforced as part of the
new registration. When the mobile station moves from AR1 to AR2, the
proxy registration from AR2, will force the home agent to move the
MN route from the previous tunnel AR1 to AR2. However, we did think
of defining a new message at AR1, when it detects a layer-2 event
when the moves out, it can certainly send PBU with 0 life. Minor
extension, we can do that.


> 3. I think the case of the response to RS with multicast RA should be des=
cribed in the draft.
>

Sure. We can do that. The RA will have the properties of the mobile
station's home link. The advertised prefix, address configuration
modes (stateful/stateless), Router life time ..etc will all be
consistent with the home link.

We can certainly add more text.


>
>
> ----- =D4=AD=D3=CA=BC=FE -----
> =B7=A2=BC=FE=C8=CB: Sri Gundavelli <sgundave@cisco.com>
> =C8=D5=C6=DA: =D0=C7=C6=DA=D2=BB, =CA=AE=D4=C2 16=C8=D5, 2006 =CF=C2=CE=
=E78:36
> =D6=F7=CC=E2: [Mip6] Proxy Mobile IPv6 - I-D Submission
>
>> Attached is the draft on Proxy Mobile IPv6 that we have
>> posted today. Please review and comment on this work.
>>
>> Regards
>> Sri
>>
>> -------- Original Message --------
>> Subject: I-D Submission: draft-sgundave-mip6-proxymip6-00.txt
>> Date: Mon, 16 Oct 2006 05:25:39 -0700
>> From: Sri Gundavelli <sgundave@cisco.com>
>> To: internet-drafts@ietf.org
>>
>> Hi,
>>
>> Please find the attached internet-draft
>>
>>   draft-sgundave-mip6-proxymip6-00.txt
>>
>> This is an individual submission for the Mobile IPv6 working group.
>> Please post this to the archives.
>>
>> Thanks
>> Sri
>>
>>
>
---559023410-15952070-1161179956=:5867
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

---559023410-15952070-1161179956=:5867--




From mip6-bounces@ietf.org Wed Oct 18 10:02:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaC0C-00049I-OT; Wed, 18 Oct 2006 10:02:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaC0B-00049C-Eu
	for mip6@ietf.org; Wed, 18 Oct 2006 10:02:35 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaC09-0004PT-5J
	for mip6@ietf.org; Wed, 18 Oct 2006 10:02:35 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 18 Oct 2006 07:02:32 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9IE2W08028455; Wed, 18 Oct 2006 07:02:32 -0700
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9IE2Vio024488;
	Wed, 18 Oct 2006 07:02:32 -0700 (PDT)
Date: Wed, 18 Oct 2006 07:02:31 -0700 (PDT)
From: Sri Gundavelli <sgundave@cisco.com>
To: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
In-Reply-To: <4535D660.4090501@6wind.com>
Message-ID: <Pine.GSO.4.63.0610180700460.5867@irp-view7.cisco.com>
References: <45337CD9.5060500@cisco.com> <4535D660.4090501@6wind.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=1448; t=1161180152; x=1162044152;
	c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DXGn6skthNznVb6BceIKNv9Z4nis=3D;
	b=alX1qVtNUWG7oKsKVehoXfcM7zo7Aw8tsxU0Kt/OtGrNh0178IcWGWJRgGIfl2/6b/S5fthg
	nPeZdMCe5XRlPgJiZRvQDZVlPxLo/1qGiWNwWYB0pSdd9gdmOsXQW4IM;
Authentication-Results: sj-dkim-1.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jean,

Thanks for the review. Comments inline ..


On Wed, 18 Oct 2006, Jean-Mickael Guerin wrote:

> Hello,
>
> >  Attached is the draft on Proxy Mobile IPv6 that we have
> >  posted today. Please review and comment on this work.
> My first idea of PMIP6 is an access router using directly MIP6
> to register multiple home addresses, each home address being
> actually mobile node's address. Assuming no change on Home agent,
> and same prefix sent by PMIP6 to mobiles.
>
> But looking at new PBU/PBA messages you introduced, it looks
> we can't do this way, could you elaborate ?
>

Access router (proxy mobile agent) is the proxy and is the entity
that is doing the binding update and we call this binding update
as proxy binding update (PBU). It is indeed using MIP6. Proxy
Binding Update is the MIP6 BU message with an additional flag
indicating to the home agent that it is a proxy registration and
thus the authorization checks have to be bit different.

The proxy mobile agent will advertise the same home prefix to
the mobile station on the access link. It emulates the home
link behaviour.

The changes in the home agent are semantical, a tunnel between the
home agent and the proxy mobile agent, that has no 1:1 relation
to a mobile station, as the tunnel can now be shared for multiple
mobiles, as in MIP4. The changes in the home agent are just
to support these minor extensions.

Regards
Sri


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



From mip6-bounces@ietf.org Wed Oct 18 10:35:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaCVW-0001Vt-5q; Wed, 18 Oct 2006 10:34:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaCVU-0001Vl-HQ
	for mip6@ietf.org; Wed, 18 Oct 2006 10:34:56 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaCVT-0001Th-80
	for mip6@ietf.org; Wed, 18 Oct 2006 10:34:56 -0400
Received: from [10.1.210.5] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 07:34:54 -0700
Message-ID: <45363B78.90401@azairenet.com>
Date: Wed, 18 Oct 2006 07:34:32 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <45337CD9.5060500@cisco.com> <4535D660.4090501@6wind.com>
In-Reply-To: <4535D660.4090501@6wind.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Oct 2006 14:34:54.0660 (UTC)
	FILETIME=[93F63040:01C6F2C2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	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

Jean-Mickael,

the current PMIPv6 draft is an individual submission.
we haven't yet decided on whether there will be per-MN
tunnel between the PMA and the HA or there will be one
tunnel for all mobile nodes, or both. my personal
preference is to allow both (I think there are
deployment scenarios for both).

its the same with per-MN security association or just
one security association between the PMA and the HA.

this will be a WG decision to be made later (once we
figure out how to standardize PMIPv6).

Vijay

Jean-Mickael Guerin wrote:
> Hello,
> 
>> Attached is the draft on Proxy Mobile IPv6 that we have
>> posted today. Please review and comment on this work.
> My first idea of PMIP6 is an access router using directly MIP6
> to register multiple home addresses, each home address being
> actually mobile node's address. Assuming no change on Home agent,
> and same prefix sent by PMIP6 to mobiles.
> 
> But looking at new PBU/PBA messages you introduced, it looks
> we can't do this way, could you elaborate ?
> 
> Regards,
> 
> Jean-Mickael

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



From mip6-bounces@ietf.org Wed Oct 18 13:10:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaEvg-0006zv-5O; Wed, 18 Oct 2006 13:10:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaEvf-0006zq-BI
	for mip6@ietf.org; Wed, 18 Oct 2006 13:10:07 -0400
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaEva-00032v-Uc
	for mip6@ietf.org; Wed, 18 Oct 2006 13:10:07 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	k9IH3Hr25410; Wed, 18 Oct 2006 13:03:17 -0400 (EDT)
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] Proxy Mobile IPv6 - I-D Submission
Date: Wed, 18 Oct 2006 12:09:57 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F66E3@zrc2hxm2.corp.nortel.com>
In-Reply-To: <45363B78.90401@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Proxy Mobile IPv6 - I-D Submission
Thread-Index: AcbyxHVW4ANyA+0bQ7GUSYZMk1lh5wAE2h1g
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Jean-Mickael Guerin" <jean-mickael.guerin@6wind.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	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

I believe we should consider the following as tunnel options:

1- tunnel which could be shared between n MTs (n=3D1..N).
2- we should consider uni-directional tunnel, since it is needed by some
new wireless technologies.

-----Original Message-----
From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
Sent: Wednesday, October 18, 2006 9:35 AM
To: Jean-Mickael Guerin
Cc: mip6@ietf.org; Kent Leung (kleung); Sri Gundavelli
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission


Jean-Mickael,

the current PMIPv6 draft is an individual submission.
we haven't yet decided on whether there will be per-MN
tunnel between the PMA and the HA or there will be one
tunnel for all mobile nodes, or both. my personal
preference is to allow both (I think there are
deployment scenarios for both).

its the same with per-MN security association or just
one security association between the PMA and the HA.

this will be a WG decision to be made later (once we
figure out how to standardize PMIPv6).

Vijay

Jean-Mickael Guerin wrote:
> Hello,
>=20
>> Attached is the draft on Proxy Mobile IPv6 that we have posted today.

>> Please review and comment on this work.
> My first idea of PMIP6 is an access router using directly MIP6 to=20
> register multiple home addresses, each home address being actually=20
> mobile node's address. Assuming no change on Home agent, and same=20
> prefix sent by PMIP6 to mobiles.
>=20
> But looking at new PBU/PBA messages you introduced, it looks we can't=20
> do this way, could you elaborate ?
>=20
> Regards,
>=20
> Jean-Mickael

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

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



From mip6-bounces@ietf.org Wed Oct 18 13:50:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaFYC-0006ix-U2; Wed, 18 Oct 2006 13:49:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaFYB-0006im-7f
	for mip6@ietf.org; Wed, 18 Oct 2006 13:49:55 -0400
Received: from ccerelrim04.cce.hp.com ([161.114.21.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaFY5-0003Pv-L4
	for mip6@ietf.org; Wed, 18 Oct 2006 13:49:55 -0400
Received: from ccerelrim04.cce.hp.com (localhost.localdomain [127.0.0.1])
	by receive-from-antispam-filter (Postfix) with SMTP id EEE484023;
	Wed, 18 Oct 2006 12:49:48 -0500 (CDT)
Received: from mailstation.cce.hp.com (mailstation.cce.hp.com [161.114.20.124])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by ccerelrim04.cce.hp.com (Postfix) with ESMTP id 29A824030;
	Wed, 18 Oct 2006 12:49:48 -0500 (CDT)
Received: from [192.168.1.101] (c-24-91-248-53.hsd1.ma.comcast.net
	[24.91.248.53]) by mailstation.cce.hp.com (Postfix) with ESMTP
	id 3F8C9F894; Wed, 18 Oct 2006 12:49:45 -0500 (CDT)
Message-ID: <4536692F.40606@hp.com>
Date: Wed, 18 Oct 2006 13:49:35 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <45337CD9.5060500@cisco.com>
In-Reply-To: <45337CD9.5060500@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.2.1.279297, Antispam-Engine: 2.4.0.264935,
	Antispam-Data: 2006.10.18.102443
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Sri,

A few comments on the draft inline.

>                            Proxy Mobile IPv6
>                    draft-sgundave-mipv6-proxymipv6-00

>    Further, the home agent will create a route entry pointing the home
>    prefix of the mobile agent as reachable over the tunnel to the proxy
>    mobile agent.  This route is not redistributed in the IGP.  The home
>    agent will also send a Binding Acknowledgment accepting the binding
>    update request.  The proxy mobile agent on receiving this Binding
>    Acknowledgment will create a tunnel pointing to the home agent and
>    will add a default route over the tunnel to the home agent.  All
>    traffic from the mobile station that the proxy mobile agent receives
>    in the role of a default router will route the traffic to the home
>    agent over the tunnel.

Alexandru also brought-up the "default route" text in this paragraph as 
an issue, I'd second a request to change per Sri's/Kent's comments. 
Section 6.4 too.

>    The mobile station on receiving this Router Advertisement will try to
>    configure its interface either using stateful or stateless address
>    configuration modes.  Either way, the mobile station will be able to
>    obtain its home address for configuring on the interface.

What Router Advertisement? :)  Assuming it's the same from page 3, maybe 
the simple fix would be to change this to "The mobile station, on 
receiving a Router Advertisement...", but maybe you should say that 
after receiving the BAck and setting up the tunnel, the MPA sends out an 
RA to the MN.

>    Packet Routing:
> 
>    The home agent is the anchor point for the mobile station's home
>    prefix and thus it will receive all packets sent to the mobile
>    station's home address/prefix.  The home agent will route all the
>    received packets over the tunnel to the mobile proxy agent and in
>    turn will route it on the access link.

s/and in turn/which in turn/

> 4.3.  Home Network Prefix Option
> 
>    A new option, Home Network Prefix Option is defined for using it in
>    the Binding Acknowledgment sent from the home agent to the proxy
>    mobile agent.  This option can be used for notifying the assigned
>    Home network prefix for the mobile station.  The proxy mobile agent
>    can use this prefix information in Router Advertisements sent to the
>    mobile station and also in the Address Pool Identifier option in the
>    DHCP messages sent to the DHCP Server.
> 
>    The Home Network Prefix Option is only valid in the Proxy Binding
>    Acknowledgments that are sent from the proxy mobile agent to the home
>    agent in reply to a Proxy Binding Update request.  The home network
>    prefix Option has an alignment requirement of 8n+4.  Its format is as
>    follows:
> 
> 
> 
>        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     |   Length      |   Reserved    | Prefix Length |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |                                                               |
>       +                                                               +
>       |                                                               |
>       +                   Local Network Prefix                        +
>       |                                                               |
>       +                                                               +
>       |                                                               |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

s/Local Network Prefix/Home Network Prefix/

> 5.1.  Extensions to conceptual data structures
> 
>    The home agent maintains a binding cache entry for each currently
>    registered mobile node.  The Binding Cache is a conceptual data
>    structure described in detail in [1].  For supporting this

>    specification, the home agent will continue to create binding cache
>    entries for each mobile station that gets proxy registered by a proxy

s/gets proxy registered/gets registered/

>    mobile agent.  In addition, the home agent may have to add an
>    additional flag to this conceptual data structure indicating that the
>    entry is a proxy registration.  This proxy registration flag may be
>    turned off for all the usual direct registrations.

That last sentence is kind-of implied and can be removed, right?

> 5.2.  Processing a Proxy Binding Update Request
> 
>    After receiving a Proxy Binding Update request from a proxy mobile
>    agent on behalf of a mobile station, the home agent must process the
>    request as defined Section 10, of the base Mobile IPv6 specification
>    [1], with one exception that this request is a proxy request and
>    proper authorization checks have to be enforced.
> 
>    The home agent has to verify the policy to ensure the proxy mobile
>    agent that is sending this request has the right to do so, else it
>    MUST reject the request and send a Proxy Binding Acknowledgment with
>    the proper status code.

The way this is written, only status code 141 applies, maybe it should read:

     "The home agent MUST verify it's policy before accepting a Proxy
      Binding Update request.  If the home agent is not configured to
      accept proxy registrations, it MUST reject the request and send
      a Proxy Binding Acknowledgement with status code 140 (Proxy
      Registration not supported).  Furthermore, if the proxy mobile
      agent sending the request is not authorized, it MUST reject the
      request and send a Proxy Binding Acknowledgement with status code
      141 (Proxy Registration from this proxy mobile agent not allowed)."

> 6.  Proxy Mobile Agent Operation
> 
>    The Proxy Mobile Agent has the following functional roles.  It will
>    emulate the mobile station's home network on the access link, will
>    update the home agent about the current location of the mobile
>    station, will setup data path for enabling the mobile station to use
>    its home address for communication and to some extent the role of the
>    proxy mobile agent is comparable to that of the foreign agent in
>    Mobile IPv4.

That's a really long sentence, maybe it should be 3 bullet points 
followed by "The proxy mobile agent is comparable to that of..."

> 6.2.  Access Authentication and obtaining the profile
> 
>    When the mobile station attaches to a link on the access router
>    running proxy mobile agent, it will present its identity to the
>    network in the form of NAI as part of the access authentication
>    procedure.  The proxy mobile agent should be able fetch the mobile
>    station's profile using the presented NAI.

s/be able fetch/be able to fetch/

> 6.5.  Emulating the Mobile Station's home link
> 
>    The mobile proxy agent on the access link emulates the mobile
>    station's home link behaviour.  It makes the mobile station believe
>    it is on its home link.  The Router Advertisements that the mobile
>    proxy agent sends on the access link will contain the mobile
>    station's home link prefix.  The other parameters in the Router
>    Advertisement with respect to address configuration should be policy
>    driven and may be present in the mobile station's profile.

I guess it's a policy decision on how the RA info is collected, but 
since you define a Home Network Prefix option above, why wasn't that 
contained in the profile?  Alternately, why doesn't the HA just provide 
the RA settings to the PMA?

Also, does it advertise a smaller MTU so that packets the MS sends don't 
need to get fragmented upon tunnel entry?  Or maybe pmtu discovery will 
take care of this?

>    The life cycle of the tunnels should not be based on a single binding
>    entry.  A tunnel may get created due to a single binding entry and
>    later may be shared by many other nodes.  So, the tearing down logic
>    of the tunnel has to be based on the number of visitors over that
>    tunnel.  Implementations are free to pre-establish tunnels between
>    every home agent and every proxy mobile station in the network and
>    with out creating and destroying the tunnels on a need basis.

The last part of this sentence is a little confusing, maybe you can just 
delete everything after "network".


General comment:

You use both Mobile Node and Mobile Station when referring to the same 
system in numerous places, most should be Mobile Station since that 
implies a non-MIPv6-aware node.

-Brian

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



From mip6-bounces@ietf.org Wed Oct 18 17:57:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaJPx-0001UH-Qq; Wed, 18 Oct 2006 17:57:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJ60-0001Ya-F0
	for mip6@ietf.org; Wed, 18 Oct 2006 17:37:04 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaHyR-0008JC-Nx
	for mip6@ietf.org; Wed, 18 Oct 2006 16:25:32 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 18 Oct 2006 22:25:11 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9IKPAce003308; Wed, 18 Oct 2006 22:25:10 +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 k9IKPAmd020785; 
	Wed, 18 Oct 2006 22:25:10 +0200 (MEST)
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Oct 2006 22:25:10 +0200
Received: from cisco.com ([10.32.246.213]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 13:25:09 -0700
Message-ID: <45368DA3.2080401@cisco.com>
Date: Wed, 18 Oct 2006 13:25:07 -0700
From: Sri Gundavelli <sgundave@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.2) Gecko/20030208 Netscape/7
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mohamed Khalil <mkhalil@nortel.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <62B9B0847CC47543B6B3B5E26BD268E60B5F66E3@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Oct 2006 20:25:09.0780 (UTC)
	FILETIME=[81F30540:01C6F2F3]
DKIM-Signature: a=rsa-sha1; q=dns; l=2029; t=1161203111; x=1162067111;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3Dc9K0h9MuAJl/guAyAfS7pM4BVnw=3D;
	b=sndgamOruHeUj4wk9OCdxWlpTPoeZSFHnFjHvc1g/hvLLF+umYoKdhsVAYmvIlJi8qPvkv8q
	0w3ft0bN9EuMBTc7/2tgS0ziuAtn0BZy98s5wXK+UBPLuoXffyrAPAMM;
Authentication-Results: ams-dkim-1; header.From=sgundave@cisco.com; dkim=pass (
	sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Mohamed,

Mohamed Khalil wrote:
 > I believe we should consider the following as tunnel options:
 >
 > 1- tunnel which could be shared between n MTs (n=1..N).
 > 2- we should consider uni-directional tunnel, since it is needed by some
 > new wireless technologies.
 >

I Agree. The tunnel management is very much implementation specific.
The draft took the same stand as well. Thanks for the feedback.

Regards
Sri


> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com] 
> Sent: Wednesday, October 18, 2006 9:35 AM
> To: Jean-Mickael Guerin
> Cc: mip6@ietf.org; Kent Leung (kleung); Sri Gundavelli
> Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
> 
> 
> Jean-Mickael,
> 
> the current PMIPv6 draft is an individual submission.
> we haven't yet decided on whether there will be per-MN
> tunnel between the PMA and the HA or there will be one
> tunnel for all mobile nodes, or both. my personal
> preference is to allow both (I think there are
> deployment scenarios for both).
> 
> its the same with per-MN security association or just
> one security association between the PMA and the HA.
> 
> this will be a WG decision to be made later (once we
> figure out how to standardize PMIPv6).
> 
> Vijay
> 
> Jean-Mickael Guerin wrote:
> 
>>Hello,
>>
>>
>>>Attached is the draft on Proxy Mobile IPv6 that we have posted today.
>>
> 
>>>Please review and comment on this work.
>>
>>My first idea of PMIP6 is an access router using directly MIP6 to 
>>register multiple home addresses, each home address being actually 
>>mobile node's address. Assuming no change on Home agent, and same 
>>prefix sent by PMIP6 to mobiles.
>>
>>But looking at new PBU/PBA messages you introduced, it looks we can't 
>>do this way, could you elaborate ?
>>
>>Regards,
>>
>>Jean-Mickael
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Wed Oct 18 18:02:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaJUa-0004vc-N9; Wed, 18 Oct 2006 18:02:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJ5y-0001bq-Vh
	for mip6@ietf.org; Wed, 18 Oct 2006 17:37:02 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GaHzE-0008BD-40
	for mip6@ietf.org; Wed, 18 Oct 2006 16:26:08 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 18 Oct 2006 13:21:32 -0700
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.20060308/8.12.11) with ESMTP id
	k9IKLVVw005161; Wed, 18 Oct 2006 13:21:31 -0700
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9IKLVAp011450;
	Wed, 18 Oct 2006 13:21:31 -0700 (PDT)
Date: Wed, 18 Oct 2006 13:21:31 -0700 (PDT)
From: Sri Gundavelli <sgundave@cisco.com>
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
In-Reply-To: <4536692F.40606@hp.com>
Message-ID: <Pine.GSO.4.63.0610181311250.15600@irp-view7.cisco.com>
References: <45337CD9.5060500@cisco.com> <4536692F.40606@hp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=9881; t=1161202891; x=1162066891;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DXGn6skthNznVb6BceIKNv9Z4nis=3D;
	b=QnFh+UFprqXrEWQgnr8JoqTjw8VOYbhyWCuDuXdAKNwbANgTjQMHDnNImJH4PR0X2SlHFceN
	BTC92Q0KXOjot+OuThe/L4OLZqfVeHJ6UxoX2sZ6M5XDX04rRqpzchwY;
Authentication-Results: sj-dkim-2.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Brian,

Thanks for the review. Response inline ...
with the note that its still an individual submission...


On Wed, 18 Oct 2006, Brian Haley wrote:

> Hi Sri,
>
> A few comments on the draft inline.
>
>>                             Proxy Mobile IPv6
>>                     draft-sgundave-mipv6-proxymipv6-00
>
>>     Further, the home agent will create a route entry pointing the home
>>     prefix of the mobile agent as reachable over the tunnel to the proxy
>>     mobile agent.  This route is not redistributed in the IGP.  The home
>>     agent will also send a Binding Acknowledgment accepting the binding
>>     update request.  The proxy mobile agent on receiving this Binding
>>     Acknowledgment will create a tunnel pointing to the home agent and
>>     will add a default route over the tunnel to the home agent.  All
>>     traffic from the mobile station that the proxy mobile agent receives
>>     in the role of a default router will route the traffic to the home
>>     agent over the tunnel.
>
> Alexandru also brought-up the "default route" text in this paragraph as an 
> issue, I'd second a request to change per Sri's/Kent's comments. Section 6.4 
> too.
>

Ok. I agree.. we can add some text to be very clear on this.

>>     The mobile station on receiving this Router Advertisement will try to
>>     configure its interface either using stateful or stateless address
>>     configuration modes.  Either way, the mobile station will be able to
>>     obtain its home address for configuring on the interface.
>
> What Router Advertisement? :)  Assuming it's the same from page 3, maybe the 
> simple fix would be to change this to "The mobile station, on receiving a 
> Router Advertisement...", but maybe you should say that after receiving the 
> BAck and setting up the tunnel, the MPA sends out an RA to the MN.
>

You know : ) The line before that should have talked about when the PMA
sends the RA and about the RS it received from the MS.

Sure. We should add some text to be clear.

>>     Packet Routing:
>>
>>     The home agent is the anchor point for the mobile station's home
>>     prefix and thus it will receive all packets sent to the mobile
>>     station's home address/prefix.  The home agent will route all the
>>     received packets over the tunnel to the mobile proxy agent and in
>>     turn will route it on the access link.
>
> s/and in turn/which in turn/
>

my english ! : ) sure. We need to fix the text ..


>>  4.3.  Home Network Prefix Option
>>
>>     A new option, Home Network Prefix Option is defined for using it in
>>     the Binding Acknowledgment sent from the home agent to the proxy
>>     mobile agent.  This option can be used for notifying the assigned
>>     Home network prefix for the mobile station.  The proxy mobile agent
>>     can use this prefix information in Router Advertisements sent to the
>>     mobile station and also in the Address Pool Identifier option in the
>>     DHCP messages sent to the DHCP Server.
>>
>>     The Home Network Prefix Option is only valid in the Proxy Binding
>>     Acknowledgments that are sent from the proxy mobile agent to the home
>>     agent in reply to a Proxy Binding Update request.  The home network
>>     prefix Option has an alignment requirement of 8n+4.  Its format is as
>>     follows:
>>
>>
>>
>>         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     |   Length      |   Reserved    | Prefix Length |
>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> | |
>>        +                                                               +
>> | |
>>        +                   Local Network Prefix                        +
>> | |
>>        +                                                               +
>> | |
>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> s/Local Network Prefix/Home Network Prefix/
>

Ok.

>>  5.1.  Extensions to conceptual data structures
>>
>>     The home agent maintains a binding cache entry for each currently
>>     registered mobile node.  The Binding Cache is a conceptual data
>>     structure described in detail in [1].  For supporting this
>
>>     specification, the home agent will continue to create binding cache
>>     entries for each mobile station that gets proxy registered by a proxy
>
> s/gets proxy registered/gets registered/
>

Ok.

>>     mobile agent.  In addition, the home agent may have to add an
>>     additional flag to this conceptual data structure indicating that the
>>     entry is a proxy registration.  This proxy registration flag may be
>>     turned off for all the usual direct registrations.
>
> That last sentence is kind-of implied and can be removed, right?
>

That's true.


>>  5.2.  Processing a Proxy Binding Update Request
>>
>>     After receiving a Proxy Binding Update request from a proxy mobile
>>     agent on behalf of a mobile station, the home agent must process the
>>     request as defined Section 10, of the base Mobile IPv6 specification
>>     [1], with one exception that this request is a proxy request and
>>     proper authorization checks have to be enforced.
>>
>>     The home agent has to verify the policy to ensure the proxy mobile
>>     agent that is sending this request has the right to do so, else it
>>     MUST reject the request and send a Proxy Binding Acknowledgment with
>>     the proper status code.
>
> The way this is written, only status code 141 applies, maybe it should read:
>
>     "The home agent MUST verify it's policy before accepting a Proxy
>      Binding Update request.  If the home agent is not configured to
>      accept proxy registrations, it MUST reject the request and send
>      a Proxy Binding Acknowledgement with status code 140 (Proxy
>      Registration not supported).  Furthermore, if the proxy mobile
>      agent sending the request is not authorized, it MUST reject the
>      request and send a Proxy Binding Acknowledgement with status code
>      141 (Proxy Registration from this proxy mobile agent not allowed)."
>

Thanks for the text. We can certainly incorporate it in to the doc.


>>  6.  Proxy Mobile Agent Operation
>>
>>     The Proxy Mobile Agent has the following functional roles.  It will
>>     emulate the mobile station's home network on the access link, will
>>     update the home agent about the current location of the mobile
>>     station, will setup data path for enabling the mobile station to use
>>     its home address for communication and to some extent the role of the
>>     proxy mobile agent is comparable to that of the foreign agent in
>>     Mobile IPv4.
>
> That's a really long sentence, maybe it should be 3 bullet points followed by 
> "The proxy mobile agent is comparable to that of..."
>

Ok.


>>  6.2.  Access Authentication and obtaining the profile
>>
>>     When the mobile station attaches to a link on the access router
>>     running proxy mobile agent, it will present its identity to the
>>     network in the form of NAI as part of the access authentication
>>     procedure.  The proxy mobile agent should be able fetch the mobile
>>     station's profile using the presented NAI.
>
> s/be able fetch/be able to fetch/
>

Ok.

>>  6.5.  Emulating the Mobile Station's home link
>>
>>     The mobile proxy agent on the access link emulates the mobile
>>     station's home link behaviour.  It makes the mobile station believe
>>     it is on its home link.  The Router Advertisements that the mobile
>>     proxy agent sends on the access link will contain the mobile
>>     station's home link prefix.  The other parameters in the Router
>>     Advertisement with respect to address configuration should be policy
>>     driven and may be present in the mobile station's profile.
>
> I guess it's a policy decision on how the RA info is collected, but since you 
> define a Home Network Prefix option above, why wasn't that contained in the 
> profile?  Alternately, why doesn't the HA just provide the RA settings to the 
> PMA?
>

This was discussed. Trying to be more flexible, giving the deployments
the option to preconfigure Prefix or the HA address. Agreed.


> Also, does it advertise a smaller MTU so that packets the MS sends don't need 
> to get fragmented upon tunnel entry?  Or maybe pmtu discovery will take care 
> of this?
>
>>     The life cycle of the tunnels should not be based on a single binding
>>     entry.  A tunnel may get created due to a single binding entry and
>>     later may be shared by many other nodes.  So, the tearing down logic
>>     of the tunnel has to be based on the number of visitors over that
>>     tunnel.  Implementations are free to pre-establish tunnels between
>>     every home agent and every proxy mobile station in the network and
>>     with out creating and destroying the tunnels on a need basis.
>
> The last part of this sentence is a little confusing, maybe you can just 
> delete everything after "network".
>

Sure. The doc will require few edits.

>
> General comment:
>
> You use both Mobile Node and Mobile Station when referring to the same system 
> in numerous places, most should be Mobile Station since that implies a 
> non-MIPv6-aware node.
>

We used the term MN, in the context of Client based MIP and MS as a pure
IPv6 host. Some places, its possible we incorrectly used one for the 
other. Thanks for the detailed comments.

Thanks again for the review.

Sri

> -Brian
>
>

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



From mip6-bounces@ietf.org Thu Oct 19 00:42:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaPi5-0002Dh-1l; Thu, 19 Oct 2006 00:40:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaPi4-0002DZ-Mh
	for mip6@ietf.org; Thu, 19 Oct 2006 00:40:48 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaPi3-00011O-8H
	for mip6@ietf.org; Thu, 19 Oct 2006 00:40:48 -0400
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0J7D009528ZT3M@mailout3.samsung.com> for mip6@ietf.org;
	Thu, 19 Oct 2006 13:40:41 +0900 (KST)
Received: from wable ([107.108.72.147])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0J7D007UN8ZS2V@mmp2.samsung.com> for
	mip6@ietf.org; Thu, 19 Oct 2006 13:40:41 +0900 (KST)
Date: Thu, 19 Oct 2006 10:13:21 +0530
From: Ranjitsinh Wable <wable@samsung.com>
To: mip6@ietf.org
Message-id: <0a0601c6f339$1fe785b0$93486c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; reply-type=original; charset=iso-8859-1;
	format=flowed
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <1155336548.19749.316.camel@shrimp> <44DD4D24.8010101@hp.com>
	<1155356515.19749.338.camel@shrimp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Subject: [Mip6] Clarification on sending ICMP error in RFC 3775
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

I  was going through the RFC 3775. Section 9.2 of the RFC says that when
 received packet is erroneous then ipv6 node(CN) should send the ICMP
 packet.  And message has to be sent to the directly to the source of a
 packet. And the Binding cache should not be used for the same.

Section 9.2 RFC 3775.

    The Payload Proto field MUST be IPPROTO_NONE (59 decimal).
    Otherwise, the node MUST discard the message and SHOULD send ICMP
    Parameter Problem, Code 0, directly to the Source Address of the
    packet as specified in RFC 2463 [14].  Thus no Binding Cache
    information is used in sending the ICMP message.  The Pointer
    field in the ICMP message SHOULD point at the Payload Proto field.

Section 10.2 of the RFC says that HA should also follow the same rules
specified in the section 9.2.

I have small question on this. Now lets say that the MN returned home and
sent a BU(De-registration) with palyload proto not equal to 59.
BU packet is sent from the home link. So it will have only IPv6 header and
mobility header and some additional payload header.
IPv6 Source address will be the HoA of the MN. HA will have the valid
Binding cache for the MN.

In the above case HA should send ICMP error message to the MN not using the
binding cache and it should be directly sent to HoA of the MN.
If HA is still intercepting the packets for the MN (as valid binding cache 
is
present), how the ICMP error message will be sent to MN address.

1) Whether the HA should send NS to resolve the HoA of MN? but in this case
HA itself is defending the MN HoA. (This may require special routing)

RFC says(section 11.5.4) it is possible for MN to respond to the NS by
 sending the unicast NA. This case is required for sending the BA to MN by 
HA.
And it is assumed that time the BU for De-registration is accepted.
and HA is no longer serving/ defending the MN HoA.
    OR
2) Whether HA should tunnel the packet without using binding cache?
But in this case packet will be unneccessarily sent to foreign network.
OR
3) HA silently discard the errenous packet?

IMHO Section 9.2 holds good for CN but may not be for HA.
Kindly let me know your views on the same.

Thanks and Regards,

Wable R. U.
















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



From mip6-bounces@ietf.org Thu Oct 19 04:15:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaT2P-0005ef-6z; Thu, 19 Oct 2006 04:14:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaT2O-0005eR-4Y
	for mip6@ietf.org; Thu, 19 Oct 2006 04:14:00 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaT2M-0003ah-La
	for mip6@ietf.org; Thu, 19 Oct 2006 04:14:00 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9J8Dt6r029040 for <mip6@ietf.org>; Thu, 19 Oct 2006 11:13:57 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 11:13:55 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 03:13:52 -0500
Received: from 10.241.58.139 ([10.241.58.139]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 19 Oct 2006 08:13:52 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Thu, 19 Oct 2006 03:10:39 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C15C9D2F.26D18%basavaraj.patil@nokia.com>
Thread-Topic: Draft agenda of MIP6 WG meeting at IETF67
Thread-Index: AcbzVhAhTssKJF9JEdulYgARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 19 Oct 2006 08:13:52.0042 (UTC)
	FILETIME=[833148A0:01C6F356]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [Mip6] Draft agenda of MIP6 WG meeting at IETF67
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Draft agenda:                        Rev 0

MONDAY, November 6, 2006
1300-1500 Afternoon Session I
Harbor Island III

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

1. Agenda review, Blue sheets and volunteers for taking notes and
   Jabber scribe       5 Mins

2. WG status and I-Ds update                5 Mins

3. Mobile IPv6 Operation with IKEv2 and the revised IPsec Architecture
   I-D: draft-ietf-mip6-ikev2-ipsec-06
   Vijay Devarapalli                    15 Mins

4. Experimental and vendor specific messages
   I-D: draft-devarapalli-mip6-vsm-01
   I-D: draft-devarapalli-mip6-experimental-messages-00
   Vijay Devarapalli                    10 Mins

5. Home agent reliability protocol update
   I-D: draft-ietf-mip6-hareliability-00 (revised?)
   Ryuji Wakikawa                     10 Mins

6. Proxy Mobile IPv6 Discussion                30 Mins
   I-D: draft-sgundave-mipv6-proxymipv6-00
   I-D: draft-chowdhury-netmip6-01
   Sri Gundaveli/Kuntal Chowdhury

7. Next steps        Chairs                10 mins

Or at:
http://www3.ietf.org/proceedings/06nov/agenda/mip6.txt


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



From mip6-bounces@ietf.org Thu Oct 19 04:16:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaT4I-00079J-AU; Thu, 19 Oct 2006 04:15:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaT4H-00077a-5y
	for mip6@ietf.org; Thu, 19 Oct 2006 04:15:57 -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 1GaT4F-0003ys-T4
	for mip6@ietf.org; Thu, 19 Oct 2006 04:15:57 -0400
Received: from [10.16.0.164] (unknown [10.16.0.164])
	by proxy.6wind.com (Postfix) with ESMTP id DB4D3525F93;
	Thu, 19 Oct 2006 10:15:54 +0200 (CEST)
Message-ID: <45373425.2040000@6wind.com>
Date: Thu, 19 Oct 2006 10:15:33 +0200
From: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <45337CD9.5060500@cisco.com> <4535D660.4090501@6wind.com>
	<Pine.GSO.4.63.0610180637330.5867@irp-view7.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0610180637330.5867@irp-view7.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


>
> Access router (proxy mobile agent) is the proxy and is the entity
> that is doing the binding update and we call this binding update
> as proxy binding update (PBU). It is indeed using MIP6. Proxy
> Binding Update is the MIP6 BU message with an additional flag
> indicating to the home agent that it is a proxy registration and
> thus the authorization checks have to be bit different.
I can live with "PBU", simply if PBU is just BU with flag P,
 we could keep on naming it "BU", like NEMO spec and its R flag.

Regards,

Jean-Mickael


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



From mip6-bounces@ietf.org Thu Oct 19 04:21:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaT8o-0004l1-Km; Thu, 19 Oct 2006 04:20:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaT8n-0004e2-EB
	for mip6@ietf.org; Thu, 19 Oct 2006 04:20:37 -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 1GaT8m-0004n5-51
	for mip6@ietf.org; Thu, 19 Oct 2006 04:20:37 -0400
Received: from [10.16.0.164] (unknown [10.16.0.164])
	by proxy.6wind.com (Postfix) with ESMTP id 89300525F84;
	Thu, 19 Oct 2006 10:20:35 +0200 (CEST)
Message-ID: <45373548.2060609@6wind.com>
Date: Thu, 19 Oct 2006 10:20:24 +0200
From: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
References: <45337CD9.5060500@cisco.com> <4535D660.4090501@6wind.com>
	<Pine.GSO.4.63.0610180637330.5867@irp-view7.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0610180637330.5867@irp-view7.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


>
> The changes in the home agent are semantical, a tunnel between the
> home agent and the proxy mobile agent, that has no 1:1 relation
> to a mobile station, as the tunnel can now be shared for multiple
> mobiles, as in MIP4. The changes in the home agent are just
> to support these minor extensions.
>
We could compare to NEMO as well - a proxy MIP6 looks close to
a NEMO router able to write MN/128 addresses in place of network
prefixes, and HA (with NEMO support) keeps same semantic.

Regards,

Jean-Mickael


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



From mip6-bounces@ietf.org Thu Oct 19 08:18:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaWox-0003qs-QQ; Thu, 19 Oct 2006 08:16:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaWow-0003oR-J5
	for mip6@ietf.org; Thu, 19 Oct 2006 08:16:22 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaWov-000080-20
	for mip6@ietf.org; Thu, 19 Oct 2006 08:16:22 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-4.cisco.com with ESMTP; 19 Oct 2006 05:16:20 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9JCGKRm031927; Thu, 19 Oct 2006 05:16:20 -0700
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9JCGBOW024928;
	Thu, 19 Oct 2006 05:16:15 -0700 (PDT)
Date: Thu, 19 Oct 2006 05:16:11 -0700 (PDT)
From: Sri Gundavelli <sgundave@cisco.com>
To: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
Subject: Re: [Mip6] Proxy Mobile IPv6 - I-D Submission
In-Reply-To: <45373425.2040000@6wind.com>
Message-ID: <Pine.GSO.4.63.0610190515040.28072@irp-view7.cisco.com>
References: <45337CD9.5060500@cisco.com> <4535D660.4090501@6wind.com>
	<Pine.GSO.4.63.0610180637330.5867@irp-view7.cisco.com>
	<45373425.2040000@6wind.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=720; t=1161260180; x=1162124180;
	c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20Proxy=20Mobile=20IPv6=20-=20I-D=20Submission; 
	X=v=3Dcisco.com=3B=20h=3DXGn6skthNznVb6BceIKNv9Z4nis=3D;
	b=YHXMLHrD49w5LX9yHhnk95T0+sL4+9/JWDz/7Pe+9IY4mSfgEmzmJ4S2YNfs0oOvhJF/SGK6
	P/9ZqrzR4eXNrzqRm5HmNCNveYKPtyRjChB+GSkPIDUJfOW/M0CGxGWk;
Authentication-Results: sj-dkim-7.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6@ietf.org, "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



On Thu, 19 Oct 2006, Jean-Mickael Guerin wrote:

>
>>
>>  Access router (proxy mobile agent) is the proxy and is the entity
>>  that is doing the binding update and we call this binding update
>>  as proxy binding update (PBU). It is indeed using MIP6. Proxy
>>  Binding Update is the MIP6 BU message with an additional flag
>>  indicating to the home agent that it is a proxy registration and
>>  thus the authorization checks have to be bit different.
> I can live with "PBU", simply if PBU is just BU with flag P,
> we could keep on naming it "BU", like NEMO spec and its R flag.

Sure. The "R" flag for the NEMO support is a good example.

Thanks
Sri


>
> Regards,
>
> Jean-Mickael
>
>

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



From mip6-bounces@ietf.org Thu Oct 19 10:23:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaYlz-0000vN-DC; Thu, 19 Oct 2006 10:21:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaYly-0000vE-9V; Thu, 19 Oct 2006 10:21:26 -0400
Received: from outbound-cpk.frontbridge.com ([207.46.163.16]
	helo=outbound2-cpk-R.bigfish.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GaYli-0006bO-IK; Thu, 19 Oct 2006 10:21:26 -0400
Received: from outbound2-cpk.bigfish.com (localhost.localdomain [127.0.0.1])
	by outbound2-cpk-R.bigfish.com (Postfix) with ESMTP id 060168C6DF4;
	Thu, 19 Oct 2006 14:21:10 +0000 (UTC)
Received: from mail143-cpk-R.bigfish.com (unknown [192.168.21.3])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by outbound2-cpk.bigfish.com (Postfix) with ESMTP id EF13F8BF6E2;
	Thu, 19 Oct 2006 14:21:09 +0000 (UTC)
Received: from mail143-cpk.bigfish.com (localhost.localdomain [127.0.0.1])
	by mail143-cpk-R.bigfish.com (Postfix) with ESMTP id D0D885593B5;
	Thu, 19 Oct 2006 14:21:09 +0000 (UTC)
X-BigFish: V
Received: by mail143-cpk (MessageSwitch) id 1161267613618636_30517;
	Thu, 19 Oct 2006 14:20:13 +0000 (UCT)
Received: from smtpgw6.it.sprintspectrum.com (smtpgw6.sprintspectrum.com
	[207.40.188.14])
	by mail143-cpk.bigfish.com (Postfix) with ESMTP id E28D4557AC7;
	Thu, 19 Oct 2006 14:19:45 +0000 (UTC)
Received: from mailhost.sprintspectrum.com (smtpgw8.it.sprintspectrum.com
	[207.40.65.56])
	by smtpgw6.it.sprintspectrum.com (8.12.11.Beta0/8.12.8) with ESMTP id
	k9JEJPGq029765; Thu, 19 Oct 2006 09:19:25 -0500 (CDT)
Received: from pdawg05a.ad.sprint.com (PDAWG05A.corp.sprint.com [10.122.2.38])
	by mailhost.sprintspectrum.com (Switch-3.2.5/Switch-3.2.5) with
	ESMTP id k9JEJOQX011022; Thu, 19 Oct 2006 09:19:24 -0500 (CDT)
Received: from PLSWB09C.ad.sprint.com ([208.10.70.239]) by
	pdawg05a.ad.sprint.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 09:19:24 -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] RE: [netlmm] Network-based mobility - NETLMM DTSolutionVsA
	solutionbased on MIP6 
Date: Thu, 19 Oct 2006 09:19:20 -0500
Message-ID: <F17E4C92F3397E409CCE96C2F16EC7E009E3B0FD@PLSWB09C.ad.sprint.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: [netlmm] Network-based mobility - NETLMM
	DTSolutionVsA solutionbased on MIP6 
Thread-Index: AcbpwAp7HRPzyaoPTA6JNQjWM+QniADlMI0gABJ/p7AAIZK1AAEKBePAAACDNzAAAOziUABMeMsQ
From: "Zhang, Qiang [NTK]" <Qiang.Zhang@sprint.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Kent Leung \(kleung\)" <kleung@cisco.com>
X-OriginalArrivalTime: 19 Oct 2006 14:19:24.0803 (UTC)
	FILETIME=[94230530:01C6F389]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mip6@ietf.org, netlmm@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



The PMIP6 approach seems to fit both the "global" and "localized" =
mobility management concepts depending on the usage models, e.g. it =
supports either intra or inter access network roaming given proper AAA =
brokerage infrastructure. Given two DTs are defining the similar PMIP AR =
signaling and routing and the netlmm and MIP6 are not really mutually =
exclusive, I guess this addresses a overlap portion of the design, a =
reasonable compromise may be to define this in one of the WGs and cross =
reference or extend it to fit into the other



-----Original Message-----
From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
Sent: Tuesday, October 17, 2006 9:39 PM
To: Kent Leung (kleung)
Cc: mip6@ietf.org; netlmm@ietf.org
Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM =
DTSolutionVsA solutionbased on MIP6=20

Hi Kent,

See inline....

-Kuntal

> -----Original Message-----
> From: Kent Leung (kleung) [mailto:kleung@cisco.com]
> Sent: Tuesday, October 17, 2006 7:53 PM
> To: Chowdhury, Kuntal
> Cc: mip6@ietf.org; netlmm@ietf.org
> Subject: RE: [Mip6] RE: [netlmm] Network-based mobility - NETLMM DT=20
> SolutionVsA solutionbased on MIP6
>=20
> Hi Kuntal.
> <snip>
> >
> > Some SDOs have adopted PMIPv4 but not for localized MM within the
> access
> > network (which is the scope of NetLMM).
> >
> [KC>] PMIP (4 and 6) is used for network based mobility management for =

> simple IP sessions. Whether the scope is NOT localized is a subjective =

> discussion.
>=20
> KL> An objective way to look at it is from the reference interface
> perspective.
>=20
[KC>] If the discussion gets too SDO specific (which I believe is going =
to happen), I would suggest we take this offline. MIP4 is used for =
inter-RNC mobility management in the radio access network in an SDO.
What do you call that? NOT global mobility I guess :-)

>=20
> > I think we should clarify the difference between non-MIPv6 mobility=20
> > option re-use vs. re-usable MIPv6 Home Agent.  Maybe this is
something
>=20
> > the PMIPv6 camp should sort out first? ;)
>=20
> [KC>] Aren't you also in that camp now? Ref, your newly revived I-D on =

> pmip6. So, why don't you answer your own question?
>=20
> KL> The answer is in the draft. :)  Do you have an opinion?
>=20
[KC>] You can get a hint of my opinion in the I-D that we (Ajoy and I) =
submitted. FYI...we have an I-D on pmip6 (aka netmip6) which we are =
pursing all along w/o shifting position. The I-D is :
http://www.ietf.org/internet-drafts/draft-chowdhury-netmip6-01.txt

We do not propose non-MIP6 MO for *mobility management* in this I-D. The =
essence of pmip6 is the compatibility with mip6. Maximum reuse of mip6 =
MO should be the guideline and re-inventing the wheel for the heck of it =
should be avoided. So, the approach that introduces NEW MO for pmip6 =
seems to defeat the very purpose i.e. reuse mip6 protocol for proxy mip6 =
operation, IMHO.

=20
> Kent

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



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



From mip6-bounces@ietf.org Thu Oct 19 12:20:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gaabw-0002Ld-I2; Thu, 19 Oct 2006 12:19:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gaabv-0002Hf-Ai
	for mip6@ietf.org; Thu, 19 Oct 2006 12:19:11 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gaabm-0001Gr-BN
	for mip6@ietf.org; Thu, 19 Oct 2006 12:19:11 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9JGJ0LK014454
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Thu, 19 Oct 2006 09:19:01 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9JGFuhN015785
	for <mip6@ietf.org>; Thu, 19 Oct 2006 09:18:59 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 09:18:41 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 09:18:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Thu, 19 Oct 2006 09:18:38 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A8DB@NAEX14.na.qualcomm.com>
In-Reply-To: <D4AE20519DDD544A98B3AE9235C8A4C221AF0F@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAABwFpABQRjqkA==
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 19 Oct 2006 16:18:41.0799 (UTC)
	FILETIME=[3E09F170:01C6F39A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,=20

This issue was revived mainly due to Vijay points on the need for the
checksum option when the alt-CoA is not used. Let me summarise the
issues first then propose a way forward.=20

Summary:
--------

The initial resolution for the issue suggested that we add a checksum
option that includes a checksum on the src and dst addresses in the IPv6
header. This was suggested to be used when the alt-coa is not present to
maintain the integrity of the src address when ESP is used. I want to
emphasise that this is only needed when ESP is used, not with AH.=20

Now the point that Vijay raised is also quite valid: With NAT traversal,
the outer IPv4 header is vulnerable, yet it is needed because the HA
responds to that address and sets up the UDP tunnel to the outer
(natted) IPv4 src address in the packet containing the BU. There is no
way we can secure that address, yet, it essentially acts as another
binding, which if modified maliciously, would redirect the MN's packets
to another IPv4 address. To be clear, here is the packet format:
BU packet received by HA after passing through NAT:
  IPv4 HDR (src=3Dnatted-v4, dst=3DHA-addr)
       UDP
         IPv6 HDR (src=3Dv4-mapped-v6, dst=3DHA-addr)
          ESP
          DST-OPT
          MH (BU)

The HA responds with a similar packet including the BA and forwards all
future packets in the UDP tunnel, with the dst address in the IPv4
header being the "natted-v4" address above.=20
So essentially protecting the BU does not protect the MN from
redirection attacks in this case because the IPv4 header is vulnerable.
This is an inherent problem with NAT traversal. There is practically
nothing we can do about it.=20

So the remaining question is: Is it worth worrying about the integrity
of the BU in this case? IMHO I think the answer is yes. Why? Two main
reasons:

1. There can be cases where the BU is sent to a local HA and the
operator can guarantee that no NATs are in the path. In this case we
would lose integrity for no reason, i.e. the BU becomes the weakest
link. This is not unusual really because an operator may decide that it
will only provide the HA function within its domain, which happens to
not include NATs between the MN and the HA.=20

2. We have precedence with MIPv4 and NAT traversal where the RREQ is
still secure despite the UNSAF NAT traversal.=20
=20
Note that the answer to 1) above may be "Use AH", but I prefer to not
force that on implementations that do not do it today (although I would
personally prefer AH in general for the BU).

For these reasons, and there may be more, I prefer to not take this big
decision to lose the integrity for the BU.=20

Way forward:
------------

This issue is now closed, we all agree on it, but there may be
disagreement on the checksum part. So I suggest that I generate a new
issue for this discussion. Until the new issue is resolved, I won't add
the checksum option to the draft.=20

Feel free to send comments.=20

Hesham=20

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



From mip6-bounces@ietf.org Thu Oct 19 15:15:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GadKN-0005U9-SE; Thu, 19 Oct 2006 15:13:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GadKM-0005Tt-Vi
	for mip6@ietf.org; Thu, 19 Oct 2006 15:13:14 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GadKL-0001ua-Ls
	for mip6@ietf.org; Thu, 19 Oct 2006 15:13:14 -0400
Received: from [10.1.201.21] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 12:13:09 -0700
Message-ID: <4537CD92.4010706@azairenet.com>
Date: Thu, 19 Oct 2006 12:10:10 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A24A8DB@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A8DB@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Oct 2006 19:13:09.0614 (UTC)
	FILETIME=[9D57C0E0:01C6F3B2]
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

Soliman, Hesham wrote:

> This is an inherent problem with NAT traversal. There is practically
> nothing we can do about it. 

right.

> So the remaining question is: Is it worth worrying about the integrity
> of the BU in this case? IMHO I think the answer is yes. Why? Two main
> reasons:
> 
> 1. There can be cases where the BU is sent to a local HA and the
> operator can guarantee that no NATs are in the path. In this case we
> would lose integrity for no reason, i.e. the BU becomes the weakest
> link. This is not unusual really because an operator may decide that it
> will only provide the HA function within its domain, which happens to
> not include NATs between the MN and the HA. 

if there is no NAT on the path, the use of alt-CoA
gives automatic integrity protection for the CoA.
so its best to use the alt-CoA option all the time
(which is what RFC 3775 says anyway).

the original suggestion was to relax the "MUST"
in RFC 3775 which says the HA should always use the
CoA in the alt-CoA option. not to relax the
MN requirement to include the alt-CoA option when
ESP is used.

Vijay

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



From mip6-bounces@ietf.org Thu Oct 19 16:03:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gae61-0006pm-KL; Thu, 19 Oct 2006 16:02:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gae5y-0006kK-Ji; Thu, 19 Oct 2006 16:02:26 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gae5x-0000Cx-2l; Thu, 19 Oct 2006 16:02:26 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7E007NQFIT3D@usaga01-in.huawei.com>; Thu,
	19 Oct 2006 12:59:18 -0700 (PDT)
Received: from huawei6cc10c70
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J7E0007RFIPRQ@usaga01-in.huawei.com>; Thu,
	19 Oct 2006 12:59:17 -0700 (PDT)
Date: Thu, 19 Oct 2006 13:02:19 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
In-reply-to: <452E862E.7010809@azairenet.com>
To: 'Vijay Devarapalli' <vijay.devarapalli@azairenet.com>,
	'Hannes Tschofenig' <Hannes.Tschofenig@gmx.net>
Message-id: <001501c6f3b9$7be40c00$2f01a8c0@huawei6cc10c70>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcbuLV5RCJ2MDyrDTKO2btQNWvJufwFiWlSw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: mip6@ietf.org, dime@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 would agree with Vijay as well. But, we need to see if we have the process
in place for this to happen and what the consequences for inserting that
process is. 

These specs are being produced addressing the set of requirements in HA-AAAH
document (not sure if other requirement docs are in place).

The way I understand it that requirement documents were not written to
address the 4285 requirements specifically. 

If my understanding incorrect and people think the requirement docs include
4285-related requirements, then, that is fine and hopefully the specs will
address most of the 4285 needs (except possibly some AVPs that may be added
later) either initially or through revisions.

However, if my understanding is correct and the requirements docs do not
include 4285 requirements, why would we expect the design specs will
automatically? 

Does the group feel it want to spend time issuing a set of requirements to
meet 4285 needs and then design accordingly? If not, then I think we should
just accept that the outcoming specs simply MAY support 4285. I am sure the
two WGs do not appreciate this issue being raised two years down the road.

What I am missing here?

R,

Madjid

-----Original Message-----
From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com] 
Sent: Thursday, October 12, 2006 11:15 AM
To: Hannes Tschofenig
Cc: mip6@ietf.org; dime@ietf.org
Subject: [Mip6] Re: [Dime] Impact of RFC 4285 for Diameter MIP6
Bootstrapping Work

looks like nobody replied to this email. :)

Hannes Tschofenig wrote:
> Hi all,
> 
> in the DIME working group we are currently producing documents that 
> relate to the backend solution of the
> 
> * Integrated Scenario
>   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> 
> * Split Scenario
>   draft-ietf-mip6-bootstrapping-split-02
> 
> Now, the question came up whether we have to consider RFC 4285 
> ('Authentication Protocol for Mobile IPv6') for our work as well.

currently it is not clear if we are going to do any
further work on RFC 4285 in the MIP6 WG. so my
suggestion is to assume only the use of IKEv2 (with
and without EAP).

but it would be good to keep the solution flexible
so that it can be extended later for 4285 if required.

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 Oct 19 16:05:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gae80-0000dE-Hf; Thu, 19 Oct 2006 16:04:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gae7g-000081-MT; Thu, 19 Oct 2006 16:04:12 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gae7d-0000zi-Ka; Thu, 19 Oct 2006 16:04:12 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7E0070HFLQ3D@usaga01-in.huawei.com>; Thu,
	19 Oct 2006 13:01:03 -0700 (PDT)
Received: from huawei6cc10c70
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J7E006PHFLM0D@usaga01-in.huawei.com>; Thu,
	19 Oct 2006 13:01:02 -0700 (PDT)
Date: Thu, 19 Oct 2006 13:04:04 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
In-reply-to: <eaa74a7e0610130036r75db5182ta4549ebcb4d26e97@mail.gmail.com>
To: 'Gerardo Giaretta' <gerardo.giaretta@gmail.com>,
	'Vijay Devarapalli' <vijay.devarapalli@azairenet.com>
Message-id: <001601c6f3b9$bab56ff0$2f01a8c0@huawei6cc10c70>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acbumw6p3zT0zAqJTneSA123Ge3v5wFHn+Cw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: mip6@ietf.org, dime@ietf.org
Subject: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Ok, so I see I spend a long email without reading the rest of the thread. 
Do we feel the AAA goal draft efficiently captures the 4285 requirements?
If yes, sorry for clogging your mailboxes..

R,

Madjid

-----Original Message-----
From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com] 
Sent: Friday, October 13, 2006 12:37 AM
To: Vijay Devarapalli
Cc: mip6@ietf.org; dime@ietf.org
Subject: Re: [Dime] Impact of RFC 4285 for Diameter MIP6 Bootstrapping Work

> > in the DIME working group we are currently producing documents that
> > relate to the backend solution of the
> >
> > * Integrated Scenario
> >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> >
> > * Split Scenario
> >   draft-ietf-mip6-bootstrapping-split-02
> >
> > Now, the question came up whether we have to consider RFC 4285
> > ('Authentication Protocol for Mobile IPv6') for our work as well.
>
> currently it is not clear if we are going to do any
> further work on RFC 4285 in the MIP6 WG. so my
> suggestion is to assume only the use of IKEv2 (with
> and without EAP).
>

Agree with Vijay, this is also the assumption for the AAA goals draft.

--Gerardo

> but it would be good to keep the solution flexible
> so that it can be extended later for 4285 if required.
>
> Vijay
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
>

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



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



From mip6-bounces@ietf.org Thu Oct 19 16:34:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaeZa-0000xV-NR; Thu, 19 Oct 2006 16:33:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaeZY-0000v5-H5; Thu, 19 Oct 2006 16:33:00 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GaeZO-0005We-K6; Thu, 19 Oct 2006 16:33:00 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id k9JKWeeG020052;
	Fri, 20 Oct 2006 05:32:40 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id k9JKWepU001656;
	Fri, 20 Oct 2006 05:32:40 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id FAA01655;
	Fri, 20 Oct 2006 05:32:40 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id k9JKWd00019452;
	Fri, 20 Oct 2006 05:32:39 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id k9JKWdod007994;
	Fri, 20 Oct 2006 05:32:39 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0J7E00FZ1H29EQK0@mail.po.toshiba.co.jp>; Fri,
	20 Oct 2006 05:32:38 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1GaeZ6-0000LK-NX; Thu,
	19 Oct 2006 13:32:32 -0700
Date: Thu, 19 Oct 2006 16:32:32 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
In-reply-to: <001601c6f3b9$bab56ff0$2f01a8c0@huawei6cc10c70>
To: Madjid Nakhjiri <mnakhjiri@huawei.com>
Message-id: <20061019203232.GF30464@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <eaa74a7e0610130036r75db5182ta4549ebcb4d26e97@mail.gmail.com>
	<001601c6f3b9$bab56ff0$2f01a8c0@huawei6cc10c70>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: mip6@ietf.org, dime@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

Madjid,

On Thu, Oct 19, 2006 at 01:04:04PM -0700, Madjid Nakhjiri wrote:
> Ok, so I see I spend a long email without reading the rest of the thread. 
> Do we feel the AAA goal draft efficiently captures the 4285 requirements?
> If yes, sorry for clogging your mailboxes..

That is my feeling and is why I had the following comment on aaa-ha-goals draft:

"
  YO: This document seems to assume the use of IPsec between MN and HA
  for securing Mobile IPv6 signaling.  But the AAA interface could
  also be used for RFC 4285.  So I think it might be good to mention
  in this section that the document may not preclude the use of
  alternative methods for securing Mobile IPv6 signaling between MN
  and HA while this document focuses on the use of IPsec between MN
  and HA.
"

Yoshihiro Ohba


> 
> R,
> 
> Madjid
> 
> -----Original Message-----
> From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com] 
> Sent: Friday, October 13, 2006 12:37 AM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org; dime@ietf.org
> Subject: Re: [Dime] Impact of RFC 4285 for Diameter MIP6 Bootstrapping Work
> 
> > > in the DIME working group we are currently producing documents that
> > > relate to the backend solution of the
> > >
> > > * Integrated Scenario
> > >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> > >
> > > * Split Scenario
> > >   draft-ietf-mip6-bootstrapping-split-02
> > >
> > > Now, the question came up whether we have to consider RFC 4285
> > > ('Authentication Protocol for Mobile IPv6') for our work as well.
> >
> > currently it is not clear if we are going to do any
> > further work on RFC 4285 in the MIP6 WG. so my
> > suggestion is to assume only the use of IKEv2 (with
> > and without EAP).
> >
> 
> Agree with Vijay, this is also the assumption for the AAA goals draft.
> 
> --Gerardo
> 
> > but it would be good to keep the solution flexible
> > so that it can be extended later for 4285 if required.
> >
> > Vijay
> >
> > _______________________________________________
> > DiME mailing list
> > DiME@ietf.org
> > https://www1.ietf.org/mailman/listinfo/dime
> >
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 

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



From mip6-bounces@ietf.org Thu Oct 19 16:48:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaenH-0005ro-RV; Thu, 19 Oct 2006 16:47:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaenH-0005rI-Cp
	for mip6@ietf.org; Thu, 19 Oct 2006 16:47:11 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaenC-0007od-3M
	for mip6@ietf.org; Thu, 19 Oct 2006 16:47:11 -0400
Received: from [10.1.201.21] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 13:47:03 -0700
Message-ID: <4537E38F.1070705@azairenet.com>
Date: Thu, 19 Oct 2006 13:43:59 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A24A8DB@NAEX14.na.qualcomm.com>
	<4537CD92.4010706@azairenet.com>
In-Reply-To: <4537CD92.4010706@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Oct 2006 20:47:03.0879 (UTC)
	FILETIME=[BBA05D70:01C6F3BF]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
> Soliman, Hesham wrote:
> 
>> This is an inherent problem with NAT traversal. There is practically
>> nothing we can do about it. 
> 
> right.
> 
>> So the remaining question is: Is it worth worrying about the integrity
>> of the BU in this case? IMHO I think the answer is yes. Why? Two main
>> reasons:
>>
>> 1. There can be cases where the BU is sent to a local HA and the
>> operator can guarantee that no NATs are in the path. In this case we
>> would lose integrity for no reason, i.e. the BU becomes the weakest
>> link. This is not unusual really because an operator may decide that it
>> will only provide the HA function within its domain, which happens to
>> not include NATs between the MN and the HA. 
> 
> if there is no NAT on the path, the use of alt-CoA
> gives automatic integrity protection for the CoA.
> so its best to use the alt-CoA option all the time
> (which is what RFC 3775 says anyway).
> 
> the original suggestion was to relax the "MUST"
> in RFC 3775 which says the HA should always use the
> CoA in the alt-CoA option. not to relax the
> MN requirement to include the alt-CoA option when
> ESP is used.

I should have said "... when ESP in transport mode is used". :)

Vijay

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



From mip6-bounces@ietf.org Thu Oct 19 17:16:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GafEZ-0001sQ-Mi; Thu, 19 Oct 2006 17:15:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GafEY-0001of-9T; Thu, 19 Oct 2006 17:15:22 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GafEV-0003lY-UD; Thu, 19 Oct 2006 17:15:22 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7E007N6IWD3D@usaga01-in.huawei.com>; Thu,
	19 Oct 2006 14:12:13 -0700 (PDT)
Received: from huawei6cc10c70
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J7E000SIIW8CJ@usaga01-in.huawei.com>; Thu,
	19 Oct 2006 14:12:13 -0700 (PDT)
Date: Thu, 19 Oct 2006 14:15:14 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
In-reply-to: <20061019203232.GF30464@steelhead>
To: 'Yoshihiro Ohba' <yohba@tari.toshiba.com>
Message-id: <002f01c6f3c3$aba66960$2f01a8c0@huawei6cc10c70>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcbzvlwH1HPrrrslT/+MNONAfYCxEQAA1Jwg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: mip6@ietf.org, dime@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 Yoshi,

I agree, no point on insisting that solutions would support 4285, if 4285
requirements are not included. I can think of aspects of 4285 that can be
problematic, but won't mention them now, since I don't want to be accused of
opening the pandora's box while aaa-ha-goals is going through last call or
the dime docs are underway :) 

We should not make claims we cannot back up later as that might derail the
standardization process two years from now. As Persians say (after a lousy
marketing translation) "A small quarrel in the beginning better than a
bloody peace at the end"



R,

Madjid


-----Original Message-----
From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com] 
Sent: Thursday, October 19, 2006 1:33 PM
To: Madjid Nakhjiri
Cc: 'Gerardo Giaretta'; 'Vijay Devarapalli'; mip6@ietf.org; dime@ietf.org
Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
Bootstrapping Work

Madjid,

On Thu, Oct 19, 2006 at 01:04:04PM -0700, Madjid Nakhjiri wrote:
> Ok, so I see I spend a long email without reading the rest of the thread. 
> Do we feel the AAA goal draft efficiently captures the 4285 requirements?
> If yes, sorry for clogging your mailboxes..

That is my feeling and is why I had the following comment on aaa-ha-goals
draft:

"
  YO: This document seems to assume the use of IPsec between MN and HA
  for securing Mobile IPv6 signaling.  But the AAA interface could
  also be used for RFC 4285.  So I think it might be good to mention
  in this section that the document may not preclude the use of
  alternative methods for securing Mobile IPv6 signaling between MN
  and HA while this document focuses on the use of IPsec between MN
  and HA.
"

Yoshihiro Ohba


> 
> R,
> 
> Madjid
> 
> -----Original Message-----
> From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com] 
> Sent: Friday, October 13, 2006 12:37 AM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org; dime@ietf.org
> Subject: Re: [Dime] Impact of RFC 4285 for Diameter MIP6 Bootstrapping
Work
> 
> > > in the DIME working group we are currently producing documents that
> > > relate to the backend solution of the
> > >
> > > * Integrated Scenario
> > >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> > >
> > > * Split Scenario
> > >   draft-ietf-mip6-bootstrapping-split-02
> > >
> > > Now, the question came up whether we have to consider RFC 4285
> > > ('Authentication Protocol for Mobile IPv6') for our work as well.
> >
> > currently it is not clear if we are going to do any
> > further work on RFC 4285 in the MIP6 WG. so my
> > suggestion is to assume only the use of IKEv2 (with
> > and without EAP).
> >
> 
> Agree with Vijay, this is also the assumption for the AAA goals draft.
> 
> --Gerardo
> 
> > but it would be good to keep the solution flexible
> > so that it can be extended later for 4285 if required.
> >
> > Vijay
> >
> > _______________________________________________
> > DiME mailing list
> > DiME@ietf.org
> > https://www1.ietf.org/mailman/listinfo/dime
> >
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 



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



From mip6-bounces@ietf.org Thu Oct 19 21:47:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GajSW-0000AZ-A9; Thu, 19 Oct 2006 21:46:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GajSU-0000AQ-US
	for mip6@ietf.org; Thu, 19 Oct 2006 21:46:02 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GajSS-0000Jb-Le
	for mip6@ietf.org; Thu, 19 Oct 2006 21:46:02 -0400
Received: from wee.isi.edu (wee.isi.edu [128.9.168.112])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9K1jLLc012712
	for <mip6@ietf.org>; Thu, 19 Oct 2006 18:45:21 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Thu, 19 Oct 2006 18:45:20 -0700
Message-Id: <1161308720.5170.41.camel@wee.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k9K1jLLc012712
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 4d9aaf4f837d0910b987cb9188300fdd
Subject: [Mip6] ACM SenSys'06 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

Our apologies if you have received multiple copies.

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

Cut off date for early registration is *October 30, 2006*:

  http://www.regonline.com/Checkin.asp?EventId=3D97157

Conference Hotels:

  Rooms at the Boulderado are still available.

  http://www.boulderado.com/

  Rate: $129/night (Group code: ACM)

  Bus service will pick up at the offical SenSys hotels.

---------------
ACM SenSys 2006 - Call for Participation

The 4th ACM Conference on Embedded Networked Sensor Systems

http://sensys.acm.org/2006/

Boulder, Colorado, USA
October 31 - November 3, 2006

In the short period since its inception in Los Angeles in 2003,
SenSys has risen to become the leading
forum for reporting on new, exciting, and technically important
research in the field of sensor networks.

Please note that the cut off dates for the conference hotels and
early registration are September 29 and October 30, respectively.

This year we have a stellar conference for you that includes:

* A keynote by David Carlson
   Director, International Polar Year Program Office, and formally,
   Director of the Atmospheric Technology Division of the US National
   Centre for Atmospheric Research (NCAR).

* 24 technical papers

* 29 Sensor network demos

* 19 Posters - representing early results and work-in-progress

* 2 one day workshops on emerging and important new topics in sensor
   networks. The workshops will be held the day prior to the main
   technical program

   + First Workshop on World-Sensor-Web: Mobile Device Centric Sensory
     Networks and Applications
     http://www.sensorplanet.org/wsw2006/

   + First Workshop on Distributed Smart Cameras
     http://www.iti.tugraz.at/dsc06/

Registration is now open:

http://www.regonline.com/Checkin.asp?EventId=3D97157

Important Dates:

Cut off date for reduced hotel rates is *September 29, 2006*

Cut off date for early registration is *October 30, 2006*

Please book and register today to guarantee the best rates.

One behalf of the whole organizing team we very much look forward to
seeing you at SenSys in Boulder!

Best regards,

Andrew T. Campbell
SenSys 2006 General Chair

Thanks to our sponsors:

ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS, SIGBED

NSF, NCAR, ISTS, Crossbow, Intel, Microsoft Research, Moteiv, Nokia

Below you'll find the technical program. Please go to
http://sensys.acm.org/2006/ for more information.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
**Technical Program, Demos, and Posters**
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Wednesday, November 1

08:15-08:30 Opening announcements

08:30-10:00 Keynote

David Carlson
Director, International Polar Year Program Office

10:00-10:30 Break

10:30-12:00 Operating Systems

t-kernel: Providing Reliable OS Support to Wireless Sensor Networks
Lin Gu, John A. Stankovic (University of Virginia)

Run-time Dynamic Linking for Reprogramming Wireless Sensor Networks
Adam Dunkels, Niclas Finne, Joakim Eriksson, Thiemo Voigt (Swedish
Institute of Computer Science)

Protothreads: Simplifying Event-Driven Programming of Memory-
Constrained Embedded Systems
Adam Dunkels, Oliver Schmidt, Thiemo Voigt (Swedish Institute of
Computer Science), Muneeb Ali (TU Delft)

12:00-13:30 Lunch

13:30-14:30 Sensing

Capturing High-Frequency Phenomena Using a Bandwidth-Limited Sensor
Network
Ben Greenstein, Christopher Mar, Alex Pesterev, Shahin Farshchi,
Eddie Kohler, Jack Judy, Deborah Estrin (UCLA)

Virtual High-resolution for Sensor Networks
Aman Kansal, William J. Kaiser, Gregory J. Pottie, Mani B. Srivastava
(UCLA) and Gaurav Sukhatme (USC)

14:30-15:00 Break

15:00 -16:30 Routing and Dissemination

RBP: Robust Broadcast Propagation in Wireless Networks
Fred Stann (Amgen), John Heidemann, Rajesh Shroff, Muhammad Zaki
Murtaza (USC/ISI)

Interest Dissemination with Directional Antenna for Wireless Sensor
Networks with Mobile Sinks
Yihong Wu, Xiaobo Chen, Lin Zhang, Zhisheng Niu (Tsinghua University)

Lazy Cross-Link Removal for Geographic Routing
Young-Jin Kim, Ramesh Govindan (USC), Brad Karp (University Colledge
London), Scott Shenker (UCB)

18:30-22:30 Banquet at the Walnut Brewery Boulder's Original Brew Pub
1123 Walnut Street

Thursday, November 2

09:00-10:00 Configuration

StarDust: A Flexible Architecture for Passive Localization in
Wireless Sensor Networks
Radu Stoleru, Pascal Vicaire, Tian He, John A. Stankovic (University
of Virginia)

The Design and Implementation of a Self-Calibrating Distributed
Acoustic Sensing Platform
Lewis Girod (MIT/CSAIL), Martin Lukac, Vlad Trifa, Deborah Estrin (UCLA)

10:00-10:30 Break

10:30-11:30 In-network Processing

Target Tracking with Binary Proximity Sensors: Fundamental Limits,
Minimal Descriptions, and Algorithms
Nisheeth Shrivastava, Raghuraman Mudumbai, Upamanyu Madhow, Subhash
Suri (UCSB)

Data Compression Algorithms for Energy-Constrained Devices in Delay
Tolerant Networks
Christopher M. Sadler, Margaret Martonosi (Princeton University)

11:30-13:00 Lunch

13:00-14:30 Radio Propagation and Transport

Datalink Streaming in Wireless Sensor Networks
Raghu K. Ganti, Praveen Jayachandran, Tarek F. Abdelzaher, and Haiyun
Luo (UIUC)

ATPC: Adaptive Transmission Power Control for Wireless Sensor
Shan Lin (University of Virginia), Tian He (University of Minnesota),
Jingbin Zhang, Gang Zhou, Lin Gu, John A. Stankovic (University of
Virginia)

Experimental Study of Concurrent Transmission in Wireless Sensor
Networks
Dongjin Son, Bhaskar Krishnamachari (USC), John Heidemann (USC/ISI)

14:30-15:00 Break

15:00-16:30 Storage and Abstractions

Abstractions for Safe Concurrent Programming in Networked Embedded
Systems
William P. McCartney, Nigamanth Sridhar (Cleveland State University)

Scalable Data Aggregation for Dynamic Events in Sensor Networks
Kai-Wei Fan, Sha Liu, Prasun Sinha (The Ohio State University)

An Energy-Optimized Object Storage System for Memory-Constrained
Sensor Devices
Gaurav Mathur, Peter Desnoyers, Deepak Ganesan, Prashant Shenoy
(University of Massachusetts, Amherst)

16:30-20:00 Demonstration and poster session

List of accepted demonstrations and posters

http://sensys.acm.org/2006/demo_poster.html

20:00-21:00 TinyOS Alliance BoF

Friday, November 3

08:30-10:00 Architecture

CarTel: A Distributed Mobile Sensor Computing System
Bret Hull, Vladimir Bychkovsky, Yang Zhang, Kevin Chen, Michel
Goraczko, Allen Miu, Eugene Shih, Hari Balakrishnan, Samuel Madden
(MIT/CSAIL)

MELETE: Supporting Concurrent Applications in Wireless Sensor Networks
Yang Yu, Loren Rittle (Motorola Labs), Jason LeBrun (UCD), Vartika
Bhandari (UIUC)

The Tenet Architecture for Tiered Sensor Networks
Omprakash Gnawali (USC), Ben Greenstein (UCLA), Ki-Young Jang (USC),
August Joki (UCLA), Jeongyeup Paek, Marcos Vieira (USC), Deborah
Estrin (UCLA), Ramesh Govindan (USC), Eddie Kohler (UCLA)

10:00-10:30 Break

10:30-12:00 Media Access Control

Funneling-MAC: A Localized, Sink-Oriented MAC for Boosting Fidelity
in Sensor Networks
Gahng-Seop Ahn (Columbia University), Emiliano Miluzzo, Andrew T.
Campbell (Dartmouth College), Se Gi Hong (Columbia University),
Francesca Cuomo (University of Rome "La Sapienza")

X-MAC: A Short Preamble MAC Protocol for Duty-Cycled Wireless Sensor
Networks
Michael Buettner, Gary V. Yee, Eric Anderson, Richard Han (University
of Colorado, Boulder)

Ultra-Low Duty Cycle MAC with Scheduled Channel Polling
Wei Ye, Fabio Silva, John Heidemann (USC/ISI)

12:00-12:15 Best Talk Award and Closing

14:30-16:30 NCAR Tour (optional)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
***************DEMOS*********************
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

SignetLab: Deployable Sensor Network Testbed and Management Tool
Riccardo Crepaldi, Albert F Harris III, Alberto Scarpa, Andrea
Zanella, Michele Zorzi (University of Padova)

An Eventual Consistent Wireless Light Control System
Jeonghoon Kang (Korea Electronics Technology Institute), Alec Woo
(Arch Rock), Junejae Yoo, Myunghyun Yoon (Korea Electronics
Technology Institute)

Data Analysis Tools for Sensor-Based Science
Stuart Ozer (Microsoft Research), Alex Szalay (Johns Hopkins
University), Jim Gray (Microsoft Research), Andreas Terzis, Razvan
Musaloiu-E., Katalin Szlavecz, Josh Cogan, Randal Burns (Johns
Hopkins University)

Data Collection in Delay Tolerant Mobile Sensor Networks using SCAR
Cecilia Mascolo, Mirco Musolesi, Bence Pasztor (University College
London)

cCAM: Ultra Compact, High Data-Rate Wireless Sensor Node with a
Miniature Camera
Chulsung Park, Pai H. Chou (UCI)

Using Grid Technologies to Optimise a Wireless Sensor Network for
Flood Management
Danny Hughes, Phil Greenwood, Geoff Coulson, Gordon Blair, Barry
Porter, Paul Grace, Florian Pappenberger, Paul Smith, Keith Beven
(Lancaster University)

A Funneling-MAC for High Performance Data Collection in Sensor Networks
Gahng-Seop Ahn (Columbia University) Emiliano Miluzzo, Andrew T.
Campbell (Dartmouth College)

A Storage-centric Camera Sensor Network
Gaurav Mathur, Paul Chukiu, Peter Desnoyers, Deepak Ganesan, Prashant
Shenoy (University of Massachusetts)

Real-Time Volcanic Earthquake Localization
Geoffrey Werner-Allen, Patrick Swieskowski, Matt Welsh (Harvard
University)

Low Power, Low Cost, Wireless Camera Sensor Nodes For Human Detection
Jason Schlessman, Jaechang Shim, Ikdong Kim, Yun Cheol Baek, Wayne
Wolf (Princeton University)

A Unified Architecture for Flexible Radio Power Management in
Wireless Sensor Networks
Kevin Klues, Guoliang Xing, Chenyang Lu (Washington University)

A Self-Calibrating Distributed Acoustic Sensing Platform
Lewis D Girod (MIT/CSAIL), Martin Lukac (UCLA), Vladimir Trifa
(EPFL), Deborah Estrin (UCLA)

A Virtualizing OS Kernel for Wireless Sensor Networks
Lin Gu, John A Stankovic (University of Virginia)

Flexible Hardware/Software Platform for Tracking Applications
Junaid Ansari, Jos=C3=83=C2=A9 S=C3=83=C2=A1nchez, Marina Petrova, Janne =
Riihij=C3=83=C2=A4rvi,
Ossi Raivio, Krisakorn Rerkrai, Chirstine Jardak, Frank Oldewurtel,
Mathias
Wellens, Lili Wu, Petri M=C3=83=C2=A4h=C3=83=C2=B6nen (RWTH Aachen Univer=
sity)

Simple Sensor Syndiciation
Michael Colagrosso, Wade Simmons, Marianne Graham (Colorado School of
Mines)

Responsive and Energy-Efficient Sensor Networking for Real Time
Location Tracking
Henoc Agbota, Mike Hazas (Lancaster University)

Demonstrating Distributed Signal Strength Location Estimation
Neal Patwari (University of Utah), Alfred O. Hero (University of
Michigan)

Sensing and Reproducing the Shapes of 3D Objects Using Claytronics
Padmanabhan Pillai, Jason Campbell (Intel Research Pittsburgh)

Cascades: An Extensible Heterogeneous Sensor Networking Framework
Phillip Sitbon, Nirupama Bulusu, Wu-Chi Feng (Portland State University)

LiteOS - A Lightweight Operating System for C++ Software Development
in Sensor Networks
Qing Cao, Tarek Abdelzaher (UIUC)

GRAIL: General Real-Time Adaptable Indoor Localization
Yingying Chen (Rutgers University), Eiman Elnahrawy (Kordinate LLC),
John-Austen Francisco, Konstantinos Kleisouris (Rutgers University),
Xiaoyan Li (Lafayette College), Hongyi Xue (Rutgers University),
Richard P. Martin (Rutgers University and Kordinate LLC)

A Hierarchical Location Directory Service Across Sensor and IP Networks
Sangeeta Bhattacharya, Chien-Liang Fok, Chenyang Lu, Gruia-Catalin
Roman (Washington University)

Software Radio Implementation of Short-range
Wireless Standards for Sensor Networking
Thomas Schmid, Tad Dreier, Mani B. Srivastava (UCLA)

The CarTel Mobile Sensor Computing System
Vladimir L Bychkovsky, Kevin Chen, Michel Goraczko, Hongyi Hu, Bret W
Hull, Allen K Miu, Eugene I Shih, Yang Zhang (MIT)

TOSDev: A Rapid Development Environment for TinyOS
William P McCartney, Nigamanth Sridhar (Cleveland State University)

Step-wise Context Extraction in AoK Mule System
Yuichi Uehara, Masato Mori, Nayuta Ishii (Tokyo Denki University),
Yoh Shiraishi (The University of Tokyo) Yoshito Tobe (Tokyo Denki
University)

SensorMap: A Web Site for Sensors World-Wide
Suman Nath, Jie Liu, Jessica Miller, Feng Zhao (Microsoft Research),
Andre Santanche (UNICAMP)

Mobility Centric Campus Area Sensor Network for Locality Specific
Applications
Mukundan Sridharan, Anish Arora, Rajiv Ramnath, Emre Ertin (The Ohio
State University)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
***************Posters*******************
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Routing and Processing Multiple Aggregate Queries in Sensor Networks
Niki Trigoni, Alexandre Guitton, Antonios Skordylis (University of
London)

Rateless Codes for Data Dissemination in Sensor Networks
Andrew Hagedorn, David Starobinski, Ari Trachtenberg (Boston University)

AMSecure: Secure Link-Layer Communication in TinyOS for IEEE 802.15.4-
based Wireless Sensor Networks
Anthony D Wood, John A Stankovic (University of Virginia)

Virtual Sensing Range
Emiliano Miluzzo, Nicholas D Lane, Andrew T Campbell (Dartmouth College)

uScan: A Lightweight Two-Tier Global Sensing CoverageDesign
Yu Gu, Tian He (University of Minnesota)

SkiScape Sensing
Shane B. Eisenman (Columbia University), Andrew T. Campbell
(Dartmouth College)

Channel Surfing: Defending WirelessSensor Networks from Jamming and
Interference
Wenyuan Xu, Wade Trappe, Yanyong Zhang (Rutgers University)

Energy Adaptation Techniques to Optimize Data Delivery in Store-and-
Forward Sensor Networks
Pei Zhang, Margaret Martonosi (Princeton Unviersity)

A Distributed Reliable Data Transport Strategy for Event Based
Wireless Sensor Networks
Yuyan Xue, Byrav Ramamurthy, Ying Lu (University of Nebraska - Lincoln)

Lowering Radio Duty Cycle Through Temperature Compensated Timing
Joakim Arfvidsson, Eric Park, Philip Levis (Stanford University)

Collaborative Scheduling of Event Types and Allocation of Rates for
Wireless Sensor Nodes with Multiple Sensing Units
Hidayet Ozgur Sanli, Hasan Cam (Arizona State University)

Kaizen: Improving Sensor Network Operating Systems
James Horey, Jean-Charles Tournier, Arthur B Maccabe (University of
New Mexico)

Achieving Realistic Sensing Area Modeling
Joengmin Hwang, Tian He, Yongdae Kim (University of Minnesota)

Is Data-Centric Storage and Querying Scalable?
Joon Ahn, Bhaskar Krishnamachari (USC)

Understanding the Causes of Packet Delivery Success and Failure in
Dense Wireless Sensor Networks
Kannan Srinivasan (Stanford University), Prabal Dutta, Arsalan
Tavakoli (UCB), Philip Levis (Stanford University)

WaveScope: A Signal-Oriented Data Stream Management System
Lewis Girod, Kyle Jamieson, Yuan Mei, Ryan Newton, Stanislav Rost,
Arvind Thiagarajan, Hari Balakrishnan, Samuel Madden (MIT/CSAIL)

Comprehensive Monitoring of CO2 Sequestration in Subalpine Forest
Ecosystems and its Relation to Global Warming
Lynette L. Laffea, Russ K. Monson, Ryan Manning, Ashly Glasser,
Richard Han (University of Colorado, Boulder), Steve Oncley, Jielun
Sun, Sean Burns, Steve Semmer, John Militzer (NCAR)

TINX A Tiny Index Design for Flash Memory on Wireless Sensor Devices
Ajay Mani, Manjunath B Rajashekhar, Philip Levis (Stanford University)

Wireless Sensor Networks for Structural Health Monitoring
Sukun Kim, Shamim Pakzad, David Culler, James Demmel, Gregory Fenves,
Steve Glaser (UCB), Martin Turon (Crossbow)




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



From mip6-bounces@ietf.org Fri Oct 20 01:05:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GamZN-0001rX-LF; Fri, 20 Oct 2006 01:05:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GamZL-0001rG-Og
	for mip6@ietf.org; Fri, 20 Oct 2006 01:05:19 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GamZK-0000Tg-Dv
	for mip6@ietf.org; Fri, 20 Oct 2006 01:05:19 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9K55GKv017438
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 19 Oct 2006 22:05:16 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9K55ESX011432; Thu, 19 Oct 2006 22:05:15 -0700 (PDT)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 22:05:14 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 22:05:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Thu, 19 Oct 2006 22:05:11 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A9B0@NAEX14.na.qualcomm.com>
In-Reply-To: <4537CD92.4010706@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: Acbzsqhz7Iw2pzw7QP28LCEIlw5aMQAUiucw
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 20 Oct 2006 05:05:14.0485 (UTC)
	FILETIME=[53D0E250:01C6F405]
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



 > > So the remaining question is: Is it worth worrying about=20
 > the integrity
 > > of the BU in this case? IMHO I think the answer is yes.=20
 > Why? Two main
 > > reasons:
 > >=20
 > > 1. There can be cases where the BU is sent to a local HA and the
 > > operator can guarantee that no NATs are in the path. In=20
 > this case we
 > > would lose integrity for no reason, i.e. the BU becomes the weakest
 > > link. This is not unusual really because an operator may=20
 > decide that it
 > > will only provide the HA function within its domain, which=20
 > happens to
 > > not include NATs between the MN and the HA.=20
 >=20
 > if there is no NAT on the path, the use of alt-CoA
 > gives automatic integrity protection for the CoA.

=3D> The point here is that you don't know that at the time the BU is
sent. As I said in an earlier email we can't say that "the mobile node
should do X if there is no NAT". The MN doesn't know if there is a NAT
or not.=20

 > the original suggestion was to relax the "MUST"
 > in RFC 3775 which says the HA should always use the
 > CoA in the alt-CoA option. not to relax the
 > MN requirement to include the alt-CoA option when
 > ESP is used.

=3D> Of course, but the only way to fix it for DSMIP is to say "when in =
an
IPv4 network don't use the alt-coa". We can't rely on the knowledge of
the presence of a NAT before the BU is sent.=20

Hesham

 >=20
 > Vijay
 >=20

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



From mip6-bounces@ietf.org Fri Oct 20 01:49:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GanFQ-0002lF-3O; Fri, 20 Oct 2006 01:48:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GanFN-0002l6-Vt
	for mip6@ietf.org; Fri, 20 Oct 2006 01:48:45 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GanFL-0005v7-L9
	for mip6@ietf.org; Fri, 20 Oct 2006 01:48:45 -0400
Received: from [10.1.210.9] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 22:48:38 -0700
Message-ID: <4538627F.2090805@azairenet.com>
Date: Thu, 19 Oct 2006 22:45:35 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A24A9B0@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A9B0@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Oct 2006 05:48:38.0503 (UTC)
	FILETIME=[63EE7F70:01C6F40B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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

Soliman, Hesham wrote:
> 
>  > > So the remaining question is: Is it worth worrying about 
>  > the integrity
>  > > of the BU in this case? IMHO I think the answer is yes. 
>  > Why? Two main
>  > > reasons:
>  > > 
>  > > 1. There can be cases where the BU is sent to a local HA and the
>  > > operator can guarantee that no NATs are in the path. In 
>  > this case we
>  > > would lose integrity for no reason, i.e. the BU becomes the weakest
>  > > link. This is not unusual really because an operator may 
>  > decide that it
>  > > will only provide the HA function within its domain, which 
>  > happens to
>  > > not include NATs between the MN and the HA. 
>  > 
>  > if there is no NAT on the path, the use of alt-CoA
>  > gives automatic integrity protection for the CoA.
> 
> => The point here is that you don't know that at the time the BU is
> sent. As I said in an earlier email we can't say that "the mobile node
> should do X if there is no NAT". The MN doesn't know if there is a NAT
> or not. 
> 
>  > the original suggestion was to relax the "MUST"
>  > in RFC 3775 which says the HA should always use the
>  > CoA in the alt-CoA option. not to relax the
>  > MN requirement to include the alt-CoA option when
>  > ESP is used.
> 
> => Of course, but the only way to fix it for DSMIP is to say "when in an
> IPv4 network don't use the alt-coa". We can't rely on the knowledge of
> the presence of a NAT before the BU is sent. 

no. simple solution is for the MN to include the
alt-CoA all the time in the BU when using ESP in
transport mode.

the HA does the NAT detection. if it does not
detect a NAT, it uses the CoA in the alt-CoA
option. the CoA is integrity protected in this
case. if the HA detects a NAT, it uses the
source address in the outer IPv4 header. no
integrity protection for the CoA in this case.

Vijay

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



From mip6-bounces@ietf.org Fri Oct 20 02:50:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GaoCV-0006Da-DS; Fri, 20 Oct 2006 02:49:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GaoCT-0006DP-GN
	for mip6@ietf.org; Fri, 20 Oct 2006 02:49:49 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaoCS-0004Mv-5V
	for mip6@ietf.org; Fri, 20 Oct 2006 02:49:49 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9K6njpP017767
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 19 Oct 2006 23:49:46 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.na.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9K6niv9006206; 
	Thu, 19 Oct 2006 23:49:45 -0700 (PDT)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 23:49:44 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Oct 2006 23:49:44 -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] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Thu, 19 Oct 2006 23:49:41 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A9B2@NAEX14.na.qualcomm.com>
In-Reply-To: <4538627F.2090805@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: Acb0C2z9EcjFeQkRRvK4LwZvrmmmvwAB+r7Q
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 20 Oct 2006 06:49:44.0296 (UTC)
	FILETIME=[ECEA1E80:01C6F413]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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

You've just done a complete 180 degree turn and are essentially asking
to always use it instead of the agreed decision to not use the alt-coa.=20

 > no. simple solution is for the MN to include the
 > alt-CoA all the time in the BU when using ESP in
 > transport mode.
 >=20
 > the HA does the NAT detection. if it does not
 > detect a NAT, it uses the CoA in the alt-CoA
 > option. the CoA is integrity protected in this
 > case. if the HA detects a NAT, it uses the
 > source address in the outer IPv4 header. no
 > integrity protection for the CoA in this case.

=3D> You're misrepresenting the issue here. It's not an either or
situation...you use **both**
addresses, the one in the outer IPv4 header and the one in the IPv6
packets in *both* cases...

I prefer to avoid a circular discussion about this issue. Since we all
agreed to relax the requirement, let's focus the discussion on whether
we need the checksum or not.=20

Hesham

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



From mip6-bounces@ietf.org Fri Oct 20 04:15:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GapPc-0005xY-0d; Fri, 20 Oct 2006 04:07:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GapPX-0005sb-1P
	for mip6@ietf.org; Fri, 20 Oct 2006 04:07:23 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GapKf-0001Zk-Ms
	for mip6@ietf.org; Fri, 20 Oct 2006 04:02:22 -0400
Received: by ug-out-1314.google.com with SMTP id 72so610067ugd
	for <mip6@ietf.org>; Fri, 20 Oct 2006 01:02:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=UuuWl5rs+cklGm8lD+9VejwoWQEI5DOIQUrjCtLF05weekl2IMRjN202yV5jB1iIcZBn6gW9NxtKSO1XyZZSIJgHTrTXgf7GRpFbbQHh5OV1fAlrrnyWjdw+q/3u67lVzUfG4NoPWWbRlDBe6UjBxatGWfSB+dzcZxIkX3OKL/k=
Received: by 10.67.89.5 with SMTP id r5mr1423430ugl;
	Fri, 20 Oct 2006 01:02:18 -0700 (PDT)
Received: by 10.66.243.16 with HTTP; Fri, 20 Oct 2006 01:02:18 -0700 (PDT)
Message-ID: <eaa74a7e0610200102s11be04bdr59b2ed6566ed0804@mail.gmail.com>
Date: Fri, 20 Oct 2006 10:02:18 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Madjid Nakhjiri" <mnakhjiri@huawei.com>, 
	"Yoshihiro Ohba" <yohba@tari.toshiba.com>
Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
In-Reply-To: <002f01c6f3c3$aba66960$2f01a8c0@huawei6cc10c70>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20061019203232.GF30464@steelhead>
	<002f01c6f3c3$aba66960$2f01a8c0@huawei6cc10c70>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: mip6@ietf.org, dime@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 Yoshi and Madjid,

the AAA goals draft does not include any specific goal for rfc4285.
This issue was raised in Montreal and during MIP6 re-chartering
discussion. The outcome of the discussion was that there is no a clear
interest now in the IETF to standardize a bootstrapping solution for
rfc4285 and a Diameter Application that supports rfc4285. MIP6 chairs
and Jari mentioned that they may ask for rfc4285 support if
significant interest will be raised. Remember also that rfc4285 is
informational and the Diameter Application will be PS: not sure how to
this difference would be handled.

Having said that, I think that the approach taken so far in the design
of the Diameter Application is flexible enough to include rfc4285
later without any big change: the authorization application does not
need to be changed for rfc4285 support and we may define another
application for authentication purposes. Therefore the
authentication/authorization split seems a correct approach in order
to introduce rfc4285 support later.

--Gerardo

On 10/19/06, Madjid Nakhjiri <mnakhjiri@huawei.com> wrote:
> Hi Yoshi,
>
> I agree, no point on insisting that solutions would support 4285, if 4285
> requirements are not included. I can think of aspects of 4285 that can be
> problematic, but won't mention them now, since I don't want to be accused of
> opening the pandora's box while aaa-ha-goals is going through last call or
> the dime docs are underway :)
>
> We should not make claims we cannot back up later as that might derail the
> standardization process two years from now. As Persians say (after a lousy
> marketing translation) "A small quarrel in the beginning better than a
> bloody peace at the end"
>
>
>
> R,
>
> Madjid
>
>
> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Thursday, October 19, 2006 1:33 PM
> To: Madjid Nakhjiri
> Cc: 'Gerardo Giaretta'; 'Vijay Devarapalli'; mip6@ietf.org; dime@ietf.org
> Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
> Bootstrapping Work
>
> Madjid,
>
> On Thu, Oct 19, 2006 at 01:04:04PM -0700, Madjid Nakhjiri wrote:
> > Ok, so I see I spend a long email without reading the rest of the thread.
> > Do we feel the AAA goal draft efficiently captures the 4285 requirements?
> > If yes, sorry for clogging your mailboxes..
>
> That is my feeling and is why I had the following comment on aaa-ha-goals
> draft:
>
> "
>   YO: This document seems to assume the use of IPsec between MN and HA
>   for securing Mobile IPv6 signaling.  But the AAA interface could
>   also be used for RFC 4285.  So I think it might be good to mention
>   in this section that the document may not preclude the use of
>   alternative methods for securing Mobile IPv6 signaling between MN
>   and HA while this document focuses on the use of IPsec between MN
>   and HA.
> "
>
> Yoshihiro Ohba
>
>
> >
> > R,
> >
> > Madjid
> >
> > -----Original Message-----
> > From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> > Sent: Friday, October 13, 2006 12:37 AM
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org; dime@ietf.org
> > Subject: Re: [Dime] Impact of RFC 4285 for Diameter MIP6 Bootstrapping
> Work
> >
> > > > in the DIME working group we are currently producing documents that
> > > > relate to the backend solution of the
> > > >
> > > > * Integrated Scenario
> > > >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> > > >
> > > > * Split Scenario
> > > >   draft-ietf-mip6-bootstrapping-split-02
> > > >
> > > > Now, the question came up whether we have to consider RFC 4285
> > > > ('Authentication Protocol for Mobile IPv6') for our work as well.
> > >
> > > currently it is not clear if we are going to do any
> > > further work on RFC 4285 in the MIP6 WG. so my
> > > suggestion is to assume only the use of IKEv2 (with
> > > and without EAP).
> > >
> >
> > Agree with Vijay, this is also the assumption for the AAA goals draft.
> >
> > --Gerardo
> >
> > > but it would be good to keep the solution flexible
> > > so that it can be extended later for 4285 if required.
> > >
> > > Vijay
> > >
> > > _______________________________________________
> > > DiME mailing list
> > > DiME@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/dime
> > >
> >
> > _______________________________________________
> > DiME mailing list
> > DiME@ietf.org
> > https://www1.ietf.org/mailman/listinfo/dime
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>

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



From mip6-bounces@ietf.org Fri Oct 20 05:30:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gaqhl-0005UG-4L; Fri, 20 Oct 2006 05:30:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gaqhj-0005U1-HZ
	for mip6@ietf.org; Fri, 20 Oct 2006 05:30:15 -0400
Received: from nf-out-0910.google.com ([64.233.182.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gaqhh-0004pO-PU
	for mip6@ietf.org; Fri, 20 Oct 2006 05:30:15 -0400
Received: by nf-out-0910.google.com with SMTP id n15so1444476nfc
	for <mip6@ietf.org>; Fri, 20 Oct 2006 02:30:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=UHhr5fqoIhOEV1HlCUXXh0hfhlRWBcG56QcsM+f07CT9vsw2ohr/t3NUSvPgPgB+eKiGNErkgytU8BiHDn53N6bOjhlHU9f2R44PFY4NjCmdtGHaQhM4sXf1LcHWtc502cHRXn5DSskxZiwJ1jysg9mENWWAXZ1a0RD8qut6qaE=
Received: by 10.82.139.17 with SMTP id m17mr387921bud;
	Fri, 20 Oct 2006 02:30:12 -0700 (PDT)
Received: by 10.82.98.7 with HTTP; Fri, 20 Oct 2006 02:30:12 -0700 (PDT)
Message-ID: <5e2406980610200230x7d7f9345l176b576627791f74@mail.gmail.com>
Date: Fri, 20 Oct 2006 11:30:12 +0200
From: "Julien Bournelle" <julien.bournelle@gmail.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
In-Reply-To: <eaa74a7e0610200102s11be04bdr59b2ed6566ed0804@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20061019203232.GF30464@steelhead>
	<002f01c6f3c3$aba66960$2f01a8c0@huawei6cc10c70>
	<eaa74a7e0610200102s11be04bdr59b2ed6566ed0804@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Cc: mip6@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>, dime@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,

 concerning support for rfc4285, I think we'll need messages to carry the BU
 from the HA to the AAAH for the authentifcation. As such, a new application
 may be necessary. As a consequence, the authorization and accounting part
 may be handled by the same application.

 This application would be similar to the RFC4004 (without FA...).

 Just my 2 cents,

 Julien

On 10/20/06, Gerardo Giaretta <gerardo.giaretta@gmail.com> wrote:
> Hi Yoshi and Madjid,
>
> the AAA goals draft does not include any specific goal for rfc4285.
> This issue was raised in Montreal and during MIP6 re-chartering
> discussion. The outcome of the discussion was that there is no a clear
> interest now in the IETF to standardize a bootstrapping solution for
> rfc4285 and a Diameter Application that supports rfc4285. MIP6 chairs
> and Jari mentioned that they may ask for rfc4285 support if
> significant interest will be raised. Remember also that rfc4285 is
> informational and the Diameter Application will be PS: not sure how to
> this difference would be handled.
>
> Having said that, I think that the approach taken so far in the design
> of the Diameter Application is flexible enough to include rfc4285
> later without any big change: the authorization application does not
> need to be changed for rfc4285 support and we may define another
> application for authentication purposes. Therefore the
> authentication/authorization split seems a correct approach in order
> to introduce rfc4285 support later.
>
> --Gerardo
>
> On 10/19/06, Madjid Nakhjiri <mnakhjiri@huawei.com> wrote:
> > Hi Yoshi,
> >
> > I agree, no point on insisting that solutions would support 4285, if 4285
> > requirements are not included. I can think of aspects of 4285 that can be
> > problematic, but won't mention them now, since I don't want to be accused of
> > opening the pandora's box while aaa-ha-goals is going through last call or
> > the dime docs are underway :)
> >
> > We should not make claims we cannot back up later as that might derail the
> > standardization process two years from now. As Persians say (after a lousy
> > marketing translation) "A small quarrel in the beginning better than a
> > bloody peace at the end"
> >
> >
> >
> > R,
> >
> > Madjid
> >
> >
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Thursday, October 19, 2006 1:33 PM
> > To: Madjid Nakhjiri
> > Cc: 'Gerardo Giaretta'; 'Vijay Devarapalli'; mip6@ietf.org; dime@ietf.org
> > Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
> > Bootstrapping Work
> >
> > Madjid,
> >
> > On Thu, Oct 19, 2006 at 01:04:04PM -0700, Madjid Nakhjiri wrote:
> > > Ok, so I see I spend a long email without reading the rest of the thread.
> > > Do we feel the AAA goal draft efficiently captures the 4285 requirements?
> > > If yes, sorry for clogging your mailboxes..
> >
> > That is my feeling and is why I had the following comment on aaa-ha-goals
> > draft:
> >
> > "
> >   YO: This document seems to assume the use of IPsec between MN and HA
> >   for securing Mobile IPv6 signaling.  But the AAA interface could
> >   also be used for RFC 4285.  So I think it might be good to mention
> >   in this section that the document may not preclude the use of
> >   alternative methods for securing Mobile IPv6 signaling between MN
> >   and HA while this document focuses on the use of IPsec between MN
> >   and HA.
> > "
> >
> > Yoshihiro Ohba
> >
> >
> > >
> > > R,
> > >
> > > Madjid
> > >
> > > -----Original Message-----
> > > From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> > > Sent: Friday, October 13, 2006 12:37 AM
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org; dime@ietf.org
> > > Subject: Re: [Dime] Impact of RFC 4285 for Diameter MIP6 Bootstrapping
> > Work
> > >
> > > > > in the DIME working group we are currently producing documents that
> > > > > relate to the backend solution of the
> > > > >
> > > > > * Integrated Scenario
> > > > >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> > > > >
> > > > > * Split Scenario
> > > > >   draft-ietf-mip6-bootstrapping-split-02
> > > > >
> > > > > Now, the question came up whether we have to consider RFC 4285
> > > > > ('Authentication Protocol for Mobile IPv6') for our work as well.
> > > >
> > > > currently it is not clear if we are going to do any
> > > > further work on RFC 4285 in the MIP6 WG. so my
> > > > suggestion is to assume only the use of IKEv2 (with
> > > > and without EAP).
> > > >
> > >
> > > Agree with Vijay, this is also the assumption for the AAA goals draft.
> > >
> > > --Gerardo
> > >
> > > > but it would be good to keep the solution flexible
> > > > so that it can be extended later for 4285 if required.
> > > >
> > > > Vijay
> > > >
> > > > _______________________________________________
> > > > DiME mailing list
> > > > DiME@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/dime
> > > >
> > >
> > > _______________________________________________
> > > DiME mailing list
> > > DiME@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/dime
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
>

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



From mip6-bounces@ietf.org Fri Oct 20 09:01:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gau02-00032C-13; Fri, 20 Oct 2006 09:01:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gau00-00031J-RB
	for mip6@ietf.org; Fri, 20 Oct 2006 09:01:20 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gatzz-0002QU-DO
	for mip6@ietf.org; Fri, 20 Oct 2006 09:01:20 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 83B9A8989C;
	Fri, 20 Oct 2006 16:01:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 37456898A9;
	Fri, 20 Oct 2006 16:01:11 +0300 (EEST)
Message-ID: <45389200.3020403@piuha.net>
Date: Fri, 20 Oct 2006 12:08:16 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060921)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] issue 75: Authors on the front page should be less than 6
References: <7EB20EA0938B4D42A2D82689365C9B7A24A109@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A109@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


It is important to recognize the input from the individual
authors. Its the right thing to do. And one of the things
that I like in the IETF process  is that having a person's
name in the document makes them feel personally
responsible about the content.

However, this does not necessarily always translate
to having a long list of names listed at the front. There
are practical reasons such as the AUTH48 process
which become cumbersome if there are a large number
of authors. But the author limit is not a hard rule, its
a guideline. Though in this particular case it would seem
logical to put the editor's name at the front and add a
"Contributors" or "Additional Authors" section
for the rest. If needed, describe the level of the
contribution or the source of text.

And remember to use the acknowledgment and
contributor sections in this and other drafts. In the
IETF process it is expected that a lot of people
participate in design, review, and even writing
of specifications. But not all of these people are
authors. You should not expect to get your name
at the top just because you reviewed it, participated
in the design discussions, or even contributed
paragraphs of text. For such level of contribution
the proper attribution is the acknowledgment
section.

--Jari



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



From mip6-bounces@ietf.org Fri Oct 20 09:28:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GauQD-00068Y-MQ; Fri, 20 Oct 2006 09:28:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GauQB-00068L-QP
	for mip6@ietf.org; Fri, 20 Oct 2006 09:28:23 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GauQ9-0006qR-GW
	for mip6@ietf.org; Fri, 20 Oct 2006 09:28:23 -0400
Received: from [10.1.210.9] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Oct 2006 06:28:19 -0700
Message-ID: <4538CE41.3060808@azairenet.com>
Date: Fri, 20 Oct 2006 06:25:21 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A24A9B2@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A9B2@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Oct 2006 13:28:19.0607 (UTC)
	FILETIME=[9B8CFA70:01C6F44B]
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

Soliman, Hesham wrote:
> Vijay, 
> 
> You've just done a complete 180 degree turn and are essentially asking
> to always use it instead of the agreed decision to not use the alt-coa. 

??

from what I remember we wanted to relax the MUST
requirement at the HA to always the CoA in the
alt-CoA option when there is a NAT present.

I remember someone suggesting not using the option
at all in DS-MIPv6, but I don't remember concluding
on that. anyway, lets figure out what we want to do
now.

>  > no. simple solution is for the MN to include the
>  > alt-CoA all the time in the BU when using ESP in
>  > transport mode.
>  > 
>  > the HA does the NAT detection. if it does not
>  > detect a NAT, it uses the CoA in the alt-CoA
>  > option. the CoA is integrity protected in this
>  > case. if the HA detects a NAT, it uses the
>  > source address in the outer IPv4 header. no
>  > integrity protection for the CoA in this case.
> 
> => You're misrepresenting the issue here. It's not an either or
> situation...you use **both**
> addresses, the one in the outer IPv4 header and the one in the IPv6
> packets in *both* cases...

The HA uses both for NAT detection. but considers
only one as the CoA.

> I prefer to avoid a circular discussion about this issue. Since we all
> agreed to relax the requirement, let's focus the discussion on whether
> we need the checksum or not. 

:) I don't think we need it.

Vijay

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



From mip6-bounces@ietf.org Fri Oct 20 11:40:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GawT2-0000rg-PB; Fri, 20 Oct 2006 11:39:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GawT0-0000rR-Sx
	for mip6@ietf.org; Fri, 20 Oct 2006 11:39:26 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GawSw-0004XM-Gz
	for mip6@ietf.org; Fri, 20 Oct 2006 11:39:26 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9KFdJFp016587
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 20 Oct 2006 08:39:20 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9KFdI85015721; Fri, 20 Oct 2006 08:39:19 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Oct 2006 08:39:17 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Oct 2006 08:39:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Fri, 20 Oct 2006 08:39:12 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A9EF@NAEX14.na.qualcomm.com>
In-Reply-To: <4538CE41.3060808@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: Acb0S6GRyL9+KSZZTq2Yfxf/Mhr5jQAEcmSQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 20 Oct 2006 15:39:18.0586 (UTC)
	FILETIME=[E7DE01A0:01C6F45D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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


 > > You've just done a complete 180 degree turn and are=20
 > essentially asking
 > > to always use it instead of the agreed decision to not use=20
 > the alt-coa.=20
 >=20
 > ??
 >=20
 > from what I remember we wanted to relax the MUST
 > requirement at the HA to always the CoA in the
 > alt-CoA option when there is a NAT present.

=3D> Right, but please s/when a NAT is present/when in an IPv4 network.
As I said a couple of times now, the MN doesn't know if a NAT is present
when it sends the BU.

 >=20
 > The HA uses both for NAT detection. but considers
 > only one as the CoA.

=3D> Not quite. The outer v4 address is still used in the UDP tunnel
interface, the IPv4 address in the IPv6 packet is the "CoA" as far as
MIPv6 is concerned. Of course the two can be the same (no NAT) or
different (NAT or MITM).

 >=20
 > > I prefer to avoid a circular discussion about this issue.=20
 > Since we all
 > > agreed to relax the requirement, let's focus the=20
 > discussion on whether
 > > we need the checksum or not.=20
 >=20
 > :) I don't think we need it.

=3D> That's fine, so you just express that opinion for this new issue. =
All
I said was that the checksum (the need for it) will be a separate issue
since we agreed on the other part (relaxing of 3775).=20

Hesham


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



From mip6-bounces@ietf.org Fri Oct 20 11:55:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GawiW-0002RT-Ut; Fri, 20 Oct 2006 11:55:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GawiV-0002Pw-6J
	for mip6@ietf.org; Fri, 20 Oct 2006 11:55:27 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GawiQ-0007AG-OU
	for mip6@ietf.org; Fri, 20 Oct 2006 11:55:27 -0400
Received: from [192.168.1.102] ([24.6.251.221]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Oct 2006 08:55:21 -0700
Message-ID: <4538F0B2.3080403@azairenet.com>
Date: Fri, 20 Oct 2006 08:52:18 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A24A9EF@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24A9EF@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Oct 2006 15:55:22.0044 (UTC)
	FILETIME=[262207C0:01C6F460]
X-Spam-Score: 0.1 (/)
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

Soliman, Hesham wrote:
>  > > You've just done a complete 180 degree turn and are 
>  > essentially asking
>  > > to always use it instead of the agreed decision to not use 
>  > the alt-coa. 
>  > 
>  > ??
>  > 
>  > from what I remember we wanted to relax the MUST
>  > requirement at the HA to always the CoA in the
>  > alt-CoA option when there is a NAT present.
> 
> => Right, but please s/when a NAT is present/when in an IPv4 network.

nope. the HA needs to relax the requirement only
when it detects a NAT, not because the MN is on
an IPv4 access network.

> As I said a couple of times now, the MN doesn't know if a NAT is present
> when it sends the BU.

who disagreed?

> => That's fine, so you just express that opinion for this new issue. All
> I said was that the checksum (the need for it) will be a separate issue
> since we agreed on the other part (relaxing of 3775). 

lets be clear on what we agreed to relax. only the
MUST requirement on the HA to use the CoA in the
alt-CoA option all the time.

Vijay

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



From mip6-bounces@ietf.org Fri Oct 20 12:00:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gawne-0007Ro-4A; Fri, 20 Oct 2006 12:00:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gawnd-0007R4-13
	for mip6@ietf.org; Fri, 20 Oct 2006 12:00:45 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GawnZ-00089o-Mt
	for mip6@ietf.org; Fri, 20 Oct 2006 12:00:45 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9KG0eQ4029538
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Fri, 20 Oct 2006 09:00:41 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9KFxQRs026968
	for <mip6@ietf.org>; Fri, 20 Oct 2006 09:00:33 -0700 (PDT)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Oct 2006 08:59:47 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Oct 2006 08:59: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] issue 75: Authors on the front page should be less than 6
Date: Fri, 20 Oct 2006 08:59:41 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A9F7@NAEX14.na.qualcomm.com>
In-Reply-To: <45389200.3020403@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] issue 75: Authors on the front page should be less than 6
Thread-Index: Acb0R+aNxeuWpgcVT5+CmHxov5i2mgAGI3cA
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 20 Oct 2006 15:59:47.0388 (UTC)
	FILETIME=[C44A4FC0:01C6F460]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,=20

This issue is now accepted and closed, we received ample feedback and
there is concensus on moving forward with the editor on the front and
additional authors in the authors' section.=20

Hesham

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



From mip6-bounces@ietf.org Fri Oct 20 13:29:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gay9x-00070N-8y; Fri, 20 Oct 2006 13:27:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gay9v-00070B-Sj; Fri, 20 Oct 2006 13:27:51 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gay9t-0000FY-C6; Fri, 20 Oct 2006 13:27:51 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7G008XO3176Z@usaga01-in.huawei.com>; Fri,
	20 Oct 2006 10:24:44 -0700 (PDT)
Received: from huawei6cc10c70
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J7G009CM3128A@usaga01-in.huawei.com>; Fri,
	20 Oct 2006 10:24:43 -0700 (PDT)
Date: Fri, 20 Oct 2006 10:27:42 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
In-reply-to: <5e2406980610200230x7d7f9345l176b576627791f74@mail.gmail.com>
To: 'Julien Bournelle' <julien.bournelle@gmail.com>,
	'Gerardo Giaretta' <gerardo.giaretta@gmail.com>
Message-id: <000d01c6f46d$0d29be90$2f01a8c0@huawei6cc10c70>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acb0KvfPL1bG87fiRSe/6aV0315s9wAPdrUA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: mip6@ietf.org, 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, dime@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Julien

Your 2 cents are part of the nickel (5 cents) that I did not want to bring
up:) I said this once before, 4285 is a lot like MIP4 key bootstrapping
process. You can look at the combination of 4004 and Nakhjiri-radius-mip4-02
to see all kinds of things needed.
 
Gerardo, here are the issues: 
1) We don't have a set of requirements on 4285 (read non-existing 4285
requirement).
2) We don't even know we want to meet these requirement, even if they
existed?? I.e. MUST or SHOULD the AAA goals include those requirements?
That translates into MUST we or SHOULD the solutions meet the requirements,
once they are developed?


Personally, I think, we don't have any answer to issue 1 and we have already
said the answer to question 2 is no. 

I think without a thorough analysis of the 4285 requirements and without a
MUST/SHOULD meet requirements, we should just move on, without rubber
stamping the solution document as something that supports 4285? The solution
MAY support for 4285, but it is not a requirement.

Your statement on
> Having said that, I think that the approach taken so far in the design
> of the Diameter Application is flexible enough to include rfc4285
> later without any big change

Sounds like a MAY meet the requirements to me! Any other solution may or may
not do it:)

As engineers we design based on requirements, no?


R,

Madjid


-----Original Message-----
From: Julien Bournelle [mailto:julien.bournelle@gmail.com] 
Sent: Friday, October 20, 2006 2:30 AM
To: Gerardo Giaretta
Cc: Madjid Nakhjiri; Yoshihiro Ohba; mip6@ietf.org; dime@ietf.org
Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
Bootstrapping Work

Hi all,

 concerning support for rfc4285, I think we'll need messages to carry the BU
 from the HA to the AAAH for the authentifcation. As such, a new application
 may be necessary. As a consequence, the authorization and accounting part
 may be handled by the same application.

 This application would be similar to the RFC4004 (without FA...).

 Just my 2 cents,

 Julien

On 10/20/06, Gerardo Giaretta <gerardo.giaretta@gmail.com> wrote:
> Hi Yoshi and Madjid,
>
> the AAA goals draft does not include any specific goal for rfc4285.
> This issue was raised in Montreal and during MIP6 re-chartering
> discussion. The outcome of the discussion was that there is no a clear
> interest now in the IETF to standardize a bootstrapping solution for
> rfc4285 and a Diameter Application that supports rfc4285. MIP6 chairs
> and Jari mentioned that they may ask for rfc4285 support if
> significant interest will be raised. Remember also that rfc4285 is
> informational and the Diameter Application will be PS: not sure how to
> this difference would be handled.
>
> Having said that, I think that the approach taken so far in the design
> of the Diameter Application is flexible enough to include rfc4285
> later without any big change: the authorization application does not
> need to be changed for rfc4285 support and we may define another
> application for authentication purposes. Therefore the
> authentication/authorization split seems a correct approach in order
> to introduce rfc4285 support later.
>
> --Gerardo
>
> On 10/19/06, Madjid Nakhjiri <mnakhjiri@huawei.com> wrote:
> > Hi Yoshi,
> >
> > I agree, no point on insisting that solutions would support 4285, if
4285
> > requirements are not included. I can think of aspects of 4285 that can
be
> > problematic, but won't mention them now, since I don't want to be
accused of
> > opening the pandora's box while aaa-ha-goals is going through last call
or
> > the dime docs are underway :)
> >
> > We should not make claims we cannot back up later as that might derail
the
> > standardization process two years from now. As Persians say (after a
lousy
> > marketing translation) "A small quarrel in the beginning better than a
> > bloody peace at the end"
> >
> >
> >
> > R,
> >
> > Madjid
> >
> >
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Thursday, October 19, 2006 1:33 PM
> > To: Madjid Nakhjiri
> > Cc: 'Gerardo Giaretta'; 'Vijay Devarapalli'; mip6@ietf.org;
dime@ietf.org
> > Subject: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter MIP6
> > Bootstrapping Work
> >
> > Madjid,
> >
> > On Thu, Oct 19, 2006 at 01:04:04PM -0700, Madjid Nakhjiri wrote:
> > > Ok, so I see I spend a long email without reading the rest of the
thread.
> > > Do we feel the AAA goal draft efficiently captures the 4285
requirements?
> > > If yes, sorry for clogging your mailboxes..
> >
> > That is my feeling and is why I had the following comment on
aaa-ha-goals
> > draft:
> >
> > "
> >   YO: This document seems to assume the use of IPsec between MN and HA
> >   for securing Mobile IPv6 signaling.  But the AAA interface could
> >   also be used for RFC 4285.  So I think it might be good to mention
> >   in this section that the document may not preclude the use of
> >   alternative methods for securing Mobile IPv6 signaling between MN
> >   and HA while this document focuses on the use of IPsec between MN
> >   and HA.
> > "
> >
> > Yoshihiro Ohba
> >
> >
> > >
> > > R,
> > >
> > > Madjid
> > >
> > > -----Original Message-----
> > > From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> > > Sent: Friday, October 13, 2006 12:37 AM
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org; dime@ietf.org
> > > Subject: Re: [Dime] Impact of RFC 4285 for Diameter MIP6 Bootstrapping
> > Work
> > >
> > > > > in the DIME working group we are currently producing documents
that
> > > > > relate to the backend solution of the
> > > > >
> > > > > * Integrated Scenario
> > > > >   draft-ietf-mip6-bootstrapping-integrated-dhc-01
> > > > >
> > > > > * Split Scenario
> > > > >   draft-ietf-mip6-bootstrapping-split-02
> > > > >
> > > > > Now, the question came up whether we have to consider RFC 4285
> > > > > ('Authentication Protocol for Mobile IPv6') for our work as well.
> > > >
> > > > currently it is not clear if we are going to do any
> > > > further work on RFC 4285 in the MIP6 WG. so my
> > > > suggestion is to assume only the use of IKEv2 (with
> > > > and without EAP).
> > > >
> > >
> > > Agree with Vijay, this is also the assumption for the AAA goals draft.
> > >
> > > --Gerardo
> > >
> > > > but it would be good to keep the solution flexible
> > > > so that it can be extended later for 4285 if required.
> > > >
> > > > Vijay
> > > >
> > > > _______________________________________________
> > > > DiME mailing list
> > > > DiME@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/dime
> > > >
> > >
> > > _______________________________________________
> > > DiME mailing list
> > > DiME@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/dime
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
>



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



From mip6-bounces@ietf.org Sat Oct 21 02:38:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbATY-0006nh-ER; Sat, 21 Oct 2006 02:36:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbATX-0006nc-8s
	for mip6@ietf.org; Sat, 21 Oct 2006 02:36:55 -0400
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbATR-0005MJ-V4
	for mip6@ietf.org; Sat, 21 Oct 2006 02:36:55 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id k9L6alqs015191
	for <mip6@ietf.org>; Sat, 21 Oct 2006 14:36:47 +0800 (SGT)
Received: from newpascal.lit.org.sg ([192.122.134.77])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id k9L6akKu015185
	for <mip6@ietf.org>; Sat, 21 Oct 2006 14:36:46 +0800 (SGT)
Received: from mailbe01.teak.local.net ([192.122.134.10])
	by mailhost.lit.org.sg
	(Sun Java System Messaging Server 6.1 HotFix 0.09 (built Dec 14 2004))
	with ESMTP id <0J7H0069O3P98C00@mailhost.lit.org.sg> for mip6@ietf.org;
	Sat, 21 Oct 2006 14:36:45 +0800 (SGT)
Received: from mailfe01.teak.local.net ([192.122.134.9])
	by mailbe01.teak.local.net with Microsoft SMTPSVC(6.0.3790.1830); Sat,
	21 Oct 2006 14:36:09 +0800
Received: from DELL9150 ([192.168.137.186]) by mailfe01.teak.local.net with
	Microsoft SMTPSVC(6.0.3790.1830); Sat, 21 Oct 2006 14:36:08 +0800
Date: Sat, 21 Oct 2006 14:36:56 +0800
From: QIU Ying <qiuying@i2r.a-star.edu.sg>
To: basavaraj.patil@nokia.com
Message-id: <08e101c6f4db$4d954080$ba89a8c0@DELL9150>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format=flowed; charset=Windows-1252;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-OriginalArrivalTime: 21 Oct 2006 06:36:08.0887 (UTC)
	FILETIME=[314E5470:01C6F4DB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mip6@ietf.org
Subject: [Mip6] timeslot is requested for mip6 firewall issues
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi, Raj,

If time is allowed, we would like to request 10-15 mins for our two drafts:

A Scheme of Mobile Firewall in Mobile IPv6
http://www.ietf.org/internet-drafts/draft-qiu-mip6-mobile-firewall-02.txt

and
Solution of MIPv6 Friendly Firewall
http://www.ietf.org/internet-drafts/draft-qiu-mip6-friendly-firewall-01.txt

The first one proposes a scheme how to protect a mobile node continuously by 
a firewall. The 2nd one proposes the solution how to let a mobile node go 
through the firewalls according to RFC4487.

Regards
Qiu Ying 


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

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



From mip6-bounces@ietf.org Sat Oct 21 10:21:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbHim-0004hQ-LG; Sat, 21 Oct 2006 10:21:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbHil-0004hK-CK
	for mip6@ietf.org; Sat, 21 Oct 2006 10:21:07 -0400
Received: from email1.etri.re.kr ([129.254.16.131] helo=email1.etri.info)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbHij-0007p4-CS
	for mip6@ietf.org; Sat, 21 Oct 2006 10:21:07 -0400
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC;
	Sat, 21 Oct 2006 23:24:53 +0900
Priority: normal
X-ReadCheckName: mip6%40ietf.org
Thread-Topic: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter
	MIP6Bootstrapping Work
X-ReadCheckMessageID: <e8cf6188-0adf-42fc-a289-8f33ff08a614@etri.re.kr>
thread-index: Acb1HKyr1NUiuWXXRKWXTWauasW09w==
From: =?ks_c_5601-1987?B?wfbBpMjG?= <jhjee@etri.re.kr>
To: "Julien Bournelle" <julien.bournelle@gmail.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
Bcc: 
Subject: RE: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter
	MIP6Bootstrapping Work
Date: Sat, 21 Oct 2006 23:24:53 +0900
Comment: =?ks_c_5601-1987?B?x9GxucD8wNrF673Fv6yxuL/4LCDAzLW/xeu9xSDHpcHY?=
	=?ks_c_5601-1987?B?v6yxuMbALCC047Tn?=
Message-ID: <105d01c6f51c$acb04380$8310fe81@etri.info>
MIME-Version: 1.0
X-Mailer: Microsoft CDO for Exchange 2000
Content-Class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
X-OriginalArrivalTime: 21 Oct 2006 14:24:53.0411 (UTC)
	FILETIME=[ACD41F30:01C6F51C]
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Cc: mip6@ietf.org, dime@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: =?ks_c_5601-1987?B?wfbBpMjG?= <jhjee@etri.re.kr>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============1465414780=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1465414780==
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1053_01C6F568.1C95A190"
Content-Class: urn:content-classes:message

This is a multi-part message in MIME format.

------=_NextPart_000_1053_01C6F568.1C95A190
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64


------=_NextPart_000_1053_01C6F568.1C95A190
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PERJViBpZD1tc2dib2R5IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiCxvLiy
Ij4NCjxESVY+SGkgSnVsaWVuLDwvRElWPg0KPERJVj5Eb2VzIHlvdXIgdGhvdWdodCBpbXBseSB0
aGF0IHRoZSBwaWdneWJhY2tpbmcgdGhlIE1JUHY2IEJVIHRvIHRoZSBBQUEgbWVzc2FnZXM/PC9E
SVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4tSnVuZ2hvb248L0RJVj4NCjxESVY+PEJSPi0t
LS0tv/i6uyC43r3DwfYtLS0tLTxCUj48Qj66uLO9ILvntvc6PC9CPiAiSnVsaWVuIEJvdXJuZWxs
ZSIgJmx0O2p1bGllbi5ib3VybmVsbGVAZ21haWwuY29tJmd0OzxCUj48Qj66uLO9ILOvwqU6PC9C
PiAyMDA2LTEwLTIwIL/AyMQgNjozMDoxMjxCUj48Qj653rTCILvntvc6PC9CPiAiR2VyYXJkbyBH
aWFyZXR0YSIgJmx0O2dlcmFyZG8uZ2lhcmV0dGFAZ21haWwuY29tJmd0OzxCUj48Qj7C/MG2Ojwv
Qj4gIm1pcDZAaWV0Zi5vcmciICZsdDttaXA2QGlldGYub3JnJmd0OywgImRpbWVAaWV0Zi5vcmci
ICZsdDtkaW1lQGlldGYub3JnJmd0OzxCUj48Qj7BprjxOjwvQj4gUmU6IFtNaXA2XSBSRTogW0Rp
bWVdIEltcGFjdCBvZiBSRkMgNDI4NSBmb3IgRGlhbWV0ZXIgTUlQNkJvb3RzdHJhcHBpbmcgV29y
azxCUj48QlI+PC9ESVY+DQo8RElWPjwhLS0gQ29udmVydGVkIGZyb20gdGV4dC9wbGFpbiBmb3Jt
YXQgLS0+PEJSPg0KPFA+PEZPTlQgc2l6ZT0yPkhpIGFsbCw8QlI+PEJSPiZuYnNwO2NvbmNlcm5p
bmcgc3VwcG9ydCBmb3IgcmZjNDI4NSwgSSB0aGluayB3ZSdsbCBuZWVkIG1lc3NhZ2VzIHRvIGNh
cnJ5IHRoZSBCVTxCUj4mbmJzcDtmcm9tIHRoZSBIQSB0byB0aGUgQUFBSCBmb3IgdGhlIGF1dGhl
bnRpZmNhdGlvbi4gQXMgc3VjaCwgYSBuZXcgYXBwbGljYXRpb248QlI+Jm5ic3A7bWF5IGJlIG5l
Y2Vzc2FyeS4gQXMgYSBjb25zZXF1ZW5jZSwgdGhlIGF1dGhvcml6YXRpb24gYW5kIGFjY291bnRp
bmcgcGFydDxCUj4mbmJzcDttYXkgYmUgaGFuZGxlZCBieSB0aGUgc2FtZSBhcHBsaWNhdGlvbi48
QlI+PEJSPiZuYnNwO1RoaXMgYXBwbGljYXRpb24gd291bGQgYmUgc2ltaWxhciB0byB0aGUgUkZD
NDAwNCAod2l0aG91dCBGQS4uLikuPEJSPjxCUj4mbmJzcDtKdXN0IG15IDIgY2VudHMsPEJSPjxC
Uj4mbmJzcDtKdWxpZW48QlI+PEJSPk9uIDEwLzIwLzA2LCBHZXJhcmRvIEdpYXJldHRhICZsdDtn
ZXJhcmRvLmdpYXJldHRhQGdtYWlsLmNvbSZndDsgd3JvdGU6PEJSPiZndDsgSGkgWW9zaGkgYW5k
IE1hZGppZCw8QlI+Jmd0OzxCUj4mZ3Q7IHRoZSBBQUEgZ29hbHMgZHJhZnQgZG9lcyBub3QgaW5j
bHVkZSBhbnkgc3BlY2lmaWMgZ29hbCBmb3IgcmZjNDI4NS48QlI+Jmd0OyBUaGlzIGlzc3VlIHdh
cyByYWlzZWQgaW4gTW9udHJlYWwgYW5kIGR1cmluZyBNSVA2IHJlLWNoYXJ0ZXJpbmc8QlI+Jmd0
OyBkaXNjdXNzaW9uLiBUaGUgb3V0Y29tZSBvZiB0aGUgZGlzY3Vzc2lvbiB3YXMgdGhhdCB0aGVy
ZSBpcyBubyBhIGNsZWFyPEJSPiZndDsgaW50ZXJlc3Qgbm93IGluIHRoZSBJRVRGIHRvIHN0YW5k
YXJkaXplIGEgYm9vdHN0cmFwcGluZyBzb2x1dGlvbiBmb3I8QlI+Jmd0OyByZmM0Mjg1IGFuZCBh
IERpYW1ldGVyIEFwcGxpY2F0aW9uIHRoYXQgc3VwcG9ydHMgcmZjNDI4NS4gTUlQNiBjaGFpcnM8
QlI+Jmd0OyBhbmQgSmFyaSBtZW50aW9uZWQgdGhhdCB0aGV5IG1heSBhc2sgZm9yIHJmYzQyODUg
c3VwcG9ydCBpZjxCUj4mZ3Q7IHNpZ25pZmljYW50IGludGVyZXN0IHdpbGwgYmUgcmFpc2VkLiBS
ZW1lbWJlciBhbHNvIHRoYXQgcmZjNDI4NSBpczxCUj4mZ3Q7IGluZm9ybWF0aW9uYWwgYW5kIHRo
ZSBEaWFtZXRlciBBcHBsaWNhdGlvbiB3aWxsIGJlIFBTOiBub3Qgc3VyZSBob3cgdG88QlI+Jmd0
OyB0aGlzIGRpZmZlcmVuY2Ugd291bGQgYmUgaGFuZGxlZC48QlI+Jmd0OzxCUj4mZ3Q7IEhhdmlu
ZyBzYWlkIHRoYXQsIEkgdGhpbmsgdGhhdCB0aGUgYXBwcm9hY2ggdGFrZW4gc28gZmFyIGluIHRo
ZSBkZXNpZ248QlI+Jmd0OyBvZiB0aGUgRGlhbWV0ZXIgQXBwbGljYXRpb24gaXMgZmxleGlibGUg
ZW5vdWdoIHRvIGluY2x1ZGUgcmZjNDI4NTxCUj4mZ3Q7IGxhdGVyIHdpdGhvdXQgYW55IGJpZyBj
aGFuZ2U6IHRoZSBhdXRob3JpemF0aW9uIGFwcGxpY2F0aW9uIGRvZXMgbm90PEJSPiZndDsgbmVl
ZCB0byBiZSBjaGFuZ2VkIGZvciByZmM0Mjg1IHN1cHBvcnQgYW5kIHdlIG1heSBkZWZpbmUgYW5v
dGhlcjxCUj4mZ3Q7IGFwcGxpY2F0aW9uIGZvciBhdXRoZW50aWNhdGlvbiBwdXJwb3Nlcy4gVGhl
cmVmb3JlIHRoZTxCUj4mZ3Q7IGF1dGhlbnRpY2F0aW9uL2F1dGhvcml6YXRpb24gc3BsaXQgc2Vl
bXMgYSBjb3JyZWN0IGFwcHJvYWNoIGluIG9yZGVyPEJSPiZndDsgdG8gaW50cm9kdWNlIHJmYzQy
ODUgc3VwcG9ydCBsYXRlci48QlI+Jmd0OzxCUj4mZ3Q7IC0tR2VyYXJkbzxCUj4mZ3Q7PEJSPiZn
dDsgT24gMTAvMTkvMDYsIE1hZGppZCBOYWtoamlyaSAmbHQ7bW5ha2hqaXJpQGh1YXdlaS5jb20m
Z3Q7IHdyb3RlOjxCUj4mZ3Q7ICZndDsgSGkgWW9zaGksPEJSPiZndDsgJmd0OzxCUj4mZ3Q7ICZn
dDsgSSBhZ3JlZSwgbm8gcG9pbnQgb24gaW5zaXN0aW5nIHRoYXQgc29sdXRpb25zIHdvdWxkIHN1
cHBvcnQgNDI4NSwgaWYgNDI4NTxCUj4mZ3Q7ICZndDsgcmVxdWlyZW1lbnRzIGFyZSBub3QgaW5j
bHVkZWQuIEkgY2FuIHRoaW5rIG9mIGFzcGVjdHMgb2YgNDI4NSB0aGF0IGNhbiBiZTxCUj4mZ3Q7
ICZndDsgcHJvYmxlbWF0aWMsIGJ1dCB3b24ndCBtZW50aW9uIHRoZW0gbm93LCBzaW5jZSBJIGRv
bid0IHdhbnQgdG8gYmUgYWNjdXNlZCBvZjxCUj4mZ3Q7ICZndDsgb3BlbmluZyB0aGUgcGFuZG9y
YSdzIGJveCB3aGlsZSBhYWEtaGEtZ29hbHMgaXMgZ29pbmcgdGhyb3VnaCBsYXN0IGNhbGwgb3I8
QlI+Jmd0OyAmZ3Q7IHRoZSBkaW1lIGRvY3MgYXJlIHVuZGVyd2F5IDopPEJSPiZndDsgJmd0OzxC
Uj4mZ3Q7ICZndDsgV2Ugc2hvdWxkIG5vdCBtYWtlIGNsYWltcyB3ZSBjYW5ub3QgYmFjayB1cCBs
YXRlciBhcyB0aGF0IG1pZ2h0IGRlcmFpbCB0aGU8QlI+Jmd0OyAmZ3Q7IHN0YW5kYXJkaXphdGlv
biBwcm9jZXNzIHR3byB5ZWFycyBmcm9tIG5vdy4gQXMgUGVyc2lhbnMgc2F5IChhZnRlciBhIGxv
dXN5PEJSPiZndDsgJmd0OyBtYXJrZXRpbmcgdHJhbnNsYXRpb24pICJBIHNtYWxsIHF1YXJyZWwg
aW4gdGhlIGJlZ2lubmluZyBiZXR0ZXIgdGhhbiBhPEJSPiZndDsgJmd0OyBibG9vZHkgcGVhY2Ug
YXQgdGhlIGVuZCI8QlI+Jmd0OyAmZ3Q7PEJSPiZndDsgJmd0OzxCUj4mZ3Q7ICZndDs8QlI+Jmd0
OyAmZ3Q7IFIsPEJSPiZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgTWFkamlkPEJSPiZndDsgJmd0OzxC
Uj4mZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPEJSPiZn
dDsgJmd0OyBGcm9tOiBZb3NoaWhpcm8gT2hiYSBbPEEgaHJlZj0ibWFpbHRvOnlvaGJhQHRhcmku
dG9zaGliYS5jb20iIHRhcmdldD1fYmxhbms+bWFpbHRvOnlvaGJhQHRhcmkudG9zaGliYS5jb208
L0E+XTxCUj4mZ3Q7ICZndDsgU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMTksIDIwMDYgMTozMyBQ
TTxCUj4mZ3Q7ICZndDsgVG86IE1hZGppZCBOYWtoamlyaTxCUj4mZ3Q7ICZndDsgQ2M6ICdHZXJh
cmRvIEdpYXJldHRhJzsgJ1ZpamF5IERldmFyYXBhbGxpJzsgbWlwNkBpZXRmLm9yZzsgZGltZUBp
ZXRmLm9yZzxCUj4mZ3Q7ICZndDsgU3ViamVjdDogUmU6IFtNaXA2XSBSRTogW0RpbWVdIEltcGFj
dCBvZiBSRkMgNDI4NSBmb3IgRGlhbWV0ZXIgTUlQNjxCUj4mZ3Q7ICZndDsgQm9vdHN0cmFwcGlu
ZyBXb3JrPEJSPiZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgTWFkamlkLDxCUj4mZ3Q7ICZndDs8QlI+
Jmd0OyAmZ3Q7IE9uIFRodSwgT2N0IDE5LCAyMDA2IGF0IDAxOjA0OjA0UE0gLTA3MDAsIE1hZGpp
ZCBOYWtoamlyaSB3cm90ZTo8QlI+Jmd0OyAmZ3Q7ICZndDsgT2ssIHNvIEkgc2VlIEkgc3BlbmQg
YSBsb25nIGVtYWlsIHdpdGhvdXQgcmVhZGluZyB0aGUgcmVzdCBvZiB0aGUgdGhyZWFkLjxCUj4m
Z3Q7ICZndDsgJmd0OyBEbyB3ZSBmZWVsIHRoZSBBQUEgZ29hbCBkcmFmdCBlZmZpY2llbnRseSBj
YXB0dXJlcyB0aGUgNDI4NSByZXF1aXJlbWVudHM/PEJSPiZndDsgJmd0OyAmZ3Q7IElmIHllcywg
c29ycnkgZm9yIGNsb2dnaW5nIHlvdXIgbWFpbGJveGVzLi48QlI+Jmd0OyAmZ3Q7PEJSPiZndDsg
Jmd0OyBUaGF0IGlzIG15IGZlZWxpbmcgYW5kIGlzIHdoeSBJIGhhZCB0aGUgZm9sbG93aW5nIGNv
bW1lbnQgb24gYWFhLWhhLWdvYWxzPEJSPiZndDsgJmd0OyBkcmFmdDo8QlI+Jmd0OyAmZ3Q7PEJS
PiZndDsgJmd0OyAiPEJSPiZndDsgJmd0OyZuYnNwOyZuYnNwOyBZTzogVGhpcyBkb2N1bWVudCBz
ZWVtcyB0byBhc3N1bWUgdGhlIHVzZSBvZiBJUHNlYyBiZXR3ZWVuIE1OIGFuZCBIQTxCUj4mZ3Q7
ICZndDsmbmJzcDsmbmJzcDsgZm9yIHNlY3VyaW5nIE1vYmlsZSBJUHY2IHNpZ25hbGluZy4mbmJz
cDsgQnV0IHRoZSBBQUEgaW50ZXJmYWNlIGNvdWxkPEJSPiZndDsgJmd0OyZuYnNwOyZuYnNwOyBh
bHNvIGJlIHVzZWQgZm9yIFJGQyA0Mjg1LiZuYnNwOyBTbyBJIHRoaW5rIGl0IG1pZ2h0IGJlIGdv
b2QgdG8gbWVudGlvbjxCUj4mZ3Q7ICZndDsmbmJzcDsmbmJzcDsgaW4gdGhpcyBzZWN0aW9uIHRo
YXQgdGhlIGRvY3VtZW50IG1heSBub3QgcHJlY2x1ZGUgdGhlIHVzZSBvZjxCUj4mZ3Q7ICZndDsm
bmJzcDsmbmJzcDsgYWx0ZXJuYXRpdmUgbWV0aG9kcyBmb3Igc2VjdXJpbmcgTW9iaWxlIElQdjYg
c2lnbmFsaW5nIGJldHdlZW4gTU48QlI+Jmd0OyAmZ3Q7Jm5ic3A7Jm5ic3A7IGFuZCBIQSB3aGls
ZSB0aGlzIGRvY3VtZW50IGZvY3VzZXMgb24gdGhlIHVzZSBvZiBJUHNlYyBiZXR3ZWVuIE1OPEJS
PiZndDsgJmd0OyZuYnNwOyZuYnNwOyBhbmQgSEEuPEJSPiZndDsgJmd0OyAiPEJSPiZndDsgJmd0
OzxCUj4mZ3Q7ICZndDsgWW9zaGloaXJvIE9oYmE8QlI+Jmd0OyAmZ3Q7PEJSPiZndDsgJmd0OzxC
Uj4mZ3Q7ICZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgJmd0OyBSLDxCUj4mZ3Q7ICZndDsgJmd0OzxC
Uj4mZ3Q7ICZndDsgJmd0OyBNYWRqaWQ8QlI+Jmd0OyAmZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7ICZn
dDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08QlI+Jmd0OyAmZ3Q7ICZndDsgRnJvbTogR2Vy
YXJkbyBHaWFyZXR0YSBbPEEgaHJlZj0ibWFpbHRvOmdlcmFyZG8uZ2lhcmV0dGFAZ21haWwuY29t
IiB0YXJnZXQ9X2JsYW5rPm1haWx0bzpnZXJhcmRvLmdpYXJldHRhQGdtYWlsLmNvbTwvQT5dPEJS
PiZndDsgJmd0OyAmZ3Q7IFNlbnQ6IEZyaWRheSwgT2N0b2JlciAxMywgMjAwNiAxMjozNyBBTTxC
Uj4mZ3Q7ICZndDsgJmd0OyBUbzogVmlqYXkgRGV2YXJhcGFsbGk8QlI+Jmd0OyAmZ3Q7ICZndDsg
Q2M6IG1pcDZAaWV0Zi5vcmc7IGRpbWVAaWV0Zi5vcmc8QlI+Jmd0OyAmZ3Q7ICZndDsgU3ViamVj
dDogUmU6IFtEaW1lXSBJbXBhY3Qgb2YgUkZDIDQyODUgZm9yIERpYW1ldGVyIE1JUDYgQm9vdHN0
cmFwcGluZzxCUj4mZ3Q7ICZndDsgV29yazxCUj4mZ3Q7ICZndDsgJmd0OzxCUj4mZ3Q7ICZndDsg
Jmd0OyAmZ3Q7ICZndDsgaW4gdGhlIERJTUUgd29ya2luZyBncm91cCB3ZSBhcmUgY3VycmVudGx5
IHByb2R1Y2luZyBkb2N1bWVudHMgdGhhdDxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgcmVs
YXRlIHRvIHRoZSBiYWNrZW5kIHNvbHV0aW9uIG9mIHRoZTxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7
ICZndDs8QlI+Jmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7ICogSW50ZWdyYXRlZCBTY2VuYXJpbzxC
Uj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsmbmJzcDsmbmJzcDsgZHJhZnQtaWV0Zi1taXA2LWJv
b3RzdHJhcHBpbmctaW50ZWdyYXRlZC1kaGMtMDE8QlI+Jmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7
PEJSPiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyAqIFNwbGl0IFNjZW5hcmlvPEJSPiZndDsgJmd0
OyAmZ3Q7ICZndDsgJmd0OyZuYnNwOyZuYnNwOyBkcmFmdC1pZXRmLW1pcDYtYm9vdHN0cmFwcGlu
Zy1zcGxpdC0wMjxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7ICZndDsg
Jmd0OyAmZ3Q7IE5vdywgdGhlIHF1ZXN0aW9uIGNhbWUgdXAgd2hldGhlciB3ZSBoYXZlIHRvIGNv
bnNpZGVyIFJGQyA0Mjg1PEJSPiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyAoJ0F1dGhlbnRpY2F0
aW9uIFByb3RvY29sIGZvciBNb2JpbGUgSVB2NicpIGZvciBvdXIgd29yayBhcyB3ZWxsLjxCUj4m
Z3Q7ICZndDsgJmd0OyAmZ3Q7PEJSPiZndDsgJmd0OyAmZ3Q7ICZndDsgY3VycmVudGx5IGl0IGlz
IG5vdCBjbGVhciBpZiB3ZSBhcmUgZ29pbmcgdG8gZG8gYW55PEJSPiZndDsgJmd0OyAmZ3Q7ICZn
dDsgZnVydGhlciB3b3JrIG9uIFJGQyA0Mjg1IGluIHRoZSBNSVA2IFdHLiBzbyBteTxCUj4mZ3Q7
ICZndDsgJmd0OyAmZ3Q7IHN1Z2dlc3Rpb24gaXMgdG8gYXNzdW1lIG9ubHkgdGhlIHVzZSBvZiBJ
S0V2MiAod2l0aDxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7IGFuZCB3aXRob3V0IEVBUCkuPEJSPiZn
dDsgJmd0OyAmZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7ICZndDsgQWdy
ZWUgd2l0aCBWaWpheSwgdGhpcyBpcyBhbHNvIHRoZSBhc3N1bXB0aW9uIGZvciB0aGUgQUFBIGdv
YWxzIGRyYWZ0LjxCUj4mZ3Q7ICZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgJmd0OyAtLUdlcmFyZG88
QlI+Jmd0OyAmZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7ICZndDsgJmd0OyBidXQgaXQgd291bGQgYmUg
Z29vZCB0byBrZWVwIHRoZSBzb2x1dGlvbiBmbGV4aWJsZTxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7
IHNvIHRoYXQgaXQgY2FuIGJlIGV4dGVuZGVkIGxhdGVyIGZvciA0Mjg1IGlmIHJlcXVpcmVkLjxC
Uj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7PEJSPiZndDsgJmd0OyAmZ3Q7ICZndDsgVmlqYXk8QlI+Jmd0
OyAmZ3Q7ICZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPiZndDsgJmd0OyAmZ3Q7ICZndDsgRGlN
RSBtYWlsaW5nIGxpc3Q8QlI+Jmd0OyAmZ3Q7ICZndDsgJmd0OyBEaU1FQGlldGYub3JnPEJSPiZn
dDsgJmd0OyAmZ3Q7ICZndDsgPEEgaHJlZj0iaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vZGltZSIgdGFyZ2V0PV9ibGFuaz5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9kaW1lPC9BPjxCUj4mZ3Q7ICZndDsgJmd0OyAmZ3Q7PEJSPiZndDsgJmd0OyAm
Z3Q7PEJSPiZndDsgJmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPEJSPiZndDsgJmd0OyAmZ3Q7IERpTUUgbWFpbGluZyBsaXN0PEJSPiZndDsg
Jmd0OyAmZ3Q7IERpTUVAaWV0Zi5vcmc8QlI+Jmd0OyAmZ3Q7ICZndDsgPEEgaHJlZj0iaHR0cHM6
Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGltZSIgdGFyZ2V0PV9ibGFuaz5odHRw
czovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaW1lPC9BPjxCUj4mZ3Q7ICZndDsg
Jmd0OzxCUj4mZ3Q7ICZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgJmd0OzxCUj4mZ3Q7ICZndDsgJmd0
OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxCUj4mZ3Q7
ICZndDsgJmd0OyBNaXA2IG1haWxpbmcgbGlzdDxCUj4mZ3Q7ICZndDsgJmd0OyBNaXA2QGlldGYu
b3JnPEJSPiZndDsgJmd0OyAmZ3Q7IDxBIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL21pcDYiIHRhcmdldD1fYmxhbms+aHR0cHM6Ly93d3cxLmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbWlwNjwvQT48QlI+Jmd0OyAmZ3Q7ICZndDs8QlI+Jmd0OyAmZ3Q7PEJS
PiZndDsgJmd0OzxCUj4mZ3Q7ICZndDs8QlI+Jmd0OzxCUj4mZ3Q7IF9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPiZndDsgRGlNRSBtYWlsaW5nIGxpc3Q8
QlI+Jmd0OyBEaU1FQGlldGYub3JnPEJSPiZndDsgPEEgaHJlZj0iaHR0cHM6Ly93d3cxLmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZGltZSIgdGFyZ2V0PV9ibGFuaz5odHRwczovL3d3dzEuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaW1lPC9BPjxCUj4mZ3Q7PEJSPjxCUj5fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxCUj5EaU1FIG1haWxpbmcgbGlz
dDxCUj5EaU1FQGlldGYub3JnPEJSPjxBIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2RpbWUiIHRhcmdldD1fYmxhbms+aHR0cHM6Ly93d3cxLmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vZGltZTwvQT48QlI+PC9GT05UPjwvUD48L0RJVj48L0RJVj48aW1nIHN0
eWxlPSJkaXNwbGF5Om5vbmUiIHdpZHRoPTAgaGVpZ2h0PTAgc3JjPSJodHRwOi8vdW1haWwuZXRy
aS5yZS5rci9FeHRlcm5hbF9SZWFkQ2hlY2suYXNweD9lbWFpbD1taXA2QGlldGYub3JnJm5hbWU9
bWlwNiU0MGlldGYub3JnJmZyb21lbWFpbD1qaGplZUBldHJpLnJlLmtyJm1lc3NhZ2VpZD0lM0Nl
OGNmNjE4OC0wYWRmLTQyZmMtYTI4OS04ZjMzZmYwOGE2MTRAZXRyaS5yZS5rciUzRSI+

------=_NextPart_000_1053_01C6F568.1C95A190--


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

--===============1465414780==--




From mip6-bounces@ietf.org Sun Oct 22 15:46:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbjFO-00027D-2M; Sun, 22 Oct 2006 15:44:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbjFM-000270-8y
	for mip6@ietf.org; Sun, 22 Oct 2006 15:44:36 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbjFJ-0003Lh-NP
	for mip6@ietf.org; Sun, 22 Oct 2006 15:44:36 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 9648A8989C;
	Sun, 22 Oct 2006 22:44:32 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 335988988B;
	Sun, 22 Oct 2006 22:44:32 +0300 (EEST)
Message-ID: <453BC9F7.1020703@piuha.net>
Date: Sun, 22 Oct 2006 22:43:51 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060921)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
References: <44E8B357.9010705@piuha.net> <4519BF97.6070002@azairenet.com>
In-Reply-To: <4519BF97.6070002@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: fb93e867a11a29ac1dc5018706b412ac
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-ikev2-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
>>
>>  >    In case the mobile node reverse tunnels all traffic including
>> Mobile
>>  >    IPv6 signaling messages exchanged between the mobile node and the
>>  >    home agent, then the Home Address Option is not required to be
>>  >    present in the messages sent to the home agent.  The packet format
>>  >    for the binding update when sent in the tunnel mode looks as
>> follows.
>>
>> ...
>>
>>  >    o  ESP encapsulation for Binding Updates and Binding
>> Acknowledgements
>>  >       MUST be supported and used.
>>
>>  >    o  When securing Binding Updates, Binding Acknowledgements, and
>>  >       prefix discovery, both the mobile nodes and the home agents
>> MUST
>>  >       support and SHOULD use the Encapsulating Security Payload (ESP)
>>  >       [6] header in transport mode and MUST use a non-null payload
>>  >       authentication algorithm to provide data origin authentication,
>>  >       connectionless integrity and optional anti-replay protection.
>>
>> The latter requirements are copied from RFC 3776 but they do not seem
>> to say anything about the new, alternate, tunnel mode BU encapsulation.
>> Please specify whether the new encapsulation is a MUST/MAY implement
>> or not.
>
> modified the above paragraph to
>
>    o  When securing Binding Updates, Binding Acknowledgements, and
>       Mobile Prefix Discovery messages, both the mobile node and the
>       home agent MUST support the use of Encapsulating Security Payload
>       (ESP) [6] header in transport mode and MUST use a non-null payload
>       authentication algorithm to provide data origin authentication,
>       connectionless integrity and optional anti-replay protection.
>       Support for protecting these messages using ESP in tunnel mode is
>       optional.
Ok.
>>
>>  >       With dynamic keying, it
>>  >       should be possible for the home agent to verify that the
>> identity
>>  >       presented in the IKE_AUTH exchange is allowed to create
>> security
>>  >       associations for a particular home address.
>>
>> This is weaker than I would like it to be. This check is not optional.
>> Say "... the home agent MUST ..." or something to that effect.
>
> changed it to
>
>       With dynamic keying, the
>       home agent MUST be able to verify that the identity presented in
>       the IKE_AUTH exchange is allowed to create security associations
>       for a particular home address.
Ok.
>>
>>  >    o  The home agent and mobile node SHOULD support Mobility Header
>>  >       message type as an IPsec selector.
>>  >
>>  >    o  The home agent and mobile node SHOULD support ICMPv6 message
>> type
>>  >       as an IPsec selector.
>>
>>  > 5.  Selector Granularity Considerations
>>  >
>>  >    IPsec implementations are compatible with this document even if
>> they
>>  >    do not support fine grain selectors such as the Mobility Header
>>  >    message type and ICMPv6 message type.
>>
>> For this spec it would seem that a MUST requirement for the
>> finer granularity would be better. This would also reduce
>> the number of variant configuration styles that implementations
>> must support, reduce configuration related problems, and
>> enhance interoperability.
>>
>> I am quite concerned about interoperability in the mobility
>> space. We have multiple protocols, they have multiple
>> ways to set up security, multiple operation modes, different
>> configuration options, etc. One of the main reasons we
>> work in organizations like the IETF is that we agree on
>> a standard way to do things (see also RFC 1958).
>>
>> I can see situations where we have to have options and
>> alternate ways. But for that we need a very good reason.
>> Is there such a reason for this? For instance, do we have
>> implementors who have stated they have a problem with
>> the granularity?
>
> this was discussed extensively on the mailing list. version
> 02 of this draft had a MUST against mobility header as a
> selector. see
> http://tools.ietf.org/wg/mip6/draft-ietf-mip6-ikev2-ipsec/draft-ietf-mip6-ikev2-ipsec-02.txt
>
>
> Francis and (I don't remember who else) objected to this.
> it was changed to SHOULD in version 03.

>
>>  >    In the examples shown above, the home address of the mobile node
>>  >    might not be available all the time.  For instance, the mobile
>> node
>>  >    might have not configured a home address yet.  When the mobile
>> node
>>  >    acquires a new home address, it must either add the address to the
>>  >    corresponding SPD entries or create the SPD entries for the home
>>  >    address.
>>
>> Has this procedure been reviewed by IKEv2 experts?
>
> this is not different from regular IPsec VPN process.
> the client acquires an IPsec remote IP address only after
> the configuration payload is received in the last IKE_AUTH
> message. any SPD entry that affects the traffic sent using
> the IPsec remote IP address must be modified after the IPsec
> remote IP address is configured, correct? I didn't see text
> in RFC 4306 which addresses this. I could have missed it....
Ok. I guess we will get additional secdir review for this
anyway.
>>
>>  >    A possible mechanism used for
>>  >    mutual authentication is a shared secret between the mobile
>> node and
>>  >    the home agent.  The home agent uses the identity of the mobile
>> node
>>  >    to identify the corresponding shared secret.  When a public key
>> based
>>  >    mechanism is available, it should be the preferred mechanism for
>>  >    mutual authentication: private keys are used to generate the AUTH
>>  >    payload and identities are verified with certificate information
>>  >    transmitted by CERT payloads.
>>
>> This text fragment has several issues:
>>
>> 1) I am not sure why we are making recommendations about the
>>     mechanism used.
>> 2) Using the identity to identify a shared secret: if this is the usual
>>     IKEv2 procedure, then maybe it is not worth repeating here. If
>>     it is something else, please clarify.
>> 3) Why are we explaining some (but not all) details of the
>>     public key authentication process in IKEv2? The same
>>     issue continues further down in the next paragraph.
>
> IMHO, we should have some text on how the MN is actually
> authenticated by the HA. thats what the 2nd paragraph in
> section 7.2 trying to do. we could refer to RFC 4306 for
> more details at the end of the paragraph.
My issue was precisely the part about "some text".
It is not clear why some details but not all is chosen.
You can explain the high level things as an introductory
explanation, though.
>>  >    The mobile node should always include its identity in the IDi
>> payload
>>  >    in the IKE_AUTH exchange.  The mobile node could use the following
>>  >    different types of identities to identity itself to the home
>> agent.
>>  >
>>  >    o  Home Address - The mobile node could use its statically
>> configured
>>  >       home address as its identity.  In this case the ID Type
>> field is
>>  >       set to ID_IPV6_ADDR.
>>  >    o  FQDN - The mobile node can use a Fully Qualified Domain Name as
>>  >       the identifier and set the ID Type field to ID_FQDN.
>>  >    o  RFC 822 identifier - If the mobile node uses a RFC 822
>> identifier
>>  >       [9], it sets the ID Type field to ID_RFC822_ADDR.
>>
>> It is good that you list the specific identities that devices
>> conformant to this spec need to employ. However, it
>> seems that you are missing one case. When EAP is used
>> within IKEv2, it is possible that the identity provided in the
>> IDi payload is not the final, true identity. See Sections 3.4
>> and 3.5 in draft-eronen-ipsec-ikev2-clarifications-09.txt.
>> I wouldn't bring this up otherwise but I think EAP usage
>> in this application is likely.
>
> good point. we can fix this by adding one sentence at the
> end of above paragraph.
>
>        The above list of identities is not exhaustive.
>
> and in section 8 that talks about the use of EAP, add the
> following.
>
>    When EAP is used, the identity presented by the mobile node in the
>    IDi field may not be the actual identity of the mobile node.  It
>    could be set to an identity that is used only for AAA routing
>    purposes and selecting the right EAP method.  The actual identity is
>    carried inside EAP payloads that is not visible to the home agent.
>    The home agent MUST acquire the mobile node's identity from the
>    corresponding AAA server.  More details can be found in [13].
>
>    [13]  Hoffman, P. and P. Eronen, "IKEv2 Clarifications and
>          Implementation Guidelines",
>          draft-eronen-ipsec-ikev2-clarifications-09 (work in progress),
>          May 2006.
Ok.
>>
>>  >    If the mobile node or the home agent does
>>  >    not support this capability, then an IKEv2 exchange MUST be
>> initiated
>>  >    to re-establish a new IKE SA.
>>
>> This seems too strict. If the K bit functionality is not there,
>> it is still possible that the peers happen to support MOBIKE.
>> The MUST prevents using it. I would phrase this as "If the
>> mobile node or the home agent does not support this capability
>> and has no other means to update the addresses (such as
>> MOBIKE [ref]), then a new IKEv2 exchange MUST be initiated
>> to re-establish another IKE SA."
>
> see http://www.mip4.org/issues/tracker/mip6/issue68. I don't
> believe MOBIKE and MIP6 can be run between the same end
> points simultaneously.
>
> how about
>
>    If the mobile node or the home agent does
>    not support this capability, and has no other means to update the
>    addresses, then an IKEv2 exchange MUST be initiated to re-establish a
>    new IKE SA.
My text but no reference? Ok.
>> > 9.  Dynamic Home Address Configuration
>>
>> This section does not say anything about the use of multiple
>> home addresses for the same mobile node. 
>
> from the same home agent or a different home agent? if its
> the same agent, then I think you can only configure one
> address at a time using the INTERNAL_IP6_ATTRIBUTE. 
Really? RFC 4306 say that "Multiple internal addresses
MAY be requested by requesting multiple internal address
attributes.  The responder MAY only send up to
the number of addresses requested."
> if you
> want multiple addresses, you would have to setup up a
> separate IKE SA and IKE_AUTH with CP request for each
> address.
>
>> I believe this
>> should be allowed. Perhaps you could explicitly mention
>> that it is allowed.
>>
>>  > 7.1.  Security Policy Database Entries
>>
>> The style of presentation in this section is taken from
>> RFC 3776. With the new IPsec architecture, it seems that
>> it would be more appropriate to state the configuration
>> in terms of the PAD and the SPD, rather than in SPD only.
>> I would also like you to go through the examples in both
>> the dynamic and manual keying sections with an RFC 4301
>> expert, to ensure that they are generally written in the
>> way that is in alignment with the current specs.
>
> that would be nice, yes.
>
> but IMO, the SPD description in section 7.1 can be easily
> mapped to whatever is needed in 4301.
> BTW the "SPD-S" comes from 4301.
One expert that I attempted to recruit to help you
indicated that there indeed was a problem. So this
may still be an issue.

Is there a possibility that you could add a discussion
of how the PAD needs to be configured for Mobile IPv6
usage?

--Jari


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



From mip6-bounces@ietf.org Sun Oct 22 19:06:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbmOj-0005W0-Lj; Sun, 22 Oct 2006 19:06:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbmO8-0005Dy-UL; Sun, 22 Oct 2006 19:05:52 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gbm9I-0004PH-W9; Sun, 22 Oct 2006 18:50:34 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Gbm9I-0004u0-Ea; Sun, 22 Oct 2006 18:50:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 1AFB3175A4;
	Sun, 22 Oct 2006 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gbm8n-0006Q8-LW; Sun, 22 Oct 2006 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gbm8n-0006Q8-LW@stiedprstage1.ietf.org>
Date: Sun, 22 Oct 2006 18:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-bootstrapping-split-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		: Mobile IPv6 bootstrapping in split scenario
	Author(s)	: G. Giaretta, et al.
	Filename	: draft-ietf-mip6-bootstrapping-split-03.txt
	Pages		: 36
	Date		: 2006-10-22
	
A Mobile IPv6 node requires a Home Agent address, a home address, 
        and IPsec security associations with its Home Agent before it can 
        start utilizing Mobile IPv6 service. RFC 3775 requires that some 
        or all of these are statically configured. This document defines 
        how a Mobile IPv6 node can bootstrap this information from non-
        topological information and security credentials preconfigured on 
        the Mobile Node. The solution defined in this document solves the 
        bootstrapping problem from draft-ietf-mip6-bootstrapping-ps-02 
        when the Mobile Node's mobility service is authorized by a 
        different service provider than basic network access, and is 
        therefore generically applicable to any bootstrapping case.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-split-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-bootstrapping-split-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-bootstrapping-split-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-22162302.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-bootstrapping-split-03.txt

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

Content-Type: text/plain
Content-ID: <2006-10-22162302.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mip6-bounces@ietf.org Sun Oct 22 19:06:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbmP3-0005qO-JZ; Sun, 22 Oct 2006 19:06:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbmOB-0005Lb-Dm; Sun, 22 Oct 2006 19:05:55 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gbm8q-0004FZ-0h; Sun, 22 Oct 2006 18:50:05 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id A86DB328BE;
	Sun, 22 Oct 2006 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gbm8o-0006Rq-Hh; Sun, 22 Oct 2006 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gbm8o-0006Rq-Hh@stiedprstage1.ietf.org>
Date: Sun, 22 Oct 2006 18:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-ha-switch-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		: Mobility Header Home Agent Switch Message
	Author(s)	: B. Haley, et al.
	Filename	: draft-ietf-mip6-ha-switch-01.txt
	Pages		: 11
	Date		: 2006-10-22
	
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-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-ha-switch-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-ha-switch-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-22174421.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-10-22174421.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mip6-bounces@ietf.org Sun Oct 22 19:06:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbmNt-00054x-6c; Sun, 22 Oct 2006 19:05:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbmNs-0004wL-C7
	for mip6@ietf.org; Sun, 22 Oct 2006 19:05:36 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbmHG-0006E8-3U
	for mip6@ietf.org; Sun, 22 Oct 2006 18:58:55 -0400
Received: from [10.1.210.10] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 22 Oct 2006 15:58:41 -0700
Message-ID: <453BF6E0.9010506@azairenet.com>
Date: Sun, 22 Oct 2006 15:55:28 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <44E8B357.9010705@piuha.net> <4519BF97.6070002@azairenet.com>
	<453BC9F7.1020703@piuha.net>
In-Reply-To: <453BC9F7.1020703@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Oct 2006 22:58:42.0217 (UTC)
	FILETIME=[9EA45990:01C6F62D]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-ikev2-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:

>>>  >    A possible mechanism used for
>>>  >    mutual authentication is a shared secret between the mobile
>>> node and
>>>  >    the home agent.  The home agent uses the identity of the mobile
>>> node
>>>  >    to identify the corresponding shared secret.  When a public key
>>> based
>>>  >    mechanism is available, it should be the preferred mechanism for
>>>  >    mutual authentication: private keys are used to generate the AUTH
>>>  >    payload and identities are verified with certificate information
>>>  >    transmitted by CERT payloads.
>>>
>>> This text fragment has several issues:
>>>
>>> 1) I am not sure why we are making recommendations about the
>>>     mechanism used.
>>> 2) Using the identity to identify a shared secret: if this is the usual
>>>     IKEv2 procedure, then maybe it is not worth repeating here. If
>>>     it is something else, please clarify.
>>> 3) Why are we explaining some (but not all) details of the
>>>     public key authentication process in IKEv2? The same
>>>     issue continues further down in the next paragraph.
>> IMHO, we should have some text on how the MN is actually
>> authenticated by the HA. thats what the 2nd paragraph in
>> section 7.2 trying to do. we could refer to RFC 4306 for
>> more details at the end of the paragraph.

> My issue was precisely the part about "some text".
> It is not clear why some details but not all is chosen.
> You can explain the high level things as an introductory
> explanation, though.

ok. removed some text so that the description is
high level.

    The mobile node initiates an IKEv2 protocol exchange if the required
    security associations are not present.  A possible mechanism used for
    mutual authentication is a shared secret between the mobile node and
    the home agent.  The home agent uses the identity of the mobile node
    to identify the corresponding shared secret.  When a public key based
    mechanism is available, it should be the preferred mechanism for
    mutual authentication.

    If a shared secret is being used, the mobile node uses the shared
    secret to generate the AUTH payload in the IKE_AUTH exchange.  If the
    mobile node is using a public key based mechanism, then it uses its
    private key to generate the AUTH payload in the IKE_AUTH exchange.

>>>> 9.  Dynamic Home Address Configuration
>>> This section does not say anything about the use of multiple
>>> home addresses for the same mobile node. 
>> from the same home agent or a different home agent? if its
>> the same agent, then I think you can only configure one
>> address at a time using the INTERNAL_IP6_ATTRIBUTE. 
> Really? RFC 4306 say that "Multiple internal addresses
> MAY be requested by requesting multiple internal address
> attributes.  The responder MAY only send up to
> the number of addresses requested."

sorry, my bad. I blame it on too much of 3GPP APN and
per-APN IKEv2 SA discussions internally. :)

modified as follows

    The mobile node can dynamically configure a home address by including
    a Configuration Payload in the IKE_AUTH exchange, with a request for
    an address from the home link.  The mobile node should include a
    zero-length INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST
    Payload.  The mobile node MAY include multiple instances of the
    INTERNAL_IP6_ADDRESS to request multiple home address to the assigned
    by the home agent.

note that if you include multiple
INTERNAL_IP6_ADDRESS attributes in the CFG_REQUEST,
you get multiple addresses from the same prefix. when
applied to MIPv6 this will result in multiple home
address from the same prefix.

>>>  > 7.1.  Security Policy Database Entries
>>>
>>> The style of presentation in this section is taken from
>>> RFC 3776. With the new IPsec architecture, it seems that
>>> it would be more appropriate to state the configuration
>>> in terms of the PAD and the SPD, rather than in SPD only.
>>> I would also like you to go through the examples in both
>>> the dynamic and manual keying sections with an RFC 4301
>>> expert, to ensure that they are generally written in the
>>> way that is in alignment with the current specs.
>> that would be nice, yes.
>>
>> but IMO, the SPD description in section 7.1 can be easily
>> mapped to whatever is needed in 4301.
>> BTW the "SPD-S" comes from 4301.
> One expert that I attempted to recruit to help you
> indicated that there indeed was a problem. So this
> may still be an issue.

it will good to get a review and/or help from this
person.

> Is there a possibility that you could add a discussion
> of how the PAD needs to be configured for Mobile IPv6
> usage?

we have some text.

    o  The home agent MAY use the Peer Authorization Database (PAD) [5]
       to store per-mobile node state.  The PAD entry for a mobile node
       MAY contain a shared key, public key or a trust anchor to verify
       the mobile node's certificate for authenticating the mobile node.

AFAIK, the PAD entries are created either manually or
delivered via some proprietary interface.

RFC 4306 avoids talking about PAD completely. so the
usage of PAD with IKEv2 is not clear to me.

Vijay

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



From mip6-bounces@ietf.org Sun Oct 22 23:49:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbqnJ-0002yk-Kw; Sun, 22 Oct 2006 23:48:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbqnI-0002yZ-Ct
	for mip6@ietf.org; Sun, 22 Oct 2006 23:48:08 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbqnG-0002UU-SY
	for mip6@ietf.org; Sun, 22 Oct 2006 23:48:08 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 3CA2E898A9;
	Mon, 23 Oct 2006 06:48:03 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id AB3DE898A6;
	Mon, 23 Oct 2006 06:48:02 +0300 (EEST)
Message-ID: <453C3B49.8070103@piuha.net>
Date: Mon, 23 Oct 2006 06:47:21 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060921)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
References: <44E8B357.9010705@piuha.net> <4519BF97.6070002@azairenet.com>
	<453BC9F7.1020703@piuha.net> <453BF6E0.9010506@azairenet.com>
In-Reply-To: <453BF6E0.9010506@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: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-ikev2-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
>
> ok. removed some text so that the description is
> high level.
>
>    The mobile node initiates an IKEv2 protocol exchange if the required
>    security associations are not present.  A possible mechanism used for
>    mutual authentication is a shared secret between the mobile node and
>    the home agent.  The home agent uses the identity of the mobile node
>    to identify the corresponding shared secret.  When a public key based
>    mechanism is available, it should be the preferred mechanism for
>    mutual authentication.
>
>    If a shared secret is being used, the mobile node uses the shared
>    secret to generate the AUTH payload in the IKE_AUTH exchange.  If the
>    mobile node is using a public key based mechanism, then it uses its
>    private key to generate the AUTH payload in the IKE_AUTH exchange.
Ok.
>
>>>>> 9.  Dynamic Home Address Configuration
>>>> This section does not say anything about the use of multiple
>>>> home addresses for the same mobile node. 
>>> from the same home agent or a different home agent? if its
>>> the same agent, then I think you can only configure one
>>> address at a time using the INTERNAL_IP6_ATTRIBUTE. 
>> Really? RFC 4306 say that "Multiple internal addresses
>> MAY be requested by requesting multiple internal address
>> attributes.  The responder MAY only send up to
>> the number of addresses requested."
>
> sorry, my bad. I blame it on too much of 3GPP APN and
> per-APN IKEv2 SA discussions internally. :)
>
> modified as follows
>
>    The mobile node can dynamically configure a home address by including
>    a Configuration Payload in the IKE_AUTH exchange, with a request for
>    an address from the home link.  The mobile node should include a
>    zero-length INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST
>    Payload.  The mobile node MAY include multiple instances of the
>    INTERNAL_IP6_ADDRESS to request multiple home address to the assigned
>    by the home agent.
>
> note that if you include multiple
> INTERNAL_IP6_ADDRESS attributes in the CFG_REQUEST,
> you get multiple addresses from the same prefix. when
> applied to MIPv6 this will result in multiple home
> address from the same prefix.
Ok.
>>>>  > 7.1.  Security Policy Database Entries
>>>>
>>>> The style of presentation in this section is taken from
>>>> RFC 3776. With the new IPsec architecture, it seems that
>>>> it would be more appropriate to state the configuration
>>>> in terms of the PAD and the SPD, rather than in SPD only.
>>>> I would also like you to go through the examples in both
>>>> the dynamic and manual keying sections with an RFC 4301
>>>> expert, to ensure that they are generally written in the
>>>> way that is in alignment with the current specs.
>>> that would be nice, yes.
>>>
>>> but IMO, the SPD description in section 7.1 can be easily
>>> mapped to whatever is needed in 4301.
>>> BTW the "SPD-S" comes from 4301.
>> One expert that I attempted to recruit to help you
>> indicated that there indeed was a problem. So this
>> may still be an issue.
>
> it will good to get a review and/or help from this
> person.
>
>> Is there a possibility that you could add a discussion
>> of how the PAD needs to be configured for Mobile IPv6
>> usage?
>
> we have some text.
>
>    o  The home agent MAY use the Peer Authorization Database (PAD) [5]
>       to store per-mobile node state.  The PAD entry for a mobile node
>       MAY contain a shared key, public key or a trust anchor to verify
>       the mobile node's certificate for authenticating the mobile node.
>
> AFAIK, the PAD entries are created either manually or
> delivered via some proprietary interface.
>
> RFC 4306 avoids talking about PAD completely. so the
> usage of PAD with IKEv2 is not clear to me.
The text that you quoted above is about
the additional things you could store in PAD.
I am asking what the PAD as described in 4301
will do in your application and how it needs
to be configured.

I will try to recruit 4301 experts to help you
on this.

Overall, I think we are close to being able to
move your latest version forward in the process,
though I still worry about the 4301 compatibility.
But perhaps we can indicate this as an issue
and ask for help while we simultaneously run
the Last Call.

--Jari


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



From mip6-bounces@ietf.org Mon Oct 23 03:06:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gbtt8-0001Ij-FO; Mon, 23 Oct 2006 03:06:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbtsK-0008Ql-6c; Mon, 23 Oct 2006 03:05:32 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GbtdK-0005wR-U5; Mon, 23 Oct 2006 02:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id DDFF026E5A;
	Mon, 23 Oct 2006 06:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GbtdK-0006SC-M0; Mon, 23 Oct 2006 02:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GbtdK-0006SC-M0@stiedprstage1.ietf.org>
Date: Mon, 23 Oct 2006 02:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-location-privacy-ps-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		: IP Address Location Privacy and Mobile IPv6:  Problem Statement
	Author(s)	: R. Koodli
	Filename	: draft-ietf-mip6-location-privacy-ps-03.txt
	Pages		: 8
	Date		: 2006-10-22
	
In this document, we discuss Location Privacy as applicable to
    Mobile IPv6.  We document the concerns arising from revealing Home
    Address to an on-looker and from disclosing Care of Address to a
    correspondent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-location-privacy-ps-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-location-privacy-ps-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-location-privacy-ps-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-22182423.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-location-privacy-ps-03.txt

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

Content-Type: text/plain
Content-ID: <2006-10-22182423.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Mon Oct 23 04:19:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gbv1c-0004Jr-IG; Mon, 23 Oct 2006 04:19:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbv1b-0004Jj-Fy
	for mip6@ietf.org; Mon, 23 Oct 2006 04:19:11 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gbv1a-0006HU-4W
	for mip6@ietf.org; Mon, 23 Oct 2006 04:19:11 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9N8J7R1031151
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 23 Oct 2006 01:19:07 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9N8J6oW001077; Mon, 23 Oct 2006 01:19:06 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Oct 2006 01:19:05 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Oct 2006 01:19:05 -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] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Mon, 23 Oct 2006 01:19:02 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24AAD3@NAEX14.na.qualcomm.com>
In-Reply-To: <4538F0B2.3080403@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: Acb0YCr/qsqZOvNWSzqLJsrY5D397QCGwCgw
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 23 Oct 2006 08:19:05.0816 (UTC)
	FILETIME=[E7DE6580:01C6F67B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 For the benefit of the list I'm repeating what I already told Vijay in
a private mail.


 > >  > from what I remember we wanted to relax the MUST
 > >  > requirement at the HA to always the CoA in the
 > >  > alt-CoA option when there is a NAT present.
 > >=20
 > > =3D> Right, but please s/when a NAT is present/when in an=20
 > IPv4 network.
 >=20
 > nope. the HA needs to relax the requirement only
 > when it detects a NAT, not because the MN is on
 > an IPv4 access network.
 >=20

=3D> This can't work because the HA has no way of knowing whether the =
src
address in the v6 header is different because of NAT or due to a
legitimate use of the alt-coa option. So the HA can't decide whether a
NAT is detected or not by comparing the v4 and v6 headers if the alt-coa
may be found later. The only way to detect a NAT beased on the v4/v6
headers comparison is to remove the alt-coa option.


 > > =3D> That's fine, so you just express that opinion for this=20
 > new issue. All
 > > I said was that the checksum (the need for it) will be a=20
 > separate issue
 > > since we agreed on the other part (relaxing of 3775).=20
 >=20
 > lets be clear on what we agreed to relax. only the
 > MUST requirement on the HA to use the CoA in the
 > alt-CoA option all the time.

=3D> I don't think you could have agreed with that because it was never
suggested. Neither the issue text nor my analysis/recommendation ever
suggested this approach. Both clearly suggested ommitting the alt-coa
option.=20

Hesham

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



From mip6-bounces@ietf.org Mon Oct 23 07:18:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbxoR-0005x0-3z; Mon, 23 Oct 2006 07:17:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbxoO-0005uT-U0; Mon, 23 Oct 2006 07:17:44 -0400
Received: from mail1.rz.fhtw-berlin.de ([141.45.5.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gbxb7-0000Cg-TW; Mon, 23 Oct 2006 07:04:06 -0400
Received: from e178167002.adsl.alicedsl.de ([85.178.167.2]
	helo=[192.168.178.25])
	by mail1.rz.fhtw-berlin.de with esmtpsa (SSLv3:AES256-SHA:256)
	(Exim 4.42 (FreeBSD))
	id 1Gbxau-000CCN-Gz; Mon, 23 Oct 2006 13:03:48 +0200
Message-ID: <453CA23F.5050800@fhtw-berlin.de>
Date: Mon, 23 Oct 2006 13:06:39 +0200
From: Thomas C Schmidt <schmidt@fhtw-berlin.de>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
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: 8b431ad66d60be2d47c7bfeb879db82c
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-01.txt

Details:


               Multicast Mobility in MIPv6: Problem Statement
                   <draft-schmidt-mobopts-mmcastv6-ps-01.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 not only accounts for all comments / reviews given so 
far, but has been extended significantly to incorporate

  o Deployment issues;
  o Current research on the characteristics of multicast routing trees
    under mobility;
  o Fairly exhaustive exploration of the solution space;
  o A large collection of references on various aspects of the subject.


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 San Diego,

thomas


_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts

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

From mip6-bounces@ietf.org Mon Oct 23 07:18:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbxoJ-0005sV-Po; Mon, 23 Oct 2006 07:17:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbxoI-0005rK-61
	for mip6@ietf.org; Mon, 23 Oct 2006 07:17:38 -0400
Received: from nf-out-0910.google.com ([64.233.182.189])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gbxci-0000St-Go
	for mip6@ietf.org; Mon, 23 Oct 2006 07:05:42 -0400
Received: by nf-out-0910.google.com with SMTP id nFrom mip6-bounces@ietf.org Mon Oct 23 07:18:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbxoR-0005x0-3z; Mon, 23 Oct 2006 07:17:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbxoO-0005uT-U0; Mon, 23 Oct 2006 07:17:44 -0400
Received: from mail1.rz.fhtw-berlin.de ([141.45.5.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gbxb7-0000Cg-TW; Mon, 23 Oct 2006 07:04:06 -0400
Received: from e178167002.adsl.alicedsl.de ([85.178.167.2]
	helo=[192.168.178.25])
	by mail1.rz.fhtw-berlin.de with esmtpsa (SSLv3:AES256-SHA:256)
	(Exim 4.42 (FreeBSD))
	id 1Gbxau-000CCN-Gz; Mon, 23 Oct 2006 13:03:48 +0200
Message-ID: <453CA23F.5050800@fhtw-berlin.de>
Date: Mon, 23 Oct 2006 13:06:39 +0200
From: Thomas C Schmidt <schmidt@fhtw-berlin.de>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
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: 8b431ad66d60be2d47c7bfeb879db82c
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-01.txt

Details:


               Multicast Mobility in MIPv6: Problem Statement
                   <draft-schmidt-mobopts-mmcastv6-ps-01.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 not only accounts for all comments / reviews given so 
far, but has been extended significantly to incorporate

  o Deployment issues;
  o Current research on the characteristics of multicast routing trees
    under mobility;
  o Fairly exhaustive exploration of the solution space;
  o A large collection of references on various aspects of the subject.


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 San Diego,

thomas


_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts

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

From mip6-bounces@ietf.org Mon Oct 23 07:18:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GbxoJ-0005sV-Po; Mon, 23 Oct 2006 07:17:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GbxoI-0005rK-61
	for mip6@ietf.org; Mon, 23 Oct 2006 07:17:38 -0400
Received: from nf-out-0910.google.com ([64.233.182.189])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gbxci-0000St-Go
	for mip6@ietf.org; Mon, 23 Oct 2006 07:05:42 -0400
Received: by nf-out-0910.google.com with SMTP id n15so2494344nfc
	for <mip6@ietf.org>; Mon, 23 Oct 2006 04:05:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=rvAkpdEV7a86GWRUqno/Xr80bS3qCTEEL8xUg/Y/cjLswjXUS33n6WYlX+B3jzzqwvfmmJUPk374DBfYPKVs3k9YDjPcuAFGUmAd1CeFbsya4Uh8pzeWyOuV9Dq3J+w+DFSobn2wOqlXpojPnN7G6hz/qWno+IIfZogBa8I90D4=
Received: by 10.82.98.13 with SMTP id v13mr1267597bub;
	Mon, 23 Oct 2006 04:05:39 -0700 (PDT)
Received: by 10.82.130.20 with HTTP; Mon, 23 Oct 2006 04:05:38 -0700 (PDT)
Message-ID: <5e2406980610230405r402a23cbj71937ec220de6db0@mail.gmail.com>
Date: Mon, 23 Oct 2006 13:05:39 +0200
From: "Julien Bournelle" <julien.bournelle@gmail.com>
To: "=?EUC-KR?B?wfbBpMjG?=" <jhjee@etri.re.kr>
Subject: Re: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter
	MIP6Bootstrapping Work
In-Reply-To: <105201c6f51c$acadf990$8310fe81@etri.info>
MIME-Version: 1.0
References: <Acb1HKyr1NUiuWXXRKWXTWauasW09w==>
	<105201c6f51c$acadf990$8310fe81@etri.info>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: mip6@ietf.org, dime@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="===============1780442116=="
Errors-To: mip6-bounces@ietf.org

--===============1780442116==
Content-Type: text/plain; charset=EUC-KR; format=flowed
Content-Transfer-Encoding: base64
Content-Disposition: inline

SGkganVuZ2hvb24sIGFsbCwKCk9uIDEwLzIxLzA2LCDB9sGkyMYgPGpoamVlQGV0cmkucmUua3I+
IHdyb3RlOgo+Cj4KPiBIaSBKdWxpZW4sCj4gRG9lcyB5b3VyIHRob3VnaHQgaW1wbHkgdGhhdCB0
aGUgcGlnZ3liYWNraW5nIHRoZSBNSVB2NiBCVSB0byB0aGUgQUFBIG1lc3NhZ2VzPwoKIElmIHRo
ZSBNTiB1c2VzIHRoZSBNTi1BQUEgQXV0aGVudGljYXRpb24gb3B0aW9uLCBJIGd1ZXNzIHRoZSBC
VSBtYXkKYmUgcGlnZ3liYWNrZWQuCgogSnVsaWVuCgo+Cj4gLUp1bmdob29uCj4KPiAtLS0tLb/4
ursguN69w8H2LS0tLS0KPiC6uLO9ILvntvc6ICJKdWxpZW4gQm91cm5lbGxlIiA8anVsaWVuLmJv
dXJuZWxsZUBnbWFpbC5jb20+Cj4gurizvSCzr8KlOiAyMDA2LTEwLTIwIL/AyMQgNjozMDoxMgo+
ILnetMIgu+e29zogIkdlcmFyZG8gR2lhcmV0dGEiIDxnZXJhcmRvLmdpYXJldHRhQGdtYWlsLmNv
bT4KPiDC/MG2OiAibWlwNkBpZXRmLm9yZyIgPG1pcDZAaWV0Zi5vcmc+LCAiZGltZUBpZXRmLm9y
ZyIgPGRpbWVAaWV0Zi5vcmc+Cj4gwaa48TogUmU6IFtNaXA2XSBSRTogW0RpbWVdIEltcGFjdCBv
ZiBSRkMgNDI4NSBmb3IgRGlhbWV0ZXIgTUlQNkJvb3RzdHJhcHBpbmcgV29yawo+Cj4KPgo+Cj4K
Pgo+IEhpIGFsbCwKPgo+ICBjb25jZXJuaW5nIHN1cHBvcnQgZm9yIHJmYzQyODUsIEkgdGhpbmsg
d2UnbGwgbmVlZCBtZXNzYWdlcyB0byBjYXJyeSB0aGUgQlUKPiAgZnJvbSB0aGUgSEEgdG8gdGhl
IEFBQUggZm9yIHRoZSBhdXRoZW50aWZjYXRpb24uIEFzIHN1Y2gsIGEgbmV3IGFwcGxpY2F0aW9u
Cj4gIG1heSBiZSBuZWNlc3NhcnkuIEFzIGEgY29uc2VxdWVuY2UsIHRoZSBhdXRob3JpemF0aW9u
IGFuZCBhY2NvdW50aW5nIHBhcnQKPiAgbWF5IGJlIGhhbmRsZWQgYnkgdGhlIHNhbWUgYXBwbGlj
YXRpb24uCj4KPiAgVGhpcyBhcHBsaWNhdGlvbiB3b3VsZCBiZSBzaW1pbGFyIHRvIHRoZSBSRkM0
MDA0ICh3aXRob3V0IEZBLi4uKS4KPgo+ICBKdXN0IG15IDIgY2VudHMsCj4KPiAgSnVsaWVuCj4K
PiBPbiAxMC8yMC8wNiwgR2VyYXJkbyBHaWFyZXR0YSA8Z2VyYXJkby5naWFyZXR0YUBnbWFpbC5j
b20+IHdyb3RlOgo+ID4gSGkgWW9zaGkgYW5kIE1hZGppZCwKPiA+Cj4gPiB0aGUgQUFBIGdvYWxz
IGRyYWZ0IGRvZXMgbm90IGluY2x1ZGUgYW55IHNwZWNpZmljIGdvYWwgZm9yIHJmYzQyODUuCj4g
PiBUaGlzIGlzc3VlIHdhcyByYWlzZWQgaW4gTW9udHJlYWwgYW5kIGR1cmluZyBNSVA2IHJlLWNo
YXJ0ZXJpbmcKPiA+IGRpc2N1c3Npb24uIFRoZSBvdXRjb21lIG9mIHRoZSBkaXNjdXNzaW9uIHdh
cyB0aGF0IHRoZXJlIGlzIG5vIGEgY2xlYXIKPiA+IGludGVyZXN0IG5vdyBpbiB0aGUgSUVURiB0
byBzdGFuZGFyZGl6ZSBhIGJvb3RzdHJhcHBpbmcgc29sdXRpb24gZm9yCj4gPiByZmM0Mjg1IGFu
ZCBhIERpYW1ldGVyIEFwcGxpY2F0aW9uIHRoYXQgc3VwcG9ydHMgcmZjNDI4NS4gTUlQNiBjaGFp
cnMKPiA+IGFuZCBKYXJpIG1lbnRpb25lZCB0aGF0IHRoZXkgbWF5IGFzayBmb3IgcmZjNDI4NSBz
dXBwb3J0IGlmCj4gPiBzaWduaWZpY2FudCBpbnRlcmVzdCB3aWxsIGJlIHJhaXNlZC4gUmVtZW1i
ZXIgYWxzbyB0aGF0IHJmYzQyODUgaXMKPiA+IGluZm9ybWF0aW9uYWwgYW5kIHRoZSBE15so2494344nfc
	for <mip6@ietf.org>; Mon, 23 Oct 2006 04:05:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=rvAkpdEV7a86GWRUqno/Xr80bS3qCTEEL8xUg/Y/cjLswjXUS33n6WYlX+B3jzzqwvfmmJUPk374DBfYPKVs3k9YDjPcuAFGUmAd1CeFbsya4Uh8pzeWyOuV9Dq3J+w+DFSobn2wOqlXpojPnN7G6hz/qWno+IIfZogBa8I90D4=
Received: by 10.82.98.13 with SMTP id v13mr1267597bub;
	Mon, 23 Oct 2006 04:05:39 -0700 (PDT)
Received: by 10.82.130.20 with HTTP; Mon, 23 Oct 2006 04:05:38 -0700 (PDT)
Message-ID: <5e2406980610230405r402a23cbj71937ec220de6db0@mail.gmail.com>
Date: Mon, 23 Oct 2006 13:05:39 +0200
From: "Julien Bournelle" <julien.bournelle@gmail.com>
To: "=?EUC-KR?B?wfbBpMjG?=" <jhjee@etri.re.kr>
Subject: Re: Re: [Mip6] RE: [Dime] Impact of RFC 4285 for Diameter
	MIP6Bootstrapping Work
In-Reply-To: <105201c6f51c$acadf990$8310fe81@etri.info>
MIME-Version: 1.0
References: <Acb1HKyr1NUiuWXXRKWXTWauasW09w==>
	<105201c6f51c$acadf990$8310fe81@etri.info>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: mip6@ietf.org, dime@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="===============1780442116=="
Errors-To: mip6-bounces@ietf.org

--===============1780442116==
Content-Type: text/plain; charset=EUC-KR; format=flowed
Content-Transfer-Encoding: base64
Content-Disposition: inline

SGkganVuZ2hvb24sIGFsbCwKCk9uIDEwLzIxLzA2LCDB9sGkyMYgPGpoamVlQGV0cmkucmUua3I+
IHdyb3RlOgo+Cj4KPiBIaSBKdWxpZW4sCj4gRG9lcyB5b3VyIHRob3VnaHQgaW1wbHkgdGhhdCB0
aGUgcGlnZ3liYWNraW5nIHRoZSBNSVB2NiBCVSB0byB0aGUgQUFBIG1lc3NhZ2VzPwoKIElmIHRo
ZSBNTiB1c2VzIHRoZSBNTi1BQUEgQXV0aGVudGljYXRpb24gb3B0aW9uLCBJIGd1ZXNzIHRoZSBC
VSBtYXkKYmUgcGlnZ3liYWNrZWQuCgogSnVsaWVuCgo+Cj4gLUp1bmdob29uCj4KPiAtLS0tLb/4
ursguN69w8H2LS0tLS0KPiC6uLO9ILvntvc6ICJKdWxpZW4gQm91cm5lbGxlIiA8anVsaWVuLmJv
dXJuZWxsZUBnbWFpbC5jb20+Cj4gurizvSCzr8KlOiAyMDA2LTEwLTIwIL/AyMQgNjozMDoxMgo+
ILnetMIgu+e29zogIkdlcmFyZG8gR2lhcmV0dGEiIDxnZXJhcmRvLmdpYXJldHRhQGdtYWlsLmNv
bT4KPiDC/MG2OiAibWlwNkBpZXRmLm9yZyIgPG1pcDZAaWV0Zi5vcmc+LCAiZGltZUBpZXRmLm9y
ZyIgPGRpbWVAaWV0Zi5vcmc+Cj4gwaa48TogUmU6IFtNaXA2XSBSRTogW0RpbWVdIEltcGFjdCBv
ZiBSRkMgNDI4NSBmb3IgRGlhbWV0ZXIgTUlQNkJvb3RzdHJhcHBpbmcgV29yawo+Cj4KPgo+Cj4K
Pgo+IEhpIGFsbCwKPgo+ICBjb25jZXJuaW5nIHN1cHBvcnQgZm9yIHJmYzQyODUsIEkgdGhpbmsg
d2UnbGwgbmVlZCBtZXNzYWdlcyB0byBjYXJyeSB0aGUgQlUKPiAgZnJvbSB0aGUgSEEgdG8gdGhl
IEFBQUggZm9yIHRoZSBhdXRoZW50aWZjYXRpb24uIEFzIHN1Y2gsIGEgbmV3IGFwcGxpY2F0aW9u
Cj4gIG1heSBiZSBuZWNlc3NhcnkuIEFzIGEgY29uc2VxdWVuY2UsIHRoZSBhdXRob3JpemF0aW9u
IGFuZCBhY2NvdW50aW5nIHBhcnQKPiAgbWF5IGJlIGhhbmRsZWQgYnkgdGhlIHNhbWUgYXBwbGlj
YXRpb24uCj4KPiAgVGhpcyBhcHBsaWNhdGlvbiB3b3VsZCBiZSBzaW1pbGFyIHRvIHRoZSBSRkM0
MDA0ICh3aXRob3V0IEZBLi4uKS4KPgo+ICBKdXN0IG15IDIgY2VudHMsCj4KPiAgSnVsaWVuCj4K
PiBPbiAxMC8yMC8wNiwgR2VyYXJkbyBHaWFyZXR0YSA8Z2VyYXJkby5naWFyZXR0YUBnbWFpbC5j
b20+IHdyb3RlOgo+ID4gSGkgWW9zaGkgYW5kIE1hZGppZCwKPiA+Cj4gPiB0aGUgQUFBIGdvYWxz
IGRyYWZ0IGRvZXMgbm90IGluY2x1ZGUgYW55IHNwZWNpZmljIGdvYWwgZm9yIHJmYzQyODUuCj4g
PiBUaGlzIGlzc3VlIHdhcyByYWlzZWQgaW4gTW9udHJlYWwgYW5kIGR1cmluZyBNSVA2IHJlLWNo
YXJ0ZXJpbmcKPiA+IGRpc2N1c3Npb24uIFRoZSBvdXRjb21lIG9mIHRoZSBkaXNjdXNzaW9uIHdh
cyB0aGF0IHRoZXJlIGlzIG5vIGEgY2xlYXIKPiA+IGludGVyZXN0IG5vdyBpbiB0aGUgSUVURiB0
byBzdGFuZGFyZGl6ZSBhIGJvb3RzdHJhcHBpbmcgc29sdXRpb24gZm9yCj4gPiByZmM0Mjg1IGFu
ZCBhIERpYW1ldGVyIEFwcGxpY2F0aW9uIHRoYXQgc3VwcG9ydHMgcmZjNDI4NS4gTUlQNiBjaGFp
cnMKPiA+IGFuZCBKYXJpIG1lbnRpb25lZCB0aGF0IHRoZXkgbWF5IGFzayBmb3IgcmZjNDI4NSBz
dXBwb3J0IGlmCj4gPiBzaWduaWZpY2FudCBpbnRlcmVzdCB3aWxsIGJlIHJhaXNlZC4gUmVtZW1i
ZXIgYWxzbyB0aGF0IHJmYzQyODUgaXMKPiA+IGluZm9ybWF0aW9uYWwgYW5kIHRoZSBEaWFtZXRl
ciBBcHBsaWNhdGlvbiB3aWxsIGJlIFBTOiBub3Qgc3VyZSBob3cgdG8KPiA+IHRoaXMgZGlmZmVy
ZW5jZSB3b3VsZCBiZSBoYW5kbGVkLgo+ID4KPiA+IEhhdmluZyBzYWlkIHRoYXQsIEkgdGhpbmsg
dGhhdCB0aGUgYXBwcm9hY2ggdGFrZW4gc28gZmFyIGluIHRoZSBkZXNpZ24KPiA+IG9mIHRoZSBE
aWFtZXRlciBBcHBsaWNhdGlvbiBpcyBmbGV4aWJsZSBlbm91Z2ggdG8gaW5jbHVkZSByZmM0Mjg1
Cj4gPiBsYXRlciB3aXRob3V0IGFueSBiaWcgY2hhbmdlOiB0aGUgYXV0aG9yaXphdGlvbiBhcHBs
aWNhdGlvbiBkb2VzIG5vdAo+ID4gbmVlZCB0byBiZSBjaGFuZ2VkIGZvciByZmM0Mjg1IHN1cHBv
cnQgYW5kIHdlIG1heSBkZWZpbmUgYW5vdGhlcgo+ID4gYXBwbGljYXRpb24gZm9yIGF1dGhlbnRp
Y2F0aW9uIHB1cnBvc2VzLiBUaGVyZWZvcmUgdGhlCj4gPiBhdXRoZW50aWNhdGlvbi9hdXRob3Jp
emF0aW9uIHNwbGl0IHNlZW1zIGEgY29ycmVjdCBhcHByb2FjaCBpbiBvcmRlcgo+ID4gdG8gaW50
cm9kdWNlIHJmYzQyODUgc3VwcG9ydCBsYXRlci4KPiA+Cj4gPiAtLUdlcmFyZG8KPiA+Cj4gPiBP
biAxMC8xOS8wNiwgTWFkamlkIE5ha2hqaXJpIDxtbmFraGppcmlAaHVhd2VpLmNvbT4gd3JvdGU6
Cj4gPiA+IEhpIFlvc2hpLAo+ID4gPgo+ID4gPiBJIGFncmVlLCBubyBwb2ludCBvbiBpbnNpc3Rp
bmcgdGhhdCBzb2x1dGlvbnMgd291bGQgc3VwcG9ydCA0Mjg1LCBpZiA0Mjg1Cj4gPiA+IHJlcXVp
cmVtZW50cyBhcmUgbm90IGluY2x1ZGVkLiBJIGNhbiB0aGluayBvZiBhc3BlY3RzIG9mIDQyODUg
dGhhdCBjYW4gYmUKPiA+ID4gcHJvYmxlbWF0aWMsIGJ1dCB3b24ndCBtZW50aW9uIHRoZW0gbm93
LCBzaW5jZSBJIGRvbid0IHdhbnQgdG8gYmUgYWNjdXNlZCBvZgo+ID4gPiBvcGVuaW5nIHRoZSBw
YW5kb3JhJ3MgYm94IHdoaWxlIGFhYS1oYS1nb2FscyBpcyBnb2luZyB0aHJvdWdoIGxhc3QgY2Fs
bCBvcgo+ID4gPiB0aGUgZGltZSBkb2NzIGFyZSB1bmRlcndheSA6KQo+ID4gPgo+ID4gPiBXZSBz
aG91bGQgbm90IG1ha2UgY2xhaW1zIHdlIGNhbm5vdCBiYWNrIHVwIGxhdGVyIGFzIHRoYXQgbWln
aHQgZGVyYWlsIHRoZQo+ID4gPiBzdGFuZGFyZGl6YXRpb24gcHJvY2VzcyB0d28geWVhcnMgZnJv
bSBub3cuIEFzIFBlcnNpYW5zIHNheSAoYWZ0ZXIgYSBsb3VzeQo+ID4gPiBtYXJrZXRpbmcgdHJh
bnNsYXRpb24pICJBIHNtYWxsIHF1YXJyZWwgaW4gdGhlIGJlZ2lubmluZyBiZXR0ZXIgdGhhbiBh
Cj4gPiA+IGJsb29keSBwZWFjZSBhdCB0aGUgZW5kIgo+ID4gPgo+ID4gPgo+ID4gPgo+ID4gPiBS
LAo+ID4gPgo+ID4gPiBNYWRqaWQKPiA+ID4KPiA+ID4KPiA+ID4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0KPiA+ID4gRnJvbTogWW9zaGloaXJvIE9oYmEgW21haWx0bzp5b2hiYUB0YXJpLnRv
c2hpYmEuY29tXQo+ID4gPiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxOSwgMjAwNiAxOjMzIFBN
Cj4gPiA+IFRvOiBNYWRqaWQgTmFraGppcmkKPiA+ID4gQ2M6ICdHZXJhcmRvIEdpYXJldHRhJzsg
J1ZpamF5IERldmFyYXBhbGxpJzsgbWlwNkBpZXRmLm9yZzsgZGltZUBpZXRmLm9yZwo+ID4gPiBT
dWJqZWN0OiBSZTogW01pcDZdIFJFOiBbRGltZV0gSW1wYWN0IG9mIFJGQyA0Mjg1IGZvciBEaWFt
ZXRlciBNSVA2Cj4gPiA+IEJvb3RzdHJhcHBpbmcgV29yawo+ID4gPgo+ID4gPiBNYWRqaWQsCj4g
PiA+Cj4gPiA+IE9uIFRodSwgT2N0IDE5LCAyMDA2IGF0IDAxOjA0OjA0UE0gLTA3MDAsIE1hZGpp
ZCBOYWtoamlyaSB3cm90ZToKPiA+ID4gPiBPaywgc28gSSBzZWUgSSBzcGVuZCBhIGxvbmcgZW1h
aWwgd2l0aG91dCByZWFkaW5nIHRoZSByZXN0IG9mIHRoZSB0aHJlYWQuCj4gPiA+ID4gRG8gd2Ug
ZmVlbCB0aGUgQUFBIGdvYWwgZHJhZnQgZWZmaWNpZW50bHkgY2FwdHVyZXMgdGhlIDQyODUgcmVx
dWlyZW1lbnRzPwo+ID4gPiA+IElmIHllcywgc29ycnkgZm9yIGNsb2dnaW5nIHlvdXIgbWFpbGJv
eGVzLi4KPiA+ID4KPiA+ID4gVGhhdCBpcyBteSBmZWVsaW5nIGFuZCBpcyB3aHkgSSBoYWQgdGhl
IGZvbGxvd2luZyBjb21tZW50IG9uIGFhYS1oYS1nb2Fscwo+ID4gPiBkcmFmdDoKPiA+ID4KPiA+
ID4gIgo+ID4gPiAgIFlPOiBUaGlzIGRvY3VtZW50IHNlZW1zIHRvIGFzc3VtZSB0aGUgdXNlIG9m
IElQc2VjIGJldHdlZW4gTU4gYW5kIEhBCj4gPiA+ICAgZm9yIHNlY3VyaW5nIE1vYmlsZSBJUHY2
IHNpZ25hbGluZy4gIEJ1dCB0aGUgQUFBIGludGVyZmFjZSBjb3VsZAo+ID4gPiAgIGFsc28gYmUg
dXNlZCBmb3IgUkZDIDQyODUuICBTbyBJIHRoaW5rIGl0IG1pZ2h0IGJlIGdvb2QgdG8gbWVudGlv
bgo+ID4gPiAgIGluIHRoaXMgc2VjdGlvbiB0aGF0IHRoZSBkb2N1bWVudCBtYXkgbm90IHByZWNs
dWRlIHRoZSB1c2Ugb2YKPiA+ID4gICBhbHRlcm5hdGl2ZSBtZXRob2RzIGZvciBzZWN1cmluZyBN
b2JpbGUgSVB2NiBzaWduYWxpbmcgYmV0d2VlbiBNTgo+ID4gPiAgIGFuZCBIQSB3aGlsZSB0aGlz
IGRvY3VtZW50IGZvY3VzZXMgb24gdGhlIHVzZSBvZiBJUHNlYyBiZXR3ZWVuIE1OCj4gPiA+ICAg
YW5kIEhBLgo+ID4gPiAiCj4gPiA+Cj4gPiA+IFlvc2hpaGlybyBPaGJhCj4gPiA+Cj4gPiA+Cj4g
PiA+ID4KPiA+ID4gPiBSLAo+ID4gPiA+Cj4gPiA+ID4gTWFkamlkCj4gPiA+ID4KPiA+ID4gPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+ID4gPiA+IEZyb206IEdlcmFyZG8gR2lhcmV0dGEg
W21haWx0bzpnZXJhcmRvLmdpYXJldHRhQGdtYWlsLmNvbV0KPiA+ID4gPiBTZW50OiBGcmlkYXks
IE9jdG9iZXIgMTMsIDIwMDYgMTI6MzcgQU0KPiA+ID4gPiBUbzogVmlqYXkgRGV2YXJhcGFsbGkK
PiA+ID4gPiBDYzogbWlwNkBpZXRmLm9yZzsgZGltZUBpZXRmLm9yZwo+ID4gPiA+IFN1YmplY3Q6
IFJlOiBbRGltZV0gSW1wYWN0IG9mIFJGQyA0Mjg1IGZvciBEaWFtZXRlciBNSVA2IEJvb3RzdHJh
cHBpbmcKPiA+ID4gV29yawo+ID4gPiA+Cj4gPiA+ID4gPiA+IGluIHRoZSBESU1FIHdvcmtpbmcg
Z3JvdXaWFtZXRl
ciBBcHBsaWNhdGlvbiB3aWxsIGJlIFBTOiBub3Qgc3VyZSBob3cgdG8KPiA+IHRoaXMgZGlmZmVy
ZW5jZSB3b3VsZCBiZSBoYW5kbGVkLgo+ID4KPiA+IEhhdmluZyBzYWlkIHRoYXQsIEkgdGhpbmsg
dGhhdCB0aGUgYXBwcm9hY2ggdGFrZW4gc28gZmFyIGluIHRoZSBkZXNpZ24KPiA+IG9mIHRoZSBE
aWFtZXRlciBBcHBsaWNhdGlvbiBpcyBmbGV4aWJsZSBlbm91Z2ggdG8gaW5jbHVkZSByZmM0Mjg1
Cj4gPiBsYXRlciB3aXRob3V0IGFueSBiaWcgY2hhbmdlOiB0aGUgYXV0aG9yaXphdGlvbiBhcHBs
aWNhdGlvbiBkb2VzIG5vdAo+ID4gbmVlZCB0byBiZSBjaGFuZ2VkIGZvciByZmM0Mjg1IHN1cHBv
cnQgYW5kIHdlIG1heSBkZWZpbmUgYW5vdGhlcgo+ID4gYXBwbGljYXRpb24gZm9yIGF1dGhlbnRp
Y2F0aW9uIHB1cnBvc2VzLiBUaGVyZWZvcmUgdGhlCj4gPiBhdXRoZW50aWNhdGlvbi9hdXRob3Jp
emF0aW9uIHNwbGl0IHNlZW1zIGEgY29ycmVjdCBhcHByb2FjaCBpbiBvcmRlcgo+ID4gdG8gaW50
cm9kdWNlIHJmYzQyODUgc3VwcG9ydCBsYXRlci4KPiA+Cj4gPiAtLUdlcmFyZG8KPiA+Cj4gPiBP
biAxMC8xOS8wNiwgTWFkamlkIE5ha2hqaXJpIDxtbmFraGppcmlAaHVhd2VpLmNvbT4gd3JvdGU6
Cj4gPiA+IEhpIFlvc2hpLAo+ID4gPgo+ID4gPiBJIGFncmVlLCBubyBwb2ludCBvbiBpbnNpc3Rp
bmcgdGhhdCBzb2x1dGlvbnMgd291bGQgc3VwcG9ydCA0Mjg1LCBpZiA0Mjg1Cj4gPiA+IHJlcXVp
cmVtZW50cyBhcmUgbm90IGluY2x1ZGVkLiBJIGNhbiB0aGluayBvZiBhc3BlY3RzIG9mIDQyODUg
dGhhdCBjYW4gYmUKPiA+ID4gcHJvYmxlbWF0aWMsIGJ1dCB3b24ndCBtZW50aW9uIHRoZW0gbm93
LCBzaW5jZSBJIGRvbid0IHdhbnQgdG8gYmUgYWNjdXNlZCBvZgo+ID4gPiBvcGVuaW5nIHRoZSBw
YW5kb3JhJ3MgYm94IHdoaWxlIGFhYS1oYS1nb2FscyBpcyBnb2luZyB0aHJvdWdoIGxhc3QgY2Fs
bCBvcgo+ID4gPiB0aGUgZGltZSBkb2NzIGFyZSB1bmRlcndheSA6KQo+ID4gPgo+ID4gPiBXZSBz
aG91bGQgbm90IG1ha2UgY2xhaW1zIHdlIGNhbm5vdCBiYWNrIHVwIGxhdGVyIGFzIHRoYXQgbWln
aHQgZGVyYWlsIHRoZQo+ID4gPiBzdGFuZGFyZGl6YXRpb24gcHJvY2VzcyB0d28geWVhcnMgZnJv
bSBub3cuIEFzIFBlcnNpYW5zIHNheSAoYWZ0ZXIgYSBsb3VzeQo+ID4gPiBtYXJrZXRpbmcgdHJh
bnNsYXRpb24pICJBIHNtYWxsIHF1YXJyZWwgaW4gdGhlIGJlZ2lubmluZyBiZXR0ZXIgdGhhbiBh
Cj4gPiA+IGJsb29keSBwZWFjZSBhdCB0aGUgZW5kIgo+ID4gPgo+ID4gPgo+ID4gPgo+ID4gPiBS
LAo+ID4gPgo+ID4gPiBNYWRqaWQKPiA+ID4KPiA+ID4KPiA+ID4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0KPiA+ID4gRnJvbTogWW9zaGloaXJvIE9oYmEgW21haWx0bzp5b2hiYUB0YXJpLnRv
c2hpYmEuY29tXQo+ID4gPiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxOSwgMjAwNiAxOjMzIFBN
Cj4gPiA+IFRvOiBNYWRqaWQgTmFraGppcmkKPiA+ID4gQ2M6ICdHZXJhcmRvIEdpYXJldHRhJzsg
J1ZpamF5IERldmFyYXBhbGxpJzsgbWlwNkBpZXRmLm9yZzsgZGltZUBpZXRmLm9yZwo+ID4gPiBT
dWJqZWN0OiBSZTogW01pcDZdIFJFOiBbRGltZV0gSW1wYWN0IG9mIFJGQyA0Mjg1IGZvciBEaWFt
ZXRlciBNSVA2Cj4gPiA+IEJvb3RzdHJhcHBpbmcgV29yawo+ID4gPgo+ID4gPiBNYWRqaWQsCj4g
PiA+Cj4gPiA+IE9uIFRodSwgT2N0IDE5LCAyMDA2IGF0IDAxOjA0OjA0UE0gLTA3MDAsIE1hZGpp
ZCBOYWtoamlyaSB3cm90ZToKPiA+ID4gPiBPaywgc28gSSBzZWUgSSBzcGVuZCBhIGxvbmcgZW1h
aWwgd2l0aG91dCByZWFkaW5nIHRoZSByZXN0IG9mIHRoZSB0aHJlYWQuCj4gPiA+ID4gRG8gd2Ug
ZmVlbCB0aGUgQUFBIGdvYWwgZHJhZnQgZWZmaWNpZW50bHkgY2FwdHVyZXMgdGhlIDQyODUgcmVx
dWlyZW1lbnRzPwo+ID4gPiA+IElmIHllcywgc29ycnkgZm9yIGNsb2dnaW5nIHlvdXIgbWFpbGJv
eGVzLi4KPiA+ID4KPiA+ID4gVGhhdCBpcyBteSBmZWVsaW5nIGFuZCBpcyB3aHkgSSBoYWQgdGhl
IGZvbGxvd2luZyBjb21tZW50IG9uIGFhYS1oYS1nb2Fscwo+ID4gPiBkcmFmdDoKPiA+ID4KPiA+
ID4gIgo+ID4gPiAgIFlPOiBUaGlzIGRvY3VtZW50IHNlZW1zIHRvIGFzc3VtZSB0aGUgdXNlIG9m
IElQc2VjIGJldHdlZW4gTU4gYW5kIEhBCj4gPiA+ICAgZm9yIHNlY3VyaW5nIE1vYmlsZSBJUHY2
IHNpZ25hbGluZy4gIEJ1dCB0aGUgQUFBIGludGVyZmFjZSBjb3VsZAo+ID4gPiAgIGFsc28gYmUg
dXNlZCBmb3IgUkZDIDQyODUuICBTbyBJIHRoaW5rIGl0IG1pZ2h0IGJlIGdvb2QgdG8gbWVudGlv
bgo+ID4gPiAgIGluIHRoaXMgc2VjdGlvbiB0aGF0IHRoZSBkb2N1bWVudCBtYXkgbm90IHByZWNs
dWRlIHRoZSB1c2Ugb2YKPiA+ID4gICBhbHRlcm5hdGl2ZSBtZXRob2RzIGZvciBzZWN1cmluZyBN
b2JpbGUgSVB2NiBzaWduYWxpbmcgYmV0d2VlbiBNTgo+ID4gPiAgIGFuZCBIQSB3aGlsZSB0aGlz
IGRvY3VtZW50IGZvY3VzZXMgb24gdGhlIHVzZSBvZiBJUHNlYyBiZXR3ZWVuIE1OCj4gPiA+ICAg
YW5kIEhBLgo+ID4gPiAiCj4gPiA+Cj4gPiA+IFlvc2hpaGlybyBPaGJhCj4gPiA+Cj4gPiA+Cj4g
PiA+ID4KPiA+ID4gPiBSLAo+ID4gPiA+Cj4gPiA+ID4gTWFkamlkCj4gPiA+ID4KPiA+ID4gPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+ID4gPiA+IEZyb206IEdlcmFyZG8gR2lhcmV0dGEg
W21haWx0bzpnZXJhcmRvLmdpYXJldHRhQGdtYWlsLmNvbV0KPiA+ID4gPiBTZW50OiBGcmlkYXks
IE9jdG9iZXIgMTMsIDIwMDYgMTI6MzcgQU0KPiA+ID4gPiBUbzogVmlqYXkgRGV2YXJhcGFsbGkK
PiA+ID4gPiBDYzogbWlwNkBpZXRmLm9yZzsgZGltZUBpZXRmLm9yZwo+ID4gPiA+IFN1YmplY3Q6
IFJlOiBbRGltZV0gSW1wYWN0IG9mIFJGQyA0Mjg1IGZvciBEaWFtZXRlciBNSVA2IEJvb3RzdHJh
cHBpbmcKPiA+ID4gV29yawo+ID4gPiA+Cj4gPiA+ID4gPiA+IGluIHRoZSBESU1FIHdvcmtpbmcg
Z3JvdXAgd2UgYXJlIGN1cnJlbnRseSBwcm9kdWNpbmcgZG9jdW1lbnRzIHRoYXQKPiA+ID4gPiA+
ID4gcmVsYXRlIHRvIHRoZSBiYWNrZW5kIHNvbHV0aW9uIG9mIHRoZQo+ID4gPiA+ID4gPgo+ID4g
PiA+ID4gPiAqIEludGVncmF0ZWQgU2NlbmFyaW8KPiA+ID4gPiA+ID4gICBkcmFmdC1pZXRmLW1p
cDYtYm9vdHN0cmFwcGluZy1pbnRlZ3JhdGVkLWRoYy0wMQo+ID4gPiA+ID4gPgo+ID4gPiA+ID4g
PiAqIFNwbGl0IFNjZW5hcmlvCj4gPiA+ID4gPiA+ICAgZHJhZnQtaWV0Zi1taXA2LWJvb3RzdHJh
cHBpbmctc3BsaXQtMDIKPiA+ID4gPiA+ID4KPiA+ID4gPiA+ID4gTm93LCB0aGUgcXVlc3Rpb24g
Y2FtZSB1cCB3aGV0aGVyIHdlIGhhdmUgdG8gY29uc2lkZXIgUkZDIDQyODUKPiA+ID4gPiA+ID4g
KCdBdXRoZW50aWNhdGlvbiBQcm90b2NvbCBmb3IgTW9iaWxlIElQdjYnKSBmb3Igb3VyIHdvcmsg
YXMgd2VsbC4KPiA+ID4gPiA+Cj4gPiA+ID4gPiBjdXJyZW50bHkgaXQgaXMgbm90IGNsZWFyIGlm
IHdlIGFyZSBnb2luZyB0byBkbyBhbnkKPiA+ID4gPiA+IGZ1cnRoZXIgd29yayBvbiBSRkMgNDI4
NSBpbiB0aGUgTUlQNiBXRy4gc28gbXkKPiA+ID4gPiA+IHN1Z2dlc3Rpb24gaXMgdG8gYXNzdW1l
IG9ubHkgdGhlIHVzZSBvZiBJS0V2MiAod2l0aAo+ID4gPiA+ID4gYW5kIHdpdGhvdXQgRUFQKS4K
PiA+ID4gPiA+Cj4gPiA+ID4KPiA+ID4gPiBBZ3JlZSB3aXRoIFZpamF5LCB0aGlzIGlzIGFsc28g
dGhlIGFzc3VtcHRpb24gZm9yIHRoZSBBQUEgZ29hbHMgZHJhZnQuCj4gPiA+ID4KPiA+ID4gPiAt
LUdlcmFyZG8KPiA+ID4gPgo+ID4gPiA+ID4gYnV0IGl0IHdvdWxkIGJlIGdvb2QgdG8ga2VlcCB0
aGUgc29sdXRpb24gZmxleGlibGUKPiA+ID4gPiA+IHNvIHRoYXQgaXQgY2FuIGJlIGV4dGVuZGVk
IGxhdGVyIGZvciA0Mjg1IGlmIHJlcXVpcmVkLgo+ID4gPiA+ID4KPiA+ID4gPiA+IFZpamF5Cj4g
PiA+ID4gPgo+ID4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KPiA+ID4gPiA+IERpTUUgbWFpbGluZyBsaXN0Cj4gPiA+ID4gPiBEaU1FQGlldGYu
b3JnCj4gPiA+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaW1l
Cj4gPiA+ID4gPgo+ID4gPiA+Cj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KPiA+ID4gPiBEaU1FIG1haWxpbmcgbGlzdAo+ID4gPiA+IERpTUVA
aWV0Zi5vcmcKPiA+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9k
aW1lCj4gPiA+ID4KPiA+ID4gPgo+ID4gPiA+Cj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KPiA+ID4gPiBNaXA2IG1haWxpbmcgbGlzdAo+ID4g
PiA+IE1pcDZAaWV0Zi5vcmcKPiA+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9taXA2Cj4gPiA+ID4KPiA+ID4KPiA+ID4KPiA+ID4KPiA+Cj4gPiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+ID4gRGlNRSBtYWlsaW5nIGxp
c3QKPiA+IERpTUVAaWV0Zi5vcmcKPiA+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2RpbWUKPiA+Cj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXwo+IERpTUUgbWFpbGluZyBsaXN0Cj4gRGlNRUBpZXRmLm9yZwo+IGh0dHBzOi8v
d3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RpbWUKPgo=


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

--===============1780442116==--





Agd2UgYXJlIGN1cnJlbnRseSBwcm9kdWNpbmcgZG9jdW1lbnRzIHRoYXQKPiA+ID4gPiA+
ID4gcmVsYXRlIHRvIHRoZSBiYWNrZW5kIHNvbHV0aW9uIG9mIHRoZQo+ID4gPiA+ID4gPgo+ID4g
PiA+ID4gPiAqIEludGVncmF0ZWQgU2NlbmFyaW8KPiA+ID4gPiA+ID4gICBkcmFmdC1pZXRmLW1p
cDYtYm9vdHN0cmFwcGluZy1pbnRlZ3JhdGVkLWRoYy0wMQo+ID4gPiA+ID4gPgo+ID4gPiA+ID4g
PiAqIFNwbGl0IFNjZW5hcmlvCj4gPiA+ID4gPiA+ICAgZHJhZnQtaWV0Zi1taXA2LWJvb3RzdHJh
cHBpbmctc3BsaXQtMDIKPiA+ID4gPiA+ID4KPiA+ID4gPiA+ID4gTm93LCB0aGUgcXVlc3Rpb24g
Y2FtZSB1cCB3aGV0aGVyIHdlIGhhdmUgdG8gY29uc2lkZXIgUkZDIDQyODUKPiA+ID4gPiA+ID4g
KCdBdXRoZW50aWNhdGlvbiBQcm90b2NvbCBmb3IgTW9iaWxlIElQdjYnKSBmb3Igb3VyIHdvcmsg
YXMgd2VsbC4KPiA+ID4gPiA+Cj4gPiA+ID4gPiBjdXJyZW50bHkgaXQgaXMgbm90IGNsZWFyIGlm
IHdlIGFyZSBnb2luZyB0byBkbyBhbnkKPiA+ID4gPiA+IGZ1cnRoZXIgd29yayBvbiBSRkMgNDI4
NSBpbiB0aGUgTUlQNiBXRy4gc28gbXkKPiA+ID4gPiA+IHN1Z2dlc3Rpb24gaXMgdG8gYXNzdW1l
IG9ubHkgdGhlIHVzZSBvZiBJS0V2MiAod2l0aAo+ID4gPiA+ID4gYW5kIHdpdGhvdXQgRUFQKS4K
PiA+ID4gPiA+Cj4gPiA+ID4KPiA+ID4gPiBBZ3JlZSB3aXRoIFZpamF5LCB0aGlzIGlzIGFsc28g
dGhlIGFzc3VtcHRpb24gZm9yIHRoZSBBQUEgZ29hbHMgZHJhZnQuCj4gPiA+ID4KPiA+ID4gPiAt
LUdlcmFyZG8KPiA+ID4gPgo+ID4gPiA+ID4gYnV0IGl0IHdvdWxkIGJlIGdvb2QgdG8ga2VlcCB0
aGUgc29sdXRpb24gZmxleGlibGUKPiA+ID4gPiA+IHNvIHRoYXQgaXQgY2FuIGJlIGV4dGVuZGVk
IGxhdGVyIGZvciA0Mjg1IGlmIHJlcXVpcmVkLgo+ID4gPiA+ID4KPiA+ID4gPiA+IFZpamF5Cj4g
PiA+ID4gPgo+ID4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KPiA+ID4gPiA+IERpTUUgbWFpbGluZyBsaXN0Cj4gPiA+ID4gPiBEaU1FQGlldGYu
b3JnCj4gPiA+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaW1l
Cj4gPiA+ID4gPgo+ID4gPiA+Cj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KPiA+ID4gPiBEaU1FIG1haWxpbmcgbGlzdAo+ID4gPiA+IERpTUVA
aWV0Zi5vcmcKPiA+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9k
aW1lCj4gPiA+ID4KPiA+ID4gPgo+ID4gPiA+Cj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KPiA+ID4gPiBNaXA2IG1haWxpbmcgbGlzdAo+ID4g
PiA+IE1pcDZAaWV0Zi5vcmcKPiA+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9taXA2Cj4gPiA+ID4KPiA+ID4KPiA+ID4KPiA+ID4KPiA+Cj4gPiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+ID4gRGlNRSBtYWlsaW5nIGxp
c3QKPiA+IERpTUVAaWV0Zi5vcmcKPiA+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2RpbWUKPiA+Cj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXwo+IERpTUUgbWFpbGluZyBsaXN0Cj4gRGlNRUBpZXRmLm9yZwo+IGh0dHBzOi8v
d3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RpbWUKPgo=


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

--===============1780442116==--





From mip6-bounces@ietf.org Mon Oct 23 13:10:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gc3J2-0005xL-Uk; Mon, 23 Oct 2006 13:09:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc3J1-0005xA-1J
	for mip6@ietf.org; Mon, 23 Oct 2006 13:09:43 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gc3Iw-0007Td-Ld
	for mip6@ietf.org; Mon, 23 Oct 2006 13:09:43 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 10:09:37 -0700
Message-ID: <453CF690.2050909@azairenet.com>
Date: Mon, 23 Oct 2006 10:06:24 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Mip6 issue tracker <tracker-mip6@mip4.org>,  mip6@ietf.org
References: <1161600299.67.0.542962233908.issue66@mip4.org>
In-Reply-To: <1161600299.67.0.542962233908.issue66@mip4.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Oct 2006 17:09:37.0906 (UTC)
	FILETIME=[0545DD20:01C6F6C6]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
Subject: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 object.

I still think we shouldn't talk about a binding
cache entry for the IPv4 home address. how its
implemented is not the issue here. the issue is
about what we are calling it in the DS-MIPv6
specification.

I don't think we had consensus on the mailing
list to reject the issue. did we?

Vijay

Hesham Soliman wrote:
> Hesham Soliman <solimanhs@gmail.com> added the comment:
> 
> Several IETF specifications describe conceptual data as part of
> documenting a protocol. This is typically done for additional
> clarification. Examples of such specifications include IPsec, ND, and
> MIP (v4 and v6). MIPv6 described the binding cache as a mechanism for
> storing bindings. However, this does not in anyway force implementers to
> implement MIPv6 exactly as described in the document, as long as the
> external behaviour is consistent with the specification. Since this
> specification is an extension to MIPv6, it is appropriate to describe
> the conceptual data structure in a manner consistent with RFC 3775. 
> 
> RFC 3775 maintains that there is a separate Binding Cache entry for each
> home address. As we are extending MIPv6 to support another address
> family (IPv4), we still maintain the same philosophy of one binding
> cache entry per home address, regardless of the type of HoA. 
> Similar to MIPv6, this does not require implementers to do it exactly in
> this manner, hence the term "conceptual data structure". One may choose
> to implement the v4 entry in the routing table for instance (the same
> can be said for the v6 entry). But in all cases, the entries will need
> to be maintained (refreshed/deleted ...etc) as per the BU. 
> 
> Conclusion:
> -----------
> 
> Keeping with the conceptual data structures in MIPv6 makes the spec
> clear and does not limit implementers. There is no harm or bugs
> introduced by the current text. Therefore the issue should be rejected.
> 
> ----------
> status: Pending -> Rejected
> 
> _________________________________________________
> Mip6 issue tracker <tracker-mip6@mip4.org>
> <http://www.mip4.org/issues/tracker/mip6/issue66>
> _________________________________________________


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



From mip6-bounces@ietf.org Mon Oct 23 13:21:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gc3Tn-00038b-Lc; Mon, 23 Oct 2006 13:20:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc3Tm-00036T-1r
	for mip6@ietf.org; Mon, 23 Oct 2006 13:20:50 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gc3Tk-0000Gp-MA
	for mip6@ietf.org; Mon, 23 Oct 2006 13:20:50 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 10:20:48 -0700
Message-ID: <453CF92F.5050809@azairenet.com>
Date: Mon, 23 Oct 2006 10:17:35 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
References: <7EB20EA0938B4D42A2D82689365C9B7A24AAD3@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24AAD3@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Oct 2006 17:20:48.0187 (UTC)
	FILETIME=[94CAA0B0:01C6F6C7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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

Soliman, Hesham wrote:
>  For the benefit of the list I'm repeating what I already told Vijay in
> a private mail.
> 
> 
>  > >  > from what I remember we wanted to relax the MUST
>  > >  > requirement at the HA to always the CoA in the
>  > >  > alt-CoA option when there is a NAT present.
>  > > 
>  > > => Right, but please s/when a NAT is present/when in an 
>  > IPv4 network.
>  > 
>  > nope. the HA needs to relax the requirement only
>  > when it detects a NAT, not because the MN is on
>  > an IPv4 access network.
>  > 
> 
> => This can't work because the HA has no way of knowing whether the src
> address in the v6 header is different because of NAT or due to a
> legitimate use of the alt-coa option. 

thats an inherent problem with NAT traversal.
any recipient of a packet that goes through
a NAT does not know if the source address on
the packet was modified by a NAT or by some
attacker on the path.

> So the HA can't decide whether a
> NAT is detected or not by comparing the v4 and v6 headers if the alt-coa
> may be found later. The only way to detect a NAT beased on the v4/v6
> headers comparison is to remove the alt-coa option.

does not follow.

>  > > => That's fine, so you just express that opinion for this 
>  > new issue. All
>  > > I said was that the checksum (the need for it) will be a 
>  > separate issue
>  > > since we agreed on the other part (relaxing of 3775). 
>  > 
>  > lets be clear on what we agreed to relax. only the
>  > MUST requirement on the HA to use the CoA in the
>  > alt-CoA option all the time.
> 
> => I don't think you could have agreed with that because it was never
> suggested. Neither the issue text nor my analysis/recommendation ever
> suggested this approach. Both clearly suggested ommitting the alt-coa
> option. 

my bad. I was under the impression that we are
relaxing the MUST requirement in RFC 3775. not
the altCoA option. anyway, I don't believe we
have consensus on removing the alt-CoA option.
did we have consensus on the mailing list?

Vijay

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



From mip6-bounces@ietf.org Tue Oct 24 00:20:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcDkN-0005Xh-Rb; Tue, 24 Oct 2006 00:18:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcDkN-0005XX-1z
	for mip6@ietf.org; Tue, 24 Oct 2006 00:18:39 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcDkL-000617-Jc
	for mip6@ietf.org; Tue, 24 Oct 2006 00:18: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
	k9O4IZWB027229
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 23 Oct 2006 21:18:36 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9O4IUUU023626; Mon, 23 Oct 2006 21:18:33 -0700 (PDT)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Oct 2006 21:18:31 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Oct 2006 21:18:31 -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] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Date: Mon, 23 Oct 2006 21:18:29 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24AB97@NAEX14.na.qualcomm.com>
In-Reply-To: <453CF92F.5050809@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when traversing
	IPv4 NAT
Thread-Index: Acb2x6KFHArwrL+vS8ODAYZRk0RhqQAW3VXw
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 24 Oct 2006 04:18:31.0627 (UTC)
	FILETIME=[76D5B1B0:01C6F723]
X-Spam-Score: 0.0 (/)
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


 > > =3D> This can't work because the HA has no way of knowing=20
 > whether the src
 > > address in the v6 header is different because of NAT or due to a
 > > legitimate use of the alt-coa option.=20
 >=20
 > thats an inherent problem with NAT traversal.
 > any recipient of a packet that goes through
 > a NAT does not know if the source address on
 > the packet was modified by a NAT or by some
 > attacker on the path.

=3D> No I'm not talking about that. If the alt-coa is present, the HA
can't tell that a NAT was in the path just by comparing the v4 and v6
headers. This has nothing to do with NAT and everything to do with the
alt-coa option. That is the issue.

 >=20
 > > So the HA can't decide whether a
 > > NAT is detected or not by comparing the v4 and v6 headers=20
 > if the alt-coa
 > > may be found later. The only way to detect a NAT beased on=20
 > the v4/v6
 > > headers comparison is to remove the alt-coa option.
 >=20
 > does not follow.

=3D> What doesn't follow??

Hesham

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



From mip6-bounces@ietf.org Tue Oct 24 00:22:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcDnA-0000gc-Cg; Tue, 24 Oct 2006 00:21:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcDn8-0000gQ-Ut
	for mip6@ietf.org; Tue, 24 Oct 2006 00:21:30 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcDn7-0006co-Gp
	for mip6@ietf.org; Tue, 24 Oct 2006 00:21:30 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9O4LSbJ027364
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Mon, 23 Oct 2006 21:21:29 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9O4LRvm014542
	for <mip6@ietf.org>; Mon, 23 Oct 2006 21:21:27 -0700 (PDT)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Oct 2006 21:21:27 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Oct 2006 21:21:26 -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] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Mon, 23 Oct 2006 21:21:24 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24AB98@NAEX14.na.qualcomm.com>
In-Reply-To: <453CF690.2050909@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb2x+0I51Jwk6/RQbe68U0LpMizKgAW5gRg
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 24 Oct 2006 04:21:26.0908 (UTC)
	FILETIME=[DF4F73C0:01C6F723]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 still think we shouldn't talk about a binding
 > cache entry for the IPv4 home address. how its
 > implemented is not the issue here. the issue is
 > about what we are calling it in the DS-MIPv6
 > specification.

=3D> DSMIP does what RFC 3775 and many other specs do in IETF. If you =
have
an issue with that please explain it.=20

 >=20
 > I don't think we had consensus on the mailing
 > list to reject the issue. did we?

=3D> When an issue is raised, and no one supports it then we don't have
concensus to do anything. I suggested a rejection, there were no
comments, so I went along with that.=20

Hesham

 >=20
 > Vijay
 >=20
 > Hesham Soliman wrote:
 > > Hesham Soliman <solimanhs@gmail.com> added the comment:
 > >=20
 > > Several IETF specifications describe conceptual data as part of
 > > documenting a protocol. This is typically done for additional
 > > clarification. Examples of such specifications include=20
 > IPsec, ND, and
 > > MIP (v4 and v6). MIPv6 described the binding cache as a=20
 > mechanism for
 > > storing bindings. However, this does not in anyway force=20
 > implementers to
 > > implement MIPv6 exactly as described in the document, as=20
 > long as the
 > > external behaviour is consistent with the specification. Since this
 > > specification is an extension to MIPv6, it is appropriate=20
 > to describe
 > > the conceptual data structure in a manner consistent with=20
 > RFC 3775.=20
 > >=20
 > > RFC 3775 maintains that there is a separate Binding Cache=20
 > entry for each
 > > home address. As we are extending MIPv6 to support another address
 > > family (IPv4), we still maintain the same philosophy of one binding
 > > cache entry per home address, regardless of the type of HoA.=20
 > > Similar to MIPv6, this does not require implementers to do=20
 > it exactly in
 > > this manner, hence the term "conceptual data structure".=20
 > One may choose
 > > to implement the v4 entry in the routing table for=20
 > instance (the same
 > > can be said for the v6 entry). But in all cases, the=20
 > entries will need
 > > to be maintained (refreshed/deleted ...etc) as per the BU.=20
 > >=20
 > > Conclusion:
 > > -----------
 > >=20
 > > Keeping with the conceptual data structures in MIPv6 makes the spec
 > > clear and does not limit implementers. There is no harm or bugs
 > > introduced by the current text. Therefore the issue should=20
 > be rejected.
 > >=20
 > > ----------
 > > status: Pending -> Rejected
 > >=20
 > > _________________________________________________
 > > Mip6 issue tracker <tracker-mip6@mip4.org>
 > > <http://www.mip4.org/issues/tracker/mip6/issue66>
 > > _________________________________________________
 >=20
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

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



From mip6-bounces@ietf.org Tue Oct 24 13:17:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcPsn-0000PZ-Q4; Tue, 24 Oct 2006 13:16:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcPpj-0007Zt-GQ
	for mip6@ietf.org; Tue, 24 Oct 2006 13:12:59 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcPmx-0006Ga-3s
	for mip6@ietf.org; Tue, 24 Oct 2006 13:10:15 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 10:10:06 -0700
Message-ID: <453E482D.5090302@azairenet.com>
Date: Tue, 24 Oct 2006 10:06:53 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7EB20EA0938B4D42A2D82689365C9B7A24AB98@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24AB98@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 17:10:06.0000 (UTC)
	FILETIME=[406E6B00:01C6F78F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> 
>  > I still think we shouldn't talk about a binding
>  > cache entry for the IPv4 home address. how its
>  > implemented is not the issue here. the issue is
>  > about what we are calling it in the DS-MIPv6
>  > specification.
> 
> => DSMIP does what RFC 3775 and many other specs do in IETF. If you have
> an issue with that please explain it. 

please lookup the earlier mails on why there is an
issue in the first place. you should still have
the mip6trans emails.

for your benefit I am repeating them here.

- in the DS-MIPv6 case, there is only BCE that is
based on the MN's IPv6 home address. all other
information is tied to this BCE. this may include
tunnel state for the MN, forwarding state for an
IPv6 NEMO prefix, forwarding state for the MN's
IPv4 home address, forwarding state for the MN's
IPv4 NEMO prefix.

- we setup binding cache entries for the IPv4 home
address only in MIPv4.

- we shouldn't mix up things by saying we create
binding cache entries for both the IPv4 and IPv6
HoAs.

also see the comments at
http://www.mip4.org/issues/tracker/mip6/issue66

>  > I don't think we had consensus on the mailing
>  > list to reject the issue. did we?
> 
> => When an issue is raised, and no one supports it then we don't have
> concensus to do anything. I suggested a rejection, there were no
> comments, so I went along with that. 

:) you want people to repeat things all the time.
I count at least two now, Pascal (see the URL above)

for one there was never a consensus to call it a
binding cache entry for the IPv4 HoA. the issue
was open from the beginning. when we picked a draft
to be the base document, it does not mean everything
that is in there in the draft is already agreed to.

Vijay

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

From mip6-bounces@ietf.org Tue Oct 24 13:17:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcPsc-0000Ga-FY; Tue, 24 Oct 2006 13:15:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esFrom mip6-bounces@ietf.org Tue Oct 24 13:17:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcPsn-0000PZ-Q4; Tue, 24 Oct 2006 13:16:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcPpj-0007Zt-GQ
	for mip6@ietf.org; Tue, 24 Oct 2006 13:12:59 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcPmx-0006Ga-3s
	for mip6@ietf.org; Tue, 24 Oct 2006 13:10:15 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 10:10:06 -0700
Message-ID: <453E482D.5090302@azairenet.com>
Date: Tue, 24 Oct 2006 10:06:53 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7EB20EA0938B4D42A2D82689365C9B7A24AB98@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A24AB98@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 17:10:06.0000 (UTC)
	FILETIME=[406E6B00:01C6F78F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> 
>  > I still think we shouldn't talk about a binding
>  > cache entry for the IPv4 home address. how its
>  > implemented is not the issue here. the issue is
>  > about what we are calling it in the DS-MIPv6
>  > specification.
> 
> => DSMIP does what RFC 3775 and many other specs do in IETF. If you have
> an issue with that please explain it. 

please lookup the earlier mails on why there is an
issue in the first place. you should still have
the mip6trans emails.

for your benefit I am repeating them here.

- in the DS-MIPv6 case, there is only BCE that is
based on the MN's IPv6 home address. all other
information is tied to this BCE. this may include
tunnel state for the MN, forwarding state for an
IPv6 NEMO prefix, forwarding state for the MN's
IPv4 home address, forwarding state for the MN's
IPv4 NEMO prefix.

- we setup binding cache entries for the IPv4 home
address only in MIPv4.

- we shouldn't mix up things by saying we create
binding cache entries for both the IPv4 and IPv6
HoAs.

also see the comments at
http://www.mip4.org/issues/tracker/mip6/issue66

>  > I don't think we had consensus on the mailing
>  > list to reject the issue. did we?
> 
> => When an issue is raised, and no one supports it then we don't have
> concensus to do anything. I suggested a rejection, there were no
> comments, so I went along with that. 

:) you want people to repeat things all the time.
I count at least two now, Pascal (see the URL above)

for one there was never a consensus to call it a
binding cache entry for the IPv4 HoA. the issue
was open from the beginning. when we picked a draft
to be the base document, it does not mean everything
that is in there in the draft is already agreed to.

Vijay

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

From mip6-bounces@ietf.org Tue Oct 24 13:17:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcPsc-0000Ga-FY; Tue, 24 Oct 2006 13:15:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcPqC-0007vW-BM
	for mip6@ietf.org; Tue, 24 Oct 2006 13:13:28 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcPex-0004yV-Pc
	for mip6@ietf.org; Tue, 24 Oct 2006 13:01:56 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9OH1k3p019602 for <mip6@ietf.org>; Tue, 24 Oct 2006 20:01:50 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 20:01:47 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 12:01:42 -0500
Received: from 172.19.244.193 ([172.19.244.193]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 24 Oct 2006 17:01:42 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 24 Oct 2006 12:03:47 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C163B1A3.27154%basavaraj.patil@nokia.com>
Thread-Topic: Note the change in meeting date for MIP6 at IETF67
Thread-Index: Acb3jl6HnOaLDmOBEduV2AARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 17:01:42.0202 (UTC)
	FILETIME=[1424F1A0:01C6F78E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [Mip6] Note the change in meeting date for MIP6 at IETF67
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Please note that the MIP6 WG meeting has now been scheduled for Tuesday, Nov
7th. The meeting is in the afternoon from 1740-1950.

The latest agenda is at:
http://www3.ietf.org/proceedings/06nov/agenda/mip6.txt

And as of Oct 24th:


TUESDAY, November 7, 2006
1740-1950 Afternoon Sessions 3 and 4
Harbor Island II

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

1. Agenda review, Blue sheets and volunteers for taking notes and
   Jabber scribe       5 Mins

2. WG status and I-Ds update                5 Mins

3. Mobile IPv6 Operation with IKEv2 and the revised IPsec Architecture
   I-D: draft-ietf-mip6-ikev2-ipsec-06
   Vijay Devarapalli                    15 Mins

4. MIP6 support for DS hosts/routers
   I-D: draft-ietf-mip6-nemo-v4traversal-02
   Hesham Soliman                    10 Mins

5. AAA Goals for Mobile IPv6
   I-D: draft-ietf-mip6-aaa-ha-goals-03
   Gerardo Giaretta                        10 Mins

6. Home agent reliability protocol update
   I-D: draft-ietf-mip6-hareliability-00 (revised?)
   Ryuji Wakikawa                     10 Mins

7. Experimental and vendor specific messages
   I-D: draft-devarapalli-mip6-vsm-01
   I-D: draft-devarapalli-mip6-experimental-messages-00
   Vijay Devarapalli


8. Proxy Mobile IPv6 Discussion                15 Mins
   I-D: draft-sgundave-mipv6-proxymipv6-00
   I-D: draft-chowdhury-netmip6-01
   Sri Gundaveli/Kuntal Chowdhury

9. Next steps        Chairs                5 mins


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





mtp (Exim 4.43) id 1GcPqC-0007vW-BM
	for mip6@ietf.org; Tue, 24 Oct 2006 13:13:28 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcPex-0004yV-Pc
	for mip6@ietf.org; Tue, 24 Oct 2006 13:01:56 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9OH1k3p019602 for <mip6@ietf.org>; Tue, 24 Oct 2006 20:01:50 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 20:01:47 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 12:01:42 -0500
Received: from 172.19.244.193 ([172.19.244.193]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 24 Oct 2006 17:01:42 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 24 Oct 2006 12:03:47 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C163B1A3.27154%basavaraj.patil@nokia.com>
Thread-Topic: Note the change in meeting date for MIP6 at IETF67
Thread-Index: Acb3jl6HnOaLDmOBEduV2AARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 17:01:42.0202 (UTC)
	FILETIME=[1424F1A0:01C6F78E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [Mip6] Note the change in meeting date for MIP6 at IETF67
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Please note that the MIP6 WG meeting has now been scheduled for Tuesday, Nov
7th. The meeting is in the afternoon from 1740-1950.

The latest agenda is at:
http://www3.ietf.org/proceedings/06nov/agenda/mip6.txt

And as of Oct 24th:


TUESDAY, November 7, 2006
1740-1950 Afternoon Sessions 3 and 4
Harbor Island II

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

1. Agenda review, Blue sheets and volunteers for taking notes and
   Jabber scribe       5 Mins

2. WG status and I-Ds update                5 Mins

3. Mobile IPv6 Operation with IKEv2 and the revised IPsec Architecture
   I-D: draft-ietf-mip6-ikev2-ipsec-06
   Vijay Devarapalli                    15 Mins

4. MIP6 support for DS hosts/routers
   I-D: draft-ietf-mip6-nemo-v4traversal-02
   Hesham Soliman                    10 Mins

5. AAA Goals for Mobile IPv6
   I-D: draft-ietf-mip6-aaa-ha-goals-03
   Gerardo Giaretta                        10 Mins

6. Home agent reliability protocol update
   I-D: draft-ietf-mip6-hareliability-00 (revised?)
   Ryuji Wakikawa                     10 Mins

7. Experimental and vendor specific messages
   I-D: draft-devarapalli-mip6-vsm-01
   I-D: draft-devarapalli-mip6-experimental-messages-00
   Vijay Devarapalli


8. Proxy Mobile IPv6 Discussion                15 Mins
   I-D: draft-sgundave-mipv6-proxymipv6-00
   I-D: draft-chowdhury-netmip6-01
   Sri Gundaveli/Kuntal Chowdhury

9. Next steps        Chairs                5 mins


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





From mip6-bounces@ietf.org Tue Oct 24 14:28:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcQzl-0007XP-Hj; Tue, 24 Oct 2006 14:27:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcQzj-0007IB-QN
	for mip6@ietf.org; Tue, 24 Oct 2006 14:27:23 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcQzb-0006dM-I4
	for mip6@ietf.org; Tue, 24 Oct 2006 14:27:23 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9OIRCu0005420
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 24 Oct 2006 11:27:13 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.na.qualcomm.com
	[10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9OILXcf023593; Tue, 24 Oct 2006 11:27:11 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 11:27:06 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 11:27:06 -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] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Tue, 24 Oct 2006 11:27:04 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A2AC15E@NAEX14.na.qualcomm.com>
In-Reply-To: <453E482D.5090302@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb3j5dmXfjBOaMvTVKPAyq9SpVd5gACRUoQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 24 Oct 2006 18:27:06.0760 (UTC)
	FILETIME=[029E7080:01C6F79A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20

 > please lookup the earlier mails on why there is an
 > issue in the first place. you should still have
 > the mip6trans emails.
 >=20
 > for your benefit I am repeating them here.

=3D> I'm quite sure most people on this list are not psychic. Since no =
one
saw the DT mailing list except the DT members, you do need to explain
things for the benefit of the WG...

 >=20
 > - in the DS-MIPv6 case, there is only BCE that is
 > based on the MN's IPv6 home address. all other
 > information is tied to this BCE.=20

=3D> Are you saying this is how it should be? I assume you mean you'll
implement it this way. I hope you're not suggesting we mandate that in
the spec. In the current draft (yet to be announced) *nothing* is
mandated as far as the BC is concerned. And nothing should be mandated
as far as the implementation is concerned.

 > - we setup binding cache entries for the IPv4 home
 > address only in MIPv4.

=3D> Huh? Of course that's the case when only MIPv4 manages mobility for
IPv4 addresses.=20

 >=20
 > - we shouldn't mix up things by saying we create
 > binding cache entries for both the IPv4 and IPv6
 > HoAs.

=3D> Why not? What conceptual data structure are you suggesting ?=20

 > :) you want people to repeat things all the time.

=3D> No, only once to the WG who's supposed to know what the issue is
about...

 > for one there was never a consensus to call it a
 > binding cache entry for the IPv4 HoA. the issue
 > was open from the beginning. when we picked a draft
 > to be the base document, it does not mean everything
 > that is in there in the draft is already agreed to.

=3D> No one said everything in the draft must be accepted by the WG, not
to my knowledge anyway.

Hesham

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



From mip6-bounces@ietf.org Tue Oct 24 14:40:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcRB9-0003ia-IR; Tue, 24 Oct 2006 14:39:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcRB8-0003iV-OJ
	for mip6@ietf.org; Tue, 24 Oct 2006 14:39:10 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcRB4-0000GV-B7
	for mip6@ietf.org; Tue, 24 Oct 2006 14:39:10 -0400
Received: from [192.168.77.23] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 11:39:05 -0700
Message-ID: <453E5D06.3090706@azairenet.com>
Date: Tue, 24 Oct 2006 11:35:50 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7EB20EA0938B4D42A2D82689365C9B7A2AC15E@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A2AC15E@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 18:39:05.0437 (UTC)
	FILETIME=[AEFBD8D0:01C6F79B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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

Soliman, Hesham wrote:
>  
> 
>  > please lookup the earlier mails on why there is an
>  > issue in the first place. you should still have
>  > the mip6trans emails.
>  > 
>  > for your benefit I am repeating them here.
> 
> => I'm quite sure most people on this list are not psychic. Since no one
> saw the DT mailing list except the DT members, you do need to explain
> things for the benefit of the WG...

ok. but as an editor you are supposed to present
all the arguments related to the issue and then
ask for consensus on the mailing list. not present
it in a way such that it is easy to reject the
issue. that is not correct.

>  > - in the DS-MIPv6 case, there is only BCE that is
>  > based on the MN's IPv6 home address. all other
>  > information is tied to this BCE. 

you didnt respond to my first point.

> - in the DS-MIPv6 case, there is only BCE that is
> based on the MN's IPv6 home address. all other
> information is tied to this BCE. this may include
> tunnel state for the MN, forwarding state for an
> IPv6 NEMO prefix, forwarding state for the MN's
> IPv4 home address, forwarding state for the MN's
> IPv4 NEMO prefix. 

> => Are you saying this is how it should be? I assume you mean you'll
> implement it this way. I hope you're not suggesting we mandate that in
> the spec. In the current draft (yet to be announced) *nothing* is
> mandated as far as the BC is concerned. And nothing should be mandated
> as far as the implementation is concerned.

you are not responding to my email. you are
saying something very generic. I agree that no
implementation specific stuff should be mandated
in the spec. as I said in one of my earlier mails,
this issue is not about how to implement it, it
is about what to call it.

>  > - we setup binding cache entries for the IPv4 home
>  > address only in MIPv4.
> 
> => Huh? Of course that's the case when only MIPv4 manages mobility for
> IPv4 addresses. 
> 
>  > 
>  > - we shouldn't mix up things by saying we create
>  > binding cache entries for both the IPv4 and IPv6
>  > HoAs.
> 
> => Why not? What conceptual data structure are you suggesting ? 

no conceptual data structure at all. the forwarding
state for the IPv4 home address should be tied to
the BCE for the IPv6 home address. this may translate
into a routing entry for the IPv4 home address, but
it is still tied to the BCE for the IPv6 home address.
the routing state disappears when the BCE for the IPv6
home address is deleted.

>  > :) you want people to repeat things all the time.
> 
> => No, only once to the WG who's supposed to know what the issue is
> about...
> 
>  > for one there was never a consensus to call it a
>  > binding cache entry for the IPv4 HoA. the issue
>  > was open from the beginning. when we picked a draft
>  > to be the base document, it does not mean everything
>  > that is in there in the draft is already agreed to.
> 
> => No one said everything in the draft must be accepted by the WG, not
> to my knowledge anyway.

good. the point was that this has been an issue from
the beginning. so you can't claim that an issue has
been brought up against existing text and then suggest
rejecting it on the mailing list. you need to present
two options.

Vijay

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



From mip6-bounces@ietf.org Tue Oct 24 15:16:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcRkT-0000X8-PG; Tue, 24 Oct 2006 15:15:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcRkS-0000Wy-LH
	for mip6@ietf.org; Tue, 24 Oct 2006 15:15:40 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcRkR-000677-AD
	for mip6@ietf.org; Tue, 24 Oct 2006 15:15:40 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 12:15:38 -0700
Message-ID: <453E659D.40901@azairenet.com>
Date: Tue, 24 Oct 2006 12:12:29 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <44E8B357.9010705@piuha.net> <4519BF97.6070002@azairenet.com>
	<453BC9F7.1020703@piuha.net> <453BF6E0.9010506@azairenet.com>
	<453C3B49.8070103@piuha.net>
In-Reply-To: <453C3B49.8070103@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 19:15:38.0781 (UTC)
	FILETIME=[CA5194D0:01C6F7A0]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-ikev2-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:

>>> Is there a possibility that you could add a discussion
>>> of how the PAD needs to be configured for Mobile IPv6
>>> usage?
>> we have some text.
>>
>>    o  The home agent MAY use the Peer Authorization Database (PAD) [5]
>>       to store per-mobile node state.  The PAD entry for a mobile node
>>       MAY contain a shared key, public key or a trust anchor to verify
>>       the mobile node's certificate for authenticating the mobile node.
>>
>> AFAIK, the PAD entries are created either manually or
>> delivered via some proprietary interface.
>>
>> RFC 4306 avoids talking about PAD completely. so the
>> usage of PAD with IKEv2 is not clear to me.
> The text that you quoted above is about
> the additional things you could store in PAD.
> I am asking what the PAD as described in 4301
> will do in your application and how it needs
> to be configured.
> 
> I will try to recruit 4301 experts to help you
> on this.
> 
> Overall, I think we are close to being able to
> move your latest version forward in the process,
> though I still worry about the 4301 compatibility.
> But perhaps we can indicate this as an issue
> and ask for help while we simultaneously run
> the Last Call.

sounds good to me.

Vijay

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



From mip6-bounces@ietf.org Tue Oct 24 19:02:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcVG8-0007rX-Oo; Tue, 24 Oct 2006 19:00:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcVG7-0007rO-44
	for mip6@ietf.org; Tue, 24 Oct 2006 19:00:35 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcVFx-0000aw-Mc
	for mip6@ietf.org; Tue, 24 Oct 2006 19:00:27 -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
	k9ON0KkH025644
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 24 Oct 2006 16:00:21 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9OMxlS3018344; Tue, 24 Oct 2006 16:00:18 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 15:59:10 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Oct 2006 15:59:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Tue, 24 Oct 2006 15:59:08 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A2AC1AC@NAEX14.na.qualcomm.com>
In-Reply-To: <453E5D06.3090706@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb3m7khtQbK2fXaRIeGEWoZsbKE6AAAMo9w
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 24 Oct 2006 22:59:10.0294 (UTC)
	FILETIME=[04340F60:01C6F7C0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
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


 > ok. but as an editor you are supposed to present
 > all the arguments related to the issue and then
 > ask for consensus on the mailing list. not present
 > it in a way such that it is easy to reject the
 > issue. that is not correct.

=3D> I believe I did on every issue where there were multiple opinions
discussed. I'm finding it very difficult to represent the alternative
here because there is no technical implication for the spec. It's an
editorial issue that seems to be a matter of taste.

 >=20
 > >  > - in the DS-MIPv6 case, there is only BCE that is
 > >  > based on the MN's IPv6 home address. all other
 > >  > information is tied to this BCE.=20
 >=20
 > you didnt respond to my first point.
 >=20
 > > - in the DS-MIPv6 case, there is only BCE that is
 > > based on the MN's IPv6 home address. all other
 > > information is tied to this BCE. this may include
 > > tunnel state for the MN, forwarding state for an
 > > IPv6 NEMO prefix, forwarding state for the MN's
 > > IPv4 home address, forwarding state for the MN's
 > > IPv4 NEMO prefix.=20
 >=20
 > > =3D> Are you saying this is how it should be? I assume you=20
 > mean you'll
 > > implement it this way. I hope you're not suggesting we=20
 > mandate that in
 > > the spec. In the current draft (yet to be announced) *nothing* is
 > > mandated as far as the BC is concerned. And nothing should=20
 > be mandated
 > > as far as the implementation is concerned.
 >=20
 > you are not responding to my email. you are
 > saying something very generic. I agree that no
 > implementation specific stuff should be mandated
 > in the spec. as I said in one of my earlier mails,
 > this issue is not about how to implement it, it
 > is about what to call it.

=3D> So why does it matter what to call it? What you're saying amounts =
to
an editorial change. If that's the case, what's confusing about the
current text? I find it clear because it follows 3775, which is well
understood. I don't understand why we're discussing the "name" of this
storage area when no new name was introduced.

 > >  > - we shouldn't mix up things by saying we create
 > >  > binding cache entries for both the IPv4 and IPv6
 > >  > HoAs.
 > >=20
 > > =3D> Why not? What conceptual data structure are you suggesting ?=20
 >=20
 > no conceptual data structure at all. the forwarding
 > state for the IPv4 home address should be tied to
 > the BCE for the IPv6 home address.=20

=3D> You're simply replacing one conceptual representation with another.
What you describe above *is* a conceptual representation where a single
BCE is created and the IPv4 HoA is stored in it.=20

   this may translate
 > into a routing entry for the IPv4 home address, but
 > it is still tied to the BCE for the IPv6 home address.

=3D> If you read my reponse to Jean Luc Gimault you'll find that I said
that all those entries would be linked whether it's done in a separate
entry or not.=20

 > the routing state disappears when the BCE for the IPv6
 > home address is deleted.

=3D> Sure, which will happen in either case. Again I stated that in the
same email I mentioned above.

 > good. the point was that this has been an issue from
 > the beginning. so you can't claim that an issue has
 > been brought up against existing text and then suggest
 > rejecting it on the mailing list. you need to present
 > two options.

=3D> Of course the two options are represented if the issue text is
included in the same email. I didn't suggest pros and cons for either
option (if that's what you mean) because it's  an editorial matter of
taste which has no technical implications on the spec.

Hesham


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



From mip6-bounces@ietf.org Tue Oct 24 19:20:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcVYN-0008HK-Ud; Tue, 24 Oct 2006 19:19:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcVYM-0008Bb-OW
	for mip6@ietf.org; Tue, 24 Oct 2006 19:19:26 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcVYL-000797-CV
	for mip6@ietf.org; Tue, 24 Oct 2006 19:19:26 -0400
Received: from [10.1.201.0] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 16:19:20 -0700
Message-ID: <453E9E68.6040904@azairenet.com>
Date: Tue, 24 Oct 2006 16:14:48 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060927)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7EB20EA0938B4D42A2D82689365C9B7A2AC1AC@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A2AC1AC@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2006 23:19:20.0344 (UTC)
	FILETIME=[D5730980:01C6F7C2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
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

Hesham,

I don't believe we can converge on this issue. this
issue has been open for more than a year and we have
discussed it too many times. I am tired.

if anybody else has an opinion on this, please say
something. :)

Vijay

Soliman, Hesham wrote:
>  > ok. but as an editor you are supposed to present
>  > all the arguments related to the issue and then
>  > ask for consensus on the mailing list. not present
>  > it in a way such that it is easy to reject the
>  > issue. that is not correct.
> 
> => I believe I did on every issue where there were multiple opinions
> discussed. I'm finding it very difficult to represent the alternative
> here because there is no technical implication for the spec. It's an
> editorial issue that seems to be a matter of taste.
> 
>  > 
>  > >  > - in the DS-MIPv6 case, there is only BCE that is
>  > >  > based on the MN's IPv6 home address. all other
>  > >  > information is tied to this BCE. 
>  > 
>  > you didnt respond to my first point.
>  > 
>  > > - in the DS-MIPv6 case, there is only BCE that is
>  > > based on the MN's IPv6 home address. all other
>  > > information is tied to this BCE. this may include
>  > > tunnel state for the MN, forwarding state for an
>  > > IPv6 NEMO prefix, forwarding state for the MN's
>  > > IPv4 home address, forwarding state for the MN's
>  > > IPv4 NEMO prefix. 
>  > 
>  > > => Are you saying this is how it should be? I assume you 
>  > mean you'll
>  > > implement it this way. I hope you're not suggesting we 
>  > mandate that in
>  > > the spec. In the current draft (yet to be announced) *nothing* is
>  > > mandated as far as the BC is concerned. And nothing should 
>  > be mandated
>  > > as far as the implementation is concerned.
>  > 
>  > you are not responding to my email. you are
>  > saying something very generic. I agree that no
>  > implementation specific stuff should be mandated
>  > in the spec. as I said in one of my earlier mails,
>  > this issue is not about how to implement it, it
>  > is about what to call it.
> 
> => So why does it matter what to call it? What you're saying amounts to
> an editorial change. If that's the case, what's confusing about the
> current text? I find it clear because it follows 3775, which is well
> understood. I don't understand why we're discussing the "name" of this
> storage area when no new name was introduced.
> 
>  > >  > - we shouldn't mix up things by saying we create
>  > >  > binding cache entries for both the IPv4 and IPv6
>  > >  > HoAs.
>  > > 
>  > > => Why not? What conceptual data structure are you suggesting ? 
>  > 
>  > no conceptual data structure at all. the forwarding
>  > state for the IPv4 home address should be tied to
>  > the BCE for the IPv6 home address. 
> 
> => You're simply replacing one conceptual representation with another.
> What you describe above *is* a conceptual representation where a single
> BCE is created and the IPv4 HoA is stored in it. 
> 
>    this may translate
>  > into a routing entry for the IPv4 home address, but
>  > it is still tied to the BCE for the IPv6 home address.
> 
> => If you read my reponse to Jean Luc Gimault you'll find that I said
> that all those entries would be linked whether it's done in a separate
> entry or not. 
> 
>  > the routing state disappears when the BCE for the IPv6
>  > home address is deleted.
> 
> => Sure, which will happen in either case. Again I stated that in the
> same email I mentioned above.
> 
>  > good. the point was that this has been an issue from
>  > the beginning. so you can't claim that an issue has
>  > been brought up against existing text and then suggest
>  > rejecting it on the mailing list. you need to present
>  > two options.
> 
> => Of course the two options are represented if the issue text is
> included in the same email. I didn't suggest pros and cons for either
> option (if that's what you mean) because it's  an editorial matter of
> taste which has no technical implications on the spec.
> 
> Hesham
> 


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



From mip6-bounces@ietf.org Wed Oct 25 03:05:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GccoV-0006qh-HJ; Wed, 25 Oct 2006 03:04:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gccn8-0004kW-RM
	for mip6@ietf.org; Wed, 25 Oct 2006 03:03:10 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gccgz-0006Sa-IJ
	for mip6@ietf.org; Wed, 25 Oct 2006 02:56:50 -0400
X-VirusChecked: Checked
X-Env-Sender: saumya@motorola.com
X-Msg-Ref: server-9.tower-128.messagelabs.com!1161759342!4317672!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 27950 invoked from network); 25 Oct 2006 06:55:42 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-9.tower-128.messagelabs.com with SMTP;
	25 Oct 2006 06:55:42 -0000
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id k9P6tcL4027600
	for <mip6@ietf.org>; Tue, 24 Oct 2006 23:55:42 -0700 (MST)
Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k9P6taiU003590
	for <mip6@ietf.org>; Wed, 25 Oct 2006 01:55:37 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 Oct 2006 14:55:34 +0800
Message-ID: <AE007C20C0A3D44D8EE9DD46764559AD01513207@ZMY16EXM67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-saumya-mip6-bootstrap-00.txt 
thread-index: AcbvAcZkO6zoZsuOQras2dO91gxQsgI9R7Eg
From: "Upadhyaya Saumya-a20369" <saumya@motorola.com>
To: <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Subject: [Mip6] FW: I-D ACTION:draft-saumya-mip6-bootstrap-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

Below is a draft that addresses the MIPv6 bootstrapping in both the
split and integrated scenarios using a single solution.

Please review and comment on this work.

Thanks
Saumya

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Saturday, October 14, 2006 1:20 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-saumya-mip6-bootstrap-00.txt=20

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


	Title		: MIPv6 bootstrapping solution for split and
integrated scenario using DHCPv6=20
	Author(s)	: S. Upadhyaya
	Filename	: draft-saumya-mip6-bootstrap-00.txt
	Pages		: 13
	Date		: 2006-10-13
=09
   In mobile IPv6 (MIP6), there is a need to transfer the home agent=20
   address, home IP address to the mobile node when the mobile node is=20
   in the foreign network. This problem is referred to as bootstrapping.

   This document defines a Bootstrapping Information Server Function=20
   (BISF) and Bootstrapping Information Client Function (BICF). The BICF

   uses AAA messaging for obtaining the bootstrapping information from=20
   the BISF. Such a mechanism can be used by either the integrated or=20
   split scenarios. =20


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

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

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

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

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

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

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



From mip6-bounces@ietf.org Wed Oct 25 07:11:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcgex-0003rB-6T; Wed, 25 Oct 2006 07:10:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcgev-0003qD-Uy
	for mip6@ietf.org; Wed, 25 Oct 2006 07:10:57 -0400
Received: from sehan002bb.han.telia.se ([131.115.18.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcget-000804-IF
	for mip6@ietf.org; Wed, 25 Oct 2006 07:10:57 -0400
Received: from SEHAN021MB.tcad.telia.se ([131.115.18.160]) by
	sehan002bb.han.telia.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Oct 2006 13:10:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 Oct 2006 13:10:37 +0200
Message-ID: <5D25AEFB114D034FBDC8B156FCA78E030135A5E1@SEHAN021MB.tcad.telia.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: about HA switch message
Thread-Index: Acb4JjLMfoGI0VMiRruAmmQHoCYBxg==
From: <jouni.korhonen@teliasonera.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 25 Oct 2006 11:10:41.0398 (UTC)
	FILETIME=[35570960:01C6F826]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Mip6] about HA switch message
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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,

After reading this draft again I got few questions. Maybe these
have been asked earlier already, in which case I have missed
them.

I guess the home agent switch message could also be used for general
signaling from HA to MN? I.e. setting # addresses to 1 and giving the
address of the current HA as the alternative HA address. Then using
Mobility Options to carry whatever an operator wants to sporadically
send from the HA to the MN. This would also have some side effects
on the retransmission logic I guess.

Also the security considerations state that the message must be
protected using the IPSec SAs between the HA and the MN. What
about RFC4285 auth option?

Cheers,
	Jouni

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



From mip6-bounces@ietf.org Wed Oct 25 09:26:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcilt-0006iF-S7; Wed, 25 Oct 2006 09:26:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcikW-0004lk-RH
	for mip6@ietf.org; Wed, 25 Oct 2006 09:24:52 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GciZy-0001bz-GL
	for mip6@ietf.org; Wed, 25 Oct 2006 09:14:02 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 25 Oct 2006 15:13:56 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9PDDtmi011471; Wed, 25 Oct 2006 15:13:55 +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 k9PDDtmd009708; 
	Wed, 25 Oct 2006 15:13:55 +0200 (MEST)
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, 25 Oct 2006 15:13:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Wed, 25 Oct 2006 15:13:29 +0200
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC02E34086@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb3xLbBkflLxb6qRJCUiv6/ABxoHwAakLDQ
From: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>
X-OriginalArrivalTime: 25 Oct 2006 13:13:54.0986 (UTC)
	FILETIME=[6C4308A0:01C6F837]
DKIM-Signature: a=rsa-sha1; q=dns; l=4299; t=1161782035; x=1162646035;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pthubert@cisco.com;
	z=From:=22Pascal=20Thubert=20\(pthubert\)=22=20<pthubert@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Re=3A=20[issue66]=20Setting=20up=20forwarding=20for=20I
	Pv4=20HoA;
	X=v=3Dcisco.com=3B=20h=3DVWFUP/3uPa5u69/UqSjYGErJGxA=3D;
	b=E62oCJPIHCUI6rG4I5aGbj4VVI4uhQ314aGLyJ0NBQDezhejDEB8h2BggCgcYDNoQNru0OaQ
	RwtwMqqG53CIVSIBE7Yl5upHLbOXPj9MUIRirK9maMFENolSslC9eeG9;
Authentication-Results: ams-dkim-1; header.From=pthubert@cisco.com; dkim=pass (
	sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



>-----Original Message-----
>From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>Sent: Wednesday, October 25, 2006 1:15 AM
>To: Soliman, Hesham
>Cc: mip6@ietf.org
>Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
>
>Hesham,
>
>I don't believe we can converge on this issue. this
>issue has been open for more than a year and we have
>discussed it too many times. I am tired.
>
[Pascal] OK; let me jump in then.=20

I agree with both :) maybe it's a matter of wording.

I do not mind having a conceptual data structure. As Hesham says, we
have that in other drafts. It helps implementers remember the core data
they have to store. The conceptual data can be stored as a single
control block in memory, or as multiple tables in a distributed
database, alone or mixed with other data. That's why it's only
conceptual.

What is NOT conceptual (and that's when I agree with Vijay) is the index
to the data. The protocol must ensure that the index to the conceptual
data is unique. And that unique index in MIP6, NEMO and MIPTRANS is the
IPv6 Home Address. Using an IPv6 address guarantees the global
uniqueness of the index, the scalability of the protocol, etc... And
this is one good reason why MIPTRANS builds on MIP6/NEMO as opposed to
MIP4.

The MIPTRANS conceptual data could be stored in an IPv6 table and an
IPv4 table in a given implementation, but both tables MUST be indexed
with the IPv6 Home Address. In my mind that makes it a single conceptual
binding cache, but that's secondary.

The key is that the IPv4 Home Address in the draft is not a Home Address
stricto sensu, as understood in MIP4, MIP6 and NEMO. It is just an IPv4
address that the Home Agent can bind to that mobile node, just like it
will bind a prefix to a Mobile Router. Note that MRs do not need to bind
an IPv4 Home Address at all: all they need to bind is an IPv4 subnet.

So I'm fine with storing the IPv4 HoA in the conceptual BCE, together
with the prefixes in the BUs as Hesham suggests. I'd wish some text to
make sure that it is very clear that the IPv4 HoA does not inherit the
index characteristics from the MIPx/NEMO RFCs.=20

I'm afraid that part of this discussion comes from the name of the
option, IPv4 home address option. Consider this, when the 'p' bit is
set, this is the equivalent of the Mobile Network Prefix Option in NEMO.


Again: MIPTRANS IPv4 home address option IS_SAME_AS RFC3963 Mobile
Network Prefix Option.=20

Also, if you go back to RFC 3775, there is a Home Address Option, the
destination option that's used to swap woth the source address in the
packet. And now:

Again: MIPTRANS IPv4 home address option IS_ALIEN_FROM RFC3775 Home
Address Option

Also, the IPv4 address does not have to be from a 'Home'. There might
not be an IPv4 Home. For instance, the HA could be a NAT and give a same
private address to all MNs. You can not do that with MIP4 because the
IPv4 HoA is the index, but MIPTRANS enables this.

Finally, the word "address" is used in the name of the option though for
NEMO it will be a prefix (or a subnet I do not mind the wording).

At the end of the day, I figure that the name of the option is
ill-chosen, and I see that as the source of the miscommunication around
issue 66.

=20
I'd say:

1) About the following text the end of page 18 of version 02
" - If the binding update is accepted for the IPv4 home address, the
     home agent MUST create a binding cache entry for the IPv4 home
     address/prefix. If a single IPv4 home address were requested, it
     MAY be stored in the IPv4-mapped IPv6 address format. The home
     agent MUST include an IPv4 acknowledgement option in the mobility
     header containing the binding acknowledgement.
"

I agree with Vijay that the text should be improved to avoid confusion.
I agree with Hesham that we can keep the conceptual data. I want to make
sure that the IPv4 "HoA" is not confused to be an index to the BCE being
created in that text.

2) About the IPv4 home address option
Can I suggest to rename it "IPv4 addressing option". That removes the
similarity in name with the MIP6 option, and opens to the fact that it
can carry a prefix.

What do you think?
=09

Pascal

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



From mip6-bounces@ietf.org Wed Oct 25 10:19:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcjbd-0005r4-UX; Wed, 25 Oct 2006 10:19:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcjbd-0005qz-0Y
	for mip6@ietf.org; Wed, 25 Oct 2006 10:19:45 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcjbX-0000wN-2W
	for mip6@ietf.org; Wed, 25 Oct 2006 10:19:44 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9PEJaZv027890
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 25 Oct 2006 07:19:36 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.na.qualcomm.com
	[129.46.134.172])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9PEJX1o009808; Wed, 25 Oct 2006 07:19:35 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Oct 2006 07:19:33 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Oct 2006 07:19:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Wed, 25 Oct 2006 07:19:31 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A2AC207@NAEX14.na.qualcomm.com>
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC02E34086@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb3xLbBkflLxb6qRJCUiv6/ABxoHwAakLDQAAQi5LA=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 25 Oct 2006 14:19:33.0085 (UTC)
	FILETIME=[978D40D0:01C6F840]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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'm glad we have more than two people making comments!=20


 > I agree with both :) maybe it's a matter of wording.
 >=20
 > I do not mind having a conceptual data structure. As Hesham says, we
 > have that in other drafts. It helps implementers remember=20
 > the core data
 > they have to store. The conceptual data can be stored as a single
 > control block in memory, or as multiple tables in a distributed
 > database, alone or mixed with other data. That's why it's only
 > conceptual.
 >=20
 > What is NOT conceptual (and that's when I agree with Vijay)=20
 > is the index
 > to the data. The protocol must ensure that the index to the=20
 > conceptual
 > data is unique. And that unique index in MIP6, NEMO and=20
 > MIPTRANS is the
 > IPv6 Home Address. Using an IPv6 address guarantees the global
 > uniqueness of the index, the scalability of the protocol, etc... And
 > this is one good reason why MIPTRANS builds on MIP6/NEMO as=20
 > opposed to
 > MIP4.

=3D> I completely agree with you. I believe what you're saying is that
it's fine to describe conceptual data in the draft but we need to ensure
that the MN is identified by its IPv6 HoA. This is perfectly fine with
me and essentially guaranteed by the draft since we use MIPv6 and
piggyback additional requests in the BU on the MN's identity, which is
the IPv6 HoA. In other  words, you can't send the BU without the IPv6
HoA.

 > So I'm fine with storing the IPv4 HoA in the conceptual BCE, together
 > with the prefixes in the BUs as Hesham suggests. I'd wish=20
 > some text to
 > make sure that it is very clear that the IPv4 HoA does not=20
 > inherit the
 > index characteristics from the MIPx/NEMO RFCs.=20

=3D> Fine with me.

 >=20
 > I'm afraid that part of this discussion comes from the name of the
 > option, IPv4 home address option. Consider this, when the 'p' bit is
 > set, this is the equivalent of the Mobile Network Prefix=20
 > Option in NEMO.

=3D> Please note that we explicitly state in the draft that we use the
address to represent the address/prefix format, where "prefix" is a
variable length. Similarly, we explicitly state that the term "mobile
node" is used to represent hosts and routers.

 > Again: MIPTRANS IPv4 home address option IS_SAME_AS RFC3963 Mobile
 > Network Prefix Option.=20
 >=20
 > Also, if you go back to RFC 3775, there is a Home Address Option, the
 > destination option that's used to swap woth the source address in the
 > packet. And now:
 >=20
 > Again: MIPTRANS IPv4 home address option IS_ALIEN_FROM RFC3775 Home
 > Address Option

=3D> Yes to all of the above.

 > Finally, the word "address" is used in the name of the=20
 > option though for
 > NEMO it will be a prefix (or a subnet I do not mind the wording).

=3D> Please see above.

 > I'd say:
 >=20
 > 1) About the following text the end of page 18 of version 02
 > " - If the binding update is accepted for the IPv4 home address, the
 >      home agent MUST create a binding cache entry for the IPv4 home
 >      address/prefix. If a single IPv4 home address were requested, it
 >      MAY be stored in the IPv4-mapped IPv6 address format. The home
 >      agent MUST include an IPv4 acknowledgement option in=20
 > the mobility
 >      header containing the binding acknowledgement.
 > "
 >=20
 > I agree with Vijay that the text should be improved to avoid=20
 > confusion.
 > I agree with Hesham that we can keep the conceptual data. I=20
 > want to make
 > sure that the IPv4 "HoA" is not confused to be an index to=20
 > the BCE being
 > created in that text.

=3D> Feel free to suggest text. The "MUSTs" above should not be there, I
thought I removed them all but I must have missed one.

 >=20
 > 2) About the IPv4 home address option
 > Can I suggest to rename it "IPv4 addressing option". That removes the
 > similarity in name with the MIP6 option, and opens to the=20
 > fact that it
 > can carry a prefix.
 >=20
 > What do you think?

=3D> That's fine with me.

Hesham


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



From mip6-bounces@ietf.org Wed Oct 25 11:53:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcl42-0002of-ME; Wed, 25 Oct 2006 11:53:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcl40-0002oa-QQ
	for mip6@ietf.org; Wed, 25 Oct 2006 11:53:08 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcl3w-0004jO-GO
	for mip6@ietf.org; Wed, 25 Oct 2006 11:53:08 -0400
Received: from smtp2.fc.hp.com (smtp-test.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id C4622391BD;
	Wed, 25 Oct 2006 11:53:03 -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 2907C10BF7F;
	Wed, 25 Oct 2006 15:53:03 +0000 (UTC)
Message-ID: <453F885D.8090208@hp.com>
Date: Wed, 25 Oct 2006 11:53:01 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: jouni.korhonen@teliasonera.com
Subject: Re: [Mip6] about HA switch message
References: <5D25AEFB114D034FBDC8B156FCA78E030135A5E1@SEHAN021MB.tcad.telia.se>
In-Reply-To: <5D25AEFB114D034FBDC8B156FCA78E030135A5E1@SEHAN021MB.tcad.telia.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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 Jouni,

Thanks for reading the draft.

> I guess the home agent switch message could also be used for general
> signaling from HA to MN? I.e. setting # addresses to 1 and giving the
> address of the current HA as the alternative HA address. Then using
> Mobility Options to carry whatever an operator wants to sporadically
> send from the HA to the MN. This would also have some side effects
> on the retransmission logic I guess.

I guess it could do that, although it was not the intention, also the 
draft doesn't define any valid options.  I have an expired draft that is 
probably in need of an update - draft-haley-mip6-mh-signaling-01 that 
proposes that solution.

> Also the security considerations state that the message must be
> protected using the IPSec SAs between the HA and the MN. What
> about RFC4285 auth option?

Yes, I guess RFC 4285 auth option should be supported, I can add that in 
the next revision.

Thanks,

-Brian

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



From mip6-bounces@ietf.org Wed Oct 25 13:08:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcmE1-0004KT-2E; Wed, 25 Oct 2006 13:07:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcmDz-0004KO-Va
	for mip6@ietf.org; Wed, 25 Oct 2006 13:07:31 -0400
Received: from mail2.iabg.de ([62.245.167.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcmDv-0002yM-K4
	for mip6@ietf.org; Wed, 25 Oct 2006 13:07:31 -0400
Received: from mail2.iabg.de (localhost [127.0.0.1])
	by localhost.iabg.de (Mailserver2 IABG) with ESMTP id 60E0C11F8;
	Wed, 25 Oct 2006 19:07:10 +0200 (CEST)
Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37])
	by mail2.iabg.de (Mailserver2 IABG) with ESMTP id 4CD8911D0;
	Wed, 25 Oct 2006 19:07:10 +0200 (CEST)
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: AW: [Mip6] about HA switch message
Date: Wed, 25 Oct 2006 19:06:49 +0200
Message-ID: <69A5E767EC979846826F566C7932A3F2046DE81B@exchange03.iabg.de>
In-Reply-To: <453F885D.8090208@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] about HA switch message
Thread-Index: Acb4ThIPP0VymZI+Q7C0o20KmQVoZAACYJHg
From: "Fritsche Wolfgang" <Fritsche@iabg.de>
To: "Brian Haley" <brian.haley@hp.com>,
	<jouni.korhonen@teliasonera.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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

BTW, has there be a specific reason for not specifying a kind of "Home =
Agent Swick Acknowledgement/Reply" message?

Cheers,

Wolfgang

>-----Urspr=FCngliche Nachricht-----
>Von: Brian Haley [mailto:brian.haley@hp.com]=20
>Gesendet: Mittwoch, 25. Oktober 2006 17:53
>An: jouni.korhonen@teliasonera.com
>Cc: mip6@ietf.org
>Betreff: Re: [Mip6] about HA switch message
>
>Hi Jouni,
>
>Thanks for reading the draft.
>
>> I guess the home agent switch message could also be used for general=20
>> signaling from HA to MN? I.e. setting # addresses to 1 and=20
>giving the=20
>> address of the current HA as the alternative HA address. Then using=20
>> Mobility Options to carry whatever an operator wants to sporadically=20
>> send from the HA to the MN. This would also have some side=20
>effects on=20
>> the retransmission logic I guess.
>
>I guess it could do that, although it was not the intention,=20
>also the draft doesn't define any valid options.  I have an=20
>expired draft that is probably in need of an update -=20
>draft-haley-mip6-mh-signaling-01 that proposes that solution.
>
>> Also the security considerations state that the message must be=20
>> protected using the IPSec SAs between the HA and the MN. What about=20
>> RFC4285 auth option?
>
>Yes, I guess RFC 4285 auth option should be supported, I can=20
>add that in the next revision.
>
>Thanks,
>
>-Brian
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Oct 25 13:12:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcmJ9-0001VV-2T; Wed, 25 Oct 2006 13:12:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcmJ7-0001VQ-Ok
	for mip6@ietf.org; Wed, 25 Oct 2006 13:12:49 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcmJ5-0003yg-GF
	for mip6@ietf.org; Wed, 25 Oct 2006 13:12:49 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 0533C385E8;
	Wed, 25 Oct 2006 13:12:46 -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 5E5A210A728;
	Wed, 25 Oct 2006 17:12:46 +0000 (UTC)
Message-ID: <453F9B0D.3040004@hp.com>
Date: Wed, 25 Oct 2006 13:12:45 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Fritsche Wolfgang <Fritsche@iabg.de>
Subject: Re: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE81B@exchange03.iabg.de>
In-Reply-To: <69A5E767EC979846826F566C7932A3F2046DE81B@exchange03.iabg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Fritsche Wolfgang wrote:
> BTW, has there be a specific reason for not specifying a kind of "Home Agent Swick Acknowledgement/Reply" message?

The Binding Update the MN sends serves as the Ack, so there was no need 
for another message.

-Brian

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



From mip6-bounces@ietf.org Wed Oct 25 13:18:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcmOp-0005Ff-Fi; Wed, 25 Oct 2006 13:18:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcmOn-0005FY-27
	for mip6@ietf.org; Wed, 25 Oct 2006 13:18:41 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcmOg-00052T-FJ
	for mip6@ietf.org; Wed, 25 Oct 2006 13:18:41 -0400
Received: by ug-out-1314.google.com with SMTP id 72so131517ugd
	for <mip6@ietf.org>; Wed, 25 Oct 2006 10:18:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=LKdINFfOlsqmy6+xGD4rLRzDuW9jAXJqK10TQU9Q2nJER0zwIPNKXL4KiWc7N9wqH4NSUQ9F3v+dnFOboqJW6/JY15wZP254z8DyZZY85/kIK2XqxyKehs+zBHW3Wd8T6QVZzlPkTYdNML1sf5ihadFJPDRQUiZIH0d/CFU1WlM=
Received: by 10.78.165.16 with SMTP id n16mr1155706hue;
	Wed, 25 Oct 2006 10:18:32 -0700 (PDT)
Received: from ?203.178.143.168? ( [203.178.143.168])
	by mx.google.com with ESMTP id 30sm1285121hub.2006.10.25.10.18.28;
	Wed, 25 Oct 2006 10:18:32 -0700 (PDT)
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A2AC207@NAEX14.na.qualcomm.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A2AC207@NAEX14.na.qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BFC430B8-83B1-4C24-A912-5CA3F8F18605@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Thu, 26 Oct 2006 02:18:19 +0900
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi  Hesham,

On 2006/10/25, at 23:19, Soliman, Hesham wrote:

> I'm glad we have more than two people making comments!

OK, let me jump in, too:-)

I agree with Pascal, too.

There is  another possible problem of using BC for IPv4 HoA.
After MN sends a BU with IPv4 HoA option and registers two bindings  
for both v4 and v6 HoA,
what happened if MN sends de-register BU without IPv4 HoA?
The both bindings should be removed. However, if each HoA is managed  
in separate BC,
it is hard to identify the BC for IPv4 HoA. This is problem when BC  
is indexed by IPv4 HoA.

Anyway, Hesham agree with Pascal.
As Pascal said in the comments,  IPv4 HoA treatment is very similar  
to MNP in the NEMO.
You can simply say that a HA creates a forwarding for each IPv4 HoA  
as RFC3963.
If you really keep the conceptual data,
you should remove all the paragraph saying like

"If the binding update is accepted for both IPv4 and IPv6 home
    addresses, the home agent MUST create two separate binding cache
    entries, one for each home address." (section 4.4)

This text strongly requests creating two binding cache entries to  
implementations.

My suggestion is
"The home agent MUST create a binding cache entry for IPv6 HoA and
  MUST setup  a forwarding for the IPv4 HoA. The forwarding information
  can be stored in anyway  (ex. binding cache entry). "

regards,
ryuji




>
>> I agree with both :) maybe it's a matter of wording.
>>
>> I do not mind having a conceptual data structure. As Hesham says, we
>> have that in other drafts. It helps implementers remember
>> the core data
>> they have to store. The conceptual data can be stored as a single
>> control block in memory, or as multiple tables in a distributed
>> database, alone or mixed with other data. That's why it's only
>> conceptual.
>>
>> What is NOT conceptual (and that's when I agree with Vijay)
>> is the index
>> to the data. The protocol must ensure that the index to the
>> conceptual
>> data is unique. And that unique index in MIP6, NEMO and
>> MIPTRANS is the
>> IPv6 Home Address. Using an IPv6 address guarantees the global
>> uniqueness of the index, the scalability of the protocol, etc... And
>> this is one good reason why MIPTRANS builds on MIP6/NEMO as
>> opposed to
>> MIP4.
>
> => I completely agree with you. I believe what you're saying is that
> it's fine to describe conceptual data in the draft but we need to  
> ensure
> that the MN is identified by its IPv6 HoA. This is perfectly fine with
> me and essentially guaranteed by the draft since we use MIPv6 and
> piggyback additional requests in the BU on the MN's identity, which is
> the IPv6 HoA. In other  words, you can't send the BU without the IPv6
> HoA.
>
>> So I'm fine with storing the IPv4 HoA in the conceptual BCE, together
>> with the prefixes in the BUs as Hesham suggests. I'd wish
>> some text to
>> make sure that it is very clear that the IPv4 HoA does not
>> inherit the
>> index characteristics from the MIPx/NEMO RFCs.
>
> => Fine with me.
>
>>
>> I'm afraid that part of this discussion comes from the name of the
>> option, IPv4 home address option. Consider this, when the 'p' bit is
>> set, this is the equivalent of the Mobile Network Prefix
>> Option in NEMO.
>
> => Please note that we explicitly state in the draft that we use the
> address to represent the address/prefix format, where "prefix" is a
> variable length. Similarly, we explicitly state that the term "mobile
> node" is used to represent hosts and routers.
>
>> Again: MIPTRANS IPv4 home address option IS_SAME_AS RFC3963 Mobile
>> Network Prefix Option.
>>
>> Also, if you go back to RFC 3775, there is a Home Address Option, the
>> destination option that's used to swap woth the source address in the
>> packet. And now:
>>
>> Again: MIPTRANS IPv4 home address option IS_ALIEN_FROM RFC3775 Home
>> Address Option
>
> => Yes to all of the above.
>
>> Finally, the word "address" is used in the name of the
>> option though for
>> NEMO it will be a prefix (or a subnet I do not mind the wording).
>
> => Please see above.
>
>> I'd say:
>>
>> 1) About the following text the end of page 18 of version 02
>> " - If the binding update is accepted for the IPv4 home address, the
>>      home agent MUST create a binding cache entry for the IPv4 home
>>      address/prefix. If a single IPv4 home address were requested, it
>>      MAY be stored in the IPv4-mapped IPv6 address format. The home
>>      agent MUST include an IPv4 acknowledgement option in
>> the mobility
>>      header containing the binding acknowledgement.
>> "
>>
>> I agree with Vijay that the text should be improved to avoid
>> confusion.
>> I agree with Hesham that we can keep the conceptual data. I
>> want to make
>> sure that the IPv4 "HoA" is not confused to be an index to
>> the BCE being
>> created in that text.
>
> => Feel free to suggest text. The "MUSTs" above should not be there, I
> thought I removed them all but I must have missed one.
>
>>
>> 2) About the IPv4 home address option
>> Can I suggest to rename it "IPv4 addressing option". That removes the
>> similarity in name with the MIP6 option, and opens to the
>> fact that it
>> can carry a prefix.
>>
>> What do you think?
>
> => That's fine with me.
>
> 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 Oct 25 13:28:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcmYO-0002C4-DY; Wed, 25 Oct 2006 13:28:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcmYN-0002By-CO
	for mip6@ietf.org; Wed, 25 Oct 2006 13:28:35 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcmYL-0007BO-TB
	for mip6@ietf.org; Wed, 25 Oct 2006 13:28:35 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 10:28:31 -0700
Message-ID: <453F9EBC.4020406@azairenet.com>
Date: Wed, 25 Oct 2006 10:28:28 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: jouni.korhonen@teliasonera.com
Subject: Re: [Mip6] about HA switch message
References: <5D25AEFB114D034FBDC8B156FCA78E030135A5E1@SEHAN021MB.tcad.telia.se>
In-Reply-To: <5D25AEFB114D034FBDC8B156FCA78E030135A5E1@SEHAN021MB.tcad.telia.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Oct 2006 17:28:31.0547 (UTC)
	FILETIME=[FDCD40B0:01C6F85A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jouni,

jouni.korhonen@teliasonera.com wrote:
> Hi,
> 
> After reading this draft again I got few questions. Maybe these
> have been asked earlier already, in which case I have missed
> them.
> 
> I guess the home agent switch message could also be used for general
> signaling from HA to MN? I.e. setting # addresses to 1 and giving the
> address of the current HA as the alternative HA address. Then using
> Mobility Options to carry whatever an operator wants to sporadically
> send from the HA to the MN. This would also have some side effects
> on the retransmission logic I guess.

the only use-case we could nail down was the HA
Switch. thats why we decided to standardize it.
if there are more cases, I guess we could
standardize a generic notification message.

Vijay

> 
> Also the security considerations state that the message must be
> protected using the IPSec SAs between the HA and the MN. What
> about RFC4285 auth option?
> 
> Cheers,
> 	Jouni
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Oct 25 13:36:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcmfs-0000ct-IA; Wed, 25 Oct 2006 13:36:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcmfr-0000co-PC
	for mip6@ietf.org; Wed, 25 Oct 2006 13:36:19 -0400
Received: from mail2.iabg.de ([62.245.167.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcmfq-00006v-Fx
	for mip6@ietf.org; Wed, 25 Oct 2006 13:36:19 -0400
Received: from mail2.iabg.de (localhost [127.0.0.1])
	by localhost.iabg.de (Mailserver2 IABG) with ESMTP id 990AAE22;
	Wed, 25 Oct 2006 19:36:11 +0200 (CEST)
Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37])
	by mail2.iabg.de (Mailserver2 IABG) with ESMTP id 83921DFF;
	Wed, 25 Oct 2006 19:36:11 +0200 (CEST)
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: AW: AW: [Mip6] about HA switch message
Date: Wed, 25 Oct 2006 19:35:51 +0200
Message-ID: <69A5E767EC979846826F566C7932A3F2046DE81F@exchange03.iabg.de>
In-Reply-To: <453F9B0D.3040004@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [Mip6] about HA switch message
Thread-Index: Acb4WMuSEZVRGtj9TF2qVI311bW0FwAAoUvA
From: "Fritsche Wolfgang" <Fritsche@iabg.de>
To: "Brian Haley" <brian.haley@hp.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 read this in draft-ietf-mip6-ha-switch-01.txt and also partly in =
draft-ietf-mip6-hareliability-00.txt, however, chapter 8.3 of =
draft-ietf-mip6-hareliability-00.txt also says

   "However, in this specification, the binding cache
   information is already synchronized among the redundant home agent
   set, the mobile node can skip this binding re-registration to the new
   active home agent.  In this case, the mobile node only updates the
   Home Agent address of all the binding update list, MIP6 tunnel end
   points, etc."

This seems to indicate that sending a BU to the new active HA is left as =
optional to the MN, that is, in this case also the Ack for the HA Switch =
will be optional, right?

Wolfgang

>-----Urspr=FCngliche Nachricht-----
>Von: Brian Haley [mailto:brian.haley@hp.com]=20
>Gesendet: Mittwoch, 25. Oktober 2006 19:13
>An: Fritsche Wolfgang
>Cc: jouni.korhonen@teliasonera.com; mip6@ietf.org
>Betreff: Re: AW: [Mip6] about HA switch message
>
>Fritsche Wolfgang wrote:
>> BTW, has there be a specific reason for not specifying a=20
>kind of "Home Agent Swick Acknowledgement/Reply" message?
>
>The Binding Update the MN sends serves as the Ack, so there=20
>was no need for another message.
>
>-Brian
>

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



From mip6-bounces@ietf.org Wed Oct 25 13:58:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcn1O-0005eJ-Ck; Wed, 25 Oct 2006 13:58:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcn1N-0005eD-23
	for mip6@ietf.org; Wed, 25 Oct 2006 13:58:33 -0400
Received: from mail2.iabg.de ([62.245.167.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcn1L-0003vD-KF
	for mip6@ietf.org; Wed, 25 Oct 2006 13:58:33 -0400
Received: from mail2.iabg.de (localhost [127.0.0.1])
	by localhost.iabg.de (Mailserver2 IABG) with ESMTP id 969A311F8;
	Wed, 25 Oct 2006 19:58:24 +0200 (CEST)
Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37])
	by mail2.iabg.de (Mailserver2 IABG) with ESMTP id 8174811D1;
	Wed, 25 Oct 2006 19:58:24 +0200 (CEST)
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: AW: [Mip6] about HA switch message
Date: Wed, 25 Oct 2006 19:58:04 +0200
Message-ID: <69A5E767EC979846826F566C7932A3F2046DE829@exchange03.iabg.de>
In-Reply-To: <453F9EBC.4020406@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] about HA switch message
Thread-Index: Acb4WzUVpBTIRneVT5m0+ahH+JtbKgAAvdmw
From: "Fritsche Wolfgang" <Fritsche@iabg.de>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	<jouni.korhonen@teliasonera.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay,

I think there are scenarios requiring an immediate HA Switch (e.g. HA =
failure) and scenarios allowing for some more time to stay with the =
current HA (e.g. upcoming maintenance). For the latter category one =
could allow established sessions to stay for a certain time with the =
current HA, and force new sessions to make use of the new HA. This would =
allow established connections to survive for a certain time after =
receiving the HA Switch, which could be long enough to have these =
established sessions ended anyway. Such a time period could be one of =
the mobility options carried by a HA Switch message. What do you think?

Wolfgang

>-----Urspr=FCngliche Nachricht-----
>Von: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
>Gesendet: Mittwoch, 25. Oktober 2006 19:28
>An: jouni.korhonen@teliasonera.com
>Cc: mip6@ietf.org
>Betreff: Re: [Mip6] about HA switch message
>
>Hi Jouni,
>
>jouni.korhonen@teliasonera.com wrote:
>> Hi,
>>=20
>> After reading this draft again I got few questions. Maybe these have=20
>> been asked earlier already, in which case I have missed them.
>>=20
>> I guess the home agent switch message could also be used for general=20
>> signaling from HA to MN? I.e. setting # addresses to 1 and=20
>giving the=20
>> address of the current HA as the alternative HA address. Then using=20
>> Mobility Options to carry whatever an operator wants to sporadically=20
>> send from the HA to the MN. This would also have some side=20
>effects on=20
>> the retransmission logic I guess.
>
>the only use-case we could nail down was the HA Switch. thats=20
>why we decided to standardize it.
>if there are more cases, I guess we could standardize a=20
>generic notification message.
>
>Vijay
>
>>=20
>> Also the security considerations state that the message must be=20
>> protected using the IPSec SAs between the HA and the MN. What about=20
>> RFC4285 auth option?
>>=20
>> Cheers,
>> 	Jouni
>>=20
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Oct 25 13:58:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcn1n-0005pM-GF; Wed, 25 Oct 2006 13:58:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcn1l-0005p8-Tk
	for mip6@ietf.org; Wed, 25 Oct 2006 13:58:57 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcn1k-000415-HV
	for mip6@ietf.org; Wed, 25 Oct 2006 13:58:57 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 10:58:55 -0700
Message-ID: <453FA5E1.9040709@azairenet.com>
Date: Wed, 25 Oct 2006 10:58:57 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7892795E1A87F04CADFCCF41FADD00FC02E34086@xmb-ams-337.emea.cisco.com>
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC02E34086@xmb-ams-337.emea.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Oct 2006 17:58:55.0875 (UTC)
	FILETIME=[3D2F9D30:01C6F85F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Pascal Thubert (pthubert) wrote:

> What is NOT conceptual (and that's when I agree with Vijay) is the index
> to the data. The protocol must ensure that the index to the conceptual
> data is unique. And that unique index in MIP6, NEMO and MIPTRANS is the
> IPv6 Home Address. Using an IPv6 address guarantees the global
> uniqueness of the index, the scalability of the protocol, etc... And
> this is one good reason why MIPTRANS builds on MIP6/NEMO as opposed to
> MIP4.
> 
> The MIPTRANS conceptual data could be stored in an IPv6 table and an
> IPv4 table in a given implementation, but both tables MUST be indexed
> with the IPv6 Home Address. 

YES. this is the point I was trying to make. thank
you.

In my mind that makes it a single conceptual
> binding cache, but that's secondary.
> 
> The key is that the IPv4 Home Address in the draft is not a Home Address
> stricto sensu, as understood in MIP4, MIP6 and NEMO. It is just an IPv4
> address that the Home Agent can bind to that mobile node, just like it
> will bind a prefix to a Mobile Router. Note that MRs do not need to bind
> an IPv4 Home Address at all: all they need to bind is an IPv4 subnet.
> 
> So I'm fine with storing the IPv4 HoA in the conceptual BCE, together
> with the prefixes in the BUs as Hesham suggests. I'd wish some text to
> make sure that it is very clear that the IPv4 HoA does not inherit the
> index characteristics from the MIPx/NEMO RFCs. 

I can live with this.

> I'm afraid that part of this discussion comes from the name of the
> option, IPv4 home address option. Consider this, when the 'p' bit is
> set, this is the equivalent of the Mobile Network Prefix Option in NEMO.
> 
> 
> Again: MIPTRANS IPv4 home address option IS_SAME_AS RFC3963 Mobile
> Network Prefix Option. 
> 
> Also, if you go back to RFC 3775, there is a Home Address Option, the
> destination option that's used to swap woth the source address in the
> packet. And now:
> 
> Again: MIPTRANS IPv4 home address option IS_ALIEN_FROM RFC3775 Home
> Address Option
> 
> Also, the IPv4 address does not have to be from a 'Home'. There might
> not be an IPv4 Home. For instance, the HA could be a NAT and give a same
> private address to all MNs. You can not do that with MIP4 because the
> IPv4 HoA is the index, but MIPTRANS enables this.
> 
> Finally, the word "address" is used in the name of the option though for
> NEMO it will be a prefix (or a subnet I do not mind the wording).
> 
> At the end of the day, I figure that the name of the option is
> ill-chosen, and I see that as the source of the miscommunication around
> issue 66.
> 
>  
> I'd say:
> 
> 1) About the following text the end of page 18 of version 02
> " - If the binding update is accepted for the IPv4 home address, the
>      home agent MUST create a binding cache entry for the IPv4 home
>      address/prefix. If a single IPv4 home address were requested, it
>      MAY be stored in the IPv4-mapped IPv6 address format. The home
>      agent MUST include an IPv4 acknowledgement option in the mobility
>      header containing the binding acknowledgement.
> "
> 
> I agree with Vijay that the text should be improved to avoid confusion.
> I agree with Hesham that we can keep the conceptual data. I want to make
> sure that the IPv4 "HoA" is not confused to be an index to the BCE being
> created in that text.

agree with the above, but I still think we don't
have to talk about a conceptual data structure at
all for the IPv4 "HoA" similar to how we don't
talk about a conceptual data structure for the
IPv6/IPv4 NEMO prefix.

> 2) About the IPv4 home address option
> Can I suggest to rename it "IPv4 addressing option". That removes the
> similarity in name with the MIP6 option, and opens to the fact that it
> can carry a prefix.

agree.

Vijay

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



From mip6-bounces@ietf.org Wed Oct 25 14:00:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcmz0-0004pq-NX; Wed, 25 Oct 2006 13:56:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcmyw-0004kD-9W
	for mip6@ietf.org; Wed, 25 Oct 2006 13:56:02 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcmql-0001z0-69
	for mip6@ietf.org; Wed, 25 Oct 2006 13:47:36 -0400
Received: by ug-out-1314.google.com with SMTP id 72so138470ugd
	for <mip6@ietf.org>; Wed, 25 Oct 2006 10:47:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=nyIPmtW3zynlxkjYw6mt0YkInh/CZpbYcjvTIrtutXVWBA8ZXjc0pAA4gbeVdOTLtPnk/5bOJGMk27U6C/IS2vIaR0iAfV7ucxthp3wbYE9UC0e4JpG0iOHucD9FK/uV9iqe9fadqA+Z2qEcjjWxmMsqOzlJnTssef+2jKz8N4M=
Received: by 10.78.201.8 with SMTP id y8mr167471huf;
	Wed, 25 Oct 2006 10:47:30 -0700 (PDT)
Received: from ?203.178.143.168? ( [203.178.143.168])
	by mx.google.com with ESMTP id 40sm1349385hue.2006.10.25.10.47.26;
	Wed, 25 Oct 2006 10:47:29 -0700 (PDT)
In-Reply-To: <453F9EBC.4020406@azairenet.com>
References: <5D25AEFB114D034FBDC8B156FCA78E030135A5E1@SEHAN021MB.tcad.telia.se>
	<453F9EBC.4020406@azairenet.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DBA648CF-3C77-4B6B-9600-0DC05DEFCD6F@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] about HA switch message
Date: Thu, 26 Oct 2006 02:47:19 +0900
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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

BU is the best choice for the current purpose of HA switch.
HA can confirm correct tunnel setup and IPsec by receiving a BU.

regards,
ryuji

On 2006/10/26, at 2:28, Vijay Devarapalli wrote:

> Hi Jouni,
>
> jouni.korhonen@teliasonera.com wrote:
>> Hi,
>> After reading this draft again I got few questions. Maybe these
>> have been asked earlier already, in which case I have missed
>> them.
>> I guess the home agent switch message could also be used for general
>> signaling from HA to MN? I.e. setting # addresses to 1 and giving the
>> address of the current HA as the alternative HA address. Then using
>> Mobility Options to carry whatever an operator wants to sporadically
>> send from the HA to the MN. This would also have some side effects
>> on the retransmission logic I guess.
>
> the only use-case we could nail down was the HA
> Switch. thats why we decided to standardize it.
> if there are more cases, I guess we could
> standardize a generic notification message.
>
> Vijay
>
>> Also the security considerations state that the message must be
>> protected using the IPSec SAs between the HA and the MN. What
>> about RFC4285 auth option?
>> Cheers,
>> 	Jouni
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Oct 25 14:03:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcmz1-0004pz-Ec; Wed, 25 Oct 2006 13:56:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcmyx-0004n2-7k
	for mip6@ietf.org; Wed, 25 Oct 2006 13:56:03 -0400
Received: from atlrel8.hp.com ([156.153.255.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcmpv-0001wT-CJ
	for mip6@ietf.org; Wed, 25 Oct 2006 13:46:44 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel8.hp.com (Postfix) with ESMTP id F22AF36E76;
	Wed, 25 Oct 2006 13:46:47 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 04A69108906;
	Wed, 25 Oct 2006 17:46:41 +0000 (UTC)
Message-ID: <453FA301.5080107@hp.com>
Date: Wed, 25 Oct 2006 13:46:41 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Fritsche Wolfgang <Fritsche@iabg.de>
Subject: Re: AW: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE81F@exchange03.iabg.de>
In-Reply-To: <69A5E767EC979846826F566C7932A3F2046DE81F@exchange03.iabg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Fritsche Wolfgang wrote:
> I read this in draft-ietf-mip6-ha-switch-01.txt and also partly in draft-ietf-mip6-hareliability-00.txt, however, chapter 8.3 of draft-ietf-mip6-hareliability-00.txt also says
> 
>    "However, in this specification, the binding cache
>    information is already synchronized among the redundant home agent
>    set, the mobile node can skip this binding re-registration to the new
>    active home agent.  In this case, the mobile node only updates the
>    Home Agent address of all the binding update list, MIP6 tunnel end
>    points, etc."
> 
> This seems to indicate that sending a BU to the new active HA is left as optional to the MN, that is, in this case also the Ack for the HA Switch will be optional, right?

I think we're going to remove that text from the ha-reliability draft.

-Brian

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



From mip6-bounces@ietf.org Wed Oct 25 14:05:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcn7v-00019n-Jn; Wed, 25 Oct 2006 14:05:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcn7u-00017B-BH
	for mip6@ietf.org; Wed, 25 Oct 2006 14:05:18 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcn7t-0005DB-1z
	for mip6@ietf.org; Wed, 25 Oct 2006 14:05:18 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 11:05:16 -0700
Message-ID: <453FA75E.9060000@azairenet.com>
Date: Wed, 25 Oct 2006 11:05:18 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7EB20EA0938B4D42A2D82689365C9B7A2AC207@NAEX14.na.qualcomm.com>
	<BFC430B8-83B1-4C24-A912-5CA3F8F18605@gmail.com>
In-Reply-To: <BFC430B8-83B1-4C24-A912-5CA3F8F18605@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Oct 2006 18:05:16.0609 (UTC)
	FILETIME=[201F0310:01C6F860]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

RYUJI WAKIKAWA wrote:

> As Pascal said in the comments,  IPv4 HoA treatment is very similar to 
> MNP in the NEMO.
> You can simply say that a HA creates a forwarding for each IPv4 HoA as 
> RFC3963.
> If you really keep the conceptual data,
> you should remove all the paragraph saying like
> 
> "If the binding update is accepted for both IPv4 and IPv6 home
>    addresses, the home agent MUST create two separate binding cache
>    entries, one for each home address." (section 4.4)
> 
> This text strongly requests creating two binding cache entries to 
> implementations.
> 
> My suggestion is
> "The home agent MUST create a binding cache entry for IPv6 HoA and
>  MUST setup  a forwarding for the IPv4 HoA. The forwarding information
>  can be stored in anyway  (ex. binding cache entry). "

building on your text, how about the following?

   The home agent MUST create a binding cache entry for IPv6 HoA and
   MUST setup forwarding for the IPv4 HoA. The forwarding information
   for the IPv4 HoA can be in the form of a routing table entry or a
   separate binding cache entry.  But this information is tied to the
   binding cache entry for the IPv6 HoA and is removed when the
   binding cache entry expires.

Vijay

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



From mip6-bounces@ietf.org Wed Oct 25 14:07:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcn9v-0001b7-63; Wed, 25 Oct 2006 14:07:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcn9t-0001b1-Lo
	for mip6@ietf.org; Wed, 25 Oct 2006 14:07:21 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcn9s-0005jk-AW
	for mip6@ietf.org; Wed, 25 Oct 2006 14:07:21 -0400
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 11:07:18 -0700
Message-ID: <453FA7D8.7060206@azairenet.com>
Date: Wed, 25 Oct 2006 11:07:20 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Fritsche Wolfgang <Fritsche@iabg.de>
Subject: Re: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE829@exchange03.iabg.de>
In-Reply-To: <69A5E767EC979846826F566C7932A3F2046DE829@exchange03.iabg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 25 Oct 2006 18:07:18.0984 (UTC)
	FILETIME=[690FF480:01C6F860]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Fritsche Wolfgang wrote:
> Vijay,
> 
> I think there are scenarios requiring an immediate HA Switch (e.g. HA failure) and scenarios allowing for some more time to stay with the current HA (e.g. upcoming maintenance). For the latter category one could allow established sessions to stay for a certain time with the current HA, and force new sessions to make use of the new HA. This would allow established connections to survive for a certain time after receiving the HA Switch, which could be long enough to have these established sessions ended anyway. Such a time period could be one of the mobility options carried by a HA Switch message. What do you think?

sounds good to me. we can add a mobility option to
say how much time (in seconds) the MN has before
it has to pick another HA.

Vijay

> 
> Wolfgang
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com] 
>> Gesendet: Mittwoch, 25. Oktober 2006 19:28
>> An: jouni.korhonen@teliasonera.com
>> Cc: mip6@ietf.org
>> Betreff: Re: [Mip6] about HA switch message
>>
>> Hi Jouni,
>>
>> jouni.korhonen@teliasonera.com wrote:
>>> Hi,
>>>
>>> After reading this draft again I got few questions. Maybe these have 
>>> been asked earlier already, in which case I have missed them.
>>>
>>> I guess the home agent switch message could also be used for general 
>>> signaling from HA to MN? I.e. setting # addresses to 1 and 
>> giving the 
>>> address of the current HA as the alternative HA address. Then using 
>>> Mobility Options to carry whatever an operator wants to sporadically 
>>> send from the HA to the MN. This would also have some side 
>> effects on 
>>> the retransmission logic I guess.
>> the only use-case we could nail down was the HA Switch. thats 
>> why we decided to standardize it.
>> if there are more cases, I guess we could standardize a 
>> generic notification message.
>>
>> Vijay
>>
>>> Also the security considerations state that the message must be 
>>> protected using the IPSec SAs between the HA and the MN. What about 
>>> RFC4285 auth option?
>>>
>>> Cheers,
>>> 	Jouni
>>>
>>> _______________________________________________
>>> Mip6 mailing list
>>> Mip6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mip6
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>


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



From mip6-bounces@ietf.org Wed Oct 25 15:03:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gco2J-0008Ur-O4; Wed, 25 Oct 2006 15:03:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gco2H-0008Tk-Lp
	for mip6@ietf.org; Wed, 25 Oct 2006 15:03:33 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gco2F-0007ww-Cu
	for mip6@ietf.org; Wed, 25 Oct 2006 15:03:33 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel6.hp.com (Postfix) with ESMTP id C32073402C;
	Wed, 25 Oct 2006 15:03:30 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp1.fc.hp.com (Postfix) with ESMTP id ED5E710642C;
	Wed, 25 Oct 2006 19:03:29 +0000 (UTC)
Message-ID: <453FB501.8010704@hp.com>
Date: Wed, 25 Oct 2006 15:03:29 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Fritsche Wolfgang <Fritsche@iabg.de>
Subject: Re: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE829@exchange03.iabg.de>
In-Reply-To: <69A5E767EC979846826F566C7932A3F2046DE829@exchange03.iabg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> I think there are scenarios requiring an immediate HA Switch (e.g. HA failure) and scenarios allowing for some more time to stay with the current HA (e.g. upcoming maintenance). For the latter category one could allow established sessions to stay for a certain time with the current HA, and force new sessions to make use of the new HA. This would allow established connections to survive for a certain time after receiving the HA Switch, which could be long enough to have these established sessions ended anyway. Such a time period could be one of the mobility options carried by a HA Switch message. What do you think?

There was also a suggestion to put a Lifetime field in the Switch 
message, replacing the reserved field.  Would that be an option?  I 
didn't make that change in the -01 version.

-Brian

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



From mip6-bounces@ietf.org Wed Oct 25 15:17:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcoFz-0007BF-Hp; Wed, 25 Oct 2006 15:17:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcoFy-0007B9-K2
	for mip6@ietf.org; Wed, 25 Oct 2006 15:17:42 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcoFx-0002CV-4f
	for mip6@ietf.org; Wed, 25 Oct 2006 15:17:42 -0400
Message-ID: <160401c6f86a$920dfd50$5f6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>
References: <7892795E1A87F04CADFCCF41FADD00FC02E34086@xmb-ams-337.emea.cisco.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Wed, 25 Oct 2006 12:19:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
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 agree with Pascal.

            jak

----- Original Message ----- 
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>; "Soliman, Hesham" 
<hsoliman@qualcomm.com>
Cc: <mip6@ietf.org>
Sent: Wednesday, October 25, 2006 6:13 AM
Subject: RE: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA




>-----Original Message-----
>From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>Sent: Wednesday, October 25, 2006 1:15 AM
>To: Soliman, Hesham
>Cc: mip6@ietf.org
>Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
>
>Hesham,
>
>I don't believe we can converge on this issue. this
>issue has been open for more than a year and we have
>discussed it too many times. I am tired.
>
[Pascal] OK; let me jump in then.

I agree with both :) maybe it's a matter of wording.

I do not mind having a conceptual data structure. As Hesham says, we
have that in other drafts. It helps implementers remember the core data
they have to store. The conceptual data can be stored as a single
control block in memory, or as multiple tables in a distributed
database, alone or mixed with other data. That's why it's only
conceptual.

What is NOT conceptual (and that's when I agree with Vijay) is the index
to the data. The protocol must ensure that the index to the conceptual
data is unique. And that unique index in MIP6, NEMO and MIPTRANS is the
IPv6 Home Address. Using an IPv6 address guarantees the global
uniqueness of the index, the scalability of the protocol, etc... And
this is one good reason why MIPTRANS builds on MIP6/NEMO as opposed to
MIP4.

The MIPTRANS conceptual data could be stored in an IPv6 table and an
IPv4 table in a given implementation, but both tables MUST be indexed
with the IPv6 Home Address. In my mind that makes it a single conceptual
binding cache, but that's secondary.

The key is that the IPv4 Home Address in the draft is not a Home Address
stricto sensu, as understood in MIP4, MIP6 and NEMO. It is just an IPv4
address that the Home Agent can bind to that mobile node, just like it
will bind a prefix to a Mobile Router. Note that MRs do not need to bind
an IPv4 Home Address at all: all they need to bind is an IPv4 subnet.

So I'm fine with storing the IPv4 HoA in the conceptual BCE, together
with the prefixes in the BUs as Hesham suggests. I'd wish some text to
make sure that it is very clear that the IPv4 HoA does not inherit the
index characteristics from the MIPx/NEMO RFCs.

I'm afraid that part of this discussion comes from the name of the
option, IPv4 home address option. Consider this, when the 'p' bit is
set, this is the equivalent of the Mobile Network Prefix Option in NEMO.


Again: MIPTRANS IPv4 home address option IS_SAME_AS RFC3963 Mobile
Network Prefix Option.

Also, if you go back to RFC 3775, there is a Home Address Option, the
destination option that's used to swap woth the source address in the
packet. And now:

Again: MIPTRANS IPv4 home address option IS_ALIEN_FROM RFC3775 Home
Address Option

Also, the IPv4 address does not have to be from a 'Home'. There might
not be an IPv4 Home. For instance, the HA could be a NAT and give a same
private address to all MNs. You can not do that with MIP4 because the
IPv4 HoA is the index, but MIPTRANS enables this.

Finally, the word "address" is used in the name of the option though for
NEMO it will be a prefix (or a subnet I do not mind the wording).

At the end of the day, I figure that the name of the option is
ill-chosen, and I see that as the source of the miscommunication around
issue 66.


I'd say:

1) About the following text the end of page 18 of version 02
" - If the binding update is accepted for the IPv4 home address, the
     home agent MUST create a binding cache entry for the IPv4 home
     address/prefix. If a single IPv4 home address were requested, it
     MAY be stored in the IPv4-mapped IPv6 address format. The home
     agent MUST include an IPv4 acknowledgement option in the mobility
     header containing the binding acknowledgement.
"

I agree with Vijay that the text should be improved to avoid confusion.
I agree with Hesham that we can keep the conceptual data. I want to make
sure that the IPv4 "HoA" is not confused to be an index to the BCE being
created in that text.

2) About the IPv4 home address option
Can I suggest to rename it "IPv4 addressing option". That removes the
similarity in name with the MIP6 option, and opens to the fact that it
can carry a prefix.

What do you think?


Pascal

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


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



From mip6-bounces@ietf.org Wed Oct 25 15:37:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcoYt-0003Pg-LH; Wed, 25 Oct 2006 15:37:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcoYs-0003PS-SS
	for mip6@ietf.org; Wed, 25 Oct 2006 15:37:14 -0400
Received: from sehan001bb.han.telia.se ([131.115.18.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcoYq-0005SA-LS
	for mip6@ietf.org; Wed, 25 Oct 2006 15:37:14 -0400
Received: from SEHAN021MB.tcad.telia.se ([131.115.18.160]) by
	sehan001bb.han.telia.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Oct 2006 21:36:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] about HA switch message
Date: Wed, 25 Oct 2006 21:36:58 +0200
Message-ID: <5D25AEFB114D034FBDC8B156FCA78E03014DF6A6@SEHAN021MB.tcad.telia.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] about HA switch message
Thread-Index: Acb4Tasn3638WZnuQhuibg5EpPxVzQAA5e0Q
From: <jouni.korhonen@teliasonera.com>
To: <brian.haley@hp.com>
X-OriginalArrivalTime: 25 Oct 2006 19:36:59.0172 (UTC)
	FILETIME=[EFE77E40:01C6F86C]
X-Spam-Score: 0.2 (/)
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

Hi Brian,=20

> Hi Jouni,
>=20
> Thanks for reading the draft.
>=20
> > I guess the home agent switch message could also be used=20
> for general=20
> > signaling from HA to MN? I.e. setting # addresses to 1 and=20
> giving the=20
> > address of the current HA as the alternative HA address. Then using=20
> > Mobility Options to carry whatever an operator wants to=20
> sporadically=20
> > send from the HA to the MN. This would also have some side=20
> effects on=20
> > the retransmission logic I guess.
>=20
> I guess it could do that, although it was not the intention,=20
> also the draft doesn't define any valid options.  I have an=20

The next question is whether the HA switch message as defined now
should prohibit sending current HA as the only HA address? If not
I would guess it leaves a door open for unintended use of the HA
switch message.

> expired draft that is probably in need of an update -=20
> draft-haley-mip6-mh-signaling-01 that proposes that solution.
>
> > Also the security considerations state that the message must be=20
> > protected using the IPSec SAs between the HA and the MN. What about=20
> > RFC4285 auth option?
>=20
> Yes, I guess RFC 4285 auth option should be supported, I can=20
> add that in the next revision.

Good.

> Thanks,
>=20
> -Brian

Cheers,
	Jouni

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



From mip6-bounces@ietf.org Wed Oct 25 15:50:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcolp-00049W-Us; Wed, 25 Oct 2006 15:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcolH-0003nE-Bn; Wed, 25 Oct 2006 15:50:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GcolF-0007oN-SQ; Wed, 25 Oct 2006 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id CF82926E3A;
	Wed, 25 Oct 2006 19:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GcolF-0004nF-Nd; Wed, 25 Oct 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GcolF-0004nF-Nd@stiedprstage1.ietf.org>
Date: Wed, 25 Oct 2006 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-ikev2-ipsec-07.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 Operation with IKEv2 and the revised IPsec Architecture
	Author(s)	: F. Dupont, V. Devarapalli
	Filename	: draft-ietf-mip6-ikev2-ipsec-07.txt
	Pages		: 25
	Date		: 2006-10-25
	
This document describes Mobile IPv6 operation with the revised IPsec
   architecture and IKEv2.

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

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

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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-25103551.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-ikev2-ipsec-07.txt

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

Content-Type: text/plain
Content-ID: <2006-10-25103551.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Wed Oct 25 16:30:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcpOB-0001ee-SB; Wed, 25 Oct 2006 16:30:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcpO9-0001dO-OZ
	for mip6@ietf.org; Wed, 25 Oct 2006 16:30:13 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcpNj-0001AL-N3
	for mip6@ietf.org; Wed, 25 Oct 2006 16:30:13 -0400
Received: from smtp1.fc.hp.com (smtp-test.fc.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id 2D167392BB;
	Wed, 25 Oct 2006 15:54:23 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 8BCD3107DA7;
	Wed, 25 Oct 2006 19:54:22 +0000 (UTC)
Message-ID: <453FC0EC.3030706@hp.com>
Date: Wed, 25 Oct 2006 15:54:20 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: jouni.korhonen@teliasonera.com
Subject: Re: [Mip6] about HA switch message
References: <5D25AEFB114D034FBDC8B156FCA78E03014DF6A6@SEHAN021MB.tcad.telia.se>
In-Reply-To: <5D25AEFB114D034FBDC8B156FCA78E03014DF6A6@SEHAN021MB.tcad.telia.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jouni,

>>> I guess the home agent switch message could also be used 
>> for general 
>>> signaling from HA to MN? I.e. setting # addresses to 1 and 
>> giving the 
>>> address of the current HA as the alternative HA address. Then using 
>>> Mobility Options to carry whatever an operator wants to 
>> sporadically 
>>> send from the HA to the MN. This would also have some side 
>> effects on 
>>> the retransmission logic I guess.
>> I guess it could do that, although it was not the intention, 
>> also the draft doesn't define any valid options.  I have an 
> 
> The next question is whether the HA switch message as defined now
> should prohibit sending current HA as the only HA address? If not
> I would guess it leaves a door open for unintended use of the HA
> switch message.

That would imply a broken HA, right?  I'm inclined to not add special 
case text for this since responding with a binding update doesn't hurt, 
it just causes some unnecessary network traffic.  At best I could put a 
sentence into Section 4.1 (HA sending), but it already says "alternate 
home agent addresses".

Is there some specific unintended use you were thinking of?

-Brian

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



From mip6-bounces@ietf.org Wed Oct 25 16:45:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcpcO-00085u-0k; Wed, 25 Oct 2006 16:44:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcpcN-00085i-Ad
	for mip6@ietf.org; Wed, 25 Oct 2006 16:44:55 -0400
Received: from mail2.iabg.de ([62.245.167.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcpcF-0005BZ-FY
	for mip6@ietf.org; Wed, 25 Oct 2006 16:44:55 -0400
Received: from mail2.iabg.de (localhost [127.0.0.1])
	by localhost.iabg.de (Mailserver2 IABG) with ESMTP id E4BC911FC;
	Wed, 25 Oct 2006 22:44:39 +0200 (CEST)
Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37])
	by mail2.iabg.de (Mailserver2 IABG) with ESMTP id CF82811D1;
	Wed, 25 Oct 2006 22:44:39 +0200 (CEST)
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: AW: AW: [Mip6] about HA switch message
Date: Wed, 25 Oct 2006 22:44:19 +0200
Message-ID: <69A5E767EC979846826F566C7932A3F2046DE840@exchange03.iabg.de>
In-Reply-To: <453FB501.8010704@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [Mip6] about HA switch message
Thread-Index: Acb4aEPJa7wEO3qZTOyM3RvCgGjp1AADXgPg
From: "Fritsche Wolfgang" <Fritsche@iabg.de>
To: "Brian Haley" <brian.haley@hp.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

>-----Urspr=FCngliche Nachricht-----
>Von: Brian Haley [mailto:brian.haley@hp.com]=20
>Gesendet: Mittwoch, 25. Oktober 2006 21:03
>An: Fritsche Wolfgang
>Cc: Vijay Devarapalli; jouni.korhonen@teliasonera.com; mip6@ietf.org
>Betreff: Re: AW: [Mip6] about HA switch message
>
>> I think there are scenarios requiring an immediate HA Switch=20
>(e.g. HA failure) and scenarios allowing for some more time to=20
>stay with the current HA (e.g. upcoming maintenance). For the=20
>latter category one could allow established sessions to stay=20
>for a certain time with the current HA, and force new sessions=20
>to make use of the new HA. This would allow established=20
>connections to survive for a certain time after receiving the=20
>HA Switch, which could be long enough to have these=20
>established sessions ended anyway. Such a time period could be=20
>one of the mobility options carried by a HA Switch message.=20
>What do you think?
>
>There was also a suggestion to put a Lifetime field in the=20
>Switch message, replacing the reserved field.  Would that be=20
>an option?  I didn't make that change in the -01 version.
>
>-Brian
>

If this lifetime will indicate how long the MN is allowed to continue to =
use the HA, which sent the HA switch message, for already established =
sessions, it would be an option.

Cheers,

Wolfgang

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



From mip6-bounces@ietf.org Wed Oct 25 20:32:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gct9l-0002OL-2w; Wed, 25 Oct 2006 20:31:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gct9k-0002OB-Db
	for mip6@ietf.org; Wed, 25 Oct 2006 20:31:36 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gct9j-0004bd-3F
	for mip6@ietf.org; Wed, 25 Oct 2006 20:31:36 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9Q0VUtX000354
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 25 Oct 2006 17:31:30 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9Q0VQ1G000580; Wed, 25 Oct 2006 17:31:29 -0700 (PDT)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Oct 2006 17:31:27 -0700
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Oct 2006 17:31:27 -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] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Wed, 25 Oct 2006 17:31:21 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A2AC2CC@NAEX14.na.qualcomm.com>
In-Reply-To: <453FA75E.9060000@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb4YCiOGQctgAJBQauCfBoMWcDXwQANcB8A
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"RYUJI WAKIKAWA" <ryuji.wakikawa@gmail.com>
X-OriginalArrivalTime: 26 Oct 2006 00:31:27.0524 (UTC)
	FILETIME=[13100E40:01C6F896]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@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


 > building on your text, how about the following?
 >=20
 >    The home agent MUST create a binding cache entry for IPv6 HoA and
 >    MUST setup forwarding for the IPv4 HoA. The forwarding information
 >    for the IPv4 HoA can be in the form of a routing table entry or a
 >    separate binding cache entry.  But this information is tied to the
 >    binding cache entry for the IPv6 HoA and is removed when the
 >    binding cache entry expires.
 >=20

=3D> This text is perfectly fine with me, anyone has a problem with =
this?
If not, then it's in! No more please :)

Hesham

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



From mip6-bounces@ietf.org Wed Oct 25 23:56:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GcwLJ-0007zd-7A; Wed, 25 Oct 2006 23:55:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GcwLH-0007zY-Oi
	for mip6@ietf.org; Wed, 25 Oct 2006 23:55:43 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcwLC-0002oS-Fe
	for mip6@ietf.org; Wed, 25 Oct 2006 23:55:43 -0400
Received: by ug-out-1314.google.com with SMTP id 72so242095ugd
	for <mip6@ietf.org>; Wed, 25 Oct 2006 20:55:37 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=C4PSQ1V9sLE/1WfDUPmsQhFIlSwr0aIeP/+/ibCxZwXdwOT9D9wYLHHOZB7MhUEpKIT8JaLUo6in0mXyV2ncDwfS/uR0RvbLZinCp/ta8RgFWQjvvautwJwhY3FUzlCm8skEq/2J45uLj4sUVa5uhzwOsnHNAg1j5Niyg+uflFA=
Received: by 10.78.201.8 with SMTP id y8mr1038174huf;
	Wed, 25 Oct 2006 20:55:37 -0700 (PDT)
Received: from ?203.178.143.168? ( [203.178.143.168])
	by mx.google.com with ESMTP id 20sm1468818huf.2006.10.25.20.55.33;
	Wed, 25 Oct 2006 20:55:36 -0700 (PDT)
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A2AC2CC@NAEX14.na.qualcomm.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A2AC2CC@NAEX14.na.qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EC027893-A676-4E2C-8DDD-F20623BB0D2A@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Thu, 26 Oct 2006 12:55:26 +0900
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Hesham

Good to have consensus :-)

BTW, shall I open the DT ML archive to public?

regards,
ryuji

On 2006/10/26, at 9:31, Soliman, Hesham wrote:

>
>> building on your text, how about the following?
>>
>>    The home agent MUST create a binding cache entry for IPv6 HoA and
>>    MUST setup forwarding for the IPv4 HoA. The forwarding information
>>    for the IPv4 HoA can be in the form of a routing table entry or a
>>    separate binding cache entry.  But this information is tied to the
>>    binding cache entry for the IPv6 HoA and is removed when the
>>    binding cache entry expires.
>>
>
> => This text is perfectly fine with me, anyone has a problem with  
> this?
> If not, then it's in! No more please :)
>
> Hesham


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



From mip6-bounces@ietf.org Thu Oct 26 02:50:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcz43-0000FA-H9; Thu, 26 Oct 2006 02:50:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcz3y-0000Ax-IJ; Thu, 26 Oct 2006 02:50:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gcz3y-0002GB-9U; Thu, 26 Oct 2006 02:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 425EE26E3B;
	Thu, 26 Oct 2006 06:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gcz3y-00022M-2Z; Thu, 26 Oct 2006 02:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gcz3y-00022M-2Z@stiedprstage1.ietf.org>
Date: Thu, 26 Oct 2006 02:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-location-privacy-ps-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		: IP Address Location Privacy and Mobile IPv6:  Problem Statement
	Author(s)	: R. Koodli
	Filename	: draft-ietf-mip6-location-privacy-ps-04.txt
	Pages		: 8
	Date		: 2006-10-25
	
In this document, we discuss Location Privacy as applicable to
    Mobile IPv6.  We document the concerns arising from revealing Home
    Address to an on-looker and from disclosing Care of Address to a
    correspondent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-location-privacy-ps-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-location-privacy-ps-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-location-privacy-ps-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: <2006-10-25181157.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-location-privacy-ps-04.txt

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

Content-Type: text/plain
Content-ID: <2006-10-25181157.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Thu Oct 26 02:51:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcz4u-0001HO-9E; Thu, 26 Oct 2006 02:51:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gcz4T-0000o6-T9; Thu, 26 Oct 2006 02:50:33 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gcz4T-0002NM-R4; Thu, 26 Oct 2006 02:50:33 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Gcz4S-0008JU-H1; Thu, 26 Oct 2006 02:50:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6ED352AD11;
	Thu, 26 Oct 2006 06:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gcz3y-00022e-6B; Thu, 26 Oct 2006 02:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gcz3y-00022e-6B@stiedprstage1.ietf.org>
Date: Thu, 26 Oct 2006 02:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-radius-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		: RADIUS Mobile IPv6 Support
	Author(s)	: K. Chowdhury, et al.
	Filename	: draft-ietf-mip6-radius-01.txt
	Pages		: 31
	Date		: 2006-10-25
	
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-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-radius-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-radius-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-25183548.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-10-25183548.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mip6-bounces@ietf.org Thu Oct 26 09:20:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gd599-0001EO-0L; Thu, 26 Oct 2006 09:19:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gd598-0001E7-AM; Thu, 26 Oct 2006 09:19:46 -0400
Received: from [193.234.218.130] (helo=p130.piuha.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gd58z-0007KG-Um; Thu, 26 Oct 2006 09:19:46 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 36AE1898C5;
	Thu, 26 Oct 2006 16:18:45 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id EB3A7898C4;
	Thu, 26 Oct 2006 16:18:44 +0300 (EEST)
Message-ID: <4540B5B5.9040409@piuha.net>
Date: Thu, 26 Oct 2006 16:18:45 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Hannes Tschofenig <HannesTschofenig@web.de>
References: <451B7EC0.70801@gmx.net> <4540ACC1.5010707@web.de>
In-Reply-To: <4540ACC1.5010707@web.de>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: gdommety@cisco.com, mip6@ietf.org, dime@ietf.org, basavaraj.patil@nokia.com
Subject: [Mip6] Re: Important: Impact of RFC 4285 for Diameter MIP6
 Bootstrapping Work
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 you should do the work based on the WG draft.
(But I don't think anyone minds if the solution happens
to support or be easily adoptable for RFC 4285 too. But
don't go out of your way to achieve that.)

--Jari


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



From mip6-bounces@ietf.org Thu Oct 26 11:24:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gd75K-0001Ac-1q; Thu, 26 Oct 2006 11:23:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd75J-0001A9-D6
	for mip6@ietf.org; Thu, 26 Oct 2006 11:23:57 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd75F-0007XU-3c
	for mip6@ietf.org; Thu, 26 Oct 2006 11:23:57 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel9.hp.com (Postfix) with ESMTP id 8362D345B6;
	Thu, 26 Oct 2006 11:23:52 -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 81AC9112D9B;
	Thu, 26 Oct 2006 15:23:51 +0000 (UTC)
Message-ID: <4540D306.8090600@hp.com>
Date: Thu, 26 Oct 2006 11:23:50 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Fritsche Wolfgang <Fritsche@iabg.de>
Subject: Re: AW: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE840@exchange03.iabg.de>
In-Reply-To: <69A5E767EC979846826F566C7932A3F2046DE840@exchange03.iabg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Fritsche Wolfgang wrote:
> If this lifetime will indicate how long the MN is allowed to continue to use the HA, which sent the HA switch message, for already established sessions, it would be an option.

This is what I'd put in a -02 draft:

Lifetime

A 16-bit unsigned integer indicating the number of seconds the home 
agent will continue to honor the home binding.  If set to zero, the 
mobile node MUST stop using its current home agent following the rules 
in Section 5.1.

Sound good?

-Brian

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



From mip6-bounces@ietf.org Thu Oct 26 12:30:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gd87k-000167-5T; Thu, 26 Oct 2006 12:30:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd87i-0000sP-2a
	for mip6@ietf.org; Thu, 26 Oct 2006 12:30:30 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd87e-0002gi-JM
	for mip6@ietf.org; Thu, 26 Oct 2006 12:30:30 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9QGUPu8006623 for <mip6@ietf.org>; Thu, 26 Oct 2006 19:30:25 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Oct 2006 19:30:25 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Oct 2006 11:30:22 -0500
Received: from [10.241.164.221] ([10.241.164.221]) by daebe101.NOE.Nokia.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Oct 2006 11:30:21 -0500
Message-ID: <4540E2AA.9080606@nokia.com>
Date: Thu, 26 Oct 2006 09:30:34 -0700
From: "Charles E. Perkins" <charles.perkins@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: ext Brian Haley <brian.haley@hp.com>
Subject: Re: AW: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE840@exchange03.iabg.de>
	<4540D306.8090600@hp.com>
In-Reply-To: <4540D306.8090600@hp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Oct 2006 16:30:21.0979 (UTC)
	FILETIME=[08452EB0:01C6F91C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hello folks,

Shouldn't the time unit for lifetimes be 4 seconds (instead of
one second), to be like RFC 3775?

Regards,
Charlie P.


ext Brian Haley wrote:
> Fritsche Wolfgang wrote:
>> If this lifetime will indicate how long the MN is allowed to continue 
>> to use the HA, which sent the HA switch message, for already 
>> established sessions, it would be an option.
>
> This is what I'd put in a -02 draft:
>
> Lifetime
>
> A 16-bit unsigned integer indicating the number of seconds the home 
> agent will continue to honor the home binding.  If set to zero, the 
> mobile node MUST stop using its current home agent following the rules 
> in Section 5.1.
>
> Sound good?
>
> -Brian
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


-- 
Please address return e-mail to charles.perkins@nokia.com


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



From mip6-bounces@ietf.org Thu Oct 26 13:31:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gd93m-0003OM-R1; Thu, 26 Oct 2006 13:30:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd93l-0003Lc-Fj
	for mip6@ietf.org; Thu, 26 Oct 2006 13:30:29 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd93h-0004GI-0N
	for mip6@ietf.org; Thu, 26 Oct 2006 13:30:29 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id 70A1B34562;
	Thu, 26 Oct 2006 13:30:24 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 8EB4110DCE0;
	Thu, 26 Oct 2006 17:30:23 +0000 (UTC)
Message-ID: <4540F0AE.9020400@hp.com>
Date: Thu, 26 Oct 2006 13:30:22 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@nokia.com>
Subject: Re: AW: AW: [Mip6] about HA switch message
References: <69A5E767EC979846826F566C7932A3F2046DE840@exchange03.iabg.de>
	<4540D306.8090600@hp.com> <4540E2AA.9080606@nokia.com>
In-Reply-To: <4540E2AA.9080606@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: 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

Charles E. Perkins wrote:
> Shouldn't the time unit for lifetimes be 4 seconds (instead of
> one second), to be like RFC 3775?

You're right Charlie, thanks.

A 16-bit unsigned integer indicating the number of time units remaining 
before the mobile node MUST stop using its current home agent and choose 
another home agent, following the rules in Section 5.1.  A value of zero 
indicates that the mobile node MUST do this immediately.  One time unit 
is 4 seconds.

There's a bunch of other edits to make this happen, they'll all be in -02.

-Brian

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



From mip6-bounces@ietf.org Thu Oct 26 14:10:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gd9gL-0005p9-8G; Thu, 26 Oct 2006 14:10:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd9gI-0005hQ-U1
	for mip6@ietf.org; Thu, 26 Oct 2006 14:10:18 -0400
Received: from mail2.iabg.de ([62.245.167.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd9WC-0000RI-Ql
	for mip6@ietf.org; Thu, 26 Oct 2006 13:59:56 -0400
Received: from mail2.iabg.de (localhost [127.0.0.1])
	by localhost.iabg.de (Mailserver2 IABG) with ESMTP id A18ABF3A;
	Thu, 26 Oct 2006 19:59:45 +0200 (CEST)
Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37])
	by mail2.iabg.de (Mailserver2 IABG) with ESMTP id 89D8EF0D;
	Thu, 26 Oct 2006 19:59:45 +0200 (CEST)
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: AW: AW: AW: [Mip6] about HA switch message
Date: Thu, 26 Oct 2006 19:59:48 +0200
Message-ID: <69A5E767EC979846826F566C7932A3F2046DED68@exchange03.iabg.de>
In-Reply-To: <4540D306.8090600@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: AW: [Mip6] about HA switch message
Thread-Index: Acb5Er94XyiosTC/SCSKkWehhk+vDAAFZ5jQ
From: "Fritsche Wolfgang" <Fritsche@iabg.de>
To: "Brian Haley" <brian.haley@hp.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mip6@ietf.org, jouni.korhonen@teliasonera.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?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 reads fine for me, considering also the hint from Charlie =
concerning the time unit to be used.

Wolfgang=20

>-----Urspr=FCngliche Nachricht-----
>Von: Brian Haley [mailto:brian.haley@hp.com]=20
>Gesendet: Donnerstag, 26. Oktober 2006 17:24
>An: Fritsche Wolfgang
>Cc: Vijay Devarapalli; jouni.korhonen@teliasonera.com; mip6@ietf.org
>Betreff: Re: AW: AW: [Mip6] about HA switch message
>
>Fritsche Wolfgang wrote:
>> If this lifetime will indicate how long the MN is allowed to=20
>continue to use the HA, which sent the HA switch message, for=20
>already established sessions, it would be an option.
>
>This is what I'd put in a -02 draft:
>
>Lifetime
>
>A 16-bit unsigned integer indicating the number of seconds the=20
>home agent will continue to honor the home binding.  If set to=20
>zero, the mobile node MUST stop using its current home agent=20
>following the rules in Section 5.1.
>
>Sound good?
>
>-Brian
>

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



From mip6-bounces@ietf.org Thu Oct 26 15:44:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdB9A-0006eZ-8w; Thu, 26 Oct 2006 15:44:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GdB7a-000562-2h
	for mip6@ietf.org; Thu, 26 Oct 2006 15:42:34 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GdAwc-0005zn-Hq
	for mip6@ietf.org; Thu, 26 Oct 2006 15:31:15 -0400
Received: (qmail invoked by alias); 26 Oct 2006 19:31:13 -0000
Received: from p549851A5.dip.t-dialin.net (EHLO [192.168.2.33]) [84.152.81.165]
	by mail.gmx.net (mp039) with SMTP; 26 Oct 2006 21:31:13 +0200
X-Authenticated: #29516787
Message-ID: <45410CFF.1060903@gmx.net>
Date: Thu, 26 Oct 2006 21:31:11 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] Re: Important: Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
References: <451B7EC0.70801@gmx.net> <4540ACC1.5010707@web.de>
	<4540B5B5.9040409@piuha.net>
In-Reply-To: <4540B5B5.9040409@piuha.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: gdommety@cisco.com, mip6@ietf.org, dime@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

Hi Jari,

Jari Arkko wrote:
> I believe you should do the work based on the WG draft.
> (But I don't think anyone minds if the solution happens
> to support or be easily adoptable for RFC 4285 too. But
> don't go out of your way to achieve that.)

Thanks for the quick response.

Ciao
Hannes

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



From mip6-bounces@ietf.org Fri Oct 27 15:50:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdXiQ-0004Wp-Ek; Fri, 27 Oct 2006 15:50:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdXiL-0004VE-RD; Fri, 27 Oct 2006 15:50:01 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GdXiL-0000mf-Ja; Fri, 27 Oct 2006 15:50:01 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 8A8D0328FE;
	Fri, 27 Oct 2006 19:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GdXiL-00014W-EX; Fri, 27 Oct 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GdXiL-00014W-EX@stiedprstage1.ietf.org>
Date: Fri, 27 Oct 2006 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-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		: Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)
	Author(s)	: H. Soliman
	Filename	: draft-ietf-mip6-nemo-v4traversal-03.txt
	Pages		: 23
	Date		: 2006-10-27
	
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-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-nemo-v4traversal-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-nemo-v4traversal-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

Content-Type: text/plain
Content-ID: <2006-10-27125423.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-10-27125423.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 Oct 27 17:07:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdYul-0004CG-UX; Fri, 27 Oct 2006 17:06:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdYuf-0003Fa-5u; Fri, 27 Oct 2006 17:06:49 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GdYue-00031Q-CD; Fri, 27 Oct 2006 17:06:49 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 56C7926E61;
	Fri, 27 Oct 2006 21:06:48 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GdYue-0007AU-7y; Fri, 27 Oct 2006 17:06:48 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1GdYue-0007AU-7y@stiedprstage1.ietf.org>
Date: Fri, 27 Oct 2006 17:06:48 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org
Subject: [Mip6] Last Call: 'Mobile IPv6 Operation with IKEv2 and the revised
 IPsec Architecture' to Proposed Standard 
 (draft-ietf-mip6-ikev2-ipsec) 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@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

The IESG has received a request from the Mobility for IPv6 WG to 
consider the following document:

- 'Mobile IPv6 Operation with IKEv2 and the revised IPsec Architecture '
   <draft-ietf-mip6-ikev2-ipsec-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2006-11-10.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mip6-ikev2-ipsec-07.txt


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



From mip6-bounces@ietf.org Fri Oct 27 18:54:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdaaV-0008Ot-P3; Fri, 27 Oct 2006 18:54:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GdaaU-0008Ol-QQ; Fri, 27 Oct 2006 18:54:06 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GdaaT-00080Y-HN; Fri, 27 Oct 2006 18:54:06 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J7T001EMGSRCE@usaga01-in.huawei.com>; Fri,
	27 Oct 2006 15:50:51 -0700 (PDT)
Received: from N737011 (c-24-17-254-79.hsd1.mn.comcast.net [24.17.254.79])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J7T000J3GSM1C@usaga01-in.huawei.com>; Fri,
	27 Oct 2006 15:50:51 -0700 (PDT)
Date: Fri, 27 Oct 2006 15:53:49 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
In-reply-to: <2C9AA86BEC0D4B4ABBD55350FD743854736214@stntexch14>
To: "'Bunch, Rebecca'" <Rebecca.Bunch@neustar.biz>
Message-id: <005201c6fa1a$c4d95930$02fda8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acb4hswGHnlbJoC/TZaQbcRnvhXhogAfKbhQAEWaMuA=
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: ietf@ietf.org, 'Charles Clancy' <clancy@cs.umd.edu>, gwz@cisco.com,
	basavaraj.patil@nokia.com, mip6@ietf.org, hokeyp@opendiameter.org
Subject: [Mip6] hokeyp and MIP6 slots are colliding
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============0768931074=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0768931074==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_BPG4YiXuzfB7DtcoLqbyjw)"

This is a multi-part message in MIME format.

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

Any chance to move one of hokeyp and MIP6 to a different slot so they are
not colliding??

 

Thanks,

 

Madjid


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

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

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Any chance to move one of hokeyp and MIP6
to a different slot so they are not colliding??<o:p></o:p></span></font></p>

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

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

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

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

</div>

</body>

</html>

--Boundary_(ID_BPG4YiXuzfB7DtcoLqbyjw)--


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

--===============0768931074==--




From mip6-bounces@ietf.org Mon Oct 30 07:55:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GeWfC-0007yr-Q3; Mon, 30 Oct 2006 07:54:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GeWf2-0007yg-Qg
	for mip6@ietf.org; Mon, 30 Oct 2006 07:54:40 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeWf1-0000gw-CF
	for mip6@ietf.org; Mon, 30 Oct 2006 07:54:40 -0500
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 30 Oct 2006 13:54:40 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9UCsc49000913; Mon, 30 Oct 2006 13:54:38 +0100
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 k9UCscmd008214; 
	Mon, 30 Oct 2006 13:54:38 +0100 (MET)
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); 
	Mon, 30 Oct 2006 13:54:37 +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] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Mon, 30 Oct 2006 13:54:29 +0100
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC02EE76D8@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb4YCiOGQctgAJBQauCfBoMWcDXwQANcB8AAOJuS0A=
From: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"RYUJI WAKIKAWA" <ryuji.wakikawa@gmail.com>
X-OriginalArrivalTime: 30 Oct 2006 12:54:37.0829 (UTC)
	FILETIME=[8E9BA350:01C6FC22]
DKIM-Signature: a=rsa-sha1; q=dns; l=3218; t=1162212878; x=1163076878;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pthubert@cisco.com;
	z=From:=22Pascal=20Thubert=20\(pthubert\)=22=20<pthubert@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Re=3A=20[issue66]=20Setting=20up=20forwarding=20for=20I
	Pv4=20HoA;
	X=v=3Dcisco.com=3B=20h=3DVWFUP/3uPa5u69/UqSjYGErJGxA=3D;
	b=Ca2LZzbTjEYLQEvqDYISaKupsGjwQdtS5+TQoXEs2/Cii2dlIwfdpfTA2h5kss1HZ2xZgz8o
	T5VCmVJY5DSrKQGXRlr0LXerDSVOsUez7llUsUTY3rXiqw0e2r25EjEr;
Authentication-Results: ams-dkim-1; header.From=pthubert@cisco.com; dkim=pass (
	sig from cisco.com 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

Just to make sure on what the agreement is:

1) There are 2 paragraphs in the original text that we want to update

"
If the binding update is accepted for the IPv4 home address, the home
agent MUST create a binding cache entry for the IPv4 home
address/prefix. If a single IPv4 home address were requested, it MAY be
stored in the IPv4-mapped IPv6 address format. The home agent MUST
include an IPv4 acknowledgement option in the mobility header containing
the binding acknowledgement.

If the binding update is accepted for both IPv4 and IPv6 home addresses,
the home agent MUST create two separate binding cache entries, one for
each home address. The care-of address is the one included in the
binding update. If the care-of address is an IPv4- mapped IPv6 address,
the home agent MUST setup a tunnel to the IPv4 care-of address of the
mobile node.
"

2) When Vijay says IPv4 HoA, we mean IPv4 Home Address/prefix since that
is the language used in the draft and we might set up a network route as
opposed to a host route for IPv4.=20

So the text in 1) becomes:


   The home agent MUST create a binding cache entry for IPv6 HoA and
   MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
information
   for the IPv4 HoA/prefix can be in the form of a routing table entry
or a
   separate binding cache entry.  But this information is tied to the
   binding cache entry for the IPv6 HoA and is removed when the
   binding cache entry expires.



3) The text seems to force the forwarding information to be either BCE
or RIB. I'd suggest that these are only examples, since a NAT table
could be useful too.=20


So the text in 1) becomes:


   The home agent MUST create a binding cache entry for IPv6 HoA and
   MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
information
   for the IPv4 HoA/prefix can be for instance in the form of a routing
table entry or a
   separate binding cache entry.  In any case, this information is tied
to the
   binding cache entry for the IPv6 HoA and is removed when the
   binding cache entry expires.


IS that OK?


By the way, we seem to also have consensus on renaming the "IPv4 home
address option". I did not see opposition to "IPv4 addressing option".

Any alternate proposal?

Pascal

>-----Original Message-----
>From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>Sent: Thursday, October 26, 2006 2:31 AM
>To: Vijay Devarapalli; RYUJI WAKIKAWA
>Cc: Pascal Thubert (pthubert); mip6@ietf.org
>Subject: RE: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
>
>
> > building on your text, how about the following?
> >
> >    The home agent MUST create a binding cache entry for IPv6 HoA and
> >    MUST setup forwarding for the IPv4 HoA. The forwarding
information
> >    for the IPv4 HoA can be in the form of a routing table entry or a
> >    separate binding cache entry.  But this information is tied to
the
> >    binding cache entry for the IPv6 HoA and is removed when the
> >    binding cache entry expires.
> >
>
>=3D> This text is perfectly fine with me, anyone has a problem with =
this?
>If not, then it's in! No more please :)
>
>Hesham

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



From mip6-bounces@ietf.org Mon Oct 30 10:45:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GeZJq-0003HA-GJ; Mon, 30 Oct 2006 10:44:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GeZJp-0003H5-Sc
	for mip6@ietf.org; Mon, 30 Oct 2006 10:44:57 -0500
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeZJZ-0006mf-Ob
	for mip6@ietf.org; Mon, 30 Oct 2006 10:44:57 -0500
Received: from [10.1.210.16] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Oct 2006 07:44:40 -0800
Message-ID: <45461D17.9000807@azairenet.com>
Date: Mon, 30 Oct 2006 07:41:11 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7892795E1A87F04CADFCCF41FADD00FC02EE76D8@xmb-ams-337.emea.cisco.com>
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC02EE76D8@xmb-ams-337.emea.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Oct 2006 15:44:40.0920 (UTC)
	FILETIME=[501FC580:01C6FC3A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Pascal Thubert (pthubert) wrote:

>    The home agent MUST create a binding cache entry for IPv6 HoA and
>    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
> information
>    for the IPv4 HoA/prefix can be for instance in the form of a routing
> table entry or a
>    separate binding cache entry.  In any case, this information is tied
> to the
>    binding cache entry for the IPv6 HoA and is removed when the
>    binding cache entry expires.
> 
> 
> IS that OK?
> 
> 
> By the way, we seem to also have consensus on renaming the "IPv4 home
> address option". I did not see opposition to "IPv4 addressing option".

both are fine with me.

Vijay

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



From mip6-bounces@ietf.org Mon Oct 30 12:13:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GeagY-0006zk-9e; Mon, 30 Oct 2006 12:12:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GeagX-0006zV-Bh
	for mip6@ietf.org; Mon, 30 Oct 2006 12:12:29 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeagR-0005Eg-T7
	for mip6@ietf.org; Mon, 30 Oct 2006 12:12:29 -0500
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 30 Oct 2006 18:12:23 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k9UHCN6T005218; Mon, 30 Oct 2006 18:12:23 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9UHCMmd021968; 
	Mon, 30 Oct 2006 18:12:23 +0100 (MET)
Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Oct 2006 18:12:22 +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] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Date: Mon, 30 Oct 2006 18:12:16 +0100
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC02EE78E3@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] RE: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Thread-Index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAABwFpABQRjqkAIq1qwg
From: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 30 Oct 2006 17:12:22.0781 (UTC)
	FILETIME=[90700AD0:01C6FC46]
DKIM-Signature: a=rsa-sha1; q=dns; l=5116; t=1162228343; x=1163092343;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pthubert@cisco.com;
	z=From:=22Pascal=20Thubert=20\(pthubert\)=22=20<pthubert@cisco.com>
	|Subject:RE=3A=20[Mip6]=20RE=3A=20issue=2076=3A=20Alt=20CoA=20should=20not=20be=2
	0used=20when=20traversingIPv4=20NAT;
	X=v=3Dcisco.com=3B=20h=3D1aEDM0eo1nud30oW8S8AR1djsaI=3D;
	b=b4xD5G4msCJ3k8BBMrgMhFfKdiqyHGmA4AbNw/UA5WFgBHJOiIORZSPeeCMyZvC/Q8Wpwbp9
	0d7RRmSnHBcgpOZW+CJz/X+Y9KEj0ZvmqTJ2vS+JWRaVUGC2pFCc+RCO;
Authentication-Results: ams-dkim-1; header.From=pthubert@cisco.com; dkim=pass (
	sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Hesham:

I agree:

1) with relaxing the requirement in RFC 3775 to include an Alt CoA
option all the time.

2) that the MN should omit it, as opposed to the HA filtering it out.
The Alt CoA is the real address at which the MN is reachable, that is
what HAs implement today, that is what all people in the art understand.
I want to stay simple and keep it that way.  I'd hate to have rules like
"this is A but then if there is also that then this is B which is the
opposite of A", etc... we are not lawyers!=20

3) that we have to find an alternate way to endure that the MN is
reachable at the CoA, defined as the source of the packet when the HA
gets it.

I'd also agree that:

4) UDP is used all the time in IPv4 roaming situation, regardless on
whether NAT is detected or not. That's not really in the mail but since
you fixed the message format in the thread to add UDP, I take advantage
of the exchange to raise that point again.

I disagree:

5) to jump too quickly on the conclusion that the checksum is the way to
go. I understand that it has value in certain scenarios that you
mention. But it fails to guarantee that the MN is reachable at the CoA
in another common case that is NAT; and it does not protect against a
rogue DHCP server assigning you an IPv4 DoS'ed address, which could
easily happen in the IPv4 world.=20

So when you call for consensus, please leave open the solution to 3) so
we can see if there's a preferable alternative. I, for one, would favor
an approach like 2 BU flows in row, which would emulate a 3 way
handshake and guarantee the reachability of the MN in all cases.=20

Pascal




>-----Original Message-----
>From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>Sent: Thursday, October 19, 2006 6:19 PM
>To: mip6@ietf.org
>Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
traversingIPv4 NAT
>
>Folks,
>
>This issue was revived mainly due to Vijay points on the need for the
>checksum option when the alt-CoA is not used. Let me summarise the
>issues first then propose a way forward.
>
>Summary:
>--------
>
>The initial resolution for the issue suggested that we add a checksum
>option that includes a checksum on the src and dst addresses in the
IPv6
>header. This was suggested to be used when the alt-coa is not present
to
>maintain the integrity of the src address when ESP is used. I want to
>emphasise that this is only needed when ESP is used, not with AH.
>
>Now the point that Vijay raised is also quite valid: With NAT
traversal,
>the outer IPv4 header is vulnerable, yet it is needed because the HA
>responds to that address and sets up the UDP tunnel to the outer
>(natted) IPv4 src address in the packet containing the BU. There is no
>way we can secure that address, yet, it essentially acts as another
>binding, which if modified maliciously, would redirect the MN's packets
>to another IPv4 address. To be clear, here is the packet format:
>BU packet received by HA after passing through NAT:
>  IPv4 HDR (src=3Dnatted-v4, dst=3DHA-addr)
>       UDP
>         IPv6 HDR (src=3Dv4-mapped-v6, dst=3DHA-addr)
>          ESP
>          DST-OPT
>          MH (BU)
>
>The HA responds with a similar packet including the BA and forwards all
>future packets in the UDP tunnel, with the dst address in the IPv4
>header being the "natted-v4" address above.
>So essentially protecting the BU does not protect the MN from
>redirection attacks in this case because the IPv4 header is vulnerable.
>This is an inherent problem with NAT traversal. There is practically
>nothing we can do about it.
>
>So the remaining question is: Is it worth worrying about the integrity
>of the BU in this case? IMHO I think the answer is yes. Why? Two main
>reasons:
>
>1. There can be cases where the BU is sent to a local HA and the
>operator can guarantee that no NATs are in the path. In this case we
>would lose integrity for no reason, i.e. the BU becomes the weakest
>link. This is not unusual really because an operator may decide that it
>will only provide the HA function within its domain, which happens to
>not include NATs between the MN and the HA.
>
>2. We have precedence with MIPv4 and NAT traversal where the RREQ is
>still secure despite the UNSAF NAT traversal.
>
>Note that the answer to 1) above may be "Use AH", but I prefer to not
>force that on implementations that do not do it today (although I would
>personally prefer AH in general for the BU).
>
>For these reasons, and there may be more, I prefer to not take this big
>decision to lose the integrity for the BU.
>
>Way forward:
>------------
>
>This issue is now closed, we all agree on it, but there may be
>disagreement on the checksum part. So I suggest that I generate a new
>issue for this discussion. Until the new issue is resolved, I won't add
>the checksum option to the draft.
>
>Feel free to send comments.
>
>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 Mon Oct 30 17:24:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GefX8-0002cL-ML; Mon, 30 Oct 2006 17:23:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GefX7-0002cG-Ss
	for mip6@ietf.org; Mon, 30 Oct 2006 17:23:05 -0500
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GefX6-0003C8-9g
	for mip6@ietf.org; Mon, 30 Oct 2006 17:23:05 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9UMN1BX007503 for <mip6@ietf.org>; Tue, 31 Oct 2006 00:23:03 +0200
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 00:23:02 +0200
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Oct 2006 16:22:58 -0600
Received: from 172.19.244.134 ([172.19.244.134]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 30 Oct 2006 22:22:58 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 30 Oct 2006 16:25:10 -0600
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C16BD7E6.27730%basavaraj.patil@nokia.com>
Thread-Topic: Update to Internet-Draft and RFC Boilerplate 
Thread-Index: Acb8ckKSgWXevGhlEduBwwARJNUNiA==
In-Reply-To: <200610302208.k9UM8XE37495@magenta.juniper.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Oct 2006 22:22:58.0991 (UTC)
	FILETIME=[F47C03F0:01C6FC71]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061031002303-1A33ABB0-4AFFF06C/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Subject: [Mip6] FW: Update to Internet-Draft and RFC Boilerplate 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

FYI,

> ------- Forwarded Message
> 
> Date:    Thu, 26 Oct 2006 21:19:59 -0400
> From:    IETF Chair <chair@ietf.org>
> To:      IETF Announcement list <ietf-announce@ietf.org>
> cc:      
> Subject: Update to Internet-Draft and RFC Boilerplate
> 
> A small update to BCP 78 was recently approved by the IESG as
> RFC 4748, to update the boilerplate (i.e., standard legal text) in
> RFCs and Internet-Drafts to recognize the IETF Trust as a rights
> holder, instead of ISOC.
> 
> The actual boilerplate changes are given below this message.
> 
> Starting as soon as reasonably possible, all authors of Internet-Drafts
> are requested to use the new boilerplate. The RFC Editor will in any case
> be inserting it in all RFCs issued from 2006-11-01. (The rights held by
> ISOC in older RFCs will be administratively transferred to the IETF
> Trust.)
> 
> The public ID Nits checker already accepts I-Ds with old or new
> boilerplate.
> The Secretariat has started accepting I-Ds with old or new boilerplate
> 
> XML2RFC version 1.32 will generate the new boilerplate.
> Users of I-D templates are requested to update them appropriately.
> 
> http://www.ietf.org/ID-Checklist.html and
> http://www.ietf.org/ietf/1id-guidelines.html are being updated.
> 
> Starting December, the public ID Nits checker will issue warnings for
> old boilerplate.
> 
> Starting February 2007, the Secretariat will refuse
> the old boilerplate in Internet-Drafts.
> 
> We are sorry for the inconvenience, but this change cannot
> be avoided.
> 
>     IETF Chair
>     IETF Secretariat
>     TOOLS Team
> 
> - --------
> 
> Copyright Notice (required for all IETF Documents)
> 
>    (Normally placed at the end of the IETF Document.)
> 
> NOTE: by convention, the first line of the copyright statement
> is usually placed near the beginning of each document. This must
> also be updated.
> 
> OLD
>       "Copyright (C) The Internet Society (year).
> 
>       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.
> 
> NEW
>       "Copyright (C) The IETF Trust (year).
> 
>       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.
> 
> 
> Disclaimer (required in all IETF Documents)
> 
>    (Normally placed at the end of the IETF Document after the copyright
>    notice.)
> 
> 
> OLD
>       "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 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."
> 
> 
> NEW
>       "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."
> 
> Exceptions
> 
>       In MIB modules, PIB modules and similar material commonly
>       extracted from IETF Documents, except for material that is being
>       placed under IANA maintenance, the following abbreviated notice
>       shall be included in the body of the material that will be
>       extracted in lieu of the notices otherwise required by Section 5:
> 
> OLD
>          "Copyright (C) The Internet Society <year>.  This version of
>          this MIB module is part of RFC XXXX; see the RFC itself for
>          full legal notices."
> 
> NEW
>          "Copyright (C) The IETF Trust <year>.  This version of
>          this MIB module is part of RFC XXXX; see the RFC itself for
>          full legal notices."
> 
>       When the MIB or PIB module is the initial version of a module that
>       is to be maintained by the IANA, the following abbreviated notice
>       shall be included:
> 
> OLD
>          "Copyright (C) The Internet Society <year>.  The initial
>          version of this MIB module was published in RFC XXXX; for full
>          legal notices see the RFC itself.  Supplementary information
>          may be available at:
>          http://www.ietf.org/copyrights/ianamib.html."
> 
> NEW
>          "Copyright (C) The IETF Trust <year>.  The initial
>          version of this MIB module was published in RFC XXXX; for full
>          legal notices see the RFC itself.  Supplementary information
>          may be available at:
>          http://www.ietf.org/copyrights/ianamib.html."
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
> 
> ------- End of Forwarded Message


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



From mip6-bounces@ietf.org Mon Oct 30 18:20:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GegQP-000525-MC; Mon, 30 Oct 2006 18:20:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GegQO-0004yb-Gi; Mon, 30 Oct 2006 18:20:12 -0500
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GegQI-0003YD-Vr; Mon, 30 Oct 2006 18:20:12 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	k9UNJYoZ016346; Tue, 31 Oct 2006 01:19:59 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 01:19:36 +0200
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Oct 2006 17:19:34 -0600
Received: from 172.19.244.134 ([172.19.244.134]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 30 Oct 2006 23:19:33 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 30 Oct 2006 17:21:45 -0600
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Hannes Tschofenig <HannesTschofenig@web.de>,
	Gopal Dommety <gdommety@cisco.com>
Message-ID: <C16BE529.27755%basavaraj.patil@nokia.com>
Thread-Topic: Important: Impact of RFC 4285 for Diameter MIP6
	Bootstrapping Work
Thread-Index: Acb8eiomaK/bOGhtEduBwwARJNUNiA==
In-Reply-To: <4540ACC1.5010707@web.de>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Oct 2006 23:19:34.0151 (UTC)
	FILETIME=[DC285170:01C6FC79]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::061031012002-3B3FEBB0-78F953D8/0-0/0-0
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: mip6@ietf.org, dime@ietf.org
Subject: [Mip6] Re: Important: Impact of RFC 4285 for Diameter MIP6
 Bootstrapping Work
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hannes,

We will try and get some more input to the work in DIME w.r.t the
bootstrapping requirements.

The bootstrapping solution in MIP6 (until now) has been based on the
assumption that the security for signaling between the MN and HA is via
IPsec. We have not really considered RFC4285 in the bootstrapping work.
However there is a draft (by Vijay Devarapalli) that proposes a solution for
bootstrapping with RFC4285.

I would suggest that you focus on the WG I-D (
draft-ietf-mip6-aaa-ha-goals-03.txt)  but as Jari said if you can cover the
other case, i.e RFC4285 as well without extra effort that would be good.

-Raj


On 10/26/06 7:40 AM, "ext Hannes Tschofenig" <HannesTschofenig@web.de>
wrote:

> Hi Raj,
> Hi Gopal,
> 
> some time back I have posted the attached mail to the list soliciting
> guidance for the Diameter MIP6 bootstrapping work.
> Unfortunately, we haven't received a lot of feedback and guidance on
> this issue.
> 
> We are making progress with our work and we would like to know ahead of
> time whether we should develop a backend solution based on
> (a) 
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-aaa-ha-goals-03.txt, or
> (b) 
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-aaa-ha-goals-03.txt
> and http://www.ietf.org/rfc/rfc4285.txt.
> 
> Ciao
> Hannes
> 
> Hannes Tschofenig wrote:
>> Hi all,
>> 
>> in the DIME working group we are currently producing documents that
>> relate to the backend solution of the
>> 
>> * Integrated Scenario
>>   draft-ietf-mip6-bootstrapping-integrated-dhc-01
>> 
>> * Split Scenario
>>   draft-ietf-mip6-bootstrapping-split-02
>> 
>> Now, the question came up whether we have to consider RFC 4285
>> ('Authentication Protocol for Mobile IPv6') for our work as well.
>> 
>> Thoughts?
>> 
>> Ciao
>> Hannes
>> 
>> 
> 


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



From mip6-bounces@ietf.org Tue Oct 31 08:11:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GetOM-0004m7-IH; Tue, 31 Oct 2006 08:10:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GetOL-0004h2-Km
	for mip6@ietf.org; Tue, 31 Oct 2006 08:10:57 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GetOF-000270-Lz
	for mip6@ietf.org; Tue, 31 Oct 2006 08:10:57 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k9VDAnF2009213
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 31 Oct 2006 05:10:50 -0800
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.141.78])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k9VDAmDc004916; Tue, 31 Oct 2006 05:10:49 -0800 (PST)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 05:10:48 -0800
Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 05:10:48 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 31 Oct 2006 05:10:40 -0800
Message-ID: <2309978910A6A6478C2C7585692B0AF40151E4@NAEX16.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Thread-Index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAABwFpABQRjqkAIq1qwgACpqkBA=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 31 Oct 2006 13:10:48.0235 (UTC)
	FILETIME=[FB6D97B0:01C6FCED]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Cc: 
Subject: [Mip6] concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Pascal, all,=20

There's been a lot of emails on this issue so I think WG members are
fully informed now about what this issue involves. I will ask a simple
question and I'd like people to choose one of the options below. To
avoid any confusion I'm keeping the question simple and clear.=20

Leaving the checksum option and integrity issue aside (because I know we
can fix it and I'm writing a separate issue for it) please let give me
an answer to the following question:=20

Do you agree that the MN does not include the Alt-CoA option in the BU
when it is located in an IPv4-only network?=20

1. Yes
2. No

Please include a brief reason for you answer, Pascal already did so I
don't expect another one :). As I said, ignore the checksum issue, this
will be handled separately.

FWIW, I choose 1) above because it's the only way to make sure that the
HA can detect the presence of a NAT by comparing the outer v4 addresses
with the IPv6 header.=20

Hesham


 > -----Original Message-----
 > From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]=20
 > Sent: Tuesday, October 31, 2006 4:12 AM
 > To: Soliman, Hesham; mip6@ietf.org
 > Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used=20
 > when traversingIPv4 NAT
 >=20
 > Hi Hesham:
 >=20
 > I agree:
 >=20
 > 1) with relaxing the requirement in RFC 3775 to include an Alt CoA
 > option all the time.
 >=20
 > 2) that the MN should omit it, as opposed to the HA filtering it out.
 > The Alt CoA is the real address at which the MN is reachable, that is
 > what HAs implement today, that is what all people in the art=20
 > understand.
 > I want to stay simple and keep it that way.  I'd hate to=20
 > have rules like
 > "this is A but then if there is also that then this is B which is the
 > opposite of A", etc... we are not lawyers!=20
 >=20
 > 3) that we have to find an alternate way to endure that the MN is
 > reachable at the CoA, defined as the source of the packet when the HA
 > gets it.
 >=20
 > I'd also agree that:
 >=20
 > 4) UDP is used all the time in IPv4 roaming situation, regardless on
 > whether NAT is detected or not. That's not really in the=20
 > mail but since
 > you fixed the message format in the thread to add UDP, I=20
 > take advantage
 > of the exchange to raise that point again.
 >=20
 > I disagree:
 >=20
 > 5) to jump too quickly on the conclusion that the checksum=20
 > is the way to
 > go. I understand that it has value in certain scenarios that you
 > mention. But it fails to guarantee that the MN is reachable=20
 > at the CoA
 > in another common case that is NAT; and it does not protect against a
 > rogue DHCP server assigning you an IPv4 DoS'ed address, which could
 > easily happen in the IPv4 world.=20
 >=20
 > So when you call for consensus, please leave open the=20
 > solution to 3) so
 > we can see if there's a preferable alternative. I, for one,=20
 > would favor
 > an approach like 2 BU flows in row, which would emulate a 3 way
 > handshake and guarantee the reachability of the MN in all cases.=20
 >=20
 > Pascal
 >=20
 >=20
 >=20
 >=20
 > >-----Original Message-----
 > >From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > >Sent: Thursday, October 19, 2006 6:19 PM
 > >To: mip6@ietf.org
 > >Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
 > traversingIPv4 NAT
 > >
 > >Folks,
 > >
 > >This issue was revived mainly due to Vijay points on the=20
 > need for the
 > >checksum option when the alt-CoA is not used. Let me summarise the
 > >issues first then propose a way forward.
 > >
 > >Summary:
 > >--------
 > >
 > >The initial resolution for the issue suggested that we add=20
 > a checksum
 > >option that includes a checksum on the src and dst addresses in the
 > IPv6
 > >header. This was suggested to be used when the alt-coa is=20
 > not present
 > to
 > >maintain the integrity of the src address when ESP is used.=20
 > I want to
 > >emphasise that this is only needed when ESP is used, not with AH.
 > >
 > >Now the point that Vijay raised is also quite valid: With NAT
 > traversal,
 > >the outer IPv4 header is vulnerable, yet it is needed because the HA
 > >responds to that address and sets up the UDP tunnel to the outer
 > >(natted) IPv4 src address in the packet containing the BU.=20
 > There is no
 > >way we can secure that address, yet, it essentially acts as another
 > >binding, which if modified maliciously, would redirect the=20
 > MN's packets
 > >to another IPv4 address. To be clear, here is the packet format:
 > >BU packet received by HA after passing through NAT:
 > >  IPv4 HDR (src=3Dnatted-v4, dst=3DHA-addr)
 > >       UDP
 > >         IPv6 HDR (src=3Dv4-mapped-v6, dst=3DHA-addr)
 > >          ESP
 > >          DST-OPT
 > >          MH (BU)
 > >
 > >The HA responds with a similar packet including the BA and=20
 > forwards all
 > >future packets in the UDP tunnel, with the dst address in the IPv4
 > >header being the "natted-v4" address above.
 > >So essentially protecting the BU does not protect the MN from
 > >redirection attacks in this case because the IPv4 header is=20
 > vulnerable.
 > >This is an inherent problem with NAT traversal. There is practically
 > >nothing we can do about it.
 > >
 > >So the remaining question is: Is it worth worrying about=20
 > the integrity
 > >of the BU in this case? IMHO I think the answer is yes.=20
 > Why? Two main
 > >reasons:
 > >
 > >1. There can be cases where the BU is sent to a local HA and the
 > >operator can guarantee that no NATs are in the path. In this case we
 > >would lose integrity for no reason, i.e. the BU becomes the weakest
 > >link. This is not unusual really because an operator may=20
 > decide that it
 > >will only provide the HA function within its domain, which=20
 > happens to
 > >not include NATs between the MN and the HA.
 > >
 > >2. We have precedence with MIPv4 and NAT traversal where the RREQ is
 > >still secure despite the UNSAF NAT traversal.
 > >
 > >Note that the answer to 1) above may be "Use AH", but I=20
 > prefer to not
 > >force that on implementations that do not do it today=20
 > (although I would
 > >personally prefer AH in general for the BU).
 > >
 > >For these reasons, and there may be more, I prefer to not=20
 > take this big
 > >decision to lose the integrity for the BU.
 > >
 > >Way forward:
 > >------------
 > >
 > >This issue is now closed, we all agree on it, but there may be
 > >disagreement on the checksum part. So I suggest that I=20
 > generate a new
 > >issue for this discussion. Until the new issue is resolved,=20
 > I won't add
 > >the checksum option to the draft.
 > >
 > >Feel free to send comments.
 > >
 > >Hesham
 > >
 > >_______________________________________________
 > >Mip6 mailing list
 > >Mip6@ietf.org
 > >https://www1.ietf.org/mailman/listinfo/mip6
 >=20

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



From mip6-bounces@ietf.org Tue Oct 31 10:20:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GevPF-0006Nt-5W; Tue, 31 Oct 2006 10:20:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GevP9-0006NW-Q5
	for mip6@ietf.org; Tue, 31 Oct 2006 10:19:58 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GevOz-0006Hg-Ou
	for mip6@ietf.org; Tue, 31 Oct 2006 10:19:55 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 31 Oct 2006 16:19:43 +0100
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.20060308/8.12.11) with ESMTP id
	k9VFJh2t004102; Tue, 31 Oct 2006 16:19:43 +0100
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 k9VFJgmd015786; 
	Tue, 31 Oct 2006 16:19:42 +0100 (MET)
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); 
	Tue, 31 Oct 2006 16:19:42 +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
Date: Tue, 31 Oct 2006 16:19:32 +0100
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC02EE7D68@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Thread-Index: AcbuKRTePQYFgB62S8u2UMKyCITDHgAaLNXAAABwFpABQRjqkAIq1qwgACpqkBAABLpS4A==
From: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 31 Oct 2006 15:19:42.0308 (UTC)
	FILETIME=[FD4B7A40:01C6FCFF]
DKIM-Signature: a=rsa-sha1; q=dns; l=7306; t=1162307983; x=1163171983;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pthubert@cisco.com;
	z=From:=22Pascal=20Thubert=20\(pthubert\)=22=20<pthubert@cisco.com>
	|Subject:RE=3A=20concensus=3A=20=20issue=2076=3A=20Alt=20CoA=20should=20not=20be=
	20used=20when=20traversingIPv4=20NAT;
	X=v=3Dcisco.com=3B=20h=3DaybENvSZe18SStGw5z17LA7j81A=3D;
	b=jLI3k8r+OSEC8hCWEldDc45mI5Jbr2KS7z1bDSxjkYahF9QkYbK94xchkgiEKxNInDaKbjds
	iYcugcf82BQ6oeFh6/OjhKEikHRrLcR9s5uweqfoHBUdGqWGv1iVeLM9;
Authentication-Results: ams-dkim-2; header.From=pthubert@cisco.com; dkim=pass (
	sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53
Cc: 
Subject: [Mip6] RE: concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

1) Yes ...

>-----Original Message-----
>From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>Sent: Tuesday, October 31, 2006 2:11 PM
>To: Pascal Thubert (pthubert); mip6@ietf.org
>Subject: concensus: issue 76: Alt CoA should not be used when
traversingIPv4 NAT
>
>Pascal, all,
>
>There's been a lot of emails on this issue so I think WG members are
>fully informed now about what this issue involves. I will ask a simple
>question and I'd like people to choose one of the options below. To
>avoid any confusion I'm keeping the question simple and clear.
>
>Leaving the checksum option and integrity issue aside (because I know
we
>can fix it and I'm writing a separate issue for it) please let give me
>an answer to the following question:
>
>Do you agree that the MN does not include the Alt-CoA option in the BU
>when it is located in an IPv4-only network?
>
>1. Yes
>2. No
>
>Please include a brief reason for you answer, Pascal already did so I
>don't expect another one :). As I said, ignore the checksum issue, this
>will be handled separately.
>
>FWIW, I choose 1) above because it's the only way to make sure that the
>HA can detect the presence of a NAT by comparing the outer v4 addresses
>with the IPv6 header.
>
>Hesham
>
>
> > -----Original Message-----
> > From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
> > Sent: Tuesday, October 31, 2006 4:12 AM
> > To: Soliman, Hesham; mip6@ietf.org
> > Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used
> > when traversingIPv4 NAT
> >
> > Hi Hesham:
> >
> > I agree:
> >
> > 1) with relaxing the requirement in RFC 3775 to include an Alt CoA
> > option all the time.
> >
> > 2) that the MN should omit it, as opposed to the HA filtering it
out.
> > The Alt CoA is the real address at which the MN is reachable, that
is
> > what HAs implement today, that is what all people in the art
> > understand.
> > I want to stay simple and keep it that way.  I'd hate to
> > have rules like
> > "this is A but then if there is also that then this is B which is
the
> > opposite of A", etc... we are not lawyers!
> >
> > 3) that we have to find an alternate way to endure that the MN is
> > reachable at the CoA, defined as the source of the packet when the
HA
> > gets it.
> >
> > I'd also agree that:
> >
> > 4) UDP is used all the time in IPv4 roaming situation, regardless on
> > whether NAT is detected or not. That's not really in the
> > mail but since
> > you fixed the message format in the thread to add UDP, I
> > take advantage
> > of the exchange to raise that point again.
> >
> > I disagree:
> >
> > 5) to jump too quickly on the conclusion that the checksum
> > is the way to
> > go. I understand that it has value in certain scenarios that you
> > mention. But it fails to guarantee that the MN is reachable
> > at the CoA
> > in another common case that is NAT; and it does not protect against
a
> > rogue DHCP server assigning you an IPv4 DoS'ed address, which could
> > easily happen in the IPv4 world.
> >
> > So when you call for consensus, please leave open the
> > solution to 3) so
> > we can see if there's a preferable alternative. I, for one,
> > would favor
> > an approach like 2 BU flows in row, which would emulate a 3 way
> > handshake and guarantee the reachability of the MN in all cases.
> >
> > Pascal
> >
> >
> >
> >
> > >-----Original Message-----
> > >From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
> > >Sent: Thursday, October 19, 2006 6:19 PM
> > >To: mip6@ietf.org
> > >Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
> > traversingIPv4 NAT
> > >
> > >Folks,
> > >
> > >This issue was revived mainly due to Vijay points on the
> > need for the
> > >checksum option when the alt-CoA is not used. Let me summarise the
> > >issues first then propose a way forward.
> > >
> > >Summary:
> > >--------
> > >
> > >The initial resolution for the issue suggested that we add
> > a checksum
> > >option that includes a checksum on the src and dst addresses in the
> > IPv6
> > >header. This was suggested to be used when the alt-coa is
> > not present
> > to
> > >maintain the integrity of the src address when ESP is used.
> > I want to
> > >emphasise that this is only needed when ESP is used, not with AH.
> > >
> > >Now the point that Vijay raised is also quite valid: With NAT
> > traversal,
> > >the outer IPv4 header is vulnerable, yet it is needed because the
HA
> > >responds to that address and sets up the UDP tunnel to the outer
> > >(natted) IPv4 src address in the packet containing the BU.
> > There is no
> > >way we can secure that address, yet, it essentially acts as another
> > >binding, which if modified maliciously, would redirect the
> > MN's packets
> > >to another IPv4 address. To be clear, here is the packet format:
> > >BU packet received by HA after passing through NAT:
> > >  IPv4 HDR (src=3Dnatted-v4, dst=3DHA-addr)
> > >       UDP
> > >         IPv6 HDR (src=3Dv4-mapped-v6, dst=3DHA-addr)
> > >          ESP
> > >          DST-OPT
> > >          MH (BU)
> > >
> > >The HA responds with a similar packet including the BA and
> > forwards all
> > >future packets in the UDP tunnel, with the dst address in the IPv4
> > >header being the "natted-v4" address above.
> > >So essentially protecting the BU does not protect the MN from
> > >redirection attacks in this case because the IPv4 header is
> > vulnerable.
> > >This is an inherent problem with NAT traversal. There is
practically
> > >nothing we can do about it.
> > >
> > >So the remaining question is: Is it worth worrying about
> > the integrity
> > >of the BU in this case? IMHO I think the answer is yes.
> > Why? Two main
> > >reasons:
> > >
> > >1. There can be cases where the BU is sent to a local HA and the
> > >operator can guarantee that no NATs are in the path. In this case
we
> > >would lose integrity for no reason, i.e. the BU becomes the weakest
> > >link. This is not unusual really because an operator may
> > decide that it
> > >will only provide the HA function within its domain, which
> > happens to
> > >not include NATs between the MN and the HA.
> > >
> > >2. We have precedence with MIPv4 and NAT traversal where the RREQ
is
> > >still secure despite the UNSAF NAT traversal.
> > >
> > >Note that the answer to 1) above may be "Use AH", but I
> > prefer to not
> > >force that on implementations that do not do it today
> > (although I would
> > >personally prefer AH in general for the BU).
> > >
> > >For these reasons, and there may be more, I prefer to not
> > take this big
> > >decision to lose the integrity for the BU.
> > >
> > >Way forward:
> > >------------
> > >
> > >This issue is now closed, we all agree on it, but there may be
> > >disagreement on the checksum part. So I suggest that I
> > generate a new
> > >issue for this discussion. Until the new issue is resolved,
> > I won't add
> > >the checksum option to the draft.
> > >
> > >Feel free to send comments.
> > >
> > >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 Tue Oct 31 10:25:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GevUP-0001OV-3R; Tue, 31 Oct 2006 10:25:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GevUK-0001My-FI
	for mip6@ietf.org; Tue, 31 Oct 2006 10:25:19 -0500
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GevUH-0007FR-Jz
	for mip6@ietf.org; Tue, 31 Oct 2006 10:25:16 -0500
Received: by ug-out-1314.google.com with SMTP id 72so1258940ugd
	for <mip6@ietf.org>; Tue, 31 Oct 2006 07:25:12 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=qSlWH+nfnFSJ1F/Qr+g0ZQmGlz+N5FOzLzSNoeKDiS0pLLFzmd34Bkh6CyGdTyvGi30bspVvrQ2f0okXi3nyqKoRaOY3048HEcgK4x+l0SNrz97OdVtn0lgb84rSOyVsFvTOSt1bDpyQKcTKh1LRi9bN2wJqaKFAcltGME0qkes=
Received: by 10.78.160.2 with SMTP id i2mr6976494hue;
	Tue, 31 Oct 2006 07:25:12 -0800 (PST)
Received: from ?203.178.143.168? ( [203.178.143.168])
	by mx.google.com with ESMTP id 39sm7057641hui.2006.10.31.07.25.08;
	Tue, 31 Oct 2006 07:25:11 -0800 (PST)
In-Reply-To: <2309978910A6A6478C2C7585692B0AF40151E4@NAEX16.na.qualcomm.com>
References: <2309978910A6A6478C2C7585692B0AF40151E4@NAEX16.na.qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <31E6BA48-BA33-40B6-AF39-397F010F1C12@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Date: Wed, 1 Nov 2006 00:24:51 +0900
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bcd240e64c427d3d3617cfc704e7fd7f
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@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

Hello Hesham

Yes and No.
Sorry, but it's hard to tell without concerning checksum and  
integrity issue..

It depends on how we provide integrity check to IPv4 CoA.
If there is a way to solve this, i don't mind to omit ACoA.

Otherwise, no.
We should protect IPv4 CoA by ACoA, even if it is valid only
when MN roams in global IPv4 access network.
If the src address and the IPv4 CoA in an ACoA option are different,  
HA assumes
that MN is at NATed network and ignores the address in the ACoA option.
We leave redirection attack and warns this possibility in the spec.

> Leaving the checksum option and integrity issue aside (because I  
> know we
> can fix it and I'm writing a separate issue for it) please let give me

I am interested in how you fix this:-)

regards,
ryuji

On 2006/10/31, at 22:10, Soliman, Hesham wrote:

> Pascal, all,
>
> There's been a lot of emails on this issue so I think WG members are
> fully informed now about what this issue involves. I will ask a simple
> question and I'd like people to choose one of the options below. To
> avoid any confusion I'm keeping the question simple and clear.
>
> Leaving the checksum option and integrity issue aside (because I  
> know we
> can fix it and I'm writing a separate issue for it) please let give me
> an answer to the following question:
>
> Do you agree that the MN does not include the Alt-CoA option in the BU
> when it is located in an IPv4-only network?
>
> 1. Yes
> 2. No
>
> Please include a brief reason for you answer, Pascal already did so I
> don't expect another one :). As I said, ignore the checksum issue,  
> this
> will be handled separately.
>
> FWIW, I choose 1) above because it's the only way to make sure that  
> the
> HA can detect the presence of a NAT by comparing the outer v4  
> addresses
> with the IPv6 header.
>
> Hesham
>
>
>> -----Original Message-----
>> From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
>> Sent: Tuesday, October 31, 2006 4:12 AM
>> To: Soliman, Hesham; mip6@ietf.org
>> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used
>> when traversingIPv4 NAT
>>
>> Hi Hesham:
>>
>> I agree:
>>
>> 1) with relaxing the requirement in RFC 3775 to include an Alt CoA
>> option all the time.
>>
>> 2) that the MN should omit it, as opposed to the HA filtering it out.
>> The Alt CoA is the real address at which the MN is reachable, that is
>> what HAs implement today, that is what all people in the art
>> understand.
>> I want to stay simple and keep it that way.  I'd hate to
>> have rules like
>> "this is A but then if there is also that then this is B which is the
>> opposite of A", etc... we are not lawyers!
>>
>> 3) that we have to find an alternate way to endure that the MN is
>> reachable at the CoA, defined as the source of the packet when the HA
>> gets it.
>>
>> I'd also agree that:
>>
>> 4) UDP is used all the time in IPv4 roaming situation, regardless on
>> whether NAT is detected or not. That's not really in the
>> mail but since
>> you fixed the message format in the thread to add UDP, I
>> take advantage
>> of the exchange to raise that point again.
>>
>> I disagree:
>>
>> 5) to jump too quickly on the conclusion that the checksum
>> is the way to
>> go. I understand that it has value in certain scenarios that you
>> mention. But it fails to guarantee that the MN is reachable
>> at the CoA
>> in another common case that is NAT; and it does not protect against a
>> rogue DHCP server assigning you an IPv4 DoS'ed address, which could
>> easily happen in the IPv4 world.
>>
>> So when you call for consensus, please leave open the
>> solution to 3) so
>> we can see if there's a preferable alternative. I, for one,
>> would favor
>> an approach like 2 BU flows in row, which would emulate a 3 way
>> handshake and guarantee the reachability of the MN in all cases.
>>
>> Pascal
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>>> Sent: Thursday, October 19, 2006 6:19 PM
>>> To: mip6@ietf.org
>>> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
>> traversingIPv4 NAT
>>>
>>> Folks,
>>>
>>> This issue was revived mainly due to Vijay points on the
>> need for the
>>> checksum option when the alt-CoA is not used. Let me summarise the
>>> issues first then propose a way forward.
>>>
>>> Summary:
>>> --------
>>>
>>> The initial resolution for the issue suggested that we add
>> a checksum
>>> option that includes a checksum on the src and dst addresses in the
>> IPv6
>>> header. This was suggested to be used when the alt-coa is
>> not present
>> to
>>> maintain the integrity of the src address when ESP is used.
>> I want to
>>> emphasise that this is only needed when ESP is used, not with AH.
>>>
>>> Now the point that Vijay raised is also quite valid: With NAT
>> traversal,
>>> the outer IPv4 header is vulnerable, yet it is needed because the HA
>>> responds to that address and sets up the UDP tunnel to the outer
>>> (natted) IPv4 src address in the packet containing the BU.
>> There is no
>>> way we can secure that address, yet, it essentially acts as another
>>> binding, which if modified maliciously, would redirect the
>> MN's packets
>>> to another IPv4 address. To be clear, here is the packet format:
>>> BU packet received by HA after passing through NAT:
>>>  IPv4 HDR (src=natted-v4, dst=HA-addr)
>>>       UDP
>>>         IPv6 HDR (src=v4-mapped-v6, dst=HA-addr)
>>>          ESP
>>>          DST-OPT
>>>          MH (BU)
>>>
>>> The HA responds with a similar packet including the BA and
>> forwards all
>>> future packets in the UDP tunnel, with the dst address in the IPv4
>>> header being the "natted-v4" address above.
>>> So essentially protecting the BU does not protect the MN from
>>> redirection attacks in this case because the IPv4 header is
>> vulnerable.
>>> This is an inherent problem with NAT traversal. There is practically
>>> nothing we can do about it.
>>>
>>> So the remaining question is: Is it worth worrying about
>> the integrity
>>> of the BU in this case? IMHO I think the answer is yes.
>> Why? Two main
>>> reasons:
>>>
>>> 1. There can be cases where the BU is sent to a local HA and the
>>> operator can guarantee that no NATs are in the path. In this case we
>>> would lose integrity for no reason, i.e. the BU becomes the weakest
>>> link. This is not unusual really because an operator may
>> decide that it
>>> will only provide the HA function within its domain, which
>> happens to
>>> not include NATs between the MN and the HA.
>>>
>>> 2. We have precedence with MIPv4 and NAT traversal where the RREQ is
>>> still secure despite the UNSAF NAT traversal.
>>>
>>> Note that the answer to 1) above may be "Use AH", but I
>> prefer to not
>>> force that on implementations that do not do it today
>> (although I would
>>> personally prefer AH in general for the BU).
>>>
>>> For these reasons, and there may be more, I prefer to not
>> take this big
>>> decision to lose the integrity for the BU.
>>>
>>> Way forward:
>>> ------------
>>>
>>> This issue is now closed, we all agree on it, but there may be
>>> disagreement on the checksum part. So I suggest that I
>> generate a new
>>> issue for this discussion. Until the new issue is resolved,
>> I won't add
>>> the checksum option to the draft.
>>>
>>> Feel free to send comments.
>>>
>>> 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 Tue Oct 31 10:28:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GevX5-0001xK-UI; Tue, 31 Oct 2006 10:28:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GevX4-0001wv-Eh
	for mip6@ietf.org; Tue, 31 Oct 2006 10:28:06 -0500
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GevWz-0007m6-Vq
	for mip6@ietf.org; Tue, 31 Oct 2006 10:28:06 -0500
Received: by ug-out-1314.google.com with SMTP id 72so1259594ugd
	for <mip6@ietf.org>; Tue, 31 Oct 2006 07:28:01 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=ZZnMecS2zYvWbqWHJthtxLWDC++ftBiM+QqBXlROMxU1J2TQqCDyA+RBjKixDZt/0zwqckb4mDHgMYfD6kNaZPgIIYKUb+jmZS+PY3R7n+6jpTp6l4GPbNtooJmixlOTFofBb+5/knC4rKaOL5PWWUbU/oehuDt89MJ48m6xXK0=
Received: by 10.78.160.2 with SMTP id i2mr6966564hue;
	Tue, 31 Oct 2006 07:28:00 -0800 (PST)
Received: from ?203.178.143.168? ( [203.178.143.168])
	by mx.google.com with ESMTP id 30sm7017343hue.2006.10.31.07.27.56;
	Tue, 31 Oct 2006 07:27:58 -0800 (PST)
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC02EE76D8@xmb-ams-337.emea.cisco.com>
References: <7892795E1A87F04CADFCCF41FADD00FC02EE76D8@xmb-ams-337.emea.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <ABCE8887-962B-4661-8BEA-ECD87D2BD069@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
Date: Wed, 1 Nov 2006 00:27:47 +0900
To: Pascal Thubert ((pthubert)) <pthubert@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Pascal,

I am fine with both texts.
And same for the option name.

ryuji

On 2006/10/30, at 21:54, Pascal Thubert ((pthubert)) wrote:

> Just to make sure on what the agreement is:
>
> 1) There are 2 paragraphs in the original text that we want to update
>
> "
> If the binding update is accepted for the IPv4 home address, the home
> agent MUST create a binding cache entry for the IPv4 home
> address/prefix. If a single IPv4 home address were requested, it  
> MAY be
> stored in the IPv4-mapped IPv6 address format. The home agent MUST
> include an IPv4 acknowledgement option in the mobility header  
> containing
> the binding acknowledgement.
>
> If the binding update is accepted for both IPv4 and IPv6 home  
> addresses,
> the home agent MUST create two separate binding cache entries, one for
> each home address. The care-of address is the one included in the
> binding update. If the care-of address is an IPv4- mapped IPv6  
> address,
> the home agent MUST setup a tunnel to the IPv4 care-of address of the
> mobile node.
> "
>
> 2) When Vijay says IPv4 HoA, we mean IPv4 Home Address/prefix since  
> that
> is the language used in the draft and we might set up a network  
> route as
> opposed to a host route for IPv4.
>
> So the text in 1) becomes:
>
>
>    The home agent MUST create a binding cache entry for IPv6 HoA and
>    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
> information
>    for the IPv4 HoA/prefix can be in the form of a routing table entry
> or a
>    separate binding cache entry.  But this information is tied to the
>    binding cache entry for the IPv6 HoA and is removed when the
>    binding cache entry expires.
>
>
>
> 3) The text seems to force the forwarding information to be either BCE
> or RIB. I'd suggest that these are only examples, since a NAT table
> could be useful too.
>
>
> So the text in 1) becomes:
>
>
>    The home agent MUST create a binding cache entry for IPv6 HoA and
>    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
> information
>    for the IPv4 HoA/prefix can be for instance in the form of a  
> routing
> table entry or a
>    separate binding cache entry.  In any case, this information is  
> tied
> to the
>    binding cache entry for the IPv6 HoA and is removed when the
>    binding cache entry expires.
>
>
> IS that OK?
>
>
> By the way, we seem to also have consensus on renaming the "IPv4 home
> address option". I did not see opposition to "IPv4 addressing option".
>
> Any alternate proposal?
>
> Pascal
>
>> -----Original Message-----
>> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>> Sent: Thursday, October 26, 2006 2:31 AM
>> To: Vijay Devarapalli; RYUJI WAKIKAWA
>> Cc: Pascal Thubert (pthubert); mip6@ietf.org
>> Subject: RE: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
>>
>>
>>> building on your text, how about the following?
>>>
>>>    The home agent MUST create a binding cache entry for IPv6 HoA and
>>>    MUST setup forwarding for the IPv4 HoA. The forwarding
> information
>>>    for the IPv4 HoA can be in the form of a routing table entry or a
>>>    separate binding cache entry.  But this information is tied to
> the
>>>    binding cache entry for the IPv6 HoA and is removed when the
>>>    binding cache entry expires.
>>>
>>
>> => This text is perfectly fine with me, anyone has a problem with  
>> this?
>> If not, then it's in! No more please :)
>>
>> Hesham


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



From mip6-bounces@ietf.org Tue Oct 31 11:47:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GewlY-00055O-Bd; Tue, 31 Oct 2006 11:47:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GewlW-00054w-NK
	for mip6@ietf.org; Tue, 31 Oct 2006 11:47:06 -0500
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GewlU-00045F-W3
	for mip6@ietf.org; Tue, 31 Oct 2006 11:47:06 -0500
Received: by ug-out-1314.google.com with SMTP id 72so1278878ugd
	for <mip6@ietf.org>; Tue, 31 Oct 2006 08:47:03 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=qb+ArVsm8YMhCiWGFIX7wM+3umPIet8PX9sxRZyyxDPdnwkQuox+Z6BznRU6khJZ21FNpQnIEGodSZASp9EQA5bGhoZOzaVm6GnBgoKITsatFVLLwpyBkUXys15ac4VF1JWTsHXfDas3BK8gMZ/bqp+C1C1nwh9zqjgi1bGkbwE=
Received: by 10.67.93.6 with SMTP id v6mr6421675ugl;
	Tue, 31 Oct 2006 08:47:03 -0800 (PST)
Received: by 10.66.243.16 with HTTP; Tue, 31 Oct 2006 08:47:03 -0800 (PST)
Message-ID: <eaa74a7e0610310847o3660df39gdb49e635f3478a4d@mail.gmail.com>
Date: Tue, 31 Oct 2006 17:47:03 +0100
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Julien Bournelle" <julien.bournelle@int-evry.fr>, 
	"Yoshihiro Ohba" <yohba@tari.toshiba.com>
Subject: Re: [Mip6] WG LC: Yoshihiro Ohba's review
In-Reply-To: <20061010133810.GA1208@ipv6-3.int-evry.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C147E294.257AE%basavaraj.patil@nokia.com>
	<20061010133810.GA1208@ipv6-3.int-evry.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: mip6@ietf.org, Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Yoshi,

thanks for your review. Most of your comments are editorial: I agree
with them and I will fix them in next revision. Please find some
answers below for other comments.


>
>    G4.1  The AAA-HA interface MUST support pass-through EAP
>       authentication with the HA working as EAP authenticator operating
>       in pass-through mode and the AAAH server working as back-end
>       authentication server.
>
> YO: We can simplify the text something like:
>
> "
>    G4.1  The AAA-HA interface MUST allow the HA to act as a pass-through EAP
>       authenticator.
> "
>

ok

>
> 5.5.  Provisioning of Configuration Parameters
>
>    G5.1  The HA SHOULD be able to communicate to the AAAH server the
>       Home Address allocated to the MN (e.g., for allowing the AAAH
>       server to perform a DNS update on behalf of the MN).
>
> YO: FQDN is missing here.
>
> YO: Also, I am wondering if there is an option in which AAAH assigns a
> home address or a home address prefix and communicate the assignment
> to the HA.
>

This is not present in any bootstrapping solution specified in MIP6 WG
even though it may possible in some deployment scenarios.

>    G5.2  The AAAH SHOULD be able to indicate to the HA if the MN is
>       authorized to autoconfigure its Home Address.
>
> YO: Why this is not "MUST be able to"?
>

I'll fix it.

>
>    G6.2  The NAS SHOULD be able to notify that it supports the
>       functionalities described in [4].
>
> YO: The NAS notifies to whom?  I guess the NAS notifies AAAH server of
> the functionalities.  If so, please explicitly mention it.  Also why
> this is not "MUST be able to"?
>

ok, I'll fix it

>
>    G6.3  The ASP/MSP SHOULD be able to indicate to the MSA if it can
>       allocate a Home Agent to the MN.
>
> YO: Why MSP is mentioned here?  Also why this is not "MUST be able to"?
>

because if the ASP can allocate a Home Agent, this implies that it can
act as MSP.

>
>    G6.4  The AAA server of the MSA MUST be able to indicate to the NAS
>       whether the MN is authorized to use a local Home Agent (i.e. a
>       Home Agent in the ASP/MSP)
>
> YO: "MSA" should read "ASA/MSA".  Also "ASP/MSP" should read "MSP".
>

if the HA is local, the MSP is also ASP

> YO: Also, I would like to see the following discussions in this section:
>
> - Whether the AAA-HA interface as well as AAA-NAS interface allow
> authentication and authorization messages to be processed by different
> AAA servers.
>
> - In the integrated case, whether the AAA server for the AAA-HA
> interface and the AAA server for the AAA-NAS interface can be
> different.
>

Isn't this related to the discussion? Maybe we can add a goal stating
that in integrated scenario the AAA server authenticating the network
access may be different from the AAA server authenticating the
mobility service and the solution must support this. Is it ok?

>
> 8.  Security Considerations
>
>    As stated in Section 5.1 the AAA-HA interface must provide mutual
>    authentication, integrity and replay protection.  Furthermore, if
>    security parameters (e.g., IKE pre-shared key) are transferred
>    through this interface, confidentiality is strongly recommended to be
>    supported.  However note that AAA protocols does not support this
>    unless it exists a direct connection between corresponding entities.
>
> YO: Is there any scenario in which security parameters are not
> transferred through this interface?
>

What do you mean by security parameters here?

Anyway, the text si not fully correct since there is not any official
solution in MIP6 WG so far that implies that a pre-shared key is
transferred through this interface. However, there are some proposals
on this approach and I think the text in the sec cons can be kept.

--Gerardo

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



From mip6-bounces@ietf.org Tue Oct 31 11:55:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gewto-00084B-7l; Tue, 31 Oct 2006 11:55:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gewtm-000814-2C
	for mip6@ietf.org; Tue, 31 Oct 2006 11:55:38 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gewtf-0005Zk-Oo
	for mip6@ietf.org; Tue, 31 Oct 2006 11:55:37 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-7.tower-119.messagelabs.com!1162313553!6631154!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 14109 invoked from network); 31 Oct 2006 16:52:33 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-7.tower-119.messagelabs.com with SMTP;
	31 Oct 2006 16:52:33 -0000
Received: from il06exb01.corp.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k9VGqWFT009372;
	Tue, 31 Oct 2006 09:52:33 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exb01.corp.mot.com (8.13.1/8.13.0) with ESMTP id k9VGqVvX022310; 
	Tue, 31 Oct 2006 10:52:31 -0600 (CST)
Message-ID: <45477F4E.1020901@motorola.com>
Date: Tue, 31 Oct 2006 17:52:30 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
References: <7892795E1A87F04CADFCCF41FADD00FC02EE76D8@xmb-ams-337.emea.cisco.com>
	<ABCE8887-962B-4661-8BEA-ECD87D2BD069@gmail.com>
In-Reply-To: <ABCE8887-962B-4661-8BEA-ECD87D2BD069@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6@ietf.org, "Pascal Thubert \(\(pthubert\)\)" <pthubert@cisco.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

RYUJI WAKIKAWA wrote:
> Hi Pascal,
> 
> I am fine with both texts.
> And same for the option name.
[...]
>>    The home agent MUST create a binding cache entry for IPv6 HoA and
>>    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
>> information
>>    for the IPv4 HoA/prefix can be for instance in the form of a routing
>> table entry or a
>>    separate binding cache entry.  In any case, this information is tied
>> to the
>>    binding cache entry for the IPv6 HoA and is removed when the
>>    binding cache entry expires.
>>
>> IS that OK?
>>
>> By the way, we seem to also have consensus on renaming the "IPv4 home
>> address option". I did not see opposition to "IPv4 addressing option".
>>
>> Any alternate proposal?

YEs: IPv4 home address/subnet option.

Alex


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



From mip6-bounces@ietf.org Tue Oct 31 14:31:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GezJT-0001NM-Jj; Tue, 31 Oct 2006 14:30:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GezJQ-0001N8-7Q
	for mip6@ietf.org; Tue, 31 Oct 2006 14:30:16 -0500
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GezJL-0001uM-Oh
	for mip6@ietf.org; Tue, 31 Oct 2006 14:30:16 -0500
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 11:30:08 -0800
Message-ID: <4547A363.7030606@azairenet.com>
Date: Tue, 31 Oct 2006 11:26:27 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not be used
	when	traversingIPv4 NAT
References: <2309978910A6A6478C2C7585692B0AF40151E4@NAEX16.na.qualcomm.com>
In-Reply-To: <2309978910A6A6478C2C7585692B0AF40151E4@NAEX16.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2006 19:30:08.0499 (UTC)
	FILETIME=[F99A4430:01C6FD22]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@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

Soliman, Hesham wrote:
> Pascal, all, 
> 
> There's been a lot of emails on this issue so I think WG members are
> fully informed now about what this issue involves. I will ask a simple
> question and I'd like people to choose one of the options below. To
> avoid any confusion I'm keeping the question simple and clear. 
> 
> Leaving the checksum option and integrity issue aside (because I know we
> can fix it and I'm writing a separate issue for it) 

we have a solution in the form of altCoA or
the IPv4 CoA option. don't think we need a new
solution.

please let give me
> an answer to the following question: 
> 
> Do you agree that the MN does not include the Alt-CoA option in the BU
> when it is located in an IPv4-only network? 
> 
> 1. Yes
> 2. No

I vote NO.

you have to include either the IPv6 altCoA option
(with the IPv4 CoA present in the mapped format)
or include the IPv4 CoA option (its not in the
DS-MIPv6 draft currently but has been proposed
on the mailing list) to carry the IPv4 CoA and
provide integrity protection when there is no NAT.

Vijay

> Please include a brief reason for you answer, Pascal already did so I
> don't expect another one :). As I said, ignore the checksum issue, this
> will be handled separately.
> 
> FWIW, I choose 1) above because it's the only way to make sure that the
> HA can detect the presence of a NAT by comparing the outer v4 addresses
> with the IPv6 header. 
> 
> Hesham
> 
> 
>  > -----Original Message-----
>  > From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com] 
>  > Sent: Tuesday, October 31, 2006 4:12 AM
>  > To: Soliman, Hesham; mip6@ietf.org
>  > Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used 
>  > when traversingIPv4 NAT
>  > 
>  > Hi Hesham:
>  > 
>  > I agree:
>  > 
>  > 1) with relaxing the requirement in RFC 3775 to include an Alt CoA
>  > option all the time.
>  > 
>  > 2) that the MN should omit it, as opposed to the HA filtering it out.
>  > The Alt CoA is the real address at which the MN is reachable, that is
>  > what HAs implement today, that is what all people in the art 
>  > understand.
>  > I want to stay simple and keep it that way.  I'd hate to 
>  > have rules like
>  > "this is A but then if there is also that then this is B which is the
>  > opposite of A", etc... we are not lawyers! 
>  > 
>  > 3) that we have to find an alternate way to endure that the MN is
>  > reachable at the CoA, defined as the source of the packet when the HA
>  > gets it.
>  > 
>  > I'd also agree that:
>  > 
>  > 4) UDP is used all the time in IPv4 roaming situation, regardless on
>  > whether NAT is detected or not. That's not really in the 
>  > mail but since
>  > you fixed the message format in the thread to add UDP, I 
>  > take advantage
>  > of the exchange to raise that point again.
>  > 
>  > I disagree:
>  > 
>  > 5) to jump too quickly on the conclusion that the checksum 
>  > is the way to
>  > go. I understand that it has value in certain scenarios that you
>  > mention. But it fails to guarantee that the MN is reachable 
>  > at the CoA
>  > in another common case that is NAT; and it does not protect against a
>  > rogue DHCP server assigning you an IPv4 DoS'ed address, which could
>  > easily happen in the IPv4 world. 
>  > 
>  > So when you call for consensus, please leave open the 
>  > solution to 3) so
>  > we can see if there's a preferable alternative. I, for one, 
>  > would favor
>  > an approach like 2 BU flows in row, which would emulate a 3 way
>  > handshake and guarantee the reachability of the MN in all cases. 
>  > 
>  > Pascal
>  > 
>  > 
>  > 
>  > 
>  > >-----Original Message-----
>  > >From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>  > >Sent: Thursday, October 19, 2006 6:19 PM
>  > >To: mip6@ietf.org
>  > >Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
>  > traversingIPv4 NAT
>  > >
>  > >Folks,
>  > >
>  > >This issue was revived mainly due to Vijay points on the 
>  > need for the
>  > >checksum option when the alt-CoA is not used. Let me summarise the
>  > >issues first then propose a way forward.
>  > >
>  > >Summary:
>  > >--------
>  > >
>  > >The initial resolution for the issue suggested that we add 
>  > a checksum
>  > >option that includes a checksum on the src and dst addresses in the
>  > IPv6
>  > >header. This was suggested to be used when the alt-coa is 
>  > not present
>  > to
>  > >maintain the integrity of the src address when ESP is used. 
>  > I want to
>  > >emphasise that this is only needed when ESP is used, not with AH.
>  > >
>  > >Now the point that Vijay raised is also quite valid: With NAT
>  > traversal,
>  > >the outer IPv4 header is vulnerable, yet it is needed because the HA
>  > >responds to that address and sets up the UDP tunnel to the outer
>  > >(natted) IPv4 src address in the packet containing the BU. 
>  > There is no
>  > >way we can secure that address, yet, it essentially acts as another
>  > >binding, which if modified maliciously, would redirect the 
>  > MN's packets
>  > >to another IPv4 address. To be clear, here is the packet format:
>  > >BU packet received by HA after passing through NAT:
>  > >  IPv4 HDR (src=natted-v4, dst=HA-addr)
>  > >       UDP
>  > >         IPv6 HDR (src=v4-mapped-v6, dst=HA-addr)
>  > >          ESP
>  > >          DST-OPT
>  > >          MH (BU)
>  > >
>  > >The HA responds with a similar packet including the BA and 
>  > forwards all
>  > >future packets in the UDP tunnel, with the dst address in the IPv4
>  > >header being the "natted-v4" address above.
>  > >So essentially protecting the BU does not protect the MN from
>  > >redirection attacks in this case because the IPv4 header is 
>  > vulnerable.
>  > >This is an inherent problem with NAT traversal. There is practically
>  > >nothing we can do about it.
>  > >
>  > >So the remaining question is: Is it worth worrying about 
>  > the integrity
>  > >of the BU in this case? IMHO I think the answer is yes. 
>  > Why? Two main
>  > >reasons:
>  > >
>  > >1. There can be cases where the BU is sent to a local HA and the
>  > >operator can guarantee that no NATs are in the path. In this case we
>  > >would lose integrity for no reason, i.e. the BU becomes the weakest
>  > >link. This is not unusual really because an operator may 
>  > decide that it
>  > >will only provide the HA function within its domain, which 
>  > happens to
>  > >not include NATs between the MN and the HA.
>  > >
>  > >2. We have precedence with MIPv4 and NAT traversal where the RREQ is
>  > >still secure despite the UNSAF NAT traversal.
>  > >
>  > >Note that the answer to 1) above may be "Use AH", but I 
>  > prefer to not
>  > >force that on implementations that do not do it today 
>  > (although I would
>  > >personally prefer AH in general for the BU).
>  > >
>  > >For these reasons, and there may be more, I prefer to not 
>  > take this big
>  > >decision to lose the integrity for the BU.
>  > >
>  > >Way forward:
>  > >------------
>  > >
>  > >This issue is now closed, we all agree on it, but there may be
>  > >disagreement on the checksum part. So I suggest that I 
>  > generate a new
>  > >issue for this discussion. Until the new issue is resolved, 
>  > I won't add
>  > >the checksum option to the draft.
>  > >
>  > >Feel free to send comments.
>  > >
>  > >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 Tue Oct 31 14:35:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GezO1-0003u0-2b; Tue, 31 Oct 2006 14:35:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GezNw-0003sa-DY
	for mip6@ietf.org; Tue, 31 Oct 2006 14:34:58 -0500
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GezNw-0002jm-0l
	for mip6@ietf.org; Tue, 31 Oct 2006 14:34:56 -0500
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	k9VJYCTC034107; Tue, 31 Oct 2006 14:34:12 -0500 (EST)
	(envelope-from yohba@tari.toshiba.com)
Date: Tue, 31 Oct 2006 14:34:15 -0500
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] WG LC: Yoshihiro Ohba's review
Message-ID: <20061031193214.GF17201@steelhead>
References: <C147E294.257AE%basavaraj.patil@nokia.com>
	<20061010133810.GA1208@ipv6-3.int-evry.fr>
	<eaa74a7e0610310847o3660df39gdb49e635f3478a4d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <eaa74a7e0610310847o3660df39gdb49e635f3478a4d@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 95
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Julien Bournelle <julien.bournelle@int-evry.fr>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Gerardo, Julien,

On Tue, Oct 31, 2006 at 05:47:03PM +0100, Gerardo Giaretta wrote:

(snip)

> >
> >   G5.1  The HA SHOULD be able to communicate to the AAAH server the
> >      Home Address allocated to the MN (e.g., for allowing the AAAH
> >      server to perform a DNS update on behalf of the MN).
> >
> >YO: FQDN is missing here.
> >
> >YO: Also, I am wondering if there is an option in which AAAH assigns a
> >home address or a home address prefix and communicate the assignment
> >to the HA.
> >
> 
> This is not present in any bootstrapping solution specified in MIP6 WG
> even though it may possible in some deployment scenarios.

I thought that operators may want to let AAAH assign home
address/prefix dedicated to a particular user.  But if no one cares
this scenario, I would not care.

(snip)

> 
> >YO: Also, I would like to see the following discussions in this section:
> >
> >- Whether the AAA-HA interface as well as AAA-NAS interface allow
> >authentication and authorization messages to be processed by different
> >AAA servers.
> >
> >- In the integrated case, whether the AAA server for the AAA-HA
> >interface and the AAA server for the AAA-NAS interface can be
> >different.
> >
> 
> Isn't this related to the discussion? Maybe we can add a goal stating
> that in integrated scenario the AAA server authenticating the network
> access may be different from the AAA server authenticating the
> mobility service and the solution must support this. Is it ok?

Yes, this works for me for the second part.  What about the first part
about separation of authentication and authorization?  In general,
separation of authentication and authorization is good for being
flexibile in providing services.  For example, in a particular
scenario it is possible that an IKEv2 certificate without EAP is used
for authenticating MN, but a AAA protocol is used for authorizing the
MN.  Note that authorization does not necessary imply home
address/prefix assignment by AAAH, it can be just a binary result
(approved/denied).

> 
> >
> >8.  Security Considerations
> >
> >   As stated in Section 5.1 the AAA-HA interface must provide mutual
> >   authentication, integrity and replay protection.  Furthermore, if
> >   security parameters (e.g., IKE pre-shared key) are transferred
> >   through this interface, confidentiality is strongly recommended to be
> >   supported.  However note that AAA protocols does not support this
> >   unless it exists a direct connection between corresponding entities.
> >
> >YO: Is there any scenario in which security parameters are not
> >transferred through this interface?
> >
> 
> What do you mean by security parameters here?

I meant IKE pre-shared key because it is the only security parameter
mentioned in the text.  

> 
> Anyway, the text si not fully correct since there is not any official
> solution in MIP6 WG so far that implies that a pre-shared key is
> transferred through this interface. However, there are some proposals
> on this approach and I think the text in the sec cons can be kept.

In the authorization-only scenario I mentioned above, no IKE
pre-shared key would be transferred.

Regards,
Yoshihiro Ohba


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

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



From mip6-bounces@ietf.org Tue Oct 31 19:55:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf4NG-0004oy-VE; Tue, 31 Oct 2006 19:54:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf4NC-0004k9-8p
	for mip6@ietf.org; Tue, 31 Oct 2006 19:54:30 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf4NA-0004aG-I2
	for mip6@ietf.org; Tue, 31 Oct 2006 19:54:30 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kA10sNgR015743
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 31 Oct 2006 16:54:24 -0800
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kA10sMOc025479; Tue, 31 Oct 2006 16:54:23 -0800 (PST)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 16:54:22 -0800
Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 16:54:22 -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] concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Date: Tue, 31 Oct 2006 16:54:17 -0800
Message-ID: <2309978910A6A6478C2C7585692B0AF4036795@NAEX16.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
Thread-Index: Acb9BFsScJCtz+/mSx2Q6enpUkpIKAAS7UWQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "RYUJI WAKIKAWA" <ryuji.wakikawa@gmail.com>
X-OriginalArrivalTime: 01 Nov 2006 00:54:22.0128 (UTC)
	FILETIME=[44DE7B00:01C6FD50]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Ryuji,=20

Sounds good. I can assure you that we can protect the CoA, I want the
same thing. I just wanted to put aside the question for the moment. But
I definitely want to protect it.

Hesham=20

 > -----Original Message-----
 > From: RYUJI WAKIKAWA [mailto:ryuji.wakikawa@gmail.com]=20
 > Sent: Wednesday, November 01, 2006 2:25 AM
 > To: Soliman, Hesham
 > Cc: Pascal Thubert (pthubert); mip6@ietf.org
 > Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not=20
 > be used when traversingIPv4 NAT
 >=20
 > Hello Hesham
 >=20
 > Yes and No.
 > Sorry, but it's hard to tell without concerning checksum and =20
 > integrity issue..
 >=20
 > It depends on how we provide integrity check to IPv4 CoA.
 > If there is a way to solve this, i don't mind to omit ACoA.
 >=20
 > Otherwise, no.
 > We should protect IPv4 CoA by ACoA, even if it is valid only
 > when MN roams in global IPv4 access network.
 > If the src address and the IPv4 CoA in an ACoA option are=20
 > different, =20
 > HA assumes
 > that MN is at NATed network and ignores the address in the=20
 > ACoA option.
 > We leave redirection attack and warns this possibility in the spec.
 >=20
 > > Leaving the checksum option and integrity issue aside (because I =20
 > > know we
 > > can fix it and I'm writing a separate issue for it) please=20
 > let give me
 >=20
 > I am interested in how you fix this:-)
 >=20
 > regards,
 > ryuji
 >=20
 > On 2006/10/31, at 22:10, Soliman, Hesham wrote:
 >=20
 > > Pascal, all,
 > >
 > > There's been a lot of emails on this issue so I think WG=20
 > members are
 > > fully informed now about what this issue involves. I will=20
 > ask a simple
 > > question and I'd like people to choose one of the options below. To
 > > avoid any confusion I'm keeping the question simple and clear.
 > >
 > > Leaving the checksum option and integrity issue aside (because I =20
 > > know we
 > > can fix it and I'm writing a separate issue for it) please=20
 > let give me
 > > an answer to the following question:
 > >
 > > Do you agree that the MN does not include the Alt-CoA=20
 > option in the BU
 > > when it is located in an IPv4-only network?
 > >
 > > 1. Yes
 > > 2. No
 > >
 > > Please include a brief reason for you answer, Pascal=20
 > already did so I
 > > don't expect another one :). As I said, ignore the=20
 > checksum issue, =20
 > > this
 > > will be handled separately.
 > >
 > > FWIW, I choose 1) above because it's the only way to make=20
 > sure that =20
 > > the
 > > HA can detect the presence of a NAT by comparing the outer v4 =20
 > > addresses
 > > with the IPv6 header.
 > >
 > > Hesham
 > >
 > >
 > >> -----Original Message-----
 > >> From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
 > >> Sent: Tuesday, October 31, 2006 4:12 AM
 > >> To: Soliman, Hesham; mip6@ietf.org
 > >> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used
 > >> when traversingIPv4 NAT
 > >>
 > >> Hi Hesham:
 > >>
 > >> I agree:
 > >>
 > >> 1) with relaxing the requirement in RFC 3775 to include an Alt CoA
 > >> option all the time.
 > >>
 > >> 2) that the MN should omit it, as opposed to the HA=20
 > filtering it out.
 > >> The Alt CoA is the real address at which the MN is=20
 > reachable, that is
 > >> what HAs implement today, that is what all people in the art
 > >> understand.
 > >> I want to stay simple and keep it that way.  I'd hate to
 > >> have rules like
 > >> "this is A but then if there is also that then this is B=20
 > which is the
 > >> opposite of A", etc... we are not lawyers!
 > >>
 > >> 3) that we have to find an alternate way to endure that the MN is
 > >> reachable at the CoA, defined as the source of the packet=20
 > when the HA
 > >> gets it.
 > >>
 > >> I'd also agree that:
 > >>
 > >> 4) UDP is used all the time in IPv4 roaming situation,=20
 > regardless on
 > >> whether NAT is detected or not. That's not really in the
 > >> mail but since
 > >> you fixed the message format in the thread to add UDP, I
 > >> take advantage
 > >> of the exchange to raise that point again.
 > >>
 > >> I disagree:
 > >>
 > >> 5) to jump too quickly on the conclusion that the checksum
 > >> is the way to
 > >> go. I understand that it has value in certain scenarios that you
 > >> mention. But it fails to guarantee that the MN is reachable
 > >> at the CoA
 > >> in another common case that is NAT; and it does not=20
 > protect against a
 > >> rogue DHCP server assigning you an IPv4 DoS'ed address,=20
 > which could
 > >> easily happen in the IPv4 world.
 > >>
 > >> So when you call for consensus, please leave open the
 > >> solution to 3) so
 > >> we can see if there's a preferable alternative. I, for one,
 > >> would favor
 > >> an approach like 2 BU flows in row, which would emulate a 3 way
 > >> handshake and guarantee the reachability of the MN in all cases.
 > >>
 > >> Pascal
 > >>
 > >>
 > >>
 > >>
 > >>> -----Original Message-----
 > >>> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > >>> Sent: Thursday, October 19, 2006 6:19 PM
 > >>> To: mip6@ietf.org
 > >>> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
 > >> traversingIPv4 NAT
 > >>>
 > >>> Folks,
 > >>>
 > >>> This issue was revived mainly due to Vijay points on the
 > >> need for the
 > >>> checksum option when the alt-CoA is not used. Let me=20
 > summarise the
 > >>> issues first then propose a way forward.
 > >>>
 > >>> Summary:
 > >>> --------
 > >>>
 > >>> The initial resolution for the issue suggested that we add
 > >> a checksum
 > >>> option that includes a checksum on the src and dst=20
 > addresses in the
 > >> IPv6
 > >>> header. This was suggested to be used when the alt-coa is
 > >> not present
 > >> to
 > >>> maintain the integrity of the src address when ESP is used.
 > >> I want to
 > >>> emphasise that this is only needed when ESP is used, not with AH.
 > >>>
 > >>> Now the point that Vijay raised is also quite valid: With NAT
 > >> traversal,
 > >>> the outer IPv4 header is vulnerable, yet it is needed=20
 > because the HA
 > >>> responds to that address and sets up the UDP tunnel to the outer
 > >>> (natted) IPv4 src address in the packet containing the BU.
 > >> There is no
 > >>> way we can secure that address, yet, it essentially acts=20
 > as another
 > >>> binding, which if modified maliciously, would redirect the
 > >> MN's packets
 > >>> to another IPv4 address. To be clear, here is the packet format:
 > >>> BU packet received by HA after passing through NAT:
 > >>>  IPv4 HDR (src=3Dnatted-v4, dst=3DHA-addr)
 > >>>       UDP
 > >>>         IPv6 HDR (src=3Dv4-mapped-v6, dst=3DHA-addr)
 > >>>          ESP
 > >>>          DST-OPT
 > >>>          MH (BU)
 > >>>
 > >>> The HA responds with a similar packet including the BA and
 > >> forwards all
 > >>> future packets in the UDP tunnel, with the dst address=20
 > in the IPv4
 > >>> header being the "natted-v4" address above.
 > >>> So essentially protecting the BU does not protect the MN from
 > >>> redirection attacks in this case because the IPv4 header is
 > >> vulnerable.
 > >>> This is an inherent problem with NAT traversal. There is=20
 > practically
 > >>> nothing we can do about it.
 > >>>
 > >>> So the remaining question is: Is it worth worrying about
 > >> the integrity
 > >>> of the BU in this case? IMHO I think the answer is yes.
 > >> Why? Two main
 > >>> reasons:
 > >>>
 > >>> 1. There can be cases where the BU is sent to a local HA and the
 > >>> operator can guarantee that no NATs are in the path. In=20
 > this case we
 > >>> would lose integrity for no reason, i.e. the BU becomes=20
 > the weakest
 > >>> link. This is not unusual really because an operator may
 > >> decide that it
 > >>> will only provide the HA function within its domain, which
 > >> happens to
 > >>> not include NATs between the MN and the HA.
 > >>>
 > >>> 2. We have precedence with MIPv4 and NAT traversal where=20
 > the RREQ is
 > >>> still secure despite the UNSAF NAT traversal.
 > >>>
 > >>> Note that the answer to 1) above may be "Use AH", but I
 > >> prefer to not
 > >>> force that on implementations that do not do it today
 > >> (although I would
 > >>> personally prefer AH in general for the BU).
 > >>>
 > >>> For these reasons, and there may be more, I prefer to not
 > >> take this big
 > >>> decision to lose the integrity for the BU.
 > >>>
 > >>> Way forward:
 > >>> ------------
 > >>>
 > >>> This issue is now closed, we all agree on it, but there may be
 > >>> disagreement on the checksum part. So I suggest that I
 > >> generate a new
 > >>> issue for this discussion. Until the new issue is resolved,
 > >> I won't add
 > >>> the checksum option to the draft.
 > >>>
 > >>> Feel free to send comments.
 > >>>
 > >>> 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
 >=20
 >=20

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



From mip6-bounces@ietf.org Tue Oct 31 21:17:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf5e8-00055i-Rl; Tue, 31 Oct 2006 21:16:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf5e3-00055V-Bw
	for mip6@ietf.org; Tue, 31 Oct 2006 21:16:00 -0500
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf5dz-0001y1-1Z
	for mip6@ietf.org; Tue, 31 Oct 2006 21:15:59 -0500
Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 18:15:51 -0800
Message-ID: <45480357.2030601@azairenet.com>
Date: Tue, 31 Oct 2006 18:15:51 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>, 
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] WG LC: Yoshihiro Ohba's review
References: <C147E294.257AE%basavaraj.patil@nokia.com>	<20061010133810.GA1208@ipv6-3.int-evry.fr>
	<eaa74a7e0610310847o3660df39gdb49e635f3478a4d@mail.gmail.com>
In-Reply-To: <eaa74a7e0610310847o3660df39gdb49e635f3478a4d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Nov 2006 02:15:51.0804 (UTC)
	FILETIME=[A757D3C0:01C6FD5B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

>>    G5.2  The AAAH SHOULD be able to indicate to the HA if the MN is
>>       authorized to autoconfigure its Home Address.
>>
>> YO: Why this is not "MUST be able to"?
>>
> 
> I'll fix it.

this might be specific to the home agent. basically
the AAAH might not care whether the HA assigns the
home address or if the HA allows the MN to
autoconfigure the home address. so I don't think we
should have a "MUST" here.

>>    G6.2  The NAS SHOULD be able to notify that it supports the
>>       functionalities described in [4].
>>
>> YO: The NAS notifies to whom?  I guess the NAS notifies AAAH server of
>> the functionalities.  If so, please explicitly mention it.  Also why
>> this is not "MUST be able to"?
>>
> 
> ok, I'll fix it

again, should this be a MUST? I don't think we
should be requiring the NAS to be able to tell the
AAAH that it can support this functionality. Kuntal?

Vijay

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



From mip6-bounces@ietf.org Tue Oct 31 21:37:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf5yY-0000Ae-7Z; Tue, 31 Oct 2006 21:37:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf5yW-0000AU-Sm
	for mip6@ietf.org; Tue, 31 Oct 2006 21:37:09 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf5yV-0005H4-8k
	for mip6@ietf.org; Tue, 31 Oct 2006 21:37:08 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 31 Oct 2006 18:37:06 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	kA12b6ZR028861; Tue, 31 Oct 2006 18:37:06 -0800
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kA12b6W5009488;
	Tue, 31 Oct 2006 18:37:06 -0800 (PST)
Date: Tue, 31 Oct 2006 18:37:06 -0800 (PST)
From: Sri Gundavelli <sgundave@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [Mip6] RE: concensus: issue 76: Alt CoA should not be used when
	traversingIPv4 NAT
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC02EE7D68@xmb-ams-337.emea.cisco.com>
Message-ID: <Pine.GSO.4.63.0610311833220.11236@irp-view7.cisco.com>
References: <7892795E1A87F04CADFCCF41FADD00FC02EE7D68@xmb-ams-337.emea.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=7637; t=1162348626; x=1163212626;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sgundave@cisco.com;
	z=From:Sri=20Gundavelli=20<sgundave@cisco.com>
	|Subject:Re=3A=20[Mip6]=20RE=3A=20concensus=3A=20issue=2076=3A=20Alt=20CoA=20shou
	ld=20not=20be=20used=20when=0A=20traversingIPv4=20NAT;
	X=v=3Dcisco.com=3B=20h=3DX3iip0tuqm6GyGh1J9Evp+T2Z7Q=3D;
	b=Y0hUtI0/gX4nSg3yZTqXO7v+C4GcRE6RCgjlzZjGhz3/5MmvdGqi6C47XWlY8Zr10j+IZc0G
	IAQqHS2CNV7USwn2Hf1RUdGqzBjEpPZNrCTAlLn2Z7CRt1X2flJgVWGv;
Authentication-Results: sj-dkim-2.cisco.com; header.From=sgundave@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
Cc: mip6@ietf.org, "Soliman, Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


I support this. I agree with Pascal's explanation on
this.

1. Yes



On Tue, 31 Oct 2006, Pascal Thubert (pthubert) wrote:

> 1) Yes ...
>
>> -----Original Message-----
>> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>> Sent: Tuesday, October 31, 2006 2:11 PM
>> To: Pascal Thubert (pthubert); mip6@ietf.org
>> Subject: concensus: issue 76: Alt CoA should not be used when
> traversingIPv4 NAT
>>
>> Pascal, all,
>>
>> There's been a lot of emails on this issue so I think WG members are
>> fully informed now about what this issue involves. I will ask a simple
>> question and I'd like people to choose one of the options below. To
>> avoid any confusion I'm keeping the question simple and clear.
>>
>> Leaving the checksum option and integrity issue aside (because I know
> we
>> can fix it and I'm writing a separate issue for it) please let give me
>> an answer to the following question:
>>
>> Do you agree that the MN does not include the Alt-CoA option in the BU
>> when it is located in an IPv4-only network?
>>
>> 1. Yes
>> 2. No
>>
>> Please include a brief reason for you answer, Pascal already did so I
>> don't expect another one :). As I said, ignore the checksum issue, this
>> will be handled separately.
>>
>> FWIW, I choose 1) above because it's the only way to make sure that the
>> HA can detect the presence of a NAT by comparing the outer v4 addresses
>> with the IPv6 header.
>>
>> Hesham
>>
>>
>>> -----Original Message-----
>>> From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
>>> Sent: Tuesday, October 31, 2006 4:12 AM
>>> To: Soliman, Hesham; mip6@ietf.org
>>> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used
>>> when traversingIPv4 NAT
>>>
>>> Hi Hesham:
>>>
>>> I agree:
>>>
>>> 1) with relaxing the requirement in RFC 3775 to include an Alt CoA
>>> option all the time.
>>>
>>> 2) that the MN should omit it, as opposed to the HA filtering it
> out.
>>> The Alt CoA is the real address at which the MN is reachable, that
> is
>>> what HAs implement today, that is what all people in the art
>>> understand.
>>> I want to stay simple and keep it that way.  I'd hate to
>>> have rules like
>>> "this is A but then if there is also that then this is B which is
> the
>>> opposite of A", etc... we are not lawyers!
>>>
>>> 3) that we have to find an alternate way to endure that the MN is
>>> reachable at the CoA, defined as the source of the packet when the
> HA
>>> gets it.
>>>
>>> I'd also agree that:
>>>
>>> 4) UDP is used all the time in IPv4 roaming situation, regardless on
>>> whether NAT is detected or not. That's not really in the
>>> mail but since
>>> you fixed the message format in the thread to add UDP, I
>>> take advantage
>>> of the exchange to raise that point again.
>>>
>>> I disagree:
>>>
>>> 5) to jump too quickly on the conclusion that the checksum
>>> is the way to
>>> go. I understand that it has value in certain scenarios that you
>>> mention. But it fails to guarantee that the MN is reachable
>>> at the CoA
>>> in another common case that is NAT; and it does not protect against
> a
>>> rogue DHCP server assigning you an IPv4 DoS'ed address, which could
>>> easily happen in the IPv4 world.
>>>
>>> So when you call for consensus, please leave open the
>>> solution to 3) so
>>> we can see if there's a preferable alternative. I, for one,
>>> would favor
>>> an approach like 2 BU flows in row, which would emulate a 3 way
>>> handshake and guarantee the reachability of the MN in all cases.
>>>
>>> Pascal
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
>>>> Sent: Thursday, October 19, 2006 6:19 PM
>>>> To: mip6@ietf.org
>>>> Subject: RE: [Mip6] RE: issue 76: Alt CoA should not be used when
>>> traversingIPv4 NAT
>>>>
>>>> Folks,
>>>>
>>>> This issue was revived mainly due to Vijay points on the
>>> need for the
>>>> checksum option when the alt-CoA is not used. Let me summarise the
>>>> issues first then propose a way forward.
>>>>
>>>> Summary:
>>>> --------
>>>>
>>>> The initial resolution for the issue suggested that we add
>>> a checksum
>>>> option that includes a checksum on the src and dst addresses in the
>>> IPv6
>>>> header. This was suggested to be used when the alt-coa is
>>> not present
>>> to
>>>> maintain the integrity of the src address when ESP is used.
>>> I want to
>>>> emphasise that this is only needed when ESP is used, not with AH.
>>>>
>>>> Now the point that Vijay raised is also quite valid: With NAT
>>> traversal,
>>>> the outer IPv4 header is vulnerable, yet it is needed because the
> HA
>>>> responds to that address and sets up the UDP tunnel to the outer
>>>> (natted) IPv4 src address in the packet containing the BU.
>>> There is no
>>>> way we can secure that address, yet, it essentially acts as another
>>>> binding, which if modified maliciously, would redirect the
>>> MN's packets
>>>> to another IPv4 address. To be clear, here is the packet format:
>>>> BU packet received by HA after passing through NAT:
>>>>  IPv4 HDR (src=natted-v4, dst=HA-addr)
>>>>       UDP
>>>>         IPv6 HDR (src=v4-mapped-v6, dst=HA-addr)
>>>>          ESP
>>>>          DST-OPT
>>>>          MH (BU)
>>>>
>>>> The HA responds with a similar packet including the BA and
>>> forwards all
>>>> future packets in the UDP tunnel, with the dst address in the IPv4
>>>> header being the "natted-v4" address above.
>>>> So essentially protecting the BU does not protect the MN from
>>>> redirection attacks in this case because the IPv4 header is
>>> vulnerable.
>>>> This is an inherent problem with NAT traversal. There is
> practically
>>>> nothing we can do about it.
>>>>
>>>> So the remaining question is: Is it worth worrying about
>>> the integrity
>>>> of the BU in this case? IMHO I think the answer is yes.
>>> Why? Two main
>>>> reasons:
>>>>
>>>> 1. There can be cases where the BU is sent to a local HA and the
>>>> operator can guarantee that no NATs are in the path. In this case
> we
>>>> would lose integrity for no reason, i.e. the BU becomes the weakest
>>>> link. This is not unusual really because an operator may
>>> decide that it
>>>> will only provide the HA function within its domain, which
>>> happens to
>>>> not include NATs between the MN and the HA.
>>>>
>>>> 2. We have precedence with MIPv4 and NAT traversal where the RREQ
> is
>>>> still secure despite the UNSAF NAT traversal.
>>>>
>>>> Note that the answer to 1) above may be "Use AH", but I
>>> prefer to not
>>>> force that on implementations that do not do it today
>>> (although I would
>>>> personally prefer AH in general for the BU).
>>>>
>>>> For these reasons, and there may be more, I prefer to not
>>> take this big
>>>> decision to lose the integrity for the BU.
>>>>
>>>> Way forward:
>>>> ------------
>>>>
>>>> This issue is now closed, we all agree on it, but there may be
>>>> disagreement on the checksum part. So I suggest that I
>>> generate a new
>>>> issue for this discussion. Until the new issue is resolved,
>>> I won't add
>>>> the checksum option to the draft.
>>>>
>>>> Feel free to send comments.
>>>>
>>>> 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 Tue Oct 31 21:41:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf62c-0002cq-3H; Tue, 31 Oct 2006 21:41:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf62a-0002ck-Vh
	for mip6@ietf.org; Tue, 31 Oct 2006 21:41:20 -0500
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf62Z-0005rs-L1
	for mip6@ietf.org; Tue, 31 Oct 2006 21:41:20 -0500
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	kA12eZpx035982; Tue, 31 Oct 2006 21:40:35 -0500 (EST)
	(envelope-from yohba@tari.toshiba.com)
Date: Tue, 31 Oct 2006 21:40:39 -0500
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [Mip6] WG LC: Yoshihiro Ohba's review
Message-ID: <20061101024039.GB22250@steelhead>
References: <C147E294.257AE%basavaraj.patil@nokia.com>
	<20061010133810.GA1208@ipv6-3.int-evry.fr>
	<eaa74a7e0610310847o3660df39gdb49e635f3478a4d@mail.gmail.com>
	<45480357.2030601@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <45480357.2030601@azairenet.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 49
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: mip6@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,

What I meant in my comment was that these requirements seem to
indicate "mandatory-to-support and optional-to-use" features, and thus
I thought it is better to say "MUST be able to" than "SHOULD be able
to".  Perhaps we could simply say:

G5.2 The AAAH MAY indicate to the HA if the MN is authorized to
autoconfigure its Home Address.

G6.2 The NAS MAY notify that it supports the functionalities described
in [4].

Yoshihiro Ohba


On Tue, Oct 31, 2006 at 06:15:51PM -0800, Vijay Devarapalli wrote:
> Gerardo Giaretta wrote:
> 
> >>   G5.2  The AAAH SHOULD be able to indicate to the HA if the MN is
> >>      authorized to autoconfigure its Home Address.
> >>
> >>YO: Why this is not "MUST be able to"?
> >>
> >
> >I'll fix it.
> 
> this might be specific to the home agent. basically
> the AAAH might not care whether the HA assigns the
> home address or if the HA allows the MN to
> autoconfigure the home address. so I don't think we
> should have a "MUST" here.
> 
> >>   G6.2  The NAS SHOULD be able to notify that it supports the
> >>      functionalities described in [4].
> >>
> >>YO: The NAS notifies to whom?  I guess the NAS notifies AAAH server of
> >>the functionalities.  If so, please explicitly mention it.  Also why
> >>this is not "MUST be able to"?
> >>
> >
> >ok, I'll fix it
> 
> again, should this be a MUST? I don't think we
> should be requiring the NAS to be able to tell the
> AAAH that it can support this functionality. Kuntal?
> 
> Vijay
> 

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



From mip6-bounces@ietf.org Tue Oct 31 22:06:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf6QZ-0001Sq-8i; Tue, 31 Oct 2006 22:06:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf6QU-0001Sa-MY
	for mip6@ietf.org; Tue, 31 Oct 2006 22:06:03 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf6QT-0002QQ-0e
	for mip6@ietf.org; Tue, 31 Oct 2006 22:06:02 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kA135vXb025885
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 31 Oct 2006 19:05:58 -0800
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kA135mio002400; Tue, 31 Oct 2006 19:05:56 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 19:05:55 -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] concensus: issue 76: Alt CoA should not be
	usedwhen	traversingIPv4 NAT
Date: Tue, 31 Oct 2006 19:05:56 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325132D434C@NAEX13.na.qualcomm.com>
In-Reply-To: <4547A363.7030606@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus: issue 76: Alt CoA should not be
	usedwhen	traversingIPv4 NAT
Thread-Index: Acb9Lrn8GiniwXB0QBid/6unTH0IIwAMsWNg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>
X-OriginalArrivalTime: 01 Nov 2006 03:05:55.0345 (UTC)
	FILETIME=[A597D010:01C6FD62]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@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

All,
I just caught up with the long list of emails on this issue. Basically,
I think 1) makes sense, since in an IPv4 network, there is no prediction
of when the packets may pass through a NAT and when they may not. =20

Vijay, I'm confused by your choice here. Either the tampering of a CoA
needs to be detectable or it doesn't - applying a threat model where it
is sometimes needed (i.e., when there are no NATs) and at other times a
don't care (i.e., when there are NATs) is not making any sense to me.=20

That said, I'd make a couple of observations - I think detecting the
tampering of a CoA is important in all cases, regardless of whether
there is a NAT or not. But, I am not yet sure that the checksum approach
solves it the best way (checksum is certainly not a cryptographic
guarantee). I'll think about it more - at the moment, I'm not confident
enough to make that leap :)=20

Thanks,
Vidya

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
> Sent: Tuesday, October 31, 2006 11:26 AM
> To: Soliman, Hesham
> Cc: mip6@ietf.org; Pascal Thubert (pthubert)
> Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not=20
> be usedwhen traversingIPv4 NAT
>=20
> Soliman, Hesham wrote:
> > Pascal, all,
> >=20
> > There's been a lot of emails on this issue so I think WG=20
> members are=20
> > fully informed now about what this issue involves. I will=20
> ask a simple=20
> > question and I'd like people to choose one of the options below. To=20
> > avoid any confusion I'm keeping the question simple and clear.
> >=20
> > Leaving the checksum option and integrity issue aside=20
> (because I know=20
> > we can fix it and I'm writing a separate issue for it)
>=20
> we have a solution in the form of altCoA or the IPv4 CoA=20
> option. don't think we need a new solution.
>=20
> please let give me
> > an answer to the following question:=20
> >=20
> > Do you agree that the MN does not include the Alt-CoA=20
> option in the BU=20
> > when it is located in an IPv4-only network?
> >=20
> > 1. Yes
> > 2. No
>=20
> I vote NO.
>=20
> you have to include either the IPv6 altCoA option (with the=20
> IPv4 CoA present in the mapped format) or include the IPv4=20
> CoA option (its not in the
> DS-MIPv6 draft currently but has been proposed on the mailing=20
> list) to carry the IPv4 CoA and provide integrity protection=20
> when there is no NAT.
>=20
> Vijay
>=20
> > Please include a brief reason for you answer, Pascal=20
> already did so I=20
> > don't expect another one :). As I said, ignore the checksum issue,=20
> > this will be handled separately.
> >=20
> > FWIW, I choose 1) above because it's the only way to make sure that=20
> > the HA can detect the presence of a NAT by comparing the outer v4=20
> > addresses with the IPv6 header.
> >=20
> > Hesham
> >=20
> >=20
> >  > -----Original Message-----
> >  > From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]  >=20
> > Sent: Tuesday, October 31, 2006 4:12 AM  > To: Soliman, Hesham;=20
> > mip6@ietf.org  > Subject: RE: [Mip6] RE: issue 76: Alt CoA=20
> should not=20
> > be used  > when traversingIPv4 NAT  >  > Hi Hesham:
> >  >
> >  > I agree:
> >  >
> >  > 1) with relaxing the requirement in RFC 3775 to include=20
> an Alt CoA =20
> > > option all the time.
> >  >
> >  > 2) that the MN should omit it, as opposed to the HA=20
> filtering it out.
> >  > The Alt CoA is the real address at which the MN is=20
> reachable, that=20
> > is  > what HAs implement today, that is what all people in=20
> the art  >=20
> > understand.
> >  > I want to stay simple and keep it that way.  I'd hate to  > have=20
> > rules like  > "this is A but then if there is also that=20
> then this is B=20
> > which is the  > opposite of A", etc... we are not lawyers!
> >  >
> >  > 3) that we have to find an alternate way to endure that=20
> the MN is =20
> > > reachable at the CoA, defined as the source of the packet=20
> when the=20
> > HA  > gets it.
> >  >
> >  > I'd also agree that:
> >  >
> >  > 4) UDP is used all the time in IPv4 roaming situation,=20
> regardless=20
> > on  > whether NAT is detected or not. That's not really in=20
> the  > mail=20
> > but since  > you fixed the message format in the thread to=20
> add UDP, I =20
> > > take advantage  > of the exchange to raise that point again.
> >  >
> >  > I disagree:
> >  >
> >  > 5) to jump too quickly on the conclusion that the checksum  > is=20
> > the way to  > go. I understand that it has value in certain=20
> scenarios=20
> > that you  > mention. But it fails to guarantee that the MN is=20
> > reachable  > at the CoA  > in another common case that is=20
> NAT; and it=20
> > does not protect against a  > rogue DHCP server assigning=20
> you an IPv4=20
> > DoS'ed address, which could  > easily happen in the IPv4 world.
> >  >
> >  > So when you call for consensus, please leave open the  >=20
> solution=20
> > to 3) so  > we can see if there's a preferable alternative. I, for=20
> > one,  > would favor  > an approach like 2 BU flows in row,=20
> which would=20
> > emulate a 3 way  > handshake and guarantee the reachability=20
> of the MN=20
> > in all cases.
> >  >
> >  > Pascal
> >  >
> >  >
> >  >
> >  >
> >  > >-----Original Message-----
> >  > >From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]  > >Sent:=20
> > Thursday, October 19, 2006 6:19 PM  > >To: mip6@ietf.org  >=20
> >Subject:=20
> > RE: [Mip6] RE: issue 76: Alt CoA should not be used when  >=20
> > traversingIPv4 NAT  > >  > >Folks,  > >  > >This issue was revived=20
> > mainly due to Vijay points on the  > need for the  >=20
> >checksum option=20
> > when the alt-CoA is not used. Let me summarise the  > >issues first=20
> > then propose a way forward.
> >  > >
> >  > >Summary:
> >  > >--------
> >  > >
> >  > >The initial resolution for the issue suggested that we add  > a=20
> > checksum  > >option that includes a checksum on the src and dst=20
> > addresses in the  > IPv6  > >header. This was suggested to be used=20
> > when the alt-coa is  > not present  > to  > >maintain the=20
> integrity of=20
> > the src address when ESP is used.
> >  > I want to
> >  > >emphasise that this is only needed when ESP is used,=20
> not with AH.
> >  > >
> >  > >Now the point that Vijay raised is also quite valid:=20
> With NAT  >=20
> > traversal,  > >the outer IPv4 header is vulnerable, yet it=20
> is needed=20
> > because the HA  > >responds to that address and sets up the=20
> UDP tunnel=20
> > to the outer  > >(natted) IPv4 src address in the packet containing=20
> > the BU.
> >  > There is no
> >  > >way we can secure that address, yet, it essentially acts as=20
> > another  > >binding, which if modified maliciously, would=20
> redirect the =20
> > > MN's packets  > >to another IPv4 address. To be clear,=20
> here is the=20
> > packet format:
> >  > >BU packet received by HA after passing through NAT:
> >  > >  IPv4 HDR (src=3Dnatted-v4, dst=3DHA-addr)
> >  > >       UDP
> >  > >         IPv6 HDR (src=3Dv4-mapped-v6, dst=3DHA-addr)
> >  > >          ESP
> >  > >          DST-OPT
> >  > >          MH (BU)
> >  > >
> >  > >The HA responds with a similar packet including the BA and  >=20
> > forwards all  > >future packets in the UDP tunnel, with the dst=20
> > address in the IPv4  > >header being the "natted-v4" address above.
> >  > >So essentially protecting the BU does not protect the=20
> MN from  >=20
> > >redirection attacks in this case because the IPv4 header is  >=20
> > vulnerable.
> >  > >This is an inherent problem with NAT traversal. There is=20
> > practically  > >nothing we can do about it.
> >  > >
> >  > >So the remaining question is: Is it worth worrying about  > the=20
> > integrity  > >of the BU in this case? IMHO I think the=20
> answer is yes.
> >  > Why? Two main
> >  > >reasons:
> >  > >
> >  > >1. There can be cases where the BU is sent to a local=20
> HA and the =20
> > > >operator can guarantee that no NATs are in the path. In=20
> this case=20
> > we  > >would lose integrity for no reason, i.e. the BU becomes the=20
> > weakest  > >link. This is not unusual really because an=20
> operator may =20
> > > decide that it  > >will only provide the HA function within its=20
> > domain, which  > happens to  > >not include NATs between the MN and=20
> > the HA.
> >  > >
> >  > >2. We have precedence with MIPv4 and NAT traversal=20
> where the RREQ=20
> > is  > >still secure despite the UNSAF NAT traversal.
> >  > >
> >  > >Note that the answer to 1) above may be "Use AH", but I=20
>  > prefer=20
> > to not  > >force that on implementations that do not do it today  >=20
> > (although I would  > >personally prefer AH in general for the BU).
> >  > >
> >  > >For these reasons, and there may be more, I prefer to=20
> not  > take=20
> > this big  > >decision to lose the integrity for the BU.
> >  > >
> >  > >Way forward:
> >  > >------------
> >  > >
> >  > >This issue is now closed, we all agree on it, but there=20
> may be  >=20
> > >disagreement on the checksum part. So I suggest that I  >=20
> generate a=20
> > new  > >issue for this discussion. Until the new issue is=20
> resolved,  >=20
> > I won't add  > >the checksum option to the draft.
> >  > >
> >  > >Feel free to send comments.
> >  > >
> >  > >Hesham
> >  > >
> >  > >_______________________________________________
> >  > >Mip6 mailing list
> >  > >Mip6@ietf.org
> >  > >https://www1.ietf.org/mailman/listinfo/mip6
> >  >
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Tue Oct 31 22:49:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf763-0000Cx-Mo; Tue, 31 Oct 2006 22:48:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf75x-0008PY-Kw
	for mip6@ietf.org; Tue, 31 Oct 2006 22:48:54 -0500
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf75v-0003ZT-Ps
	for mip6@ietf.org; Tue, 31 Oct 2006 22:48:53 -0500
Received: from [10.1.210.3] ([66.92.223.6]) by moe.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 19:48:50 -0800
Message-ID: <4548191C.80501@azairenet.com>
Date: Tue, 31 Oct 2006 19:48:44 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not be
	usedwhen	traversingIPv4 NAT
References: <C24CB51D5AA800449982D9BCB90325132D434C@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325132D434C@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Nov 2006 03:48:50.0460 (UTC)
	FILETIME=[A47B2DC0:01C6FD68]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8d89ee9312a95de8ee48d1c94511f1bb
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

well, if there is a NAT on the path the source
address on the outer IPv4 header is modified.
anytime a packet goes through a NAT, we have
this problem. this is a common problem. so I
don't think we should design a DS-MIPv6
specific mechanism to protect  an address that
is modified by the NAT. its not worth it.

when there is no NAT, the use of altCoA or the
IPv4 CoA option provides automatic integrity
protection to the care-of address. thats all.

Vijay

Narayanan, Vidya wrote:
> All,
> I just caught up with the long list of emails on this issue. Basically,
> I think 1) makes sense, since in an IPv4 network, there is no prediction
> of when the packets may pass through a NAT and when they may not.  
> 
> Vijay, I'm confused by your choice here. Either the tampering of a CoA
> needs to be detectable or it doesn't - applying a threat model where it
> is sometimes needed (i.e., when there are no NATs) and at other times a
> don't care (i.e., when there are NATs) is not making any sense to me. 
> 
> That said, I'd make a couple of observations - I think detecting the
> tampering of a CoA is important in all cases, regardless of whether
> there is a NAT or not. But, I am not yet sure that the checksum approach
> solves it the best way (checksum is certainly not a cryptographic
> guarantee). I'll think about it more - at the moment, I'm not confident
> enough to make that leap :) 
> 
> Thanks,
> Vidya
> 
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com] 
>> Sent: Tuesday, October 31, 2006 11:26 AM
>> To: Soliman, Hesham
>> Cc: mip6@ietf.org; Pascal Thubert (pthubert)
>> Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not 
>> be usedwhen traversingIPv4 NAT
>>
>> Soliman, Hesham wrote:
>>> Pascal, all,
>>>
>>> There's been a lot of emails on this issue so I think WG 
>> members are 
>>> fully informed now about what this issue involves. I will 
>> ask a simple 
>>> question and I'd like people to choose one of the options below. To 
>>> avoid any confusion I'm keeping the question simple and clear.
>>>
>>> Leaving the checksum option and integrity issue aside 
>> (because I know 
>>> we can fix it and I'm writing a separate issue for it)
>> we have a solution in the form of altCoA or the IPv4 CoA 
>> option. don't think we need a new solution.
>>
>> please let give me
>>> an answer to the following question: 
>>>
>>> Do you agree that the MN does not include the Alt-CoA 
>> option in the BU 
>>> when it is located in an IPv4-only network?
>>>
>>> 1. Yes
>>> 2. No
>> I vote NO.
>>
>> you have to include either the IPv6 altCoA option (with the 
>> IPv4 CoA present in the mapped format) or include the IPv4 
>> CoA option (its not in the
>> DS-MIPv6 draft currently but has been proposed on the mailing 
>> list) to carry the IPv4 CoA and provide integrity protection 
>> when there is no NAT.
>>
>> Vijay
>>
>>> Please include a brief reason for you answer, Pascal 
>> already did so I 
>>> don't expect another one :). As I said, ignore the checksum issue, 
>>> this will be handled separately.
>>>
>>> FWIW, I choose 1) above because it's the only way to make sure that 
>>> the HA can detect the presence of a NAT by comparing the outer v4 
>>> addresses with the IPv6 header.
>>>
>>> Hesham
>>>
>>>
>>>  > -----Original Message-----
>>>  > From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]  > 
>>> Sent: Tuesday, October 31, 2006 4:12 AM  > To: Soliman, Hesham; 
>>> mip6@ietf.org  > Subject: RE: [Mip6] RE: issue 76: Alt CoA 
>> should not 
>>> be used  > when traversingIPv4 NAT  >  > Hi Hesham:
>>>  >
>>>  > I agree:
>>>  >
>>>  > 1) with relaxing the requirement in RFC 3775 to include 
>> an Alt CoA  
>>>> option all the time.
>>>  >
>>>  > 2) that the MN should omit it, as opposed to the HA 
>> filtering it out.
>>>  > The Alt CoA is the real address at which the MN is 
>> reachable, that 
>>> is  > what HAs implement today, that is what all people in 
>> the art  > 
>>> understand.
>>>  > I want to stay simple and keep it that way.  I'd hate to  > have 
>>> rules like  > "this is A but then if there is also that 
>> then this is B 
>>> which is the  > opposite of A", etc... we are not lawyers!
>>>  >
>>>  > 3) that we have to find an alternate way to endure that 
>> the MN is  
>>>> reachable at the CoA, defined as the source of the packet 
>> when the 
>>> HA  > gets it.
>>>  >
>>>  > I'd also agree that:
>>>  >
>>>  > 4) UDP is used all the time in IPv4 roaming situation, 
>> regardless 
>>> on  > whether NAT is detected or not. That's not really in 
>> the  > mail 
>>> but since  > you fixed the message format in the thread to 
>> add UDP, I  
>>>> take advantage  > of the exchange to raise that point again.
>>>  >
>>>  > I disagree:
>>>  >
>>>  > 5) to jump too quickly on the conclusion that the checksum  > is 
>>> the way to  > go. I understand that it has value in certain 
>> scenarios 
>>> that you  > mention. But it fails to guarantee that the MN is 
>>> reachable  > at the CoA  > in another common case that is 
>> NAT; and it 
>>> does not protect against a  > rogue DHCP server assigning 
>> you an IPv4 
>>> DoS'ed address, which could  > easily happen in the IPv4 world.
>>>  >
>>>  > So when you call for consensus, please leave open the  > 
>> solution 
>>> to 3) so  > we can see if there's a preferable alternative. I, for 
>>> one,  > would favor  > an approach like 2 BU flows in row, 
>> which would 
>>> emulate a 3 way  > handshake and guarantee the reachability 
>> of the MN 
>>> in all cases.
>>>  >
>>>  > Pascal
>>>  >
>>>  >
>>>  >
>>>  >
>>>  > >-----Original Message-----
>>>  > >From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]  > >Sent: 
>>> Thursday, October 19, 2006 6:19 PM  > >To: mip6@ietf.org  > 
>>> Subject: 
>>> RE: [Mip6] RE: issue 76: Alt CoA should not be used when  > 
>>> traversingIPv4 NAT  > >  > >Folks,  > >  > >This issue was revived 
>>> mainly due to Vijay points on the  > need for the  > 
>>> checksum option 
>>> when the alt-CoA is not used. Let me summarise the  > >issues first 
>>> then propose a way forward.
>>>  > >
>>>  > >Summary:
>>>  > >--------
>>>  > >
>>>  > >The initial resolution for the issue suggested that we add  > a 
>>> checksum  > >option that includes a checksum on the src and dst 
>>> addresses in the  > IPv6  > >header. This was suggested to be used 
>>> when the alt-coa is  > not present  > to  > >maintain the 
>> integrity of 
>>> the src address when ESP is used.
>>>  > I want to
>>>  > >emphasise that this is only needed when ESP is used, 
>> not with AH.
>>>  > >
>>>  > >Now the point that Vijay raised is also quite valid: 
>> With NAT  > 
>>> traversal,  > >the outer IPv4 header is vulnerable, yet it 
>> is needed 
>>> because the HA  > >responds to that address and sets up the 
>> UDP tunnel 
>>> to the outer  > >(natted) IPv4 src address in the packet containing 
>>> the BU.
>>>  > There is no
>>>  > >way we can secure that address, yet, it essentially acts as 
>>> another  > >binding, which if modified maliciously, would 
>> redirect the  
>>>> MN's packets  > >to another IPv4 address. To be clear, 
>> here is the 
>>> packet format:
>>>  > >BU packet received by HA after passing through NAT:
>>>  > >  IPv4 HDR (src=natted-v4, dst=HA-addr)
>>>  > >       UDP
>>>  > >         IPv6 HDR (src=v4-mapped-v6, dst=HA-addr)
>>>  > >          ESP
>>>  > >          DST-OPT
>>>  > >          MH (BU)
>>>  > >
>>>  > >The HA responds with a similar packet including the BA and  > 
>>> forwards all  > >future packets in the UDP tunnel, with the dst 
>>> address in the IPv4  > >header being the "natted-v4" address above.
>>>  > >So essentially protecting the BU does not protect the 
>> MN from  > 
>>>> redirection attacks in this case because the IPv4 header is  > 
>>> vulnerable.
>>>  > >This is an inherent problem with NAT traversal. There is 
>>> practically  > >nothing we can do about it.
>>>  > >
>>>  > >So the remaining question is: Is it worth worrying about  > the 
>>> integrity  > >of the BU in this case? IMHO I think the 
>> answer is yes.
>>>  > Why? Two main
>>>  > >reasons:
>>>  > >
>>>  > >1. There can be cases where the BU is sent to a local 
>> HA and the  
>>>>> operator can guarantee that no NATs are in the path. In 
>> this case 
>>> we  > >would lose integrity for no reason, i.e. the BU becomes the 
>>> weakest  > >link. This is not unusual really because an 
>> operator may  
>>>> decide that it  > >will only provide the HA function within its 
>>> domain, which  > happens to  > >not include NATs between the MN and 
>>> the HA.
>>>  > >
>>>  > >2. We have precedence with MIPv4 and NAT traversal 
>> where the RREQ 
>>> is  > >still secure despite the UNSAF NAT traversal.
>>>  > >
>>>  > >Note that the answer to 1) above may be "Use AH", but I 
>>  > prefer 
>>> to not  > >force that on implementations that do not do it today  > 
>>> (although I would  > >personally prefer AH in general for the BU).
>>>  > >
>>>  > >For these reasons, and there may be more, I prefer to 
>> not  > take 
>>> this big  > >decision to lose the integrity for the BU.
>>>  > >
>>>  > >Way forward:
>>>  > >------------
>>>  > >
>>>  > >This issue is now closed, we all agree on it, but there 
>> may be  > 
>>>> disagreement on the checksum part. So I suggest that I  > 
>> generate a 
>>> new  > >issue for this discussion. Until the new issue is 
>> resolved,  > 
>>> I won't add  > >the checksum option to the draft.
>>>  > >
>>>  > >Feel free to send comments.
>>>  > >
>>>  > >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
>>


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



From mip6-bounces@ietf.org Tue Oct 31 22:54:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf7Al-0003tR-5S; Tue, 31 Oct 2006 22:53:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf7Aj-0003t9-7B
	for mip6@ietf.org; Tue, 31 Oct 2006 22:53:49 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf7Ah-0004jX-Rx
	for mip6@ietf.org; Tue, 31 Oct 2006 22:53:49 -0500
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kA13rZeO005038
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 31 Oct 2006 19:53:36 -0800
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kA13rYvp003763; Tue, 31 Oct 2006 19:53:35 -0800 (PST)
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 19:53:34 -0800
Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 19:53:34 -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] concensus: issue 76: Alt CoA should not be
	usedwhen	traversingIPv4 NAT
Date: Tue, 31 Oct 2006 19:53:31 -0800
Message-ID: <2309978910A6A6478C2C7585692B0AF40367AD@NAEX16.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] concensus: issue 76: Alt CoA should not be
	usedwhen	traversingIPv4 NAT
Thread-Index: Acb9aK97Zgh6NbX7T4KfiBpUzJtlSgAAB1rw
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>
X-OriginalArrivalTime: 01 Nov 2006 03:53:34.0106 (UTC)
	FILETIME=[4D8C1FA0:01C6FD69]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@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


 > well, if there is a NAT on the path the source
 > address on the outer IPv4 header is modified.
 > anytime a packet goes through a NAT, we have
 > this problem. this is a common problem. so I
 > don't think we should design a DS-MIPv6
 > specific mechanism to protect  an address that
 > is modified by the NAT. its not worth it.

=3D> You keep repeating that and I keep answering as follows: If there =
is
an alt-coa in the packet then the HA has no way of knowing if there was
a NAT or not without checking it first, it can't simply compare the
outer headers...Again, this has nothing to do with the presence of the
NAT and everything to do with the presence of the alt-CoA...

So it makes zero sense to say that the "HA should ignore the alt-coa if
a NAT were detected" because the HA can't possibly know that a NAT was
en route without inspecting the alt-coa....

Hesham

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



From mip6-bounces@ietf.org Tue Oct 31 23:00:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf7H8-0007gq-RB; Tue, 31 Oct 2006 23:00:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf7H5-0007gX-Pm
	for mip6@ietf.org; Tue, 31 Oct 2006 23:00:25 -0500
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6]
	helo=moe.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf7H4-0006A4-Ey
	for mip6@ietf.org; Tue, 31 Oct 2006 23:00:23 -0500
Received: from [192.168.1.102] ([67.180.82.252]) by moe.corp.azairenet.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 20:00:21 -0800
Message-ID: <45481BD4.9070506@azairenet.com>
Date: Tue, 31 Oct 2006 20:00:20 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] concensus: issue 76: Alt CoA should not be
	usedwhen	traversingIPv4 NAT
References: <2309978910A6A6478C2C7585692B0AF40367AD@NAEX16.na.qualcomm.com>
In-Reply-To: <2309978910A6A6478C2C7585692B0AF40367AD@NAEX16.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Nov 2006 04:00:21.0788 (UTC)
	FILETIME=[408B75C0:01C6FD6A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org, "Pascal Thubert \(pthubert\)" <pthubert@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

Soliman, Hesham wrote:
>  > well, if there is a NAT on the path the source
>  > address on the outer IPv4 header is modified.
>  > anytime a packet goes through a NAT, we have
>  > this problem. this is a common problem. so I
>  > don't think we should design a DS-MIPv6
>  > specific mechanism to protect  an address that
>  > is modified by the NAT. its not worth it.
> 
> => You keep repeating that and I keep answering as follows: If there is
> an alt-coa in the packet then the HA has no way of knowing if there was
> a NAT or not without checking it first, it can't simply compare the
> outer headers...

I actually agree with this. :)

Again, this has nothing to do with the presence of the
> NAT and everything to do with the presence of the alt-CoA...
> 
> So it makes zero sense to say that the "HA should ignore the alt-coa if
> a NAT were detected" because the HA can't possibly know that a NAT was
> en route without inspecting the alt-coa....

hmmm... there is a misunderstanding. I didn't
say ignore the alt-CoA option. I said the HA
should not use the contents of the altCoA
option as the CoA when it detects a NAT.

it does not matter if the HA compares the source
address on the outer IPv4 header with the source
address of the inner header or the contents of
the altCoA option to detect the presence of a
NAT. its the same for me.

Vijay

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



From mip6-bounces@ietf.org Tue Oct 31 23:09:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf7Pd-0004WG-VZ; Tue, 31 Oct 2006 23:09:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf7Pd-0004W8-3g
	for mip6@ietf.org; Tue, 31 Oct 2006 23:09:13 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf7Pb-0007kS-MK
	for mip6@ietf.org; Tue, 31 Oct 2006 23:09:13 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kA1490it029680
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 31 Oct 2006 20:09:02 -0800
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.141.78])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kA148vIS016390; Tue, 31 Oct 2006 20:08:59 -0800 (PST)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 20:08:58 -0800
Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Oct 2006 20:08: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
Date: Tue, 31 Oct 2006 20:08:54 -0800
Message-ID: <2309978910A6A6478C2C7585692B0AF40367AF@NAEX16.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Resolution: [issue66] Setting up forwarding for IPv4 HoA
Thread-Index: Acb9ASr7k7wjpBVjTjiQhR+r4nUBqwAaiahQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "RYUJI WAKIKAWA" <ryuji.wakikawa@gmail.com>,
	"Pascal Thubert \(\(pthubert\)\)" <pthubert@cisco.com>
X-OriginalArrivalTime: 01 Nov 2006 04:08:57.0882 (UTC)
	FILETIME=[742927A0:01C6FD6B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Cc: mip6@ietf.org
Subject: [Mip6] Resolution: [issue66] Setting up forwarding for IPv4 HoA
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Ok with me too.

Folks, this issue is now closed.

Thanks for your feedback.

Hesham=20

 > -----Original Message-----
 > From: RYUJI WAKIKAWA [mailto:ryuji.wakikawa@gmail.com]=20
 > Sent: Wednesday, November 01, 2006 2:28 AM
 > To: Pascal Thubert ((pthubert))
 > Cc: Soliman, Hesham; Vijay Devarapalli; mip6@ietf.org
 > Subject: Re: [Mip6] Re: [issue66] Setting up forwarding for IPv4 HoA
 >=20
 > Hi Pascal,
 >=20
 > I am fine with both texts.
 > And same for the option name.
 >=20
 > ryuji
 >=20
 > On 2006/10/30, at 21:54, Pascal Thubert ((pthubert)) wrote:
 >=20
 > > Just to make sure on what the agreement is:
 > >
 > > 1) There are 2 paragraphs in the original text that we=20
 > want to update
 > >
 > > "
 > > If the binding update is accepted for the IPv4 home=20
 > address, the home
 > > agent MUST create a binding cache entry for the IPv4 home
 > > address/prefix. If a single IPv4 home address were requested, it =20
 > > MAY be
 > > stored in the IPv4-mapped IPv6 address format. The home agent MUST
 > > include an IPv4 acknowledgement option in the mobility header =20
 > > containing
 > > the binding acknowledgement.
 > >
 > > If the binding update is accepted for both IPv4 and IPv6 home =20
 > > addresses,
 > > the home agent MUST create two separate binding cache=20
 > entries, one for
 > > each home address. The care-of address is the one included in the
 > > binding update. If the care-of address is an IPv4- mapped IPv6 =20
 > > address,
 > > the home agent MUST setup a tunnel to the IPv4 care-of=20
 > address of the
 > > mobile node.
 > > "
 > >
 > > 2) When Vijay says IPv4 HoA, we mean IPv4 Home=20
 > Address/prefix since =20
 > > that
 > > is the language used in the draft and we might set up a network =20
 > > route as
 > > opposed to a host route for IPv4.
 > >
 > > So the text in 1) becomes:
 > >
 > >
 > >    The home agent MUST create a binding cache entry for=20
 > IPv6 HoA and
 > >    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
 > > information
 > >    for the IPv4 HoA/prefix can be in the form of a routing=20
 > table entry
 > > or a
 > >    separate binding cache entry.  But this information is=20
 > tied to the
 > >    binding cache entry for the IPv6 HoA and is removed when the
 > >    binding cache entry expires.
 > >
 > >
 > >
 > > 3) The text seems to force the forwarding information to=20
 > be either BCE
 > > or RIB. I'd suggest that these are only examples, since a NAT table
 > > could be useful too.
 > >
 > >
 > > So the text in 1) becomes:
 > >
 > >
 > >    The home agent MUST create a binding cache entry for=20
 > IPv6 HoA and
 > >    MUST setup forwarding for the IPv4 HoA/prefix. The forwarding
 > > information
 > >    for the IPv4 HoA/prefix can be for instance in the form of a =20
 > > routing
 > > table entry or a
 > >    separate binding cache entry.  In any case, this=20
 > information is =20
 > > tied
 > > to the
 > >    binding cache entry for the IPv6 HoA and is removed when the
 > >    binding cache entry expires.
 > >
 > >
 > > IS that OK?
 > >
 > >
 > > By the way, we seem to also have consensus on renaming the=20
 > "IPv4 home
 > > address option". I did not see opposition to "IPv4=20
 > addressing option".
 > >
 > > Any alternate proposal?
 > >
 > > Pascal
 > >
 > >> -----Original Message-----
 > >> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > >> Sent: Thursday, October 26, 2006 2:31 AM
 > >> To: Vijay Devarapalli; RYUJI WAKIKAWA
 > >> Cc: Pascal Thubert (pthubert); mip6@ietf.org
 > >> Subject: RE: [Mip6] Re: [issue66] Setting up forwarding=20
 > for IPv4 HoA
 > >>
 > >>
 > >>> building on your text, how about the following?
 > >>>
 > >>>    The home agent MUST create a binding cache entry for=20
 > IPv6 HoA and
 > >>>    MUST setup forwarding for the IPv4 HoA. The forwarding
 > > information
 > >>>    for the IPv4 HoA can be in the form of a routing=20
 > table entry or a
 > >>>    separate binding cache entry.  But this information is tied to
 > > the
 > >>>    binding cache entry for the IPv6 HoA and is removed when the
 > >>>    binding cache entry expires.
 > >>>
 > >>
 > >> =3D> This text is perfectly fine with me, anyone has a=20
 > problem with =20
 > >> this?
 > >> If not, then it's in! No more please :)
 > >>
 > >> Hesham
 >=20
 >=20

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



