Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)

Jeff Tantsura <jefftant.ietf@gmail.com> Sun, 01 March 2020 23:30 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4D953A0B9E for <spring@ietfa.amsl.com>; Sun, 1 Mar 2020 15:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 htFswZcfh4hD for <spring@ietfa.amsl.com>; Sun, 1 Mar 2020 15:30:32 -0800 (PST)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 D8A873A0B9D for <spring@ietf.org>; Sun, 1 Mar 2020 15:30:31 -0800 (PST)
Received: by mail-pl1-x629.google.com with SMTP id u3so3434708plr.9 for <spring@ietf.org>; Sun, 01 Mar 2020 15:30:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=MPz2By8O7SGtxhLzj0HZUVGIzSN2x1McssGg7/bdgFk=; b=O4jImt8+jFaHMPnSVuO8SHeRYDiMhMFjZL6Pu5T5HwoN7LCUAwX5V8+6Z+EEIL5/Uq JH7elZLZHmm7Ae86sDnwPo+TQ72dv57B17MhO/XvU1Gc+rxmQhDaGNF+kr78a0YjRTLw Qm3jsqGXxOIRdc6EI46SI3LQPBppkLOyMDwaMiw9qXl4QRb3vSylF0wZcPXN/VDEYzrs DZsbQ4RPVramD6/y6ZwWhHTtPytJQ47f0m81RvhTuvpLwqKiyBA2MZPpr/DSmRcfloYg C+4JxdOXA/zX0mtEZjmUQWUNbLwym/kwFfNHERuak6yNAg23JxcZbwcp8DpxJZFrBkFq cpuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=MPz2By8O7SGtxhLzj0HZUVGIzSN2x1McssGg7/bdgFk=; b=AwWa1Sb//dAeUHAAJcYQgHIWzJAVbYWTQJIJczD0pKq46dM7TSL+hthpYS9z5zJ9yw JKYe5B2Il2zK0NBScNf29Dw8gOCYVv4H9Ecktze3Hgx9kdKJ3OdbrZ+2dzl9UAG8yM1a Lno11aAmMOxJtvvsZVrRlKKl/0T6h5UBvO13+HGCr2zdwFbD2f6S5kec3Amjcuhbrzse XZW2HuPPy5LiU0PZ9HJDcTLaqkG4nmbKfK1qK8EJZdgrjYmN04hejJxxPLpg9j2/cNfP U37jDt9+4rQD/8ERrhlzAAtiE4OpjzXHUNlH6Yxy27ek4ZpTYriSgWfK81sw6BB9S1i5 L/xQ==
X-Gm-Message-State: APjAAAVwkTKnm9KmLwQPWTm09s1wwamAUVlJvE5lP/ptprgjGlp0vLOM o+0gtYjKl+U2PW3kAZyQTGc=
X-Google-Smtp-Source: =?utf-8?q?APXvYqzexFwD6sFGCPpBSx782caDZaiO4jdDlVuUxlrW?= =?utf-8?q?+8CBEJYSLfKimbcCghHGd/Dc3jB+zDuZ4Q=3D=3D?=
X-Received: by 2002:a17:90b:2318:: with SMTP id mt24mr17966788pjb.113.1583105431221; Sun, 01 Mar 2020 15:30:31 -0800 (PST)
Received: from [192.168.1.25] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id x7sm15081787pgp.0.2020.03.01.15.30.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Mar 2020 15:30:30 -0800 (PST)
Date: Sun, 1 Mar 2020 15:30:24 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Robert Raszuk <robert@raszuk.net>, "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: SPRING WG <spring@ietf.org>
Message-ID: <692f9b92-4c64-49e3-86ab-80d9423adc57@Spark>
In-Reply-To: <abc665ae-603b-49d9-9ce5-c51c3072e571@joelhalpern.com>
References: =?utf-8?q?=3C17421=5F1575566127=5F5DE93B2F=5F17421=5F93=5F1=5F53?= =?utf-8?q?C29892C857584299CBF5D05346208A48D1A3DA=40OPEXCAUBM43=2Ecorporate?= =?utf-8?q?=2Eadroot=2Einfra=2Eftgroup=3E_=3C5518=5F1582908787=5F5E594573=5F?= =?utf-8?q?5518=5F436=5F1=5F53C29892C857584299CBF5D05346208A48DD1BCA=40OPEXC?= =?utf-8?q?AUBM43=2Ecorporate=2Eadroot=2Einfra=2Eftgroup=3E?= <C8417F71-D61E-42AC-831E-B85269D5D4A5@steffann.nl> <9b677b7c-fe52-dbae-7f83-2b5be5194325@gont.com.ar> <6.2.5.6.2.20200228132634.1060a610@elandnews.com> <9449c98e-b1d6-2c74-b78d-df3f5ba15ebc@nokia.com> =?utf-8?q?=3C6=2E2=2E5=2E6=2E2=2E20200229223634=2E093850f0=40elandnews=2Eco?= =?utf-8?q?m=3E_=3CDBBPR03MB54150500DA829FBAB73DFEC1EEE60=40DBBPR03MB5415=2E?= =?utf-8?q?eurprd03=2Eprod=2Eoutlook=2Ecom=3E?= <6.2.5.6.2.20200301111046.0c0499b0@elandnews.com> <CAOj+MMH3eyjoQe=SokYQ89HM2po01G1V=kgO+653EKx8eaobzw@mail.gmail.com> <abc665ae-603b-49d9-9ce5-c51c3072e571@joelhalpern.com>
X-Readdle-Message-ID: 692f9b92-4c64-49e3-86ab-80d9423adc57@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5e5c4595_b13a31_ba8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/YgeY6hX8wX5p_lkGFOXj_VRiJ0g>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Mar 2020 23:30:35 -0000

