Skip to content

Commit

Permalink
Merge pull request #34 from cdh4u/cdh4u-reliability-note
Browse files Browse the repository at this point in the history
Note added regarding reliable and ordered transmission
  • Loading branch information
cdh4u committed Sep 30, 2019
2 parents bca4745 + fdd8aec commit 5dffa6f
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion draft-ietf-mmusic-t140-usage-data-channel.xml
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,17 @@
<c>Label</c>
<c>See <xref target="sec.sdp.dcmap"/> and <xref target="sec.gw"/></c>
</texttable>
<t>
NOTE: T.140 requires the transport channel to provide transmission of real-time text without
duplication and in original order. Therefore, T.140 does not specify reliable and ordered
transmission of T.140 data on the application layer. Instead, when RTP based transport is used,
the RTP sequence number is used to detect packet loss and out-of-order packets, and a redundancy
mechanism using the RTP timestamp is used to achieve reliable delivery of T.140 data. By using
the WebRTC data channel reliable and in-order transmission features <xref target="I-D.ietf-rtcweb-data-channel"/>
for the T.140 data channel, there is no need for a redundancy mechanism or a mechanism to detect
data loss and out-of-order delivery on the application level. The latency characteristics of the
T.140 data channel is also regarded to be sufficient to meet the application requirements of T.140.
</t>
</section>

<section anchor="sec.sdp" title="SDP Considerations">
Expand Down Expand Up @@ -841,7 +852,7 @@ Answer:
<t>
Thomas Belling provided useful comments on the initial (pre-submission) version
of the draft. Gunnar Hellstrom provided comments and text on the draft. Paul
Kyzivat provides comments on the draft.
Kyzivat and Bernard Aboba provided comments on the draft.
</t>
</section>
</middle>
Expand Down

0 comments on commit 5dffa6f

Please sign in to comment.