[Dime] FW: [Editorial Errata Reported] RFC4072 (1956)

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 07 December 2009 13:49 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09BD93A67B1 for <dime@core3.amsl.com>; Mon, 7 Dec 2009 05:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.419
X-Spam-Level:
X-Spam-Status: No, score=-2.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id my+Jv6INrTqk for <dime@core3.amsl.com>; Mon, 7 Dec 2009 05:49:14 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 0DD533A67B5 for <dime@ietf.org>; Mon, 7 Dec 2009 05:49:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.47,355,1257138000"; d="scan'208";a="192995928"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Dec 2009 08:49:03 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Dec 2009 08:49:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 07 Dec 2009 14:48:58 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401C70BA2@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Editorial Errata Reported] RFC4072 (1956)
Thread-Index: Acp0JOV3HhzGjBTvSbGltvyD7gBc5QDHxzUg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dime@ietf.org
Subject: [Dime] FW: [Editorial Errata Reported] RFC4072 (1956)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2009 13:49:15 -0000

  DIME WG,

Please advice concerning this errata. 

Thanks and Regards,

Dan

-----Original Message-----
From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] 
Sent: Thursday, December 03, 2009 4:27 PM
To: pasi.eronen@nokia.com; tomhiller@lucent.com; gwz@cisco.com;
Romascanu, Dan (Dan); rbonica@juniper.net; Bernard_Aboba@hotmail.com;
david@mitton.com; john.loughney@nokia.com
Cc: gwz@net-zen.net; rfc-editor@rfc-editor.org
Subject: [Editorial Errata Reported] RFC4072 (1956)


The following errata report has been submitted for RFC4072, "Diameter
Extensible Authentication Protocol (EAP) Application".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4072&eid=1956

--------------------------------------
Type: Editorial
Reported by: Glen Zorn <gwz@net-zen.net>

Section: 4.1.4

Original Text
-------------
In addition, the home Diameter server SHOULD include this AVP in
Diameter-EAP-Response only if an empty EAP-Key-Name AVP was present in
Diameter-EAP-Request.


Corrected Text
--------------
In addition, the home Diameter server SHOULD include this AVP in the
Diameter-EAP-Answer message only if an empty EAP-Key-Name AVP was
present in the corresponding Diameter-EAP-Request.


Notes
-----
There's no such thing as a "Diameter-EAP-Response" message; the
rephrasing is for purposes of clarification.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC4072 (draft-ietf-aaa-eap-10)
--------------------------------------
Title               : Diameter Extensible Authentication Protocol (EAP)
Application
Publication Date    : August 2005
Author(s)           : P. Eronen, Ed., T. Hiller, G. Zorn
Category            : PROPOSED STANDARD
Source              : Authentication, Authorization and Accounting
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG