[Mip4] 3344bis clarification on identifying the FA's SA
Kent Leung <kleung@cisco.com> Wed, 19 January 2005 23:34 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09332 for <mip4-web-archive@ietf.org>; Wed, 19 Jan 2005 18:34:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrPak-0002k0-1P for mip4-web-archive@ietf.org; Wed, 19 Jan 2005 18:50:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CrPF4-0001n0-3I; Wed, 19 Jan 2005 18:28:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CrPD3-0001Q0-La for mip4@megatron.ietf.org; Wed, 19 Jan 2005 18:25:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08837 for <mip4@ietf.org>; Wed, 19 Jan 2005 18:25:55 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrPSb-0002XM-I4 for mip4@ietf.org; Wed, 19 Jan 2005 18:42:02 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 19 Jan 2005 16:33:04 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0JNPLMA029021 for <mip4@ietf.org>; Wed, 19 Jan 2005 15:25:23 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-128-107-163-211.cisco.com [128.107.163.211]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BAU27417; Wed, 19 Jan 2005 15:25:21 -0800 (PST)
Message-Id: <4.3.2.7.2.20050119151642.02b41798@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 19 Jan 2005 15:25:20 -0800
To: mip4@ietf.org
From: Kent Leung <kleung@cisco.com>
In-Reply-To: <41EB8B4E.2010205@motorola.com>
References: <41B76050.8080709@levkowetz.com> <41B76050.8080709@levkowetz.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [Mip4] 3344bis clarification on identifying the FA's SA
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Hi. I realized during our Deregistration/FHAE discussions that
we assumed that the FA's SA is indexed by the source IP address of the
RRQ on the HA. But it's not explicitly clear in RFC 3344 (going back to
RFC 2002) that source IP address is the method to identify the FA since
CoA may also be used.
So this leaves ambiguity in implementation and also introduces deployment
issues where the SA is configured based on CoA.
I think we should clearly state some text to avoid ambiguity? Something like
"The FA or HA is identified by the source IP address of the registration
message. This IP address and the SPI is used to index the security
association to authenticate the message."
Thoughts?
Kent
--
| | Kent Leung
:|: :|: IP Mobility Development
:|||: :|||: IOS Technologies Division
:|||||||: :|||||||: Voice: 408.526.5030
.:|||||||||:.:|||||||||:. Fax: 408.525.1653
c i s c o S y s t e m s Email: kleung@cisco.com
--
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/
- [Mip4] DRAFT Minutes from MIP4 meeting in Washing… Henrik Levkowetz
- Re: [Mip4] DRAFT Minutes from MIP4 meeting in Was… Alexandru Petrescu
- [Mip4] 3344bis clarification on identifying the F… Kent Leung
- Re: [Mip4] 3344bis clarification on identifying t… Henrik Levkowetz
- RE: [Mip4] 3344bis clarification on identifying t… Fredrik Johansson
- RE: [Mip4] 3344bis clarification on identifying t… Kent Leung
- Re: [Mip4] 3344bis clarification on identifying t… Kent Leung
- Re: [Mip4] 3344bis clarification on identifying t… Pete McCann
- Re: [Mip4] 3344bis clarification on identifying t… Kent Leung