> On Sep 1, 2015:1:58 PM, at 1:58 PM, Juergen Schoenwaelder > <j.schoenwael...@jacobs-university.de> wrote: > > On Tue, Sep 01, 2015 at 06:45:55PM +0100, Giles Heron wrote: >> On 1 Sep 2015, at 18:30, Juergen Schoenwaelder >> <j.schoenwael...@jacobs-university.de> wrote: >>> >>> On Tue, Sep 01, 2015 at 05:58:59PM +0100, Giles Heron wrote: >>>> On 1 Sep 2015, at 17:47, Juergen Schoenwaelder >>>> <j.schoenwael...@jacobs-university.de> wrote: >>>>> >>>>> I suggest people write I-Ds if they have any far reaching ideas. >>>> >>>> I think GitHub would be better. The overhead is much lower than writing a >>>> draft. >>>> >>> >>> IETF processes usually starts with ideas presented in I-Ds. I do not >>> care much which tools people use to produce I-Ds. >> >> sure, that is the process in general. But I’m unconvinced that it’s the >> right way to proceed with YANG. E.g. we used a numbered of issues for YANG >> 1.1. So why not a numbered list of suggestions for YANG 2.0? >> > > The formal answer is that the WG is charted to do YANG 1.1 and not > 2.0. The other answer is that (a) collecting issues is easy, (b) > finding agreement on issues is difficult, (c) getting the final text > written and _all the details that pop up worked out_ is very hard > work. Unfortunately, you see many people working on (a), less people > on (b) and finally very few doing (c). > > /js
Juergen is technically correct, although conversations with the AD have started about adjusting our charter to facilitate a 2.0 rev of Yang. If you have input/opinions around whether or not we should embark on this, I suggest sending a note to Benoit. I am also collecting issues to publish into a draft, that will document these problems right now. If anyone has issues they wish to document and want to contribute, please contact me offline. —Tom > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod