trTeInstMode - HTM should be expanded consistently as
"History Trace Messaging" (instead of History Branch Messaging)
trTeProtocolMajor - "must be rejected by the trace tool" ->
"must be rejected by the trace tool that if it is only compliant
with version 1.0 of the N-trace protocol"
trTeProtocolMinor - "Different values..." ->
"When trTeProtocolMajor is 1, values other than 0 are considered
down-compatible extension and should be accepted by the trace tool"
(Qualification by trTeProtocolMajor is important)
trTeInstMode - the description seems to imply that HTM mode must be
allowed. Is that right? If the "must be allowed" was intended to
qualify "One or more..." then suggest rewriting as:
"One or more of the following values must be supported:
3: BTM (Branch Trace Messaging) mode
6: HTM (History Branch Messaging) mode"
Editorial:
trTeEnable - Remove parenthesis around "potentiall...Unit" ->
"Part of potentially shared Timestamp Unit. Controls generation of
the TSTAMP field. See..."
Other trTeData... -> must be 0?
trTeInstMode - HTM should be expanded consistently as "History Trace Messaging" (instead of History Branch Messaging)
trTeProtocolMajor - "must be rejected by the trace tool" -> "must be rejected by the trace tool that if it is only compliant with version 1.0 of the N-trace protocol"
trTeProtocolMinor - "Different values..." -> "When trTeProtocolMajor is 1, values other than 0 are considered down-compatible extension and should be accepted by the trace tool" (Qualification by trTeProtocolMajor is important)
trTeInstMode - the description seems to imply that HTM mode must be allowed. Is that right? If the "must be allowed" was intended to qualify "One or more..." then suggest rewriting as: "One or more of the following values must be supported: 3: BTM (Branch Trace Messaging) mode 6: HTM (History Branch Messaging) mode"
Editorial: