Magnus,
It is not clear what you mean with adjusted. The RTP timestamp does need
to be specified by the RTP payload format. From RFC 3550, section 5.1:
<snip>
So if you could try to write out a definition for the RTP TS.
I believe this and other issues related to parameters and the offer/answer
model needs to go back into the T.38 spec. The other fields, as you pointed
out, are defined there. This draft is intended only to serve as the basis
for registering the MIME type for audio/t38.
I would even be favorable to removing the description of all of the
parameters and, again, just referencing the appropriate section(s) in T.38.
I feel like we're trying to solve two problems here, but the real work needs
to be done in T.38.
need to be documented here, as I do not believe it is documented in T.38.
However, the T.38-specific attributes that would appear on the a= line are
documented in T.38. It became clear to me as I was working on this that
T.38 needed more description of how these parameters should be used. I
would prefer to not try to solve that problem in two places and just raise
this as an issue to the ITU to fix.