
From nobody Sat Sep  5 16:32:42 2015
Return-Path: <aland@freeradius.org>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 574581B3021 for <aaa-doctors@ietfa.amsl.com>; Sat,  5 Sep 2015 16:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.511
X-Spam-Level: 
X-Spam-Status: No, score=-0.511 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 7BvutxKjt8WH for <aaa-doctors@ietfa.amsl.com>; Sat,  5 Sep 2015 16:32:38 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0791B2F8B for <aaa-doctors@ietf.org>; Sat,  5 Sep 2015 16:32:38 -0700 (PDT)
Received: by power.freeradius.org (Postfix, from userid 1000) id 3189A2240C73; Sun,  6 Sep 2015 01:32:07 +0200 (CEST)
From: aland@freeradius.org
To: <aaa-doctors@ietf.org>
X-Mailer: mail (GNU Mailutils 2.99.98)
Message-Id: <20150905233207.3189A2240C73@power.freeradius.org>
Date: Sun,  6 Sep 2015 01:32:07 +0200 (CEST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/WqeRcPmQ8I_e1_O_Pkm_0ZORwPI>
Subject: [AAA-DOCTORS] Automatic tech report for Sun Sep 6 01:32:06 CEST 2015
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Sep 2015 23:32:40 -0000

  This is an automatically generated email.  It lists the IETF internet-drafts
which are WG items and which reference RADIUS.  Drafts
from the RADEXT and DIME working groups are not included.

--
draft-ietf-abfab-aaa-saml-11                      Active	
draft-ietf-abfab-arch-13                          In IESG processing - ID Tracker state <RFC Ed Queue>	
draft-ietf-softwire-map-radius-04                 Active	


From nobody Sat Sep 12 16:32:12 2015
Return-Path: <aland@freeradius.org>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 370161B4804 for <aaa-doctors@ietfa.amsl.com>; Sat, 12 Sep 2015 16:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 2JBYKqXSLj58 for <aaa-doctors@ietfa.amsl.com>; Sat, 12 Sep 2015 16:32:09 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 91BE71B49AC for <aaa-doctors@ietf.org>; Sat, 12 Sep 2015 16:32:09 -0700 (PDT)
Received: by power.freeradius.org (Postfix, from userid 1000) id 9FF3622406D0; Sun, 13 Sep 2015 01:32:07 +0200 (CEST)
From: aland@freeradius.org
To: <aaa-doctors@ietf.org>
X-Mailer: mail (GNU Mailutils 2.99.98)
Message-Id: <20150912233207.9FF3622406D0@power.freeradius.org>
Date: Sun, 13 Sep 2015 01:32:07 +0200 (CEST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/intlh_FRXtuFMoQadJStRUtx4oM>
Subject: [AAA-DOCTORS] Automatic tech report for Sun Sep 13 01:32:07 CEST 2015
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2015 23:32:11 -0000

  This is an automatically generated email.  It lists the IETF internet-drafts
which are WG items and which reference RADIUS.  Drafts
from the RADEXT and DIME working groups are not included.

--
draft-ietf-abfab-aaa-saml-11                      Active	
draft-ietf-abfab-arch-13                          In IESG processing - ID Tracker state <RFC Ed Queue>	
draft-ietf-softwire-map-radius-04                 Active	


From nobody Mon Sep 14 06:13:26 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A391B3370 for <aaa-doctors@ietfa.amsl.com>; Mon, 14 Sep 2015 06:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 U3xJGjg6Tys8 for <aaa-doctors@ietfa.amsl.com>; Mon, 14 Sep 2015 06:13:22 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 716671B3263 for <aaa-doctors@ietf.org>; Mon, 14 Sep 2015 06:13:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3713; q=dns/txt; s=iport; t=1442236402; x=1443446002; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=aLbU/5em2PvLgNenL7+RE1Hz/R6ZIDUeJNa7rze0Eao=; b=M3t/CrnodwoUY5Gzv/VkYsT1fCdocJWNAuSDhkRsyVnSyUVgyUpc/aIm IM36aIUsCL7BgQm9ovmZhhFuY2Bg4hI980OzAUtcJVILWx3ZqfVYAaEL+ opX3/CZwg6R4HR2U/NULwio/aYAbp9w/YNIp2dJOKqHImoogYHsXye1fw M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CdBACHxvZV/xbLJq1DGoN3ab9EhXkCggEBAQEBAQGBC4QkAQEEOEABEAsYCQ8HBQoJAwIBAgFFBg0GAgEBiCoNO7prjlABAQEBAQEBAQEBAQEBAQEBAQEBGYZzhH2BPYMFSwcZhBMBBIV7gTcGhm6HMYx+gUyHMYEGjFk2g2xjghEND4FWPDMBE4ppAQEB
X-IronPort-AV: E=Sophos;i="5.17,528,1437436800"; d="scan'208";a="606995199"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 14 Sep 2015 13:13:20 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t8EDDK1Y002529; Mon, 14 Sep 2015 13:13:20 GMT
To: Alan DeKok <aland@freeradius.org>
References: <20150914103150.25791180472@rfc-editor.org> <5023772F-2B40-40F2-9606-1E0C1BEE12FA@freeradius.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <55F6C7EF.8050506@cisco.com>
Date: Mon, 14 Sep 2015 15:13:19 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5023772F-2B40-40F2-9606-1E0C1BEE12FA@freeradius.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/tZjP9JYg49KH4OpuJfRaQkeZXyg>
Cc: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Errata Rejected] RFC2548 (4369)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2015 13:13:24 -0000

Alan,

Let's solve that on the AAA-doctors.
Kathleen and I are waiting for the outcome of your discussion.

Regards, Benoit
>    While the comment about 24 octets vs 32 is correct and appreciated, there are still open issues.
>
>    User-Password is not supposed to contain embedded zeros.  It is padded out to a multiple of 16 octets in length.  BUT there is no explicit "length" field in the attribute, unlike Tunnel-Password.
>
>    Therefore, implementations determine the length by going to the end of the decrypted buffer, and looking for the first non-zero character.
>
>    That method does not work for MS-CHAP-MPPE-Keys.  That attribute is binary, and is explicitly allowed to contain embedded zeros.  Therefore the above method for determining length doesn't work.  There is a 1/256 chance that the last octet of the NT key is, in fact, zero.
>
>    The technical errata points out that the length of the decoded attribute MUST be manually set to 24.  The "normal" method of looking for a non-zero octet doesn't work.
>
> On Sep 14, 2015, at 6:31 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>
>> The following errata report has been rejected for RFC2548,
>> "Microsoft Vendor-specific RADIUS Attributes".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=2548&eid=4369
>>
>> --------------------------------------
>> Status: Rejected
>> Type: Technical
>>
>> Reported by: Alan DeKok <aland@freeradius.org>
>> Date Reported: 2015-05-19
>> Rejected by: Benoit Claise (IESG)
>>
>> Section: 2.4.1
>>
>> Original Text
>> -------------
>> The Keys field MUST be encrypted by the RADIUS server using the
>> same method defined for the User-Password Attribute [3].  Padding
>> is required because the method referenced above requires the field
>> to be encrypted to be a multiple of sixteen octets in length.
>>
>> Corrected Text
>> --------------
>> The Keys field MUST be encrypted by the RADIUS server using the
>> same method defined for the User-Password Attribute [3].  Padding
>> is required because the method referenced above requires the field
>> to be encrypted to be a multiple of sixteen octets in length.
>>
>> We note that the encryption method for the User-Password attribute
>> does not contain a field describing the length of the decrypted data.
>>   Despite this, the User-Password attribute contains data which is
>> variable length.  The length of that data is commonly determined by
>> looking for either the end of the data, or the first zero octet in the
>> data, whichever comes first.
>>
>> That practice cannot be used here, as the Keys field can contain
>> embedded zero octets.  This means that the length of the decrypted
>> data MUST be set explicitly to 32 octets for this attribute.
>>
>> Notes
>> -----
>> re: MS-CHAP-MPPE-Keys "obfuscation"
>> --VERIFIER NOTES--
>> Section 2.4.1 describes 32 octets of content, which *include* padding.
>>
>> The decrypted data is thus less than 32 octets. The ASCII art in that sections shows 64 bit of padding in the end, meaning it's only 24 octets of decrypted keys.
>>
>> --------------------------------------
>> RFC2548 (draft-ietf-radius-ms-vsa-01)
>> --------------------------------------
>> Title               : Microsoft Vendor-specific RADIUS Attributes
>> Publication Date    : March 1999
>> Author(s)           : G. Zorn
>> Category            : INFORMATIONAL
>> Source              : Remote Authentication Dial-In User Service
>> Area                : Operations and Management
>> Stream              : IETF
>> Verifying Party     : IESG
>>


From nobody Sat Sep 19 16:32:44 2015
Return-Path: <aland@freeradius.org>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98DDD1B3146 for <aaa-doctors@ietfa.amsl.com>; Sat, 19 Sep 2015 16:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 C7rU8-ikB0yE for <aaa-doctors@ietfa.amsl.com>; Sat, 19 Sep 2015 16:32:39 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id DE6E41B3145 for <aaa-doctors@ietf.org>; Sat, 19 Sep 2015 16:32:38 -0700 (PDT)
Received: by power.freeradius.org (Postfix, from userid 1000) id A114F22407AA; Sun, 20 Sep 2015 01:32:07 +0200 (CEST)
From: aland@freeradius.org
To: <aaa-doctors@ietf.org>
X-Mailer: mail (GNU Mailutils 2.99.98)
Message-Id: <20150919233207.A114F22407AA@power.freeradius.org>
Date: Sun, 20 Sep 2015 01:32:07 +0200 (CEST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/hQdlRmCit3nltgaiRHxpb8J_pAY>
Subject: [AAA-DOCTORS] Automatic tech report for Sun Sep 20 01:32:07 CEST 2015
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Sep 2015 23:32:40 -0000

  This is an automatically generated email.  It lists the IETF internet-drafts
which are WG items and which reference RADIUS.  Drafts
from the RADEXT and DIME working groups are not included.

--
draft-ietf-abfab-aaa-saml-11                      Active	
draft-ietf-abfab-arch-13                          In IESG processing - ID Tracker state <RFC Ed Queue>	
draft-ietf-softwire-map-radius-04                 Active	


From nobody Sat Sep 26 16:32:41 2015
Return-Path: <aland@freeradius.org>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECB61A89B5 for <aaa-doctors@ietfa.amsl.com>; Sat, 26 Sep 2015 16:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level: 
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 J4dGTaCkYLi1 for <aaa-doctors@ietfa.amsl.com>; Sat, 26 Sep 2015 16:32:38 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id BDE8E1A89B3 for <aaa-doctors@ietf.org>; Sat, 26 Sep 2015 16:32:38 -0700 (PDT)
Received: by power.freeradius.org (Postfix, from userid 1000) id 415292240702; Sun, 27 Sep 2015 01:32:07 +0200 (CEST)
From: aland@freeradius.org
To: <aaa-doctors@ietf.org>
X-Mailer: mail (GNU Mailutils 2.99.98)
Message-Id: <20150926233207.415292240702@power.freeradius.org>
Date: Sun, 27 Sep 2015 01:32:07 +0200 (CEST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/OusyA3ELHA1X7ygmhKmlfCPm1Ew>
Subject: [AAA-DOCTORS] Automatic tech report for Sun Sep 27 01:32:06 CEST 2015
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Sep 2015 23:32:40 -0000

  This is an automatically generated email.  It lists the IETF internet-drafts
which are WG items and which reference RADIUS.  Drafts
from the RADEXT and DIME working groups are not included.

--
draft-ietf-abfab-aaa-saml-11                      Active	
draft-ietf-abfab-arch-13                          In IESG processing - ID Tracker state <RFC Ed Queue>	
draft-ietf-softwire-map-radius-04                 Active	


From nobody Mon Sep 28 04:09:23 2015
Return-Path: <stefan.winter@restena.lu>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759B91A88DE for <aaa-doctors@ietfa.amsl.com>; Mon, 28 Sep 2015 04:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, WEIRD_PORT=0.001] 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 AopZR-FRpXor for <aaa-doctors@ietfa.amsl.com>; Mon, 28 Sep 2015 04:09:20 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFA1A1A88EA for <aaa-doctors@ietf.org>; Mon, 28 Sep 2015 04:09:19 -0700 (PDT)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id EACC74396F; Mon, 28 Sep 2015 13:09:17 +0200 (CEST)
From: Stefan Winter <stefan.winter@restena.lu>
To: Benoit Claise <bclaise@cisco.com>, "radext-chairs@tools.ietf.org" <radext-chairs@tools.ietf.org>
References: <20150928030705.92AA04502F@ariadne.telemancy.com> <5608FE64.8090209@cisco.com>
Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66; url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66
Message-ID: <56091FDD.9030701@restena.lu>
Date: Mon, 28 Sep 2015 13:09:17 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5608FE64.8090209@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GivQfaJNHtsASJhWDN22j8QoGvSGmpLCU"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/6CX3EK5I7tenoutS6CoW1XA54hE>
Cc: aaa-doctors@ietf.org
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4485)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2015 11:09:22 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--GivQfaJNHtsASJhWDN22j8QoGvSGmpLCU
Content-Type: multipart/mixed;
 boundary="------------020501010001000007020409"

This is a multi-part message in MIME format.
--------------020501010001000007020409
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello, this time including the doctors,

hm, I'm not so sure. The errata notes contain the assertion that RFC2866
was not meant to be used like that.

But that statement is not a given. the RFC states in 4.1 that

"Any attribute valid in a RADIUS Access-Request or Access-Accept
      packet is valid in a RADIUS Accounting-Request packet, except that
      the following attributes MUST NOT [...]"

So, sending Called-Station-Id is something that's allowed just fine.

It is not reasonable to assume the On/Off is atomic for the entire NAS -
the text "(for example, just before a scheduled reboot)" is really jsut
that - an example.

True, it is not defined how this attribute is supposed to be used and
that the action "only terminate Accounting for sessions matching this
Called-Station-Id" is not explicitly defined.

But I do not concur with the consequence that all Accounting-On/Off must
be treated as an atomic operation for the entire NAS.

If a reaction to this admitted ambiguity is needed, IMHO it should not
take the form of an errata which retroactively makes everyone else's
halfways reasonable assumption of behaviour incorrect, but take the form
of an RFC making the desired behaviour explicit.

In that latter case, I am even against the errata Notes suggestion -
there is no need for "Scoped-Accounting-*" - instead, an RFC can very
simply clarify the matters by stating:

"Presence of additional attributes in Accounting-On/Off means that
accounting is starting/stopping only for sessions matching the
attributes that are present in the packet."

Thinking of it further, *that* would also be an errata text I could live
with :-)

