RE: So where have all these new 6man WG people come from?

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 28 May 2020 13:53 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBCFE3A0ED5 for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 06:53:44 -0700 (PDT)
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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=boeing.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 QB-gcxFEZslT for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 06:53:43 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 28BCA3A0ED2 for <6man@ietf.org>; Thu, 28 May 2020 06:53:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 04SDrdOf021888; Thu, 28 May 2020 09:53:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1590674021; bh=EdPcRFjfPUw4SuXlXgYlPodJcpAjDDyC0qIdT6Fp10A=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=fn38Xqi4pqkflfyIvgtLWfKeSrz/rha8YGycEhJeoV53yPMsYsjTmXwqe6CQOvsgW HVv+tuyCNiJkrBpQTDxsBh7ErpxLJgb9WQYTBcM61DC7+OH4roTtGeJe+PyC+gy/f5 tDhIQ5mFGnWginiCyqFwAxfnBKTK391z9p9qlTsS9Vxg3btooG/NJX8TSMuibfrILE NivGlGM5M/Hxv0oq1ufC13r/vw++tWP7J9nWzPFA65s585CUl6UqHioqRXRIKV7503 GndkvxorI7WHEn0Z93lsFTGze6ato0Cq9clQ70JrXvlD4YcdX/T5edxmeBvi9SA9YQ Bk97s8bm8ooyg==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 04SDrQcN020264 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 28 May 2020 09:53:26 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1979.3; Thu, 28 May 2020 06:53:24 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1979.003; Thu, 28 May 2020 06:53:24 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, Mark Smith <markzzzsmith@gmail.com>
CC: 6MAN <6man@ietf.org>
Subject: RE: So where have all these new 6man WG people come from?
Thread-Topic: So where have all these new 6man WG people come from?
Thread-Index: AQHWNOJ5rT7wA6MSxUq0TPCOwZJLuqi93egA//+lYtA=
Date: Thu, 28 May 2020 13:53:24 +0000
Message-ID: <17ef0331f1b3466dbf3a19ffc7cb2758@boeing.com>
References: <CAO42Z2xDygUXTGwVunGSTMkZGMF8VePrPaXLSAJg14vAJdca5A@mail.gmail.com> <6DB604C0-2C29-44A8-AB01-DA697552C7DA@employees.org>
In-Reply-To: <6DB604C0-2C29-44A8-AB01-DA697552C7DA@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: BA6ADC3D310B502B17D0A298A1B7A3B25A2161063A869DCA9A2A593D73FA15792000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bsTNqeJ7m4uJkOz9FulI7qDlTq0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2020 13:53:45 -0000

Ole,

> It seems that a proxy war is being fought out in the working group.
> With both opponents and proponents of proposals closely aligned along company borders.

I am representing real-world use cases (planes, trains and automobiles) with my
aviation hat on. I do not work for a network equipment vendor and do not have
company influences driving my decisions. I think this flood of people coming into
6man many for the first time is bad for the 6man technical process and may
interfere with the timely need for solutions to real world problems. I trust that
the chairs will recognize what is going on and make the right decisions.

Thanks - Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.org
> Sent: Thursday, May 28, 2020 5:12 AM
> To: Mark Smith <markzzzsmith@gmail.com>
> Cc: 6MAN <6man@ietf.org>
> Subject: Re: So where have all these new 6man WG people come from?
> 
> Segment Routing (CRH, SRH and friends) isn't something 6man has traditionally dealt with.
> We have been more concerned about IPv6 in the open Internet, end to end, and not so much of technologies only applicable within a
> controlled domain.
> 
> From that perspective, it is not surprising that this work attracts a different participant-set than before.
> 
> It seems that a proxy war is being fought out in the working group.
> With both opponents and proponents of proposals closely aligned along company borders.
> 
> Best regards,
> Ole, with the dystopian hat on.
> 
> 
> > On 28 May 2020, at 13:23, Mark Smith <markzzzsmith@gmail.com> wrote:
> >
> > I've been an active participant in the ipng, 6man and v6ops IETF working groups since 2002.
> >
> > While I've only been to one IETF meeting in person since then (106, sponsored by the Internet Society), over that time I've come to
> recognise the names of many of the regular and active participants in these IPv6 working groups.
> >
> > I do not recognise many of the names of people who are objecting to the 6man working group adopting the CRH draft.
> >
> > Those who have been active 6man participants in recent years would know that even an ID adopted by 6man, written by Bob and
> Brian, that had a number of revisions, didn't survive WG last call, and that occurred while Bob was (as he still is) one of the 6man WG
> chairs.
> >
> >
> > Regards,
> > Mark.
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------