Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 23 November 2007 14:23 UTC
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvZRB-0001eO-S4; Fri, 23 Nov 2007 09:23:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvZRA-0001e8-4w for mext@ietf.org; Fri, 23 Nov 2007 09:23:20 -0500
Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IvZR6-0001dB-QV for mext@ietf.org; Fri, 23 Nov 2007 09:23:20 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-12.tower-153.messagelabs.com!1195827795!4962029!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.101]
Received: (qmail 11128 invoked from network); 23 Nov 2007 14:23:15 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-12.tower-153.messagelabs.com with SMTP; 23 Nov 2007 14:23:15 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id lANENFJs020977; Fri, 23 Nov 2007 07:23:15 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id lANENEQY007324; Fri, 23 Nov 2007 08:23:14 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id lANENCZD007306; Fri, 23 Nov 2007 08:23:13 -0600 (CST)
Message-ID: <4746E24F.1030008@gmail.com>
Date: Fri, 23 Nov 2007 15:23:11 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps
References: <60E12A29-9221-4C3A-A4B6-22C1BEC3A02A@it.uc3m.es>
In-Reply-To: <60E12A29-9221-4C3A-A4B6-22C1BEC3A02A@it.uc3m.es>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 071122-0, 22/11/2007), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: mext@ietf.org
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org
marcelo bagnulo braun wrote: > Folks, > > We have been discussing with our AD the way forward w.r.t. WG drafts > inherited from the previous WGs (MIP6, NEMO and MONAMI6). > > We have grouped drafts into five categories and decided about the > actions to be taken for drafts of each category: > > --------------------------------------------------------------------- > > Cat. I: former WG drafts submitted to IESG already > > Action: Address possible IESG Comments/Discusses as they surface. > > I-Ds: draft-ietf-mip6-bootstrapping-integrated-dhc-05 > draft-ietf-mip6-cn-ipsec-06 > draft-ietf-mip6-ha-switch-05 > draft-ietf-mip6-hiopt-08 > draft-ietf-mip6-whyauthdataoption-04 > draft-ietf-mip6-experimental-messages-03 > draft-ietf-mip6-vsm-03 > > ---------------------------------------------------------------------- > > Cat. II: former WG drafts corresponding to MEXT charter work items > > Action: - MEXT to adopt drafts as WG drafts > - authors to submit new versions if/when needed as > draft-ietf-mext-... > > I-Ds (MEXT work item): draft-ietf-nemo-mib-03 work item (B.3) > draft-ietf-nemo-prefix-delegation-02 (B.3) In addition, I'd like to request inclusion of draft-ietf-nemo-dhcpv6-pd which although expired I find it relevant (http://tools.ietf.org/id/draft-ietf-nemo-dhcpv6-pd-02.txt) . On and off it's been forgotten expired and re-activated. I'd suggest a deadline in the MEXT timeline as well. We're currently discussing publicly on the MEXT list about how to progress the two NEMO documents of prefix allocation. What do you think? Thanks, Alex > draft-ietf-monami6-mipv6-analysis-04 (A.3) > draft-ietf-monami6-multihoming-motivation-scenario-02 (A.3) > draft-ietf-monami6-multiplecoa-04 (A.3) > draft-ietf-mip6-hareliability-03 (A.2) > draft-ietf-mip6-nemo-v4traversal-05 (A.1) > draft-ietf-mip6-radius-02 (A.6) > > ---------------------------------------------------------------------- > > Cat. III: individual drafts corresponding to MEXT charter work items > that were accepted as former WG drafts but never submitted as such. > > Action: - MEXT to adopt drafts as WG drafts as long as the authors > follow the > conditions requested by the respective WG at the moment of > acceptancy > - authors to submit new versions if/when needed as > draft-ietf-mext-... > > I-Ds (MEXT work item): draft-eddy-nemo-aero-reqs-01 (A.5) > draft-soliman-monami6-flow-binding-04 (A.3) > > ---------------------------------------------------------------------- > > Cat. IV: individual drafts corresponding to MEXT charter work items > that were *conditionally* accepted as former WG drafts. > > Action: - authors to update drafts so that they fullfills conditions. > > I-Ds (MEXT work item): draft-baldessari-c2ccc-nemo-req-01 (A.5) > > ---------------------------------------------------------------------- > > Cat. V: former WG drafts without corresponding MEXT charter work item > > Action: - MEXT to include this drafts as part of the rechartering > discussion. > > I-Ds: draft-ietf-mip6-rfc4285bis-01 > draft-ietf-mip6-generic-notification-message-00 > > ------------------------------------------------------------------------ > > Comments? > > Cheers, > > -- > Julien and Marcelo, MEXT chairs > > > _______________________________________________ > MEXT mailing list > MEXT@ietf.org > https://www1.ietf.org/mailman/listinfo/mext > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ MEXT mailing list MEXT@ietf.org https://www1.ietf.org/mailman/listinfo/mext
- [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps marcelo bagnulo braun
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Alexandru Petrescu
- RE: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Vijay Devarapalli
- RE: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Vijay Devarapalli
- RE: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Vijay Devarapalli
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… RYUJI WAKIKAWA
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Jari Arkko
- Potential recharter items (was Re: [MEXT] MIP6/NE… marcelo bagnulo braun
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Behcet Sarikaya
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… T.J. Kniveton
- Re: MN-ID extension beyong NAI for PMIPv6 (was: [… Alexandru Petrescu
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Alexandru Petrescu
- RE: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Giaretta, Gerardo
- Re: Potential recharter items (was Re: [MEXT] MIP… George Tsirtsis
- [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… marcelo bagnulo braun
- RE: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Roberto Baldessari
- Re: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… marcelo bagnulo braun
- RE: [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- RE: [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- RE: [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- RE: [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Kazuyuki Tasaka
- RE: [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Kazuyuki Tasaka
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules George Tsirtsis
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Hannes Tschofenig
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Xiaoming Fu
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Martin Stiemerling
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Martin Stiemerling
- Re: [MEXT] RSVP TSPEC for flow-distribution-rules Romain KUNTZ
- RE: [MEXT] RSVP TSPEC for flow-distribution-rules Hesham Soliman