Ryuji,
On Mar 20, 2014, at 4:55 PM, Ryuji Wakikawa <[email protected]> wrote: > Jouni > > It’s good to see some room for non-MIP based solution in DMM;-) > > One clarification, the charter said following > > "Specifically, when solutions are not > based on IP mobility protocols, the DMM workingvgroup shall cooperate > with other IETF working groups working on other technologies that > might allow the mobility of an end host. These working groups include > but are not limited to I2rs, Lisp, and Forces." > > If we need to extend existing non-MIP protocols, it is reasonable to > do extension in the working group owning the protocol. I agree on the charter. > > However, DMM should work on documenting “how to use it”. The document should > be informational or experimental. Is this scope of DMM? In a case some DMMish feature depends on a work done by other WG and it is used then in a DMM specific way, that should be documented in DMM document. This is specifically the case if the feature or extension done in other WG can be used also for other than DMM purposes. > > btw, you may add IDR in the listed of working group. Ok. - Jouni > > thanks > ryuji > > > 2014/03/17 午後3:41、Jouni Korhonen <[email protected]> のメール： > >> Folks, >> >> I have updated the charter draft text slightly: >> https://github.com/jounikor/dmm-re-charter/blob/master/recharter_draft.txt >> >> Basically: >> >> Added Sri's comment on PMIPv6 maintenance. >> Added Alper's comment of location of mobility functions. >> Added links to other IETF WGs on possible mobility enabling technologies. >> Added a comment that virtualised network functions are in scope. >> >> - Jouni >> >> _______________________________________________ >> dmm mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/dmm > _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
