On Jan 6, 2022, at 20:48, Paul Vixie <[email protected]> wrote: > > > > George Michaelson wrote on 2022-01-06 16:50: >> for a 200 in 200,000,000 problem? Ban it. > > i agree that we should ban it, but not on the basis of its infrequency of > use. rather, on the basis of data provenance.
Who wants to be the first to fail resolving adobe.net 😀 Seriously though, this draft is not about banning certain deployments or not. Its only concern is MAY vs SHOULD vs MUST require the found glue to be added to the response and potentially cause TC. I am tempted to SHOULD (or just not mentioning sibling glue at all) for two reasons. 1) the WG keeps punting this so MUST or MUST NOT seems too strong 2) in general the whole point of this draft is to get the glue in as it’s important and some implementations don’t always do that. Making it MAY or SHOULD NOT might leak into the non-sibling use case and for this 0.0000002% I don’t really care what happens. (Adobe can fix it if they need to) Paul _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
