A state of spin ... presented in ASCII (was: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 04:02 19-03-10, Dave Cridland wrote:
The IAB made a clear statement that we need i18n support, yet over a
decade after RFC 2130 or RFC 2825, the RFCs themselves still have a
strict ASCII limitation. Sure, that wasn't mentioned at the time, but
does nobody else find this plain shameful?

As seen in an I-D:

  "The IETF is an international organization with open participation.
   It is important that the IETF leadership be a reflection of the
   diversity of its participants."

   The "IETF is an open organization as such one would expect that no
   single company or funder of participants would dominate the
   leadership positions."

What if those positions were a non-diverse set in terms of geographic region, ethnicity and gender?

What if the number of positions was not limited to two for a single company or funding source and the positions for an area had the same funding source?

What if there was a dominance of vendors in those positions?

A person could also ask whether it is shameful. There is absolutely no relationship between the question asked (see quoted text) and this response. It is up to the reader to assess the state of spin.

Regards,
-sm
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]