IETF Logo Mail Archive

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

"radext issue tracker" <trac+radext@trac.tools.ietf.org> Mon, 15 July 2013 03:56 UTC

Return-Path: <trac+radext@trac.tools.ietf.org>
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 82CC321F99D3 for <radext@ietfa.amsl.com>; Sun, 14 Jul 2013 20:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 5JSFIdtU7lkH for <radext@ietfa.amsl.com>; Sun, 14 Jul 2013 20:56:50 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 714C321F9D95 for <radext@ietf.org>; Sun, 14 Jul 2013 20:56:48 -0700 (PDT)
Received: from localhost ([127.0.0.1]:49807 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1UyZtu-0006oB-Kx; Mon, 15 Jul 2013 05:56:38 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: radext issue tracker <trac+radext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-radext-ieee802ext@tools.ietf.org, bernard_aboba@hotmail.com, jsalowey@cisco.com
X-Trac-Project: radext
Date: Mon, 15 Jul 2013 03:56:38 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/153#comment:5
Message-ID: <081.8e2856e09114f63c61fb32d7ade0ac46@trac.tools.ietf.org>
References: <066.e99973544c7878635851fd28a6cf5689@trac.tools.ietf.org>
X-Trac-Ticket-ID: 153
In-Reply-To: <066.e99973544c7878635851fd28a6cf5689@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-radext-ieee802ext@tools.ietf.org, bernard_aboba@hotmail.com, jsalowey@cisco.com, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: bernard_aboba@hotmail.com, j@w1.fi, jsalowey@cisco.com, mark@azu.ca, paul_congdon@hp.com
Resent-Message-Id: <20130715035648.714C321F9D95@ietfa.amsl.com>
Resent-Date: Sun, 14 Jul 2013 20:56:48 -0700
Resent-From: trac+radext@trac.tools.ietf.org
Cc: radext@ietf.org
Subject: Re: [radext] #153: Section 2.8 Access-Info
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: radext@ietf.org
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 03:56:50 -0000

#153: Section 2.8 Access-Info


Comment (by bernard_aboba@hotmail.com):

 EAPOL-Announcement messages can be generic or specific.  They can also
 refer to a particular NID-Name.  So there is a question of how it is
 indicated what kind of EAPOL-Announcement message the access status is to
 be encoded in.  One potential way of indicating the NID-Name to which the
 access-status applies is to assume that it applies to the NID-Name
 indicated in the Network-Id-Name attribute.  However, the NID-Name
 attribute is not permitted within an Access-Challenge.  Should this be
 changed? Proposed text is enclosed below:

     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 (Specific) frames.

       Zero or one Access-Info Attribute is permitted within an Access-
       Accept, Access-Challenge, Access-Reject, Accounting-Request, CoA-
       Request or Disconnect-Request packet.  When sent along with the
       Network-Id-Name Attribute, the Access-Info Attribute provides
       Access status information relating to that particular NID-Name.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-radext-
  bernard_aboba@hotmail.com          |  ieee802ext@tools.ietf.org
     Type:  defect                   |      Status:  reopened
 Priority:  critical                 |   Milestone:  milestone1
Component:  ieee802ext               |     Version:  1.0
 Severity:  In WG Last Call          |  Resolution:
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/153#comment:5>
radext <http://tools.ietf.org/radext/>

v2.23.0 | Report a Bug | By Email