Re: [MEXT] NEMO MNP in RA Informational/Experimental item?

[Thierry Ernst <[e-mail]>]

Hi Julien, Alex,

It depends where you stand from. As pointed out by Alex, in the previous 
MEXT charter there is an Automotive requirements WG item and the 
associated draft
draft-mext-nemo-ro-automotive-req (expired, but authors are on the way 
to update it -- also note that ETSI and ISO are going their way in 
specifying standards that will at some time require discussion with 
IETF), "which mentions vehicle-to-vehicle V2V
requirements, to which the MNP-in-RA is a potential solution.  That is a
potential reason for bringing MNP-in-RA in MEXT.".

Of course, should such a solution for a MEXT draft requirement by 
chosen, one might wonder which IETF WG is the best and MEXT might not, 
or might.

On this specific point I consider that a BOF is premature.  First, 
draft-mext-nemo-ro-automotive-req must be updated, and a sufficient 
number of people be interested in the solution. Now, ETSI and ISO are 
working on non-IP issues, and only later will they be concerned about IP 
solutions, including MR-MR RO. Things could change quickly, though I 
don't see a window in 2010.

Regards,
Thierry.



On 25/08/10 01:07, Laganier, Julien wrote:
> Hi Alex,
>
> IMHO this does not fit in the MEXT WG since this is orthogonal to the Mobile IPv6 suite of protocols (i.e., it doesn't build on, or extend.)
>
> --julien
>
>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]] On Behalf Of
>> Alexandru Petrescu
>> Sent: Wednesday, August 04, 2010 1:15 AM
>> To: [e-mail]
>> Subject: Re: [MEXT] NEMO MNP in RA Informational/Experimental item?
>> (was: new charter proposal)
>>
>> Hi Julien, WG,
>>
>> I would like to discuss addition of an item related to moving network
>> to
>> moving network communications.  Two drafts have been discussed in the
>> WG
>> recently, although probably more review is needed:
>>
>>         draft-jhlee-mext-mnpp-00.txt
>>         draft-petrescu-autoconf-ra-based-routing-00.txt
>>
>> The intended status of the first reads Informational, and of the second
>> should also be Informational, or Experimental (the current tag is wrong
>> in the draft).
>>
>> Router Advertisement extensions are used to exchange routes between two
>> moving networks.  When infrastructure Internet is not available, MIP6
>> NEMO is not triggered.
>>
>> AUTOCONF WG discussed the second draft a little bit, but I don't think
>> it will be Chartered there because that is going to be mostly about
>> DHCP.
>>
>> What do you Julien, group, think?
>>
>> Alex
>>
>> Le 28/07/2010 14:36, Laganier, Julien a écrit :
>>> Folks,
>>>
>>> For your information, below is the recharter proposal that we've put
>>>   together and forwarded to IESG.
>>>
>>> --julien
>>>
>>> Mobile IPv6 specifies routing support which permits an IPv6 host to
>>> continue using its home address as it moves around the Internet,
>>> enabling continuity of sessions. Mobile IPv6 supports transparency
>>> above the IP layer, including maintenance of active transport level
>>> sessions. In addition, network mobility (NEMO) mechanisms built on
>>> top of Mobile IPv6 allow managing the mobility of an entire network,
>>>   as it changes its point of attachment to the Internet. The base
>>> specifications consist of:
>>>
>>> o RFC 3775 (Mobile IPv6) o RFC 3963 (NEMO) o RFC 4877 (Mobile IPv6
>>> Operation with IKEv2) o RFC 5555 (Dual Stack Mobile IPv6) o RFC 5648
>>>   (Multiple Care-of Addresses Registration) o RFC 5846 (Binding
>>> Revocation) o RFC-to-be (Flow Binding Policy Transport and Flow
>>> Binding Policy Format)
>>>
>>> The MEXT Working Group continues the work of the former MIP6, NEMO,
>>> and MONAMI6 Working Groups.
>>>
>>> The primary goal of MEXT will be to enhance base IPv6 mobility by
>>> continuing work on developments that are required for wide-scale
>>> deployments and specific deployment scenarios. Additionally, the
>>> working group will ensure that any issues identified by
>>> implementation and interoperability experience are addressed, and
>>> that the base specifications are maintained. The group will also
>>> produce informational documentation, such as design rationale
>>> documents or description of specific issues within the protocol.
>>>
>>> The MEXT WG will also explore experimental alternative security
>>> mechanisms. The security mechanism specified in the existing standard
>>> track RFCs (RFC3775bis, RFC4877) remains the mandatory to implement
>>> mechanism that guarantees interoperability between different
>>> implementations. The MEXT WG is chartered to deliver one or more
>>> experimental alternative mechanisms. All the alternative solutions
>>> will be published as experimental RFCs.
>>>
>>> Work items related to base specification maintenance include: Create
>>>   and maintain issue lists that are generated on the basis of
>>> implementation and interoperability experience. Address specific
>>> issues with specific updates or revisions of the base specification.
>>>   One specific area of concern that should be analyzed and addressed
>>> relates to multilink subnets.
>>>
>>>
>>>
>>> Goals and Milestones
>>>
>>> Done 	Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
>>> publication as a Proposed Standard Done 	Submit I-D 'Mobile IPv6
>>> Experimental Allocations' to IESG for publication as a Proposed
>>> Standard Done 	Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG
>>>   for publication as a Proposed Standard. Done 	Submit I-D
>> 'Motivation
>>>   for Authentication I-D' to IESG for publication as Informational.
>>> Done 	Submit Multiple CoA Registration to IESG Done 	Submit I-D
>>> 'Goals for AAA HA Interface' to IESG for publication as
>>> Informational. Done 	Submit -00 draft on Route Optimization Needs
>> for
>>> Automobile and Highway Deployments Done 	Submit -00 draft on
>> Route
>>> Optimization Needs for Aircraft and Spacecraft Deployments Dec 2010
>>> Submit the final doc on Prefix Delegation for NEMO to the IESG, for
>>> Proposed Standard Done 	Submit I-D 'Mobility Header Home Agent
>> Switch
>>> Message' to IESG for publication as a Proposed Standard Done Submit
>>> final doc on Route Optimization Needs for Aircraft and Spacecraft
>>> Deployments, for Informational Jun 2008 	Submit the I-D 'RADIUS
>>> Mobile IPv6 Support' to IESG for publication as a proposed standard.
>>> Done 	Submit 00 draft on Binding Revocation Jan 2010 Submit I-D
>>> 'Mobile IPv6 Operation with Firewalls' to IESG for publication as
>>> Informational. Done 	Submit the final doc on MIB for NEMO Basic
>>> Support to the IESG, for Proposed Standard Done 	Submit
>> Flow/binding
>>> policy transport to IESG, for Proposed Standard Done Submit
>>> Flow/binding policy format to IESG, for Proposed Standard Done Submit
>>> draft on Binding Revocation to IESG Dec 2010 	Submit I-D(s) related
>>> to specific updates and corrections of RFC 3775 to IESG for
>>> publication as Proposed Standard. Jan 2011 	Submit I-D 'Home agent
>>> reliability' to IESG for publication as a Proposed Standard. Aug 2011
>>> Submit I-Ds on alternative security mechanisms to the IESG for
>>> publication as experimental
>>>
>>> _______________________________________________ MEXT mailing list
>>> [e-mail] https://www.ietf.org/mailman/listinfo/mext
>>>
>>
>> _______________________________________________
>> MEXT mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/mext
> _______________________________________________
> MEXT mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mext