IETF Logo Mail Archive

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

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Tue, 07 May 2013 00:26 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 2C73C21F8EED for <radext@ietfa.amsl.com>; Mon, 6 May 2013 17:26:57 -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=[BAYES_00=-2.599, 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 e4GuJYrb6e7E for <radext@ietfa.amsl.com>; Mon, 6 May 2013 17:26:52 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5292421F8EE8 for <radext@ietf.org>; Mon, 6 May 2013 17:26:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2043; q=dns/txt; s=iport; t=1367886412; x=1369096012; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=GqlseFitCZDk0zX2Wde9CNmuKdW5e2N6ufq5dpGM/Ko=; b=atjyWz6AWvbjiapHqQcTOvGMWKCCQ2JYKzHt4eLf9gdn2DeOx3tEf2GI FB+fjKiDykqOJiP9BKvSA3cIxqO94OeLPdiYXiqDPMiX++fC/4hTs/5LZ IllNsfP6CGpFBHJ5QthmHvceIb4c6Ks7tJlJxIgxlzTZqWMxnYJKCDg+L c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAMRJiFGtJXG8/2dsb2JhbABQgwc3rHSSFYEJFnSCIAEBBDo/EAIBCCIUEDIlAgQOBQiHcgMPDLI5jjOMW4EudQIxB4JyYQOVS4MJiHmBdAOFHoMNgic
X-IronPort-AV: E=Sophos;i="4.87,624,1363132800"; d="scan'208";a="206918771"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 07 May 2013 00:26:52 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r470Qp7b007273 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 May 2013 00:26:51 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.125]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Mon, 6 May 2013 19:26:51 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "<radext@ietf.org>" <radext@ietf.org>
Thread-Topic: [radext] #153: Section 2.8 Access-Info
Thread-Index: AQHOSRoJhjEhE2N9nEKPHCMplUm8jJj5NMCA
Date: Tue, 07 May 2013 00:26:51 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628BC5323@xmb-rcd-x09.cisco.com>
References: <066.e99973544c7878635851fd28a6cf5689@trac.tools.ietf.org>
In-Reply-To: <066.e99973544c7878635851fd28a6cf5689@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.248.202]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7CF3F9EA7899D0478355E619771B8D06@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<bernard_aboba@hotmail.com>" <bernard_aboba@hotmail.com>, "<draft-ietf-radext-ieee802ext@tools.ietf.org>" <draft-ietf-radext-ieee802ext@tools.ietf.org>
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, 07 May 2013 00:26:57 -0000

On May 4, 2013, at 3:52 PM, radext issue tracker <trac+radext@trac.tools.ietf.org>
 wrote:

> #153: Section 2.8 Access-Info
> 
> The Access-Info Attribute is utilized by implementations of
>       IEEE-802.1X [IEEE-802.1X] to specify the Access status information
>       field within an Access Information Type Length Value Tuple (TLV)
>       to be sent to the user within MACsec Key Agreement (MKA) or EAPoL-
>       Announcement frames.
> 
>       A single Access-Info Attribute is permitted within a RADIUS
>       Access-Accept, Access-Challenge, Access-Reject or Accounting-
>       Request packet.
> 
> [BA] The above paragraph seems to imply that the Access-Info Attribute
> could cause the Access status information to change during and after
> authentication.  It is unclear how supplicants would respond to such a
> change.  For example, the potential response to a change in MKA (which is
> authenticated) could be quite different from a change in an EAPoL-
> Announcement frame (which is not).  As a result, the desired behavior is
> unclear.
> 

[Joe]  The EAPoL-announcement may be protected with MACSEC if a connectivity association exists.   IEEE-802.1X-2010 specifies that the access status information in section 10.1.  Do you think it is within our scope to specify something in addition to this? 

> -- 
> -------------------------------------+-------------------------------------
> Reporter:                           |      Owner:  draft-ietf-radext-
>  bernard_aboba@hotmail.com          |  ieee802ext@tools.ietf.org
>     Type:  defect                   |     Status:  new
> Priority:  critical                 |  Milestone:  milestone1
> Component:  ieee802ext               |    Version:  1.0
> Severity:  In WG Last Call          |   Keywords:
> -------------------------------------+-------------------------------------
> 
> Ticket URL: <http://wiki.tools.ietf.org/wg/radext/trac/ticket/153>
> radext <http://tools.ietf.org/radext/>
>

v2.23.0 | Report a Bug | By Email