Time and direction are independent
04A session schedule and a media direction attribute answer different questions.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5.9 ↗
RFC 8866 · § 5.9EXAMPLE
3 / 3
03
Two separate facts
An active session schedule does not imply bidirectional media.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
t= uses NTP-format seconds for start and stop times.
- t= uses NTP-format seconds for start and stop times.
- t=0 0 describes an unbounded session time.
- sendrecv, sendonly, recvonly, and inactive describe media direction under their scope.
The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy