IETF Logo Mail Archive

Re: [radext] #153: Section 2.8 Access-Info

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Tue, 11 June 2013 04:24 UTC

Return-Path: <jsalowey@cisco.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BEB21F8FE5 for <radext@ietfa.amsl.com>; Mon, 10 Jun 2013 21:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGuqFV81PWGh for <radext@ietfa.amsl.com>; Mon, 10 Jun 2013 21:24:02 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 69A8621F8EFE for <radext@ietf.org>; Mon, 10 Jun 2013 21:23:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7407; q=dns/txt; s=iport; t=1370924636; x=1372134236; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=LXoqp/6wN8EkaBXjcpRWo/4f38OoSIlZt1q01N1OPH0=; b=buFOHk8CVa3faEHmkvex645tpx9SfLGtoWDuAwmuhWRfHG8PlKM32i7O Jg56tK87uYFLNYD/RychzHGawbZlxmanaH3ycXHq7qEtjeZlfb4gvy4ns NfnesPLUd+F4gx2TCEJ7NLlDuMetcFc8K+gqtyaGXcOr+CpRlHgaa9hL+ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlkFAPyktlGtJV2d/2dsb2JhbABZgkVEeawYkjF7FnSCJAEBBHkQAgEIIh0HMhQRAgQOBQiHcwMPuiiMWoElgQcxB4J/YQOIaIxyjBCBdIUkgw+BaD8
X-IronPort-AV: E=Sophos; i="4.87,842,1363132800"; d="scan'208,217"; a="221190189"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP; 11 Jun 2013 04:23:42 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5B4Ng9w002435 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Jun 2013 04:23:42 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Mon, 10 Jun 2013 23:23:42 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Thread-Topic: [radext] #153: Section 2.8 Access-Info
Thread-Index: AQHOZW4stsZL+aukRUKLu5DzU1lvWJkvjoKAgACxd4A=
Date: Tue, 11 Jun 2013 04:23:42 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628CE081E@xmb-rcd-x09.cisco.com>
References: <066.e99973544c7878635851fd28a6cf5689@trac.tools.ietf.org>, <27657_1370418838_51AEEE96_27657_5798_1_6B7134B31289DC4FAF731D844122B36E1FB0BA@PEXCVZYM13.corporate.adroot.infra.ftgroup>, <A95B4818FD85874D8F16607F1AC7C628CDB0A5@xmb-rcd-x09.cisco.com> <BLU169-W9693996E7E4D2C59FDE2CC93840@phx.gbl>
In-Reply-To: <BLU169-W9693996E7E4D2C59FDE2CC93840@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.248.222]
Content-Type: multipart/alternative; boundary="_000_A95B4818FD85874D8F16607F1AC7C628CE081Exmbrcdx09ciscocom_"
MIME-Version: 1.0
Cc: "radext@ietf.org" <radext@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>
Subject: Re: [radext] #153: Section 2.8 Access-Info
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 04:24:08 -0000

On Jun 10, 2013, at 10:48 AM, Bernard Aboba <bernard_aboba@hotmail.com<mailto:bernard_aboba@hotmail.com>> wrote:

Joe said:

"Access Status is advertised to the supplicant in EAPOL-Announcement Messages which are separate from authentication messages. I would it expect to be communicated in any message from the AAA server as it is possible you have some level of access before authentication completes. Access-Info needs to be included in an Access-Challenge message. "

[BA]  As I understand it, the use of the Access-Info attribute is to allow for the setting (and reporting) of the Access Status, which might be provided in response to a request (or not); protected by MKA (or not); could relate to a particular NID or for the port in general.   This raises the question of what the usage scenarios are, and whether the document covers them.

For example:

a. Is there a scenario where the Access-Info attribute could be used along with Service-Type="Call Check"?  For example, if a request comes in, could the RADIUS client generate a Call-Check message (e.g. with the MAC address of the supplicant in the Calling-Station-Id parameter) and then use the information in the Access-Info Attribute within the EAPoL-Announcement sent in reply?


[Joe] Yes, some systems provide limited access for specific MAC addresses.

b.  Is the Access-Info Attribute always used to communicate status for the port in general, or can it sometimes be used to indicate the status for a particular NID?  If the latter, how is the NID to which Access-Info relates communicated?  Does the inclusion of an Network-Id-Name Attribute in the Access-Accept indicate that the Access-Info Attribute is NID-specific?


[Joe] Good point.  I agree the behavior should be that if the Access-info attribute is included without a Network-ID-Name then it should pertain to the port in general.  If the access info attribute is included along with a network-ID-Name attribute then it pertains to the identified NID.


IEEE 802.1X-2010 Section 11.12.2 states:

The Access Information TLV provides the information specified in clause 10.1 (see Table 11-9) for a particular NID or for the port in general (if the TLV is encoded before any set TLV).

v2.23.0 | Report a Bug | By Email