RFC 8732 on Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2
rfc-editor@rfc-editor.org Fri, 28 February 2020 22:54 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 29C6D3A1FD4; Fri, 28 Feb 2020 14:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GODV9mZWUP7T; Fri, 28 Feb 2020 14:54:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D858D3A1FCE; Fri, 28 Feb 2020 14:54:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 07A26F40729; Fri, 28 Feb 2020 14:53:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8732 on Generic Security Service Application Program Interface (GSS-API) Key Exchange with SHA-2
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200228225351.07A26F40729@rfc-editor.org>
Date: Fri, 28 Feb 2020 14:53:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/LqYjgBC05NYogMwaQa9P2NWeEBI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Feb 2020 22:54:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8732
Title: Generic Security Service Application Program
Interface (GSS-API) Key Exchange with SHA-2
Author: S. Sorce,
H. Kario
Status: Standards Track
Stream: IETF
Date: February 2020
Mailbox: simo@redhat.com,
hkario@redhat.com
Pages: 12
Updates: RFC 4462
I-D Tag: draft-ietf-curdle-gss-keyex-sha2-10.txt
URL: https://www.rfc-editor.org/info/rfc8732
DOI: 10.17487/RFC8732
This document specifies additions and amendments to RFC 4462. It
defines a new key exchange method that uses SHA-2 for integrity and
deprecates weak Diffie-Hellman (DH) groups. The purpose of this
specification is to modernize the cryptographic primitives used by
Generic Security Service (GSS) key exchanges.
This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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