Moving tls to bcc, and adding rfc-interest. (This is the kind of discussion that is likely to ignite a dumpster fire, and it's not specific to TLS work.)
On Mon, Aug 19, 2019 at 11:05 AM Watson Ladd <watsonbl...@gmail.com> wrote: > I see no reason why English alone should be accepted for standards > documents we reference. French and German pose few difficulties, and one > can always learn Russian. > > What I don't know is how difficult Mandarin is at a level to read a > standards document. I expect the mechanics of using the dictionary to > dominate. > > I'm concerned about the traceability of unofficial Englidh PDFs on some > website: could the Chinese body responsible host them instead? > > I fully expect this to be a more general IETF problem. > For purely practical reasons, within a knowledge domain it makes sense to have a single language in which normative documents are written, with fluency in that language an implicit requirement of direct participation. Otherwise, the number of people who will be able to contribute to IETF work (writing or reviewing) will be very small, limiting the throughput, shared knowledge base, and overall utility of the SDO. For historical reasons, that single language is English. This isn't something unique to the IETF, either: for a variety of reasons too numerous to cover here, English has become the default shared language in a multilingual world when actual work needs to get done between people with different native tongues. The IETF exists in this reality: fair or not, there's really no other practical choice. Informational documents and upstream references are maybe a different story as they are not required to implement IETF protocols, but I suspect similar issues would crop up even there, given how important many informational documents are. Kyle
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