But an interesting nuance to discuss. Looking forward to Lionel's opinion=
=2E

Greetings,

Stefan Winter

Am 28.09.2015 um 10:46 schrieb Benoit Claise:
> FYI.
>=20
> Regards, Benoit
>=20
>=20
> -------- Forwarded Message --------
> Subject:     Re: [Technical Errata Reported] RFC2866 (4485)
> Date:     Sun, 27 Sep 2015 20:07:05 -0700
> From:     Carl Rigney <cdr@telemancy.com>
> To:     bclaise@cisco.com, cdr@telemancy.com, joelja@bogus.com,
> rfc-editor@rfc-editor.org
> CC:     nick.lowe@lugatech.com
>=20
>=20
>=20
> That seems like a reasonable clarification to me.
>=20
> --=20
> Carl Rigney
> cdr@telemancy.com
>=20
> On Sun, Sep 27, 2015 at 9:51 AM, RFC Errata System
> <rfc-editor@rfc-editor.org> wrote:
>=20
>     The following errata report has been submitted for RFC2866,
>     "RADIUS Accounting".
>=20
>     --------------------------------------
>     You may review the report below and at:
>     http://www.rfc-editor.org/errata_search.php?rfc=3D2866&eid=3D4485
>=20
>     --------------------------------------
>     Type: Technical
>     Reported by: Nick Lowe <nick.lowe@lugatech.com
>=20
>     Section: 5.1
>=20
>     Original Text
>     -------------
>     This attribute indicates whether this Accounting-Request
>     marks the beginning of the user service (Start) or the end (Stop).
>=20
>     It MAY be used by the client to mark the start of accounting
>     (for example, upon booting) by specifying Accounting-On and
>     to mark the end of accounting (for example, just before a
>     scheduled reboot) by specifying Accounting-Off.
>=20
>     Corrected Text
>     --------------
>     This attribute indicates
>     whether this Accounting-Request marks the beginning of the
>     user service (Start) or the end (Stop).
>=20
>     It MAY be used by the client to mark the start of accounting
>     for the NAS (for example, upon booting) by specifying
>     Accounting-On and to mark the end of accounting for the NAS
>     (for example, just before a scheduled reboot) by specifying
>     Accounting-Off.
>=20
>     Notes
>     -----
>     Some RADIUS client implementations send scoped Accounting-On
>     and Accounting-Off Accounting-Request packets.  This is
>     seen, for example, with some wireless APs that include a
>     Called-Station-Id attribute to scope to a Basic Service Set (BSS).
>=20
>     This is an incorrect interpretation of the RFC that is not
>     backwards compatible with consumers of RADIUS accounting
>     information, yet the RFC is ambiguous on this point.
>=20
>     The RFC must be clear that Accounting-On and Accounting-Off
>     apply to the whole NAS and cannot be scoped in this manner.
>=20
>     New Acct-Status-Type values must instead be defined to allow
>     this, perhaps named something like Scoped-Accounting-On and
>     Scoped-Accounting-Off.
>=20
>     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.
>=20
>     --------------------------------------
>     RFC2866 (draft-ietf-radius-accounting-v2-05)
>     --------------------------------------
>     Title               : RADIUS Accounting Publication
>     Date    : June 2000
>     Author(s) : C. Rigney
>     Category            : INFORMATIONAL
>     Source : Remote Authentication Dial-In User Service
>     Area : Operations and Management
>     Stream              : IETF
>     Verifying Party     : IESG
>=20


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
recipient's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xC0DE6A358A39DC66


--------------020501010001000007020409
Content-Type: application/pgp-keys;
 name="0x8A39DC66.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x8A39DC66.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2

mQINBFIplEwBEADTSz+DS8nio+RSvfSLLfaOnCGi1nqpn8Pb1laVUyEvnAAzZ5je
miS88GxfiDH6hUGlWzcaW0hCfUHGiohr485adbjxRksPngWgAt/1bRxpifsW3zOb
Fjgog01WWQV5Sihlwc4zr8zvYbFA5BJZ6YdkR9C5J015riv5OS30WTjA65SSXgYr
b7zJWPwmegTFwE093uBFvC39waz3xYpVu5j87nO6w2MVQt/8sY2/2BFPEq+xfOaj
l18UEwc7w8SCgnZdlVNcmEK4UBvJuwS/1lsR2JeQa8Gu1EDxC7PRgMgNXsDSWnnB
e9aVmfG54+6ILe1QH2dwk9sPBQT5w2+vjijrb3Dv9ur+1kN+TNU2XE436jVpnnY/
3OsLdix30STQn4Q/XOm7YoVMeDwwviefilRxzK0dXA+wKj92T68Od82CFxuZqPAg
BCVmWfQM91iK9piqFK+QP+R3vF6+NGDBdwbe68iVKs0v5L8XmbxBQndjpmo+lo2a
smBR2TAIfZHaKdgtBw13u3GPVVKlg/Mpko8ki9JOSem2aFyi3kQEVKptWgXT3POl
97DWJzsR5VyKz6GOx9kJAEISRyLZwm0wqh8+9LCza5oeIKW381lzq1b9x30vOh8C
BSQQJ+cG9ko0yPHAj7Suw2TmPXx1qMctmE6Ahq82ZW30SljdZby8WQuR2wARAQAB
tDxTdGVmYW4gV2ludGVyIChSRVNURU5BIGtleSAyMDEzKykgPHN0ZWZhbi53aW50
ZXJAcmVzdGVuYS5sdT6JAjkEEwECACMFAlIplEwCGwMHCwkIBwMCAQYVCAIJCgsE
FgIDAQIeAQIXgAAKCRDA3mo1ijncZj7/D/99hVS+mJr8dSPCaDaUFFxBiT2eI1Lo
R8VKEerTCRw5BsdL6pN2eRJZ9NmsqWo1ynWVHEzO91bNZ+oZGgyoNohcBAI7p+r0
qUTzkyqwdZO4kMm0pqKoM9xkP3tf2mjGujKjOz4Y7S7wnz2ZFokeUsecoRVJF/++
/qHnmeWLn44J1HUKLHYCjMu+QXGOgGXgz024jQ5eUrnPwzNp0Z90AFVHlWC+bymt
y/ToIUUCQqS5Ff0jzdWLd8U695OG9iGvjBQT1LdEjsfbAwuKV5UcnpxNqUpUwKa5
9hdX5/2cMZP07FI1UXwnBlxa8rJfdb13FLjSKX4vUUHedYUZMjMPgcwl1a+zGE22
lHiSQWgP8QLA/W3BLsi22ERCEPZBfexOeOtaWIItDIz18fIaQoMDoRPshzar0JI2
CzLYsyeKySAtYJEHFVoLmMvhkwzBmgqA/BEswUA67CfCr1jFHRXdpmWM7YkyAmMa
9q6LwquWKS5+MXlUXe/3oZUcgpw/T9Uuy3Jo3RdS7B3jFcWaVr6KsO/A9u1gr/aY
n5M+iJTQSj4vzqtkQaJTpSspRZoKa66HZt3IwSYiDiYZqtM83ynuj9kjnZzGfnuT
aNIi996q6Mptr33mOzIE1wmMqnJYwTr3EcNtf483q/qrJwh5ES8Q9xY7aat/ZcSl
8fKubW4TlfVr8YhGBBARAgAGBQJSKZUGAAoJEPo5vdH/HhVmYTgAn24eoqO/O98o
vNpt08Uab/+/tmYKAJ9kjXm9Njz5h33efzeelZUa484rr7kCDQRSKZRMARAAvBPp
n7FQq7LQ5glohtbL6XIEo1U4X67S0TzUYieENSWSVYuWYIhCBldmWdmH8Bpj/qHe
qdon7v+SLtR4WngzMR9toupKcFfHnbP9kpazTSB2ySHxXWGX1gJOpPXdCcg9iveK
BHEsDn00ThTcPsvtXpnnzET16pXIvOXO0bxTmVZ4INIF1SWgvYma/g8kBbgXLpkj
8tOywBqFiiYPEZlDeCxDHiMgUDh6olda9K/0TZFTdMPUgjKuubfAeaDNCOrVt4Rj
mFOaRLikcZocmgJhm3z/j25x7/mnNu+0di1H/S67YGQJ+pqCFInzIXDx7aRW2+JC
iqsY2X3xOPWZZzjyis5SNnfOcPH3gt2hYz1fy+thsBGf4NgCN01JRqIJ2/MOQCgU
dwh+9l8xqaJvCkUHM4hVh4W62MAe1u7UEqQbvvNEqxM5034vcvlE+/LRkrDCspw+
2YJ9QyroLerVRwW5DVleP8Ifi8VB3yD80nqXYs9aqRy0BkDNIQ43ERhESMt8dJqr
NkxgC6pemZrhNwyDh+hy2kPNGQh/iBpdKuH1o3E24TIZoV2v3YHvzob7aAYHddE/
PofAXhJW7I9mAs+HdWDmnI8ckuPDFpFH+Y/BFGvEXgcnJAJ1wEvf+4LuiIi0MHjR
4EWFn9vvoFDAIqD10h3FSd3D59HGtdSsNn4XaCsAEQEAAYkCHwQYAQIACQUCUimU
TAIbDAAKCRDA3mo1ijncZhBtEACL036ddjc5pFoYIdoUY1vT8SMXJNquewCnL1qu
DADzqDZFU5GNlQEy10krSfBwlTb9ahTtE0JFrOdZwUZtoa1Pgfr8nU6KOgrXPHbN
jS/9dyc5CwGVVIpOavIm2CsMVDJ9LCF/NT+u/t1k6eGfHhPVl3dUQyDa/lzc1chK
UIVQYQkFmr0A/iXP+29lFCaI+IeyU0bSdZhezDwUROn5vEx+fiPZyHDShCb+BxJv
/o2LQp9JHenCiSbO+ioRZdxgbWfoKBuXOfmSStqMWXas/gZ5vS3xq72LNtKPRxgp
jX3P8Zml1XDqpcBau7eK75VKE0Yd06YxnUIsbcEzInUc3uzW/u0DFpXYkMJb0XIv
JyUt5yYPKfV13N8kSkPi5pLxm8yuftXMzfgeFMR7nafY3glTVj/TxElzg6xeZNqf
C2ZjIbBtZg9ylHU8u8wwB+dX282crs0R3N9A064C71/cXlBqcjzjlKH2NUIWGxr+
od3TXFIFjszSU3NgMPKrWNhFLLwS81MpbkOe73s6aDhS8RDyNucoxtKXriLR+4Xi
u4+pyj5ukYP1JqpB3ZobY/XZgCnJMye+7xeTpIDJ1LPORxM3NNAElyb26lxAK2P+
km+EpI0Zzz6rNSCfg5jYQ474+e/GBgaSG4MlaPoZ+XAfN46u1Xjjv1/AkkA4IA6m
5zP5og=3D=3D
=3D3NUt
-----END PGP PUBLIC KEY BLOCK-----


--------------020501010001000007020409
Content-Type: application/pgp-keys;
 name="0x8A39DC66.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x8A39DC66.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2

mQINBFIplEwBEADTSz+DS8nio+RSvfSLLfaOnCGi1nqpn8Pb1laVUyEvnAAzZ5je
miS88GxfiDH6hUGlWzcaW0hCfUHGiohr485adbjxRksPngWgAt/1bRxpifsW3zOb
Fjgog01WWQV5Sihlwc4zr8zvYbFA5BJZ6YdkR9C5J015riv5OS30WTjA65SSXgYr
b7zJWPwmegTFwE093uBFvC39waz3xYpVu5j87nO6w2MVQt/8sY2/2BFPEq+xfOaj
l18UEwc7w8SCgnZdlVNcmEK4UBvJuwS/1lsR2JeQa8Gu1EDxC7PRgMgNXsDSWnnB
e9aVmfG54+6ILe1QH2dwk9sPBQT5w2+vjijrb3Dv9ur+1kN+TNU2XE436jVpnnY/
3OsLdix30STQn4Q/XOm7YoVMeDwwviefilRxzK0dXA+wKj92T68Od82CFxuZqPAg
BCVmWfQM91iK9piqFK+QP+R3vF6+NGDBdwbe68iVKs0v5L8XmbxBQndjpmo+lo2a
smBR2TAIfZHaKdgtBw13u3GPVVKlg/Mpko8ki9JOSem2aFyi3kQEVKptWgXT3POl
97DWJzsR5VyKz6GOx9kJAEISRyLZwm0wqh8+9LCza5oeIKW381lzq1b9x30vOh8C
BSQQJ+cG9ko0yPHAj7Suw2TmPXx1qMctmE6Ahq82ZW30SljdZby8WQuR2wARAQAB
tDxTdGVmYW4gV2ludGVyIChSRVNURU5BIGtleSAyMDEzKykgPHN0ZWZhbi53aW50
ZXJAcmVzdGVuYS5sdT6JAjkEEwECACMFAlIplEwCGwMHCwkIBwMCAQYVCAIJCgsE
FgIDAQIeAQIXgAAKCRDA3mo1ijncZj7/D/99hVS+mJr8dSPCaDaUFFxBiT2eI1Lo
R8VKEerTCRw5BsdL6pN2eRJZ9NmsqWo1ynWVHEzO91bNZ+oZGgyoNohcBAI7p+r0
qUTzkyqwdZO4kMm0pqKoM9xkP3tf2mjGujKjOz4Y7S7wnz2ZFokeUsecoRVJF/++
/qHnmeWLn44J1HUKLHYCjMu+QXGOgGXgz024jQ5eUrnPwzNp0Z90AFVHlWC+bymt
y/ToIUUCQqS5Ff0jzdWLd8U695OG9iGvjBQT1LdEjsfbAwuKV5UcnpxNqUpUwKa5
9hdX5/2cMZP07FI1UXwnBlxa8rJfdb13FLjSKX4vUUHedYUZMjMPgcwl1a+zGE22
lHiSQWgP8QLA/W3BLsi22ERCEPZBfexOeOtaWIItDIz18fIaQoMDoRPshzar0JI2
CzLYsyeKySAtYJEHFVoLmMvhkwzBmgqA/BEswUA67CfCr1jFHRXdpmWM7YkyAmMa
9q6LwquWKS5+MXlUXe/3oZUcgpw/T9Uuy3Jo3RdS7B3jFcWaVr6KsO/A9u1gr/aY
n5M+iJTQSj4vzqtkQaJTpSspRZoKa66HZt3IwSYiDiYZqtM83ynuj9kjnZzGfnuT
aNIi996q6Mptr33mOzIE1wmMqnJYwTr3EcNtf483q/qrJwh5ES8Q9xY7aat/ZcSl
8fKubW4TlfVr8YhGBBARAgAGBQJSKZUGAAoJEPo5vdH/HhVmYTgAn24eoqO/O98o
vNpt08Uab/+/tmYKAJ9kjXm9Njz5h33efzeelZUa484rr7kCDQRSKZRMARAAvBPp
n7FQq7LQ5glohtbL6XIEo1U4X67S0TzUYieENSWSVYuWYIhCBldmWdmH8Bpj/qHe
qdon7v+SLtR4WngzMR9toupKcFfHnbP9kpazTSB2ySHxXWGX1gJOpPXdCcg9iveK
BHEsDn00ThTcPsvtXpnnzET16pXIvOXO0bxTmVZ4INIF1SWgvYma/g8kBbgXLpkj
8tOywBqFiiYPEZlDeCxDHiMgUDh6olda9K/0TZFTdMPUgjKuubfAeaDNCOrVt4Rj
mFOaRLikcZocmgJhm3z/j25x7/mnNu+0di1H/S67YGQJ+pqCFInzIXDx7aRW2+JC
iqsY2X3xOPWZZzjyis5SNnfOcPH3gt2hYz1fy+thsBGf4NgCN01JRqIJ2/MOQCgU
dwh+9l8xqaJvCkUHM4hVh4W62MAe1u7UEqQbvvNEqxM5034vcvlE+/LRkrDCspw+
2YJ9QyroLerVRwW5DVleP8Ifi8VB3yD80nqXYs9aqRy0BkDNIQ43ERhESMt8dJqr
NkxgC6pemZrhNwyDh+hy2kPNGQh/iBpdKuH1o3E24TIZoV2v3YHvzob7aAYHddE/
PofAXhJW7I9mAs+HdWDmnI8ckuPDFpFH+Y/BFGvEXgcnJAJ1wEvf+4LuiIi0MHjR
4EWFn9vvoFDAIqD10h3FSd3D59HGtdSsNn4XaCsAEQEAAYkCHwQYAQIACQUCUimU
TAIbDAAKCRDA3mo1ijncZhBtEACL036ddjc5pFoYIdoUY1vT8SMXJNquewCnL1qu
DADzqDZFU5GNlQEy10krSfBwlTb9ahTtE0JFrOdZwUZtoa1Pgfr8nU6KOgrXPHbN
jS/9dyc5CwGVVIpOavIm2CsMVDJ9LCF/NT+u/t1k6eGfHhPVl3dUQyDa/lzc1chK
UIVQYQkFmr0A/iXP+29lFCaI+IeyU0bSdZhezDwUROn5vEx+fiPZyHDShCb+BxJv
/o2LQp9JHenCiSbO+ioRZdxgbWfoKBuXOfmSStqMWXas/gZ5vS3xq72LNtKPRxgp
jX3P8Zml1XDqpcBau7eK75VKE0Yd06YxnUIsbcEzInUc3uzW/u0DFpXYkMJb0XIv
JyUt5yYPKfV13N8kSkPi5pLxm8yuftXMzfgeFMR7nafY3glTVj/TxElzg6xeZNqf
C2ZjIbBtZg9ylHU8u8wwB+dX282crs0R3N9A064C71/cXlBqcjzjlKH2NUIWGxr+
od3TXFIFjszSU3NgMPKrWNhFLLwS81MpbkOe73s6aDhS8RDyNucoxtKXriLR+4Xi
u4+pyj5ukYP1JqpB3ZobY/XZgCnJMye+7xeTpIDJ1LPORxM3NNAElyb26lxAK2P+
km+EpI0Zzz6rNSCfg5jYQ474+e/GBgaSG4MlaPoZ+XAfN46u1Xjjv1/AkkA4IA6m
5zP5og=3D=3D
=3D3NUt
-----END PGP PUBLIC KEY BLOCK-----

--------------020501010001000007020409--

--GivQfaJNHtsASJhWDN22j8QoGvSGmpLCU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJWCR/dAAoJEMDeajWKOdxmAGAQAISPMXawtiTmaT2c09Jgq3wB
uOCMH8TtrlBfW28jg6LHdsyVnahH7oxI2VgLZ7KDfXIo8tE9gBZHiIg+bQ/Nj1NY
FvAJDOjMcUca+rykuFpuXgaIYqOWFIyhb4WBS8LCr/T0wU100heAlm68V5+lXGPk
t1aF0OvapA2tXkbhDuomN0/KaTNYJe9APT4MFiFNWzbhOgiHzqxuz2qA3HHbRjnU
I3W4LXaWuNDHheAmvoUHlDupT50lcc3p5JvFSrB6UtWG0zoYdAdaO22QIDMgIO41
xS2eakeOiskSHJXGW9z4TWGNALnTMkNp1+CE0Bm5UpeLgXZwa0vGrR07hh/6dOKB
m0w4+ei8ddxe5cTkeXy/UBWFOWVtCfJZCLKbRo6eYJXDyJausH7nVcbOM23hSUUU
KDskU7C4BWx8OzuReYx/V4pQxiPKcWbYvPVh81UYn1aoleg4RIyAoNnjVPDQ6sY5
lIKLxdzSG3bAXCWzGsPgTsOgmo1wo/A5ByMscj5pa98hsYR71hsrFK5+r1pQn49c
2jX2ba9hseYqJnBXUMn1YpA8GNJvXB5U1J7p/H/TWvHch3T8IpM5umbUDV3sX4sE
0xBIFEtIR2HpRzknArLJeqWeiDTDNxgbEYRx9dimgNig2nx2yJr6NU8hEfQgK4wi
hcc4nQlY8s7P1lEQUzfo
=KKBh
-----END PGP SIGNATURE-----

--GivQfaJNHtsASJhWDN22j8QoGvSGmpLCU--


From nobody Mon Sep 28 04:37:49 2015
Return-Path: <aland@deployingradius.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A831A8A0B; Mon, 28 Sep 2015 04:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, WEIRD_PORT=0.001] 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 Gyepcl2xWu8d; Mon, 28 Sep 2015 04:37:44 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC8B1A899D; Mon, 28 Sep 2015 04:37:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 6643022405AC; Mon, 28 Sep 2015 13:37:13 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DUXufwTWq27n; Mon, 28 Sep 2015 13:37:10 +0200 (CEST)
Received: from [192.168.2.14] (bas1-ottawa11-1176122299.dsl.bell.ca [70.26.51.187]) by power.freeradius.org (Postfix) with ESMTPSA id 81CA222404F8; Mon, 28 Sep 2015 13:37:09 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <56091FDD.9030701@restena.lu>
Date: Mon, 28 Sep 2015 07:37:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E2C45E5-D573-473D-BEFE-8A0ED14036C4@deployingradius.com>
References: <20150928030705.92AA04502F@ariadne.telemancy.com> <5608FE64.8090209@cisco.com> <56091FDD.9030701@restena.lu>
To: Winter Stefan <stefan.winter@restena.lu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/QbfU25U6bmfCSxEpmc4NhNmuNM8>
Cc: aaa-doctors@ietf.org, "radext-chairs@tools.ietf.org" <radext-chairs@tools.ietf.org>, radext@ietf.org
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4485)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2015 11:37:48 -0000

On Sep 28, 2015, at 7:09 AM, Stefan Winter <stefan.winter@restena.lu> =
wrote:
> hm, I'm not so sure. The errata notes contain the assertion that =
RFC2866
> was not meant to be used like that.
>=20
> But that statement is not a given.

  The main problem with the RADIUS RFCs is that they make a lot of =
assumptions, and leave a lot unsaid.  As a result, a huge portion of odd =
behaviour is neither permitted nor denied.

  I've had *many* discussions with people who claim "X is allowed by the =
RFCs".  No... it's not *disallowed*.  But there is no statement saying =
"You can do X".

  The same applies here.

> the RFC states in 4.1 that
>=20
> "Any attribute valid in a RADIUS Access-Request or Access-Accept
>      packet is valid in a RADIUS Accounting-Request packet, except =
that
>      the following attributes MUST NOT [...]"
>=20
> So, sending Called-Station-Id is something that's allowed just fine.

  Yes, but that's a separate issue.

> It is not reasonable to assume the On/Off is atomic for the entire NAS =
-
> the text "(for example, just before a scheduled reboot)" is really =
jsut
> that - an example.

  This is a problem with ambiguity in the language.  Is it:

a) On/Off is used to signal the start or stop of RADIUS accounting for =
the NAS.  e.g. for example, when the NAS boots or is about to go down

  or

b) On/Off is use to signal (for example) the start or stop of RADIUS =
accounting.

  I think the answer is (a).  The interpretation of (b) would indicate =
that On/Off can really mean anything.  Which makes them useless.

> True, it is not defined how this attribute is supposed to be used and
> that the action "only terminate Accounting for sessions matching this
> Called-Station-Id" is not explicitly defined.

  Like too many things in RADIUS.

  The problem is that until recently, *everyone* treated On/Off as "NAS =
reboot".  And marked all "matching" sessions as offline.

  I say "matching" sessions because the RFCs are silent on this.  Which =
means much behaviour is implementation-defined.

> But I do not concur with the consequence that all Accounting-On/Off =
must
> be treated as an atomic operation for the entire NAS.

  I would agree to that.  It's what everyone has been doing until fairly =
recently.

> If a reaction to this admitted ambiguity is needed, IMHO it should not
> take the form of an errata which retroactively makes everyone else's
> halfways reasonable assumption of behaviour incorrect, but take the =
form
> of an RFC making the desired behaviour explicit.

  I see the errata as documenting existing practice.

> In that latter case, I am even against the errata Notes suggestion -
> there is no need for "Scoped-Accounting-*" - instead, an RFC can very
> simply clarify the matters by stating:
>=20
> "Presence of additional attributes in Accounting-On/Off means that
> accounting is starting/stopping only for sessions matching the
> attributes that are present in the packet."

 *Which* attributes?  All of them?  None?  Some random sample?

  You can't just wave your hands and go "People will know what I mean".  =
This errata exists precisely of ambiguities in the specs.

  I fully support a new value for Acct-Status-Type for "subsystem =
on/off".  Since the values for Acct-Status-Type are assigned by "expert =
review", there's nothing stopping us from doing that now.  There are =
(approximately) 2^32 unused values for Acct-Status-Type.  I suggest that =
explicit descriptions of behaviour (Subsystem on/off) is better than =
implicit descriptions (On/Off with ???? some different attributes)

  The various vendors implementing the *changed* behaviour for On/Off =
didn't request a new value.  Doing so would have avoided this problem.

  I *really* think that On/Off is the wrong thing to  use for subsystem =
