RFC 9993: RTP Payload Format for Haptics

This memo specifies an RTP payload format for MPEG-I haptic data. A haptic media stream is composed of MPEG-I Haptic Stream (MIHS) units including a MIHS unit…

Read RFC 9993 on the RFC Editor

Outgoing relationships (17 related RFCs)

Updates, Normative reference — RFC 9695: The 'haptics' Top-Level Media Type
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3550: RTP: A Transport Protocol for Real-Time Applications
Normative reference — RFC 3264: An Offer/Answer Model with Session Description Protocol (SDP)
Normative reference — RFC 8866: SDP: Session Description Protocol
Informative reference — RFC 4303: IP Encapsulating Security Payload (ESP)
Informative reference — RFC 3711: The Secure Real-time Transport Protocol (SRTP)
Informative reference — RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control
Informative reference — RFC 4585: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)
Informative reference — RFC 7296: Internet Key Exchange Protocol Version 2 (IKEv2)
Informative reference — RFC 5124: Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)
Informative reference — RFC 7201: Options for Securing RTP Sessions
Informative reference — RFC 5104: Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)
Informative reference — RFC 7202: Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
Informative reference — RFC 2736: Guidelines for Writers of RTP Payload Format Specifications
Informative reference — RFC 8088: How to Write an RTP Payload Format