Re: [Ntp] Wildcards in NTS certificate checking

["Salz, Rich" <[e-mail]>]

>   I think I've figured out where my confusion is/was coming from.  I was 
    thinking of 6125bis as a modification to 6125 rather than a replacement.

Well, I guess it depends on semantics.  The actual number of changes between the two is very small
	Do not use the CN field

6125 allowed wildcards (see 6.4, 6.4.2) but section 7.2 said SHOULD NOT as you point out. It doesn't say that clients SHOULD NOT use them if the server presents them, and maybe that's where you got confused?  7.2 ends with this:
   Notwithstanding the foregoing security considerations, specifications
   that reuse this one can legitimately encourage continued support for
   the wildcard character if they have good reasons to do so, such as
   backward compatibility with deployed infrastructure (see, for
   example, [EV-CERTS])

The "good reasons to do so" have evolved, and it's not longer "backward compatibility" but rather "compatibility."

I will copy the rest of your items over to the UTA working group if that's okay.

>    OpenSSL treats ".example.com" (leading dot) as matching x.example.com or 
    x.y.example.com or x.y.x.example.com ...

That's something to take up with the OpenSSL folks.  I didn't know they still do it.  They shouldn't.  But OpenSSL does many things to support testing and unusual environments.