As Robert mentioned, it is quite often the case for a chair to participate in the development of a draft.
Taking RTGWG as an example, when we got (as result of a merge) a draft that both Chris and myself have co-authored, we had RTGWG secretary taking care of the life cycle of the draft.
I’m more than convinced that Bruno is entirely capable of driving the process unbiased and fair to all involved,  pointing out that there are formal possibilities to address this.

Cheers,
Jeff
On Mar 1, 2020, 3:17 PM -0800, Joel M. Halpern <jmh@joelhalpern.com>om>, wrote:
> The usual practice when a hair o-authors a document is for the co-chair
> to manage all aspects of the document life cycle. In this case, due to
> the co-chair being unavailable, we have a bit of a problem. For
> non-contentious documents, we can easily manage anyway. In this case,
> the document is quite contentious. Which makes things complicated.
>
> Yours,
> Joel
>
> On 3/1/2020 6:02 PM, Robert Raszuk wrote:
> >
> > Exception ? As far as I see it this is rather a norm in multiple WGs
> > across IETF for chair to co-author or contribute to his area of focus.
> > And there is absolutely nothing wrong with it. In fact it is
> > expected for chair to read the draft  and comment othen resulting in
> > becoming a contributor or at least being added to the Ack section.
> >
> > If this saga continues any further I recommend we start first by
> > obsoleting RFC8200 too. After all it's main author Bob Hinden was also a
> > 6man chair who requested publication of 2460bis:
> >
> > 2016-12-02
> > 2016-12-02 17:06:39 -0800
> > 08 Bob Hinden IETF WG state changed to Submitted to IESG for
> > Publication from WG Consensus: Waiting for Write-Up
> > 2016-12-02
> > 08 Bob Hinden IESG state changed to Publication Requested
> > 2016-12-02
> > 08 Bob Hinden IESG process started in state Publication Requested
> > 2016-11-30
> > 08 Bob Hinden Changed document writeup
> > 2016-11-15
> > 08 Bob Hinden New version available: draft-ietf-6man-rfc2460bis-08.txt
> >
> >
> > On Sun, Mar 1, 2020 at 9:38 PM S Moonesamy <sm+ietf@elandsys.com
> > <mailto:sm%2Bietf@elandsys.com>> wrote:
> >
> > Hi Andrew,
> >
> > [Cc to ietf@]
> >
> > I'll disclose that I am also affiliated with a
> > RIR.  I am copying this message to the
> > Responsible Area Director [1] for the SPRING Working Group.
> >
> > At 01:17 AM 01-03-2020, Andrew Alston wrote:
> > > While some on this list have made references to
> > > Bruno’s integrity – let me start by saying – I
> > > make no comment on anyone’s integrity – because
> > > I don’t know Mr. Decraene well enough to comment
> > > on that, and because I find an individual’s
> > > integrity in a discussion about if a potential
> > > conflict exists to be irrelevant. When people
> > > recuse for conflict in any normal environment,
> > > it is not because they will act on the conflict
> > > necessarily, it is because of perception,
> > > because it can taint the issue under discussion,
> > > and it leaves the process open to both attack and appeal.
> >
> > My question was about the process and the role
> > with respect to
> > draft-ietf-spring-srv6-network-programming.  I am
> > not personally acquainted with Mr. Decraene to
> > comment about his integrity.  It has been pointed
> > out to me that the person is well-known.  I don't
> > see what that has to do with the question which I asked.
> >
> > There is a message at
> > https://mailarchive.ietf.org/arch/msg/spring/3zbi71sjcJ8KaFgVIrF2Ymx4GC8/
> >
> > which lists the Responsible Area Director as a
> > Contributor.  In my opinion, the procedural
> > aspects are problematic.  I commented about a
> > somewhat similar topic previously [2].  From what
> > I understand, RFC 2026 is applicable for all
> > documents coming out of the IETF
> > Stream.  According to that RFC, the "procedures
> > are explicitly aimed at recognizing and adopting
> > generally-accepted practices".  One of the
> > definitions in RFC 7776 is: "A conflict of
> > interest may arise if someone involved in the
> > process of handling a harassment report is in the
> > role of Reporter, Respondent, or
> > Subject.  Furthermore, a conflict of interest
> > arises if the person involved in the process of
> > handling a harassment report is closely
> > associated personally or through affiliation with
> > any of the Reporter, Respondent, or
> > Subject".  The general practice, in such a
> > situation, is recusal.  I'll invite the
> > Responsible Area Director to comment about
> > whether there should be an exception to that practice and the
> > rationale for it.
> >
> > Regards,
> > S. Moonesamy
> >
> > 1. https://datatracker.ietf.org/wg/spring/about/
> > 2.
> > https://mailarchive.ietf.org/arch/msg/ietf/xBjDAIM4hdnSTyxL7QHlbiFX3eE/
> >
> >
> > _______________________________________________
> > spring mailing list
> > spring@ietf.org
> > https://www.ietf.org/mailman/listinfo/spring
> >
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring