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

"Voyer, Daniel" <daniel.voyer@bell.ca> Fri, 29 May 2020 14:26 UTC

Return-Path: <prvs=411c256fd=daniel.voyer@bell.ca>
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 302493A091F for <ipv6@ietfa.amsl.com>; Fri, 29 May 2020 07:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=bell.ca
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 WHSlHlbbjGrl for <ipv6@ietfa.amsl.com>; Fri, 29 May 2020 07:26:56 -0700 (PDT)
Received: from ESA3-Dor.bell.ca (esa3-dor.bell.ca [204.101.223.60]) (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 842C73A091C for <6man@ietf.org>; Fri, 29 May 2020 07:26:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bell.ca; i=@bell.ca; q=dns/txt; s=ESAcorp; t=1590762416; x=1622298416; h=from:to:cc:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=cuWiAJiTh/DVDKPQu2xLOwd2RLecPscc6vd9m52fW7E=; b=LBYHuuXaAA0sEirAVFl7lanN6Jxgo4TiaZ689FoJ/MuPOHuAJ4Z8l+I9 yce7JzVfQFFRMNEjBEZjbi9EsLq3sLZvzR6A/wH15Eg2/XAlUE2e2cKhX /fbtb10CERn6DXMUrD9AKpCk7/Sj1CTYz7eqeEhRiTH4+QhFfbEu8V98s yRBrvWA6jECyi0PWMnMv4qiH+nKrkj7BhP+vjbkoY9isfEc7VOzdeq6lw Xnylq1rfqOWrN+Vb2v46WKQtDE0hEL896ZN4ERVSryY5StZyWLjaALN9X swGKc8jL+uAYBoVG5uSADFWX6lamH5N9cNkoAvwIR9WZbuntkSmWyfFMl g==;
IronPort-SDR: +3pCofcYmvC0rs8hdhbk1UCjEq5Fj73Duxjo62qgUb23U2bbTfMX6TikSpHx3yZulV+I/X7ksR HdEFxVEEoQyw==
Subject: RE: So where have all these new 6man WG people come from?
Received: from unknown (HELO DG1MBX02-WYN.bell.corp.bce.ca) ([10.39.18.12]) by esa03corp-dor.bell.corp.bce.ca with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 29 May 2020 10:26:55 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca (2002:8eb6:120e::8eb6:120e) by DG1MBX02-WYN.bell.corp.bce.ca (2002:8eb6:120c::8eb6:120c) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 29 May 2020 10:26:54 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca ([fe80::985f:63a7:1da1:aa02]) by DG1MBX04-WYN.bell.corp.bce.ca ([fe80::985f:63a7:1da1:aa02%22]) with mapi id 15.00.1497.006; Fri, 29 May 2020 10:26:54 -0400
From: "Voyer, Daniel" <daniel.voyer@bell.ca>
To: Fred Baker <fredbaker.ietf@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>
CC: 6MAN <6man@ietf.org>
Thread-Topic: [EXT]Re: So where have all these new 6man WG people come from?
Thread-Index: AQHWNcFI6KyG3tqOrEe7xSr2LvPYY6i/X1qAgAAA0AD//766AA==
Date: Fri, 29 May 2020 14:26:54 +0000
Message-ID: <CC0E929B-4A46-4AE3-B6DD-2C759887E6AF@bell.ca>
References: <CAO42Z2xDygUXTGwVunGSTMkZGMF8VePrPaXLSAJg14vAJdca5A@mail.gmail.com> <6DB604C0-2C29-44A8-AB01-DA697552C7DA@employees.org> <1C1F0496-33A8-4646-B356-369EA9ABAD33@gmail.com> <DM6PR05MB6348501B266FF51DD805C25DAE8F0@DM6PR05MB6348.namprd05.prod.outlook.com> <70CDD965-C9B4-4A15-9ACA-FFE685D97129@gmail.com> <53AACAD4-5A84-481D-983E-FC2CB04DB893@gmail.com>
In-Reply-To: <53AACAD4-5A84-481D-983E-FC2CB04DB893@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.28.92.8]
Content-Type: text/plain; charset="utf-8"
Content-ID: <70DDB7FEAB81FD428059BB1CB5579242@exchange.bell.ca>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZKr63s6-clCAJCqBjTUXNg8AMMo>
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: Fri, 29 May 2020 14:26:58 -0000

I agree with Stewart. Addressing these outstanding issues by email only is a challenge. 

When people make the effort to meet in person means they are truly determine solve it and also agree they might put a bit of water in their wine

We could also have virtual room/webex.

dan

On 2020-05-29, 10:20 AM, "ipv6 on behalf of Fred Baker" <ipv6-bounces@ietf.org on behalf of fredbaker.ietf@gmail.com> wrote:



    > On May 29, 2020, at 7:17 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
    > 
    > My main point was that a list discussion of this type rarely reaches an acceptable outcome, and that an objective discussion at IETF is normally a better approach. Indeed resolving issues like this is exactly why we meet F2F at IETF.

    So your point is that this entire discussion needs to wait until we meet f2f?

    I think, in fairness, we have done quite a bit on email, and check things discussed f2f on email.