Re: [Mip4] 3344bis clarification on identifying the FA's SA
Kent Leung <kleung@cisco.com> Mon, 24 January 2005 18:18 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 NAA08323 for <mip4-web-archive@ietf.org>; Mon, 24 Jan 2005 13:18:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ct93L-0006X0-F8 for mip4-web-archive@ietf.org; Mon, 24 Jan 2005 13:35:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ct8iY-0003N3-Ng; Mon, 24 Jan 2005 13:13:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ct8Wn-0000bJ-Pi for mip4@megatron.ietf.org; Mon, 24 Jan 2005 13:01:29 -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 NAA06700 for <mip4@ietf.org>; Mon, 24 Jan 2005 13:01:26 -0500 (EST)
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.33) id 1Ct8nK-0005mV-M5 for mip4@ietf.org; Mon, 24 Jan 2005 13:18:36 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 24 Jan 2005 10:08:33 -0800
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 j0OI0mM8010964; Mon, 24 Jan 2005 10:00:50 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-128-107-163-176.cisco.com [128.107.163.176]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BAX78645; Mon, 24 Jan 2005 10:00:49 -0800 (PST)
Message-Id: <4.3.2.7.2.20050124095136.02d36a20@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 24 Jan 2005 10:00:49 -0800
To: Pete McCann <mccap@lucent.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] 3344bis clarification on identifying the FA's SA
In-Reply-To: <16885.8644.146401.668240@gargle.gargle.HOWL>
References: <4.3.2.7.2.20050120110108.02b3f568@mira-sjcm-2.cisco.com> <4.3.2.7.2.20050119151642.02b41798@mira-sjcm-2.cisco.com> <41B76050.8080709@levkowetz.com> <4.3.2.7.2.20050120110108.02b3f568@mira-sjcm-2.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
At 10:26 AM 1/24/2005 -0600, Pete McCann wrote:
>Hi, all,
>
>Kent Leung writes:
> > Hi Henrik.
> >
> > At 01:33 AM 1/20/2005 +0100, Henrik Levkowetz wrote:
> >
> >
> > >I suspect that the reason this has not been raised before is that before
> > >we introduced NAT traversal into the equation, it was an unstated
> > >assumption that the source IP address and the CoA address would be
> the same.
> >
> > KL>
> >
> > Actually, RFC 2002/3344 states to use the egress interface's IP
> address as the
> > source IP address of the RRQ (sect. 3.7.2.2). When RFC 3519 was
> introduced,
> > the mandate for the addressed to be the same was added.
>
>Clearly, this only applies when using an FA-located CoA, right?
>For Co-located CoA (in an R-bit environment) the FA must relay the
>message with a different source IP address and CoA.
Yes. The behavior of the R-bit is documented in Sect. 4.11 in RFC 3519.
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