Re: [DNSOP] The DNSOP WG has placed draft-woodworth-bulk-rr in state "Candidate for WG Adoption"

"Woodworth, John R" <John.Woodworth@CenturyLink.com> Thu, 20 July 2017 01:17 UTC

Return-Path: <John.Woodworth@CenturyLink.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 B2D49127868 for <dnsop@ietfa.amsl.com>; Wed, 19 Jul 2017 18:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 3uHVuFfTL3vz for <dnsop@ietfa.amsl.com>; Wed, 19 Jul 2017 18:17:42 -0700 (PDT)
Received: from lxdnp29m.centurylink.com (lxdnp29m.centurylink.com [155.70.32.52]) (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 B4DA41272E1 for <dnsop@ietf.org>; Wed, 19 Jul 2017 18:17:42 -0700 (PDT)
Received: from lxdnp04n.corp.intranet (emailout.qintra.com [151.119.92.83]) by lxdnp29m.centurylink.com (8.14.8/8.14.8) with ESMTP id v6K1HfD8026774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 19 Jul 2017 19:17:42 -0600
Received: from lxdnp04n.corp.intranet (localhost [127.0.0.1]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id v6K1HaDO035974; Wed, 19 Jul 2017 19:17:36 -0600
Received: from lxdnp32k.corp.intranet (lxdnp23m.corp.intranet [151.119.92.134]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id v6K1Haqd035971 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=NO); Wed, 19 Jul 2017 19:17:36 -0600
Received: from lxdnp32k.corp.intranet (localhost [127.0.0.1]) by lxdnp32k.corp.intranet (8.14.8/8.14.8) with ESMTP id v6K1HavY003477; Wed, 19 Jul 2017 19:17:36 -0600
Received: from vodcwhubex501.ctl.intranet (vodcwhubex501.ctl.intranet [151.117.206.27]) by lxdnp32k.corp.intranet (8.14.8/8.14.8) with ESMTP id v6K1Habr003472 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Jul 2017 19:17:36 -0600
Received: from PODCWMBXEX501.ctl.intranet ([169.254.1.120]) by vodcwhubex501.ctl.intranet ([151.117.206.27]) with mapi id 14.03.0339.000; Wed, 19 Jul 2017 20:17:36 -0500
From: "Woodworth, John R" <John.Woodworth@CenturyLink.com>
To: "'Jim Reid'" <jim@rfc1035.com>
CC: dnsop WG <dnsop@ietf.org>, "Woodworth, John R" <John.Woodworth@CenturyLink.com>
Thread-Topic: [DNSOP] The DNSOP WG has placed draft-woodworth-bulk-rr in state "Candidate for WG Adoption"
Thread-Index: AQHTAAPw+UbndOaHcUud70v4A7K1OaJbDfuAgAAPdwCAABuOAP//u9kwgABcYQCAAJGCYA==
Date: Thu, 20 Jul 2017 01:17:34 +0000
Message-ID: <A05B583C828C614EBAD1DA920D92866BD081E686@PODCWMBXEX501.ctl.intranet>
References: <150040947342.11401.6673996996138598307.idtracker@ietfa.amsl.com> <CAKr6gn3xHZ6bzSSLoLt0FQzBrunqFPa-PFG6bAjLpfdEsD_iGQ@mail.gmail.com> <alpine.LRH.2.20.1707190347390.10419@ns0.nohats.ca> <alpine.DEB.2.11.1707191023090.27210@grey.csi.cam.ac.uk> <A05B583C828C614EBAD1DA920D92866BD081C441@PODCWMBXEX501.ctl.intranet> <AED0BED0-BF26-4FD2-9ACD-F2043C248C1A@rfc1035.com>
In-Reply-To: <AED0BED0-BF26-4FD2-9ACD-F2043C248C1A@rfc1035.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [151.117.206.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/f_It3TIjihmm34xGuxlr0rnTRlY>
Subject: Re: [DNSOP] 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: Thu, 20 Jul 2017 01:17:43 -0000

> -----Original Message-----
> From: Jim Reid [mailto:jim@rfc1035.com]
>
> What value has each IPv6 address? Or a name like
> host-2001-67c-1232-144-21f-5bff-fec3-ab9d.example.com? Please
> enlighten me.
>

Hi Jim,

I guess beauty (or value) is in the eye of the beholder :)

Although in practice the name would likely be shorter and potentially
include other customer attributes,
say acmewabbit-21f-5bff-fec3-ab9d.example.com

   1. This shows the owner is example.com, customer acmewabbit
   2. Reverse lookups are helpful for tools (e.g. traceroute)
      and logs.
   3. Fulfills customer demand
      (not sure all their use cases but this topic shows up
       often enough to be important to them.)

>
> If you have a need to generate PTRs on the fly for IPv6 addresses
> in your network, fine. However that doesn't seem to be a
> compelling reason to modify the DNS protocol and change every
> DNS server on the planet.
>

Forget for a moment about IPv6.  This draft makes $GENERATE more
memory efficient, scales bigger, stays intact through AXFR's
and yes -it makes some nameservers (authoritative) work a bit more
as a trade-off.

The fact that IPv6 is a drastically bigger namespace and would
benefit more is simply a bonus, this is just a next-gen $GENERATE.


Thanks,
John

>
> The cost/benefit optics of this draft are unclear.
>
>
-- THESE ARE THE DROIDS TO WHOM I REFER:
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.