Re: [Mipshop] MIPSHOP Re-chartering
Vijay Devarapalli <vijay.devarapalli@azairenet.com> Tue, 19 February 2008 20:14 UTC
Return-Path: <mipshop-bounces@ietf.org>
X-Original-To: ietfarch-mipshop-archive@core3.amsl.com
Delivered-To: ietfarch-mipshop-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2C0328C600; Tue, 19 Feb 2008 12:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.159
X-Spam-Level:
X-Spam-Status: No, score=-1.159 tagged_above=-999 required=5 tests=[AWL=-0.722, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1o4YRwzd3YU; Tue, 19 Feb 2008 12:14:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 141293A6A47; Tue, 19 Feb 2008 12:14:07 -0800 (PST)
X-Original-To: mipshop@core3.amsl.com
Delivered-To: mipshop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D62928C5C3 for <mipshop@core3.amsl.com>; Tue, 19 Feb 2008 12:14:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JeNDzFaRjRZK for <mipshop@core3.amsl.com>; Tue, 19 Feb 2008 12:14:04 -0800 (PST)
Received: from mail2.azairenet.com (mail2.azairenet.com [207.47.15.6]) by core3.amsl.com (Postfix) with ESMTP id 5A3A03A6B2B for <mipshop@ietf.org>; Tue, 19 Feb 2008 12:14:04 -0800 (PST)
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 Feb 2008 12:14:01 -0800
Message-ID: <47BB3889.4030507@azairenet.com>
Date: Tue, 19 Feb 2008 12:14:01 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Wassim Haddad <whaddad@tcs.hut.fi>
References: <47B0E108.2050208@azairenet.com> <Pine.LNX.4.64.0802190111410.15123@rhea.tcs.hut.fi>
In-Reply-To: <Pine.LNX.4.64.0802190111410.15123@rhea.tcs.hut.fi>
X-OriginalArrivalTime: 19 Feb 2008 20:14:01.0927 (UTC) FILETIME=[F7E07D70:01C87333]
Cc: mipshop@ietf.org
Subject: Re: [Mipshop] MIPSHOP Re-chartering
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <mipshop.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mipshop-bounces@ietf.org
Errors-To: mipshop-bounces@ietf.org
Wassim Haddad wrote: > Hello Vijay, > > I don't know how the selection of new ietms have been made, Simple. :) The DHCP and DNS extensions to enable MIH server discovery are normative dependencies for the MIH solution document we have. At the last IETF meeting, folks seemed to be comfortable with having the MIH solution split across three documents. Using FMIPv6 for PMIPv6 is a new topic. There seems to be interest in using FMIPv6 to tunnel packets between MAGs. The draft also on the 3GPP2-IETF dependency list (that means 3GPP2 is planning to use the mechanism described in the draft). The p2p link prefix management for FMIPv6 and using AAA-based infrastructure for FMIPv6 key management have been discussed quite a bit in MIPSHOP WG in the past. Both are considered necessary for FMIPv6. > but I would > like to add suggest adding further work on RFC4866 as it has been described > in draft-haddad-mext-netflood-defense-00. Sure, but I would like to see some interest from other folks. There hasn't been much discussion on draft-haddad-mext-netflood-defense-00. Vijay > Note that the suggested work (as > described in the draft) is NOT optional as RFC4866 needs further work which > must be inline with the optimizations brought to MIPv6 RO mode. > > > Regards, > > Wassim H. > > > On Mon, 11 Feb 2008, Vijay Devarapalli wrote: > >> Hello folks, >> >> Stefano and I want to initiate some discussion on re-chartering. >> We have completed most of the work items that we have in our >> charter (the documents are either with the IESG or about to be >> WG last called). >> >> For the revised charter, the following new items have been proposed. >> >> 1. DHCP extensions for discovering MIH information server. This >> is described in >> http://www.ietf.org/internet-drafts/draft-bajko-mos-dhcp-options-02.txt >> >> 2. DNS extensions for discovering MIH information servers. This >> is described in >> http://www.ietf.org/internet-drafts/draft-bajko-mos-dns-discovery-01.txt >> >> The current working group document >> draft-ietf-mipshop-mstp-solution has dependencies on the two >> documents above. >> >> 3. Using FMIPv6 with PMIPv6. This is described in >> http://www.ietf.org/internet-drafts/draft-yokota-mipshop-pfmipv6-01.txt >> >> 4. Prefix Management for FMIPv6 use with p2p links. This is >> described in >> http://tools.ietf.org/id/draft-xia-mipshop-fmip-ptp-01.txt >> >> 5. AAA based handover keys for FMIPv6. The base document for this >> is yet to be resolved. A separate email will be sent on this. >> >> We would like to hear some comments on the proposed work items >> for the new charter. >> >> Vijay >> >> >> _______________________________________________ >> Mipshop mailing list >> Mipshop@ietf.org >> http://www.ietf.org/mailman/listinfo/mipshop >> >> _______________________________________________ Mipshop mailing list Mipshop@ietf.org http://www.ietf.org/mailman/listinfo/mipshop
- Re: [Mipshop] MIPSHOP Re-chartering Wassim Haddad
- [Mipshop] MIPSHOP Re-chartering Vijay Devarapalli
- Re: [Mipshop] MIPSHOP Re-chartering Wassim Haddad
- Re: [Mipshop] MIPSHOP Re-chartering Vijay Devarapalli