2822upd-04 definition of terms needed

2822upd-04 uses several terms in ways which may or may not conflict
with related specifications and documents; unfortunately, as 2822upd-04
does not define these terms, it is unclear whether or not there are in
fact conflicts.  Moreover, lacking precise definitions of these terms, it
is not clear exactly what the specifications using these terms in the
draft mean.

The terms and sections where they are used are:

structured field bodies     as used in section 2.2.2 and later;
specifically, is this definition meant to apply to (extension) fields
defined in other specifications?

local time     as used in section 3.3.  Specifically, what is "local time"
if a (human) message composer is sitting in an airplane composing a
message via a telnet link to a (ground-based) host computer which will
then send the message via a separate, remote submission server?  [By
the way, the airplane is crossing over the (North) polar ice cap as
the composer travels an intercontinental great circle route to his
destination.]

unlimited     w.r.t. the number of optional-fields as specified in
section 3.6.  Specifically, does it mean that the specification for
extension fields is not allowed to specify a maximum (or minimum, for
that matter) field count for extension fields?

creator      as used in sections 1.2.3 and 3.6.1.

user      as used in sections 3.6.1 and 3.6.6.

automatic (and related terms)    as used in sections 3.6.3 and 3.6.6.

final form       as used in section 3.6.1.

reply (and related terms)     as used in sections 3.6.2, 3.6.3, and 3.6.6.

sender        as used in sections 3.4 and 3.6.4.

reintroduced       as used in section 3.6.6.