[payload] RFC 8088 on How to Write an RTP Payload Format
rfc-editor@rfc-editor.org Wed, 03 May 2017 01:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BC212EB49; Tue, 2 May 2017 18:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.503
X-Spam-Level:
X-Spam-Status: No, score=-1.503 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id My82EuUe83IR; Tue, 2 May 2017 18:36:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DFC7129C11; Tue, 2 May 2017 18:33:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 44AABB813A4; Tue, 2 May 2017 18:33:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, payload@ietf.org
Message-Id: <20170503013325.44AABB813A4@rfc-editor.org>
Date: Tue, 02 May 2017 18:33:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/IFUIPtHt6BBeVBYyFQN15JDxCNk>
Subject: [payload] RFC 8088 on How to Write an RTP Payload Format
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 May 2017 01:36:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8088
Title: How to Write an RTP
Payload Format
Author: M. Westerlund
Status: Informational
Stream: IETF
Date: May 2017
Mailbox: magnus.westerlund@ericsson.com
Pages: 65
Characters: 164369
Updates: RFC 2736
I-D Tag: draft-ietf-payload-rtp-howto-14.txt
URL: https://www.rfc-editor.org/info/rfc8088
DOI: 10.17487/RFC8088
This document contains information on how best to write an RTP
payload format specification. It provides reading tips, design
practices, and practical tips on how to produce an RTP payload format
specification quickly and with good results. A template is also
included with instructions.
This document is a product of the Audio/Video Transport Payloads Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC