Re: Change of Affiliation

S Moonesamy <sm+ietf@elandsys.com> Fri, 15 March 2019 15:50 UTC

Return-Path: <sm@elandsys.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 38584131279 for <ietf@ietfa.amsl.com>; Fri, 15 Mar 2019 08:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=2aeokfpv; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=rJNR3N4f
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 3Cd8CpPyMeYp for <ietf@ietfa.amsl.com>; Fri, 15 Mar 2019 08:50:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D32F6131291 for <ietf@ietf.org>; Fri, 15 Mar 2019 08:50:46 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.49.158]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x2FFoWDG013663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Mar 2019 08:50:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1552665044; x=1552751444; bh=k0OC4csYoiPWwsuwzRutuvX0UOxopGYDhyICbKGlGZA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2aeokfpvJ3uhPUH5xGMHSExjB1QOEp0UvHydKEid35gbzphR4YJtI2JPRidpzxlUK hW9+KJcBGU0V4pDdNMJKTxnolhzMTyBos93ocMu0+sWTodh6oJ8+9tu+rXnP7dS7Vh wtXbAhQwf05whgCmBKWAyTSJ0HMFaBAporwamVXw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1552665044; x=1552751444; i=@elandsys.com; bh=k0OC4csYoiPWwsuwzRutuvX0UOxopGYDhyICbKGlGZA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rJNR3N4fQlNphCby3tmHa4g1QR/xgc1xLHrOJW8JQxfMg8znkOpyHg/jdOu8743bD 8GdKmBuhwonVaRtMKYHiJRfessfDeseCTYMVB0ldnoFh55ll2/Ud84X8QXPleVO994 UbcmxpOUAC/OzLYyyjZdMPFYWhHlXdMDGCmxRno0=
Message-Id: <6.2.5.6.2.20190315082127.12368480@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 15 Mar 2019 08:43:21 -0700
To: iesg@ietf, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Change of Affiliation
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <31856161-4B76-4F11-BC78-8CC7B28459EB@kuehlewind.net>
References: <31856161-4B76-4F11-BC78-8CC7B28459EB@kuehlewind.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xBjDAIM4hdnSTyxL7QHlbiFX3eE>
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: Fri, 15 Mar 2019 15:50:52 -0000

Dear IESG,
At 05:40 AM 13-03-2019, Mirja Kuehlewind wrote:
>documents is one of the main drivers or contributors in these 
>groups. A situation where at least one author and the responsible AD 
>have the same affiliation is less rare and usually not necessarily 
>seen as a conflict of interest, as least for wg documents where 
>other individuals have been involved in the process and consensus 
>was built by the whole group. However, whenever we get into a 
>situation where a potential conflict or bias could be assumed, we 
>will ask for the help of other members in the IESG, e.g. by 
>shepherding a conflicted document by another AD outside the 
>transport area if necessary. Still, if you think there is a conflict 
>or bias that we overlook or are not handling appropriately, please 
>talk with us, the rest of the IESG, or,
>alternatively, the IETF chair and we will handle this carefully.

There can be potential impartiality issues when an author and the 
Responsible Area Director share the same affiliation.  There is a 
thread in the mailing list archives about that topic.

Regards,
S. Moonesamy