Re: rechartering

Alper Yegin <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <[email protected]>
Hello Jouni, folks,

Here are few more comments:

      DMM can be used to realise such a distributed deployment
      model, by distributing forwarding functions at optimal location; for
      example, closer either to the mobile user or the corresponding node.

We had already talked about that: s/mobile user/mobile node. 



     o Enhanced gateway & mobility anchor selection and re-selection: define 
        protocol solutions for a gateway and mobility anchor selection that
        go beyond what has been, for example, described in RFC 6097. The
        solution should also define a mechanism for anchor re-selection that allow
        preserving ongoing mobility sessions in a single administrative domain.
       
      o Forwarding path and signalling management: the mobility agent that handles
        the mobility signalling interacts with the network elements in the DMM network
        for managing the forwarding state associated with a mobile node's IP traffic.
        These two functions may or may not be collocated. Furthermore, the forwarding
        state may also be distributed into multiple network elements instead of a
        single anchor like network element. Define required protocol extensions to
        allow described forwarding path and signalling management.

GW selection and data-path management signaling may be defined in the same "solution" document. In at least some cases these are provided as part of the same solution set. They may also be separable, maybe, but we shall not be hung up on producing separate documents for these… The solution discussions will guide us… (no specific change required on the above text, more on this below…)


The milestones are missing any document that defines the "data-path management signaling" (what's mentioned above). And like I said before, that's "the"  product of this WG IMO. It'd of course be supplemented by GW selection and mobility state exposure bits to complete the picture.

Let's add another milestone:

Nov 2014 - Submit 'Forwarding path and signaling management' as a working group document. To be Proposed Standard.
Mar 2015 - Submit 'Forwarding path and signaling management' submitted to the IESG. To be Proposed Standard.


Cheers,

Alper















On May 27, 2014, at 11:50 AM, Jouni Korhonen wrote:

> 
> Now that the gap analysis I-D is almost on the stage of leaving the WG and the requirements I-D has almost completed IESG, it would be time to return to the rechartering topic.
> 
> First, the latest revision can be found at:
> https://github.com/jounikor/dmm-re-charter
> 
> Second, have a look at it. There are few changes proposed by Alper eons ago and corrected milestones pointed by Behcet.
> 
> Third, let us get this finally done..
> 
> - Jouni
> 
> 4/22/2014 3:55 PM, Jouni Korhonen kirjoitti:
>> Folks,
>> 
>> Sorry for letting this topic to rot in a dark for the couple of last
>> weeks. I'll crank out a revision shortly..
>> 
>> - Jouni & Dapeng
> 
> _______________________________________________
> dmm mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dmm

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.