> This document has been sitting around for 4 years indeed, but it has been > presented to the WG for discussion only during IETF 96 (Summer 2016). > https://www.ietf.org/proceedings/96/lisp.html > The presentation was only 2 slides long and had no comments (you can check > the minutes).
Because it is that simple and nothing has changed in the document. > No discussions have being going on ever since, neither in the mailing list > nor during face to face meetings. Because people support it. You saw that on the mailing list. Joel just had recent comments, and they surfaced because of my initial email. He wanted clarity in the document. So I will make another revision. > You have all rights to ask for adoption, but not to formally open the call > for adoption. I don't have authority to formally do anything. I sent an email *requesting* adoption. I cannot mandate it as an individual. You chairs know that. > IETF procedures want that is up to the chairs to open the adoption call. > Even so, your _informal_ call for adoption has raised 2 supports and 1 > objection. There were more than 2 supports emails. And you said "formal" above and now you said "informal". So the labels are not helpful. > At this stage there are no sufficient elements that allow the chairs to > declare consensus for adoption. Well I will let the working group speak. So I would request the group to post on this list and show even more support. > What I would suggest is: > - to continue the technical discussion on the mailing list > - the more the better Agree. But how much is enough is the question. > - present the document during one of the next meetings Sure. > - Please focus on why this is needed from a technical standpoint. Just > stating I use it in another document is not a technical reason. The drafts that reference it provide technical material. > - If at that point there is interest from the WG, we will make the > call for adoption. There is interest. I don't know what more you want. > I encourage you all to continue the discussion. And I encourage you chairs to be open minded. And allow the working group to be creative and productive. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
