RFC 7197 on Duplication Delay Attribute in the Session Description Protocol
rfc-editor@rfc-editor.org Fri, 25 April 2014 18:42 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7558E1A0687; Fri, 25 Apr 2014 11:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.174
X-Spam-Level:
X-Spam-Status: No, score=-102.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 dlntOAqIKsOK; Fri, 25 Apr 2014 11:42:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id F181D1A067D; Fri, 25 Apr 2014 11:42:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8791C1801A2; Fri, 25 Apr 2014 11:41:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7197 on Duplication Delay Attribute in the Session Description Protocol
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140425184101.8791C1801A2@rfc-editor.org>
Date: Fri, 25 Apr 2014 11:41:01 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/7zl1KmH_1hzY_mj4r0BLDdIltms
Cc: drafts-update-ref@iana.org, mmusic@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 18:42:04 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7197
Title: Duplication Delay Attribute in the
Session Description Protocol
Author: A. Begen,
Y. Cai,
H. Ou
Status: Standards Track
Stream: IETF
Date: April 2014
Mailbox: abegen@cisco.com,
yiqunc@microsoft.com,
hou@cisco.com
Pages: 11
Characters: 22559
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mmusic-delayed-duplication-03.txt
URL: http://www.rfc-editor.org/rfc/rfc7197.txt
A straightforward approach to provide protection against packet
losses due to network outages with a longest duration of T time units
is to duplicate the original packets and send each copy separated in
time by at least T time units. This approach is commonly referred to
as "time-shifted redundancy", "temporal redundancy", or simply
"delayed duplication". This document defines an attribute to
indicate the presence of temporally redundant media streams and the
duplication delay in the Session Description Protocol.
This document is a product of the Multiparty Multimedia Session Control 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
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 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