Re: [DMM] WG adoption (was Re: DMM solution space)

[Alper Yegin <[e-mail]>]

Why? Why not make technical progress at every opportunity? 
This extreme serialization and every step overly stretching…. am I the only one having issue with the slow progress?

Alper



On Jul 17, 2014, at 8:22 PM, Jouni Korhonen wrote:

> 
> Lets get the charter approved first.
> 
> - jouni
> 
> 7/17/2014 7:42 PM, Alper Yegin kirjoitti:
>> Hi Jouni,
>> 
>> We cannot have an official approval of the documents,
>> but what we can do is:
>> - check the WG to see if they are willing to accept a document, based on the assumption that the new charter would be approved
>> - if the WG is OK, then when the charter is approved, we can double check on the mailing list and make WG adoption official.
>> 
>> We should progress…
>> 
>> Alper
>> 
>> 
>> On Jul 17, 2014, at 7:03 PM, Jouni Korhonen wrote:
>> 
>>> Alper,
>>> 
>>> The charter text you cite is not approved yet. I-D adoption requests at this point are premature.
>>> 
>>> - Jouni
>>> 
>>> 7/17/2014 9:19 AM, Alper Yegin kirjoitti:
>>>> *
>>>> *
>>>> Folks,
>>>> 
>>>> Let's change gears.
>>>> 
>>>> We'd like to propose draft-yegin-dmm-ondemand-mobility-02 for WG adoption.
>>>> 
>>>> This draft falls under the following deliverable:
>>>> 
>>>> Exposing mobility state to mobile nodes and network nodes:
>>>> _define solutions that allow, for example, mobile nodes to select_
>>>> _        either a care-of address or a home address depending on an_
>>>> _        application' mobility needs_. In order to enable this
>>>>         functionality, the network side control functions and other
>>>>         networking nodes must also be able to exchange appropriate
>>>>         control information, as well as to the mobile nodes and their
>>>>         applications.
>>>> 
>>>> 
>>>> 
>>>> Comments welcome.
>>>> 
>>>> Alper
>>>> 
>>>> 
>>>> 
>>>> Behcet/Fred: I've updated the list with your input.
>>>> *
>>>> *
>>>> *
>>>> *
>>>> *- Per-flow IP address configuration according to mobility needs*
>>>> 
>>>> Apps indicating their mobility needs to the IP stack on the MN, and
>>>> associated IP configuration signaling between the MN and the network.
>>>> 
>>>> draft-bhandari-dhc-class-based-prefix-03
>>>> draft-korhonen-dmm-prefix-properties-00.txt
>>>> draft-yegin-dmm-ondemand-mobility-02
>>>> 
>>>> *- Mobility solution selection *
>>>> 
>>>> MN determining the type of mobility solution(s) it'd apply to a given flow.
>>>> 
>>>> draft-yegin-ip-mobility-orchestrator-00
>>>> 
>>>> *- IP anchor selection*
>>>> 
>>>> MN selecting the IP anchor node after it decides to use IP anchoring
>>>> (whether in the access network or the core network).
>>>> 
>>>> draft-aliahmad-dmm-anchor-selection-00.txt
>>>> 
>>>> 
>>>> *- Access network anchoring*
>>>> 
>>>> Anchoring IP address within the access network using IP-in-IP tunneling.
>>>> 
>>>> draft-bernardos-dmm-cmip-01
>>>> draft-bernardos-dmm-pmip-03
>>>> draft-bernardos-dmm-distributed-anchoring-04
>>>> draft-chan-dmm-enhanced-mobility-anchoring-00
>>>> draft-sarikaya-dmm-for-wifi-00.txt
>>>> draft-seite-dmm-dma-07.txt
>>>> draft-xuan-dmm-nemo-dmm-02.txt
>>>> 
>>>> 
>>>> *- Corresponding node/network anchoring*
>>>> 
>>>> Anchoring IP address on the Corresponding Node or Corresponding Network.
>>>> 
>>>> Mobile IPv6 route optimization
>>>> draft-yegin-dmm-cnet-homing-02
>>>> draft-xiong-dmm-ip-reachability-01
>>>> draft-templin-aerolink-29
>>>> 
>>>> *- Host-route based intra-domain solutions*
>>>> 
>>>> Non-tunneling solutions.
>>>> 
>>>> draft-chan-dmm-enhanced-mobility-anchoring-00
>>>> draft-matsushima-stateless-uplane-vepc-02
>>>> draft-mccann-dmm-flatarch-00
>>>> draft-sarikaya-dmm-for-wifi-00.txt
>>>> 
>>>> 
>>>> _______________________________________________
>>>> dmm mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/dmm
>>>> 
>>