RFC 8009 on AES Encryption with HMAC-SHA2 for Kerberos 5

rfc-editor@rfc-editor.org Fri, 28 October 2016 05:29 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 4E0E8129631; Thu, 27 Oct 2016 22:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.033
X-Spam-Level:
X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 r0NI3N40ACw4; Thu, 27 Oct 2016 22:29:37 -0700 (PDT)
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 199A91296A8; Thu, 27 Oct 2016 22:29:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DD790B81236; Thu, 27 Oct 2016 22:29:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8009 on AES Encryption with HMAC-SHA2 for Kerberos 5
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161028052935.DD790B81236@rfc-editor.org>
Date: Thu, 27 Oct 2016 22:29:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/vaYnSytkUoEwqzrZV_beONhp5fQ>
Cc: kitten@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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 Oct 2016 05:29:44 -0000

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

        
        RFC 8009

        Title:      AES Encryption with HMAC-SHA2 for 
                    Kerberos 5 
        Author:     M. Jenkins, M. Peck,
                    K. Burgin
        Status:     Informational
        Stream:     IETF
        Date:       October 2016
        Mailbox:    mjjenki@tycho.ncsc.mil, 
                    mpeck@mitre.org, 
                    kelley.burgin@gmail.com
        Pages:      19
        Characters: 34935
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-kitten-aes-cts-hmac-sha2-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8009

        DOI:        http://dx.doi.org/10.17487/RFC8009

This document specifies two encryption types and two corresponding checksum
types for Kerberos 5.  The new types use AES in CTS mode (CBC mode with
ciphertext stealing) for confidentiality and HMAC with a SHA-2 hash for
integrity.

This document is a product of the Common Authentication Technology Next Generation Working Group of the IETF.


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
  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