Re: [radext] #153: Section 2.8 Access-Info
"radext issue tracker" <trac+radext@trac.tools.ietf.org> Sun, 20 October 2013 23:22 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 2056D11E82C5 for <radext@ietfa.amsl.com>; Sun, 20 Oct 2013 16:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.024
X-Spam-Level:
X-Spam-Status: No, score=-102.024 tagged_above=-999 required=5 tests=[AWL=0.575, 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 4ZfDreHkuaGj for <radext@ietfa.amsl.com>; Sun, 20 Oct 2013 16:22:00 -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 5B7C311E80DE for <radext@ietf.org>; Sun, 20 Oct 2013 16:22:00 -0700 (PDT)
Received: from localhost ([127.0.0.1]:44229 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 1VY2Jk-0000X4-J4; Mon, 21 Oct 2013 01:21:52 +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: Sun, 20 Oct 2013 23:21:52 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/153#comment:6
Message-ID: <081.d5a0d836d7f002ae4119f480f96e27b8@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: <20131020232200.5B7C311E80DE@ietfa.amsl.com>
Resent-Date: Sun, 20 Oct 2013 16:22:00 -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: Sun, 20 Oct 2013 23:22:01 -0000
#153: Section 2.8 Access-Info Comment (by bernard_aboba@hotmail.com): As discussed at IETF 87, it may be necessary to transport multiple EAPoL- Announcement TLVs, not just the Access Information TLV. As a result a more generic solution is needed. The proposed resolution is to define an EAPoL-Announcement Attribute in Section 2.8. Here is the proposed text: 2.8. EAPoL-Announcement Description The EAPoL-Announcement Attribute contains EAPoL-Announcement Type Length Value Tuples (TLVs) defined within Table 11-8 of IEEE-802.1X [IEEE-802.1X]. Zero or more EAPoL-Announcement Attributes are permitted within an Access-Request, Access-Accept, Access-Challenge, Access-Reject, Accounting-Request, CoA-Request or Disconnect-Request packet. When included within an Access-Request packet, EAPoL- Announcement Attributes contain TLVs that the user sent in an EAPoL-Announcement. When included within an Access-Accept, Access-Challenge, Access-Reject, CoA-Request or Disconnect-Request packet, EAPoL-Announcement Attributes contain EAPoL- Announcement TLVs that the NAS is to send to the user in a unicast EAPoL-Announcement. When sent within an Accounting-Request packet, EAPoL-Announcment attributes contain EAPoL- Announcement TLVs that the NAS has most recently sent to the user in a unicast EAPoL-Announcement. A summary of the EAPoL-Announcement Attribute format is shown below. The fields are transmitted from left to right. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | String... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code TBD7 Length >=3 String The String field is one or more octets, containing EAPoL- Announcement TLVs in the format defined in Figure 11-8 of Section 11.12 of [IEEE-802.1X]: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TLV Type | TLV Length | TLV Information String... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ If multiple EAPoL-Announcement attributes are present in a packet, their String fields should be concatenated before being parsed for EAPoL-Announcement TLVs; this allows TLVs longer than 253 octets to be transported by RADIUS. TLV Type Any EAPoL-Announcement TLV Type MAY be included within an EAPoL- Announcement Attribute, including Organizationally Specific TLVs. TLV Length <=511 TLV Information String The TLV Information String field contains information specific to the TLV Type. -- -------------------------------------+------------------------------------- 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:6> radext <http://tools.ietf.org/radext/>
- [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info lionel.morand
- Re: [radext] #153: Section 2.8 Access-Info Bernard Aboba
- Re: [radext] #153: Section 2.8 Access-Info lionel.morand
- Re: [radext] #153: Section 2.8 Access-Info Bernard Aboba
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Bernard Aboba
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker
- Re: [radext] #153: Section 2.8 Access-Info Joseph Salowey (jsalowey)
- Re: [radext] #153: Section 2.8 Access-Info radext issue tracker