Re: [DNSOP] DNS versioning, was The DNSOP WG has placed draft-woodworth-bulk-rr in state "Candidate for WG Adoption"
Matthew Pounsett <matt@conundrum.com> Mon, 24 July 2017 13:02 UTC
Return-Path: <matt@conundrum.com>
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 5FFCC131CE6 for <dnsop@ietfa.amsl.com>; Mon, 24 Jul 2017 06:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.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 wxkb0WCG4-dK for <dnsop@ietfa.amsl.com>; Mon, 24 Jul 2017 06:02:07 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 5836F1276AF for <dnsop@ietf.org>; Mon, 24 Jul 2017 06:02:06 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id 80so77634098uas.0 for <dnsop@ietf.org>; Mon, 24 Jul 2017 06:02:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gp1wxmd9fLKf38vBPh5qgLLIi5x96PMTzKuWd/MFm7w=; b=Dm/iu4Huvl6bhQPJZKMNnR6WAzFxbvEKNUNHRimm7tWVW6AdxYiUmSQ8O6XGcFJRR+ ReAwa/N9VBYGb4c7/KlsQbV0k7q2KjV6Cohw1Y3lsZre9GHdM8zbDhG+n9cbmOkRV1Lu VzbeFh2oTSgmjW5rhsxCVR3aCz4DcUAeMZtdph19yXgPX3dhZ/gCyuzm5jb0pppBl5ey zHhPTEb39TBqq47USlM/LITtdDEXlLgEkkwqhV2sKwFRmW4c9Xh/LbwBK0HSXFTtXwOc 0spRiFJ7wsa78hT1bj1BDePx/14rclQilkcbR3rwtSvtWSwztmYXE/HvZhTMDZ2MuI2R GHSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gp1wxmd9fLKf38vBPh5qgLLIi5x96PMTzKuWd/MFm7w=; b=MCK52ZL/VT3IEPcBZh8IVMSnCRhiXeqN/kpDa/zq5Dq/ULsmw3L8pQP/0Z6D1Voc/0 4EXLRRSVUu8kiZoA50FYCMyouQATsCbDy8PVzwosWlP6G+57JnA6xP5ottIldsIARakm OzUsvd9UMHgKSdkHMaBZx3x3HD7gI1aJRxFPw36cAYriEdUt+QOqTMBLZNg1VoFLXju/ nhpi2hVEsZsSlLyZ+m+OV9KvhnpkRq2zImllMEm/WvPmLrdUpgFap8aOJ43dp8mJH9Ho K55TvWKaHfppWu+djKTelfrcOAo7U7+AVxT3Os00kIKiwj9OYYFCyqFcdgltHvb0w92w F26A==
X-Gm-Message-State: AIVw110L8o8atHfZhdU51uclkgF6LLs19kYhtUcIChNsCoJqTYqXH6iH HRytyqD7o5RuysqA7uIJjDvMo6klLAwS
X-Received: by 10.159.49.7 with SMTP id m7mr10327995uab.194.1500901325934; Mon, 24 Jul 2017 06:02:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.84.14 with HTTP; Mon, 24 Jul 2017 06:02:05 -0700 (PDT)
In-Reply-To: <A05B583C828C614EBAD1DA920D92866BD0824617@PODCWMBXEX501.ctl.intranet>
References: <alpine.LRH.2.20.1707190347390.10419@ns0.nohats.ca> <20170719215749.2241.qmail@ary.lan> <20170720152559.GD22702@laperouse.bortzmeyer.org> <alpine.OSX.2.21.1707201752240.5469@dhcp-9d40.meeting.ietf.org> <CAAiTEH8VWv=WXOQDukVby=59Upa-+Y8ox7u4hk_qur_ZQ_3RBQ@mail.gmail.com> <A05B583C828C614EBAD1DA920D92866BD0824617@PODCWMBXEX501.ctl.intranet>
From: Matthew Pounsett <matt@conundrum.com>
Date: Mon, 24 Jul 2017 09:02:05 -0400
Message-ID: <CAAiTEH9Hvq3yP6yBpXQ-ozjdE2uFwsQXy5ziuZV4s5cyyDVOLQ@mail.gmail.com>
To: "Woodworth, John R" <John.Woodworth@centurylink.com>
Cc: John R Levine <johnl@taugh.com>, dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary="f403045e36cc602a6e05550fd2c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CT1yowXqDCtqth-hhf4O8rlyrR4>
Subject: Re: [DNSOP] DNS versioning, was The DNSOP WG has placed draft-woodworth-bulk-rr in state "Candidate for WG Adoption"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 13:02:09 -0000
On 22 July 2017 at 17:40, Woodworth, John R <John.Woodworth@centurylink.com> wrote: > > From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of Matthew > Pounsett > > > > > > > On 20 July 2017 at 17:53, John R Levine <johnl@taugh.com> wrote: > > > > That's why I don't share the fears about BULK: you cannot easily > > > > deploy a new feature that will require a change in the resolvers, > > > > because you don't know all the resolvers, and cannot change them even > > > > if you know they are too old. But your secondaries are only a small > > > > set of carefully chosen servers, and you have your say. > > > > > > I hear otherwise from people who run big DNS farms. It's common to > > > use multiple secondary providers, and it's hard to tell who's running > > > what server software. I also note that it took about a decade before > > > people felt comfortable using DNAMEs. > > > > > > > Hi Matthew, > > > > Thanks for your comments. > > > > I hear and understand your concerns. We have similar concerns but > > *I* feel we could offer a phased-in approach to set everyone's > > expectations appropriately. If one chooses to step ahead of the phase > > at least they'd have an idea what troubles await them. > Something's wrong with your email client. Your quoted text above was not me. > > > > > > > Dear $VENDOR. > > > > > > I'm a customer who is considering deploying the BULK RR type into my > > > zone, and I would like to know whether your systems support it. > > > > > > Thank you, > > > $CUSTOMER. > > > > > > > > > That said.. there is still an issue with key distribution for online > > > signing which is required to make this work. I see the utility in > > > BULK, but I'm persuaded that there needs to be more work before it's > > > deployable in an environment where *XFR is required. > > > > > > > Online signing in this environment will not be possible until this > > is solved but I believe the phased in approach would give us the time > > to solve for it without delaying insecure deployment (phase1). > > > What's your mechanism for enforcing (or even signalling) this phased approach in the DNS?
- [DNSOP] The DNSOP WG has placed draft-woodworth-b… IETF Secretariat
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… George Michaelson
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Paul Wouters
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Tony Finch
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Jim Reid
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Tony Finch
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Jim Reid
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… sthaug
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Paul Vixie
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … John Levine
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … John R Levine
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Jim Reid
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … tjw ietf
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Tony Finch
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Andrew Sullivan
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … John R Levine
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Stephane Bortzmeyer
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Stephane Bortzmeyer
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Stephane Bortzmeyer
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … John R Levine
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Matthew Pounsett
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Peter van Dijk
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Peter van Dijk
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … John R Levine
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … John R Levine
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Jim Reid
- [DNSOP] missing use case and problem statement fo… Jim Reid
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] missing use case and problem statemen… Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Vernon Schryver
- Re: [DNSOP] missing use case and problem statemen… Jim Reid
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Ondřej Surý
- Re: [DNSOP] DNS versioning, was The DNSOP WG has … Matthew Pounsett
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Tony Finch
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Tony Finch
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Paul Vixie
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Woodworth, John R
- Re: [DNSOP] The DNSOP WG has placed draft-woodwor… Petr Špaček