[MEDIACTRL] [Technical Errata Reported] RFC6230 (7596)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 11 August 2023 12:53 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: mediactrl@ietfa.amsl.com
Delivered-To: mediactrl@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29EE6C14CE4B for <mediactrl@ietfa.amsl.com>; Fri, 11 Aug 2023 05:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.533
X-Spam-Level:
X-Spam-Status: No, score=0.533 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZzsShg8OMce for <mediactrl@ietfa.amsl.com>; Fri, 11 Aug 2023 05:53:22 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C4E8C14CE4C for <mediactrl@ietf.org>; Fri, 11 Aug 2023 05:53:22 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3092CAB8A5; Fri, 11 Aug 2023 05:53:22 -0700 (PDT)
To: chris@ns-technologies.com, timm@rainwillow.com, smcg.stds01@mcglashan.org, superuser@gmail.com, francesca.palombini@ericsson.com, worley@ariadne.com, eburger@standardstrack.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: kim.hermansson@infracom.se, mediactrl@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230811125322.3092CAB8A5@rfcpa.amsl.com>
Date: Fri, 11 Aug 2023 05:53:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mediactrl/IZpSP2-GxZfOZwiruaMJdVMwhpU>
Subject: [MEDIACTRL] [Technical Errata Reported] RFC6230 (7596)
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mediactrl/>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Aug 2023 12:53:26 -0000

The following errata report has been submitted for RFC6230,
"Media Control Channel Framework".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7596

--------------------------------------
Type: Technical
Reported by: Kim Hermansson <kim.hermansson@infracom.se>

Section: 9.1

Original Text
-------------
ext-header = hname ":" SP hval CRLF

Corrected Text
--------------
ext-header = hname ":" SP hval

Notes
-----
Same as errata 1954 (RFC 4975); the rule:

headers = header-name CRLF

already suffixes every header with a CRLF. The result is that the extension headers are followed by 2 CRLFs, introducing empty lines inside the header segment. This appears to be unintended, since none of the other headers have a terminating CRLF in their production rules, only the ext-header.

Instructions:
-------------
This erratum 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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6230 (draft-ietf-mediactrl-sip-control-framework-12)
--------------------------------------
Title               : Media Control Channel Framework
Publication Date    : May 2011
Author(s)           : C. Boulton, T. Melanchuk, S. McGlashan
Category            : PROPOSED STANDARD
Source              : Media Server Control
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG