[AVTCORE] [Errata Held for Document Update] RFC3711 (3712)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 15 February 2014 18:38 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE801A027B; Sat, 15 Feb 2014 10:38:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 e0BWHI_tXtGW; Sat, 15 Feb 2014 10:37:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA5F1A026E; Sat, 15 Feb 2014 10:37:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 517027FC2C9; Sat, 15 Feb 2014 10:37:57 -0800 (PST)
To: coien@cisco.com, mbaugher@cisco.com, elisabetta.carrara@ericsson.com, mcgrew@cisco.com, mats.naslund@ericsson.com, karl.norrman@ericsson.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140215183757.517027FC2C9@rfc-editor.org>
Date: Sat, 15 Feb 2014 10:37:57 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/yBSFvn38qSBb69--aXKOd5nhR1U
X-Mailman-Approved-At: Sun, 16 Feb 2014 14:47:04 -0800
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, avt@ietf.org
Subject: [AVTCORE] [Errata Held for Document Update] RFC3711 (3712)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 15 Feb 2014 18:38:01 -0000
The following errata report has been held for document update for RFC3711, "The Secure Real-time Transport Protocol (SRTP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3711&eid=3712 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Christian S Oien <coien@cisco.com> Date Reported: 2013-08-27 Held by: Richard Barnes (IESG) Section: 4.3.2 Original Text ------------- Replace the SRTP index by the 32-bit quantity: 0 || SRTCP index (i.e., excluding the E-bit, replacing it with a fixed 0-bit), and use <label> = 0x03 for the SRTCP encryption key, <label> = 0x04 for the SRTCP authentication key, and, <label> = 0x05 for the SRTCP salting key. Corrected Text -------------- Replace the SRTP index by the 48-bit quantity: 000...0 || 0 || SRTCP index (i.e., excluding the E-bit, replacing it with a fixed 0-bit and padding the result so that it becomes 48 bits wide to match the size of the SRTP index). Since this quantity and the SRTP index are both 48 bits wide, the labels are all located in the same octet in the IV. The labels for the derivations of the SRTCP keys are as follows: <label> = 0x03 for the SRTCP encryption key, <label> = 0x04 for the SRTCP authentication key, and, <label> = 0x05 for the SRTCP salting key. Notes ----- Replacing with a 32-bit quantity means that the DIV operator will yield a 32-bit quantity. Following the specification of key_id for SRTCP the <label> will have 32 bits to its right when XOR'ing with master_salt. The majority of implementations, including libsrtp, invokes this XOR with the <label> at the same position as for SRTP. According to the specification this should be done 16 bits to the right of this, when invoking for SRTCP. -------------------------------------- RFC3711 (draft-ietf-avt-srtp-09) -------------------------------------- Title : The Secure Real-time Transport Protocol (SRTP) Publication Date : March 2004 Author(s) : M. Baugher, D. McGrew, M. Naslund, E. Carrara, K. Norrman Category : PROPOSED STANDARD Source : Audio/Video Transport Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG
- [AVTCORE] [Technical Errata Reported] RFC3711 (37… RFC Errata System
- Re: [AVTCORE] [Technical Errata Reported] RFC3711… Karl Norrman
- Re: [AVTCORE] [Technical Errata Reported] RFC3711… Richard Barnes
- [AVTCORE] [Errata Held for Document Update] RFC37… RFC Errata System