Re: [Dime] FW: [Editorial Errata Reported] RFC4072 (2317)
Souheil Ben Ayed <souheil@tera.ics.keio.ac.jp> Thu, 01 July 2010 09:23 UTC
Return-Path: <souheil@tera.ics.keio.ac.jp>
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 C44C53A67F7 for <dime@core3.amsl.com>; Thu, 1 Jul 2010 02:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.368
X-Spam-Level: *
X-Spam-Status: No, score=1.368 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
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 HtRQ3GJ+Wyr7 for <dime@core3.amsl.com>; Thu, 1 Jul 2010 02:23:54 -0700 (PDT)
Received: from maro.tera.ics.keio.ac.jp (maro.tera.ics.keio.ac.jp [131.113.71.3]) by core3.amsl.com (Postfix) with ESMTP id 884133A67E5 for <dime@ietf.org>; Thu, 1 Jul 2010 02:23:54 -0700 (PDT)
Received: from [131.113.71.108] (dhcp108.tera.ics.keio.ac.jp [131.113.71.108]) by maro.tera.ics.keio.ac.jp (Postfix) with ESMTPSA id EF9B220F; Thu, 1 Jul 2010 18:24:04 +0900 (JST)
Message-ID: <4C2C5EAE.70800@tera.ics.keio.ac.jp>
Date: Thu, 01 Jul 2010 18:23:58 +0900
From: Souheil Ben Ayed <souheil@tera.ics.keio.ac.jp>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Glen Zorn <gwz@net-zen.net>
References: <EDC652A26FB23C4EB6384A4584434A04022F42F2@307622ANEX5.global.avaya.com> <004801cb18ec$7f16a4d0$7d43ee70$@net>
In-Reply-To: <004801cb18ec$7f16a4d0$7d43ee70$@net>
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: dime@ietf.org
Subject: Re: [Dime] FW: [Editorial Errata Reported] RFC4072 (2317)
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: Thu, 01 Jul 2010 09:23:55 -0000
Please read the section " 2.7. Accounting" of the RFC 4072.
In this section, it is described that one or more Accounting-EAP-Auth-Method AVPs may be added in a Diameter-EAP-Answer with a successful result code.
- Allow adding one or more Accounting-EAP-Auth-Method AVPs?
- or only one Accounting-EAP-Auth-Method AVP can be included in a Diameter-EAP-Answer?
Souheil Ben Ayed
Glen Zorn wrote:
Dan Romascanu [mailto://dromasca@avaya.com] writes:Dime WG, Please assess this errata report. If I understand well then Souheil's observation is that more Accounting-EAP-Auth-Method AVPs can be included. This seems more like a Technical errata, which if accepted can create interoperability problems with existing deployment. Am I correct?I think that your understanding is correct, but the errata makes no sense to me: AFAIK, only one EAP method can be used in authenticating a user (EAP methods cannot be chained) & even if they could (as proposed for the new tunneled EAP method under development in EMU), the structure of the Diameter EAP app mirrors that of EAP (request/response). Two EAP methods cannot be operational simultaneously, so why would two method identifiers need to be in the same Diameter message?Thanks and Regards, Dan -----Original Message----- From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] Sent: Thursday, July 01, 2010 7:31 AM 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: souheil.benayed@gmail.com; rfc-editor@rfc-editor.org Subject: [Editorial Errata Reported] RFC4072 (2317) 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=2317" rel="nofollow">http://www.rfc-editor.org/errata_search.php?rfc=4072&eid=2317 -------------------------------------- Type: Editorial Reported by: Souheil Ben Ayed <souheil.benayed@gmail.com> Section: 3.2. Original Text ------------- <Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY > < Session-Id > { Auth-Application-Id } { Auth-Request-Type } { Result-Code } { Origin-Host } { Origin-Realm } [ User-Name ] [ EAP-Payload ] [ EAP-Reissued-Payload ] [ EAP-Master-Session-Key ] [ EAP-Key-Name ] [ Multi-Round-Time-Out ] [ Accounting-EAP-Auth-Method ] [ Service-Type ] Corrected Text -------------- <Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY > < Session-Id > { Auth-Application-Id } { Auth-Request-Type } { Result-Code } { Origin-Host } { Origin-Realm } [ User-Name ] [ EAP-Payload ] [ EAP-Reissued-Payload ] [ EAP-Master-Session-Key ] [ EAP-Key-Name ] [ Multi-Round-Time-Out ] * [ Accounting-EAP-Auth-Method ] [ Service-Type ] Notes ----- When one or more EAP methods used for authenticating the user, for each used EAP method an Accounting-EAP-Auth-Method AVP is added in the Diameter-EAP-Answer with a successful result code. In the message format of Diameter-EAP-Answer, one or more Accounting-EAP-Auth-Method AVPs can be included. 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 _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime" rel="nofollow">https://www.ietf.org/mailman/listinfo/dime_______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime" rel="nofollow">https://www.ietf.org/mailman/listinfo/dime
- [Dime] FW: [Editorial Errata Reported] RFC4072 (2… Romascanu, Dan (Dan)
- Re: [Dime] FW: [Editorial Errata Reported] RFC407… Glen Zorn
- Re: [Dime] FW: [Editorial Errata Reported] RFC407… Souheil Ben Ayed
- Re: [Dime] FW: [Editorial Errata Reported] RFC407… Souheil Ben Ayed
- Re: [Dime] FW: [Editorial Errata Reported] RFC407… Glen Zorn
- Re: [Dime] FW: [Editorial Errata Reported] RFC407… Souheil Ben Ayed
- Re: [Dime] FW: [Editorial Errata Reported] RFC407… Souheil Ben Ayed