[Sip] [Editorial Errata Reported] RFC5479 (2125)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 05 April 2010 18:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 06CC53A6888 for <sip@core3.amsl.com>;
Mon, 5 Apr 2010 11:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.393
X-Spam-Level:
X-Spam-Status: No, score=-2.393 tagged_above=-999 required=5 tests=[AWL=0.207,
BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bviYskDuXui7 for
<sip@core3.amsl.com>; Mon, 5 Apr 2010 11:04:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by
core3.amsl.com (Postfix) with ESMTP id 3AB153A659A for <sip@ietf.org>;
Mon, 5 Apr 2010 11:04:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D9DD3E07A3;
Mon, 5 Apr 2010 11:04:19 -0700 (PDT)
To: dwing@cisco.com, steffen.fries@siemens.com, Hannes.Tschofenig@nsn.com,
audet@nortel.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com,
dean.willis@softarmor.com, drage@alcatel-lucent.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20100405180419.D9DD3E07A3@rfc-editor.org>
Date: Mon, 5 Apr 2010 11:04:19 -0700 (PDT)
Cc: sip@ietf.org, ah@TR-Sys.de, rfc-editor@rfc-editor.org
Subject: [Sip] [Editorial Errata Reported] RFC5479 (2125)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2010 18:04:22 -0000
The following errata report has been submitted for RFC5479, "Requirements and Analysis of Media Security Management Protocols". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5479&eid=2125 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes <ah@TR-Sys.de> Section: A.4.3 Original Text ------------- | In SRTP, a cryptographic context is defined as the SSRC, destination | network address, and destination transport port number. Whereas RTP, | a flow is defined as the destination network address and destination transport port number. This results in a problem -- how to communicate the SSRC so that the SSRC can be used for the cryptographic context. Corrected Text -------------- | In SRTP, a cryptographic context is defined by the SSRC, destination | network address, and destination transport port number, whereas in RTP, | a flow is defined by the destination network address and destination transport port number. This results in a problem -- how to communicate the SSRC so that the SSRC can be used for the cryptographic context. Notes ----- Rationale: clarification/language improvement -- keep for update! 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. -------------------------------------- RFC5479 (draft-ietf-sip-media-security-requirements-09) -------------------------------------- Title : Requirements and Analysis of Media Security Management Protocols Publication Date : April 2009 Author(s) : D. Wing, Ed., S. Fries, H. Tschofenig, F. Audet Category : INFORMATIONAL Source : Session Initiation Protocol Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG
- [Sip] [Editorial Errata Reported] RFC5479 (2125) RFC Errata System