The ohttp examples in rfc9540, section 4.1 also includes a "mandatory=ohttp" example.
While I'd like to just ignore this (never having like critical extensions in x.509, and this seems similar:-), I guess we may need to provide a way to represent that in the JSON?
We probably need to say something about how to handle mandatory keys in SVCB.
The ohttp examples in rfc9540, section 4.1 also includes a "mandatory=ohttp" example.
While I'd like to just ignore this (never having like critical extensions in x.509, and this seems similar:-), I guess we may need to provide a way to represent that in the JSON?