Document Action: 'How to Write an RTP Payload Format' to Informational RFC (draft-ietf-payload-rtp-howto-13.txt)

The IESG <> Thu, 23 January 2014 17:10 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id DC9561A00C5; Thu, 23 Jan 2014 09:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FlgYg58rOdx4; Thu, 23 Jan 2014 09:10:15 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id C25561A00C7; Thu, 23 Jan 2014 09:10:11 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'How to Write an RTP Payload Format' to Informational RFC (draft-ietf-payload-rtp-howto-13.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 23 Jan 2014 09:10:11 -0800
Cc: payload chair <>, payload mailing list <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Jan 2014 17:10:20 -0000

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:

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.


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: