Re: [Mip6] Merged WG charter

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Tue, 19 June 2007 16:42 UTC

Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0gmg-0006v6-1x; Tue, 19 Jun 2007 12:42:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0gme-0006uz-HM for mip6@ietf.org; Tue, 19 Jun 2007 12:42:24 -0400
Received: from mail2.azairenet.com ([207.47.15.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0gmd-0006xO-7D for mip6@ietf.org; Tue, 19 Jun 2007 12:42:24 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jun 2007 09:42:22 -0700
Message-ID: <4678076E.4020204@azairenet.com>
Date: Tue, 19 Jun 2007 09:42:22 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] Merged WG charter
References: <5vrfma$1hlcng@smtp06.syd.iprimus.net.au> <4677F7D8.9080104@piuha.net>
In-Reply-To: <4677F7D8.9080104@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jun 2007 16:42:22.0487 (UTC) FILETIME=[CF36FA70:01C7B290]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: 'Mobile IPv6 Mailing List' <mip6@ietf.org>
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>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:

>>  > (A.4) Work on solutions to deal with firewalls and the problems that
>>  >       firewalls cause as identified in RFC 4487.
>>
>> => Hmm. I have some doubts about the "work on a solution" part. We need to
>> assess those problems and decide whether a solution is needed. If needed
>> then we should produce one. We discussed these issues in the FW DT and it's
>> not clear, at least to me, that a solution is a certainty.
> 
> Ok. But again, I don't want to hold a real rechartering discussion and most
> of the work items should just stay, unless they either have been completed
> or have something obviously wrong with them.
> 
> I do agree with your principle, though. It could be that we can leave the
> text as is, and simply handle this as a part of the management of the
> group.

Well, there are issues. We have published a document on this.
http://www.ietf.org/rfc/rfc4487.txt

If we conclude that there is no need for specifying anything
new, we would at least need a BCP recommending some firewall
configuration for MIPv6.

Vijay

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