[Emu] Potential Notes in EAP-FAST Documents

The IESG <iesg@ietf.org> Sun, 01 February 2009 22:33 UTC

Return-Path: <emu-bounces@ietf.org>
X-Original-To: emu-archive@megatron.ietf.org
Delivered-To: ietfarch-emu-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F8E828C182; Sun, 1 Feb 2009 14:33:26 -0800 (PST)
X-Original-To: emu@ietf.org
Delivered-To: emu@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id D5F093A6974; Sun, 1 Feb 2009 12:46:29 -0800 (PST)
From: The IESG <iesg@ietf.org>
To: emu@ietf.org
Mime-Version: 1.0
Message-Id: <20090201204629.D5F093A6974@core3.amsl.com>
Date: Sun, 01 Feb 2009 12:46:29 -0800
X-Mailman-Approved-At: Sun, 01 Feb 2009 14:33:25 -0800
Cc: iesg@ietf.org
Subject: [Emu] Potential Notes in EAP-FAST Documents
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/emu>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: emu-bounces@ietf.org
Errors-To: emu-bounces@ietf.org

Dear EMU WG:

These two documents are in the RFC Editor queue:

   draft-cam-winget-eap-fast-provisioning-10.txt
   draft-zhou-emu-fast-gtc-05.txt

The IESG has received a very late comment about these documents, and
we seek your input on the proposed resolution.

The late comment raises a potential interoperability concern with
existing implementations of EAP-MSCHAPv2 and EAP-GTC.
 
The draft-cam-winget-eap-fast-provisioning-10.txt document specifies
a very specific way to generate the challenges used in EAP-MSCHAPv2
that provides binding between the EAP-FAST tunnel and the EAP-MSCHAPv2
exchanges.

The draft-zhou-emu-fast-gtc-05.txt describes EAP-FAST-GTC, which is
uses EAP Type 6, originally allocated to EAP-GTC [RFC3748]. EAP-FAST-GTC
employs a subset of the EAP-GTC formatting.

The IESG recognizes the difficulties caused by re-use of an EAP Type.
Further, the IESG recognizes the concern about implementations that
might not easily adapt to additional requirements.  However, the IESG
also recognizes the significant value in documenting EAP methods that
are implemented and deployed in the Internet today.

The IESG believes that the right thing to do in this situation is to
proceed with the publication of these documents.  However, the IESG also
sees value in warning future EAP method designers about this experience
so that this pain might be avoided in the future.

The IESG is considering the additional informative paragraph in the IANA
considerations section of both documents that says:

    IESG Note: EAP-FAST has been implemented by many vendors and it is
    used in the Internet.  Publication of this is intended to promote
    interoperability, even though the use of the EAP-MSCHAPv2 and
    EAP-FAST-GTC EAP methods might be difficult in some software
    environments.  If EAP-FAST were to be designed today, these
    difficulties could be avoided by the assignment of new EAP Type
    codes.

Please provide comments on the proposed way forward.

On behalf of the IESG,
  Russ

_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu