Re: [Ianaplan] Process concern regarding the IETF proposal development process

Seun Ojedeji <seun.ojedeji@gmail.com> Tue, 27 January 2015 01:19 UTC

Return-Path: <seun.ojedeji@gmail.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28D4B1A1AF1 for <ianaplan@ietfa.amsl.com>; Mon, 26 Jan 2015 17:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkpCvLLXq0Mw for <ianaplan@ietfa.amsl.com>; Mon, 26 Jan 2015 17:19:10 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D63B1A1AF9 for <ianaplan@ietf.org>; Mon, 26 Jan 2015 17:19:09 -0800 (PST)
Received: by mail-qg0-f52.google.com with SMTP id z107so9701062qgd.11 for <ianaplan@ietf.org>; Mon, 26 Jan 2015 17:19:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7AL4XrSpbHXNMEyavYSBgWOvovEjTl1V71ukJWKHslQ=; b=BJKlwsgDqGqAEF05iGsT7Jst6f//VuD56kzZhdgOW/h6qk8Y3MH6zG6OjMjwPKd04N VfFYxt25xU4DYGftl1O9LMjrrJ49WqFghUFOPtAVGHd5TEoHuervf3dFdoiPNjIhY05C b9egT4EEVybqjw/K8CoH+rWUoLLf8Sy88/ee4hcAfGcgnUJPd38OuwYSFizWgA6gOYAd xoqqJ4/wN8FXGJs+J8AS4yZYF5V9mo9C8gC0nK3FsYVLiV42uJNs7hXNIj1hUU1SuS1X R2VImedpMLOKZzhTpQcRzYr9O+XU2NS3FxIg7gPdAAz2GtDJt/1VHTex6G0padTpaVar U8Gw==
MIME-Version: 1.0
X-Received: by 10.229.50.135 with SMTP id z7mr2868618qcf.21.1422321548378; Mon, 26 Jan 2015 17:19:08 -0800 (PST)
Received: by 10.229.38.68 with HTTP; Mon, 26 Jan 2015 17:19:07 -0800 (PST)
Received: by 10.229.38.68 with HTTP; Mon, 26 Jan 2015 17:19:07 -0800 (PST)
In-Reply-To: <67A0530C-F9D4-4A8B-A05C-C60A830A2C91@piuha.net>
References: <C172BBB7-9BA4-4BA7-848C-C7FE5B66CBF7@cooperw.in> <F8FC64C8-6FC7-4672-B18B-46DF993A653A@cooperw.in> <54C091D2.9050608@gmail.com> <1F30A463-76A9-4854-952A-35C54E42D2C6@istaff.org> <CAOW+2dvd1QRC6xbDTZ6ah23HfX=K=SeXDc1kXr2NREAcy37SvQ@mail.gmail.com> <54C13630.3050601@meetinghouse.net> <54C3D305.6030705@acm.org> <CAOW+2dv874BemFi=nSTgHQNO+7DpwhrjpVizhiEVaDK_bRzg4A@mail.gmail.com> <CAD_dc6j9vb14uPiPuAqh6-N9uyzqySv=WMb6_CVGQfob1iv95g@mail.gmail.com> <CAOW+2dsqqM_LbtxDqM0_2VmNj2e96Tifj=qpa5f1b5eAoKk9Tg@mail.gmail.com> <CAD_dc6gO=ygL7jotyqt0w0CJBnm74Apa9R6AZT5sHHmQRgQC8w@mail.gmail.com> <FB61D443-1613-4353-AA57-143800E6B425@piuha.net> <67A0530C-F9D4-4A8B-A05C-C60A830A2C91@piuha.net>
Date: Tue, 27 Jan 2015 02:19:07 +0100
Message-ID: <CAD_dc6hvmQb50j0gxkwaqWtZgczy6L5Z3gw7kHTHj_awAEOTHg@mail.gmail.com>
From: Seun Ojedeji <seun.ojedeji@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11341e5ca5c75f050d980ad0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/RMIBjOVNOdk4-Bov4ou2GNxBGwY>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] Process concern regarding the IETF proposal development process
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 01:19:12 -0000

Thanks for this Jari, it's helpful summary

Regards

sent from Google nexus 4
kindly excuse brevity and typos.
On 27 Jan 2015 01:27, "Jari Arkko" <jari.arkko@piuha.net>; wrote:

> I’d like to suggest a constructive way forward.
>
> First, I think we should observe that the ICG process put the planning and
> proposal efforts on purpose into the community processes. Those are the
> processes that we run. They are probably not perfect, they are certainly
> not the only possible ones, but they are processes that have existed and
> evolved for decades. The IANA transition is not an opportunity to redefine
> these processes.
>
> Second, the community has had a very clear opinion about matters, and
> re-opening discussions is not good practice. As usual, there are some issue
> where agreement was not universal. Disagreement with otherwise broad
> consensus is not grounds for re-opening a discussion.
>
> Third, I want everyone to focus on the concept that we’ve completed a step
> but that is not the last one. Among other things, the transition might
> involve some contract-termination/negotiation/renegotiation. And even if it
> would be very convenient, even IETF consensus doesn’t allow us to sign
> stuff in the name of other organisations :-) Or resolve conflicts between
> the three community proposals. So I would suggest that we stick to our
> clear direction from the WG, sit back, and see what these additional steps
> will bring. We will see updates as ICG, IAOC, and others have something to
> say, and any changes of direction will obviously need community feedback.
>
> Fourth, I wanted to go a bit back to the original e-mail that started this
> thread (finally!). As noted above, I think it would be inappropriate to
> start redefining the IETF process, and I think we’ve provided far more
> explanation about where we are and why than we’ve done in the approval
> process of most other IETF documents. One of the features of the IETF
> process is the expectation that most participants usually track the
> development of the community opinion, and conclusions are usually
> understood even before they are formally made. And when those conclusions
> get made, they can be brief, as the full discussion is visible on the
> mailing list archive.
>
> Yet, I have been talking to Milton and he has a point about communities
> understanding their own process well, but it being more difficult for
> newcomers, and in particular, complete outsiders that view the events
> later. I’d like to suggest that we produce an informal explanation of the
> process that helps provide visibility to people at large about what
> happened in the development of the IETF proposal from IANAPLAN WG. This is
> not a rerun of the process, an official document, or an opportunity to
> re-open discussions, but I think it would help us in the coming months as
> more people will be asking about our proposals. I’ll work with the chairs
> to produce that.
>
> Jari
>
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>
>