Return-Path: X-Original-To: dnsop@ietfa.amsl.com Delivered-To: dnsop@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 908693A08CB for ; Mon, 18 May 2020 15:38:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[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 Lbhi7FJot7Vo for ; Mon, 18 May 2020 15:38:48 -0700 (PDT) Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 E43E73A08CA for ; Mon, 18 May 2020 15:38:47 -0700 (PDT) Received: by mail-oi1-x22c.google.com with SMTP id x23so4019557oic.3 for ; Mon, 18 May 2020 15:38:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1J2GklB1V7w0wACAKIBDVfPIEy6LZImXyMcCPcQUSp0=; b=YSjOoEXnV4PcmxF2flwjXYtjaMcimCtKgEU4yX5fe5Bh6nBL2nPSOfhoS3sotjojcb gli1c/QFmGGtyKA4t5CnDVmoqewlZ1s05w3ZmM9PZsTt9e2ohN0LlDoP0israxGAy9QE 3xNRneUx9iEnIpxhx41NRzzo/1bzVMva4sH2It2D/+KQpz1OD//wuKsi4tszH3JphtQ+ 72DaNrnOhYFfOl+GfPYs3HCT1/KjzDwZukYUWC8sL5f4YgBNkOhXPY++MzWLa7TACQig f6MSKdDj4icP0m4AmTWLinZyH89wRjyitP+3hKaKrh8rQUQJQ4elX65g/xCP5NV52Q2m y0wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1J2GklB1V7w0wACAKIBDVfPIEy6LZImXyMcCPcQUSp0=; b=rW2y0UVm++OQeVaJqi5EXJcrpEo2J6Q2JeqF1OPtnJhNKWkMI+Ja2wwuRoh2jXGCOJ O/WvJf6BiN6b3FpBCfsUPabEWfAB1wx5CFEvd9wlEsY7gJ0Pz71JkmFgQ5gLANly8j7Z pwMKhAll0JG3lUVPRWnRtZiYz0NeJGCb77fQFEr4vVVgKEwNIHCmjfAgGiHwDZns4eDT XIFIJxklDAsr+k7ID6ULK3p8+4JSbHjq9BgO88i3+9ZDgD5hs9XUspQ6AtTBH9O6QryB Div2ppIzNK6Oy58vK8y3b1a6in+FkHboD2ubc2J4bw0qjlgr41CxACJkyKIVpifucOHD v7yw== X-Gm-Message-State: AOAM532/xDLRVowSFJ1KlTETRt7NqB9o2/BMbkSeTQBmOL2q/KIVokeo V58dRfk14rkWcpqGgYVcsOAsqS6NhN0P+U857dqAg4Wyhzg= X-Google-Smtp-Source: ABdhPJzX0trVOOpqx45GEFJeQ/uii7udYstnGdMBrtVAuO8x0UeA62GI1AkgHZroJzIwG5s5FxoIknkuzOl0sTlx1iw= X-Received: by 2002:aca:518c:: with SMTP id f134mr1208424oib.6.1589841527044; Mon, 18 May 2020 15:38:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tim Wicinski Date: Mon, 18 May 2020 18:38:36 -0400 Message-ID: To: Paul Wouters Cc: Wes Hardaker , dnsop Content-Type: multipart/alternative; boundary="00000000000077fbe305a5f3d303" Archived-At: Subject: Re: [DNSOP] Call for Adoption: draft-pusateri-dnsop-update-timeout X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF DNSOP WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2020 22:38:50 -0000 --00000000000077fbe305a5f3d303 Content-Type: text/plain; charset="UTF-8" All This call for adoption ended last week and the chairs were very much on the fence over adopting this document. We went to our AD to help decide this and after some poking, this was what we received: I too would like to have seen more support, but I do think that the selection and "strength" of the support messages makes this OK; I tend to side with Warren's view on this, so we're going to adopt this document for now, and we'll see how the working group works on it. tim On Tue, Apr 28, 2020 at 5:17 PM Paul Wouters wrote: > On Tue, 28 Apr 2020, Wes Hardaker wrote: > > >> We are looking for *explicit* support for adoption. > > > > I support it, though I'd feel more comfortable hearing from operators > > that want to deploy it. I suspect there are many, but that's just > suspicion. > > I think you really mean IPAM vendors? Like is this something Infoblox, > bind, Bluecat and BT and Microsoft would want to incorporate into their > enterprise products? > > Paul > --00000000000077fbe305a5f3d303 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All
This c= all for adoption ended last week and the chairs were very much on
the fence over ado= pting this document.=C2=A0 We went to our AD to help decide
this and after some poki= ng, this was what we received:=C2=A0

I too w= ould like to have seen more support, but I do think that the
selection and "strength" o= f the support messages makes this OK;

I tend to side with Warren's view on th= is, so we're going to adopt this
document for now, and we'll see how the wor= king group works on it.

tim



On Tue, Apr 28, 2020 at 5:17 PM Paul Wouters <paul@nohats.ca> wrote:
On Tue, 28 Apr 2020, Wes Hardaker= wrote:

>> We are looking for *explicit* support for adoption.
>
> I support it, though I'd feel more comfortable hearing from operat= ors
> that want to deploy it.=C2=A0 I suspect there are many, but that's= just suspicion.

I think you really mean IPAM vendors? Like is this something Infoblox,
bind, Bluecat and BT and Microsoft would want to incorporate into their
enterprise products?

Paul
--00000000000077fbe305a5f3d303--