John, If the concern is a string of period-separated gibberish, why not create some artificial/sane limit where the receivers stop at N steps?
I can't say I'm personally a huge fan of tree-walks, only because I feel like the responsible party should have the ability to manage their DMARC properly through TXT or CNAME records, though, I do understand it makes many things easier in DMARC. I would like to suggest also suggest that if the tree-walk becomes the method that it should include a method by which a receiver can be told that it should stop. Message arrives from a.b.c.d.example.com, and at d.example.com, there would be a record like "v=DMARCv2 tw=0". -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast > -----Original Message----- > From: DNSOP <dnsop-boun...@ietf.org> On Behalf Of John R Levine > Sent: Thursday, November 12, 2020 10:15 AM > To: Paul Vixie <p...@redbarn.org>; Joe Abley <jab...@hopcount.ca> > Cc: dnsop@ietf.org > Subject: Re: [DNSOP] Tell me about tree walks > > >> I understand the reason why being able to identify the registrar for > >> a particular domain is useful (or "necessary" depending on your > >> perspective). > >> I don't understand the overlap between this problem and the problem > >> that John is trying to solve, though. Could you explain? > > > > i'm happy to try. otherwise i'll just be sheltering in place. > > I read all your stuff and it's clear to me that it has nothing to do with my > question about DNS tree walks. > > R's, > John > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dnsop__;!! > CQl3mcHX2A!VakA9j7sulgmHrfAPEgF4lehHbylfRiLw1UIVO- > f38uYVtIx70hYga8j4P2AxpNk296BNdY$ _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
