A new Request for Comments is now available in online RFC libraries.

        RFC 9993

        Title:      RTP Payload Format for Haptics
        Author:     HS Yang,
                    X. de Foy
        Status:     Proposed Standard
        Stream:     IETF
        Date:       May 2026
        Mailbox:    [email protected],
                    [email protected]
        Pages:      22
        Updates:    RFC 9695

        I-D Tag:    draft-ietf-avtcore-rtp-haptics-14

        URL:        https://www.rfc-editor.org/info/rfc9993

        DOI:        10.17487/RFC9993

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 header and zero or more MIHS packets. The RTP payload header format allows 
for packetization of a MIHS unit in an RTP packet payload as well as 
fragmentation of a MIHS unit into multiple RTP packets. The original subtype 
registration for 'haptics/hmpg' (RFC 9695) did not include any required or 
optional parameters. This memo updates RFC 9695 and the 'haptics/hmpg' 
registration to add optional parameters. It also provides Session Description 
Protocol (SDP) usage information for the 'haptics' media type.

This document is a product of the Audio/Video Transport Core Maintenance 
Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to