Browse Prior Art Database

Deriving Keys for use with Microsoft Point-to-Point Encryption (MPPE) (RFC3079)

IP.com Disclosure Number: IPCOM000005273D
Original Publication Date: 2001-Mar-01
Included in the Prior Art Database: 2001-Aug-20
Document File: 22 page(s) / 39K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Zorn: AUTHOR

Abstract

The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 9% of the total text.

Network Working Group G. Zorn Request for Comments: 3079 cisco Systems Category: Informational March 2001

Deriving Keys for use with Microsoft Point-to-Point Encryption (MPPE)

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract

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 RFC 3078.

Zorn Informational [Page 1]

RFC 3079 MPPE Key Derivation March 2001

Table of Contents

1. Specification of Requirements ............................... 2 2. Deriving Session Keys from MS-CHAP Credentials .............. 2 2.1. Generating 40-bit Session Keys ............................ 3 2.2. Generating 56-bit Session Keys ............................ 3 2.3. Generating 128-bit Session Keys ........................... 4 2.4. Key Derivation Functions .................................. 5 2.5. Sample Key Derivations .................................... 6 2.5.1. Sample 40-bit Key Derivation ............................ 6 2.5.2. Sample 56-bit Key Derivation ............................ 6 2.5.3. Sample 128-bit Key Derivation ........................... 7 3. Deriving Session Keys from MS-CHAP-2 Credentials ............ 7 3.1. Generating 40-bit Session Keys ............................ 8 3.2. Generating 56-bit Session Keys ............................ 9 3.3. Generating 128-bit Session Keys ...........................10 3.4. Key Derivation Functions ..................................11 3.5. Sample Key Derivations ....................................13 3.5.1. Sample 40-bit Key Derivation ............................13 3....