Subject: Re: [AVTCORE] RFC 7007 on Update to Remove DVI4 from the Recommended Codecs for the RTP Profile for Audio and Video Conferences with Minimal Control (RTP/AVP)

From: RFC Editor <[email-masked]>
Date: Wed, 4 Sep 2013 08:30:13 -0700

Resending the announcement.  RFC 7007 has been available since it
was originally announced.

On Wed, Aug 28, 2013 at 05:07:03PM -0700, RFC Editor wrote:
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 7007
> 
>         Title:      Update to Remove DVI4 from 
>                     the Recommended Codecs for the RTP 
>                     Profile for Audio and Video Conferences 
>                     with Minimal Control (RTP/AVP) 
>         Author:     T. Terriberry
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       August 2013
>         Mailbox:    [email-masked]
>         Pages:      4
>         Characters: 6777
>         Updates:    RFC 3551
> 
>         I-D Tag:    draft-ietf-avtcore-avp-codecs-03.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc7007.txt
> 
> The RTP Profile for Audio and Video Conferences with Minimal Control
> (RTP/AVP) is the basis for many other profiles, such as the Secure
> Real-time Transport Protocol (RTP/SAVP), the Extended RTP Profile for
> Real-time Transport Control Protocol (RTCP)-Based Feedback
> (RTP/AVPF), and the Extended Secure RTP Profile for RTCP-Based
> Feedback (RTP/SAVPF).  This document updates RFC 3551, the RTP/AVP
> profile (and by extension, the profiles that build upon it), to
> reflect changes in audio codec usage since that document was
> originally published.
> 
> 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 Internet
> Official Protocol Standards (STD 1) 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
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [email-masked].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
>