Re: Escalation: time commitment to fix *production* security bugs for BLS RFC v4?

["Salz, Rich" <rsalz=40akamai.com@xxxxxxxxxxxxxx>]

• I appreciate your clarification on the terminology but if you search https://mailarchive.ietf.org/arch/browse/cfrg/?q=standard or https://mailarchive.ietf.org/arch/browse/cfrg/?q=rfc, thousands of results show up.

 That doesn’t matter.  What matters is what the document *is*

 

I can post a message saying “I have a standard way to remove fleas from dogs using software”  But that doesn’t make it an Internet-Draft, let alone a standards-track RFC.