Re: [Mipshop] MIPSHOP Re-chartering

Hello Vijay,

I don't know how the selection of new ietms have been made, but I would
like to add suggest adding further work on RFC4866 as it has been described
in draft-haddad-mext-netflood-defense-00. 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