RE: [Mip4] Document Status Update

"Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com> Wed, 12 October 2005 22:39 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPpFz-00080T-Um; Wed, 12 Oct 2005 18:39:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPpFy-0007yo-2z for mip4@megatron.ietf.org; Wed, 12 Oct 2005 18:39:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09737 for <mip4@ietf.org>; Wed, 12 Oct 2005 18:39:26 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPpQL-0007SS-HB for mip4@ietf.org; Wed, 12 Oct 2005 18:50:15 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9CMowSb020895 for <mip4@ietf.org>; Wed, 12 Oct 2005 15:50:58 -0700 (MST)
Received: from de01exm70.ds.mot.com (de01exm70.am.mot.com [10.176.8.26]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9CMkvJs004190 for <mip4@ietf.org>; Wed, 12 Oct 2005 17:46:57 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Document Status Update
Date: Wed, 12 Oct 2005 18:39:11 -0400
Message-ID: <C7ED80CD916C5B4F8069B486F5DC547918FCC5@de01exm70.ds.mot.com>
Thread-Topic: [Mip4] Document Status Update
Thread-Index: AcXLVb3/XhckOik+R/q3OFu+QVZ8uQEJ6QPA
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: Pete McCann <mccap@lucent.com>, mip4@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: quoted-printable
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>, "Kent Leung \\\\(kleung\\\\)" <kleung@cisco.com>, "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>, Avi Lior <avi@bridgewatersystems.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

I knew I saw this somewhere, turned out it was the next email in my
inbox.
It seems that you guys need the mip4 named 00, which means we have one
less week to deal with changes, I am guessing we may not be able to
incorporate all changes into mip4-00 one..

Madjid 

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Pete McCann
Sent: Friday, October 07, 2005 10:41 AM
To: mip4@ietf.org
Subject: [Mip4] Document Status Update


Note there will be a very short amount of time between the October 13th
IESG meeting (IESG hopefully will approve our new charter) and the
October 17th -00 draft cut-off.  Authors of drafts relevant to the new
work items, please be ready to submit appropriate mip4-named version -00
drafts in this window.

-Pete


Pete McCann writes:
 >
 > With the rechartering effort almost completed (the charter is on the
> agenda for the October 13 IESG meeting), we thought it was a good time
> to update everyone on the status of our documents.  This helps  >
everyone understand the work that remains to be done.
 >
 >
 >
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-hando
ffs-v4-11.txt
 > Just re-submitted by Karim, ready to go to RFC Editor  >  >
http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3012bis-04.txt
 > Need to decide whether to fork off the Generalized Mobile IP  >
Authentication Extension as a separate draft.
 >
 >
http://www.ietf.org/internet-drafts/draft-ietf-mip4-dynamic-assignment-0
5.txt
 > Waiting on Kent to update nits.
 >
 > http://www.ietf.org/internet-drafts/draft-ietf-mip4-faerr-02.txt
 > Still in IETF Last call.
 >
 > http://www.ietf.org/internet-drafts/draft-ietf-mip4-reg-tunnel-00.txt
 > Need to decide whether to include the appendix or not.
 >
 > >From our new milestones:
 > 
 > Dec 05 	Revised MIB for MIPv4 to IESG
 > Review done, revision in progress.
 > 
 > Sep 05 	Revised MIPv4 specification to IESG for Draft Standard
 > Draft for 3344bis has expired.  Update needed based on latest
consensus.
 > 
 > Dec 05 	Revised rfc2794bis (NAI extension specification) to the
IESG
 > No draft yet.
 > 
 > Jan 06 	MIPv4 Mobike interaction BCP to the IESG
 > draft-devarapalli-mip4-mobike-connectivity-00.txt is relevant.
 > 
 > Feb 06 	Generic Strings for MIPv4 to the IESG
 > draft-sastry-mip4-string-extension-01.txt is relevant.
 > 
 > Mar 06 	RADIUS Extensions for MIPv4 to the RADEXT WG for comment
 > draft-nakhjiri-radius-mip4-01.txt is relevant.
 > 
 > Mar 06 	FMIPv4 to the IESG
 > draft-koodli-fmipv4-00.txt has expired.
 > 
 > Jun 06 	RADIUS Extensions for MIPv4 to the IESG
 > See above.
 > 
 > Aug 06 	MIPv4 Extension for Configuration Options to the IESG
 > draft-bharatia-mip4-gen-ext-00.txt is relevant.


--
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/