[kitten] RFC 8070 on Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) Freshness Extension
rfc-editor@rfc-editor.org Thu, 16 February 2017 18:23 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADBD91294F8; Thu, 16 Feb 2017 10:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 QSR7eqUOZuTM; Thu, 16 Feb 2017 10:23:03 -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 B710A1293F8; Thu, 16 Feb 2017 10:23:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B176EB814FA; Thu, 16 Feb 2017 10:23:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170216182303.B176EB814FA@rfc-editor.org>
Date: Thu, 16 Feb 2017 10:23:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/cQxooIjSYi668kSqPyk4k3WUec4>
Cc: kitten@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [kitten] RFC 8070 on Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) Freshness Extension
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:23:04 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8070
Title: Public Key Cryptography for Initial
Authentication in Kerberos (PKINIT)
Freshness Extension
Author: M. Short, Ed.,
S. Moore,
P. Miller
Status: Standards Track
Stream: IETF
Date: February 2017
Mailbox: michikos@microsoft.com,
sethmo@microsoft.com,
paumil@microsoft.com
Pages: 9
Characters: 16348
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-kitten-pkinit-freshness-07.txt
URL: https://www.rfc-editor.org/info/rfc8070
DOI: 10.17487/RFC8070
This document describes how to further extend the Public Key
Cryptography for Initial Authentication in Kerberos (PKINIT)
extension (defined in RFC 4556) to exchange an opaque data blob that
a Key Distribution Center (KDC) can validate to ensure that the
client is currently in possession of the private key during a PKINIT
Authentication Service (AS) exchange.
This document is a product of the Common Authentication Technology Next Generation 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