Protocol Action: 'S/MIME AES Requirement for SIP' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 20 April 2004 12:57 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14776 for <ietf-announce-archive@ietf.org>; Tue, 20 Apr 2004 08:57:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFuoI-00065S-Vv for ietf-announce-archive@ietf.org; Tue, 20 Apr 2004 08:57:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFunD-0005iZ-00 for ietf-announce-archive@ietf.org; Tue, 20 Apr 2004 08:56:04 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFumC-0005NI-00 for ietf-announce-archive@ietf.org; Tue, 20 Apr 2004 08:55:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFuVt-0007nF-FE; Tue, 20 Apr 2004 08:38:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFhdr-0005UM-Hb for ietf-announce@optimus.ietf.org; Mon, 19 Apr 2004 18:53:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18720 for <ietf-announce@ietf.org>; Mon, 19 Apr 2004 18:53:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFhdo-0004hw-CQ for ietf-announce@ietf.org; Mon, 19 Apr 2004 18:53:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFhct-0004Ti-00 for ietf-announce@ietf.org; Mon, 19 Apr 2004 18:52:32 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFhc5-0004Fh-00; Mon, 19 Apr 2004 18:51:41 -0400
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BFhLe-0006vi-EB; Mon, 19 Apr 2004 18:34:42 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, sip mailing list <sip@ietf.org>, sip chair <dean.willis@softarmor.com>, sip chair <rohan@cisco.com>
Subject: Protocol Action: 'S/MIME AES Requirement for SIP' to Proposed Standard
Message-Id: <E1BFhLe-0006vi-EB@optimus.ietf.org>
Date: Mon, 19 Apr 2004 18:34:42 -0400
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'S/MIME AES Requirement for SIP '
   <draft-ietf-sip-smime-aes-01.txt> as a Proposed Standard

This document is the product of the Session Initiation Protocol Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary
 
   RFC3261 currently specifies 3DES as the required minimum ciphersuite
   for implementations of S/MIME in SIP.  This document updates the
   normative guidance of RFC3261 to require the Advanced Encryption
   Standard (AES) for S/MIME.
 
Working Group Summary
 
   The Working Group supported this document.  It was adopted immediately
   on its initial airing.  It was gated by progress on S/MIME support.
 
 Protocol Quality
 
   General S/MIME implementation for SIP has been fairly slow to progress.  
   Some prototype implementations have been tested at the SIP 
   interoperability events, without testing their cryptography to date.

The specification was reviewed for the IESG by Allison Mankin and Russ
Housley.


RFC Editor Notes 

OLD:
   S/MIME implementations MUST at a minimum support RSA as a digital
   signature algorithm, SHA1 as a digest algorithm, and AES as an
   encryption algorithm (as specified in [4].  For key wrap, S/MIME
   implementations MUST support the AES Key Wrap Algorithm ([5]).  

NEW:
   S/MIME implementations MUST at a minimum support RSA as a digital
   signature algorithm and SHA1 as a digest algorithm [ xx],  and AES as
   an encryption algorithm (as specified in [yy]).  For key transport, 
   S/MIME implementations MUST support RSA key transport as specified
   in section 4.2.1 of [xx].  

RFC Editor, replace [xx] with the citation number of a reference to RFC 3370
added to the Normative References.  Replace [yy] with the citation number
of a reference to RFC 3565 added to the Normative References.

3370 Cryptographic Message Syntax (CMS) Algorithms. R. Housley.
    August 2002.

3565 Use of the Advanced Encryption Standard (AES) Encryption
     Algorithm in Cryptographic Message Syntax (CMS). J. Schaad.
     July 2003.

****

Abstract

OLD:
  required minimum ciphersuite
NEW:
  mandatory-to-implement ciphersuite

****

Section 4

OLD:
  Triples-DES

NEW:
  Triple-DES

****

   Several places: Adjust line breaks to avoid funny
   line break placement --  Avoid  S/ <CR><LF> MIME


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce