[Dime] FW: [Editorial Errata Reported] RFC4072 (2317)
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 01 July 2010 06:42 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 D029B3A67D7 for <dime@core3.amsl.com>; Wed, 30 Jun 2010 23:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level:
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[AWL=0.586, 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 DsqhES6h4XEi for <dime@core3.amsl.com>; Wed, 30 Jun 2010 23:42:46 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 81CEB3A67C3 for <dime@ietf.org>; Wed, 30 Jun 2010 23:42:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,518,1272859200"; d="scan'208";a="23204096"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 01 Jul 2010 02:42:57 -0400
X-IronPort-AV: E=Sophos;i="4.53,518,1272859200"; d="scan'208";a="487903170"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Jul 2010 02:42:56 -0400
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: Thu, 01 Jul 2010 08:42:32 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F42F2@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Editorial Errata Reported] RFC4072 (2317)
Thread-Index: AcsY1ige+KLIbwB9TGepu7S0z3jI5wAEZT9g
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dime@ietf.org
Cc: souheil.benayed@gmail.com
Subject: [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 06:42:47 -0000
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? 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 -------------------------------------- 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] 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