reboot.  At least until we have some *standard* for what a "session =
identification attribute" is.  We had that discussion with RFC 5176, and =
everyone agreed to disagree.  Which makes me think any agreement is =
impossible.

> Thinking of it further, *that* would also be an errata text I could =
live
> with :-)
>=20
> But an interesting nuance to discuss. Looking forward to Lionel's =
opinion.
>=20
> Greetings,
>=20
> Stefan Winter
>=20
> Am 28.09.2015 um 10:46 schrieb Benoit Claise:
>> FYI.
>>=20
>> Regards, Benoit
>>=20
>>=20
>> -------- Forwarded Message --------
>> Subject:     Re: [Technical Errata Reported] RFC2866 (4485)
>> Date:     Sun, 27 Sep 2015 20:07:05 -0700
>> From:     Carl Rigney <cdr@telemancy.com>
>> To:     bclaise@cisco.com, cdr@telemancy.com, joelja@bogus.com,
>> rfc-editor@rfc-editor.org
>> CC:     nick.lowe@lugatech.com
>>=20
>>=20
>>=20
>> That seems like a reasonable clarification to me.
>>=20
>> --=20
>> Carl Rigney
>> cdr@telemancy.com
>>=20
>> On Sun, Sep 27, 2015 at 9:51 AM, RFC Errata System
>> <rfc-editor@rfc-editor.org> wrote:
>>=20
>>    The following errata report has been submitted for RFC2866,
>>    "RADIUS Accounting".
>>=20
>>    --------------------------------------
>>    You may review the report below and at:
>>    http://www.rfc-editor.org/errata_search.php?rfc=3D2866&eid=3D4485
>>=20
>>    --------------------------------------
>>    Type: Technical
>>    Reported by: Nick Lowe <nick.lowe@lugatech.com
>>=20
>>    Section: 5.1
>>=20
>>    Original Text
>>    -------------
>>    This attribute indicates whether this Accounting-Request
>>    marks the beginning of the user service (Start) or the end (Stop).
>>=20
>>    It MAY be used by the client to mark the start of accounting
>>    (for example, upon booting) by specifying Accounting-On and
>>    to mark the end of accounting (for example, just before a
>>    scheduled reboot) by specifying Accounting-Off.
>>=20
>>    Corrected Text
>>    --------------
>>    This attribute indicates
>>    whether this Accounting-Request marks the beginning of the
>>    user service (Start) or the end (Stop).
>>=20
>>    It MAY be used by the client to mark the start of accounting
>>    for the NAS (for example, upon booting) by specifying
>>    Accounting-On and to mark the end of accounting for the NAS
>>    (for example, just before a scheduled reboot) by specifying
>>    Accounting-Off.
>>=20
>>    Notes
>>    -----
>>    Some RADIUS client implementations send scoped Accounting-On
>>    and Accounting-Off Accounting-Request packets.  This is
>>    seen, for example, with some wireless APs that include a
>>    Called-Station-Id attribute to scope to a Basic Service Set (BSS).
>>=20
>>    This is an incorrect interpretation of the RFC that is not
>>    backwards compatible with consumers of RADIUS accounting
>>    information, yet the RFC is ambiguous on this point.
>>=20
>>    The RFC must be clear that Accounting-On and Accounting-Off
>>    apply to the whole NAS and cannot be scoped in this manner.
>>=20
>>    New Acct-Status-Type values must instead be defined to allow
>>    this, perhaps named something like Scoped-Accounting-On and
>>    Scoped-Accounting-Off.
>>=20
>>    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.
>>=20
>>    --------------------------------------
>>    RFC2866 (draft-ietf-radius-accounting-v2-05)
>>    --------------------------------------
>>    Title               : RADIUS Accounting Publication
>>    Date    : June 2000
>>    Author(s) : C. Rigney
>>    Category            : INFORMATIONAL
>>    Source : Remote Authentication Dial-In User Service
>>    Area : Operations and Management
>>    Stream              : IETF
>>    Verifying Party     : IESG
>>=20
>=20
>=20
> --=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education =
Nationale et
> de la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
> PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
> recipient's key is known to me
>=20
> http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xC0DE6A358A39DC66=

>=20
> =
<0x8A39DC66.asc><0x8A39DC66.asc>__________________________________________=
_____
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors


From nobody Tue Sep 29 07:23:19 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88AC1B41C8 for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 07:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 GF35E_j8cVOo for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 07:23:16 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF5B71B41C6 for <aaa-doctors@ietf.org>; Tue, 29 Sep 2015 07:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2553; q=dns/txt; s=iport; t=1443536595; x=1444746195; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=PEkIduWAEpkYc0Z9zDyE5Y2jACq/d24/GfFz3B2CYfE=; b=HXqqZtrvodRjn+hNGwnZ69XD+C/QQbYRqi/TlqCk0lohkxFmoX1VwoiR 39v6vhjG2+YEGmElaT53njGDEk7uqXXzPZyHtxkQeGU8od92vAcjsuAmJ b5fXfgny3lO53KyteM3iMamIW29PfpoIvc5VB+Lxcr96JgGVLd5qGKcP7 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DJAQBdngpW/xbLJq1EGoN4ab1kAQ2Be4V5AoIFFAEBAQEBAQGBCoQlAQEEOEEQCyElDwJGBwwGAgEBiCoNO8smAQEBAQEBAQEBAQEBAQEBAQEBGoZzhH2BPYNQB4QsAQSHNQeGdYQTgzCNE4FPhDaDAJI/HwEBQoIRDQ+BVjwzAROJCwEBAQ
X-IronPort-AV: E=Sophos;i="5.17,608,1437436800"; d="scan'208";a="630034664"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 29 Sep 2015 14:23:12 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t8TENCav031902; Tue, 29 Sep 2015 14:23:12 GMT
To: cdr@telemancy.com, joelja@bogus.com
References: <20150929140750.2AFFD180470@rfc-editor.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <560A9ED0.10306@cisco.com>
Date: Tue, 29 Sep 2015 16:23:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150929140750.2AFFD180470@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/mq51DqC-QGgCjHkT0SX8SnJOJMo>
Cc: nick.lowe@lugatech.com, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4488)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 14:23:18 -0000

And another one to discuss.

Regards, Benoit
> The following errata report has been submitted for RFC2866,
> "RADIUS Accounting".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2866&eid=4488
>
> --------------------------------------
> Type: Technical
> Reported by: Nick Lowe <nick.lowe@lugatech.com>
>
> Section: 5.11
>
> Original Text
> -------------
> Acct-Multi-Session-Id
>
>     Description
>
>        This attribute is a unique Accounting ID to make it easy to link
>        together multiple related sessions in a log file.  Each session
>        linked together would have a unique Acct-Session-Id but the same
>        Acct-Multi-Session-Id.  It is strongly recommended that the Acct-
>        Multi-Session-Id contain UTF-8 encoded 10646 [7] characters.
>
> Corrected Text
> --------------
> Acct-Multi-Session-Id
>
>     Description
>
>        This attribute is a globally unique Accounting ID to make it easy
>        to link together multiple related sessions in a log file.  Each
>        session linked together would have a globally unique
>        Acct-Session-Id but the same Acct-Multi-Session-Id.  It is
>        strongly recommended that the Acct-Multi-Session-Id contain
>        UTF-8 encoded 10646 [7] characters.
>
> Notes
> -----
> The RFC does not explicitly state the scope of uniqueness and it must be clarified to state that Acct-Multi-Session-Ids are expected to be globally unique. I believe this to be the original, implicit intent of the author.
>
> An ideal Acct-Multi-Session-Id would have the properties of a GUID/UUID.
>
> See Errata 4487 for the same clarification on the Acct-Session-Id.
>
> 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.
>
> --------------------------------------
> RFC2866 (draft-ietf-radius-accounting-v2-05)
> --------------------------------------
> Title               : RADIUS Accounting
> Publication Date    : June 2000
> Author(s)           : C. Rigney
> Category            : INFORMATIONAL
> Source              : Remote Authentication Dial-In User Service
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>
> .
>


From nobody Tue Sep 29 07:23:48 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA731B41CE for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 07:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 aO4K9jgcYklp for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 07:23:44 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 662C51B41CD for <aaa-doctors@ietf.org>; Tue, 29 Sep 2015 07:23:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3222; q=dns/txt; s=iport; t=1443536624; x=1444746224; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=xNdRYKVQgmbapEBR1jGVJKxyAEbaJOq5MQwtmjM8uvE=; b=NClqRO/VcgbJsVpSzuJp9x68dtBLytXBD5d3bP5p+3ak0j5kWUzLTzIH IWgUgvt9+ehLYBop8ostCXvPByB/oVtrqwwrmnfCS0rf1upQOgFHZawVB P25uTjHNRD/VhlJsO4oSs0lSNdK31cX/+kwr5ou5Y8EfbGei3vjpV/+t8 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CeBABdngpW/xbLJq1EGoN4abRNiyCFeQKCGQEBAQEBAYELhCUBAQQ4QAEQCxgJFg8JAwIBAgFFBwwGAgEBiCoNO8smAQEBAQEBAQEBAQEBAQEBAQEBARmGc4R9gT2DUAeELAEEhzUHhnWHQ4UWh32BT0aDcIMAkj9jghEND4FWPDMBE4kLAQEB
X-IronPort-AV: E=Sophos;i="5.17,608,1437436800"; d="scan'208";a="607313761"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 29 Sep 2015 14:23:41 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t8TENe8w025268; Tue, 29 Sep 2015 14:23:40 GMT
To: cdr@telemancy.com, joelja@bogus.com
References: <20150929120435.6FCE2188CEB@rfc-editor.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <560A9EEC.2000403@cisco.com>
Date: Tue, 29 Sep 2015 16:23:40 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150929120435.6FCE2188CEB@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/mv4Hj-gJiNboTRnCqtai1TErvHg>
Cc: nick.lowe@lugatech.com, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4487)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 14:23:46 -0000

