Re: [Mip4] Status update & Recharter effort

Hi, Peter,

2009/2/12 McCann Peter-A001034 <pete.mccann@motorola.com>

> Hi, all,
>
> Traffic on the list has been light lately so I wanted to
> provide a status update on our existing work items and kick-start
> a discussion on where to take the working group next.
>
> Here is a list of our current work items and status:
>
> draft-ietf-mip4-generic-notification-message-07.txt
>  New version was uploaded on 11/3, in response to comments
>  from WGLC.  On cursory examination, it appears to me that
>  most if not all comments have been addressed.  It would be
>  nice to get confirmation of this from those who had comments
>  back in July/August.  Then we can submit for publication.

I have talked with Ahmad Muhanna, the reply of his email as the below
Sri and Kent's comments also have been replied as well

thanks for your consideration.

-Hui

-----------------------------------------------------------------------------------------------------------
Hi Hui,

Sorry for the late response, I had Monday off!

When the draft was published I went over it. Based on that quick review, I
can say:

1. I have not noticed anything major that needs attention.
2. As an overall comment, I believe that the current draft is written in a
much better way than before.
3. The document is some what long, but I guess there is no issue there.

Regards,
Ahmad
-----------------------------------------------------------------------------------------------------------

>
>
> draft-ietf-mip4-nemov4-dynamic-02.txt
>  We will issue a last call on this soon, but it has lower
>  priority than 2006bis.
>
> draft-ietf-mip4-nemov4-fa-03.txt
>  No interest in continuing.  We will drop this item from our charter.
>
> draft-ietf-mip4-rfc3344bis-07.txt
>  Still working on the shepherd writeup.  Will be submitted for
>  publication soon.
>
> draft-ietf-mip4-udptunnel-mib-01.txt
>  On hold waiting on 2006bis; then we will issue WGLC.
>
> draft-ietf-mip4-rfc2006bis-05.txt
>  Ready for last call.  Will issue soon.
>
> draft-ietf-mip4-dsmipv4-10.txt
>  In RFC Editor's queue.
>
> draft-ietf-mip4-gen-ext-04.txt
>  Ongoing discussion on whether to continue this item (see recharter
>  discussion below).
>
>
> Several new work items have come to our attention over the past
> few meeting cycles.  Here is a partial list of potential work items
> for mip4 going forward.  Please comment on which you would like to
> see and which you think should be excluded.
>
>
> draft-deng-mip4-host-configuration-00.txt
> draft-chakrabarti-mip4-mcbc-03.txt
>  These two items are related, because DHCP uses IP-layer broadcast
>  to deliver DHCPREQUEST messages.  I'd like to propose that we drop
>  the gen-ext draft and add these two.  Comments?
>
> draft-gundavelli-mip4-multiple-tunnel-support-00.txt
>  We've had some good discussion already on the mailing list and this
>  seems like a potentially useful extension.  Comments?
>
> draft-doswald-robert-mip4-btn-fmipv4-00.txt
>  This was presented at IETF-72.  Is there interest in working on it?
>  Other comments?
>
> draft-makela-mip4-nemo-haaro-03.txt
>  This was presented at IETF-70 and it looks like there have been a
> couple
>  of revisions since.  Is there interest in working on it?  Other
> comments?
>
> draft-acee-mip4-bulk-revocation-01.txt
>  This was presented at IETF-70.  Is there interest in working on it?
> Other
>  comments?
>
> draft-yegani-gre-key-extension-03.txt
>  This was presented at IETF-70.  Is there interest in working on it?
> Other
>  comments?
>
>
>
> If I left anything out please speak up.
>
> -Pete
> --
> Mip4 mailing list: Mip4@ietf.org
>    Web interface: https://www.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>