UTC Time reference in RFC 2252

["Mark Hinckley" <MHINCKLEY@novell.com>]

RFC 2252 states:
"6.31. UTC Time

  ( 1.3.6.1.4.1.1466.115.121.1.53 DESC 'UTC Time' )

  Values in this syntax are encoded as if they were printable  strings
  with the strings containing a UTCTime value.  This = is  historical; new
  attribute definitions SHOULD use GeneralizedTime=   instead."

Kurt Z. added following in his ldapv3bis-rfc2252 doc
"   // This syntax and attributes/rules which use it should = be  marked
    // OBSOLETE."


How strongly worded should the prohibition against using UTC Time = be?

How about the following:

6.31. UTC Time

  ( 1.3.6.1.4.1.1466.115.121.1.53 DESC 'UTC Time' )

  This syntax is OBSOLETE.  Any attribute definitions = and/or  rules that use
  this syntax  should also be marked OBSOLETE.   = This  syntax is included
  here only for historical reference.   Any new = attribute  definition MUST NOT
  use this syntax, but SHOULD use GeneralizedTime instead.