Re: [Mip6] Review of draft-ietf-mip6-firewalls-00.txt (with referenceto draft-chen-mip6-gprs-02.txt)

"James Kempf" <kempf@docomolabs-usa.com> Tue, 26 October 2004 20:29 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 QAA13700 for <mip6-web-archive@ietf.org>; Tue, 26 Oct 2004 16:29:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMYA1-00057r-Nb for mip6-web-archive@ietf.org; Tue, 26 Oct 2004 16:43:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMXZQ-0000dj-LP; Tue, 26 Oct 2004 16:05:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMXRq-0005BR-M0 for mip6@megatron.ietf.org; Tue, 26 Oct 2004 15:57:38 -0400
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 PAA08908 for <mip6@ietf.org>; Tue, 26 Oct 2004 15:57:36 -0400 (EDT)
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMXfX-0003mI-OI for mip6@ietf.org; Tue, 26 Oct 2004 16:11:49 -0400
Message-ID: <01da01c4bb96$27602f40$656115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: Franck.Le@nokia.com, mip6@ietf.org
References: <57A26D272F67A743952F6B4371B8F811017CA9C0@daebe007.americas.nokia.com>
Subject: Re: [Mip6] Review of draft-ietf-mip6-firewalls-00.txt (with referenceto draft-chen-mip6-gprs-02.txt)
Date: Tue, 26 Oct 2004 12:58:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

Franck,

>> jak>>> I'm not clear what you mean. Is this document intended to be a
>> comprehensive exploration of the problems involved in
>> firewall interaction
>> with MIPv6 or not? If not, then we clearly need another document that
>> explores the problems this one doesn't.
>
>The initial intent of the document was not to list all the possible
problems between the Mobile IPv6 protocol and >firewalls, but to describe
the main ones. However we could include the scenarios you just described in
the next version > of the draft.

Yes, I think that would be helpful. Especially if the draft ends up
generating some requirements for other WGs, for example, to allow
communication with the firewall.

            jak




_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6