[DNSOP] Re: Fwd: New Version Notification - draft-ietf-dnsop-domain-verification-techniques-05.txt

[Tim Wicinski <[e-mail]>]

On Thu, Jul 11, 2024 at 3:36 PM John R Levine <[e-mail]> wrote:

> On Thu, 11 Jul 2024, Tim Wicinski wrote:
> >> A) Should verification records have a tag at the front of the data to
> >> identify the record type? There's plenty of prior art for this, e.g.,
> >> the 63 text records at stanford.edu. Or you might say that a
> >> sufficiently long random token in the interesting part will prevent
> >> false positives so there's no need.
> >
> > Are you referring to the "token=value" ? This gets discussed in the Token
> > Metadata section, and perhaps the document is using the assumption of _
> > foo-challenge.example.com makes it more relevant?
>
> right, if the value is long enough there's little chance of some other
> random text record from a wildcard matching it by mistake
>

Also "token" is more generic which perhaps is not that obvious?

The stanford.edu example is useful, only because they don't show up in
those alexa top-1000(000) lists.
Like I am sure many here have, I dumped the TXT records to the top 1000 and
while the majority use
the format "token=value", there are several that use the "token:value"
format.

I wonder if there should be some suggestions for "long enough token value" ?

tim




> Regards,
> John Levine, [e-mail], Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>