On 29/09/2015 14:04, RFC Errata System wrote:
> The following errata report has been submitted for RFC2866,
> "RADIUS Accounting".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2866&eid=4487
>
> --------------------------------------
> Type: Technical
> Reported by: Nick Lowe <nick.lowe@lugatech.com>
>
> Section: 5.5
>
> Original Text
> -------------
> Acct-Session-Id
>
>     Description
>
>        This attribute is a unique Accounting ID to make it easy to match
>        start and stop records in a log file.  The start and stop records
>        for a given session MUST have the same Acct-Session-Id.  An
>        Accounting-Request packet MUST have an Acct-Session-Id.  An
>        Access-Request packet MAY have an Acct-Session-Id; if it does,
>        then the NAS MUST use the same Acct-Session-Id in the Accounting-
>        Request packets for that session.
>
>        The Acct-Session-Id SHOULD contain UTF-8 encoded 10646 [7]
>        characters.
>
> Corrected Text
> --------------
> Acct-Session-Id
>
>     Description
>
>        This attribute is a globally unique Accounting ID to make it easy
>        to match start and stop records in a log file.  The start and stop
>        records for a given session MUST have the same Acct-Session-Id.
>        An Accounting-Request packet MUST have an Acct-Session-Id.
>        An Access-Request packet MAY have an Acct-Session-Id; if it does,
>        then the NAS MUST use the same Acct-Session-Id in the Accounting-
>        Request packets for that session.
>
>        The Acct-Session-Id SHOULD contain UTF-8 encoded 10646 [7]
>        characters.
>
> Notes
> -----
> A very common implementation fault in RADIUS clients that perform accounting is that Acct-Session-Ids are observed to be reused after a NAS is rebooted or are only unique only in the scope/context of a NAS.
>
> The RFC does not explicitly state the scope of uniqueness and it must be clarified to state that Acct-Session-Ids are expected to be globally unique. I believe this to be the original, implicit intent of the author.
>
> This is necessary because the ambiguity causes substantial implementation issues today.
>
> See: http://freeradius.org/radiusd/man/rlm_acct_unique.txt
>
> An ideal Acct-Session-Id would have the properties of a GUID/UUID.
>
> 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.
>
> --------------------------------------
> RFC2866 (draft-ietf-radius-accounting-v2-05)
> --------------------------------------
> Title               : RADIUS Accounting
> Publication Date    : June 2000
> Author(s)           : C. Rigney
> Category            : INFORMATIONAL
> Source              : Remote Authentication Dial-In User Service
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>
> .
>


From nobody Tue Sep 29 07:47:46 2015
Return-Path: <aland@deployingradius.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EEC1B435E for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 07:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 nYWJNKYJgnoD for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 07:47:42 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1CE1B435C for <aaa-doctors@ietf.org>; Tue, 29 Sep 2015 07:47:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 687622240715; Tue, 29 Sep 2015 16:47:11 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3o5nTFFvinEp; Tue, 29 Sep 2015 16:47:09 +0200 (CEST)
Received: from [192.168.20.14] (69-196-165-104.dsl.teksavvy.com [69.196.165.104]) by power.freeradius.org (Postfix) with ESMTPSA id C0F7A224050C; Tue, 29 Sep 2015 16:47:07 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <560A9ED0.10306@cisco.com>
Date: Tue, 29 Sep 2015 10:47:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A403E6C-706B-4FA5-AF6F-9466DA613E4E@deployingradius.com>
References: <20150929140750.2AFFD180470@rfc-editor.org> <560A9ED0.10306@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/s9xRZNm0cqS1zjmfSpuUbCXFS-I>
Cc: Joel Jaeggli <joelja@bogus.com>, cdr@telemancy.com, nick.lowe@lugatech.com, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4488)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 14:47:45 -0000

  I think the Acct-Session-Id *should* be globally unique, but I think =
just adding the word "global" is insufficient.

  RFC 2865 Section 3 says this about the Request Authenticator:

         ...  the Request Authenticator field
         SHOULD exhibit global and temporal uniqueness.

  We could have similar text about uniqueness for Acct-Session-ID, and =
Acct-Multi-Session-ID.

  On a practical note, I've found that it's pretty much impossible to =
rely on Acct-Session-ID as being in any way unique.  Most NAS equipment =
has *terrible* choices for Acct-Session-ID.  e.g. start at "00000000" =
when the NAS reboots, and increment for every new session.  Having IDs =
generated via a cryptographically strong pseudo-random number generate =
would be *much* better.

  I typically end up creating a separate ID, let's call it =
"Better-Acct-Session-ID".  That ID is composed of a cryptographic hash =
of the original Acct-Session-ID, and a number of other session =
identification attributes.  That ID can be relied on to be unique in =
cases where Acct-Session-ID is essentially garbage.

  So.. I'm in favour of making RFC 2866 clearer that Acct-Session-ID is =
UNIQUE, and not just sort of unique, sometimes, maybe.

On Sep 29, 2015, at 10:23 AM, Benoit Claise <bclaise@cisco.com> wrote:

> And another one to discuss.
>=20
> Regards, Benoit
>> The following errata report has been submitted for RFC2866,
>> "RADIUS Accounting".
>>=20
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3D2866&eid=3D4488
>>=20
>> --------------------------------------
>> Type: Technical
>> Reported by: Nick Lowe <nick.lowe@lugatech.com>
>>=20
>> Section: 5.11
>>=20
>> Original Text
>> -------------
>> Acct-Multi-Session-Id
>>=20
>>    Description
>>=20
>>       This attribute is a unique Accounting ID to make it easy to =
link
>>       together multiple related sessions in a log file.  Each session
>>       linked together would have a unique Acct-Session-Id but the =
same
>>       Acct-Multi-Session-Id.  It is strongly recommended that the =
Acct-
>>       Multi-Session-Id contain UTF-8 encoded 10646 [7] characters.
>>=20
>> Corrected Text
>> --------------
>> Acct-Multi-Session-Id
>>=20
>>    Description
>>=20
>>       This attribute is a globally unique Accounting ID to make it =
easy
>>       to link together multiple related sessions in a log file.  Each
>>       session linked together would have a globally unique
>>       Acct-Session-Id but the same Acct-Multi-Session-Id.  It is
>>       strongly recommended that the Acct-Multi-Session-Id contain
>>       UTF-8 encoded 10646 [7] characters.
>>=20
>> Notes
>> -----
>> The RFC does not explicitly state the scope of uniqueness and it must =
be clarified to state that Acct-Multi-Session-Ids are expected to be =
globally unique. I believe this to be the original, implicit intent of =
the author.
>>=20
>> An ideal Acct-Multi-Session-Id would have the properties of a =
GUID/UUID.
>>=20
>> See Errata 4487 for the same clarification on the Acct-Session-Id.
>>=20
>> 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.
>>=20
>> --------------------------------------
>> RFC2866 (draft-ietf-radius-accounting-v2-05)
>> --------------------------------------
>> Title               : RADIUS Accounting
>> Publication Date    : June 2000
>> Author(s)           : C. Rigney
>> Category            : INFORMATIONAL
>> Source              : Remote Authentication Dial-In User Service
>> Area                : Operations and Management
>> Stream              : IETF
>> Verifying Party     : IESG
>>=20
>> .
>>=20
>=20
> _______________________________________________
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors


From nobody Tue Sep 29 15:02:31 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05A31B5321 for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 15:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 9J9pextkBmSZ for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 15:02:28 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88B9C1B5316 for <aaa-doctors@ietf.org>; Tue, 29 Sep 2015 15:02:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2769; q=dns/txt; s=iport; t=1443564141; x=1444773741; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=BMziLA3eicvYdqT6OZ9twqhWmdGG/lE7k2Ujl0CHehU=; b=WN8KY/nBdFbevchAmr81kErXNJ8EutIwilGIv/BngSXIgJWo3tK1KpyC fehca1e/shWFl1onccZvCsLeQQbwMmOrezWW5KeSpHKWcw1Y2QcJTLM/X e2ayMgc93QUqY1l3IdfB4LLSX4ZIQZazAI1EkvnAFh7pbdnDC8iR+JEfO E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CaBAD3CQtW/xbLJq1ehGG9d4d0AoIMEwEBAQEBAQGBCoQlAQEEDhUVLRMBEAsYAgIFDAoLAgIJAwIBAgFFBgEMBgIBAYgqtx+UZAEBAQEBAQEBAQEBAQEBAQEBAQEZgSKFUYR9gT2Cdw5LBwqCX4FDAQSVdI0TiQWSPyIBQIIegWU8M4dWgUgBAQE
X-IronPort-AV: E=Sophos;i="5.17,609,1437436800"; d="scan'208";a="611922819"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 29 Sep 2015 22:02:00 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t8TM205G018698; Tue, 29 Sep 2015 22:02:00 GMT
To: Nick Lowe <nick.lowe@lugatech.com>, Carl Rigney <cdr@telemancy.com>
References: <20150929140750.2AFFD180470@rfc-editor.org> <20150929201209.584AC4502F@ariadne.telemancy.com> <CAGnO3doNDwHV88H14SVRA61x3QZQqTWVTw+pEW_jpyo3F_q92Q@mail.gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <560B0A58.9020600@cisco.com>
Date: Wed, 30 Sep 2015 00:02:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CAGnO3doNDwHV88H14SVRA61x3QZQqTWVTw+pEW_jpyo3F_q92Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/SR8wL4Dm4Fc3bE-EdyaSR4786r4>
Cc: joelja@bogus.com, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, Alan DeKok <aland@deployingradius.com>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4488)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 22:02:30 -0000

[including the AAA doctors]

