Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Wed, 20 December 2006 07:22 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwvmc-0004Yf-Cm; Wed, 20 Dec 2006 02:22:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwvma-0004YP-Rt for mip4@ietf.org; Wed, 20 Dec 2006 02:22:32 -0500
Received: from mail2.azairenet.com ([66.92.223.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwvmY-0001p7-Hr for mip4@ietf.org; Wed, 20 Dec 2006 02:22:32 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Dec 2006 23:22:29 -0800
Message-ID: <4588E4B3.7070008@azairenet.com>
Date: Tue, 19 Dec 2006 23:22:27 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com> <45835C6C.1090404@iki.fi> <458840EE.9070204@azairenet.com> <4588DF84.8060607@iki.fi>
In-Reply-To: <4588DF84.8060607@iki.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2006 07:22:29.0566 (UTC) FILETIME=[9B8145E0:01C72407]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>, Mobile IPv4 Mailing List <mip4@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami Vaarala wrote:
> Vijay Devarapalli wrote:
>> Here is some new text
>>
>  >    When the mobile node sends a registration request to the i-HA from an
>  >    untrusted network that does not go through the IPsec tunnel, it may
>  >    be leaking the i-HA's address, its own identity including the NAI and
>  >    the home address, and the Authenticator value in the authentication
>  >    extensions to the untrusted network.  This may be a concern in some
>  >    deployments.
> 
> Sounds best so far.  But why "it may be leaking"?  It is leaking this
> information with 100% certainty (we're not assuming any trust in the
> network).  Whether anyone is listening is another matter :-)  So how
> about this refinement:
> 
>    When the mobile node sends a registration request to the i-HA from an
>    untrusted network that does not go through the IPsec tunnel, it leaks
>    the i-HA's address, its own identity including the NAI and the home
>    address, and the Authenticator value in the authentication extensions
>    to the untrusted network.  This may be a concern in some deployments.

Ok. Replaced "leak" by "reveal".

    When the mobile node sends a registration request to the i-HA from an
    untrusted network that does not go through the IPsec tunnel, it will
    reveal the i-HA's address, its own identity including the NAI and the
    home address, and the Authenticator value in the authentication
    extensions to the untrusted network.  This may be a concern in some
    deployments.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/