[payload] RFC 8130 on RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced (MELPe) Codec
rfc-editor@rfc-editor.org Thu, 30 March 2017 21:40 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 0E16F1296E1; Thu, 30 Mar 2017 14:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zU8nu2h3jX6v; Thu, 30 Mar 2017 14:40:37 -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 82D611296DB; Thu, 30 Mar 2017 14:40:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6D845B80E5A; Thu, 30 Mar 2017 14:40:08 -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: <20170330214008.6D845B80E5A@rfc-editor.org>
Date: Thu, 30 Mar 2017 14:40:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/Nhk3b7Hy9eZCJuOyEYpPz-eYXj4>
Subject: [payload] RFC 8130 on RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced (MELPe) Codec
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: Thu, 30 Mar 2017 21:40:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8130
Title: RTP Payload Format for the
Mixed Excitation Linear Prediction Enhanced (MELPe)
Codec
Author: V. Demjanenko, D. Satterlee
Status: Standards Track
Stream: IETF
Date: March 2017
Mailbox: victor.demjanenko@vocal.com,
david.satterlee@vocal.com
Pages: 30
Characters: 64594
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-melpe-06.txt
URL: https://www.rfc-editor.org/info/rfc8130
DOI: 10.17487/RFC8130
This document describes the RTP payload format for the Mixed
Excitation Linear Prediction Enhanced (MELPe) speech coder. MELPe's
three different speech encoding rates and sample frame sizes are
supported. Comfort noise procedures and packet loss concealment are
described in detail.
This document is a product of the Audio/Video Transport Payloads Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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