How to Write an RTP Payload Format
RFC 8088

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    payload mailing list <payload@ietf.org>,
    payload chair <payload-chairs@tools.ietf.org>
Subject: Document Action: 'How to Write an RTP Payload Format' to Informational RFC (draft-ietf-payload-rtp-howto-13.txt)

The IESG has approved the following document:
- 'How to Write an RTP Payload Format'
  (draft-ietf-payload-rtp-howto-13.txt) as Informational RFC

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

The IESG contact persons are Richard Barnes and Gonzalo Camarillo.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-howto/


Technical Summary

This document describes guidelines for people who would like to write an RTP payload format specification. There have been changes in this process and this document describes the latest. A document template is also provided.

Working Group Summary

The document received several reviews on various parts and as a whole. There have been quite a big number of improvements over time, both editorially and technically.

Document Quality

This document is informational, so does not require an implementation. Several people who have written payload format specs before reviewed the material carefully.

Personnel

Ali Begen is the document shepherd and Richard Barnes is the responsible AD.

RFC Editor Note

Please hold this document until the following documents are ready for publication:
   [I-D.ietf-avt-srtp-not-mandatory]
   [I-D.ietf-avtcore-rtp-circuit-breakers]
   [I-D.ietf-avtcore-rtp-security-options]