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

Seun Ojedeji <seun.ojedeji@gmail.com> Mon, 19 January 2015 20:52 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 116911B2C7D for <ianaplan@ietfa.amsl.com>; Mon, 19 Jan 2015 12:52:53 -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 ynnZ83GaIRZt for <ianaplan@ietfa.amsl.com>; Mon, 19 Jan 2015 12:52:50 -0800 (PST)
Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F9C01B2CA4 for <ianaplan@ietf.org>; Mon, 19 Jan 2015 12:52:14 -0800 (PST)
Received: by mail-qc0-f177.google.com with SMTP id p6so2792124qcv.8 for <ianaplan@ietf.org>; Mon, 19 Jan 2015 12:52:13 -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=ZeH/N8HenfwdBX2xRjDfpVKrVHzZK//JhGhZ5S2Hn48=; b=T8Wl/NUwW5d0tInn4tJRWOLejh9mue+YvSoxc8Ymfm+j1fJRLy9GA0YKvDU3nw9B6F 8KA0yKYx78h9J7R/WV1WfxJStMnt5I9ubbQfw3UJDtl2dZ44t2yrOUTQ4/NfR3Hm2dS0 Knlf2b7S5htmulgG1I4KkL7qUfKuhTom2yJ5Rfw7OtRPz6kvzVagrO+46p3zrN9C7sN6 eGf5bEU7n30b7HG0Lxw5gAzsk2guQlyNUPCpKHCt6/jxCe/r2FEug746iyI6fwuYZ9gg vSJO+le+bJ3mlE3Vwu2AeeFW501Q2R3KqrHtYgVon4R/rIC3abQVYqKgl88mzgwfRocA tc9w==
MIME-Version: 1.0
X-Received: by 10.140.94.6 with SMTP id f6mr6414836qge.38.1421700733373; Mon, 19 Jan 2015 12:52:13 -0800 (PST)
Received: by 10.229.38.68 with HTTP; Mon, 19 Jan 2015 12:52:13 -0800 (PST)
Received: by 10.229.38.68 with HTTP; Mon, 19 Jan 2015 12:52:13 -0800 (PST)
In-Reply-To: <CAOW+2dtbq0WFjnYuKk-9aQU-SMDGhxvV4etTYj74m7feeVtVbQ@mail.gmail.com>
References: <C172BBB7-9BA4-4BA7-848C-C7FE5B66CBF7@cooperw.in> <8B1EC865-AD1F-4165-8C3A-258BA18C4823@gmail.com> <CAD_dc6j_762J_6wRiFt1Fx3mgLGJ5Q+p1p58eMOtf7Pt6F1GWQ@mail.gmail.com> <CAOW+2dtbq0WFjnYuKk-9aQU-SMDGhxvV4etTYj74m7feeVtVbQ@mail.gmail.com>
Date: Mon, 19 Jan 2015 21:52:13 +0100
Message-ID: <CAD_dc6gqmqUnqwGA8JR=R4U=wpUhsRWZ7HNfnkripWHYGYS8vg@mail.gmail.com>
From: Seun Ojedeji <seun.ojedeji@gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary=001a1139248230939a050d077f63
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/-gffqz3h3IV_d5BNnF5Cmp-YzU0>
Cc: ianaplan@ietf.org, Alissa Cooper <alissa@cooperw.in>
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: Mon, 19 Jan 2015 20:52:53 -0000

sent from Google nexus 4
kindly excuse brevity and typos.
On 19 Jan 2015 18:15, "Bernard Aboba" <bernard.aboba@gmail.com>; wrote:
>
> Seun said:
>
> "On a lighter note, it's interesting that to note that IETF who will
mostly be affected by those issues raised had to wait to be prompted by
other communities."
>
> [BA] I don't believe that this is accurate.  Under RFC 6220, the IAOC
owns legal and contractual issues with the IANA Protocol Parameter
contractor.  The chartering of the IANAPLAN WG did not change that.  The
issues referred to have been under active discussion within IAOC and the
IETF Trust all along (with legal counsel assisting).   The IANAPLAN WG has
only been responsible for providing a sense of priorities for that legal
work - a set of requirements, if you will.
>

... yes and transfer of IPR was not recognised to be on this WG list until
it got triggered by an external community. On another note, your message
above seem to imply that this WG is not tasked with preparing a response to
the ICG and also that the IAOC could introduce other elements that did not
achieve consensus within this WG. I hope I am wrong about that?

> It is important not to confuse the "requirements" drafted by IANAPLAN WG
with the actual legal and contractual arrangements under development by the
IAOC.
>

I believe my point was not implying/expecting that this working group draft
the contract actual text. However, I think this WG is tasked with
indicating the expected features of the contract. The current IETF response
to ICG does/did not include any section implying that it expect that the
IPR on IANA be transferred from the current operator in this process.

Thanks.

Regards
>
>
>
>
> On Mon, Jan 19, 2015 at 8:31 AM, Seun Ojedeji <seun.ojedeji@gmail.com>;
wrote:
>>
>> sent from Google nexus 4
>> kindly excuse brevity and typos.
>> On 19 Jan 2015 16:53, "Bernard Aboba" <bernard.aboba@gmail.com>; wrote:
>> >
>> > I would note that both of the concerns listed are under consideration
by the IAOC. Also, the proposals from the other communities also include
mention of both items.
>> >
>> Just to note that it's 1 of the communities(numbers) that has included
this; not necessarily that I agree with that but again it does not serve as
basis for me to fault the entire process.
>>
>> >
>> So while it is fair to say that the issues require more work,
>> >
>> On a lighter note, it's interesting that to note that IETF who will
mostly be affected by those issues raised had to wait to be prompted by
other communities.
>>
>> Cheers!
>>
>> I do not believe they are process concerns in this WG.
>> >
>> >
>> >
>> > On Jan 19, 2015, at 6:33 AM, Alissa Cooper <alissa@cooperw.in>; wrote:
>> >
>> >> After draft-ietf-ianaplan-icg-response was submitted to the ICG, the
ICG received the following comment:
http://forum.icann.org/lists/icg-forum/msg00017.html
>> >>
>> >> _______________________________________________
>> >>
>> >> Ianaplan mailing list
>> >> Ianaplan@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/ianaplan
>> >
>> >
>> > _______________________________________________
>> > Ianaplan mailing list
>> > Ianaplan@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ianaplan
>> >
>
>