[arch-d] Draft IAB conflict of interest policy

Guntur Wiseno Putra <gsenopu@gmail.com> Mon, 13 January 2020 15:47 UTC

Return-Path: <gsenopu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6EC12011F; Mon, 13 Jan 2020 07:47:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 eOKT7Vt3kaoJ; Mon, 13 Jan 2020 07:47:32 -0800 (PST)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4728D12010C; Mon, 13 Jan 2020 07:47:32 -0800 (PST)
Received: by mail-oi1-x22a.google.com with SMTP id p125so8625070oif.10; Mon, 13 Jan 2020 07:47:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iI6HbzmDJ6xVCMyHCx9D6DsV++R1dNYdMgBZPxpg8Ns=; b=HIxVwNvzgGlZa0M+/iDruxymADMqeVgdSVg5vA+Gfl5CbM3T9SReR8k4UXPC5gkjay zF0slP6Z60ybfj41zgjiAxAYq2RReztD8mSmryXC6ywamhIM54D8Yk9srtMqq5dUAFcY SFJeGjh2zMmqoF4VTBMCWdGTHx2BopVhS2e2obQtx/WBw6F2NqRvwQ58qm+/g+miV96n 1FX3f6F+eAb+hSIGRMY2H8V58TOfC91hIUmTvrkaLD/JAlH8lotCYbUoKUtJyLlGbMF4 7yFQELcJL+nTEqoO2UyUTYy9cDY/5FHJdrn3f7a8m1qOFOXXc3ilWn2y/esOBNJ6uGFG KI5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iI6HbzmDJ6xVCMyHCx9D6DsV++R1dNYdMgBZPxpg8Ns=; b=h8HnvPw1d0Frff3NakHwxtTkrqGyDdJBeCS3FopV66sjRZFhTvWpAeDTza26YHkZmg R7oocbWeKA/K1e4Cw265YKl6Zpg6l7l08VTvEDWtQaXI10m3Cz4JQ4qF6rUWnmMU4YgS P4a0M+YG38pJkR7qN5+tJzPxtGQwO9LaMpSe2F4ph5mO3JRNyAmr/J0vz097JgSrFFLB Aj95TbJNb96ueMkaUjNuUpG/KQa3hvvSVvDY0tApJOtEyh4Qbiq9Aru91CvT1Q0u5GtM q1QI3Z6ERs76eWs4cKq+gp0WNYbHuWaJ8rl5fZCtSNtClzgT1+1oaPQXua00qFtfBHAE yt2Q==
X-Gm-Message-State: APjAAAV4YrnyqBKMLR7njLfdphvfVzSDMym8eODZqGsLOrNIsPciu7Gg N95isfWkXBA7mgCNzX4C8DrW9uPldzM1fDwByk0=
X-Google-Smtp-Source: APXvYqyGIsEQ9OxqFAGR9SNi3TO6HDZsASIE932Dy/7Zq+ezILkhh91TaYmmNsiAJJ3TkB5lLqjrxQMz/inbY4qhgaM=
X-Received: by 2002:a54:468b:: with SMTP id k11mr12565033oic.134.1578930451567; Mon, 13 Jan 2020 07:47:31 -0800 (PST)
MIME-Version: 1.0
Received: by 2002:a05:6830:1155:0:0:0:0 with HTTP; Mon, 13 Jan 2020 07:47:30 -0800 (PST)
In-Reply-To: <ace1b96d-e9ff-d86f-8440-f4c4977ba3d7@gmail.com>
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <5F0ADD7E-84A2-45E0-B084-F5AA5FE62822@iii.ca> <a7ff9d2e-fb01-61ba-1aa4-27f32102ed8f@gmail.com> <2f9704f7-60e2-7894-46df-72a26c2f21fd@huitema.net> <ace1b96d-e9ff-d86f-8440-f4c4977ba3d7@gmail.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Mon, 13 Jan 2020 22:47:30 +0700
Message-ID: <CAKi_AEs0P-JkvBi9e3QgS4c10mLJoNXiRUVgzJg-F13Y+2py3Q@mail.gmail.com>
Subject: [arch-d] Draft IAB conflict of interest policy
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, Cullen Jennings <fluffy@iii.ca>, IAB Chair <iab-chair@iab.org>, "iab@iab.org" <iab@iab.org>, IETF Crazy <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b0da49059c0764c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lbpTEzXfuG8YZ9TzRvilPAHjOeQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2020 15:47:37 -0000

Dear architecture-discuss,

(I am reading on "Architecture in Cyberspace":)


Networks of Interests in Cyberspace, in Internet:

The conflict of interest policy above attempted by IAB means an attempt for
a resources management, that is about managing conflicts of interests in
such a way of defining tolerances if there are those conflicts happening
among "covered members" of an organizational bodies working on Internet
technologies...--an attempt that is exclusive to "covered members" of an
organizational body...

Yet, as what was mentioned above is about the ethic, architecture comes
with aesthetic considerations also: such appreciations for, with
considerations on laws and principles of, beauties realized in arts:
architecture in cyberscape is spatialized music. There are compositional
filters made up by the intentions of the architects and perceptual capacity
of the viewers. Together the aesthetic and the ethic set values, interests,
of the beholders, for a liquid architecture in cyberspace: it is about
places of welcomes and defences of "me"...(1)


(1) Novak, Marcos, "Liquid Architecture in Cyberspace"

https://www.evl.uic.edu/datsoupi/coding/readings/1991_Novak_Liquid.pdf

Regard,
Guntur Wiseno Putra

Pada Senin, 13 Januari 2020, Brian E Carpenter <brian.e.carpenter@gmail.com>
menulis:

> On 13-Jan-20 09:28, Christian Huitema wrote:
> >
> > On 1/12/2020 9:20 AM, Brian E Carpenter wrote:
> >> BCP 39 makes it fairly clear that the IAB does not need a separate COI
> policy. This text was inserted on legal advice from Jorge Contreras, as the
> IETF's pro bono counsel at the time, who said it was intended to 'protect
> IAB members from personal liability for IAB decisions (particularly in view
> of the last paragraph, stating that they serve as "individuals")':
> >>
> >>>    Members of the IAB shall serve as individuals, and not as
> >>>    representatives of any company, agency, or other organization.
> >>>    Members of the IAB shall owe no fiduciary duty of loyalty or care to
> >>>    IAB, IETF, IRTF or IESG.
> >> The last sentence in particular seems to make a formal COI policy
> unnecessary and possibly harmful. Wouldn't such a policy nullify that
> protection that IAB members have had since May 2000?
> >
> > Brian, it is not obvious that this paragraph in RFC2850/BCP39 implies
> that "a formal COI policy is unnecessary and possibly harmful". I
> understand why you would say that, but it requires some level of reading
> between the lines.
> >
> > You are implicitly suggesting that the current attempt at writing a COI
> policy for the IAB be scrapped. That may well be very good advice. After
> all, we might say that what is expected from members of the IAB is exactly
> the same as what is expected from participants in the IETF in general. But,
> however well founded that advice may be, we will need some more explanation.
>
> Exactly why I asked about legal advice. The *ethical* aspect is probably
> not contentious, and is indeed right there in the charter already.
>
> >
> >> Can we see the legal advice that led to the current proposal?
> >
> > Similarly, if the text in RFC 2850 comes from past debates in the IAB,
> can you point us to the minutes of these debates?
>
> I'm on travel, so I can't easily search the archives, but it would have
> been late 1999 or early 2000. I did quote verbatim Jorge's comment from my
> own email archive, and I doubt if any of us would have gone against his
> advice in those days.
>
>    Brian
>
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>