[Dime] Protocol Action: 'Diameter IKEv2 SK: Shared Key-based Support for IKEv2 Server to Diameter Server Interaction' to Proposed Standard (draft-ietf-dime-ikev2-psk-diameter-11.txt)

The IESG <iesg-secretary@ietf.org> Wed, 04 January 2012 15:52 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD76E21F85CD; Wed, 4 Jan 2012 07:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level:
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DopZya24goDU; Wed, 4 Jan 2012 07:52:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F080E21F85D6; Wed, 4 Jan 2012 07:52:33 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120104155233.30398.17979.idtracker@ietfa.amsl.com>
Date: Wed, 04 Jan 2012 07:52:33 -0800
Cc: dime mailing list <dime@ietf.org>, dime chair <dime-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Dime] Protocol Action: 'Diameter IKEv2 SK: Shared Key-based Support for IKEv2 Server to Diameter Server Interaction' to Proposed Standard (draft-ietf-dime-ikev2-psk-diameter-11.txt)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2012 15:52:35 -0000

The IESG has approved the following document:
- 'Diameter IKEv2 SK: Shared Key-based Support for IKEv2 Server to
   Diameter Server Interaction'
  (draft-ietf-dime-ikev2-psk-diameter-11.txt) as a Proposed Standard

This document is the product of the Diameter Maintenance and Extensions
Working Group.

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/




Technical Summary

  The Internet Key Exchange protocol version 2 (IKEv2) is a component
   of the IPsec architecture and is used to perform mutual
   authentication as well as to establish and to maintain IPsec security
   associations (SAs) between the respective parties.  IKEv2 supports
   several different authentication mechanisms, such as the Extensible
   Authentication Protocol (EAP), certificates, and pre-shared keys.

   Diameter interworking for Mobile IPv6 between the Home Agent, as a
   Diameter client, and the Diameter server has been specified.
   However, that specification focused on the usage of EAP and did not
   include support for pre-shared key based authentication available
   with IKEv2.  This document specifies IKEv2 server, as a Diameter
   client, to the Diameter server communication for IKEv2 with pre-
   shared key based authentication.

Working Group Summary

   There is Dime WG consensus behind the document. The document was discussed for more than one year in the 
   WG and the document captures the results of the collaborative WG work.

Document Quality

   The document is complete, straightforward, simple and well-written. 

Personnel

   Lionel Morand is the Document Shepherd for this document. Dan Romascanu is the Responsible Area Director.  

IESG Note

  Please change all occurances of TBD(x) with the IANA assignment throughout the entire document. Since these are 
  scattered throughout the doc, the intent may not be obvious to them.