I'm not married to any name, I chose WHOIS for historical reasons. We can call it _hamsandwich if it builds consensus.
On 7/9/19 9:37 AM, Rubens Kuhl wrote: > > I like the overall idea, but I believe we should let go the name > WHOIS. What about "_contact" for the fields instead of "_whois" ? > I like the All record as an option. > > I don't agree with your reasoning for this, but we can agree on > something to be done for different reasons, too. > > I understand the limitation for domains without DNS servers, or with > DNS servers but in clientHold or serverHold status, but I don't think > they make this less useful since in most cases where people want to be > contacted, they have the domain up. > > What are the interactions between possible record sizes, DNS > fragmentation, DNS over TCP blocking ? This might be worthy discussing > in the draft. > > > Rubens > > > > >> Em 8 de jul de 2019, à(s) 18:38:000, John Bambenek >> <jcb=40bambenekconsulting....@dmarc.ietf.org >> <mailto:jcb=40bambenekconsulting....@dmarc.ietf.org>> escreveu: >> >> All- >> >> In response to ICANN essentially removing most of the fields in WHOIS >> for domain records, Richard Porter and myself created a draft of an >> implementation putting these records into DNS TXT records. It would >> require self-disclosure which mitigates the sticky issues of GDPR et >> al. Would love to get feedback. >> >> Name: draft-bambenek-porter-dnsop-whois-over-dns >> Revision: 01 >> Title: Domain Contact Information (WHOIS) over DNS >> Document date: 2019-06-30 >> Group: Individual Submission >> Pages: 13 >> URL: >> >> https://www.ietf.org/internet-drafts/draft-bambenek-porter-dnsop-whois-over-dns-01.txt >> Status: >> >> https://datatracker.ietf.org/doc/draft-bambenek-porter-dnsop-whois-over-dns/ >> Htmlized: >> >> https://tools.ietf.org/html/draft-bambenek-porter-dnsop-whois-over-dns-01 >> Htmlized: >> >> https://datatracker.ietf.org/doc/html/draft-bambenek-porter-dnsop-whois-over-dns >> Diff: >> >> https://www.ietf.org/rfcdiff?url2=draft-bambenek-porter-dnsop-whois-over-dns-01 >> >> Abstract: >> Domain contact information over DNS provides a vehicle for >> exchanging contact information in a programmatic and reliable >> manner. DNS has a ubiquitous presence within the internet >> infrastructure and will act as a reliable publication method for >> contact information exchange. This RFC provides an agreed upon >> structure, voluntarily, to publish points of contact for domains. >> >> This document outlines the methodology for utilizing DNS TXT records >> for voluntary publication of various forms of contact. The intended >> purpose is to provide a faster means of reliable contact for >> professionals, cyber-defense of domains. >> >> >> >> >> >> >> — >> John Bambenek >> >> On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 >> license which means commercial use will require a license. Contact >> sa...@bambenekconsulting.com <mailto:sa...@bambenekconsulting.com> >> for details >> _______________________________________________ >> DNSOP mailing list >> DNSOP@ietf.org <mailto:DNSOP@ietf.org> >> https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
