I think the problem is that RFC6830bis has too narrow a definition of “data-plane”. I believe you think it as the sole purpose of forwarding data packets. I view it as the “nodes that make up the data-plane” should be part of that.
Having said that, the Deployment section is saying where xTRs go and why. The Mobility section is saying where EIDs and RLOCs are and off often the can change. Both of these sections has nothing to do with control-plane and hence they shouldn’t go in RFC6833bis but should not go into a OAM document either. The Traceroute section is probably the only section that should go in a document titled “OAM”. But what is the cost of putting just this section in a document? The cost and time we have spent on this topic has already exceeded the benefit. Dino > On Mar 20, 2018, at 10:35 AM, Luigi Iannone <[email protected]> wrote: > > If the items are unrelated why should they go to 2 different document, > knowing that are not related to the data-plane neither ? > > L. > > >> On 20 Mar 2018, at 14:58, Reshad Rahman (rrahman) <[email protected]> wrote: >> >> I don't have a name suggestion either, but I do find it odd having a >> document with these 3 seemingly unrelated items (mobility seems to be the >> odd one out). So I would be in favour of proposal from Albert below. >> >> Regards, >> Reshad. >> >> On 2018-03-19, 4:53 PM, "lisp on behalf of Dino Farinacci" >> <[email protected] on behalf of [email protected]> wrote: >> >>> The suggested name is “LISP Mobility, Deployment and Traceroute >>> considerations”. >>> >>> The chairs would like to hear from the mailing list if there is any >>> objection or you have a better name to suggest. >> >> I don’t have a name suggestion (for the 3 items included in one document) >> but I would like to support an idea that Albert provided after the meeting >> today. >> >> He suggested to put the Mobility sections in an Appendix in RFC6830bis and >> put Deployment and Traceroute considerations in a document that now can be >> called “draft-ietf-lisp-oam”. >> >> Wonder how people would feel about that? >> >> Dino >> >> _______________________________________________ >> lisp mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/lisp >> >> > _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
