[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 3079 on MPPE Key Derivation
- To: IETF-Announce: ;
- Subject: RFC 3079 on MPPE Key Derivation
- From: RFC Editor <rfc-ed@ISI.EDU>
- Date: Thu, 29 Mar 2001 17:11:29 -0800
- Cc: rfc-ed@ISI.EDU, email@example.com
- Delivery-date: Fri, 30 Mar 2001 05:10:15 +0300
- Envelope-to: firstname.lastname@example.org
A new Request for Comments is now available in online RFC libraries.
Title: Deriving Keys for use with Microsoft
Point-to-Point Encryption (MPPE)
Author(s): G. Zorn
Date: March 2001
I-D Tag: draft-ietf-pppext-mppe-keys-03.txt
The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
The PPP Compression Control Protocol provides a method to negotiate
and utilize compression protocols over PPP encapsulated links.
Microsoft Point to Point Encryption (MPPE) is a means of representing
PPP packets in an encrypted form. MPPE uses the RSA RC4 algorithm to
provide data confidentiality. The length of the session key to be
used for initializing encryption tables can be negotiated. MPPE
currently supports 40-bit, 56-bit and 128-bit session keys. MPPE
session keys are changed frequently; the exact frequency depends upon
the options negotiated, but may be every packet. MPPE is negotiated
within option 18 in the Compression Control Protocol.
This document describes the method used to derive initial MPPE session
keys from a variety of credential types. It is expected that this
memo will be updated whenever Microsoft defines a new key derivation
method for MPPE, since its primary purpose is to provide an open,
easily accessible reference for third-parties wishing to interoperate
with Microsoft products.
MPPE itself (including the protocol used to negotiate its use,
the details of the encryption method used and the algorithm
used to change session keys during a session) is described in
This document is a product of the Point-to-Point Protocol Extensions
Working Group of the IETF.
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 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:
Subject: getting 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
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.