[radext] [Technical Errata Reported] RFC5176 (4311)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 23 March 2015 16:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94BF11ACD21 for <radext@ietfa.amsl.com>; Mon, 23 Mar 2015 09:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqmE25s0shkQ for <radext@ietfa.amsl.com>; Mon, 23 Mar 2015 09:51:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 117781A8A17 for <radext@ietf.org>; Mon, 23 Mar 2015 09:51:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CFFDA180459; Mon, 23 Mar 2015 09:50:24 -0700 (PDT)
To: mchiba@cisco.com, gdommety@cisco.com, meklund@cisco.com, david@mitton.com, bernarda@microsoft.com, bclaise@cisco.com, joelja@bogus.com, stefan.winter@restena.lu, lionel.morand@orange.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150323165024.CFFDA180459@rfc-editor.org>
Date: Mon, 23 Mar 2015 09:50:24 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/y9Od7W9rO5I70WX2UCxjUCtGBtM>
X-Mailman-Approved-At: Mon, 23 Mar 2015 10:01:22 -0700
Cc: radext@ietf.org, aland@freeradius.org, rfc-editor@rfc-editor.org
Subject: [radext] [Technical Errata Reported] RFC5176 (4311)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 16:52:00 -0000

The following errata report has been submitted for RFC5176,
"Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)".

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

--------------------------------------
Type: Technical
Reported by: Alan DeKok <aland@freeradius.org>

Section: 2.3

Original Text
-------------
Section 2.3 says:

      In CoA-Request and Disconnect-Request packets, all attributes MUST
      be treated as mandatory. 


Corrected Text
--------------
In CoA-Request and Disconnect-Request packets, all attributes MUST
be treated as mandatory, except Proxy-State.  See Section 3.1 for a
discussion of how the NAS must handle Proxy-State.

Notes
-----
This was seen with vendor equipment.  CoA proxying was done to the NAS, and the proxy was adding and forwarding Proxy-State as required by Section 3.1.  However, the NAS was returning a CoA-NAK with Error-Cause = Unsupported-Attribute.

The issue comes because Proxy-State is called out in Section 3.1 for special handling.  However, that special handling isn't called out in Section 2.3.  As a result, implementors can get confused.

The RADEXT WG is rechartering with a document to address CoA proxying.  We will also be addressing this issue in that document.  There are additional attributes which a NAS should ignore, OR which should be filtered out by the proxy closest to the NAS.

Instructions:
-------------
This erratum 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. 

--------------------------------------
RFC5176 (draft-ietf-radext-rfc3576bis-13)
--------------------------------------
Title               : Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)
Publication Date    : January 2008
Author(s)           : M. Chiba, G. Dommety, M. Eklund, D. Mitton, B. Aboba
Category            : INFORMATIONAL
Source              : RADIUS EXTensions
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG