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

Sami Vaarala <sami.vaarala@iki.fi> Wed, 20 December 2006 07:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwvT5-0002C0-B9; Wed, 20 Dec 2006 02:02:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwvT4-0002Br-2D for mip4@ietf.org; Wed, 20 Dec 2006 02:02:22 -0500
Received: from ns.academica.fi ([82.133.251.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwvT2-0005vz-Op for mip4@ietf.org; Wed, 20 Dec 2006 02:02:22 -0500
Received: from [82.133.140.68] (ip82-133-140-68.customer.academica.fi [82.133.140.68]) by ns.academica.fi (Postfix) with ESMTP id 51CE7199B26; Wed, 20 Dec 2006 07:59:49 +0200 (EET)
Message-ID: <4588DF84.8060607@iki.fi>
Date: Wed, 20 Dec 2006 09:00:20 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
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>
In-Reply-To: <458840EE.9070204@azairenet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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

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.

BR,

-Sami

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