RFC 2712 on Addition of Kerberos Cipher Suites to TLS
RFC Editor <rfc-ed@ISI.EDU> Mon, 11 October 1999 19:43 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13091; Mon, 11 Oct 1999 15:43:19 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA00293 for ietf-123-outbound.10@ietf.org; Mon, 11 Oct 1999 15:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id PAA00270 for <all-ietf@loki.ietf.org>; Mon, 11 Oct 1999 15:25:12 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12691 for <all-ietf@ietf.org>; Mon, 11 Oct 1999 15:25:12 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id MAA23180; Mon, 11 Oct 1999 12:25:11 -0700 (PDT)
Message-Id: <199910111925.MAA23180@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2712 on Addition of Kerberos Cipher Suites to TLS
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 11 Oct 1999 12:25:11 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2712: Title: Addition of Kerberos Cipher Suites to Transport Layer Security (TLS) Author(s): A. Medvinsky, M. Hur Status: Standards Track Date: October 1999 Mailbox: amedvins@excitecorp.com, matt.hur@cybersafe.com Pages: 7 Characters: 13763 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-tls-kerb-cipher-suites-04.txt URL: ftp://ftp.isi.edu/in-notes/rfc2712.txt This document proposes the addition of new cipher suites to the TLS protocol [1] to support Kerberos-based authentication. Kerberos credentials are used to achieve mutual authentication and to establish a master secret which is subsequently used to secure client-server communication. This document is a product of the Transport Layer Security Working Group of the IETF. This is now a Proposed Standard Protocol. 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 "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.