Regards, Benoit
> Thanks for the clarification Carl!
>
> At first sight, to me, it is far more realistic and pragmatic to see a
> globally unique id in the Acct-Session-Id going forward rather than
> introducing another attribute.
>
> Systems would likely remain non-compatible for a long time to a new
> attribute. There would be inherent complexity doing this that would
> easily lead to nuanced handling issues.
>
> A clarification to the RFC for the Acct-Session-Id, which is not clear
> in this area today so there is room for manoeuvre, would regress very
> little and fix a lot.
> That is, despite what the original intent was, it is a highly
> backwards compatible clarification that enhances and improves RADIUS.
>
> On balance, I feel that it is the right thing to do when the poor
> quality Acct-Session-Id issues we see today are considered, along with
> the kludges necessary to work with that accounting information. (Even
> then such kludges do not always work and duplicates are encountered.)
>
> The present status quo is highly undesirable and seems unnecessary.
>
> Poor implementations could and would carry on as normal, a
> clarification to the RFC would provide the feedback means to get
> better RADIUS client implementations in the field going forward.
>
> Kind regards,
>
> Nick Lowe
>
> On Tue, Sep 29, 2015 at 9:12 PM, Carl Rigney <cdr@telemancy.com> wrote:
>> It was not at all the intent of the original RADIUS working group
>> to make Account-Session-Id or Acct-Multi-Session-Id globally unique.
>> They were only intended to be unique to that NAS on that boot, as
>> a way for servers to acknowledge to the NAS that they'd received
>> the record and the NAS could remove it from its retransmit buffer,
>> and to make it easier for the Accounting Server to match start and
>> stop and interim records, using the ID and either NAS-IP-Address
>> or NAS-Identifier.  The Acct-Session-Id example given explicitly
>> acknowledges it might wrap.
>>
>> There was never any idea that any given NAS would know about the
>> existence of any other NAS, or maintain a lot of state between boots
>> other than knowing its RADIUS server IP address and shared secret.
>>
>> RADIUS was written to be runnable on boxes with very weak CPUS
>> (remember the 80286?) and limited memory, back in the days when one
>> megabyte was a lot.
>>
>> If you want some cryptographically strong universal ID, I'd definitely
>> recommend allocating a new Attribute for that, instead of attempting
>> to shoehorn it retroactively into an attribute never intended for it.
>>
>> That's my 2 cents as one of the original authors.
>>
>> --
>> Carl Rigney
>> cdr@telemancy.com
> .
>


From nobody Tue Sep 29 15:25:52 2015
Return-Path: <aland@deployingradius.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 455421B33E2 for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 15:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 dE_Es-veyIo3 for <aaa-doctors@ietfa.amsl.com>; Tue, 29 Sep 2015 15:25:45 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id E634D1B33D6 for <aaa-doctors@ietf.org>; Tue, 29 Sep 2015 15:25:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 5288F2240715; Wed, 30 Sep 2015 00:25:14 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cvDYXDb4WUIy; Wed, 30 Sep 2015 00:25:12 +0200 (CEST)
Received: from [192.168.2.14] (bas1-ottawa11-1176122299.dsl.bell.ca [70.26.51.187]) by power.freeradius.org (Postfix) with ESMTPSA id DC83A2240430; Wed, 30 Sep 2015 00:25:10 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <560B0A58.9020600@cisco.com>
Date: Tue, 29 Sep 2015 18:25:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D0FED64-A6AB-4CE1-8591-8EE02BBE1628@deployingradius.com>
References: <20150929140750.2AFFD180470@rfc-editor.org> <20150929201209.584AC4502F@ariadne.telemancy.com> <CAGnO3doNDwHV88H14SVRA61x3QZQqTWVTw+pEW_jpyo3F_q92Q@mail.gmail.com> <560B0A58.9020600@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/yKfHeVcWPUpdRloxFNNd1ADFJSE>
Cc: Nick Lowe <nick.lowe@lugatech.com>, Carl Rigney <cdr@telemancy.com>, joelja@bogus.com, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4488)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 22:25:47 -0000

>> At first sight, to me, it is far more realistic and pragmatic to see =
a
>> globally unique id in the Acct-Session-Id going forward rather than
>> introducing another attribute.

  Unfortunately, such technical changes are outside of the scope of an =
errata.

>> The present status quo is highly undesirable and seems unnecessary.

  As with many things RADIUS, unfortunately.  We're left with being =
compatible with a protocol designed 20+ years ago.

>> Poor implementations could and would carry on as normal, a
>> clarification to the RFC would provide the feedback means to get
>> better RADIUS client implementations in the field going forward.

  This errata could arguably have gone into the "issues and fixes" =
document, as a clarification.  Unfortunately, it was missed.

>> On Tue, Sep 29, 2015 at 9:12 PM, Carl Rigney <cdr@telemancy.com> =
wrote:
>>> It was not at all the intent of the original RADIUS working group
>>> to make Account-Session-Id or Acct-Multi-Session-Id globally unique.
>>> They were only intended to be unique to that NAS on that boot, as
>>> a way for servers to acknowledge to the NAS that they'd received
>>> the record and the NAS could remove it from its retransmit buffer,
>>> and to make it easier for the Accounting Server to match start and
>>> stop and interim records, using the ID and either NAS-IP-Address
>>> or NAS-Identifier.  The Acct-Session-Id example given explicitly
>>> acknowledges it might wrap.

  That's OK.

>>> There was never any idea that any given NAS would know about the
>>> existence of any other NAS, or maintain a lot of state between boots
>>> other than knowing its RADIUS server IP address and shared secret.

  I don't think such tracking is necessary.

>>> RADIUS was written to be runnable on boxes with very weak CPUS
>>> (remember the 80286?) and limited memory, back in the days when one
>>> megabyte was a lot.

  Sure.=20

>>> If you want some cryptographically strong universal ID, I'd =
definitely
>>> recommend allocating a new Attribute for that, instead of attempting
>>> to shoehorn it retroactively into an attribute never intended for =
it.

  The original intent of Acct-Session-ID is nice to know, but I don't =
think it should be a limiting factor.  The main requirements are =
inter-operability, and no change to the *meaning* of the attribute.  I =
think the suggestion to create it's value via a CSPRNG meets all of =
those criteria.  There is no requirement that it *must* wrap, or that it =
*must* be an incrementing counter.

  Every other entity in the network treats Acct-Session-ID as an opaque =
token.  By definition, changing the *contents* of the opaque token has =
no effect on other entities in the network.

  In any case, I think the errata should be rejected.  It's (IMHO) a =
good idea, but an errata isn't really the place to make technical =
changes to the RADIUS protocol.

  Let's see if the RADEXT WG has enough bandwidth for yet another =
"update RADIUS" document. :)

  Alan DeKok.


From nobody Wed Sep 30 06:50:47 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B57B1A8728 for <aaa-doctors@ietfa.amsl.com>; Wed, 30 Sep 2015 06:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 aETsLvvfLJUK for <aaa-doctors@ietfa.amsl.com>; Wed, 30 Sep 2015 06:50:42 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B746B1A8712 for <aaa-doctors@ietf.org>; Wed, 30 Sep 2015 06:50:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5158; q=dns/txt; s=iport; t=1443621041; x=1444830641; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=FDbApq5m9mdyj8VNdsUbq1M2MTuZ2QBEWw+7KOxDJVw=; b=EbNLmtYdpnuaKn0cY5TxonY0gQzQi14o4JXVWZaKot4/wccY6HRx5UOX sxVG098LKKL2eq6NZnRiSND26c28xQkfFSxtV0AE5ait2YcC/8/zCzp46 t1qkWTQNqyDWm9GBJXiMeNIn8PGxALH5Fa7XLYARIdDC0MhB6feozUM6j w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DPAQDY5wtW/xbLJq1EGoN4aYMrukQBDYF7hXkCgW8UAQEBAQEBAYEKhCQBAQEEIw8BBUABEAsVAgECAgUWCwICCQMCAQIBPQgGAQwGAgEBiCoNO7Y6lGgBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSKFUYR9gT2DUAeCaYFDAQSHNgiGdYQTgzKNE4FPhDaDAIdnimQfAQFCghENEIFWPDMBE4kKAQEB
X-IronPort-AV: E=Sophos;i="5.17,612,1437436800"; d="scan'208";a="630054590"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 30 Sep 2015 13:50:39 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t8UDodi3022783; Wed, 30 Sep 2015 13:50:39 GMT
To: Nick Lowe <nick.lowe@lugatech.com>, Carl Rigney <cdr@telemancy.com>
References: <20150927165155.D21A5187E4E@rfc-editor.org> <20150928030705.92AA04502F@ariadne.telemancy.com> <CAGnO3dpLzZzksuhN9+CmdFU4jKPWNL6QO4PrAdYRe2QPSq4wHA@mail.gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <560BE8AF.8040506@cisco.com>
Date: Wed, 30 Sep 2015 15:50:39 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CAGnO3dpLzZzksuhN9+CmdFU4jKPWNL6QO4PrAdYRe2QPSq4wHA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/yd7OfpPYmWe0vyqb-SbKHyWKBZk>
Cc: joel jaeggli <joelja@bogus.com>, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4485)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2015 13:50:46 -0000

Including the AAA doctors.

