All, Apologies for any procedural missteps as I am new to the group but am trainable.
I am looking to get some traction on a recent I-D my group is working on and am looking for advice along the way. We are confident this draft can play a significant role in the future of DNS especially as it relates to IPv6. While there are many problems we are attempting to address with this draft, we believe the biggest among them are related to IPv6 and the scarcity of IPv4 address space. If, by contacting this mailing list, we are heading down the wrong path we are particularly fond of any advice to move this forward as we see the need for it becoming more and more important as the adoption of IPv6 increases. The draft announcement is here: > -----Original Message----- > Subject: New Version Notification for draft-woodworth-bulk-rr-00.txt > > > A new version of I-D, draft-woodworth-bulk-rr-00.txt has been successfully > submitted by John Woodworth and posted to the IETF repository. > > Name: draft-woodworth-bulk-rr > Revision: 00 > Title: BULK DNS Resource Records > Document date: 2015-06-30 > Group: Individual Submission > Pages: 28 > URL: > https://www.ietf.org/internet-drafts/draft-woodworth-bulk-rr-00.txt > Status: https://datatracker.ietf.org/doc/draft-woodworth-bulk-rr/ > Htmlized: https://tools.ietf.org/html/draft-woodworth-bulk-rr-00 > > > Abstract: > The BULK DNS resource record type defines a method of pattern based > creation of DNS resource records to be used in place of NXDOMAIN > errors which would normally be returned. These records are currently > restricted to registered DNS resource record types A, AAAA, PTR and > CNAME. The key benefit of the BULK resource record type is the > simplification of maintaining "generic" record assignments which > would otherwise be too many to manage or require scripts or > proprietary methods as bind's $GENERATE. > Thanks and best regards, John 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. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
