-
-
@BRIAN_____@konklone@jmhodges Oh, on that I totally agree with you. But complexity is necessary because of all the broken legacy. -
@BRIAN_____@konklone@jmhodges CAs will still be shy of NCs for another decade, and if I view the ecosystem as a whole, I don't blame them -
@BRIAN_____@konklone@jmhodges So we shift the complexity to new. Incremental moves, even complex, don't need to be anathema. -
@sleevi_@BRIAN_____@konklone I would love to, at the least, get the CAA work in the spec if not the intermediate version! -
@jmhodges@BRIAN_____@konklone Intermediate is already in the spec - https://tools.ietf.org/html/draft-ietf-trans-rfc6962-bis-12#section-4.3 … -
@sleevi_@BRIAN_____@konklone hm, maybe I'm misunderstanding but that MAY seems less than what I want. Probably just don't have context -
@jmhodges@BRIAN_____@konklone Just means it is an option to munging the SAN. You already have to do cert reconstruction for precerts. -
@jmhodges@BRIAN_____@konklone What more do you want? Forcing it to an eTLD+1 via CA rather than CT policy? Something else?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.