RE: "An open letter" signed by some IAB members

"Roni Even (A)" <roni.even@huawei.com> Wed, 20 November 2019 02:31 UTC

Return-Path: <roni.even@huawei.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 3652B12008C for <ietf@ietfa.amsl.com>; Tue, 19 Nov 2019 18:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vIUsELagb0M0 for <ietf@ietfa.amsl.com>; Tue, 19 Nov 2019 18:31:23 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E373120025 for <ietf@ietf.org>; Tue, 19 Nov 2019 18:31:23 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 4AE5943327243C3AB282 for <ietf@ietf.org>; Wed, 20 Nov 2019 02:31:20 +0000 (GMT)
Received: from lhreml725-chm.china.huawei.com (10.201.108.76) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 20 Nov 2019 02:31:19 +0000
Received: from lhreml725-chm.china.huawei.com (10.201.108.76) by lhreml725-chm.china.huawei.com (10.201.108.76) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 20 Nov 2019 02:31:19 +0000
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml725-chm.china.huawei.com (10.201.108.76) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Wed, 20 Nov 2019 02:31:19 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.127]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0439.000; Wed, 20 Nov 2019 10:31:14 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Mark Nottingham <mnot@mnot.net>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: IETF discussion list <ietf@ietf.org>
Subject: RE: "An open letter" signed by some IAB members
Thread-Topic: "An open letter" signed by some IAB members
Thread-Index: AQHVnrpVtq4nzo1oY0OJxyRDzWLFOaeTVzfA
Date: Wed, 20 Nov 2019 02:31:14 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD23DC6FE2@dggemm526-mbx.china.huawei.com>
References: <CALaySJJN23vFf-k2VqU0Mx+sOWV8wJiTBBkDGopjK7vOtYyDyA@mail.gmail.com> <0F893F23-FDEF-45F0-9A5B-839A1E4DB0E8@consulintel.es> <6964E3F0-06EC-4770-A0B2-E572E0240D59@mnot.net> <683EF30F-7EB0-424F-AFC7-F342BFB59642@consulintel.es> <F8691CFF-C683-4159-AD70-E1A4E4701A39@mnot.net>
In-Reply-To: <F8691CFF-C683-4159-AD70-E1A4E4701A39@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.40.217]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MHCQoh9g7yuKpe2LdmOYMFxeLOk>
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: Wed, 20 Nov 2019 02:31:27 -0000

HI,
I would have expected something similar to what we do in the IETF when a WG chair responds to a comment stating 

Name WG  xxx Chair as Individual

