Hi Jim,  (no hats)

On 9/17/26 02:12, Jim Mozley wrote:
if a query results in an RRset with different values for well-known (and other 
parameters) the client can make a more informed decision based on the 
parameters. The client can take the positive approach of using the well-known 
resource(s) first, and then falling back to trying other resources 
speculatively if it wants to.

I am getting the impression that you'd like a well-known method to determine 
things expected to be present in /.well-known/.

Would this not best fit with another well-known URL, such as 
/.well-known/hints, which then lists one well-known suffix per line?

This would seem to keep management of related data in one system (not adding 
the DNS as the second one), and could even be returned dynamically for certain 
source subnets and what not.

You could also consider just using /.well-known/ without a suffix for this, 
which in many web servers can be configured to return an index of the available 
suffixes (files).

 From the current Security Considerations, I'm still not able to
discern what clients are allowed to do with this SvcParam.  For
example, if clients use this SvcParam to skip fetches of desired
.well-known resources because it infers that they are absent, then
this allows a DNS attacker to cause the client to misunderstand the
status of those origins.

The assumption here is that the operator of the service pointed to by the DNS 
record is managing the zone

With the above approach, you would not need that assumption.

Best,
Peter
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to