[AVTCORE] RFC 8817 on RTP Payload Format for Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) Codec

rfc-editor@rfc-editor.org Tue, 18 August 2020 00:14 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 213103A1490; Mon, 17 Aug 2020 17:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 5zOgtyJpc0NL; Mon, 17 Aug 2020 17:14:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D46A33A148F; Mon, 17 Aug 2020 17:14:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 049C3F40767; Mon, 17 Aug 2020 17:14:26 -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, avt@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200818001426.049C3F40767@rfc-editor.org>
Date: Mon, 17 Aug 2020 17:14:26 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/spN2qXYgRwYB7-yB9kEl46JNVg0>
Subject: [AVTCORE] =?utf-8?q?RFC_8817_on_RTP_Payload_Format_for_Tactical_?= =?utf-8?q?Secure_Voice_Cryptographic_Interoperability_Specification_=28TS?= =?utf-8?q?VCIS=29_Codec?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2020 00:14:42 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8817

        Title:      RTP Payload Format for Tactical Secure 
                    Voice Cryptographic Interoperability 
                    Specification (TSVCIS) Codec 
        Author:     V. Demjanenko, 
                    J. Punaro,
                    D. Satterlee
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2020
        Mailbox:    victor.demjanenko@vocal.com, 
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-payload-tsvcis-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8817

        DOI:        10.17487/RFC8817

This document describes the RTP payload format for the Tactical
Secure Voice Cryptographic Interoperability Specification (TSVCIS)
speech coder.  TSVCIS is a scalable narrowband voice coder supporting
varying encoder data rates and fallbacks.  It is implemented as an
augmentation to the Mixed Excitation Linear Prediction Enhanced
(MELPe) speech coder by conveying additional speech coder parameters
to enhance voice quality.  TSVCIS augmented speech data is processed
in conjunction with its temporally matched Mixed Excitation Linear
Prediction (MELP) 2400 speech data.  The RTP packetization of TSVCIS
and MELPe speech coder data is described in detail.

This document is a product of the Audio/Video Transport Core Maintenance 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

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