Re: [regext] Scheduling for IETF 108

tjw ietf <tjw.ietf@gmail.com> Fri, 05 June 2020 13:44 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD213A0896 for <regext@ietfa.amsl.com>; Fri, 5 Jun 2020 06:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 ZCOpuD-neGLz for <regext@ietfa.amsl.com>; Fri, 5 Jun 2020 06:44:38 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 6AED03A0876 for <regext@ietf.org>; Fri, 5 Jun 2020 06:44:38 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id g62so4915896qtd.5 for <regext@ietf.org>; Fri, 05 Jun 2020 06:44:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=NlhNT1/AS1qocmu2JpV3q8ewcZJj4rbLzCmLjPrasVo=; b=Mlfv2V1UlwklQHPg1slQmOQ7arJxpck6TkJgpCADKP3fsVT8qDCIEkRZF6Cu3XbYYb DZMO+Xw2YgaRlsxTGI19Ep5c8p5UXyLAkWgJu4gdLbfAPZHYViLFmbOCVwLViG/8zo12 fCMQhuJ/e+VT+STUitoRm7ZIzpm2r7+7FW/yLLv9crjFtPMYKgYKiL7IABw1YdhMGdYG G3rx89VQl+hXsP2G6CgYwJCDY/8pe1LIXsqNGHp1XOa9Qs4/No+d7b5woD7j7m6JBOrl COswELe9udafzOwlraBoR63q1qEfYRi2O0d43f4/SxTi42GSlnswdZDyUIbrCvpItQaX T5aQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=NlhNT1/AS1qocmu2JpV3q8ewcZJj4rbLzCmLjPrasVo=; b=PhBop7w6/mdvCmIACiRfaErTgPEpgQCKRUd7ZpnFhcEyiA3pJzWZAIgkkH54DwUy1f sHkagj8i2a/zhfOGrYWHw3zEB8wDt5pIbk4p/iYl0KA5IsVHj4P3CxXCaSjclzST9MD1 l9kTW9Uj0wxvmMpw3Me/GkcYz+2vNNBaer04zv7VS2WgWSclakSFyJsyEQP86My+Mwxy 1qlPkqLF6vtS2Z4PA8zIHTNcplwAm6xrDUAEunFw1l99SK/0lP4VDph+vkSK6o/choO9 jiedrCkUe2R7QvavmNY1fRK5f8UX8sKFIGaYWznXDoUA9CrLJXof8HcZbjUaMDxItees 5ecA==
X-Gm-Message-State: AOAM533AhgKDEQUAiEnq2NuYJVWCaztrTgN6vIrQK78l/WGthQ20oq6k 7HUjs4/iwJ9umj7jvUwh0exUF1qJ1vg=
X-Google-Smtp-Source: ABdhPJzxXKHCvgWBHDhZfTFpMmth23au6a6HJlamGPxG1jX1MhgJOM/gXt/ZZX1cGEgQS+3XC4r0YA==
X-Received: by 2002:ac8:192c:: with SMTP id t41mr9500022qtj.32.1591364676032; Fri, 05 Jun 2020 06:44:36 -0700 (PDT)
Received: from [192.168.1.89] (184-14-195-118.dr03.chtn.wv.frontiernet.net. [184.14.195.118]) by smtp.gmail.com with ESMTPSA id s4sm6867359qkh.120.2020.06.05.06.44.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 Jun 2020 06:44:35 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: tjw ietf <tjw.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 5 Jun 2020 09:44:35 -0400
Message-Id: <7FEC6C14-1CF5-4E87-B3FA-5D8678812779@gmail.com>
References: <2d8ec093a59348f2b44de58c1a8427f9@verisign.com>
Cc: "ietf@antoin.nl" <ietf@antoin.nl>, "regext@ietf.org" <regext@ietf.org>
In-Reply-To: <2d8ec093a59348f2b44de58c1a8427f9@verisign.com>
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (17F80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/CcCZdnLIYXuteEs1u5G3-q_WCrM>
Subject: Re: [regext] Scheduling for IETF 108
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2020 13:44:40 -0000

Agree on the dns.conflicts. 

Sent from my iPhone

> On Jun 5, 2020, at 09:36, Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org> wrote:
> 
> 
>> 
>> -----Original Message-----
>> From: regext <regext-bounces@ietf.org> On Behalf Of Antoin Verschuren
>> Sent: Friday, June 5, 2020 9:31 AM
>> To: regext <regext@ietf.org>
>> Subject: [EXTERNAL] [regext] Scheduling for IETF 108
>> 
>> Hi all,
>> 
>> It is time again to start thinking about scheduling a meeting for IETF 108.
>> As you are aware, IETF 108 will be an all virtual meeting this time.
>> We are reaching out to you to ask your opinion on scheduling a meeting.
>> What conflicts with other working groups or BOF’s should be avoided?
> 
> Conflicts should be avoided with all of the DNS-centric working groups, including dnsop, dprive, and add.
> 
> Scott
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext