Re: MN-ID extension beyong NAI for PMIPv6 (was: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps)
Alexandru Petrescu <alexandru.petrescu@gmail.com> Sun, 25 November 2007 12:53 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 1IwGyr-0006uM-Lp; Sun, 25 Nov 2007 07:53:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwGyp-0006ld-Ii for mext@ietf.org; Sun, 25 Nov 2007 07:52:59 -0500
Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IwGyl-0002BH-ST for mext@ietf.org; Sun, 25 Nov 2007 07:52:59 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-3.tower-128.messagelabs.com!1195995174!7766113!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 30633 invoked from network); 25 Nov 2007 12:52:54 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-3.tower-128.messagelabs.com with SMTP; 25 Nov 2007 12:52:54 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id lAPCqnYm024901; Sun, 25 Nov 2007 05:52:49 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr04.mot.com (8.13.1/Vontu) with SMTP id lAPCqn4Q011621; Sun, 25 Nov 2007 06:52:49 -0600 (CST)
Received: from [127.0.0.1] ([10.129.40.246]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id lAPCqlVt011615; Sun, 25 Nov 2007 06:52:47 -0600 (CST)
Message-ID: <4749701E.3050703@gmail.com>
Date: Sun, 25 Nov 2007 13:52:46 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>
Subject: Re: MN-ID extension beyong NAI for PMIPv6 (was: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps)
References: <60E12A29-9221-4C3A-A4B6-22C1BEC3A02A@it.uc3m.es> <D4AE20519DDD544A98B3AE9235C8A4C2EE2E6E@moe.corp.azairenet.com>
In-Reply-To: <D4AE20519DDD544A98B3AE9235C8A4C2EE2E6E@moe.corp.azairenet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 071124-0, 24/11/2007), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: Julien Laganier <julien.IETF@laposte.net>, 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
Vijay Devarapalli wrote: [...] > 4283bis - There is no draft on this yet, but a need to update > 4283 was identified on the NETLMM mailing list and then > discussed later on the mext mailing list. The update is to > mainly include other subtypes for MN identifier. For example, > the MAC address would be the new subtype. Currently the > document only defines NAI. I mainly agree with that need. I'm not sure however on the interactions with netlmm and pmipv6. The idea about 4283 potential extension (extend MN-ID option to include something else than a NAI) that was developped in the netlmm pmipv6 discussion made a lot of sense to me there. But I'm not following anylonger where is the pmipv6 overall mechanism/vision impacting this. Maybe 4283bissing discussion should be done there? I don't know? Alex > Finally, what happened to > draft-mitsuya-monami6-flow-distribution-policy-04.txt. I > thought this was also going to be adopted as a MONAMI6 WG > document. I might have missed some emails. > > Vijay > >> -----Original Message----- >> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] >> Sent: Friday, November 23, 2007 6:10 AM >> To: mext@ietf.org >> Subject: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps >> >> 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) >> 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 >> > > _______________________________________________ > 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
- RE: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next ste… Vijay Devarapalli
- [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… 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
- [MEXT] RSVP TSPEC for flow-distribution-rules Teco Boot
- 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
- 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 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 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