The IESG has approved the following document:
- 'RTP Payload Format for Haptics'
  (draft-ietf-avtcore-rtp-haptics-13.txt) as Proposed Standard

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

The IESG contact persons are Gorry Fairhurst and Mike Bishop.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-haptics/




Technical Summary

   This memo describes an RTP payload format for the MPEG-I haptic data.
   A haptic media stream is composed of MIHS units including a
   MIHS(MPEG-I Haptic Stream) 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, registered with IANA in RFC9695, did not include any required
   or optional parameters.  This memo updates RFC9695 and the haptics/
   hmpg registration to add optional parameters.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

Personnel

   The Document Shepherd for this document is Marius Kleidl. The
   Responsible Area Director is Gorry Fairhurst.

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

Reply via email to