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 14:17 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 B8CC23A0F46 for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 07:17:29 -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 2lMJzKnxt3Lc for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 07:17:27 -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 47DAB3A0F3E for <6man@ietf.org>; Thu, 28 May 2020 07:17:27 -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 04SEHMVu013635; Thu, 28 May 2020 10:17:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1590675446; bh=aWiFmsfIrmwtCZMJdPeStfdPOYKSAQXw3s/jRt5uGFo=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=EvgAsBVYoj4DvF3Z4Z1uH+tAA+KiZZdcvryVsUoxj3GCWmJ1pt7D1IGrH8AcT1yyt MGl5cEI4bfrVxF/3JlLSFsXX8I0krMwfBF2Hwot+QtcVpN/mq7B2NuKM9aIr1O+MxW DE2kiHwmLuMR8S0FhlB1ledkEjh7RXLGTh+Dl1fmrzoFyMINFp2kgDGttlsqkq2mv6 XBEtIBle85ElpsALOaikadsiEOokzT4OrlV2F9pHfV0q45kBBYMgRZ1jT/iT7jPtLN HtLNL5KuihUSHZP3xWw8lgvwwZrLFm+sgmjVzCttQl8JtJO6fOklkpZ4Rgt3QOCEaB NLYINW6di1RxQ==
Received: from XCH16-07-11.nos.boeing.com (xch16-07-11.nos.boeing.com [144.115.66.113]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 04SEHEPb012566 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 28 May 2020 10:17:14 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-11.nos.boeing.com (144.115.66.113) 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 07:17:13 -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 07:17:13 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Voyer, Daniel" <daniel.voyer@bell.ca>, "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: AQHWNPns4SR2GoqyikqG5AlmyzCwQai9ivVQ
Date: Thu, 28 May 2020 14:17:13 +0000
Message-ID: <00920ae9c30e49ed875c2837f35a1ffd@boeing.com>
References: <8A5DB52F-5355-484D-8E70-02247C2DF88E@bell.ca>
In-Reply-To: <8A5DB52F-5355-484D-8E70-02247C2DF88E@bell.ca>
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: B8D0F2E606EF5273532A86998AD9D0CB444E8426D96F34341B8A4BCF4FDCA78C2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_ZNZOpLMDtROC8myTd0k8rIilw4>
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 14:17:30 -0000

Hi Daniel, I do also have a drone hat:

https://ieeexplore.ieee.org/document/8742246

Thanks - Fred

> -----Original Message-----
> From: Voyer, Daniel [mailto:daniel.voyer@bell.ca]
> Sent: Thursday, May 28, 2020 7:12 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>om>; 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?
> 
> Hello Fred,
> 
> I too, come from the real-world, the operator side which implies wireline & wireless network. It's pretty awesome that you have an
> aviation hat though, I can't claim that I have a "drone hat" .. just yet.
> 
> But with this new ecosystem where we try to have an end-to-end type architecture, from access network, to metro and core network
> and try to adapt to a 5G/MEC, I believe we are redefining boundaries between domains. What's happening in 6man AND SPRING
> working group just reflect those new changes. New contributors coming in is not just happening to those 2 working group, there's also
> new contributors showing at DMM wg, and there's wireline folks attending 3GPP (not just related to segment routing). Proposing to
> "reject" or "treat" new contributors separately makes an "us and them" type of relationship and it's not good for reaching a form of
> consensus.
> 
> Regards,
> dan
> 
> On 2020-05-28, 9:54 AM, "ipv6 on behalf of Templin (US), Fred L" <ipv6-bounces@ietf.org on behalf of Fred.L.Templin@boeing.com>
> wrote:
> 
>     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
>     > --------------------------------------------------------------------
> 
>     --------------------------------------------------------------------
>     IETF IPv6 working group mailing list
>     ipv6@ietf.org
>     Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>     --------------------------------------------------------------------
>     ------------------------------------------------------------------------------
>     External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et
> documents joints
>