From FIXwiki

FIX Data Type UTCTimestamp

Name	BaseType	First introduced	Deprecated
UTCTimestamp	String	FIX.4.2

string field representing Time/date combination represented in UTC (Universal Time Coordinated, also known as "GMT") in either YYYYMMDD-HH:MM:SS (whole seconds) or YYYYMMDD-HH:MM:SS.sss (milliseconds) format, colons, dash, and period required.

Valid values:

* YYYY = 0000-9999, MM = 01-12, DD = 01-31, HH = 00-23, MM = 00-59, SS = 00-60 (60 only if UTC leap second) (without milliseconds).

* YYYY = 0000-9999, MM = 01-12, DD = 01-31, HH = 00-23, MM = 00-59, SS = 00-60 (60 only if UTC leap second), sss=000-999 (indicating milliseconds).

Leap Seconds: Note that UTC includes corrections for leap seconds, which are inserted to account for slowing of the rotation of the earth. Leap second insertion is declared by the International Earth Rotation Service (IERS) and has, since 1972, only occurred on the night of Dec. 31 or Jun 30. The IERS considers March 31 and September 30 as secondary dates for leap second insertion, but has never utilized these dates. During a leap second insertion, a UTCTimestamp field may read "19981231-23:59:59", "19981231-23:59:60", "19990101-00:00:00". (see http://tycho.usno.navy.mil/leapsec.html)

Notes

Please post comments, clarifications, examples here. Click on the edit button on the right and away you go! 

Don't forget to refer to the FPL Discussion Groups to back up anything you write.
You will often find the authoritative statements on matters of FIX specification interpretation there.
Links from FIXwiki pages to relevant discussions on the FPL site are very valuable.

For example if you were writing a clarification on how to specify the "quantity" of an order in FIX, you might add the
following relevant link, http://www.fixprotocol.org/discuss/read/f5014573, to back up your points.