Re: [AVTCORE] [Technical Errata Reported] RFC4585 (3313)
Alan Clark <alan.d.clark@telchemy.com> Sun, 04 November 2012 18:39 UTC
Return-Path: <alan.d.clark@telchemy.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD4AC21F84C8 for <avt@ietfa.amsl.com>; Sun, 4 Nov 2012 10:39:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTTXZOkpYAoQ for <avt@ietfa.amsl.com>; Sun, 4 Nov 2012 10:39:42 -0800 (PST)
Received: from smtp01.myhostedservice.com (smtp01.myhostedservice.com [216.134.213.70]) by ietfa.amsl.com (Postfix) with ESMTP id 727D821F8475 for <avt@ietf.org>; Sun, 4 Nov 2012 10:39:41 -0800 (PST)
Received: from mail01.netplexity.net (172.29.251.14) by SMTP01.netplexity.local (172.29.211.9) with Microsoft SMTP Server id 14.0.722.0; Sun, 4 Nov 2012 13:39:18 -0500
Received: from [192.168.1.117] (UnknownHost [97.67.102.65]) by mail01.netplexity.net with SMTP; Sun, 4 Nov 2012 13:39:30 -0500
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Sun, 04 Nov 2012 13:39:19 -0500
From: Alan Clark <alan.d.clark@telchemy.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "jo@acm.org" <jo@acm.org>
Message-ID: <CCBC2087.4B932%alan.d.clark@telchemy.com>
Thread-Topic: [AVTCORE] [Technical Errata Reported] RFC4585 (3313)
Thread-Index: Ac26u7MYNJgu1VnSo0Clz6Y0dFGUtg==
In-Reply-To: <5096B598.3050900@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: "carsten.burmeister@eu.panasonic.com" <carsten.burmeister@eu.panasonic.com>, "stewe@stewe.org" <stewe@stewe.org>, "jose.rey@eu.panasonic.com" <jose.rey@eu.panasonic.com>, Org <avt@ietf.org>, "sato652@oki.com" <sato652@oki.com>
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC4585 (3313)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 04 Nov 2012 18:39:42 -0000
Magnus I also recommend that the proposed change is approved Regards Alan On 11/4/12 1:36 PM, "Magnus Westerlund" <magnus.westerlund@ericsson.com> wrote: > WG, > > I have reviewed this errata and it appears correct. I would recommend > that it is approved. Additional views on this? Please provide any > feedback within a week, after that I will instruct the ADs to approve > this errata. > > Cheers > > Magnus > > On 2012-08-11 16:57, RFC Errata System wrote: >> >> The following errata report has been submitted for RFC4585, >> "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based >> Feedback (RTP/AVPF)". >> >> -------------------------------------- >> You may review the report below and at: >> http://www.rfc-editor.org/errata_search.php?rfc=4585&eid=3313 >> >> -------------------------------------- >> Type: Technical >> Reported by: Mo Zanaty <mzanaty@cisco.com> >> >> Section: 4.2 >> >> Original Text >> ------------- >> rtcp-fb-ack-param = SP "rpsi" >> / SP "app" [SP byte-string] >> / SP token [SP byte-string] >> / ; empty >> >> >> Corrected Text >> -------------- >> rtcp-fb-ack-param = SP "rpsi" >> / SP "app" [SP byte-string] >> / SP token [SP byte-string] >> >> >> Notes >> ----- >> RFC 4585 defines and allows generic NACK (with no further parameters) but not >> generic ACK (which always requires further parameters). Section 4.2 says: >> ... >> Parameters MUST be provided to further distinguish different types >> of positive acknowledgement feedback. >> ... >> The feedback type "nack", without parameters, indicates use of the >> Generic NACK feedback format as defined in Section 6.2.1. >> ... >> The ABNF incorrectly allows nothing after "ack", implying that generic ACK is >> valid. Even the approved errata, which replaces the invalid empty alternate >> with optional [], still allows nothing after "ack". Note that recent interest >> in RTP congestion control (e.g. RMCAT BOF) may lead to defining a standard >> ACK. >> >> Instructions: >> ------------- >> This errata is currently posted as "Reported". If necessary, please >> use "Reply All" to discuss whether it should be verified or >> rejected. When a decision is reached, the verifying party (IESG) >> can log in to change the status and edit the report, if necessary. >> >> -------------------------------------- >> RFC4585 (draft-ietf-avt-rtcp-feedback-11) >> -------------------------------------- >> Title : Extended RTP Profile for Real-time Transport Control >> Protocol (RTCP)-Based Feedback (RTP/AVPF) >> Publication Date : July 2006 >> Author(s) : J. Ott, S. Wenger, N. Sato, C. Burmeister, J. Rey >> Category : PROPOSED STANDARD >> Source : Audio/Video Transport >> Area : Real-time Applications and Infrastructure >> Stream : IETF >> Verifying Party : IESG >> _______________________________________________ >> Audio/Video Transport Core Maintenance >> avt@ietf.org >> https://www.ietf.org/mailman/listinfo/avt >> >
- [AVTCORE] [Technical Errata Reported] RFC4585 (33… RFC Errata System
- Re: [AVTCORE] [Technical Errata Reported] RFC4585… Magnus Westerlund
- Re: [AVTCORE] [Technical Errata Reported] RFC4585… Alan Clark