> On Oct 8, 2019, at 2:18 PM, Barry Leiba <barryleiba@xxxxxxxxxxxx> wrote: > >> At the risk of strawman-ing: If the problem is mainly that GEN issues >> tend to eat the IESG list, then a separate mailing list could be >> enough. Maybe the idea is mainly to have chairs responsible for >> discussion wrangling? If so, then a more conventional “GenArea” working >> group might do the trick. > > I don't think it's that they "eat the IESG list" so much as that they > "eat the IETF list”. Oops, typo on my part. I meant the IETF list. > And not in the sense that they monopolize the > list, but that that particular list isn't sufficiently focused to give > process issues proper consideration and determine what the right way > to handle them is. From my PoV, the advantage of a DISPATCH-like > group, rather than an unfocused area group, is that the former is > assigned the task of considering what's being discussed/proposed and > figuring out how best to address it... rather than to just keep > discussing it to no conclusion. Do you think writing a charter will really change people’s behavior on that matter? I imagine most people on the IETF list would like to come to a conclusion as it is. But as I think about this, it seems to me the main advantage of the wg would be to have a home for discussion and some experienced chairs to try to wrangle it. The original promise of DISPATCH was the ability to say “No, this is not something appropriate for the IETF to work on right now due to (reasons).” My experience is that mainly happens when there is insufficient interest in a proposal. Even then the proponents are often unhappy with the result. It’s rare for DISPATCH[ to conclude “There are so many opinions we are unlikely to reach consensus”. Unfortunately for GENDISPATCH, I think that will be the most common show-stopper—and a GENDISPATCH conclusion to that effect will not, by itself, stop such a discussion from continuing to eat mailing lists. I suppose it’s possible that GENDISPATCH could say “We probably can’t reach consensus on problem A, but maybe we can on B an C; can people please put their energy into those now and fight about A later?”. >> Another difference is that while DISPATCH is mainly interesting to >> people in the ART Area, we can expect GENDISPATCH to draw from all >> areas. We try not to let DISPATCH conflict with other ART meetings. How >> do you deconflict GENDISPATCH without it turning into another plenary >> or a standing BoF? > > This is always an issue with Gen Area BoFs and WGs, and this will be > no different. I think the bottom line is that there'll be a set of > people who will want to participate regularly, and we'll try to > accommodate that... there'll be people who want to parachute in for > certain topics, and we'll do what we can to accommodate that, > realizing that it's harder... and there'll be a lot of people who > won't want to have anything to do with it until a proposal is at a > stage where they strongly support it or object to it, and there's > little we can do to accommodate that. It is what it is, but it's no > different than if we just charter Gen Area WGs without a DISPATCH-like > start. No? I agree that deconflicting a GenArea wg and a GenDispatch wg would be essentially the same problem. In either case, both the “regular set” and the “paratrooper” participants are equally likely to participate in any other working group. Since gendispatch would cover (I assume) more topics than a either a GEN bof or “normal" GEN wg, the deconflicting problem will be harder. Plenary meetings would be a better comparison. Again, I’m not completely opposed, just on the fence. Ben.