Roni Even
AVTcore co-chair as Individual

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Mark Nottingham
> Sent: Tuesday, November 19, 2019 11:19 AM
> To: JORDI PALET MARTINEZ
> Cc: IETF discussion list
> Subject: Re: "An open letter" signed by some IAB members
> 
> Hi Jordi,
> 
> Yes, I agree that clarity here is good. However, "Member of IAB" is pretty
> specific, just as "Member of Parliament" is specific; it is clearly distinguishing
> the part from the whole.
> 
> There are mitigating factors here (as discussed) where it could have been
> more clear, and I appreciate the need for honest attempts to be as clear as
> possible. What I was trying to get at was that I suspect that a large part of the
> problem is that a letter that is only signed by members of a board can easily
> give the impression that it's from that board -- something that others have
> noticed too. Avoiding that impression is good, but that doesn't mean we
> should generalise this instance into a rule about all mentions of affiliation.
> 
> Cheers,
> 
> 
> > On 19 Nov 2019, at 5:09 pm, JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es> wrote:
> >
> > Hi Mark,
> >
> > I know is not always easy. I use some times my company name and even
> email instead of a private one even if I'm speaking on my own personal
> capacity ... I feel that we all in general, should clear state in which capacity we
> are speaking. Is good, nice and convient to say "I work here and volunteer
> here" as well, of course, but if clarified if it is an IAB (in this case) view of
> personal one.
> >
> > However, in all the cases that you mention, the solution that I mention,
> makes it very clear. In case all the folks that sign are on their own, a footnote
> "stating it" or alternatively a similar text, below each of the signatures (when
> there is mixture of cases).
> >
> > Regards,
> > Jordi
> > @jordipalet
> >
> >
> >
> > El 19/11/19 17:00, "ietf en nombre de Mark Nottingham" <ietf-
> bounces@ietf.org en nombre de mnot@mnot.net> escribió:
> >
> >    I suspect part of the issue here is that the letter is signed *only* by IAB
> members, not mixed with others - and so I agree that such a clarification
> would have been helpful.
> >
> >    Question: Would people have felt such a clarification were necessary if it
> these names were mixed in with non-IAB (and non-IETF) names and
> affiliations?
> >
> >    And, would people have had an issue if it were signed only by one person
> who used their affiliation (as a *member* of the IAB, not the whole)?
> >
> >    To put it another way -- sometimes I give talks and mention that I'm a
> member of the IAB, and sometimes I omit other affiliations that I hold or
> have held (for example, it's rare that I need to trot out that I served as
> president of my local primary school for several years). Are people seriously
> suggesting that this is out of line?
> >
> >    Cheers,
> >
> >
> >> On 19 Nov 2019, at 4:48 pm, JORDI PALET MARTINEZ
> <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
> >>
> >> While I believe that anyone has the right to state his position at any
> organization, never mind is paid or not (unless a contractual clause disallows
> that), I think that when it is not an official position of that organization, it
> should be done stating clearly "that is a personal opinion".
> >>
> >> Something in the line of a footnote clearly indicating that this letter is not
> the "official position of the IAB" (for this specific case).
> >>
> >> Otherwise, tomorrow, a few of us can sign a similar letter showing below
> our names "Member, IETF", and who is reading it, probably will not recognize
> that we aren't "empowered" to sign as IETF, as we are just a bunch of
> participants, but not speaking from the IETF.
> >>
> >> And so, clearly agree with Barry here.
> >>
> >>
> >> Regards,
> >> Jordi
> >> @jordipalet
> >>
> >>
> >>
> >> El 19/11/19 14:42, "ietf en nombre de Barry Leiba" <ietf-bounces@ietf.org
> en nombre de barryleiba@computer.org> escribió:
> >>
> >>   Perhaps some of you have seen that Ted Hardie posted an open letter
> on
> >>   the Hong Kong high court’s injunction on Internet speech:
> >>   https://medium.com/@ted.ietf/an-open-letter-on-the-hong-kong-high-
> court-injunction-on-internet-speech-7f0048df2f54
> >>   The letter is signed by Ted and is co-signed by three other IAB
> >>   members, each signing as an individual: the letter is not from the IAB
> >>   and doesn’t claim to be.
> >>
> >>   Nevertheless, note that all signatories identify themselves as
> >>   “Member, Internet Architecture Board”, and three of the four do not
> >>   list their company affiliations.  This has two effects:
> >>
> >>   1. By being signed by four IAB members who are identified primarily as
> >>   IAB members, the letter *appears* to be from the IAB.  I have passed
> >>   this by three non-IETF friends, asking them who they think the letter
> >>   is from, and all three said, “The Internet Architecture Board.”
> >>
> >>   2. By using “Member, Internet Architecture Board” this way, those
> >>   signing the letter are effectively (whether by intent or not) using
> >>   their IAB positions to gain credibility for their personal opinions.
> >>
> >>   I think this is wildly inappropriate.  I think those of us in IETF
> >>   leadership should be scrupulously careful NOT to call out our IETF
> >>   affiliations this way unless we are speaking for the organization.
> >>   The fact that the letter refers to things that have been published
> >>   with IAB consensus doesn’t change the fact that the *letter* does not
> >>   have IAB consensus, and we must be careful not to give the impression
> >>   that it does.
> >>
> >>   I’ve discussed this with Ted, who thinks that there’s nothing wrong
> >>   with how the letter was signed and posted.  That disturbs me.  I tried
> >>   to let it go, but I’m sufficiently bothered by it that I felt the need
> >>   to take it to the community.  This is that.  Ted tells me that all IAB
> >>   members were invited to co-sign the letter, and that none brought up a
> >>   concern about the use of the “Member, IAB” affiliation.
> >>
> >>   As you think about this and — I hope — discuss it, please keep this in
> mind:
> >>
> >>   - I’m NOT talking about the content of the message and whether I do or
> >>   don’t agree with it.  That’s not the point.  I hope that as we discuss
> >>   this we do NOT go into the content, the politics, and so on.  Let’s
> >>   please keep this highly charged issue out of IETF discussions.
> >>
> >>   - I’m NOT looking to beat Ted up here; what I want is for this not to
> >>   happen again, and I hope the ensuing discussion supports that.
> >>
> >>   --
> >>   Barry
> >>
> >>
> >>
> >>
> >>
> >> **********************************************
> >> IPv4 is over
> >> Are you ready for the new Internet ?
> >> http://www.theipv6company.com
> >> The IPv6 Company
> >>
> >> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of the
> individual(s) named above and further non-explicilty authorized disclosure,
> copying, distribution or use of the contents of this information, even if
> partially, including attached files, is strictly prohibited and will be considered a
> criminal offense. If you are not the intended recipient be aware that any
> disclosure, copying, distribution or use of the contents of this information,
> even if partially, including attached files, is strictly prohibited, will be
> considered a criminal offense, so you must reply to the original sender to
> inform about this communication and delete it.
> >>
> >>
> >>
> >
> >    --
> >    Mark Nottingham   https://www.mnot.net/
> >
> >
> >
> >
> >
> > **********************************************
> > IPv4 is over
> > Are you ready for the new Internet ?
> > http://www.theipv6company.com
> > The IPv6 Company
> >
> > This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of the
> individual(s) named above and further non-explicilty authorized disclosure,
> copying, distribution or use of the contents of this information, even if
> partially, including attached files, is strictly prohibited and will be considered a
> criminal offense. If you are not the intended recipient be aware that any
> disclosure, copying, distribution or use of the contents of this information,
> even if partially, including attached files, is strictly prohibited, will be
> considered a criminal offense, so you must reply to the original sender to
> inform about this communication and delete it.
> >
> >
> >
> 
> --
> Mark Nottingham   https://www.mnot.net/