[Mip4] WG last call follow-up for vpn traversal problem statement
Henrik Levkowetz <henrik@levkowetz.com> Sat, 20 September 2003 01:37 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01623 for <mip4-archive@odin.ietf.org>; Fri, 19 Sep 2003 21:37:31 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.12.8/8.12.8) with ESMTP id h8K1VhDl020140 for <mip4-archive@odin.ietf.org>; Fri, 19 Sep 2003 21:37:10 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7QIrjP6014269 for mip4-archive@odin.ietf.org; Tue, 26 Aug 2003 14:53:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19riwo-0003ea-JY for mip4-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 14:53:43 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21200 for <mip4-web-archive@ietf.org>; Tue, 26 Aug 2003 14:53:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19riwG-0003ZW-12; Tue, 26 Aug 2003 14:53:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rcMl-0001Ce-Bh for mip4@optimus.ietf.org; Tue, 26 Aug 2003 07:52:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00259 for <mip4@ietf.org>; Tue, 26 Aug 2003 07:51:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rcMk-0007ju-00 for mip4@ietf.org; Tue, 26 Aug 2003 07:52:02 -0400
Received: from [213.80.52.78] (helo=mailgw.local.ipunplugged.com) by ietf-mx with esmtp (Exim 4.12) id 19rcMj-0007jE-00 for mip4@ietf.org; Tue, 26 Aug 2003 07:52:01 -0400
Received: from zinfandel.local.ipunplugged.com (chardonnay.local.ipunplugged.com [192.168.4.44]) by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with SMTP id h7QBpNwf019980; Tue, 26 Aug 2003 13:51:24 +0200
Date: Tue, 26 Aug 2003 13:51:21 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
To: mip4@ietf.org
Cc: "Adrangi, Farid" <farid.adrangi@intel.com>, Sami Vaarala <sami.vaarala@netseal.com>
Message-Id: <20030826135121.3d2f4535.henrik@levkowetz.com>
X-Mailer: Sylpheed version 0.8.11claws141 (GTK+ 1.2.10; i386-debian-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=0.0 required=5.0 tests=none version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-RAVMilter-Version: 8.4.4(snapshot 20030410) (mailgw.local.ipunplugged.com)
Content-Transfer-Encoding: 7bit
Subject: [Mip4] WG last call follow-up for vpn traversal problem statement
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
During the WG last call period for
draft-ietf-mobileip-vpn-problem-statement-req-03 I received one comment,
essentially saying that the choice of the words 'in parallel' in section
2.2 was less than optimal. Accordingly, I'd like to get your comments on
the following change (in the section title and first paragraph):
FROM:
2.2 VPN Gateway and MIPv4 HA(s) in parallel
A MIPv4 HA is deployed in parallel with the VPN gateway, and it is
directly reachable by MNs inside or outside the Intranet.
..Foreign Network.. .....VPN Domain..(Intranet).....
. . . .
. +----+ +----+ . +----+ +-------+ .
. |MNs | | FA | . | VPN| | Router| .
. |away| | | .<=========>| | | 1..n | .
. +----+ +----+ . | GW | +-------+ .
. . +----+ .
. . +----+ +-------+ +-------+ .
. .<=========>| HA | | CN | | MNs | .
................... | | | 1..n | | home | .
+----+ +-------+ +-------+ .
. .
................................
Figure 2
TO:
2.2 VPN Gateway and MIPv4 HA(s) on the VPN domain border
A MIPv4 HA is deployed on the VPN domain border (e.g. in the DMZ)
together with the VPN gateway, and it is directly reachable by MNs
inside or outside the Intranet.
..Foreign Network.. .....VPN Domain..(Intranet).....
. . . .
. +----+ +----+ . +----+ +-------+ .
. |MNs | | FA | . | VPN| | Router| .
. |away| | | .<=========>| | | 1..n | .
. +----+ +----+ . | GW | +-------+ .
. . +----+ .
. . +----+ +-------+ +-------+ .
. .<=========>| HA | | CN | | MNs | .
................... | | | 1..n | | home | .
+----+ +-------+ +-------+ .
. .
................................
Figure 2
Comments?
Henrik
--
If at first you don't succeed, skydiving is not for you.
_______________________________________________
Mip4 mailing list
Mip4@ietf.org
https://www.ietf.org/mailman/listinfo/mip4
- [Mip4] WG last call follow-up for vpn traversal p… Henrik Levkowetz