RFC 6278 on Use of Static-Static Elliptic Curve Diffie-Hellman Key Agreement in Cryptographic Message Syntax

rfc-editor@rfc-editor.org Fri, 10 June 2011 17:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 925F111E8173 for <ietf-announce@ietfa.amsl.com>; Fri, 10 Jun 2011 10:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.887
X-Spam-Level:
X-Spam-Status: No, score=-105.887 tagged_above=-999 required=5 tests=[AWL=-0.962, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, SARE_OBFU_ALL=0.751, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isx2do0YbZMN for <ietf-announce@ietfa.amsl.com>; Fri, 10 Jun 2011 10:27:58 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [64.170.98.47]) by ietfa.amsl.com (Postfix) with ESMTP id 672F111E8163 for <ietf-announce@ietf.org>; Fri, 10 Jun 2011 10:27:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 55E0898C4FA; Fri, 10 Jun 2011 10:27:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6278 on Use of Static-Static Elliptic Curve Diffie-Hellman Key Agreement in Cryptographic Message Syntax
From: rfc-editor@rfc-editor.org
Message-Id: <20110610172752.55E0898C4FA@rfc-editor.org>
Date: Fri, 10 Jun 2011 10:27:52 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 10 Jun 2011 17:27:59 -0000

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

        
        RFC 6278

        Title:      Use of Static-Static Elliptic Curve 
                    Diffie-Hellman Key Agreement in Cryptographic Message 
                    Syntax 
        Author:     J. Herzog, R. Khazan
        Status:     Informational
        Stream:     IETF
        Date:       June 2011
        Mailbox:    jherzog@ll.mit.edu, 
                    rkh@ll.mit.edu
        Pages:      16
        Characters: 36593
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-herzog-static-ecdh-06.txt

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

This document describes how to use the 'static-static Elliptic Curve
Diffie-Hellman key-agreement scheme (i.e., Elliptic Curve Diffie-
Hellman where both participants use static Diffie-Hellman values)
with the Cryptographic Message Syntax.  In this form of key
agreement, the Diffie-Hellman values of both the sender and receiver
are long-term values contained in certificates.  This document is not 
an Internet Standards Track specification; it is published for 
informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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