Document Action: 'EAP Mutual Cryptographic Binding' to Informational RFC (draft-ietf-emu-crypto-bind-04.txt)
The IESG <iesg-secretary@ietf.org> Mon, 19 August 2013 16:26 UTC
Return-Path: <iesg-secretary@ietf.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 0F28911E82A6; Mon, 19 Aug 2013 09:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level:
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BUr2-njTXRt6; Mon, 19 Aug 2013 09:26:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4BA21F9C5A; Mon, 19 Aug 2013 09:25:58 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'EAP Mutual Cryptographic Binding' to Informational RFC (draft-ietf-emu-crypto-bind-04.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130819162558.16431.49047.idtracker@ietfa.amsl.com>
Date: Mon, 19 Aug 2013 09:25:58 -0700
Cc: emu mailing list <emu@ietf.org>, emu chair <emu-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Aug 2013 16:26:24 -0000
The IESG has approved the following document: - 'EAP Mutual Cryptographic Binding' (draft-ietf-emu-crypto-bind-04.txt) as Informational RFC This document is the product of the EAP Method Update Working Group. The IESG contact persons are Sean Turner and Stephen Farrell. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-emu-crypto-bind/ Technical Summary EAP tunneled methods require that EAP peers rely on information from the EAP server. Various security related information is carried inside of the tunnel, and are used by the peers. Methods exist to protect the peers against MITM attacks. The document discusses attacks on the tunneled data, and recommends mutual cryptographic binding to protect both parties. Working Group Summary The docuemnt records the consensus of the WG as developed over the last year. Any controversy about the contents has been resolved by updates to the document, and WG consensus was not rough. Document Quality The document provides a clear description of the attacks and recommended solutions. There are no protocol changes in the document, so no implementations are required. Personnel Alan DeKok is the doc shepherd. Sean Turner is the responsible AD. RFC Editor Note Please make the following modifications in section 3.2.3: OLD: First, the server and peer prove to each other knowledge of the inner MSK. Then, the inner MSK is combined into some outer key material to form the tunnel's keys. NEW: First, the server and peer prove to each other knowledge of the inner MSK. Then, the inner MSK is combined with some outer key material to form the tunnel's EAP keys.