Re: WGs/AD [IETF areas re-organisation steps]

Melinda Shore <> Sat, 27 December 2014 06:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id F16FA1A6F87 for <>; Fri, 26 Dec 2014 22:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uwPgC1PqGNEA for <>; Fri, 26 Dec 2014 22:24:26 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BAF9A1A1EB7 for <>; Fri, 26 Dec 2014 22:24:26 -0800 (PST)
Received: by with SMTP id ft15so13955579pdb.36 for <>; Fri, 26 Dec 2014 22:24:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iqrilZ2msJYQDcd0MvhfQSL5DJpwIE/D8cVGFfjp8nI=; b=y2Fn73BFc+2SshEx9TW9fx6CF9Q6oB9W/ps5nejWKnOlQe/1FmnY0cBucoxfh25SXl F+ZZKgatF9wu0Eym7tZhm0fkoutNjC6gerwu+NUuefBGzaMGxIXG1H1quhB8Qq8qZllu XPRynOtOIsMyNaYEigPw2quFa9UtrGFlhYRhe3n4s99BIe+I1qdmt0D0CzN5idwqh8Nk wy5+Q4Fzg+SRFKD2pIu89eGKguBjsfzTBIGjb1gaCyRfIPHD4wTshWjvZ4soMOJpzHuR 81l7sMEzgYHefSmACQTWfHYyS7fa3GzpSomi0LjvZMortFvvdU8KHKJZXcOJfWP1f5J2 V8uw==
X-Received: by with SMTP id dk5mr41759601pdb.98.1419661466052; Fri, 26 Dec 2014 22:24:26 -0800 (PST)
Received: from spandex.local ( []) by with ESMTPSA id o3sm29855211pdn.29.2014. for <> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Dec 2014 22:24:25 -0800 (PST)
Message-ID: <>
Date: Fri, 26 Dec 2014 21:24:23 -0900
From: Melinda Shore <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
Subject: Re: WGs/AD [IETF areas re-organisation steps]
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 27 Dec 2014 06:24:28 -0000

On 12/26/14 8:52 PM, Alia Atlas wrote:
> There are a few things we can do.  Some things that I've been trying to
> do in Routing include:
>   a) discouragement of progressing many use-case and requirements drafts.
>       We had drifted towards having WGs producing some to help
> articulate what
>       needed to be done - but then more and more appear and only some
>       actually provide more useful feedback to the architecture or
> protocol.  I
>       would rather see WGs produce things that can be implemented with the
>       necessary context than spend years working on use-cases and
> requirements.
>       I'm past the waterfall model of software development.
>   b) Encourage WG chairs to think about the need for ACTIVE consensus rather
>       than passive.  If there isn't the enthusiasm to review and improve
> a draft or
>       implement it, then does it really need to be an RFC?
>   c) Better and early cross-WG review once a draft is adopted as a WG draft.
>       Well-written drafts without serious issues are much faster to
> manage, review,
>       and progress.
>   d) Be willing to let WGs fail - by also letting them just get on with
> doing solutions.

These are all things I'd love to see implemented across the
organization, as well as raising the bar on BOFs - I've seen
some ADs put a massive amount of effort into BOFs that are
held around ideas that aren't fully-formed (it's not necessarily
that they're bad ideas, but rather the problem is that the
proposals are awfully immature).

I've been trying to decide what I think of the proposed
reorganization and I guess I'm neutral on it - it seems that
the workload problem isn't necessarily going to go away with
a reorganization, but that the two problems (structural
efficiency and manageable workload) would need to be
tackled in parallel.  I think Alia's list is a good start
on the workload issue.