B.
> Hi all,
>
> I ought to supply you with the response that I have just had from
> Aerohive Tier 3 regarding their RADIUS client implementation in
> HiveOS, the OS for their APs, as it is pertinent to what is being
> considered.
>
> Please feel free to copy it to the list.
>
> Without the erratum being approved to close the ambiguity, it is
> unlikely that I will be able to get this changed.
>
> I agree with Alan that On-Off is conceptually meaningless without it
> applying to the whole NAS. I believe the erratum is valid and should
> be approved therefore.
>
> Kind regards,
>
> Nick Lowe
>
> "From: Keith McIntyre (Aerohive)
> To: Nick Lowe
> Cc: Gary Smith
> Subject: Accounting-On and Accounting-Off should be sent, by default,
> on a per-NAS basis not per-BSS
>
> Hey Nick,
>
> Engineering have reviewed the CFD and the information that you
> provided. They are in agreement that this is not a specific defect in
> the way that Aerohive have implemented this feature, rather this is a
> request to improve upon it.
>
> Aerohive complies with the way the RFC is written and there is no
> specific defect reported. As a result I will open a Feature Request to
> request enhancement as you’ve requested. Based on the current
> understanding this is a request to enhance currently designed
> behaviour with no specific HiveOS defect reported.
>
> If you have any questions I will be happy to discuss and provide a
> followup to our engineering team.
>
> Cheers,
>
> Keith"
>
> On Mon, Sep 28, 2015 at 4:07 AM, Carl Rigney <cdr@telemancy.com> wrote:
>> That seems like a reasonable clarification to me.
>>
>> --
>> Carl Rigney
>> cdr@telemancy.com
>>
>> On Sun, Sep 27, 2015 at 9:51 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>>
>>          The following errata report has been submitted for RFC2866,
>>          "RADIUS Accounting".
>>
>>          --------------------------------------
>>          You may review the report below and at:
>>          http://www.rfc-editor.org/errata_search.php?rfc=2866&eid=4485
>>
>>          --------------------------------------
>>          Type: Technical
>>          Reported by: Nick Lowe <nick.lowe@lugatech.com
>>
>>          Section: 5.1
>>
>>          Original Text
>>          -------------
>>          This attribute indicates whether this Accounting-Request
>>          marks the beginning of the user service (Start) or the end (Stop).
>>
>>          It MAY be used by the client to mark the start of accounting
>>          (for example, upon booting) by specifying Accounting-On and
>>          to mark the end of accounting (for example, just before a
>>          scheduled reboot) by specifying Accounting-Off.
>>
>>          Corrected Text
>>          --------------
>>          This attribute indicates
>>          whether this Accounting-Request marks the beginning of the
>>          user service (Start) or the end (Stop).
>>
>>          It MAY be used by the client to mark the start of accounting
>>          for the NAS (for example, upon booting) by specifying
>>          Accounting-On and to mark the end of accounting for the NAS
>>          (for example, just before a scheduled reboot) by specifying
>>          Accounting-Off.
>>
>>          Notes
>>          -----
>>          Some RADIUS client implementations send scoped Accounting-On
>>          and Accounting-Off Accounting-Request packets.  This is
>>          seen, for example, with some wireless APs that include a
>>          Called-Station-Id attribute to scope to a Basic Service Set (BSS).
>>
>>          This is an incorrect interpretation of the RFC that is not
>>          backwards compatible with consumers of RADIUS accounting
>>          information, yet the RFC is ambiguous on this point.
>>
>>          The RFC must be clear that Accounting-On and Accounting-Off
>>          apply to the whole NAS and cannot be scoped in this manner.
>>
>>          New Acct-Status-Type values must instead be defined to allow
>>          this, perhaps named something like Scoped-Accounting-On and
>>          Scoped-Accounting-Off.
>>
>>          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.
>>
>>          --------------------------------------
>>          RFC2866 (draft-ietf-radius-accounting-v2-05)
>>          --------------------------------------
>>          Title               : RADIUS Accounting Publication
>>          Date    : June 2000
>>          Author(s) : C. Rigney
>>          Category            : INFORMATIONAL
>>          Source : Remote Authentication Dial-In User Service
>>          Area : Operations and Management
>>          Stream              : IETF
>>          Verifying Party     : IESG
>>
> .
>


From nobody Wed Sep 30 12:31:30 2015
Return-Path: <aland@deployingradius.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 111841A8997 for <aaa-doctors@ietfa.amsl.com>; Wed, 30 Sep 2015 12:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 xJjHaMbm4YmG for <aaa-doctors@ietfa.amsl.com>; Wed, 30 Sep 2015 12:31:25 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 20BBC1A8996 for <aaa-doctors@ietf.org>; Wed, 30 Sep 2015 12:31:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id C58742240549; Wed, 30 Sep 2015 21:30:53 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbESscEAkOkf; Wed, 30 Sep 2015 21:30:51 +0200 (CEST)
Received: from [192.168.20.14] (69-196-165-104.dsl.teksavvy.com [69.196.165.104]) by power.freeradius.org (Postfix) with ESMTPSA id 0B4F0224050C; Wed, 30 Sep 2015 21:30:49 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <560BE8AF.8040506@cisco.com>
Date: Wed, 30 Sep 2015 15:30:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D263644-8864-489B-B0A8-C96A165F2564@deployingradius.com>
References: <20150927165155.D21A5187E4E@rfc-editor.org> <20150928030705.92AA04502F@ariadne.telemancy.com> <CAGnO3dpLzZzksuhN9+CmdFU4jKPWNL6QO4PrAdYRe2QPSq4wHA@mail.gmail.com> <560BE8AF.8040506@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aaa-doctors/-gUxXHc5zSGSoq40eQuo-_OJcTU>
Cc: Nick Lowe <nick.lowe@lugatech.com>, Carl Rigney <cdr@telemancy.com>, RFC Errata System <rfc-editor@rfc-editor.org>, joel jaeggli <joelja@bogus.com>, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC2866 (4485)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2015 19:31:28 -0000

  I think this errata should be accepted.

  I also think a solution to the larger problem would be to assign new =
values for Acct-Status-Type, of Subsystem-On and Subsystem-Off.  That =
would allow NAS vendors to indicate that a portion of the NAS has =
rebooted, without affecting the rest of the users.

  I've put a write-up online at:

http://freeradius.org/rfc/acct_status_type_subsystem.html

  Since new values for Acct-Status-Type can be assigned via expert =
review, it may be quick to get new values.

  I've sent in a request to IANA for allocation, and referenced the =
above page.


On Sep 30, 2015, at 9:50 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Including the AAA doctors.
>=20
> B.
>> Hi all,
>>=20
>> I ought to supply you with the response that I have just had from
>> Aerohive Tier 3 regarding their RADIUS client implementation in
>> HiveOS, the OS for their APs, as it is pertinent to what is being
>> considered.
>>=20
>> Please feel free to copy it to the list.
>>=20
>> Without the erratum being approved to close the ambiguity, it is
>> unlikely that I will be able to get this changed.
>>=20
>> I agree with Alan that On-Off is conceptually meaningless without it
>> applying to the whole NAS. I believe the erratum is valid and should
>> be approved therefore.
>>=20
>> Kind regards,
>>=20
>> Nick Lowe
>>=20
>> "From: Keith McIntyre (Aerohive)
>> To: Nick Lowe
>> Cc: Gary Smith
>> Subject: Accounting-On and Accounting-Off should be sent, by default,
>> on a per-NAS basis not per-BSS
>>=20
>> Hey Nick,
>>=20
>> Engineering have reviewed the CFD and the information that you
>> provided. They are in agreement that this is not a specific defect in
>> the way that Aerohive have implemented this feature, rather this is a
>> request to improve upon it.
>>=20
>> Aerohive complies with the way the RFC is written and there is no
>> specific defect reported. As a result I will open a Feature Request =
to
>> request enhancement as you=92ve requested. Based on the current
>> understanding this is a request to enhance currently designed
>> behaviour with no specific HiveOS defect reported.
>>=20
>> If you have any questions I will be happy to discuss and provide a
>> followup to our engineering team.
>>=20
>> Cheers,
>>=20
>> Keith"
>>=20
>> On Mon, Sep 28, 2015 at 4:07 AM, Carl Rigney <cdr@telemancy.com> =
wrote:
>>> That seems like a reasonable clarification to me.
>>>=20
>>> --
>>> Carl Rigney
>>> cdr@telemancy.com
>>>=20
>>> On Sun, Sep 27, 2015 at 9:51 AM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>>>=20
>>>         The following errata report has been submitted for RFC2866,
>>>         "RADIUS Accounting".
>>>=20
>>>         --------------------------------------
>>>         You may review the report below and at:
>>>         =
http://www.rfc-editor.org/errata_search.php?rfc=3D2866&eid=3D4485
>>>=20
>>>         --------------------------------------
>>>         Type: Technical
>>>         Reported by: Nick Lowe <nick.lowe@lugatech.com
>>>=20
>>>         Section: 5.1
>>>=20
>>>         Original Text
>>>         -------------
>>>         This attribute indicates whether this Accounting-Request
>>>         marks the beginning of the user service (Start) or the end =
(Stop).
>>>=20
>>>         It MAY be used by the client to mark the start of accounting
>>>         (for example, upon booting) by specifying Accounting-On and
>>>         to mark the end of accounting (for example, just before a
>>>         scheduled reboot) by specifying Accounting-Off.
>>>=20
>>>         Corrected Text
>>>         --------------
>>>         This attribute indicates
>>>         whether this Accounting-Request marks the beginning of the
>>>         user service (Start) or the end (Stop).
>>>=20
>>>         It MAY be used by the client to mark the start of accounting
>>>         for the NAS (for example, upon booting) by specifying
>>>         Accounting-On and to mark the end of accounting for the NAS
>>>         (for example, just before a scheduled reboot) by specifying
>>>         Accounting-Off.
>>>=20
>>>         Notes
>>>         -----
>>>         Some RADIUS client implementations send scoped Accounting-On
>>>         and Accounting-Off Accounting-Request packets.  This is
>>>         seen, for example, with some wireless APs that include a
>>>         Called-Station-Id attribute to scope to a Basic Service Set =
(BSS).
>>>=20
>>>         This is an incorrect interpretation of the RFC that is not
>>>         backwards compatible with consumers of RADIUS accounting
>>>         information, yet the RFC is ambiguous on this point.
>>>=20
>>>         The RFC must be clear that Accounting-On and Accounting-Off
>>>         apply to the whole NAS and cannot be scoped in this manner.
>>>=20
>>>         New Acct-Status-Type values must instead be defined to allow
>>>         this, perhaps named something like Scoped-Accounting-On and
>>>         Scoped-Accounting-Off.
>>>=20
>>>         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.
>>>=20
>>>         --------------------------------------
>>>         RFC2866 (draft-ietf-radius-accounting-v2-05)
>>>         --------------------------------------
>>>         Title               : RADIUS Accounting Publication
>>>         Date    : June 2000
>>>         Author(s) : C. Rigney
>>>         Category            : INFORMATIONAL
>>>         Source : Remote Authentication Dial-In User Service
>>>         Area : Operations and Management
>>>         Stream              : IETF
>>>         Verifying Party     : IESG
>>>=20
>> .
>>=20
>=20
> _______________________________________________
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors

