RFC 5669 on The SEED Cipher Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)

rfc-editor@rfc-editor.org Tue, 31 August 2010 06:04 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11D3F3A690A; Mon, 30 Aug 2010 23:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.036
X-Spam-Level:
X-Spam-Status: No, score=-102.036 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 pspWxgGxOp74; Mon, 30 Aug 2010 23:04:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 90C503A68AD; Mon, 30 Aug 2010 23:04:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C24BFE06AF; Mon, 30 Aug 2010 23:05:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5669 on The SEED Cipher Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)
From: rfc-editor@rfc-editor.org
Message-Id: <20100831060522.C24BFE06AF@rfc-editor.org>
Date: Mon, 30 Aug 2010 23:05:22 -0700 (PDT)
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 31 Aug 2010 06:04:53 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5669

        Title:      The SEED Cipher Algorithm and 
                    Its Use with the Secure Real-Time 
                    Transport Protocol (SRTP) 
        Author:     S. Yoon, J. Kim,
                    H. Park, H. Jeong,
                    Y. Won
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    seokung@kisa.or.kr, 
                    seopo@kisa.or.kr, 
                    hrpark@kisa.or.kr,  hcjung@kisa.or.kr, 
                    yjwon@kisa.or.kr
        Pages:      13
        Characters: 24918
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-seed-srtp-14.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5669.txt

This document describes the use of the SEED block cipher algorithm in
the Secure Real-time Transport Protocol (SRTP) for providing
confidentiality for Real-time Transport Protocol (RTP) traffic
and for the control traffic for RTP, the Real-time Transport Control
Protocol (RTCP).  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

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/rfcsearch.html.
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