Julian Reschke wrote: > > On 13.03.2010 16:13, bill manning wrote: > > ISO not withstanding, its still confusing if only because other cultures use > > yyddmm. If the IETF website used something like ISO-2010-01-02 maybe. > > > > This format is less confusing: 02jan2010 > > As far as I recall YYYY-MM-DD was specifically chosen because it's > unambiguous; no widely used date format uses hyphens and has the > ordering different. > > Just get used to it. And while at it, switch to 24h :-) IETF Meeting agendas have long been using 24h, but desperately lacks the GMT offset for the Meeting location. It would be highly appreciated if the secretariat put in the GMT timezone offset into the Meeting agenda that applies to the meeting location -- because that is what you need when want to listen to the audio stream or participate through jabber in real time remotely. The spring IETF is often very close to the winter time -> daylight savings time transition, and that date differs between countries. While it is simple and consistent within the EU, it appears to vary within the US. The IETF Meeting Agenda uses the "middle-endian" US date format, but fortunately spells out month names for disabiguation. -Martin _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf