From internet-drafts@ietf.org Mon May 7 05:01:28 2012 Return-Path: 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 1EE7121F849D; Mon, 7 May 2012 05:01:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.476 X-Spam-Level: X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.123, 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 x4LYTzZuwXhF; Mon, 7 May 2012 05:01:27 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE2C21F8464; Mon, 7 May 2012 05:01:27 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.02 Message-ID: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> Date: Mon, 07 May 2012 05:01:27 -0700 Cc: radext@ietf.org Subject: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2012 12:01:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the RADIUS EXTensions Working Group of th= e IETF. Title : RADIUS attributes for IPv6 Access Networks Author(s) : Benoit Lourdelet Wojciech Dec Behcet Sarikaya Glen Zorn David Miles Filename : draft-ietf-radext-ipv6-access-07.txt Pages : 14 Date : 2012-05-07 This document specifies additional IPv6 RADIUS attributes useful in residential broadband network deployments. The attributes, which are used for authorization and accounting, enable assignment of a host IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an IPv6 route announced via router advertisement; assignment of a named IPv6 delegated prefix pool; and assignment of a named IPv6 pool for host DHCPv6 addressing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-radext-ipv6-access-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-radext-ipv6-access-07.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-radext-ipv6-access/ From radext-bounces@ietf.org Mon May 7 05:01:32 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1934A21F85C5; Mon, 7 May 2012 05:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336392092; bh=5v7LzPOKwlcOlk2X4/L/7Q6SGmjVjLnbWQ9heMwRzW4=; h=MIME-Version:From:To:Message-ID:Date:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=CvlcDHqMDSHB9n7kbDOpGkKQxjdDpH2pOr1IcoHo/ApL/4cx/JYrFVJV4UjEse5sF FTiN8K2WUyx7p3HGb2V4E8gVXbtrUCJKshVhF/ABMoQsXFm5QVNqbOg8JFPPlk0Yd7 g6P8y2VLoDH0+TK+shGGIWYzYK7lbuDRG/kAo62s= 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 1EE7121F849D; Mon, 7 May 2012 05:01:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.476 X-Spam-Level: X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.123, 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 x4LYTzZuwXhF; Mon, 7 May 2012 05:01:27 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE2C21F8464; Mon, 7 May 2012 05:01:27 -0700 (PDT) MIME-Version: 1.0 From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.02 Message-ID: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> Date: Mon, 07 May 2012 05:01:27 -0700 Cc: radext@ietf.org Subject: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RADIUS EXTensions Working Group of the IETF. Title : RADIUS attributes for IPv6 Access Networks Author(s) : Benoit Lourdelet Wojciech Dec Behcet Sarikaya Glen Zorn David Miles Filename : draft-ietf-radext-ipv6-access-07.txt Pages : 14 Date : 2012-05-07 This document specifies additional IPv6 RADIUS attributes useful in residential broadband network deployments. The attributes, which are used for authorization and accounting, enable assignment of a host IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an IPv6 route announced via router advertisement; assignment of a named IPv6 delegated prefix pool; and assignment of a named IPv6 pool for host DHCPv6 addressing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-radext-ipv6-access-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-radext-ipv6-access-07.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-radext-ipv6-access/ _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From jouni.nospam@gmail.com Mon May 7 07:01:11 2012 Return-Path: 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 F0DC121F8493 for ; Mon, 7 May 2012 07:01:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 vQ44tuADs1wl for ; Mon, 7 May 2012 07:01:10 -0700 (PDT) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 31F9B21F8494 for ; Mon, 7 May 2012 07:01:10 -0700 (PDT) Received: by wibhq2 with SMTP id hq2so485128wib.13 for ; Mon, 07 May 2012 07:01:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=FiZXuqxvA+Z6SrC2xpLs40BYx6z2pceww+BHIUGojco=; b=mCTq8e+IF4pq4XN89hqyKGjmkmI+aK9pPHkpFKzX6zL+OiotUkn/IBiH60pfUGog+Q gjcWglcLzutS507oPUtcssz6XJkjOeyjjHcekpXCL9R8AVA07GynvI59yOVxDHRERHUi m9QZzyUn1nnFOgXlA7u1SPmmpKP5qUBNrj6hK2u7XwcaFzP7IDMfnKZqyisxRP5tbvAM oGU8TBDzWxfLiHjZpBkrkaaRDaB7dLLSmNWni0xOPD5sirfa6bvitdvnM5sL4OzGd+K/ Qcec38bjEfbHzNF7m02ePRoKYUuxE42MNNUoHV7LykGn4aGUJEyujfPByd7Qz/KJKyWk 5yvA== Received: by 10.180.92.130 with SMTP id cm2mr35609756wib.4.1336399269010; Mon, 07 May 2012 07:01:09 -0700 (PDT) Received: from [188.117.15.106] ([188.117.15.106]) by mx.google.com with ESMTPS id u9sm21949114wix.0.2012.05.07.07.01.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 May 2012 07:01:06 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> Date: Mon, 7 May 2012 17:01:01 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> To: radext@ietf.org X-Mailer: Apple Mail (2.1084) Cc: Wojciech Dec , Leaf yeh Subject: Re: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2012 14:01:11 -0000 Folks, The I-D has been revised to reflect the comments regarding the=20 attribute format and the example broadband network scenario. Everybody happy with the changes in Sections 2, 2.3 and 3.3 ? - Jouni & Mauricio On May 7, 2012, at 3:01 PM, internet-drafts@ietf.org wrote: >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. This draft is a work item of the RADIUS EXTensions Working = Group of the IETF. >=20 > Title : RADIUS attributes for IPv6 Access Networks > Author(s) : Benoit Lourdelet > Wojciech Dec > Behcet Sarikaya > Glen Zorn > David Miles > Filename : draft-ietf-radext-ipv6-access-07.txt > Pages : 14 > Date : 2012-05-07 >=20 > This document specifies additional IPv6 RADIUS attributes useful in > residential broadband network deployments. The attributes, which = are > used for authorization and accounting, enable assignment of a host > IPv6 address and IPv6 DNS server address via DHCPv6; assignment of = an > IPv6 route announced via router advertisement; assignment of a named > IPv6 delegated prefix pool; and assignment of a named IPv6 pool for > host DHCPv6 addressing. >=20 From radext-bounces@ietf.org Mon May 7 07:01:13 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E921C21F8494; Mon, 7 May 2012 07:01:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336399272; bh=i3i41OL9DB8g7SrUYnPgpSVI4XDh7BM2cPM34Biz8PU=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=TIG3iTFcwEWCw9Fts6gFfNv9F0EDSR2DWce5l//5fKJLnR1iJEduG/6noaHwKgBEx qfUaEzw8AFOuTuGnTJpPthLh58lw32kmi5ZcNoLNXrRR9LI86H88XZ4nE3X3DHyaz3 SqsqQs6q1wH5pxuVGN1jN7yEgVCPw3mxMdLjffaA= 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 F0DC121F8493 for ; Mon, 7 May 2012 07:01:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 vQ44tuADs1wl for ; Mon, 7 May 2012 07:01:10 -0700 (PDT) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 31F9B21F8494 for ; Mon, 7 May 2012 07:01:10 -0700 (PDT) Received: by wibhq2 with SMTP id hq2so485128wib.13 for ; Mon, 07 May 2012 07:01:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=FiZXuqxvA+Z6SrC2xpLs40BYx6z2pceww+BHIUGojco=; b=mCTq8e+IF4pq4XN89hqyKGjmkmI+aK9pPHkpFKzX6zL+OiotUkn/IBiH60pfUGog+Q gjcWglcLzutS507oPUtcssz6XJkjOeyjjHcekpXCL9R8AVA07GynvI59yOVxDHRERHUi m9QZzyUn1nnFOgXlA7u1SPmmpKP5qUBNrj6hK2u7XwcaFzP7IDMfnKZqyisxRP5tbvAM oGU8TBDzWxfLiHjZpBkrkaaRDaB7dLLSmNWni0xOPD5sirfa6bvitdvnM5sL4OzGd+K/ Qcec38bjEfbHzNF7m02ePRoKYUuxE42MNNUoHV7LykGn4aGUJEyujfPByd7Qz/KJKyWk 5yvA== Received: by 10.180.92.130 with SMTP id cm2mr35609756wib.4.1336399269010; Mon, 07 May 2012 07:01:09 -0700 (PDT) Received: from [188.117.15.106] ([188.117.15.106]) by mx.google.com with ESMTPS id u9sm21949114wix.0.2012.05.07.07.01.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 May 2012 07:01:06 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) From: jouni korhonen In-Reply-To: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> Date: Mon, 7 May 2012 17:01:01 +0300 Message-Id: References: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> To: radext@ietf.org X-Mailer: Apple Mail (2.1084) Cc: Wojciech Dec , Leaf yeh Subject: Re: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Folks, The I-D has been revised to reflect the comments regarding the attribute format and the example broadband network scenario. Everybody happy with the changes in Sections 2, 2.3 and 3.3 ? - Jouni & Mauricio On May 7, 2012, at 3:01 PM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RADIUS EXTensions Working Group of the IETF. > > Title : RADIUS attributes for IPv6 Access Networks > Author(s) : Benoit Lourdelet > Wojciech Dec > Behcet Sarikaya > Glen Zorn > David Miles > Filename : draft-ietf-radext-ipv6-access-07.txt > Pages : 14 > Date : 2012-05-07 > > This document specifies additional IPv6 RADIUS attributes useful in > residential broadband network deployments. The attributes, which are > used for authorization and accounting, enable assignment of a host > IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an > IPv6 route announced via router advertisement; assignment of a named > IPv6 delegated prefix pool; and assignment of a named IPv6 pool for > host DHCPv6 addressing. > _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From mauricio.sanchez@hp.com Mon May 7 14:46:07 2012 Return-Path: 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 5B4AC21F870B for ; Mon, 7 May 2012 14:46:07 -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 wEWaANH6VTxQ for ; Mon, 7 May 2012 14:46:06 -0700 (PDT) Received: from g4t0016.houston.hp.com (g4t0016.houston.hp.com [15.201.24.19]) by ietfa.amsl.com (Postfix) with ESMTP id AB42C21F8705 for ; Mon, 7 May 2012 14:46:03 -0700 (PDT) Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net [16.236.31.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g4t0016.houston.hp.com (Postfix) with ESMTPS id 3C35D1415E for ; Mon, 7 May 2012 21:46:03 +0000 (UTC) Received: from G5W0326.americas.hpqcorp.net (16.228.8.70) by G1W0400.americas.hpqcorp.net (16.236.31.10) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 7 May 2012 21:45:47 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0326.americas.hpqcorp.net ([16.228.8.70]) with mapi; Mon, 7 May 2012 22:45:46 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Mon, 7 May 2012 22:45:46 +0100 Thread-Topic: RADEXT WG Last Call: "RADIUS Attributes for IEEE 802 Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802 Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2012 21:46:07 -0000 This is an announcement of RADEXT WG last call on "RADIUS Attributes for IE= EE 802 Networks", prior to sending the document to the IESG for publication= as a proposed standard RFC. The document is available for inspection here: http://tools.ietf.org/id/draft-ietf-radext-ieee802ext The RADEXT WG last call will last until Monday May 21, 2012. If you have = comments on the document, please file using TRAC system. See below for sum= mary of instructions. Thanks, Mauricio and Jouni 1. To submit an issue in TRAC, you first need to login to the RADEXT = WG site on the tools server: http://tools.ietf.org/wg/radext/trac/login 2. If you don=92t already have a login ID, you can obtain one by navi= gating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can fil= e an issue by navigating to the ticket entry form:http://trac.tools.ietf.o= rg/wg/radext/trac/newticket 4. When opening an issue: a. The Type: field should be set to =93defect=94 for an issue with th= e current document text, or =93enhancement=94 for a proposed addition of fu= nctionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. Fo= r example, editorial issues are typically =93minor=94 or =93trivial=94. c. The Milestone: field should be set to milestone1 (useless, I know)= . d. The Component: field should be set to the document you are filing t= he issue on. e. The Version: field should be set to =931.0=94. f. The Severity: field should be set to based on the status of the d= ocument (e.g. =93In WG Last Call=94 for a document in WG last call) g. The Keywords: and CC: fields can be left blank unless inspiration= seizes you. h. The Assign To: field is generally filled in with the email address = of the editor. 5. Typically it won=92t be necessary to enclose a file with the ticke= t, but if you need to, select =93I have files to attach to this ticket=94. 6. If you want to preview your Issue, click on the =93Preview=94 butt= on. When you=92re ready to submit the issue, click on the =93Create Ticket= =94 button. 7. If you want to update an issue, go to the "View Tickets" page: htt= p://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket # you = want to update, and then modify the ticket fields as required From radext-bounces@ietf.org Mon May 7 14:46:09 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09A9021F870B; Mon, 7 May 2012 14:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336427169; bh=tU+LjANxweHlVGhxzD72YMGlpz77UouQTn9zX9UYfGY=; h=From:To:Date:Message-ID:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=gxRyUsu9dLU9DlWEjJYRA1f69F3KDzigxZTnAH2U7NE+fnkFCaLlY7W6v45ShAY4L fWClSScM/MNIKhueqOAB6FEEH5U7D6GMyzWJ/9FU0/xfEVGXSlh+Ii4ay5qpC9zmRZ Kp98KTOPCJoDoBVmvj5arGHaJ2X9Ur/zp+AM0Rp4= 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 5B4AC21F870B for ; Mon, 7 May 2012 14:46:07 -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 wEWaANH6VTxQ for ; Mon, 7 May 2012 14:46:06 -0700 (PDT) Received: from g4t0016.houston.hp.com (g4t0016.houston.hp.com [15.201.24.19]) by ietfa.amsl.com (Postfix) with ESMTP id AB42C21F8705 for ; Mon, 7 May 2012 14:46:03 -0700 (PDT) Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net [16.236.31.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g4t0016.houston.hp.com (Postfix) with ESMTPS id 3C35D1415E for ; Mon, 7 May 2012 21:46:03 +0000 (UTC) Received: from G5W0326.americas.hpqcorp.net (16.228.8.70) by G1W0400.americas.hpqcorp.net (16.236.31.10) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 7 May 2012 21:45:47 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0326.americas.hpqcorp.net ([16.228.8.70]) with mapi; Mon, 7 May 2012 22:45:46 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Mon, 7 May 2012 22:45:46 +0100 Thread-Topic: RADEXT WG Last Call: "RADIUS Attributes for IEEE 802 Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US MIME-Version: 1.0 Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802 Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org This is an announcement of RADEXT WG last call on "RADIUS Attributes for IE= EE 802 Networks", prior to sending the document to the IESG for publication= as a proposed standard RFC. The document is available for inspection here: http://tools.ietf.org/id/draft-ietf-radext-ieee802ext The RADEXT WG last call will last until Monday May 21, 2012. If you have = comments on the document, please file using TRAC system. See below for sum= mary of instructions. Thanks, Mauricio and Jouni 1. To submit an issue in TRAC, you first need to login to the RADEXT = WG site on the tools server: http://tools.ietf.org/wg/radext/trac/login 2. If you don=92t already have a login ID, you can obtain one by navi= gating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can fil= e an issue by navigating to the ticket entry form:http://trac.tools.ietf.o= rg/wg/radext/trac/newticket 4. When opening an issue: a. The Type: field should be set to =93defect=94 for an issue with th= e current document text, or =93enhancement=94 for a proposed addition of fu= nctionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. Fo= r example, editorial issues are typically =93minor=94 or =93trivial=94. c. The Milestone: field should be set to milestone1 (useless, I know). d. The Component: field should be set to the document you are filing t= he issue on. e. The Version: field should be set to =931.0=94. f. The Severity: field should be set to based on the status of the d= ocument (e.g. =93In WG Last Call=94 for a document in WG last call) g. The Keywords: and CC: fields can be left blank unless inspiration= seizes you. h. The Assign To: field is generally filled in with the email address = of the editor. 5. Typically it won=92t be necessary to enclose a file with the ticke= t, but if you need to, select =93I have files to attach to this ticket=94. 6. If you want to preview your Issue, click on the =93Preview=94 butt= on. When you=92re ready to submit the issue, click on the =93Create Ticket= =94 button. 7. If you want to update an issue, go to the "View Tickets" page: htt= p://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket # you = want to update, and then modify the ticket fields as required _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From mauricio.sanchez@hp.com Mon May 7 14:47:34 2012 Return-Path: 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 1002111E8073 for ; Mon, 7 May 2012 14:47:34 -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 qTsKzzFMgxbR for ; Mon, 7 May 2012 14:47:33 -0700 (PDT) Received: from g5t0008.atlanta.hp.com (g5t0008.atlanta.hp.com [15.192.0.45]) by ietfa.amsl.com (Postfix) with ESMTP id 73FCA11E8072 for ; Mon, 7 May 2012 14:47:33 -0700 (PDT) Received: from G6W1798G.americas.hpqcorp.net (g6w1798g.atlanta.hp.com [16.230.17.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g5t0008.atlanta.hp.com (Postfix) with ESMTPS id 2B2462425A for ; Mon, 7 May 2012 21:47:32 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G6W1798G.americas.hpqcorp.net (16.230.17.175) with Microsoft SMTP Server (TLS) id 14.2.283.4; Mon, 7 May 2012 21:45:45 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Mon, 7 May 2012 22:45:44 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Mon, 7 May 2012 22:45:44 +0100 Thread-Topic: RADEXT @ IETF83: Meeting notes Thread-Index: Ac0smsE6Jkr6dekdT8mFR7N1NhuzIw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [radext] RADEXT @ IETF83: Meeting notes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2012 21:47:34 -0000 Meeting notes up have been uploaded for our meeting at IETF 83. Thanks to = Stefan for acting as scribe. Any corrections/modifications welcome prior t= o May 14. http://www.ietf.org/proceedings/83/minutes/minutes-83-radext.txt - Mauricio and Jouni From radext-bounces@ietf.org Mon May 7 14:47:35 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0967811E8072; Mon, 7 May 2012 14:47:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336427255; bh=1QS5A0lPI0sUYz0/YwzAWxgS/8Mg1dpRXb48tgOuK6k=; h=From:To:Date:Message-ID:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=oJvbJQS84YYWnP13nsKdNbo/mzFaH3FQxxeJDR+j9FF/WfDxatDX3FDK+tbSJ4Sru U0KK4qz59uljvoKupNsw70I7PvUzkQDhLnbtEJ4U3s8DlOSJWy060eAUOrc4nnfF4V XcK1aB8mKl3sOztLHBZcMt7UA76rG8CZy5CHEkxc= 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 1002111E8073 for ; Mon, 7 May 2012 14:47:34 -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 qTsKzzFMgxbR for ; Mon, 7 May 2012 14:47:33 -0700 (PDT) Received: from g5t0008.atlanta.hp.com (g5t0008.atlanta.hp.com [15.192.0.45]) by ietfa.amsl.com (Postfix) with ESMTP id 73FCA11E8072 for ; Mon, 7 May 2012 14:47:33 -0700 (PDT) Received: from G6W1798G.americas.hpqcorp.net (g6w1798g.atlanta.hp.com [16.230.17.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g5t0008.atlanta.hp.com (Postfix) with ESMTPS id 2B2462425A for ; Mon, 7 May 2012 21:47:32 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G6W1798G.americas.hpqcorp.net (16.230.17.175) with Microsoft SMTP Server (TLS) id 14.2.283.4; Mon, 7 May 2012 21:45:45 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Mon, 7 May 2012 22:45:44 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Mon, 7 May 2012 22:45:44 +0100 Thread-Topic: RADEXT @ IETF83: Meeting notes Thread-Index: Ac0smsE6Jkr6dekdT8mFR7N1NhuzIw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US MIME-Version: 1.0 Subject: [radext] RADEXT @ IETF83: Meeting notes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Meeting notes up have been uploaded for our meeting at IETF 83. Thanks to Stefan for acting as scribe. Any corrections/modifications welcome prior to May 14. http://www.ietf.org/proceedings/83/minutes/minutes-83-radext.txt - Mauricio and Jouni _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From trac+radext@trac.tools.ietf.org Mon May 7 15:25:07 2012 Return-Path: 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 826CA21F86C1 for ; Mon, 7 May 2012 15:25:07 -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=[AWL=0.000, 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 MnO+AZCvNYUT for ; Mon, 7 May 2012 15:25:07 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 028B521F86BE for ; Mon, 7 May 2012 15:25:06 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRWMb-0001kw-5k; Mon, 07 May 2012 18:25:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: mauricio.sanchez@hp.com X-Trac-Project: radext Date: Mon, 07 May 2012 22:25:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/108 Message-ID: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-Trac-Ticket-ID: 108 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: mauricio.sanchez@hp.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #108: Incorrect author email address X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2012 22:25:07 -0000 #108: Incorrect author email address Email of one of the listed authors, Jouni Malinen, no longer operational. Email to listed address bounces with 'does not exist' error. Request the author information for all be validated. -- --------------------------------+------------------------ Reporter: mauricio.sanchez@… | Owner: Type: defect | Status: new Priority: trivial | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: --------------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Mon May 7 15:25:09 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5385121F86C4; Mon, 7 May 2012 15:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336429509; bh=CLARu3ABrbFt9aitwQq42X9mryX5ngSg6mYYDI8CEJ0=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=jhyahqsoMkTNf8uLuCyUCsY43P1w93yVR8bXJVEqhQ4UsbyXLdijdm+uNpTy6MYkD 2Av00Hckr7ulwNVpkng0aDOyOkWLuSis7xtNIKD1A/bbIY6HGHEIN4lw/IK5piovvJ WLQ+a3it+lAMG4sCleA4LQLyHMZ9Tht9dLzdMFlk= 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 826CA21F86C1 for ; Mon, 7 May 2012 15:25:07 -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=[AWL=0.000, 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 MnO+AZCvNYUT for ; Mon, 7 May 2012 15:25:07 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 028B521F86BE for ; Mon, 7 May 2012 15:25:06 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRWMb-0001kw-5k; Mon, 07 May 2012 18:25:05 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: mauricio.sanchez@hp.com X-Trac-Project: radext Date: Mon, 07 May 2012 22:25:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/108 Message-ID: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-Trac-Ticket-ID: 108 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: mauricio.sanchez@hp.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #108: Incorrect author email address X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEwODogSW5jb3JyZWN0IGF1dGhvciBlbWFpbCBhZGRyZXNzCgogRW1haWwgb2Ygb25lIG9mIHRo ZSBsaXN0ZWQgYXV0aG9ycywgSm91bmkgTWFsaW5lbiwgbm8gbG9uZ2VyIG9wZXJhdGlvbmFsLgog RW1haWwgdG8gbGlzdGVkIGFkZHJlc3MgYm91bmNlcyB3aXRoICdkb2VzIG5vdCBleGlzdCcgZXJy b3IuICBSZXF1ZXN0IHRoZQogYXV0aG9yIGluZm9ybWF0aW9uIGZvciBhbGwgYmUgdmFsaWRhdGVk LgoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLQogUmVwb3J0ZXI6ICBtYXVyaWNpby5zYW5jaGV6QOKApiAgfCAgICAgIE93bmVyOgog ICAgIFR5cGU6ICBkZWZlY3QgICAgICAgICAgICAgIHwgICAgIFN0YXR1czogIG5ldwogUHJpb3Jp dHk6ICB0cml2aWFsICAgICAgICAgICAgIHwgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEKQ29tcG9u ZW50OiAgSUVFRTgwMi1BdHRycyAgICAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAg SW4gV0cgTGFzdCBDYWxsICAgICB8ICAgS2V5d29yZHM6Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90 cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMDg+CnJhZGV4dCA8aHR0 cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpo dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From radext-bounces@ietf.org Tue May 8 01:35:23 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A4021F853E; Tue, 8 May 2012 01:35:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336466123; bh=1rwdBGJlcRRK0Bcr/4KGOY01VoQ4HdeaaoOQLAPt0Y0=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To:Cc: Subject:Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:Content-Type:Content-Transfer-Encoding: Sender; b=W+MHoH2IUL9F556QlLhGzlh6kJioGCMc2TFcR1o4XGY5s/rkpZopoNKP4Id1/KP+L XRKwir9KXEjubauN7cYSzosPQZA11irjhCH58JHxqZ7dY+kZyjKBekbfk/VIZSgLOL JwSxvDCAKjgghp69r0Ku18AdG6VZqatldGs2fk34= 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 46E0321F8543 for ; Tue, 8 May 2012 01:35:23 -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 yQ36pSp7POI0 for ; Tue, 8 May 2012 01:35:22 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id C749221F853E for ; Tue, 8 May 2012 01:35:21 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRft9-0003y1-FK; Tue, 08 May 2012 04:35:20 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: j@w1.fi X-Trac-Project: radext Date: Tue, 08 May 2012 08:35:19 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/108#comment:1 Message-ID: <079.5dd02e114794e4cd1d61ea0ac35f54ba@trac.tools.ietf.org> References: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-Trac-Ticket-ID: 108 In-Reply-To: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: j@w1.fi, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #108: Incorrect author email address X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEwODogSW5jb3JyZWN0IGF1dGhvciBlbWFpbCBhZGRyZXNzCgoKQ29tbWVudCAoYnkgakDigKYp OgoKIEl0J3Mgbm90IG9ubHkgdGhlIGVtYWlsIGFkZHJlc3MgYnV0IGFsbCB0aGUgY29udGFjdCBp bmZvIGZvciBtZSBoYXMgbm90CiByZWFsbHkgYmVlbiB2YWxpZCBmb3IgeWVhcnMgKHRoZSBpbml0 aWFsIHBhcnRzIGZvciB0aGlzIGRyYWZ0IHdlcmUgc3RhcnRlZAogcXVpdGUgc29tZSB0aW1lIGFn by4uIDstKS4KCiBJbiB0aGUgIkF1dGhvcnMnIEFkZHJlc3NlcyIgc2VjdGlvbiwgaXQgd291bGQg cHJvYmFibHkgYmUgZWFzaWVzdCB0bwogaW5jbHVkZSBqdXN0IG15IGN1cnJlbnQgZW1haWwgYWRk cmVzczoKCiBKb3VuaSBNYWxpbmVuCiBFTWFpbDogakB3MS5maQoKIFRoZSBjb21wYW55IGFmZmls aWF0aW9uIGluIHRoZSBiZWdpbm5pbmcgb2YgdGhlIGRvY3VtZW50IHdhcyBjb3JyZWN0IGF0CiB0 aGUgdGltZSB0aGUgaW5pdGlhbCBkcmFmdCB3YXMgcHJlcGFyZWQsIGJ1dCBpdCBpcyBub3QgdmFs aWQgYW55bW9yZS4gSSdtCiBub3Qgc3VyZSB3aGV0aGVyIElFVEYgaGFzIGEgcG9saWN5IG9uIGhv dyB0byBoYW5kbGUgdGhpcyB0eXBlIG9mIGNhc2VzLAogYnV0IGVpdGhlciB0aGUgY29tcGFueSBu YW1lIGNvdWxkIGJlIHJlbW92ZWQgb3IgbGVmdCBhcy1pcyB3aXRoIGp1c3QgdGhlCiBhdXRob3Jz JyBhZGRyZXNzZXMgc2VjdGlvbiB1cGRhdGVkLgoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KIFJlcG9ydGVyOiAgbWF1cmljaW8u c2FuY2hlekDigKYgIHwgICAgICAgT3duZXI6CiAgICAgVHlwZTogIGRlZmVjdCAgICAgICAgICAg ICAgfCAgICAgIFN0YXR1czogIG5ldwogUHJpb3JpdHk6ICB0cml2aWFsICAgICAgICAgICAgIHwg ICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCkNvbXBvbmVudDogIElFRUU4MDItQXR0cnMgICAgICAg fCAgICAgVmVyc2lvbjogIDEuMAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0IENhbGwgICAgIHwgIFJl c29sdXRpb246CiBLZXl3b3JkczogICAgICAgICAgICAgICAgICAgICAgfAotLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgpUaWNrZXQgVVJM OiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFkZXh0L3RyYWMvdGlja2V0LzEwOCNj b21tZW50OjE+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBs aXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Tue May 8 01:35:23 2012 Return-Path: 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 46E0321F8543 for ; Tue, 8 May 2012 01:35:23 -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 yQ36pSp7POI0 for ; Tue, 8 May 2012 01:35:22 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id C749221F853E for ; Tue, 8 May 2012 01:35:21 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRft9-0003y1-FK; Tue, 08 May 2012 04:35:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: j@w1.fi X-Trac-Project: radext Date: Tue, 08 May 2012 08:35:19 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/108#comment:1 Message-ID: <079.5dd02e114794e4cd1d61ea0ac35f54ba@trac.tools.ietf.org> References: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-Trac-Ticket-ID: 108 In-Reply-To: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: j@w1.fi, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #108: Incorrect author email address X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 08:35:23 -0000 #108: Incorrect author email address Comment (by j@…): It's not only the email address but all the contact info for me has not really been valid for years (the initial parts for this draft were started quite some time ago.. ;-). In the "Authors' Addresses" section, it would probably be easiest to include just my current email address: Jouni Malinen EMail: j@w1.fi The company affiliation in the beginning of the document was correct at the time the initial draft was prepared, but it is not valid anymore. I'm not sure whether IETF has a policy on how to handle this type of cases, but either the company name could be removed or left as-is with just the authors' addresses section updated. -- --------------------------------+------------------------- Reporter: mauricio.sanchez@… | Owner: Type: defect | Status: new Priority: trivial | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Resolution: Keywords: | --------------------------------+------------------------- Ticket URL: radext From radext-bounces@ietf.org Tue May 8 01:47:18 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2988C21F85C4; Tue, 8 May 2012 01:47:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336466838; bh=WsujtAx3x1BbAM6BuO68A2a1L/zCWP0Ur1HdislAYoQ=; h=MIME-Version:Date:Message-ID:In-Reply-To:References:From:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=BVeUMS5JBk+AQzyCbJOIvjh/Gokh1k+x+mFlMysDRpDtcw4bTG8q1l0JTWyDzosqf 9HuGU11wSGe0UP1Y8Z62+UP1WsAb1RHC6tBCA2t59V8rTypvSsJUR8r6QWnHdG1wK8 WdS9LAHdrUoEH9C0w7+Rf8tA50JgcBVax5g+yk24= 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 B58F821F85C4 for ; Tue, 8 May 2012 01:47:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.834 X-Spam-Level: X-Spam-Status: No, score=-102.834 tagged_above=-999 required=5 tests=[AWL=-0.235, 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 D3K3s7laGb-r for ; Tue, 8 May 2012 01:47:17 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 13B8B21F85C2 for ; Tue, 8 May 2012 01:47:17 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAFABDcqE/GmAcF/2dsb2JhbABEsyKBB4IMAQEBAQMBAQEPHgoxAxcEAgEIDQQEAQELBgUBAQULAQYBJh8JCAEBBAESCBqHbAudTJ05iwAlgjIIAYJGYwSXD4UHiiqCa4FWBg X-IronPort-AV: E=Sophos;i="4.75,549,1330923600"; d="scan'208";a="8063485" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 08 May 2012 04:47:14 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 May 2012 04:44:00 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 8 May 2012 10:47:13 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zw References: From: "Romascanu, Dan (Dan)" To: "Sanchez, Mauricio (HP Networking)" , Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I believe having experts from the IEEE 802.1 WG review and comment on this document would be very useful. Regards, Dan > -----Original Message----- > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > Behalf Of Sanchez, Mauricio (HP Networking) > Sent: Tuesday, May 08, 2012 12:46 AM > To: radext@ietf.org > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > 802Networks" > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > for IEEE 802 Networks", prior to sending the document to the IESG for > publication as a proposed standard RFC. > > The document is available for inspection here: > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > The RADEXT WG last call will last until Monday May 21, 2012. If you > have comments on the document, please file using TRAC system. See > below for summary of instructions. > > Thanks, > Mauricio and Jouni > > 1. To submit an issue in TRAC, you first need to login to the > RADEXT WG site on the tools server: > http://tools.ietf.org/wg/radext/trac/login > 2. If you don't already have a login ID, you can obtain one by > navigating to this site: http://trac.tools.ietf.org/newlogin > 3. Once you have obtained an account, and have logged in, you can > file an issue by navigating to the ticket entry > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > 4. When opening an issue: > a. The Type: field should be set to "defect" for an issue with > the current document text, or "enhancement" for a proposed addition of > functionality (such as an additional requirement). > b. The Priority: field is set based on the severity of the Issue. > For example, editorial issues are typically "minor" or "trivial". > c. The Milestone: field should be set to milestone1 (useless, I > know). > d. The Component: field should be set to the document you are > filing the issue on. > e. The Version: field should be set to "1.0". > f. The Severity: field should be set to based on the status of > the document (e.g. "In WG Last Call" for a document in WG last call) > g. The Keywords: and CC: fields can be left blank unless > inspiration seizes you. > h. The Assign To: field is generally filled in with the email > address of the editor. > 5. Typically it won't be necessary to enclose a file with the > ticket, but if you need to, select "I have files to attach to this > ticket". > 6. If you want to preview your Issue, click on the "Preview" > button. When you're ready to submit the issue, click on the "Create > Ticket" button. > 7. If you want to update an issue, go to the "View Tickets" page: > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket > # you want to update, and then modify the ticket fields as required > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From dromasca@avaya.com Tue May 8 01:47:17 2012 Return-Path: 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 B58F821F85C4 for ; Tue, 8 May 2012 01:47:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.834 X-Spam-Level: X-Spam-Status: No, score=-102.834 tagged_above=-999 required=5 tests=[AWL=-0.235, 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 D3K3s7laGb-r for ; Tue, 8 May 2012 01:47:17 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 13B8B21F85C2 for ; Tue, 8 May 2012 01:47:17 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAFABDcqE/GmAcF/2dsb2JhbABEsyKBB4IMAQEBAQMBAQEPHgoxAxcEAgEIDQQEAQELBgUBAQULAQYBJh8JCAEBBAESCBqHbAudTJ05iwAlgjIIAYJGYwSXD4UHiiqCa4FWBg X-IronPort-AV: E=Sophos;i="4.75,549,1330923600"; d="scan'208";a="8063485" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 08 May 2012 04:47:14 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 May 2012 04:44:00 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 8 May 2012 10:47:13 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zw References: From: "Romascanu, Dan (Dan)" To: "Sanchez, Mauricio (HP Networking)" , Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 08:47:17 -0000 FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I believe having experts from the IEEE 802.1 WG review and comment on this document would be very useful.=20 Regards, Dan > -----Original Message----- > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > Behalf Of Sanchez, Mauricio (HP Networking) > Sent: Tuesday, May 08, 2012 12:46 AM > To: radext@ietf.org > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > 802Networks" >=20 > This is an announcement of RADEXT WG last call on "RADIUS Attributes > for IEEE 802 Networks", prior to sending the document to the IESG for > publication as a proposed standard RFC. >=20 > The document is available for inspection here: > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext >=20 > The RADEXT WG last call will last until Monday May 21, 2012. If you > have comments on the document, please file using TRAC system. See > below for summary of instructions. >=20 > Thanks, > Mauricio and Jouni >=20 > 1. To submit an issue in TRAC, you first need to login to the > RADEXT WG site on the tools server: > http://tools.ietf.org/wg/radext/trac/login > 2. If you don't already have a login ID, you can obtain one by > navigating to this site: http://trac.tools.ietf.org/newlogin > 3. Once you have obtained an account, and have logged in, you can > file an issue by navigating to the ticket entry > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > 4. When opening an issue: > a. The Type: field should be set to "defect" for an issue with > the current document text, or "enhancement" for a proposed addition of > functionality (such as an additional requirement). > b. The Priority: field is set based on the severity of the Issue. > For example, editorial issues are typically "minor" or "trivial". > c. The Milestone: field should be set to milestone1 (useless, I > know). > d. The Component: field should be set to the document you are > filing the issue on. > e. The Version: field should be set to "1.0". > f. The Severity: field should be set to based on the status of > the document (e.g. "In WG Last Call" for a document in WG last call) > g. The Keywords: and CC: fields can be left blank unless > inspiration seizes you. > h. The Assign To: field is generally filled in with the email > address of the editor. > 5. Typically it won't be necessary to enclose a file with the > ticket, but if you need to, select "I have files to attach to this > ticket". > 6. If you want to preview your Issue, click on the "Preview" > button. When you're ready to submit the issue, click on the "Create > Ticket" button. > 7. If you want to update an issue, go to the "View Tickets" page: > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket > # you want to update, and then modify the ticket fields as required > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From leaf.y.yeh@huawei.com Tue May 8 04:08:28 2012 Return-Path: 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 6D33121F8440 for ; Tue, 8 May 2012 04:08:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.564 X-Spam-Level: X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599] 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 mRxIhFcphQHb for ; Tue, 8 May 2012 04:08:27 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 99AE821F8446 for ; Tue, 8 May 2012 04:08:27 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFP76703; Tue, 08 May 2012 07:08:27 -0400 (EDT) Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 8 May 2012 04:05:45 -0700 Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 8 May 2012 04:05:47 -0700 Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.168]) by szxeml424-hub.china.huawei.com ([10.82.67.163]) with mapi id 14.01.0323.003; Tue, 8 May 2012 19:05:40 +0800 From: Leaf yeh To: "Sanchez, Mauricio (HP Networking)" , "radext@ietf.org" Thread-Topic: RADEXT @ IETF83: Meeting notes - RADIUS Accounting Extensions of Traffic Statistics Thread-Index: AQHNLQqBy7w8ZDU+KkimIWn+KZE65g== Date: Tue, 8 May 2012 11:05:40 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.70.39.132] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: Re: [radext] RADEXT @ IETF83: Meeting notes - RADIUS Accounting Extensions of Traffic Statistics X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 11:08:28 -0000 aHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy84My9taW51dGVzL21pbnV0ZXMtODMtcmFk ZXh0LnR4dA0KDQo8cXVvdGU+IDMuIFJBRElVUyBBY2NvdW50aW5nIEV4dGVuc2lvbnMgb2YgVHJh ZmZpYyBTdGF0aXN0aWNzLCBMZWFmIFllaCANCi1odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k cmFmdC15ZWgtcmFkZXh0LWV4dC10cmFmZmljLXN0YXRpc3RpY3MNCi0iRGVzaWduLTMiIChpZGVu dGljYWwgdG8gYXBwcm9hY2ggaW4gZHJhZnQtd2ludGVyLXJhZGV4dC1mYW5jeWFjY291bnRpbmcp IHVzZXMgVExWIGRhdGEgdHlwZS4NCi1EaXNjdXNzaW9ucyByZXZlYWxlZCB0aGUgZnVuZGFtZW50 YWwgcXVlc3Rpb24gZm9yIGdvLWFoZWFkOiBzaG91bGQgd2UgZGVmaW5lIGFjY291bnRpbmcgYXR0 cmlidXRlIGp1c3QgZm9yIElQdjYgYWNjb3VudGluZywgb3IgYSBnZW5lcmljYWxseSByZS11c2Fi bGUgYXBwcm9hY2ggdG8gYWxsb3cgYWNjb3VudGluZyBhZnRlciBhcmJpdHJhcnkgY3JpdGVyaWE/ DQotUXVlc3Rpb24gd2lsbCBiZSBkaXNjdXNzZWQgaW4gdGhlIGNvdXJzZSBvZiByZS1jaGFydGVy aW5nLiA8L3F1b3RlPg0KDQoNCjEuIFllcywgZHJhZnQteWVoLXJhZGV4dC1leHQtdHJhZmZpYy1z dGF0aXN0aWNzLTAyIGFkb3B0ZWQgVExWIGFzIHRoZSBkYXRhIHR5cGUgZm9yIHRoZSBuZXcgKGNv bnRhaW5lcikgYXR0cmlidXRlLCBBY2N0LVRyYWZmaWMtU3RhdGlzdGljcywgcGVyIHRoZSBuZXcg YmFzaWMgZGF0YSB0eXBlIG9mIFRMViBkZWZpbmVkIGluIGRyYWZ0LWlldGYtcmFkZXh0LXJhZGl1 cy1leHRlbnNpb25zIGFuZCB0aGUgZXhwZXJ0IGluc2lzdGVuY2Ugb2YgU3RhZmVuICYgQWxhbi4N Cg0KMi4gSSBzdGlsbCBkb24ndCB0aGluayB0aGF0IHRvICdkZWZpbmUgYWNjb3VudGluZyBhdHRy aWJ1dGUganVzdCBmb3IgSVB2NiBhY2NvdW50aW5nJyBjYW4gbWVldCB0aGUgd2hvbGUgcmVxdWly ZW1lbnQgb2YgdGhlIHJlcG9ydGluZyBvbiB0aGUgSVB2NC9JUHY2IHNlcGFyYXRlZCBhbmQgY29t YmluZWQgdHJhZmZpYyBzdGF0aXN0aWNzLCB3aGljaCB3YXMgcHJlc2VudGVkICYgcmV2aWV3ZWQg aW4gdGhlIFJBREVYVCBzZXNzaW9uIG9mIElFVEY4MiwgVGFpcGVpLiBQbHMuIHJlZmVyIHRvIGh0 dHA6Ly93d3cuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvODIvc2xpZGVzL3JhZGV4dC0yLnBwdHggYW5k IFNlY3Rpb24gOS40IG9mIEJCRiBUUi0xODcuIA0KDQpJZiB3ZSBvbmx5IGRlZmluZSBuZXcgYXR0 cmlidXRlIGp1c3QgZm9yIElQdjYsIHdlIG1pZ2h0IHVzZSB0aGlzIG5ldyBhdHRyaWJ1dGUgdG8g cmVwb3J0IHRoZSBzZXBhcmF0ZWQgSVB2NiB0cmFmZmljIHN0YXRpc3RpY3MsIGFuZCBtaWdodCB1 c2UgDQoNCjQyIEFjY3QtSW5wdXQtT2N0ZXRzIFtSRkMyODY2XQ0KNDMgQWNjdC1PdXRwdXQtT2N0 ZXRzIFtSRkMyODY2XQ0KNDcgQWNjdC1JbnB1dC1QYWNrZXRzIFtSRkMyODY2XQ0KNDggQWNjdC1P dXRwdXQtUGFja2V0cyBbUkZDMjg2Nl0NCjUyIEFjY3QtSW5wdXQtR2lnYXdvcmRzIFtSRkMyODY5 XQ0KNTMgQWNjdC1PdXRwdXQtR2lnYXdvcmRzIFtSRkMyODY5XQ0KDQp0byByZXBvcnQgdGhlIHNl cGFyYXRlZCBJUHY0IHRyYWZmaWMgc3RhdGlzdGljcywgYnV0IHRoZW4gdG8gcmVwb3J0IHRoZSBJ UHY0L0lQdjYgY29tYmluZWQgdHJhZmZpYyBzdGF0aXN0aWNzPyBPciB3ZSBkbyB0aGUgY2FsY3Vs YXRpb24gYXQgdGhlIFJBRElVUyBzZXJ2ZXIgc2lkZS4gSSBzdXBwb3NlZCB0aGUgYWJvdmUgNiBh dHRyaWJ1dGVzIG1pZ2h0IGJlIHJlY29tbWVuZGVkIHRvIHJlcG9ydCB0aGUgSVB2NC9JUHY2IGNv bWJpbmVkIHRyYWZmaWMgc3RhdGlzdGljcyBpbiBTZWN0aW9uIDkuNCBvZiBCQkYgVFItMTg3Lg0K DQozLiBBcyBJIG1lbnRpb25lZCBpbiBteSBwcmVzZW50YXRpb24gKGh0dHA6Ly93d3cuaWV0Zi5v cmcvcHJvY2VlZGluZ3MvODMvc2xpZGVzL3NsaWRlcy04My1yYWRleHQtMS5wZGYgKSBhdCB0aGUg UkFERVhUIHNlc3Npb24gb2YgSUVURjgzLCBQYXJpcywgdG8gYWRvcHQgbmVzdGluZy1UTFYgYXMg dGhlIGRhdGEgdHlwZSBmb3IgdGhlIG5ldyBkZWZpbmVkIGF0dHJpYnV0ZSwgQWNjdC1UcmFmZmlj LVN0YXRpc3RpY3MsIGluIHRoZSBleHRlbmRlZCB0eXBlIHNwYWNlIG1pZ2h0IGdhaW4gdGhlIGV4 dGVuc2liaWxpdHkgZm9yIHRoZSBmdXR1cmUgcG9zc2libGUgcmVmaW5lZCB1c2FnZS4gDQoNCkZv ciBleGFtcGxlLCBpZiB3ZSBpbnRlbmQgdG8gcmVwb3J0IHRoZSB0cmFmZmljIHN0YXRpc3RpY3Mg YXNzb2NpYXRlZCB3aXRoIERTQ1AsIERpZmZlcmVudGlhdGVkIFNlcnZpY2VzIENvZGUgUG9pbnQs IHdlIG1pZ2h0IGluY2x1ZGUgYSBuZXcgc3ViLWF0dHJpYnV0ZSBpbiB0aGUgR3JvdXAgdG8gcmVm aW5lIHRoZSB0cmFmZmljLXR5cGUgKG9yIHdlIGNhbGwgaXQgc3RhY2stdHlwZSkuIEl0IHNvdW5k cyBhIG5ldyBmaWVsZCBpbiB0aGUgY29tcGxleCBkYXRhIHN0cnVjdHVyZSwgd2hpY2ggYXQgbGFz dCB0dXJucyB0byBiZSBhIG5ldyBhdHRyaWJ1dGUgaW4gdGhlIGdyb3VwIG9mIG5lc3RpbmctVExW LiANCg0KVGhlIHF1ZXN0aW9uIHRvIHRoZSBXRyBtaWdodCBiZSB3aGV0aGVyIGl0IGlzIG5lY2Vz c2FyeSB0byBwcmVzZW50IERTQ1AgaW4gdGhlIHRyYWZmaWMgc3RhdGlzdGljcy4gSSBndWVzcyBp dCBpcyBub3QgaGFybWZ1bCBpZiB3ZSBkZWZpbmVkIERTQ1AgYXR0cmlidXRlIG5vdywgYmVjYXVz ZSB0aGUgb3BlcmF0b3Igc3RpbGwgY2FuIGNob29zZSBub3QgdG8gdXNlIGl0IG5vdy4gTG9vayBm b3J3YXJkIHRvIHlvdXIgZnVydGhlciBkaXNjdXNzaW9uIGFuZCBjb21tZW50cyBvbiBpdC4NCg0K SSd2ZSBpbnRyb2R1Y2VkIHRoaXMgaXRlbSB0byBXRyBtb3JlIHRoYW4gMSB5ZWFyIGZyb20gSUVU RjgwIChodHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzgwL3NsaWRlcy9yYWRleHQtNS5w ZGYgKS4gUmVhbGx5IGhvcGUgaXQgY291bGQgYmUgcHVibGlzaGVkIGFzIGEgd29yayBncm91cCBp dGVtIHNvb24uDQoNCg0KQmVzdCBSZWdhcmRzLA0KTGVhZiBZZWgNCg0KQWR2YW5jZWQgUmVzZWFy Y2gsIE5ldHdvcmsgUHJvZHVjdCBMaW5lLCBIdWF3ZWkgVGVjaG5vbG9naWVzIENvLiwgTHRkLg0K UGhvbmU6ICs4Ni03NTUtMjg5Nzg4NTEsICBNb2JpbGU6ICs4Ni0xMzYwMDQ1MTA3NSwgIA0KUG9z dGFsIEFkZHJlc3M6IEY0LTNBLCBIdWF3ZWksIEJhbnRpYW4sIExvbmdnYW5nIERpc3RyaWN0LFNo ZW56aGVuIDUxODEyOSwgUC5SLkNoaW5hDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N CkZyb206IHJhZGV4dC1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86cmFkZXh0LWJvdW5jZXNAaWV0 Zi5vcmddIE9uIEJlaGFsZiBPZiBTYW5jaGV6LCBNYXVyaWNpbyAoSFAgTmV0d29ya2luZykNClNl bnQ6IFR1ZXNkYXksIE1heSAwOCwgMjAxMiA1OjQ2IEFNDQpUbzogcmFkZXh0QGlldGYub3JnDQpT dWJqZWN0OiBbcmFkZXh0XSBSQURFWFQgQCBJRVRGODM6IE1lZXRpbmcgbm90ZXMNCg0KDQpNZWV0 aW5nIG5vdGVzIHVwIGhhdmUgYmVlbiB1cGxvYWRlZCBmb3Igb3VyIG1lZXRpbmcgYXQgSUVURiA4 My4gIFRoYW5rcyB0byBTdGVmYW4gZm9yIGFjdGluZyBhcyBzY3JpYmUuICBBbnkgY29ycmVjdGlv bnMvbW9kaWZpY2F0aW9ucyB3ZWxjb21lIHByaW9yIHRvIE1heSAxNC4NCg0KaHR0cDovL3d3dy5p ZXRmLm9yZy9wcm9jZWVkaW5ncy84My9taW51dGVzL21pbnV0ZXMtODMtcmFkZXh0LnR4dA0KDQot IE1hdXJpY2lvIGFuZCBKb3VuaQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX18NCnJhZGV4dCBtYWlsaW5nIGxpc3QNCnJhZGV4dEBpZXRmLm9yZw0KaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQNCg== From radext-bounces@ietf.org Tue May 8 04:08:30 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5F121F8446; Tue, 8 May 2012 04:08:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336475310; bh=W1YBAwx5Nf6iI4RuCXJosq9qkx4s2fdQ/J4LAdOlpgE=; h=From:To:Date:Message-ID:References:In-Reply-To:MIME-Version: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=EvmybTemHrrnouxGZkQViNq/mLUOx4quzexv3kaC3IcFYPpdAhAZqDmG5yH2b/0K4 3oB/g8jVL9Yt3Dc0U72swC1fuGcPUnUUh1IAvhD0CSsXESmSwSFmZjxs6th5CvCsc3 +SqCP9cFnsB6Ghr0bTYmaBtr1vxaCPGs/zP7yq1E= 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 6D33121F8440 for ; Tue, 8 May 2012 04:08:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.564 X-Spam-Level: X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599] 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 mRxIhFcphQHb for ; Tue, 8 May 2012 04:08:27 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 99AE821F8446 for ; Tue, 8 May 2012 04:08:27 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFP76703; Tue, 08 May 2012 07:08:27 -0400 (EDT) Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 8 May 2012 04:05:45 -0700 Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 8 May 2012 04:05:47 -0700 Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.168]) by szxeml424-hub.china.huawei.com ([10.82.67.163]) with mapi id 14.01.0323.003; Tue, 8 May 2012 19:05:40 +0800 From: Leaf yeh To: "Sanchez, Mauricio (HP Networking)" , "radext@ietf.org" Thread-Topic: RADEXT @ IETF83: Meeting notes - RADIUS Accounting Extensions of Traffic Statistics Thread-Index: AQHNLQqBy7w8ZDU+KkimIWn+KZE65g== Date: Tue, 8 May 2012 11:05:40 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.70.39.132] MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: Re: [radext] RADEXT @ IETF83: Meeting notes - RADIUS Accounting Extensions of Traffic Statistics X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org http://www.ietf.org/proceedings/83/minutes/minutes-83-radext.txt 3. RADIUS Accounting Extensions of Traffic Statistics, Leaf Yeh -http://tools.ietf.org/html/draft-yeh-radext-ext-traffic-statistics -"Design-3" (identical to approach in draft-winter-radext-fancyaccounting) uses TLV data type. -Discussions revealed the fundamental question for go-ahead: should we define accounting attribute just for IPv6 accounting, or a generically re-usable approach to allow accounting after arbitrary criteria? -Question will be discussed in the course of re-chartering. 1. Yes, draft-yeh-radext-ext-traffic-statistics-02 adopted TLV as the data type for the new (container) attribute, Acct-Traffic-Statistics, per the new basic data type of TLV defined in draft-ietf-radext-radius-extensions and the expert insistence of Stafen & Alan. 2. I still don't think that to 'define accounting attribute just for IPv6 accounting' can meet the whole requirement of the reporting on the IPv4/IPv6 separated and combined traffic statistics, which was presented & reviewed in the RADEXT session of IETF82, Taipei. Pls. refer to http://www.ietf.org/proceedings/82/slides/radext-2.pptx and Section 9.4 of BBF TR-187. If we only define new attribute just for IPv6, we might use this new attribute to report the separated IPv6 traffic statistics, and might use 42 Acct-Input-Octets [RFC2866] 43 Acct-Output-Octets [RFC2866] 47 Acct-Input-Packets [RFC2866] 48 Acct-Output-Packets [RFC2866] 52 Acct-Input-Gigawords [RFC2869] 53 Acct-Output-Gigawords [RFC2869] to report the separated IPv4 traffic statistics, but then to report the IPv4/IPv6 combined traffic statistics? Or we do the calculation at the RADIUS server side. I supposed the above 6 attributes might be recommended to report the IPv4/IPv6 combined traffic statistics in Section 9.4 of BBF TR-187. 3. As I mentioned in my presentation (http://www.ietf.org/proceedings/83/slides/slides-83-radext-1.pdf ) at the RADEXT session of IETF83, Paris, to adopt nesting-TLV as the data type for the new defined attribute, Acct-Traffic-Statistics, in the extended type space might gain the extensibility for the future possible refined usage. For example, if we intend to report the traffic statistics associated with DSCP, Differentiated Services Code Point, we might include a new sub-attribute in the Group to refine the traffic-type (or we call it stack-type). It sounds a new field in the complex data structure, which at last turns to be a new attribute in the group of nesting-TLV. The question to the WG might be whether it is necessary to present DSCP in the traffic statistics. I guess it is not harmful if we defined DSCP attribute now, because the operator still can choose not to use it now. Look forward to your further discussion and comments on it. I've introduced this item to WG more than 1 year from IETF80 (http://www.ietf.org/proceedings/80/slides/radext-5.pdf ). Really hope it could be published as a work group item soon. Best Regards, Leaf Yeh Advanced Research, Network Product Line, Huawei Technologies Co., Ltd. Phone: +86-755-28978851, Mobile: +86-13600451075, Postal Address: F4-3A, Huawei, Bantian, Longgang District,Shenzhen 518129, P.R.China -----Original Message----- From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf Of Sanchez, Mauricio (HP Networking) Sent: Tuesday, May 08, 2012 5:46 AM To: radext@ietf.org Subject: [radext] RADEXT @ IETF83: Meeting notes Meeting notes up have been uploaded for our meeting at IETF 83. Thanks to Stefan for acting as scribe. Any corrections/modifications welcome prior to May 14. http://www.ietf.org/proceedings/83/minutes/minutes-83-radext.txt - Mauricio and Jouni _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From paul.congdon@hp.com Tue May 8 08:27:04 2012 Return-Path: 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 566A121F854F for ; Tue, 8 May 2012 08:27:04 -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 2spMy3l6tR0t for ; Tue, 8 May 2012 08:27:03 -0700 (PDT) Received: from g1t0029.austin.hp.com (g1t0029.austin.hp.com [15.216.28.36]) by ietfa.amsl.com (Postfix) with ESMTP id A058921F8549 for ; Tue, 8 May 2012 08:27:03 -0700 (PDT) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0029.austin.hp.com (Postfix) with ESMTPS id 0F56838035; Tue, 8 May 2012 15:26:56 +0000 (UTC) Received: from G5W0326.americas.hpqcorp.net (16.228.8.70) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.2.283.4; Tue, 8 May 2012 15:26:02 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0326.americas.hpqcorp.net ([16.228.8.70]) with mapi; Tue, 8 May 2012 16:26:01 +0100 From: "Congdon, Paul T (HPLabs)" To: "Romascanu, Dan (Dan)" , "Sanchez, Mauricio (HP Networking)" , "radext@ietf.org" Date: Tue, 8 May 2012 16:26:01 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBI= Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 15:27:04 -0000 You may also want to include 802.11 Paul -- Sent from my HP TouchPad ________________________________ On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) wrote: FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I believe having experts from the IEEE 802.1 WG review and comment on this document would be very useful. Regards, Dan > -----Original Message----- > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > Behalf Of Sanchez, Mauricio (HP Networking) > Sent: Tuesday, May 08, 2012 12:46 AM > To: radext@ietf.org > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > 802Networks" > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > for IEEE 802 Networks", prior to sending the document to the IESG for > publication as a proposed standard RFC. > > The document is available for inspection here: > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > The RADEXT WG last call will last until Monday May 21, 2012. If you > have comments on the document, please file using TRAC system. See > below for summary of instructions. > > Thanks, > Mauricio and Jouni > > 1. To submit an issue in TRAC, you first need to login to the > RADEXT WG site on the tools server: > http://tools.ietf.org/wg/radext/trac/login > 2. If you don't already have a login ID, you can obtain one by > navigating to this site: http://trac.tools.ietf.org/newlogin > 3. Once you have obtained an account, and have logged in, you can > file an issue by navigating to the ticket entry > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > 4. When opening an issue: > a. The Type: field should be set to "defect" for an issue with > the current document text, or "enhancement" for a proposed addition of > functionality (such as an additional requirement). > b. The Priority: field is set based on the severity of the Issue. > For example, editorial issues are typically "minor" or "trivial". > c. The Milestone: field should be set to milestone1 (useless, I > know). > d. The Component: field should be set to the document you are > filing the issue on. > e. The Version: field should be set to "1.0". > f. The Severity: field should be set to based on the status of > the document (e.g. "In WG Last Call" for a document in WG last call) > g. The Keywords: and CC: fields can be left blank unless > inspiration seizes you. > h. The Assign To: field is generally filled in with the email > address of the editor. > 5. Typically it won't be necessary to enclose a file with the > ticket, but if you need to, select "I have files to attach to this > ticket". > 6. If you want to preview your Issue, click on the "Preview" > button. When you're ready to submit the issue, click on the "Create > Ticket" button. > 7. If you want to update an issue, go to the "View Tickets" page: > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket > # you want to update, and then modify the ticket fields as required > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Tue May 8 08:27:05 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0493F21F854F; Tue, 8 May 2012 08:27:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336490825; bh=cesAvIWiKVBqPvLn+1q+/puVl+8n+/lmOSFFPKIj//s=; h=From:To:Date:Message-ID:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=udG67IgGA+YOFFiLP9q7pvnWt56+LsFawCZ+1yHj95cXlwHbaIl5gt+E7yawz4wIV iW8RTPPmcstsW7dSowP+RgsvPKkrFmXEE8biFXnlME+QJ1NtILSE7ktmK7ijfxxMSj RqNRI7e4fq/JoBIsfrizMYMJQRzLJAR4ZsxPEs/k= 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 566A121F854F for ; Tue, 8 May 2012 08:27:04 -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 2spMy3l6tR0t for ; Tue, 8 May 2012 08:27:03 -0700 (PDT) Received: from g1t0029.austin.hp.com (g1t0029.austin.hp.com [15.216.28.36]) by ietfa.amsl.com (Postfix) with ESMTP id A058921F8549 for ; Tue, 8 May 2012 08:27:03 -0700 (PDT) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0029.austin.hp.com (Postfix) with ESMTPS id 0F56838035; Tue, 8 May 2012 15:26:56 +0000 (UTC) Received: from G5W0326.americas.hpqcorp.net (16.228.8.70) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.2.283.4; Tue, 8 May 2012 15:26:02 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0326.americas.hpqcorp.net ([16.228.8.70]) with mapi; Tue, 8 May 2012 16:26:01 +0100 From: "Congdon, Paul T (HPLabs)" To: "Romascanu, Dan (Dan)" , "Sanchez, Mauricio (HP Networking)" , "radext@ietf.org" Date: Tue, 8 May 2012 16:26:01 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBI= Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE 802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org You may also want to include 802.11 Paul -- Sent from my HP TouchPad ________________________________ On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) wrote: FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I believe having experts from the IEEE 802.1 WG review and comment on this document would be very useful. Regards, Dan > -----Original Message----- > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > Behalf Of Sanchez, Mauricio (HP Networking) > Sent: Tuesday, May 08, 2012 12:46 AM > To: radext@ietf.org > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > 802Networks" > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > for IEEE 802 Networks", prior to sending the document to the IESG for > publication as a proposed standard RFC. > > The document is available for inspection here: > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > The RADEXT WG last call will last until Monday May 21, 2012. If you > have comments on the document, please file using TRAC system. See > below for summary of instructions. > > Thanks, > Mauricio and Jouni > > 1. To submit an issue in TRAC, you first need to login to the > RADEXT WG site on the tools server: > http://tools.ietf.org/wg/radext/trac/login > 2. If you don't already have a login ID, you can obtain one by > navigating to this site: http://trac.tools.ietf.org/newlogin > 3. Once you have obtained an account, and have logged in, you can > file an issue by navigating to the ticket entry > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > 4. When opening an issue: > a. The Type: field should be set to "defect" for an issue with > the current document text, or "enhancement" for a proposed addition of > functionality (such as an additional requirement). > b. The Priority: field is set based on the severity of the Issue. > For example, editorial issues are typically "minor" or "trivial". > c. The Milestone: field should be set to milestone1 (useless, I > know). > d. The Component: field should be set to the document you are > filing the issue on. > e. The Version: field should be set to "1.0". > f. The Severity: field should be set to based on the status of > the document (e.g. "In WG Last Call" for a document in WG last call) > g. The Keywords: and CC: fields can be left blank unless > inspiration seizes you. > h. The Assign To: field is generally filled in with the email > address of the editor. > 5. Typically it won't be necessary to enclose a file with the > ticket, but if you need to, select "I have files to attach to this > ticket". > 6. If you want to preview your Issue, click on the "Preview" > button. When you're ready to submit the issue, click on the "Create > Ticket" button. > 7. If you want to update an issue, go to the "View Tickets" page: > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket > # you want to update, and then modify the ticket fields as required > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Tue May 8 10:06:39 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDA821F8603; Tue, 8 May 2012 10:06:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336496799; bh=gdfz8NLG3E9L3qwsFZNnl/Z3RniAsfjYJv6T9LXICLg=; h=MIME-Version:Date:Message-ID:In-Reply-To:References:From:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=hZ+RGXezS2/hRMAYu/uyq5l+9X24YoTt9DDHFOunZXwAnsnoxIuFRsf1++e3oznDG GiOBkXMBKDmm6GL/Y9oX7oIgrtHWA8S3jTMfiNeAsAOY32YsTnlzPxH6XUeay5RT9t Ie6he4I54LVuK2afmeX+e4hdA9daXB3HbUkjIH+Y= 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 0869B21F8600 for ; Tue, 8 May 2012 10:06:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.329 X-Spam-Level: X-Spam-Status: No, score=-103.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 PASACo6BMYCo for ; Tue, 8 May 2012 10:06:38 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id DC26421F8608 for ; Tue, 8 May 2012 10:06:37 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAFAPpRqU/GmAcF/2dsb2JhbABEsy2BB4IMAQEBAQMBAQEPHgoxAxcEAgEIDQQEAQEBCgYFAQEFCwEGASYfCQgBAQQBEggah2wLnhOdOYsDJYI7CAGCRmMElw+FB4oqgmuBVgY X-IronPort-AV: E=Sophos;i="4.75,552,1330923600"; d="scan'208";a="305441558" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 May 2012 13:05:29 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 May 2012 11:26:43 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 8 May 2012 17:29:56 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBIAABjtwA== References: From: "Romascanu, Dan (Dan)" To: "Congdon, Paul T (HPLabs)" , "Sanchez, Mauricio (HP Networking)" , Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Good point - can you forward to their reflector or do you know anybody who can do it? Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" > > You may also want to include 802.11 > > Paul > > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From dromasca@avaya.com Tue May 8 10:06:39 2012 Return-Path: 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 0869B21F8600 for ; Tue, 8 May 2012 10:06:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.329 X-Spam-Level: X-Spam-Status: No, score=-103.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 PASACo6BMYCo for ; Tue, 8 May 2012 10:06:38 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id DC26421F8608 for ; Tue, 8 May 2012 10:06:37 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAFAPpRqU/GmAcF/2dsb2JhbABEsy2BB4IMAQEBAQMBAQEPHgoxAxcEAgEIDQQEAQEBCgYFAQEFCwEGASYfCQgBAQQBEggah2wLnhOdOYsDJYI7CAGCRmMElw+FB4oqgmuBVgY X-IronPort-AV: E=Sophos;i="4.75,552,1330923600"; d="scan'208";a="305441558" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 May 2012 13:05:29 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 May 2012 11:26:43 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 8 May 2012 17:29:56 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBIAABjtwA== References: From: "Romascanu, Dan (Dan)" To: "Congdon, Paul T (HPLabs)" , "Sanchez, Mauricio (HP Networking)" , Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 17:06:39 -0000 Good point - can you forward to their reflector or do you know anybody who can do it?=20 Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" >=20 > You may also want to include 802.11 >=20 > Paul >=20 > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. >=20 > Regards, >=20 > Dan >=20 >=20 >=20 >=20 > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From paul.congdon@hp.com Tue May 8 10:34:19 2012 Return-Path: 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 3F9D821F8597 for ; Tue, 8 May 2012 10:34:19 -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 gUUWG3zUopi9 for ; Tue, 8 May 2012 10:34:18 -0700 (PDT) Received: from g5t0007.atlanta.hp.com (g5t0007.atlanta.hp.com [15.192.0.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECE121F8596 for ; Tue, 8 May 2012 10:34:17 -0700 (PDT) Received: from G6W1798G.americas.hpqcorp.net (g6w1798g.atlanta.hp.com [16.230.17.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g5t0007.atlanta.hp.com (Postfix) with ESMTPS id 93C061422A; Tue, 8 May 2012 17:34:17 +0000 (UTC) Received: from G6W0173.americas.hpqcorp.net (16.230.33.182) by G6W1798G.americas.hpqcorp.net (16.230.17.175) with Microsoft SMTP Server (TLS) id 14.2.283.4; Tue, 8 May 2012 17:33:23 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0173.americas.hpqcorp.net ([16.230.33.182]) with mapi; Tue, 8 May 2012 18:33:22 +0100 From: "Congdon, Paul T (HPLabs)" To: "Romascanu, Dan (Dan)" , "Sanchez, Mauricio (HP Networking)" , "radext@ietf.org" Date: Tue, 8 May 2012 18:33:19 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBIAABjtwAAEUjrQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 17:34:19 -0000 I typically forward these type of announcements to the EC reflector and cal= l attention to the appropriate WGs. There are likely other wireless groups= that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf Of= Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@iet= f.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Ne= tworks" Good point - can you forward to their reflector or do you know anybody who can do it?=20 Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" >=20 > You may also want to include 802.11 >=20 > Paul >=20 > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. >=20 > Regards, >=20 > Dan >=20 >=20 >=20 >=20 > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Tue May 8 10:34:21 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7442221F8597; Tue, 8 May 2012 10:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336498461; bh=rxKrQmDTAByeBFozMQSEOWI0K/uZtA6EAEK43fbm3nY=; h=From:To:Date:Message-ID:References:In-Reply-To:MIME-Version: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=oehxjLyRA2B8mXbZnWxxmV3A2xvwB4mCxvCXBVMjr5XMGl8/xINqd2Zw4d9yMuttT 2HOSh4UWtmXd4ddRs62TVJyIvGj9dI5/uYf4Uqzu8VL1jX9aZfNbZXLvEPMIQisayL o9aDwBOAejc5qQVsbT06s/xfzOzkJmnUPvqUdGwc= 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 3F9D821F8597 for ; Tue, 8 May 2012 10:34:19 -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 gUUWG3zUopi9 for ; Tue, 8 May 2012 10:34:18 -0700 (PDT) Received: from g5t0007.atlanta.hp.com (g5t0007.atlanta.hp.com [15.192.0.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECE121F8596 for ; Tue, 8 May 2012 10:34:17 -0700 (PDT) Received: from G6W1798G.americas.hpqcorp.net (g6w1798g.atlanta.hp.com [16.230.17.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g5t0007.atlanta.hp.com (Postfix) with ESMTPS id 93C061422A; Tue, 8 May 2012 17:34:17 +0000 (UTC) Received: from G6W0173.americas.hpqcorp.net (16.230.33.182) by G6W1798G.americas.hpqcorp.net (16.230.17.175) with Microsoft SMTP Server (TLS) id 14.2.283.4; Tue, 8 May 2012 17:33:23 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0173.americas.hpqcorp.net ([16.230.33.182]) with mapi; Tue, 8 May 2012 18:33:22 +0100 From: "Congdon, Paul T (HPLabs)" To: "Romascanu, Dan (Dan)" , "Sanchez, Mauricio (HP Networking)" , "radext@ietf.org" Date: Tue, 8 May 2012 18:33:19 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBIAABjtwAAEUjrQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org I typically forward these type of announcements to the EC reflector and call attention to the appropriate WGs. There are likely other wireless groups that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@ietf.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" Good point - can you forward to their reflector or do you know anybody who can do it? Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" > > You may also want to include 802.11 > > Paul > > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From dromasca@avaya.com Tue May 8 10:49:03 2012 Return-Path: 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 61A3521F8546 for ; Tue, 8 May 2012 10:49:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.834 X-Spam-Level: X-Spam-Status: No, score=-102.834 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 b6N23oPhAvKD for ; Tue, 8 May 2012 10:49:02 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1671C21F8526 for ; Tue, 8 May 2012 10:49:01 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUFACdcqU/GmAcF/2dsb2JhbABEqWUBiUeBB4IMAQEBAQMBAQEPChEDOwMXBAIBCA0EBAEBAQoGBQEBBQsBBgEmHwkIAQEEARIIGodsC54MnTWLAyWCOwgBgkZjBIgwjl+FB4oqgmuBVgY X-IronPort-AV: E=Sophos;i="4.75,552,1330923600"; d="scan'208,217";a="8169187" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 08 May 2012 13:48:28 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 May 2012 13:47:17 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD2D42.C65E2C0B" Date: Tue, 8 May 2012 19:47:59 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBIAABjtwAAEUjrQAACKJMw= References: From: "Romascanu, Dan (Dan)" To: "Congdon, Paul T (HPLabs)" , "Sanchez, Mauricio (HP Networking)" , Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 17:49:03 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CD2D42.C65E2C0B Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes, please forward to the EC reflector.=20 Thanks,=20 Dan -----Original Message----- From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] Sent: Tue 5/8/2012 8:33 PM To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); = radext@ietf.org Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes = forIEEE802Networks" =20 I typically forward these type of announcements to the EC reflector and = call attention to the appropriate WGs. There are likely other wireless = groups that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf = Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); = radext@ietf.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for = IEEE802Networks" Good point - can you forward to their reflector or do you know anybody who can do it?=20 Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" >=20 > You may also want to include 802.11 >=20 > Paul >=20 > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. >=20 > Regards, >=20 > Dan >=20 >=20 >=20 >=20 > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext ------_=_NextPart_001_01CD2D42.C65E2C0B Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [radext] RADEXT WG Last Call: "RADIUS Attributes = forIEEE802Networks"

Yes, please forward to the EC reflector.

Thanks,

Dan



-----Original Message-----
From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com]
Sent: Tue 5/8/2012 8:33 PM
To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); = radext@ietf.org
Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes = forIEEE802Networks"

I typically forward these type of announcements to the EC reflector and = call attention to the appropriate WGs.  There are likely other = wireless groups that have interest.  I can forward for you.
Paul

-----Original Message-----
From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Tuesday, May 08, 2012 8:30 AM
To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); = radext@ietf.org
Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for = IEEE802Networks"

Good point - can you forward to their reflector or do you know = anybody
who can do it?

Dan




> -----Original Message-----
> From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com]
> Sent: Tuesday, May 08, 2012 6:26 PM
> To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking);
> radext@ietf.org
> Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes = for
> IEEE802Networks"
>
> You may also want to include 802.11
>
> Paul
>
> -- Sent from my HP TouchPad
> ________________________________
> On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) = <dromasca@avaya.com>
> wrote:
> FYI - I forwarded the WGLC announcement to the IEEE 802.1 = reflector. I
> believe having experts from the IEEE 802.1 WG review and comment = on
> this
> document would be very useful.
>
> Regards,
>
> Dan
>
>
>
>
> > -----Original Message-----
> > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On
> > Behalf Of Sanchez, Mauricio (HP Networking)
> > Sent: Tuesday, May 08, 2012 12:46 AM
> > To: radext@ietf.org
> > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes = for IEEE
> > 802Networks"
> >
> > This is an announcement of RADEXT WG last call on "RADIUS = Attributes
> > for IEEE 802 Networks", prior to sending the document to = the IESG
for
> > publication as a proposed standard RFC.
> >
> > The document is available for inspection here:
> > http://too= ls.ietf.org/id/draft-ietf-radext-ieee802ext
> >
> > The RADEXT WG last call will last until Monday May 21, = 2012.   If
you
> > have comments on the document, please file using TRAC = system.  See
> > below for summary of instructions.
> >
> > Thanks,
> > Mauricio and Jouni
> >
> > 1.       To submit an issue in = TRAC, you first need to login to the
> > RADEXT WG site on the tools server:
> > http://tools.ietf.org= /wg/radext/trac/login
> > 2.       If you don't already = have a login ID, you can obtain one by
> > navigating to this site:   http://trac.tools.ietf.org/n= ewlogin
> > 3.       Once you have obtained = an account, and have logged in, you
> can
> > file an issue by navigating to the  ticket entry
> > form:http://trac.= tools.ietf.org/wg/radext/trac/newticket
> > 4.       When opening an = issue:
> > a.       The Type: field should = be set to "defect" for an issue with
> > the current document text, or "enhancement" for a = proposed addition
> of
> > functionality (such as an additional requirement).
> > b.      The Priority: field is set = based on the severity of the
> Issue.
> > For example, editorial issues are typically "minor" = or "trivial".
> > c.       The Milestone: field = should be set to milestone1 (useless,
I
> > know).
> > d.      The Component: field should = be set to the document you are
> > filing the issue on.
> > e.      The Version: field should be = set to "1.0".
> > f.        The Severity: = field should be set to based on the status
of
> > the document (e.g. "In WG Last Call" for a document = in WG last call)
> > g.        The Keywords: and = CC: fields can be left blank unless
> > inspiration seizes you.
> > h.      The Assign To: field is = generally filled in with the email
> > address of the editor.
> > 5.       Typically it won't be = necessary to enclose a file with the
> > ticket, but if you need to, select "I have files to = attach to this
> > ticket".
> > 6.       If you want to preview = your Issue, click on the "Preview"
> > button.  When you're ready to submit the issue, click on = the "Create
> > Ticket" button.
> > 7.       If you want to update = an issue, go to the "View Tickets"
> page:
> > http://trac.t= ools.ietf.org/wg/radext/trac/report/1  Click on the
> ticket
> > # you want to update, and then modify the ticket fields as = required
> > _______________________________________________
> > radext mailing list
> > radext@ietf.org
> > https://www.ietf.or= g/mailman/listinfo/radext
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.or= g/mailman/listinfo/radext
_______________________________________________
radext mailing list
radext@ietf.org
https://www.ietf.or= g/mailman/listinfo/radext

------_=_NextPart_001_01CD2D42.C65E2C0B-- From radext-bounces@ietf.org Tue May 8 10:49:05 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6816C21F8541; Tue, 8 May 2012 10:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336499345; bh=EunWP4N2IhrhudQ+THzhQDtzAFODA9qNzlD5YnkcChY=; h=MIME-Version:Date:Message-ID:References:From:To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Sender; b=sBMu+qud7/AchVI0HrtFJ4R6n5Zs+/pkzYu8wh4NmlDzoaGRqHTjT0X666ntL8e8P PF4+vyvskUB5czQaDjZ+3Y6t3UOuwVkgYCzzD7JwoTs91dg2XzkcITZMD1blFQ4xcs iC3GwgtRT3kFZVTrcTZOOXPHb3LYJtxktiRnHSsI= 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 61A3521F8546 for ; Tue, 8 May 2012 10:49:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.834 X-Spam-Level: X-Spam-Status: No, score=-102.834 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 b6N23oPhAvKD for ; Tue, 8 May 2012 10:49:02 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1671C21F8526 for ; Tue, 8 May 2012 10:49:01 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUFACdcqU/GmAcF/2dsb2JhbABEqWUBiUeBB4IMAQEBAQMBAQEPChEDOwMXBAIBCA0EBAEBAQoGBQEBBQsBBgEmHwkIAQEEARIIGodsC54MnTWLAyWCOwgBgkZjBIgwjl+FB4oqgmuBVgY X-IronPort-AV: E=Sophos;i="4.75,552,1330923600"; d="scan'208,217";a="8169187" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 08 May 2012 13:48:28 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 May 2012 13:47:17 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 8 May 2012 19:47:59 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Thread-Index: Ac0smsJwaIMfMLc7Q+C2tU2pmwf6nQAXD/zwAA33ZBIAABjtwAAEUjrQAACKJMw= References: From: "Romascanu, Dan (Dan)" To: "Congdon, Paul T (HPLabs)" , "Sanchez, Mauricio (HP Networking)" , Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8831186487540388572==" Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org This is a multi-part message in MIME format. --===============8831186487540388572== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD2D42.C65E2C0B" This is a multi-part message in MIME format. ------_=_NextPart_001_01CD2D42.C65E2C0B Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes, please forward to the EC reflector.=20 Thanks,=20 Dan -----Original Message----- From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] Sent: Tue 5/8/2012 8:33 PM To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); = radext@ietf.org Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes = forIEEE802Networks" =20 I typically forward these type of announcements to the EC reflector and = call attention to the appropriate WGs. There are likely other wireless = groups that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf = Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); = radext@ietf.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for = IEEE802Networks" Good point - can you forward to their reflector or do you know anybody who can do it?=20 Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" >=20 > You may also want to include 802.11 >=20 > Paul >=20 > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. >=20 > Regards, >=20 > Dan >=20 >=20 >=20 >=20 > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext ------_=_NextPart_001_01CD2D42.C65E2C0B Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [radext] RADEXT WG Last Call: "RADIUS Attributes = forIEEE802Networks"

Yes, please forward to the EC reflector.

Thanks,

Dan



-----Original Message-----
From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com]
Sent: Tue 5/8/2012 8:33 PM
To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); = radext@ietf.org
Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes = forIEEE802Networks"

I typically forward these type of announcements to the EC reflector and = call attention to the appropriate WGs.  There are likely other = wireless groups that have interest.  I can forward for you.
Paul

-----Original Message-----
From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Tuesday, May 08, 2012 8:30 AM
To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); = radext@ietf.org
Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for = IEEE802Networks"

Good point - can you forward to their reflector or do you know = anybody
who can do it?

Dan




> -----Original Message-----
> From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com]
> Sent: Tuesday, May 08, 2012 6:26 PM
> To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking);
> radext@ietf.org
> Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes = for
> IEEE802Networks"
>
> You may also want to include 802.11
>
> Paul
>
> -- Sent from my HP TouchPad
> ________________________________
> On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) = <dromasca@avaya.com>
> wrote:
> FYI - I forwarded the WGLC announcement to the IEEE 802.1 = reflector. I
> believe having experts from the IEEE 802.1 WG review and comment = on
> this
> document would be very useful.
>
> Regards,
>
> Dan
>
>
>
>
> > -----Original Message-----
> > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On
> > Behalf Of Sanchez, Mauricio (HP Networking)
> > Sent: Tuesday, May 08, 2012 12:46 AM
> > To: radext@ietf.org
> > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes = for IEEE
> > 802Networks"
> >
> > This is an announcement of RADEXT WG last call on "RADIUS = Attributes
> > for IEEE 802 Networks", prior to sending the document to = the IESG
for
> > publication as a proposed standard RFC.
> >
> > The document is available for inspection here:
> > http://too= ls.ietf.org/id/draft-ietf-radext-ieee802ext
> >
> > The RADEXT WG last call will last until Monday May 21, = 2012.   If
you
> > have comments on the document, please file using TRAC = system.  See
> > below for summary of instructions.
> >
> > Thanks,
> > Mauricio and Jouni
> >
> > 1.       To submit an issue in = TRAC, you first need to login to the
> > RADEXT WG site on the tools server:
> > http://tools.ietf.org= /wg/radext/trac/login
> > 2.       If you don't already = have a login ID, you can obtain one by
> > navigating to this site:   http://trac.tools.ietf.org/n= ewlogin
> > 3.       Once you have obtained = an account, and have logged in, you
> can
> > file an issue by navigating to the  ticket entry
> > form:http://trac.= tools.ietf.org/wg/radext/trac/newticket
> > 4.       When opening an = issue:
> > a.       The Type: field should = be set to "defect" for an issue with
> > the current document text, or "enhancement" for a = proposed addition
> of
> > functionality (such as an additional requirement).
> > b.      The Priority: field is set = based on the severity of the
> Issue.
> > For example, editorial issues are typically "minor" = or "trivial".
> > c.       The Milestone: field = should be set to milestone1 (useless,
I
> > know).
> > d.      The Component: field should = be set to the document you are
> > filing the issue on.
> > e.      The Version: field should be = set to "1.0".
> > f.        The Severity: = field should be set to based on the status
of
> > the document (e.g. "In WG Last Call" for a document = in WG last call)
> > g.        The Keywords: and = CC: fields can be left blank unless
> > inspiration seizes you.
> > h.      The Assign To: field is = generally filled in with the email
> > address of the editor.
> > 5.       Typically it won't be = necessary to enclose a file with the
> > ticket, but if you need to, select "I have files to = attach to this
> > ticket".
> > 6.       If you want to preview = your Issue, click on the "Preview"
> > button.  When you're ready to submit the issue, click on = the "Create
> > Ticket" button.
> > 7.       If you want to update = an issue, go to the "View Tickets"
> page:
> > http://trac.t= ools.ietf.org/wg/radext/trac/report/1  Click on the
> ticket
> > # you want to update, and then modify the ticket fields as = required
> > _______________________________________________
> > radext mailing list
> > radext@ietf.org
> > https://www.ietf.or= g/mailman/listinfo/radext
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.or= g/mailman/listinfo/radext
_______________________________________________
radext mailing list
radext@ietf.org
https://www.ietf.or= g/mailman/listinfo/radext

------_=_NextPart_001_01CD2D42.C65E2C0B-- --===============8831186487540388572== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext --===============8831186487540388572==-- From jsalowey@cisco.com Tue May 8 14:09:54 2012 Return-Path: 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 6771A21F85AD for ; Tue, 8 May 2012 14:09:54 -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 0lKkn0AAqlXW for ; Tue, 8 May 2012 14:09:53 -0700 (PDT) Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 24C3A21F84D3 for ; Tue, 8 May 2012 14:09:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsalowey@cisco.com; l=8185; q=dns/txt; s=iport; t=1336511393; x=1337720993; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=57pufM55H+hLxqWQobpaD8h9+CwAMMI7roJaHRdpaCg=; b=l1TpxBp8KUU7DJyLLOdo0OefTjTQ3WGUi1rsjdMkfnMS+IzuLrCCiekC vnbb8GvCrgrqANKpIysjgdW77CgqHkU5QyrHCahDNufCmmloCOhTsS4XD toXDXkXLh9pwVdbIVG8mdFiSltVPwdZN6XWWgmushl0hNtrwRBLqcifBF g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AicGAK2KqU+rRDoJ/2dsb2JhbABEgx6sN4NXgQeCJQGBJoEzh2uZboEooBeLA4UvYwSIZIkug2yFdohjgWmDCQ X-IronPort-AV: E=Sophos;i="4.75,553,1330905600"; d="scan'208";a="41452597" Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 08 May 2012 21:09:52 +0000 Received: from [10.33.251.111] ([10.33.251.111]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q48L9qB4024144 for ; Tue, 8 May 2012 21:09:52 GMT From: Joe Salowey Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Tue, 8 May 2012 14:09:51 -0700 Message-Id: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> To: radext@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 21:09:54 -0000 I've received a few off list suggestions for additional RADIUS = attributes to add to RADIUS Attributes for IEEE 802 Networks. These = include 1. WLAN-Reason-Code - used to transmit the reason for authentication = failure from AAA to AP in an Access-Reject. The code is included in = reason code of a Disassociation or De-authentication Frame 2. WLAN-Pairwise-Cipher - communicates the negotiated pairwise cipher = from the AP to the AAA. 3. WLAN-Group-Cipher - communicates the negotiated group cipher from = the AP to the AAA.=20 4. WLAN-AKM-Suite - contains information on the authentication and key = management suite negotiated buy the AP.=20 5. WLAN-RF-Band - contains information on the RF band used by the AP. =20= Below is suggested text for these attributes from Dave Stephenson: Thanks, Joe =20 2.9. WLAN-Reason-Code =20 Description =20 The WLAN-Reason-Code Attribute contains information on the reason for = authorization failure subsequent to a mobile device=92s authentication = request towards a Wi-Fi access network. =20 A WLAN-Reason-Code Attribute MAY be included within an Access-Reject or = Disconnect-Request packet. Upon receipt of an Access-Reject packet, the = WLAN-Reason-Code value is copied by the Authenticator / AP into the = Reason code field of a Disassociation or Deauthentication frame (see = clause 8.3.3.4 and 8.3.3.12 respectively in IEEE 802.11-2012), which is = subsequently transmitted to the Supplicant / mobile device. A summary = of the WLAN-Reason-Code Attribute format is shown below. The fields are = transmitted from left to right. =20 0 1 2 3=20 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 | Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20 Code tbd8 =20 Length =3D2 =20 Value The Value field is two octets containing a 16-bit unsigned integer drawn = from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The value=92s = least significant octet is contained in bits 23-16 and most significant = octet in bits 31-24 (network octet order). Note: not all reason codes = defined in the Table 8-36 are expected to be used by an AS. =20 [Note]: the importance of including this attribute is for authentication = and authorization of mobile devices in public Wi-Fi access; it is = important to inform the mobile when authorization is denied, even though = authentication may have been successful. This can occur for AS policy = reasons or for reasons related to the user=92s subscription. The = following Reason codes for public Wi-Fi access networks were added by = the IEEE 802.11u-2011 amendment: =20 Reason Code Value Description 27 Disassociated because session terminated by SP request 28 Disassociated because of lack of SP roaming agreement 29 Requested service rejected because of SP cipher suite or AKM = requirement 30 Requested service not authorized in this location =20 =20 =20 =20 2.10. WLAN-Pairwise-Cipher =20 Description =20 The WLAN-Pairwise-Cipher Attribute contains information on the pairwise = cipher suite used to establish the robust security network association = (RSNA) between the AP and mobile device. =20 A WLAN-Pairwise-Cipher Attribute SHOULD be included within an = Access-Request packet. A summary of the WLAN-Pairwise-Cipher Attribute = format is shown below. The fields are transmitted from left to right. =20 0 1 2 3=20 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 | Value =20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20 Code tbd9 =20 Length =3D4 =20 Value The Value field is four octets formatted in accordance with Figure 8-187 = with values drawn from Table 8-99 of IEEE 802.11-2012. =20 =20 =20 2.11. WLAN-Group-Cipher =20 Description =20 The WLAN-Group-Cipher Attribute contains information on the group cipher = suite used to establish the robust security network association (RSNA) = between the AP and mobile device. =20 A WLAN-Group-Cipher Attribute SHOULD be included within an = Access-Request packet. A summary of the WLAN-Group-Cipher Attribute = format is shown below. The fields are transmitted from left to right. =20 0 1 2 3=20 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 | Value =20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20 Code tbd10 =20 Length =3D4 =20 Value The Value field is four octets formatted in accordance with Figure 8-187 = with values drawn from Table 8-99 of IEEE 802.11-2012. =20 =20 =20 2.12. WLAN-AKM-Suite =20 Description =20 The WLAN-AKM-Suite Attribute contains information on the authentication = and key management suite used to establish the robust security network = association (RSNA) between the AP and mobile device. =20 A WLAN-AKM-Suite Attribute SHOULD be included within an Access-Request = packet. A summary of the WLAN-AKM-Suite Attribute format is shown = below. The fields are transmitted from left to right. =20 0 1 2 3=20 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 | Value =20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20 Code tbd11 =20 Length =3D4 =20 Value The Value field is four octets formatted in accordance with Figure 8-187 = with values drawn from Table 8-101 of IEEE 802.11-2012. =20 =20 =20 2.12. WLAN-RF-Band =20 Description =20 The WLAN-RF-Band Attribute contains information on the RF band used by = the AP for transmission and reception of information to and from the = mobile device. This information can be used, for example, to provide a = relative quality of experience indication for the mobile device=92s user = (i.e., some RF bands have more interference than others). =20 A WLAN-RF-Band Attribute SHOULD be included within an Access-Request = packet. A summary of the WLAN-RF-Band Attribute format is shown below. = The fields are transmitted from left to right. =20 0 1 2 3=20 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 | Value | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20 Code tbd12 =20 Length =3D2 =20 Value The Value field is 1 octet having a value chosen from the table below: Band ID value Meaning 0 TV white spaces 1 Sub-1 GHz (excluding TV white spaces) 2 2.4 GHz 3 3.6 GHz 4 4.9 and 5 GHz 5 60 GHz 6-255 Reserved =20 =20 [Note]: this table was copied from IEEE 802.11ad-d5. I=92m not sure of = the relative publication dates of this internet draft and IEEE = 802.11ad-d5. Since it=92s generally not recommended to reference a = draft specification in an RFC, I=92ve copied the table. If we discover = that the IEEE document will be published in time, then we could deleted = the table and instead reference Table 8-53a in IEEE 802.11ad. =20 =20= From radext-bounces@ietf.org Tue May 8 14:09:56 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3572821F85AE; Tue, 8 May 2012 14:09:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336511396; bh=oCvB2NrV97GGDaX6skStT7k7/VRb2RRZBrHulpTAkkE=; h=From:Date:Message-Id:To:Mime-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=gk6e9ji2+TjdQy0vrW1piQohYLOBG0VNHjhim670mz4v1WsMo0lHU1uXwF0l1NWjF 5buUu9HD8gTAVWD+w2xBjkkhk2suupF/Hiyk6rfM9uwWkvREp41gyrBRVLSoaUUxDa E+9tN2mypCRmAcfwLuEyqCSWUe2CA5bS9zNHMcfA= 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 6771A21F85AD for ; Tue, 8 May 2012 14:09:54 -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 0lKkn0AAqlXW for ; Tue, 8 May 2012 14:09:53 -0700 (PDT) Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 24C3A21F84D3 for ; Tue, 8 May 2012 14:09:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsalowey@cisco.com; l=8185; q=dns/txt; s=iport; t=1336511393; x=1337720993; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=57pufM55H+hLxqWQobpaD8h9+CwAMMI7roJaHRdpaCg=; b=l1TpxBp8KUU7DJyLLOdo0OefTjTQ3WGUi1rsjdMkfnMS+IzuLrCCiekC vnbb8GvCrgrqANKpIysjgdW77CgqHkU5QyrHCahDNufCmmloCOhTsS4XD toXDXkXLh9pwVdbIVG8mdFiSltVPwdZN6XWWgmushl0hNtrwRBLqcifBF g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AicGAK2KqU+rRDoJ/2dsb2JhbABEgx6sN4NXgQeCJQGBJoEzh2uZboEooBeLA4UvYwSIZIkug2yFdohjgWmDCQ X-IronPort-AV: E=Sophos;i="4.75,553,1330905600"; d="scan'208";a="41452597" Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 08 May 2012 21:09:52 +0000 Received: from [10.33.251.111] ([10.33.251.111]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q48L9qB4024144 for ; Tue, 8 May 2012 21:09:52 GMT From: Joe Salowey Date: Tue, 8 May 2012 14:09:51 -0700 Message-Id: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> To: radext@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org I've received a few off list suggestions for additional RADIUS attributes t= o add to RADIUS Attributes for IEEE 802 Networks. These include 1. WLAN-Reason-Code - used to transmit the reason for authentication fai= lure from AAA to AP in an Access-Reject. The code is included in reason co= de of a Disassociation or De-authentication Frame 2. WLAN-Pairwise-Cipher - communicates the negotiated pairwise cipher fro= m the AP to the AAA. 3. WLAN-Group-Cipher - communicates the negotiated group cipher from the A= P to the AAA. = 4. WLAN-AKM-Suite - contains information on the authentication and key man= agement suite negotiated buy the AP. = 5. WLAN-RF-Band - contains information on the RF band used by the AP. = Below is suggested text for these attributes from Dave Stephenson: Thanks, Joe = 2.9. WLAN-Reason-Code = Description = The WLAN-Reason-Code Attribute contains information on the reason for autho= rization failure subsequent to a mobile device=92s authentication request t= owards a Wi-Fi access network. = A WLAN-Reason-Code Attribute MAY be included within an Access-Reject or Dis= connect-Request packet. Upon receipt of an Access-Reject packet, the WLAN-= Reason-Code value is copied by the Authenticator / AP into the Reason code = field of a Disassociation or Deauthentication frame (see clause 8.3.3.4 and= 8.3.3.12 respectively in IEEE 802.11-2012), which is subsequently transmit= ted to the Supplicant / mobile device. A summary of the WLAN-Reason-Code A= ttribute format is shown below. The fields are transmitted from left to ri= ght. = 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 | Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ = Code tbd8 = Length =3D2 = Value The Value field is two octets containing a 16-bit unsigned integer drawn fr= om Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The value=92s least s= ignificant octet is contained in bits 23-16 and most significant octet in b= its 31-24 (network octet order). Note: not all reason codes defined in the= Table 8-36 are expected to be used by an AS. = [Note]: the importance of including this attribute is for authentication an= d authorization of mobile devices in public Wi-Fi access; it is important t= o inform the mobile when authorization is denied, even though authenticatio= n may have been successful. This can occur for AS policy reasons or for re= asons related to the user=92s subscription. The following Reason codes for= public Wi-Fi access networks were added by the IEEE 802.11u-2011 amendment: = Reason Code Value Description 27 Disassociated because session terminated by SP request 28 Disassociated because of lack of SP roaming agreement 29 Requested service rejected because of SP cipher suite or AKM requir= ement 30 Requested service not authorized in this location = = = = 2.10. WLAN-Pairwise-Cipher = Description = The WLAN-Pairwise-Cipher Attribute contains information on the pairwise cip= her suite used to establish the robust security network association (RSNA) = between the AP and mobile device. = A WLAN-Pairwise-Cipher Attribute SHOULD be included within an Access-Reques= t packet. A summary of the WLAN-Pairwise-Cipher 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 | Value = +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ = Code tbd9 = Length =3D4 = Value The Value field is four octets formatted in accordance with Figure 8-187 wi= th values drawn from Table 8-99 of IEEE 802.11-2012. = = = 2.11. WLAN-Group-Cipher = Description = The WLAN-Group-Cipher Attribute contains information on the group cipher su= ite used to establish the robust security network association (RSNA) betwee= n the AP and mobile device. = A WLAN-Group-Cipher Attribute SHOULD be included within an Access-Request p= acket. A summary of the WLAN-Group-Cipher 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 | Value = +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ = Code tbd10 = Length =3D4 = Value The Value field is four octets formatted in accordance with Figure 8-187 wi= th values drawn from Table 8-99 of IEEE 802.11-2012. = = = 2.12. WLAN-AKM-Suite = Description = The WLAN-AKM-Suite Attribute contains information on the authentication and= key management suite used to establish the robust security network associa= tion (RSNA) between the AP and mobile device. = A WLAN-AKM-Suite Attribute SHOULD be included within an Access-Request pack= et. A summary of the WLAN-AKM-Suite 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 | Value = +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ = Code tbd11 = Length =3D4 = Value The Value field is four octets formatted in accordance with Figure 8-187 wi= th values drawn from Table 8-101 of IEEE 802.11-2012. = = = 2.12. WLAN-RF-Band = Description = The WLAN-RF-Band Attribute contains information on the RF band used by the = AP for transmission and reception of information to and from the mobile dev= ice. This information can be used, for example, to provide a relative qual= ity of experience indication for the mobile device=92s user (i.e., some RF = bands have more interference than others). = A WLAN-RF-Band Attribute SHOULD be included within an Access-Request packet= . A summary of the WLAN-RF-Band Attribute format is shown below. The fiel= ds 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 | Value | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ = Code tbd12 = Length =3D2 = Value The Value field is 1 octet having a value chosen from the table below: Band ID value Meaning 0 TV white spaces 1 Sub-1 GHz (excluding TV white spaces) 2 2.4 GHz 3 3.6 GHz 4 4.9 and 5 GHz 5 60 GHz 6-255 Reserved = = [Note]: this table was copied from IEEE 802.11ad-d5. I=92m not sure of the= relative publication dates of this internet draft and IEEE 802.11ad-d5. S= ince it=92s generally not recommended to reference a draft specification in= an RFC, I=92ve copied the table. If we discover that the IEEE document wi= ll be published in time, then we could deleted the table and instead refere= nce Table 8-53a in IEEE 802.11ad. = = _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Tue May 8 14:42:31 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B25D11E8088; Tue, 8 May 2012 14:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336513351; bh=Odz2ja0MsguguxhHuQirRi808LR4ZSmhtdkLTcxwcjk=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=KTIOWRDTqHuvPDMTiaUY/PfOkLd7Ggu7XJLsAgC/5YBcGFe9h5iByLSzy4aLz2GSB TbHpYVeyKF15wO7XC5l7jpZD7TIK2L0BV3+hRcT/fsk4Awp5AmX/FP4dDZ83Q0FDbt in5ckauGSWU3Srtvk6nsy4pLqUdIvb1rn785aYEE= 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 8836611E8087 for ; Tue, 8 May 2012 14:42:30 -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=[AWL=0.000, 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 8SSDKodYrnzO for ; Tue, 8 May 2012 14:42:29 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7D92611E8085 for ; Tue, 8 May 2012 14:42:29 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRsAm-0002zT-7Z; Tue, 08 May 2012 17:42:20 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: bernard_aboba@hotmail.com, jsalowey@cisco.com X-Trac-Project: radext Date: Tue, 08 May 2012 21:42:20 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/109 Message-ID: <059.c3a1bc8c14e150831b18a5e69f571d5e@trac.tools.ietf.org> X-Trac-Ticket-ID: 109 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: 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 gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #109: Additional IEEE 802.11 Attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEwOTogQWRkaXRpb25hbCBJRUVFIDgwMi4xMSBBdHRyaWJ1dGVzCgogSSd2ZSByZWNlaXZlZCBh IGZldyBvZmYgbGlzdCBzdWdnZXN0aW9ucyBmb3IgYWRkaXRpb25hbCBSQURJVVMgYXR0cmlidXRl cwogdG8gYWRkIHRvIFJBRElVUyBBdHRyaWJ1dGVzIGZvciBJRUVFIDgwMiBOZXR3b3Jrcy4gIFRo ZXNlIGluY2x1ZGUKCiAxLiAgIFdMQU4tUmVhc29uLUNvZGUgIC0gdXNlZCB0byB0cmFuc21pdCB0 aGUgcmVhc29uIGZvciBhdXRoZW50aWNhdGlvbgogZmFpbHVyZSBmcm9tIEFBQSB0byBBUCBpbiBh biBBY2Nlc3MtUmVqZWN0LiAgVGhlIGNvZGUgaXMgaW5jbHVkZWQgaW4KIHJlYXNvbiBjb2RlIG9m IGEgRGlzYXNzb2NpYXRpb24gb3IgRGUtYXV0aGVudGljYXRpb24gRnJhbWUKIDIuICAgV0xBTi1Q YWlyd2lzZS1DaXBoZXIgLSBjb21tdW5pY2F0ZXMgdGhlIG5lZ290aWF0ZWQgcGFpcndpc2UgY2lw aGVyCiBmcm9tIHRoZSBBUCB0byB0aGUgQUFBLgogMy4gIFdMQU4tR3JvdXAtQ2lwaGVyIC0gY29t bXVuaWNhdGVzIHRoZSBuZWdvdGlhdGVkIGdyb3VwIGNpcGhlciBmcm9tIHRoZQogQVAgdG8gdGhl IEFBQS4KIDQuICBXTEFOLUFLTS1TdWl0ZSAtIGNvbnRhaW5zIGluZm9ybWF0aW9uIG9uIHRoZSBh dXRoZW50aWNhdGlvbiBhbmQga2V5CiBtYW5hZ2VtZW50IHN1aXRlIG5lZ290aWF0ZWQgYnV5IHRo ZSBBUC4KIDUuICBXTEFOLVJGLUJhbmQgLSBjb250YWlucyBpbmZvcm1hdGlvbiBvbiB0aGUgUkYg YmFuZCB1c2VkIGJ5IHRoZSBBUC4KCiBCZWxvdyBpcyBzdWdnZXN0ZWQgdGV4dCBmb3IgdGhlc2Ug YXR0cmlidXRlcyBmcm9tIERhdmUgU3RlcGhlbnNvbjoKCiBUaGFua3MsCgogSm9lCgogMi45LiAg V0xBTi1SZWFzb24tQ29kZQoKIERlc2NyaXB0aW9uCgogVGhlIFdMQU4tUmVhc29uLUNvZGUgQXR0 cmlidXRlIGNvbnRhaW5zIGluZm9ybWF0aW9uIG9uIHRoZSByZWFzb24gZm9yCiBhdXRob3JpemF0 aW9uIGZhaWx1cmUgc3Vic2VxdWVudCB0byBhIG1vYmlsZSBkZXZpY2XigJlzIGF1dGhlbnRpY2F0 aW9uCiByZXF1ZXN0IHRvd2FyZHMgYSBXaS1GaSBhY2Nlc3MgbmV0d29yay4KCiBBIFdMQU4tUmVh c29uLUNvZGUgQXR0cmlidXRlIE1BWSBiZSBpbmNsdWRlZCB3aXRoaW4gYW4gQWNjZXNzLVJlamVj dCBvcgogRGlzY29ubmVjdC1SZXF1ZXN0IHBhY2tldC4gIFVwb24gcmVjZWlwdCBvZiBhbiBBY2Nl c3MtUmVqZWN0IHBhY2tldCwgdGhlCiBXTEFOLVJlYXNvbi1Db2RlIHZhbHVlIGlzIGNvcGllZCBi eSB0aGUgQXV0aGVudGljYXRvciAvIEFQIGludG8gdGhlIFJlYXNvbgogY29kZSBmaWVsZCBvZiBh IERpc2Fzc29jaWF0aW9uIG9yIERlYXV0aGVudGljYXRpb24gZnJhbWUgKHNlZSBjbGF1c2UKIDgu My4zLjQgYW5kIDguMy4zLjEyIHJlc3BlY3RpdmVseSBpbiBJRUVFIDgwMi4xMS0yMDEyKSwgd2hp Y2ggaXMKIHN1YnNlcXVlbnRseSB0cmFuc21pdHRlZCB0byB0aGUgU3VwcGxpY2FudCAvIG1vYmls ZSBkZXZpY2UuICBBIHN1bW1hcnkgb2YKIHRoZSBXTEFOLVJlYXNvbi1Db2RlIEF0dHJpYnV0ZSBm b3JtYXQgaXMgc2hvd24gYmVsb3cuICBUaGUgZmllbGRzIGFyZQogdHJhbnNtaXR0ZWQgZnJvbSBs ZWZ0IHRvIHJpZ2h0LgoKICAgMCAgICAgICAgICAgICAgICAgICAxICAgICAgICAgICAgICAgICAg IDIgICAgICAgICAgICAgICAgICAgMwogICAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1 IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEKICArLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKwogIHwgICAgIFR5cGUg ICAgICB8ICBMZW5ndGggICAgICAgfCAgICAgICAgICAgICBWYWx1ZSAgICAgICAgICAgICB8CiAg Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r LSstKy0rLSsKCiBDb2RlCiAgdGJkOAoKIExlbmd0aAogID0yCgogVmFsdWUKIFRoZSBWYWx1ZSBm aWVsZCBpcyB0d28gb2N0ZXRzIGNvbnRhaW5pbmcgYSAxNi1iaXQgdW5zaWduZWQgaW50ZWdlciBk cmF3bgogZnJvbSBUYWJsZSA4LTM2IGluIGNsYXVzZSA4LjQuMS43IG9mIElFRUUgODAyLjExLTIw MTIuICBUaGUgdmFsdWXigJlzIGxlYXN0CiBzaWduaWZpY2FudCBvY3RldCBpcyBjb250YWluZWQg aW4gYml0cyAyMy0xNiBhbmQgbW9zdCBzaWduaWZpY2FudCBvY3RldCBpbgogYml0cyAzMS0yNCAo bmV0d29yayBvY3RldCBvcmRlcikuICBOb3RlOiBub3QgYWxsIHJlYXNvbiBjb2RlcyBkZWZpbmVk IGluCiB0aGUgVGFibGUgOC0zNiBhcmUgZXhwZWN0ZWQgdG8gYmUgdXNlZCBieSBhbiBBUy4KCiBb Tm90ZV06IHRoZSBpbXBvcnRhbmNlIG9mIGluY2x1ZGluZyB0aGlzIGF0dHJpYnV0ZSBpcyBmb3Ig YXV0aGVudGljYXRpb24KIGFuZCBhdXRob3JpemF0aW9uIG9mIG1vYmlsZSBkZXZpY2VzIGluIHB1 YmxpYyBXaS1GaSBhY2Nlc3M7IGl0IGlzCiBpbXBvcnRhbnQgdG8gaW5mb3JtIHRoZSBtb2JpbGUg d2hlbiBhdXRob3JpemF0aW9uIGlzIGRlbmllZCwgZXZlbiB0aG91Z2gKIGF1dGhlbnRpY2F0aW9u IG1heSBoYXZlIGJlZW4gc3VjY2Vzc2Z1bC4gIFRoaXMgY2FuIG9jY3VyIGZvciBBUyBwb2xpY3kK IHJlYXNvbnMgb3IgZm9yIHJlYXNvbnMgcmVsYXRlZCB0byB0aGUgdXNlcuKAmXMgc3Vic2NyaXB0 aW9uLiAgVGhlIGZvbGxvd2luZwogUmVhc29uIGNvZGVzIGZvciBwdWJsaWMgV2ktRmkgYWNjZXNz IG5ldHdvcmtzIHdlcmUgYWRkZWQgYnkgdGhlIElFRUUKIDgwMi4xMXUtMjAxMSBhbWVuZG1lbnQ6 CgogUmVhc29uCiAgQ29kZQogIFZhbHVlICAgRGVzY3JpcHRpb24KIDI3ICAgICAgRGlzYXNzb2Np YXRlZCBiZWNhdXNlIHNlc3Npb24gdGVybWluYXRlZCBieSBTUCByZXF1ZXN0CiAyOCAgICAgIERp c2Fzc29jaWF0ZWQgYmVjYXVzZSBvZiBsYWNrIG9mIFNQIHJvYW1pbmcgYWdyZWVtZW50CiAyOSAg ICAgIFJlcXVlc3RlZCBzZXJ2aWNlIHJlamVjdGVkIGJlY2F1c2Ugb2YgU1AgY2lwaGVyIHN1aXRl IG9yIEFLTQogcmVxdWlyZW1lbnQKIDMwICAgICAgUmVxdWVzdGVkIHNlcnZpY2Ugbm90IGF1dGhv cml6ZWQgaW4gdGhpcyBsb2NhdGlvbgoKCgoKIDIuMTAuICBXTEFOLVBhaXJ3aXNlLUNpcGhlcgoK IERlc2NyaXB0aW9uCgogVGhlIFdMQU4tUGFpcndpc2UtQ2lwaGVyIEF0dHJpYnV0ZSBjb250YWlu cyBpbmZvcm1hdGlvbiBvbiB0aGUgcGFpcndpc2UKIGNpcGhlciBzdWl0ZSB1c2VkIHRvIGVzdGFi bGlzaCB0aGUgcm9idXN0IHNlY3VyaXR5IG5ldHdvcmsgYXNzb2NpYXRpb24KIChSU05BKSBiZXR3 ZWVuIHRoZSBBUCBhbmQgbW9iaWxlIGRldmljZS4KCiBBIFdMQU4tUGFpcndpc2UtQ2lwaGVyIEF0 dHJpYnV0ZSBTSE9VTEQgYmUgaW5jbHVkZWQgd2l0aGluIGFuIEFjY2Vzcy0KIFJlcXVlc3QgcGFj a2V0LiAgQSBzdW1tYXJ5IG9mIHRoZSBXTEFOLVBhaXJ3aXNlLUNpcGhlciBBdHRyaWJ1dGUgZm9y bWF0IGlzCiBzaG93biBiZWxvdy4gIFRoZSBmaWVsZHMgYXJlIHRyYW5zbWl0dGVkIGZyb20gbGVm dCB0byByaWdodC4KCiAgIDAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAy ICAgICAgICAgICAgICAgICAgIDMKICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2 IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxCiAgKy0rLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKICB8ICAgICBUeXBlICAg ICAgfCAgTGVuZ3RoICAgICAgIHwgICAgICAgICAgICAgVmFsdWUKICArLSstKy0rLSstKy0rLSst Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKwogICAgICAg ICAgICAgVmFsdWUgICAgICAgICAgICAgICAgfAogICstKy0rLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSstKwoKIENvZGUKICB0YmQ5CgogTGVuZ3RoCiAgPTQKCiBWYWx1ZQogVGhlIFZhbHVlIGZp ZWxkIGlzIGZvdXIgb2N0ZXRzIGZvcm1hdHRlZCBpbiBhY2NvcmRhbmNlIHdpdGggRmlndXJlIDgt MTg3CiB3aXRoIHZhbHVlcyBkcmF3biBmcm9tIFRhYmxlIDgtOTkgb2YgSUVFRSA4MDIuMTEtMjAx Mi4KCgoKCiAyLjExLiAgV0xBTi1Hcm91cC1DaXBoZXIKCiBEZXNjcmlwdGlvbgoKIFRoZSBXTEFO LUdyb3VwLUNpcGhlciBBdHRyaWJ1dGUgY29udGFpbnMgaW5mb3JtYXRpb24gb24gdGhlIGdyb3Vw IGNpcGhlcgogc3VpdGUgdXNlZCB0byBlc3RhYmxpc2ggdGhlIHJvYnVzdCBzZWN1cml0eSBuZXR3 b3JrIGFzc29jaWF0aW9uIChSU05BKQogYmV0d2VlbiB0aGUgQVAgYW5kIG1vYmlsZSBkZXZpY2Uu CgogQSBXTEFOLUdyb3VwLUNpcGhlciBBdHRyaWJ1dGUgU0hPVUxEIGJlIGluY2x1ZGVkIHdpdGhp biBhbiBBY2Nlc3MtUmVxdWVzdAogcGFja2V0LiAgQSBzdW1tYXJ5IG9mIHRoZSBXTEFOLUdyb3Vw LUNpcGhlciBBdHRyaWJ1dGUgZm9ybWF0IGlzIHNob3duCiBiZWxvdy4gIFRoZSBmaWVsZHMgYXJl IHRyYW5zbWl0dGVkIGZyb20gbGVmdCB0byByaWdodC4KCiAgIDAgICAgICAgICAgICAgICAgICAg MSAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMKICAgMCAxIDIgMyA0IDUg NiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxCiAgKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSsKICB8ICAgICBUeXBlICAgICAgfCAgTGVuZ3RoICAgICAgIHwgICAgICAgICAgICAgVmFs dWUKICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSstKy0rLSstKwogICAgICAgICAgICAgVmFsdWUgICAgICAgICAgICAgICAgfAogICstKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKwoKIENvZGUKICB0YmQxMAoKIExlbmd0aAogID00 CgogVmFsdWUKIFRoZSBWYWx1ZSBmaWVsZCBpcyBmb3VyIG9jdGV0cyBmb3JtYXR0ZWQgaW4gYWNj b3JkYW5jZSB3aXRoIEZpZ3VyZSA4LTE4Nwogd2l0aCB2YWx1ZXMgZHJhd24gZnJvbSBUYWJsZSA4 LTk5IG9mIElFRUUgODAyLjExLTIwMTIuCgoKCgogMi4xMi4gIFdMQU4tQUtNLVN1aXRlCgogRGVz Y3JpcHRpb24KCiBUaGUgV0xBTi1BS00tU3VpdGUgQXR0cmlidXRlIGNvbnRhaW5zIGluZm9ybWF0 aW9uIG9uIHRoZSBhdXRoZW50aWNhdGlvbgogYW5kIGtleSBtYW5hZ2VtZW50IHN1aXRlIHVzZWQg dG8gZXN0YWJsaXNoIHRoZSByb2J1c3Qgc2VjdXJpdHkgbmV0d29yawogYXNzb2NpYXRpb24gKFJT TkEpIGJldHdlZW4gdGhlIEFQIGFuZCBtb2JpbGUgZGV2aWNlLgoKIEEgV0xBTi1BS00tU3VpdGUg QXR0cmlidXRlIFNIT1VMRCBiZSBpbmNsdWRlZCB3aXRoaW4gYW4gQWNjZXNzLVJlcXVlc3QKIHBh Y2tldC4gIEEgc3VtbWFyeSBvZiB0aGUgV0xBTi1BS00tU3VpdGUgQXR0cmlidXRlIGZvcm1hdCBp cyBzaG93biBiZWxvdy4KIFRoZSBmaWVsZHMgYXJlIHRyYW5zbWl0dGVkIGZyb20gbGVmdCB0byBy aWdodC4KCiAgIDAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAyICAgICAg ICAgICAgICAgICAgIDMKICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5 IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxCiAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKICB8ICAgICBUeXBlICAgICAgfCAg TGVuZ3RoICAgICAgIHwgICAgICAgICAgICAgVmFsdWUKICArLSstKy0rLSstKy0rLSstKy0rLSst Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKwogICAgICAgICAgICAg VmFsdWUgICAgICAgICAgICAgICAgfAogICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst KwoKIENvZGUKICB0YmQxMQoKIExlbmd0aAogID00CgogVmFsdWUKIFRoZSBWYWx1ZSBmaWVsZCBp cyBmb3VyIG9jdGV0cyBmb3JtYXR0ZWQgaW4gYWNjb3JkYW5jZSB3aXRoIEZpZ3VyZSA4LTE4Nwog d2l0aCB2YWx1ZXMgZHJhd24gZnJvbSBUYWJsZSA4LTEwMSBvZiBJRUVFIDgwMi4xMS0yMDEyLgoK CgoKIDIuMTIuICBXTEFOLVJGLUJhbmQKCiBEZXNjcmlwdGlvbgoKIFRoZSBXTEFOLVJGLUJhbmQg QXR0cmlidXRlIGNvbnRhaW5zIGluZm9ybWF0aW9uIG9uIHRoZSBSRiBiYW5kIHVzZWQgYnkgdGhl CiBBUCBmb3IgdHJhbnNtaXNzaW9uIGFuZCByZWNlcHRpb24gb2YgaW5mb3JtYXRpb24gdG8gYW5k IGZyb20gdGhlIG1vYmlsZQogZGV2aWNlLiAgVGhpcyBpbmZvcm1hdGlvbiBjYW4gYmUgdXNlZCwg Zm9yIGV4YW1wbGUsIHRvIHByb3ZpZGUgYSByZWxhdGl2ZQogcXVhbGl0eSBvZiBleHBlcmllbmNl IGluZGljYXRpb24gZm9yIHRoZSBtb2JpbGUgZGV2aWNl4oCZcyB1c2VyIChpLmUuLCBzb21lCiBS RiBiYW5kcyBoYXZlIG1vcmUgaW50ZXJmZXJlbmNlIHRoYW4gb3RoZXJzKS4KCiBBIFdMQU4tUkYt QmFuZCBBdHRyaWJ1dGUgU0hPVUxEIGJlIGluY2x1ZGVkIHdpdGhpbiBhbiBBY2Nlc3MtUmVxdWVz dAogcGFja2V0LiAgQSBzdW1tYXJ5IG9mIHRoZSBXTEFOLVJGLUJhbmQgQXR0cmlidXRlIGZvcm1h dCBpcyBzaG93biBiZWxvdy4KIFRoZSBmaWVsZHMgYXJlIHRyYW5zbWl0dGVkIGZyb20gbGVmdCB0 byByaWdodC4KCiAgIDAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAyICAg ICAgICAgICAgICAgICAgIDMKICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcg OCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxCiAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKICB8ICAgICBUeXBlICAgICAg fCAgTGVuZ3RoICAgICAgIHwgICAgIFZhbHVlICAgICB8ICAgUmVzZXJ2ZWQgICAgfAogICstKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst Ky0rCgogQ29kZQogIHRiZDEyCgogTGVuZ3RoCiAgPTIKCiBWYWx1ZQogVGhlIFZhbHVlIGZpZWxk IGlzIDEgb2N0ZXQgaGF2aW5nIGEgdmFsdWUgY2hvc2VuIGZyb20gdGhlIHRhYmxlIGJlbG93Ogog QmFuZCBJRCB2YWx1ZSAgICAgTWVhbmluZwogICAgICAgMCAgICAgICAgICAgVFYgd2hpdGUgc3Bh Y2VzCiAgICAgICAxICAgICAgICAgICBTdWItMSBHSHogKGV4Y2x1ZGluZyBUViB3aGl0ZSBzcGFj ZXMpCiAgICAgICAyICAgICAgICAgICAyLjQgR0h6CiAgICAgICAzICAgICAgICAgICAzLjYgR0h6 CiAgICAgICA0ICAgICAgICAgICA0LjkgYW5kIDUgR0h6CiAgICAgICA1ICAgICAgICAgICA2MCBH SHoKICAgICAgIDYtMjU1ICAgICAgIFJlc2VydmVkCgoKIFtOb3RlXTogdGhpcyB0YWJsZSB3YXMg Y29waWVkIGZyb20gSUVFRSA4MDIuMTFhZC1kNS4gIEnigJltIG5vdCBzdXJlIG9mIHRoZQogcmVs YXRpdmUgcHVibGljYXRpb24gZGF0ZXMgb2YgdGhpcyBpbnRlcm5ldCBkcmFmdCBhbmQgSUVFRSA4 MDIuMTFhZC1kNS4KIFNpbmNlIGl04oCZcyBnZW5lcmFsbHkgbm90IHJlY29tbWVuZGVkIHRvIHJl ZmVyZW5jZSBhIGRyYWZ0IHNwZWNpZmljYXRpb24gaW4KIGFuIFJGQywgSeKAmXZlIGNvcGllZCB0 aGUgdGFibGUuICBJZiB3ZSBkaXNjb3ZlciB0aGF0IHRoZSBJRUVFIGRvY3VtZW50IHdpbGwKIGJl IHB1Ymxpc2hlZCBpbiB0aW1lLCB0aGVuIHdlIGNvdWxkIGRlbGV0ZWQgdGhlIHRhYmxlIGFuZCBp bnN0ZWFkCiByZWZlcmVuY2UgVGFibGUgOC01M2EgaW4gSUVFRSA4MDIuMTFhZC4KCi0tIAotLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQog UmVwb3J0ZXI6ICBqc2Fsb3dleUDigKYgICAgICAgfCAgICAgIE93bmVyOiAgYmVybmFyZF9hYm9i YUDigKYKICAgICBUeXBlOiAgZGVmZWN0ICAgICAgICAgICB8ICAgICBTdGF0dXM6ICBuZXcKIFBy aW9yaXR5OiAgbWFqb3IgICAgICAgICAgICB8ICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCkNvbXBv bmVudDogIGllZWU4MDJleHQgICAgICAgfCAgICBWZXJzaW9uOiAgMS4wCiBTZXZlcml0eTogIElu IFdHIExhc3QgQ2FsbCAgfCAgIEtleXdvcmRzOgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFj LnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMDk+CnJhZGV4dCA8aHR0cDov L3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRw czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Tue May 8 14:42:30 2012 Return-Path: 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 8836611E8087 for ; Tue, 8 May 2012 14:42:30 -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=[AWL=0.000, 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 8SSDKodYrnzO for ; Tue, 8 May 2012 14:42:29 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7D92611E8085 for ; Tue, 8 May 2012 14:42:29 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRsAm-0002zT-7Z; Tue, 08 May 2012 17:42:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: bernard_aboba@hotmail.com, jsalowey@cisco.com X-Trac-Project: radext Date: Tue, 08 May 2012 21:42:20 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/109 Message-ID: <059.c3a1bc8c14e150831b18a5e69f571d5e@trac.tools.ietf.org> X-Trac-Ticket-ID: 109 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: 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 gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #109: Additional IEEE 802.11 Attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 21:42:30 -0000 #109: Additional IEEE 802.11 Attributes I've received a few off list suggestions for additional RADIUS attributes to add to RADIUS Attributes for IEEE 802 Networks. These include 1. WLAN-Reason-Code - used to transmit the reason for authentication failure from AAA to AP in an Access-Reject. The code is included in reason code of a Disassociation or De-authentication Frame 2. WLAN-Pairwise-Cipher - communicates the negotiated pairwise cipher from the AP to the AAA. 3. WLAN-Group-Cipher - communicates the negotiated group cipher from the AP to the AAA. 4. WLAN-AKM-Suite - contains information on the authentication and key management suite negotiated buy the AP. 5. WLAN-RF-Band - contains information on the RF band used by the AP. Below is suggested text for these attributes from Dave Stephenson: Thanks, Joe 2.9. WLAN-Reason-Code Description The WLAN-Reason-Code Attribute contains information on the reason for authorization failure subsequent to a mobile device’s authentication request towards a Wi-Fi access network. A WLAN-Reason-Code Attribute MAY be included within an Access-Reject or Disconnect-Request packet. Upon receipt of an Access-Reject packet, the WLAN-Reason-Code value is copied by the Authenticator / AP into the Reason code field of a Disassociation or Deauthentication frame (see clause 8.3.3.4 and 8.3.3.12 respectively in IEEE 802.11-2012), which is subsequently transmitted to the Supplicant / mobile device. A summary of the WLAN-Reason-Code 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 | Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code tbd8 Length =2 Value The Value field is two octets containing a 16-bit unsigned integer drawn from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The value’s least significant octet is contained in bits 23-16 and most significant octet in bits 31-24 (network octet order). Note: not all reason codes defined in the Table 8-36 are expected to be used by an AS. [Note]: the importance of including this attribute is for authentication and authorization of mobile devices in public Wi-Fi access; it is important to inform the mobile when authorization is denied, even though authentication may have been successful. This can occur for AS policy reasons or for reasons related to the user’s subscription. The following Reason codes for public Wi-Fi access networks were added by the IEEE 802.11u-2011 amendment: Reason Code Value Description 27 Disassociated because session terminated by SP request 28 Disassociated because of lack of SP roaming agreement 29 Requested service rejected because of SP cipher suite or AKM requirement 30 Requested service not authorized in this location 2.10. WLAN-Pairwise-Cipher Description The WLAN-Pairwise-Cipher Attribute contains information on the pairwise cipher suite used to establish the robust security network association (RSNA) between the AP and mobile device. A WLAN-Pairwise-Cipher Attribute SHOULD be included within an Access- Request packet. A summary of the WLAN-Pairwise-Cipher 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 | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code tbd9 Length =4 Value The Value field is four octets formatted in accordance with Figure 8-187 with values drawn from Table 8-99 of IEEE 802.11-2012. 2.11. WLAN-Group-Cipher Description The WLAN-Group-Cipher Attribute contains information on the group cipher suite used to establish the robust security network association (RSNA) between the AP and mobile device. A WLAN-Group-Cipher Attribute SHOULD be included within an Access-Request packet. A summary of the WLAN-Group-Cipher 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 | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code tbd10 Length =4 Value The Value field is four octets formatted in accordance with Figure 8-187 with values drawn from Table 8-99 of IEEE 802.11-2012. 2.12. WLAN-AKM-Suite Description The WLAN-AKM-Suite Attribute contains information on the authentication and key management suite used to establish the robust security network association (RSNA) between the AP and mobile device. A WLAN-AKM-Suite Attribute SHOULD be included within an Access-Request packet. A summary of the WLAN-AKM-Suite 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 | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code tbd11 Length =4 Value The Value field is four octets formatted in accordance with Figure 8-187 with values drawn from Table 8-101 of IEEE 802.11-2012. 2.12. WLAN-RF-Band Description The WLAN-RF-Band Attribute contains information on the RF band used by the AP for transmission and reception of information to and from the mobile device. This information can be used, for example, to provide a relative quality of experience indication for the mobile device’s user (i.e., some RF bands have more interference than others). A WLAN-RF-Band Attribute SHOULD be included within an Access-Request packet. A summary of the WLAN-RF-Band 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 | Value | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code tbd12 Length =2 Value The Value field is 1 octet having a value chosen from the table below: Band ID value Meaning 0 TV white spaces 1 Sub-1 GHz (excluding TV white spaces) 2 2.4 GHz 3 3.6 GHz 4 4.9 and 5 GHz 5 60 GHz 6-255 Reserved [Note]: this table was copied from IEEE 802.11ad-d5. I’m not sure of the relative publication dates of this internet draft and IEEE 802.11ad-d5. Since it’s generally not recommended to reference a draft specification in an RFC, I’ve copied the table. If we discover that the IEEE document will be published in time, then we could deleted the table and instead reference Table 8-53a in IEEE 802.11ad. -- -----------------------------+----------------------------- Reporter: jsalowey@… | Owner: bernard_aboba@… Type: defect | Status: new Priority: major | Milestone: milestone1 Component: ieee802ext | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+----------------------------- Ticket URL: radext From radext-bounces@ietf.org Tue May 8 14:43:17 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBA411E8074; Tue, 8 May 2012 14:43:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336513397; bh=Cz4QXm4ZO5oEov25XaUbp4+QcPy5WFs3LcipJfdwlwE=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To:Cc: Subject:Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:Content-Type:Content-Transfer-Encoding: Sender; b=hQOTheHrwrwNpVkM3gSj/BmJcOV4zOLM2FT4mY9g+MiJG/I9bEFmbJqqwgo/O7psf C2z5+bd6aO/DyxNFiHZtoC4dclTXj5DXb/zGeTnX+nCre3t+kC6lC+73UAymkD5cn6 l+3ZBZhBSD9xD9po9rYvnp7uitVgU9rUfWA87Lgo= 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 DF1FB11E8074 for ; Tue, 8 May 2012 14:43:16 -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=[AWL=0.000, 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 qZujTqIK-YXB for ; Tue, 8 May 2012 14:43:16 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7C711E8072 for ; Tue, 8 May 2012 14:43:16 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRsBd-0004Dz-Nz; Tue, 08 May 2012 17:43:13 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: Bernard_Aboba@hotmail.com, j@w1.fi X-Trac-Project: radext Date: Tue, 08 May 2012 21:43:13 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/108#comment:2 Message-ID: <079.fd022fc20c59528420babd7dbad6eda1@trac.tools.ietf.org> References: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-Trac-Ticket-ID: 108 In-Reply-To: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: Bernard_Aboba@hotmail.com, j@w1.fi, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #108: Incorrect author email address X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEwODogSW5jb3JyZWN0IGF1dGhvciBlbWFpbCBhZGRyZXNzCgpDaGFuZ2VzIChieSBCZXJuYXJk X0Fib2JhQOKApik6CgogKiBvd25lcjogICA9PiBCZXJuYXJkX0Fib2JhQOKApgogKiBjb21wb25l bnQ6ICBJRUVFODAyLUF0dHJzID0+IGllZWU4MDJleHQKCgotLSAKLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBvcnRlcjog IG1hdXJpY2lvLnNhbmNoZXpA4oCmICB8ICAgICAgIE93bmVyOiAgQmVybmFyZF9BYm9iYUDigKYK ICAgICBUeXBlOiAgZGVmZWN0ICAgICAgICAgICAgICB8ICAgICAgU3RhdHVzOiAgbmV3CiBQcmlv cml0eTogIHRyaXZpYWwgICAgICAgICAgICAgfCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEKQ29t cG9uZW50OiAgaWVlZTgwMmV4dCAgICAgICAgICB8ICAgICBWZXJzaW9uOiAgMS4wCiBTZXZlcml0 eTogIEluIFdHIExhc3QgQ2FsbCAgICAgfCAgUmVzb2x1dGlvbjoKIEtleXdvcmRzOiAgICAgICAg ICAgICAgICAgICAgICB8Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmll dGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMDgjY29tbWVudDoyPgpyYWRleHQgPGh0dHA6 Ly90b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0 cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Tue May 8 14:43:16 2012 Return-Path: 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 DF1FB11E8074 for ; Tue, 8 May 2012 14:43:16 -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=[AWL=0.000, 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 qZujTqIK-YXB for ; Tue, 8 May 2012 14:43:16 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7C711E8072 for ; Tue, 8 May 2012 14:43:16 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SRsBd-0004Dz-Nz; Tue, 08 May 2012 17:43:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: Bernard_Aboba@hotmail.com, j@w1.fi X-Trac-Project: radext Date: Tue, 08 May 2012 21:43:13 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/108#comment:2 Message-ID: <079.fd022fc20c59528420babd7dbad6eda1@trac.tools.ietf.org> References: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-Trac-Ticket-ID: 108 In-Reply-To: <064.1d8d4505097abc88964fe54b7e4846bb@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: Bernard_Aboba@hotmail.com, j@w1.fi, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #108: Incorrect author email address X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 21:43:17 -0000 #108: Incorrect author email address Changes (by Bernard_Aboba@…): * owner: => Bernard_Aboba@… * component: IEEE802-Attrs => ieee802ext -- --------------------------------+------------------------------ Reporter: mauricio.sanchez@… | Owner: Bernard_Aboba@… Type: defect | Status: new Priority: trivial | Milestone: milestone1 Component: ieee802ext | Version: 1.0 Severity: In WG Last Call | Resolution: Keywords: | --------------------------------+------------------------------ Ticket URL: radext From j@w1.fi Tue May 8 15:35:35 2012 Return-Path: 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 814A921F8495 for ; Tue, 8 May 2012 15:35:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 SZArPo93w4eM for ; Tue, 8 May 2012 15:35:35 -0700 (PDT) Received: from jmaline2.user.openhosting.com (kvm.w1.fi [128.177.28.162]) by ietfa.amsl.com (Postfix) with ESMTP id E0E3F21F84D9 for ; Tue, 8 May 2012 15:35:34 -0700 (PDT) Received: from jm (a91-155-81-182.elisa-laajakaista.fi [91.155.81.182]) (authenticated bits=0) by jmaline2.user.openhosting.com (8.13.8/8.13.8) with ESMTP id q48MYJjZ030205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 May 2012 18:34:20 -0400 Received: by jm (sSMTP sendmail emulation); Wed, 09 May 2012 01:35:21 +0300 Date: Wed, 9 May 2012 01:35:21 +0300 From: Jouni Malinen To: Joe Salowey Message-ID: <20120508223521.GA20470@w1.fi> References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 22:35:35 -0000 > 2.9. WLAN-Reason-Code > A summary of the WLAN-Reason-Code 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 | Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > The Value field is two octets containing a 16-bit unsigned integer drawn from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The value’s least significant octet is contained in bits 23-16 and most significant octet in bits 31-24 (network octet order). Note: not all reason codes defined in the Table 8-36 are expected to be used by an AS. Hmm.. Is this really suggesting a RADIUS attribute that is using little endian byte order? Aren't pretty pretty much all other RADIUS attributes defined using big endian byte order? While I can understand that this comes from the IEEE 802.11 side where the Reason Code is indeed little endian, this type of difference between RADIUS attributes is just asking for issues.. > [Note]: the importance of including this attribute is for authentication and authorization of mobile devices in public Wi-Fi access; it is important to inform the mobile when authorization is denied, even though authentication may have been successful. This can occur for AS policy reasons or for reasons related to the user’s subscription. The following Reason codes for public Wi-Fi access networks were added by the IEEE 802.11u-2011 amendment: That IEEE 802.11u-2011 reference should be replaced with a reference to IEEE Std 802.11-2012. > Reason > Value Description > 27 Disassociated because session terminated by SP request > 28 Disassociated because of lack of SP roaming agreement > 29 Requested service rejected because of SP cipher suite or AKM requirement > 30 Requested service not authorized in this location Is Reason Code the best place for sending this information? It is a bit difficult to extend this with any new potentially needed value while something like EAP notifications could be work better for this. > 2.10. WLAN-Pairwise-Cipher > > Description > > The WLAN-Pairwise-Cipher Attribute contains information on the pairwise cipher suite used to establish the robust security network association (RSNA) between the AP and mobile device. > > A WLAN-Pairwise-Cipher Attribute SHOULD be included within an Access-Request packet. A summary of the WLAN-Pairwise-Cipher Attribute format is shown below. The fields are transmitted from left to right. Is there some general text pointing out that these attributes are applicable only for the case of IEEE 802.11 networks? This SHOULD statement could be interpreted as a strong recommendation for any NAS to include the attribute while it should really only apply to the case where the connection is an IEEE 802.11 RSNA. > 2.11. WLAN-Group-Cipher > > Description > > The WLAN-Group-Cipher Attribute contains information on the group cipher suite used to establish the robust security network association (RSNA) between the AP and mobile device. If we are adding this, we could as well add WLAN-Group-Mgmt-Cipher from IEEE 802.11w (now in IEEE Std 802.11-2012) to cover the case of protected management frames. Though, this would also need another attribute to indicate whether the station negotiated use of the mechanism. -- Jouni Malinen PGP id EFC895FA From radext-bounces@ietf.org Tue May 8 15:35:37 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24A1F21F84D9; Tue, 8 May 2012 15:35:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336516537; bh=DLa4fu2RjIUn0LBoPGgpZx/n3w1Ky4pVIKbP8RU6fsI=; h=Date:From:To:Message-ID:References:MIME-Version:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=vEaWFVOt2/Z6c3dDuIyZpzLCEa5Ukqenspfm/vI3RPcdSIzRIUdtL8NCKhb7vOwoy DiFENdooSNDx4iTy+jvB0XzrxAELjj01jIFo582KRNYosiwWdkp5JqEGQd9cmTkChg YiZzeZUgCe7HO5gEsMp1lMuehY/t7iBN6+2/e03E= 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 814A921F8495 for ; Tue, 8 May 2012 15:35:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 SZArPo93w4eM for ; Tue, 8 May 2012 15:35:35 -0700 (PDT) Received: from jmaline2.user.openhosting.com (kvm.w1.fi [128.177.28.162]) by ietfa.amsl.com (Postfix) with ESMTP id E0E3F21F84D9 for ; Tue, 8 May 2012 15:35:34 -0700 (PDT) Received: from jm (a91-155-81-182.elisa-laajakaista.fi [91.155.81.182]) (authenticated bits=0) by jmaline2.user.openhosting.com (8.13.8/8.13.8) with ESMTP id q48MYJjZ030205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 May 2012 18:34:20 -0400 Received: by jm (sSMTP sendmail emulation); Wed, 09 May 2012 01:35:21 +0300 Date: Wed, 9 May 2012 01:35:21 +0300 From: Jouni Malinen To: Joe Salowey Message-ID: <20120508223521.GA20470@w1.fi> References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org PiAyLjkuICBXTEFOLVJlYXNvbi1Db2RlCgo+IEEgc3VtbWFyeSBvZiB0aGUgV0xBTi1SZWFzb24t Q29kZSBBdHRyaWJ1dGUgZm9ybWF0IGlzIHNob3duIGJlbG93LiAgVGhlIGZpZWxkcyBhcmUgdHJh bnNtaXR0ZWQgZnJvbSBsZWZ0IHRvIHJpZ2h0Lgo+ICAKPiAgIDAgICAgICAgICAgICAgICAgICAg MSAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMgCj4gICAwIDEgMiAzIDQg NSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEKPiAg Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r LSstKy0rLSsKPiAgfCAgICAgVHlwZSAgICAgIHwgIExlbmd0aCAgICAgICB8ICAgICAgICAgICAg IFZhbHVlICAgICAgICAgICAgIHwKPiAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKCj4gVGhlIFZhbHVlIGZpZWxkIGlzIHR3 byBvY3RldHMgY29udGFpbmluZyBhIDE2LWJpdCB1bnNpZ25lZCBpbnRlZ2VyIGRyYXduIGZyb20g VGFibGUgOC0zNiBpbiBjbGF1c2UgOC40LjEuNyBvZiBJRUVFIDgwMi4xMS0yMDEyLiAgVGhlIHZh bHVl4oCZcyBsZWFzdCBzaWduaWZpY2FudCBvY3RldCBpcyBjb250YWluZWQgaW4gYml0cyAyMy0x NiBhbmQgbW9zdCBzaWduaWZpY2FudCBvY3RldCBpbiBiaXRzIDMxLTI0IChuZXR3b3JrIG9jdGV0 IG9yZGVyKS4gIE5vdGU6IG5vdCBhbGwgcmVhc29uIGNvZGVzIGRlZmluZWQgaW4gdGhlIFRhYmxl IDgtMzYgYXJlIGV4cGVjdGVkIHRvIGJlIHVzZWQgYnkgYW4gQVMuCgpIbW0uLiBJcyB0aGlzIHJl YWxseSBzdWdnZXN0aW5nIGEgUkFESVVTIGF0dHJpYnV0ZSB0aGF0IGlzIHVzaW5nIGxpdHRsZQpl bmRpYW4gYnl0ZSBvcmRlcj8gQXJlbid0IHByZXR0eSBwcmV0dHkgbXVjaCBhbGwgb3RoZXIgUkFE SVVTIGF0dHJpYnV0ZXMKZGVmaW5lZCB1c2luZyBiaWcgZW5kaWFuIGJ5dGUgb3JkZXI/IFdoaWxl IEkgY2FuIHVuZGVyc3RhbmQgdGhhdCB0aGlzCmNvbWVzIGZyb20gdGhlIElFRUUgODAyLjExIHNp ZGUgd2hlcmUgdGhlIFJlYXNvbiBDb2RlIGlzIGluZGVlZCBsaXR0bGUKZW5kaWFuLCB0aGlzIHR5 cGUgb2YgZGlmZmVyZW5jZSBiZXR3ZWVuIFJBRElVUyBhdHRyaWJ1dGVzIGlzIGp1c3QgYXNraW5n CmZvciBpc3N1ZXMuLgoKPiBbTm90ZV06IHRoZSBpbXBvcnRhbmNlIG9mIGluY2x1ZGluZyB0aGlz IGF0dHJpYnV0ZSBpcyBmb3IgYXV0aGVudGljYXRpb24gYW5kIGF1dGhvcml6YXRpb24gb2YgbW9i aWxlIGRldmljZXMgaW4gcHVibGljIFdpLUZpIGFjY2VzczsgaXQgaXMgaW1wb3J0YW50IHRvIGlu Zm9ybSB0aGUgbW9iaWxlIHdoZW4gYXV0aG9yaXphdGlvbiBpcyBkZW5pZWQsIGV2ZW4gdGhvdWdo IGF1dGhlbnRpY2F0aW9uIG1heSBoYXZlIGJlZW4gc3VjY2Vzc2Z1bC4gIFRoaXMgY2FuIG9jY3Vy IGZvciBBUyBwb2xpY3kgcmVhc29ucyBvciBmb3IgcmVhc29ucyByZWxhdGVkIHRvIHRoZSB1c2Vy 4oCZcyBzdWJzY3JpcHRpb24uICBUaGUgZm9sbG93aW5nIFJlYXNvbiBjb2RlcyBmb3IgcHVibGlj IFdpLUZpIGFjY2VzcyBuZXR3b3JrcyB3ZXJlIGFkZGVkIGJ5IHRoZSBJRUVFIDgwMi4xMXUtMjAx MSBhbWVuZG1lbnQ6CgpUaGF0IElFRUUgODAyLjExdS0yMDExIHJlZmVyZW5jZSBzaG91bGQgYmUg cmVwbGFjZWQgd2l0aCBhIHJlZmVyZW5jZSB0bwpJRUVFIFN0ZCA4MDIuMTEtMjAxMi4KCj4gUmVh c29uCj4gIFZhbHVlICAgRGVzY3JpcHRpb24KPiAyNyAgICAgIERpc2Fzc29jaWF0ZWQgYmVjYXVz ZSBzZXNzaW9uIHRlcm1pbmF0ZWQgYnkgU1AgcmVxdWVzdAo+IDI4ICAgICAgRGlzYXNzb2NpYXRl ZCBiZWNhdXNlIG9mIGxhY2sgb2YgU1Agcm9hbWluZyBhZ3JlZW1lbnQKPiAyOSAgICAgIFJlcXVl c3RlZCBzZXJ2aWNlIHJlamVjdGVkIGJlY2F1c2Ugb2YgU1AgY2lwaGVyIHN1aXRlIG9yIEFLTSBy ZXF1aXJlbWVudAo+IDMwICAgICAgUmVxdWVzdGVkIHNlcnZpY2Ugbm90IGF1dGhvcml6ZWQgaW4g dGhpcyBsb2NhdGlvbgoKSXMgUmVhc29uIENvZGUgdGhlIGJlc3QgcGxhY2UgZm9yIHNlbmRpbmcg dGhpcyBpbmZvcm1hdGlvbj8gSXQgaXMgYSBiaXQKZGlmZmljdWx0IHRvIGV4dGVuZCB0aGlzIHdp dGggYW55IG5ldyBwb3RlbnRpYWxseSBuZWVkZWQgdmFsdWUgd2hpbGUKc29tZXRoaW5nIGxpa2Ug RUFQIG5vdGlmaWNhdGlvbnMgY291bGQgYmUgd29yayBiZXR0ZXIgZm9yIHRoaXMuCgo+IDIuMTAu ICBXTEFOLVBhaXJ3aXNlLUNpcGhlcgo+ICAKPiBEZXNjcmlwdGlvbgo+ICAKPiBUaGUgV0xBTi1Q YWlyd2lzZS1DaXBoZXIgQXR0cmlidXRlIGNvbnRhaW5zIGluZm9ybWF0aW9uIG9uIHRoZSBwYWly d2lzZSBjaXBoZXIgc3VpdGUgdXNlZCB0byBlc3RhYmxpc2ggdGhlIHJvYnVzdCBzZWN1cml0eSBu ZXR3b3JrIGFzc29jaWF0aW9uIChSU05BKSBiZXR3ZWVuIHRoZSBBUCBhbmQgbW9iaWxlIGRldmlj ZS4KPiAgCj4gQSBXTEFOLVBhaXJ3aXNlLUNpcGhlciBBdHRyaWJ1dGUgU0hPVUxEIGJlIGluY2x1 ZGVkIHdpdGhpbiBhbiBBY2Nlc3MtUmVxdWVzdCBwYWNrZXQuICBBIHN1bW1hcnkgb2YgdGhlIFdM QU4tUGFpcndpc2UtQ2lwaGVyIEF0dHJpYnV0ZSBmb3JtYXQgaXMgc2hvd24gYmVsb3cuICBUaGUg ZmllbGRzIGFyZSB0cmFuc21pdHRlZCBmcm9tIGxlZnQgdG8gcmlnaHQuCgpJcyB0aGVyZSBzb21l IGdlbmVyYWwgdGV4dCBwb2ludGluZyBvdXQgdGhhdCB0aGVzZSBhdHRyaWJ1dGVzIGFyZQphcHBs aWNhYmxlIG9ubHkgZm9yIHRoZSBjYXNlIG9mIElFRUUgODAyLjExIG5ldHdvcmtzPyBUaGlzIFNI T1VMRApzdGF0ZW1lbnQgY291bGQgYmUgaW50ZXJwcmV0ZWQgYXMgYSBzdHJvbmcgcmVjb21tZW5k YXRpb24gZm9yIGFueSBOQVMgdG8KaW5jbHVkZSB0aGUgYXR0cmlidXRlIHdoaWxlIGl0IHNob3Vs ZCByZWFsbHkgb25seSBhcHBseSB0byB0aGUgY2FzZQp3aGVyZSB0aGUgY29ubmVjdGlvbiBpcyBh biBJRUVFIDgwMi4xMSBSU05BLgoKPiAyLjExLiAgV0xBTi1Hcm91cC1DaXBoZXIKPiAgCj4gRGVz Y3JpcHRpb24KPiAgCj4gVGhlIFdMQU4tR3JvdXAtQ2lwaGVyIEF0dHJpYnV0ZSBjb250YWlucyBp bmZvcm1hdGlvbiBvbiB0aGUgZ3JvdXAgY2lwaGVyIHN1aXRlIHVzZWQgdG8gZXN0YWJsaXNoIHRo ZSByb2J1c3Qgc2VjdXJpdHkgbmV0d29yayBhc3NvY2lhdGlvbiAoUlNOQSkgYmV0d2VlbiB0aGUg QVAgYW5kIG1vYmlsZSBkZXZpY2UuCgpJZiB3ZSBhcmUgYWRkaW5nIHRoaXMsIHdlIGNvdWxkIGFz IHdlbGwgYWRkIFdMQU4tR3JvdXAtTWdtdC1DaXBoZXIgZnJvbQpJRUVFIDgwMi4xMXcgKG5vdyBp biBJRUVFIFN0ZCA4MDIuMTEtMjAxMikgdG8gY292ZXIgdGhlIGNhc2Ugb2YKcHJvdGVjdGVkIG1h bmFnZW1lbnQgZnJhbWVzLiBUaG91Z2gsIHRoaXMgd291bGQgYWxzbyBuZWVkIGFub3RoZXIKYXR0 cmlidXRlIHRvIGluZGljYXRlIHdoZXRoZXIgdGhlIHN0YXRpb24gbmVnb3RpYXRlZCB1c2Ugb2Yg dGhlCm1lY2hhbmlzbS4KCi0tIApKb3VuaSBNYWxpbmVuICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICBQR1AgaWQgRUZDODk1RkEKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0 Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From lionel.morand@orange.com Tue May 8 18:06:38 2012 Return-Path: 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 BFDF911E8080 for ; Tue, 8 May 2012 18:06:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.916 X-Spam-Level: X-Spam-Status: No, score=-6.916 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4] 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 7GmNMBsIK4HB for ; Tue, 8 May 2012 18:06:38 -0700 (PDT) Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id 27FB99E8012 for ; Tue, 8 May 2012 18:06:35 -0700 (PDT) Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C8D6CA4424A; Wed, 9 May 2012 03:08:06 +0200 (CEST) Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id BE8E8A44249; Wed, 9 May 2012 03:08:06 +0200 (CEST) Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 May 2012 03:06:33 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 9 May 2012 03:06:31 +0200 Message-ID: In-Reply-To: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] Additional 802.11 attributes Thread-Index: Ac0tXv7ci+6NEh8KRJ6WQC4M4BuiDAAFtgCw References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> From: To: , X-OriginalArrivalTime: 09 May 2012 01:06:33.0479 (UTC) FILETIME=[F991C970:01CD2D7F] X-Mailman-Approved-At: Wed, 09 May 2012 03:54:13 -0700 Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 01:06:38 -0000 Here are some questions/comments on these proposed attributes. Regards, Lionel 2.9. WLAN-Reason-Code =20 [Lionel] what about reusing Message-Reply attribute in Access-Reject and define additional values for Acct-Terminate-Cause used in Disconnect-Reject (as described in http://tools.ietf.org/html/rfc3580#section-2.1) ? =20 =20 =20 2.10. WLAN-Pairwise-Cipher=20 2.11. WLAN-Group-Cipher 2.12. WLAN-AKM-Suite [Lionel] If my understanding is correct, it is expected that the AAA server could reject the access authorization request based on these attributes describing the existing RSNA between the AP and mobile node. If the resulting RSNA is not suitable for the SP, I'm not sure if that this is something that should/could be managed per user authorization request but rather via local policies or SLA between partners. =20 =20 =20 2.12. WLAN-RF-Band =20 The WLAN-RF-Band Attribute contains information on the RF band used by the AP for transmission and reception of information to and from the mobile device. This information can be used, for example, to provide a relative quality of experience indication for the mobile device's user (i.e., some RF bands have more interference than others). [Lionel] if it is an indication for the user, why is it intended to provide this information to the AAA server? From radext-bounces@ietf.org Wed May 9 03:54:14 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E92521F85BE; Wed, 9 May 2012 03:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336560854; bh=9IJp6h825Svg0TpKXy7MhefrqQX6XsNHXVxN7rBOBes=; h=MIME-Version:Date:Message-ID:In-Reply-To:References:From:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=w+FvdeEQEceQX5TmKhIijcRpOyyYFBGUHLTJr3X2NMtIlvhrB6nodxIh67xf8atGQ vZIbNQPI/QZYo8RgtqXQxFV6Nl66GRSvgd8SYM7zoyxP5RtGR7VwytwZlqhoDosSIk 8/k4x2bZMqbmIqOAJUIMkDS1OK2rnpfGto6y6Bpc= 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 BFDF911E8080 for ; Tue, 8 May 2012 18:06:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.916 X-Spam-Level: X-Spam-Status: No, score=-6.916 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4] 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 7GmNMBsIK4HB for ; Tue, 8 May 2012 18:06:38 -0700 (PDT) Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id 27FB99E8012 for ; Tue, 8 May 2012 18:06:35 -0700 (PDT) Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C8D6CA4424A; Wed, 9 May 2012 03:08:06 +0200 (CEST) Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id BE8E8A44249; Wed, 9 May 2012 03:08:06 +0200 (CEST) Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 May 2012 03:06:33 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 9 May 2012 03:06:31 +0200 Message-ID: In-Reply-To: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] Additional 802.11 attributes Thread-Index: Ac0tXv7ci+6NEh8KRJ6WQC4M4BuiDAAFtgCw References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> From: To: , X-OriginalArrivalTime: 09 May 2012 01:06:33.0479 (UTC) FILETIME=[F991C970:01CD2D7F] X-Mailman-Approved-At: Wed, 09 May 2012 03:54:13 -0700 Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Here are some questions/comments on these proposed attributes. Regards, Lionel 2.9. WLAN-Reason-Code [Lionel] what about reusing Message-Reply attribute in Access-Reject and define additional values for Acct-Terminate-Cause used in Disconnect-Reject (as described in http://tools.ietf.org/html/rfc3580#section-2.1) ? 2.10. WLAN-Pairwise-Cipher 2.11. WLAN-Group-Cipher 2.12. WLAN-AKM-Suite [Lionel] If my understanding is correct, it is expected that the AAA server could reject the access authorization request based on these attributes describing the existing RSNA between the AP and mobile node. If the resulting RSNA is not suitable for the SP, I'm not sure if that this is something that should/could be managed per user authorization request but rather via local policies or SLA between partners. 2.12. WLAN-RF-Band The WLAN-RF-Band Attribute contains information on the RF band used by the AP for transmission and reception of information to and from the mobile device. This information can be used, for example, to provide a relative quality of experience indication for the mobile device's user (i.e., some RF bands have more interference than others). [Lionel] if it is an indication for the user, why is it intended to provide this information to the AAA server? _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Wed May 9 10:55:14 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 441BD11E8081; Wed, 9 May 2012 10:55:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336586114; bh=AdIkZWZNpruVJY1B3J8FGXe4IRsOkwYLA6PfCeq2lA8=; h=From:To:Date:Message-ID:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=UfZmQ35JSCMpzjioPZhTTrYUwjSgWXeiMIhZ5bC/vn00vKv/e4cUqdZjCbsebAgeW VGjKeuOFXBDr1GYKJBbEbAl58XNUI7dkLdEmPt9MP1t0msf62wZOm868Xs/Qo40Ov4 P4+EZ2kB9GgCXYmIdLwn1GUG32NnCxHuUq0pgwZI= 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 A125521F8569 for ; Wed, 9 May 2012 10:55:12 -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 UmBjOyYMoOJb for ; Wed, 9 May 2012 10:55:11 -0700 (PDT) Received: from g4t0014.houston.hp.com (g4t0014.houston.hp.com [15.201.24.17]) by ietfa.amsl.com (Postfix) with ESMTP id ADEA821F8568 for ; Wed, 9 May 2012 10:55:11 -0700 (PDT) Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net [16.236.31.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g4t0014.houston.hp.com (Postfix) with ESMTPS id 0F7902468F; Wed, 9 May 2012 17:55:09 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G1W0400.americas.hpqcorp.net (16.236.31.10) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 9 May 2012 17:54:47 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Wed, 9 May 2012 18:54:47 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "Romascanu, Dan (Dan)" , "Congdon, Paul T (HPLabs)" , "radext@ietf.org" Date: Wed, 9 May 2012 18:54:42 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Thread-Index: Ac0uDNHyJawaGcWNQPSdVGXqDBqrdQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Between the both of you it sounds like the appropriate groups in IEEE have or will be contacted soon. Correct? -MS From: , "dromasca@avaya.com" > To: "Congdon, Paul T (HPLabs)" >, Mauricio Sanchez >, "radext@ietf.org" > Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Yes, please forward to the EC reflector. Thanks, Dan -----Original Message----- From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] Sent: Tue 5/8/2012 8:33 PM To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); radext@ietf.org Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" I typically forward these type of announcements to the EC reflector and call attention to the appropriate WGs. There are likely other wireless groups that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@ietf.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Networks" Good point - can you forward to their reflector or do you know anybody who can do it? Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" > > You may also want to include 802.11 > > Paul > > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From mauricio.sanchez@hp.com Wed May 9 10:55:12 2012 Return-Path: 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 A125521F8569 for ; Wed, 9 May 2012 10:55:12 -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 UmBjOyYMoOJb for ; Wed, 9 May 2012 10:55:11 -0700 (PDT) Received: from g4t0014.houston.hp.com (g4t0014.houston.hp.com [15.201.24.17]) by ietfa.amsl.com (Postfix) with ESMTP id ADEA821F8568 for ; Wed, 9 May 2012 10:55:11 -0700 (PDT) Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net [16.236.31.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g4t0014.houston.hp.com (Postfix) with ESMTPS id 0F7902468F; Wed, 9 May 2012 17:55:09 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G1W0400.americas.hpqcorp.net (16.236.31.10) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 9 May 2012 17:54:47 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Wed, 9 May 2012 18:54:47 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "Romascanu, Dan (Dan)" , "Congdon, Paul T (HPLabs)" , "radext@ietf.org" Date: Wed, 9 May 2012 18:54:42 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Thread-Index: Ac0uDNHyJawaGcWNQPSdVGXqDBqrdQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 17:55:12 -0000 Between the both of you it sounds like the appropriate groups in IEEE have = or will be contacted soon. Correct? -MS From: , "dromasca@avaya.com" > To: "Congdon, Paul T (HPLabs)" >, Mauricio Sanchez >, "radext@ietf.org" > Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" Yes, please forward to the EC reflector. Thanks, Dan -----Original Message----- From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] Sent: Tue 5/8/2012 8:33 PM To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); radext@ietf.or= g Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" I typically forward these type of announcements to the EC reflector and cal= l attention to the appropriate WGs. There are likely other wireless groups= that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radex= t-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@iet= f.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Ne= tworks" Good point - can you forward to their reflector or do you know anybody who can do it? Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" > > You may also want to include 802.11 > > Paul > > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:r= adext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Wed May 9 10:55:18 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B566411E80C2; Wed, 9 May 2012 10:55:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336586118; bh=h4NXKY8QfeMTt/2m28Qi1VNqnHmWGHsaKVc/f0e5YUI=; h=From:To:Date:Message-ID:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=pHVDMpXhqEVXVJQllvp2qieL4sclV159PBhtM7nlhwve5LNY5CsxmHPnGwbgjxtiL 71ydy+bRHte1uHZQqAxcrEkQJ63TcTrBNTlDi+5fYg0afSTupMvuRUomji5RHuD60r Pi+M5sCQI9VVCx8Bm/eJe1Jlj/4r2f0xmM/zZdFc= 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 6E9D121F8569 for ; Wed, 9 May 2012 10:55:17 -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 lMTadzIh72pU for ; Wed, 9 May 2012 10:55:13 -0700 (PDT) Received: from g6t0184.atlanta.hp.com (g6t0184.atlanta.hp.com [15.193.32.61]) by ietfa.amsl.com (Postfix) with ESMTP id D118E21F8568 for ; Wed, 9 May 2012 10:55:13 -0700 (PDT) Received: from G5W2206G.americas.hpqcorp.net (g5w2206g.atlanta.hp.com [16.228.43.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0184.atlanta.hp.com (Postfix) with ESMTPS id 86092C387 for ; Wed, 9 May 2012 17:55:11 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G5W2206G.americas.hpqcorp.net (16.228.43.185) with Microsoft SMTP Server (TLS) id 14.2.283.4; Wed, 9 May 2012 17:54:37 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Wed, 9 May 2012 18:54:37 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Wed, 9 May 2012 18:54:34 +0100 Thread-Topic: RADEXT charter Thread-Index: Ac0uDMxojVllSGKhTbCFfgqqGhpcZw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US MIME-Version: 1.0 Subject: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org We have been discussing rechartering on and off since January. Below is an updated proposal that we would appreciate your review and feedback. The changes can be summarized as follows: * Updating completed work items and casting new dates for work items not accomplished per the dates in existing charter * Addition of network access identifier work item * Addition of traffic accounting work item * Addition of packet fragmentation work item Thanks, Mauricio and Jouni --------------------------------------------- Description of Working Group The RADIUS Extensions Working Group will focus on extensions to the RADIUS protocol required to expand and enrich the standard attribute space, address cryptographic algorithm agility, use of new secure transports and clarify its usage and definition. In order to enable interoperation of heterogeneous RADIUS/Diameter deployments, all RADEXT WG work items MUST contain a Diameter compatibility section, outlining how interoperability with Diameter will be maintained. Furthermore, to ensure backward compatibility with existing RADIUS implementations, as well as compatibility between RADIUS and Diameter, the following restrictions are imposed on extensions considered by the RADEXT WG: - All documents produced MUST specify means of interoperation with legacy RADIUS and, if possible, be backward compatible with existing RADIUS RFCs, including RFCs 2865-2869, 3162, 3575, 3579, 3580, 4668-4673,4675, 5080, 5090, 5176 and 6158. Transport profiles should, if possible, be compatible with RFC 3539. - All RADIUS work MUST be compatible with equivalent facilities in Diameter. Where possible, new attributes should be defined so that the same attribute can be used in both RADIUS and Diameter without translation. In other cases a translation considerations section should be included in the specification. Work Items The immediate goals of the RADEXT working group are to address the following issues: - RADIUS attribute space extension. The standard RADIUS attribute space is currently being depleted. This document will provide additional standard attribute space, while maintaining backward compatibility with existing attributes. - IEEE 802 attributes. New attributes have been proposed to support IEEE 802 standards for wired and wireless LANs. This work item will support authentication, authorization and accounting attributes needed by IEEE 802 groups including IEEE 802.1, IEEE 802.11 and IEEE 802.16. - New RADIUS transports. A reliable transport profile for RADIUS will be developed, as well as specifications for Secure transports, including TCP/TLS (RADSEC) and UDP/DTLS. - Update and clarification of Network Access Identifiers (RFC4282).This work item will correct and clarify issues present with RFC4282 in two phases. In first phase, RFC4282bis will be issued to eliminate fundamental incompatibilities with RADIUS around character encoding and NAI modifications by proxies. In second phase, a fresh review of NAI internationalization requirements and behavior will be undertaken with a clear goal of maintaining compatibility with RADIUS. - RADIUS Accounting Extensions for Traffic Statistics. This work item will specify RADIUS accounting attributes for differentiated accounting polices and traffic recording. - Fragmentation of RADIUS packets to support exchanges exceeding the existing 4KB limit imposed by RFC2865. Goals and Milestones Done Updates to RFC 2618-2621 RADIUS MIBs submitted for publication Done SIP RADIUS authentication draft submitted as a Proposed Standard RFC Done RFC 2486bis submitted as a Proposed Standard RFC Done RFC 3576 MIBs submitted as an Informational RFC Done RADIUS VLAN and Priority Attributes draft submitted as a Proposed Standard RFC (reduced in scope) Done RADIUS Implementation Issues and Fixes draft submitted as an Informational RFC Done RADIUS Filtering Attributes draft submitted as a Proposed Standard RFC (split out from VLAN & Priority draft) Done RFC 3576bis submitted as an Informational RFC (split out from Issues & Fixes draft) Done RADIUS Redirection Attributes draft submitted as a Proposed Standard RFC (split out from VLAN & Priority draft) Done RADIUS Design Guidelines submitted as a Best Current Practice RFC Done RADIUS Management Authorization I-D submitted as a Proposed Standard RFC Done Reliable Transport Profile for RADIUS I-D submitted as a Proposed Standard RFC Done Status-Server I-D submitted as a Proposed Standard RFC Done RADIUS Crypto-agility Requirements submitted as an Informational RFC Done RADSEC (RADIUS over TCP/TLS) draft submitted as an Experimental RFC May 2012 IPv6 Access I-D submitted as a Proposed Standard RFC May 2012 Extended Attributes I-D submitted as a Proposed Standard RFC Jun 2012 Dynamic Discovery I-D submitted as a Proposed Standard RFC Jun 2012 IEEE 802 Attributes I-D submitted as a Proposed Standard RFC Aug 2012 RADIUS over DTLS I-D submitted as an Experimental RFC Nov 2012 Traffic Statistics Attribute I-D submitted as a Proposed Standard RFC Nov 2012 RADIUS packet fragmentation submitted as an Experimental RFC Nov 2012 RFC 4282bis submitted as a Proposed Standard RFC Apr 2013 RADIUS support for NAI Internationalization I-D submitted as a Proposed Standard RFC _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From mauricio.sanchez@hp.com Wed May 9 10:55:17 2012 Return-Path: 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 6E9D121F8569 for ; Wed, 9 May 2012 10:55:17 -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 lMTadzIh72pU for ; Wed, 9 May 2012 10:55:13 -0700 (PDT) Received: from g6t0184.atlanta.hp.com (g6t0184.atlanta.hp.com [15.193.32.61]) by ietfa.amsl.com (Postfix) with ESMTP id D118E21F8568 for ; Wed, 9 May 2012 10:55:13 -0700 (PDT) Received: from G5W2206G.americas.hpqcorp.net (g5w2206g.atlanta.hp.com [16.228.43.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0184.atlanta.hp.com (Postfix) with ESMTPS id 86092C387 for ; Wed, 9 May 2012 17:55:11 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G5W2206G.americas.hpqcorp.net (16.228.43.185) with Microsoft SMTP Server (TLS) id 14.2.283.4; Wed, 9 May 2012 17:54:37 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Wed, 9 May 2012 18:54:37 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Wed, 9 May 2012 18:54:34 +0100 Thread-Topic: RADEXT charter Thread-Index: Ac0uDMxojVllSGKhTbCFfgqqGhpcZw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 17:55:17 -0000 We have been discussing rechartering on and off since January. Below is an= updated proposal that we would appreciate your review and feedback. The c= hanges can be summarized as follows: * Updating completed work items and casting new dates for work items not= accomplished per the dates in existing charter * Addition of network access identifier work item * Addition of traffic accounting work item * Addition of packet fragmentation work item Thanks, Mauricio and Jouni --------------------------------------------- Description of Working Group The RADIUS Extensions Working Group will focus on extensions to the RADIUS = protocol required to expand and enrich the standard attribute space, addres= s cryptographic algorithm agility, use of new secure transports and clarify= its usage and definition. In order to enable interoperation of heterogeneous RADIUS/Diameter deployme= nts, all RADEXT WG work items MUST contain a Diameter compatibility section= , outlining how interoperability with Diameter will be maintained. Furthermore, to ensure backward compatibility with existing RADIUS implemen= tations, as well as compatibility between RADIUS and Diameter, the followin= g restrictions are imposed on extensions considered by the RADEXT WG: - All documents produced MUST specify means of interoperation with legacy R= ADIUS and, if possible, be backward compatible with existing RADIUS RFCs, i= ncluding RFCs 2865-2869, 3162, 3575, 3579, 3580, 4668-4673,4675, 5080, 5090= , 5176 and 6158. Transport profiles should, if possible, be compatible with= RFC 3539. - All RADIUS work MUST be compatible with equivalent facilities in Diameter= . Where possible, new attributes should be defined so that the same attribu= te can be used in both RADIUS and Diameter without translation. In other ca= ses a translation considerations section should be included in the specific= ation. Work Items The immediate goals of the RADEXT working group are to address the followin= g issues: - RADIUS attribute space extension. The standard RADIUS attribute space is = currently being depleted. This document will provide additional standard at= tribute space, while maintaining backward compatibility with existing attri= butes. - IEEE 802 attributes. New attributes have been proposed to support IEEE 80= 2 standards for wired and wireless LANs. This work item will support authen= tication, authorization and accounting attributes needed by IEEE 802 groups= including IEEE 802.1, IEEE 802.11 and IEEE 802.16. - New RADIUS transports. A reliable transport profile for RADIUS will be de= veloped, as well as specifications for Secure transports, including TCP/TLS= (RADSEC) and UDP/DTLS. - Update and clarification of Network Access Identifiers (RFC4282).This wor= k item will correct and clarify issues present with RFC4282 in two phases. = In first phase, RFC4282bis will be issued to eliminate fundamental incompa= tibilities with RADIUS around character encoding and NAI modifications by p= roxies. In second phase, a fresh review of NAI internationalization requir= ements and behavior will be undertaken with a clear goal of maintaining com= patibility with RADIUS. - RADIUS Accounting Extensions for Traffic Statistics. This work item will = specify RADIUS accounting attributes for differentiated accounting polices = and traffic recording. - Fragmentation of RADIUS packets to support exchanges exceeding the existi= ng 4KB limit imposed by RFC2865. Goals and Milestones Done Updates to RFC 2618-2621 RADIUS MIBs submitted for publication Done SIP RADIUS authentication draft submitted as a Proposed Standard RFC Done RFC 2486bis submitted as a Proposed Standard RFC Done RFC 3576 MIBs submitted as an Informational RFC Done RADIUS VLAN and Priority Attributes draft submitted as a Proposed Stan= dard RFC (reduced in scope) Done RADIUS Implementation Issues and Fixes draft submitted as an Informati= onal RFC Done RADIUS Filtering Attributes draft submitted as a Proposed Standard RFC= (split out from VLAN & Priority draft) Done RFC 3576bis submitted as an Informational RFC (split out from Issues &= Fixes draft) Done RADIUS Redirection Attributes draft submitted as a Proposed Standard R= FC (split out from VLAN & Priority draft) Done RADIUS Design Guidelines submitted as a Best Current Practice RFC Done RADIUS Management Authorization I-D submitted as a Proposed Standard R= FC Done Reliable Transport Profile for RADIUS I-D submitted as a Proposed Stan= dard RFC Done Status-Server I-D submitted as a Proposed Standard RFC Done RADIUS Crypto-agility Requirements submitted as an Informational RFC Done RADSEC (RADIUS over TCP/TLS) draft submitted as an Experimental RFC May 2012 IPv6 Access I-D submitted as a Proposed Standard RFC May 2012 Extended Attributes I-D submitted as a Proposed Standard RFC Jun 2012 Dynamic Discovery I-D submitted as a Proposed Standard RFC Jun 2012 IEEE 802 Attributes I-D submitted as a Proposed Standard RFC Aug 2012 RADIUS over DTLS I-D submitted as an Experimental RFC Nov 2012 Traffic Statistics Attribute I-D submitted as a Proposed Standa= rd RFC Nov 2012 RADIUS packet fragmentation submitted as an Experimental RFC Nov 2012 RFC 4282bis submitted as a Proposed Standard RFC Apr 2013 RADIUS support for NAI Internationalization I-D submitted as a Pro= posed Standard RFC From radext-bounces@ietf.org Wed May 9 10:57:13 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4422921F8573; Wed, 9 May 2012 10:57:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336586233; bh=HygVGhg20IbQqEq4ozOmRaP15G+4Q+FHdMi3YIWrU0w=; h=From:To:Date:Message-ID:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=iNZ22wqZe5fzRjYWhFIcs3DM6lL2kdwH9nvHas9Ijx/Aa5komsSGOAh3ycXA7gOdc 9vXQEkaiIGZpXOvI55kjNQ9YE0s21QzDSAX5Ye+E5Pt57EAmG1EKQd1mJQ5lW8SlWN yQQNkVDd4VudcupXcb6/lPVjv31LcXa4ib02WY4k= 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 5C06721F8573; Wed, 9 May 2012 10:57:12 -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 vpBH-MgbvgKG; Wed, 9 May 2012 10:57:11 -0700 (PDT) Received: from g4t0014.houston.hp.com (g4t0014.houston.hp.com [15.201.24.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1C621F856F; Wed, 9 May 2012 10:57:11 -0700 (PDT) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g4t0014.houston.hp.com (Postfix) with ESMTPS id 4BFE3243AB; Wed, 9 May 2012 17:57:11 +0000 (UTC) Received: from G5W0602.americas.hpqcorp.net (16.228.9.185) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.2.283.4; Wed, 9 May 2012 17:56:15 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0602.americas.hpqcorp.net ([16.228.9.185]) with mapi; Wed, 9 May 2012 18:56:15 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" , "dime@ietf.org" Date: Wed, 9 May 2012 18:56:13 +0100 Thread-Topic: RADEXT WG Last Call: "RADIUS Protocol Extensions" Thread-Index: Ac0uDQatZHc5yeLqQZmcgfGJYhN4Ag== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US MIME-Version: 1.0 Subject: [radext] RADEXT WG Last Call: "RADIUS Protocol Extensions" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org This is an announcement of RADEXT WG last call on "RADIUS Protocol Extensio= ns", prior to sending the document to the IESG for publication as a propos= ed standard RFC. We are asking review from both RADEXT and DIME WGs as a ma= tter completeness. The document is available for inspection here: http://tools.ietf.org/id/draft-ietf-radext-radius-extensions The RADEXT WG last call will last until Wednesday May 23, 2012. If you ha= ve comments on the document, please file using TRAC system. See below for = summary of instructions. Thanks, Mauricio and Jouni 1. To submit an issue in TRAC, you first need to login to the RADEXT = WG site on the tools server: http://tools.ietf.org/wg/radext/trac/login 2. If you don=92t already have a login ID, you can obtain one by navi= gating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can fil= e an issue by navigating to the ticket entry form:http://trac.tools.ietf.o= rg/wg/radext/trac/newticket 4. When opening an issue: a. The Type: field should be set to =93defect=94 for an issue with th= e current document text, or =93enhancement=94 for a proposed addition of fu= nctionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. Fo= r example, editorial issues are typically =93minor=94 or =93trivial=94. c. The Milestone: field should be set to milestone1 (useless, I know). d. The Component: field should be set to the document you are filing t= he issue on. e. The Version: field should be set to =931.0=94. f. The Severity: field should be set to based on the status of the d= ocument (e.g. =93In WG Last Call=94 for a document in WG last call) g. The Keywords: and CC: fields can be left blank unless inspiration= seizes you. h. The Assign To: field is generally filled in with the email address = of the editor. 5. Typically it won=92t be necessary to enclose a file with the ticke= t, but if you need to, select =93I have files to attach to this ticket=94. 6. If you want to preview your Issue, click on the =93Preview=94 butt= on. When you=92re ready to submit the issue, click on the =93Create Ticket= =94 button. 7. If you want to update an issue, go to the "View Tickets" page: htt= p://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket # you = want to update, and then modify the ticket fields as required _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From mauricio.sanchez@hp.com Wed May 9 10:57:12 2012 Return-Path: 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 5C06721F8573; Wed, 9 May 2012 10:57:12 -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 vpBH-MgbvgKG; Wed, 9 May 2012 10:57:11 -0700 (PDT) Received: from g4t0014.houston.hp.com (g4t0014.houston.hp.com [15.201.24.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1C621F856F; Wed, 9 May 2012 10:57:11 -0700 (PDT) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g4t0014.houston.hp.com (Postfix) with ESMTPS id 4BFE3243AB; Wed, 9 May 2012 17:57:11 +0000 (UTC) Received: from G5W0602.americas.hpqcorp.net (16.228.9.185) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.2.283.4; Wed, 9 May 2012 17:56:15 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0602.americas.hpqcorp.net ([16.228.9.185]) with mapi; Wed, 9 May 2012 18:56:15 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" , "dime@ietf.org" Date: Wed, 9 May 2012 18:56:13 +0100 Thread-Topic: RADEXT WG Last Call: "RADIUS Protocol Extensions" Thread-Index: Ac0uDQatZHc5yeLqQZmcgfGJYhN4Ag== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [radext] RADEXT WG Last Call: "RADIUS Protocol Extensions" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 17:57:12 -0000 This is an announcement of RADEXT WG last call on "RADIUS Protocol Extensio= ns", prior to sending the document to the IESG for publication as a propos= ed standard RFC. We are asking review from both RADEXT and DIME WGs as a ma= tter completeness. The document is available for inspection here: http://tools.ietf.org/id/draft-ietf-radext-radius-extensions The RADEXT WG last call will last until Wednesday May 23, 2012. If you ha= ve comments on the document, please file using TRAC system. See below for = summary of instructions. Thanks, Mauricio and Jouni 1. To submit an issue in TRAC, you first need to login to the RADEXT = WG site on the tools server: http://tools.ietf.org/wg/radext/trac/login 2. If you don=92t already have a login ID, you can obtain one by navi= gating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can fil= e an issue by navigating to the ticket entry form:http://trac.tools.ietf.o= rg/wg/radext/trac/newticket 4. When opening an issue: a. The Type: field should be set to =93defect=94 for an issue with th= e current document text, or =93enhancement=94 for a proposed addition of fu= nctionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. Fo= r example, editorial issues are typically =93minor=94 or =93trivial=94. c. The Milestone: field should be set to milestone1 (useless, I know)= . d. The Component: field should be set to the document you are filing t= he issue on. e. The Version: field should be set to =931.0=94. f. The Severity: field should be set to based on the status of the d= ocument (e.g. =93In WG Last Call=94 for a document in WG last call) g. The Keywords: and CC: fields can be left blank unless inspiration= seizes you. h. The Assign To: field is generally filled in with the email address = of the editor. 5. Typically it won=92t be necessary to enclose a file with the ticke= t, but if you need to, select =93I have files to attach to this ticket=94. 6. If you want to preview your Issue, click on the =93Preview=94 butt= on. When you=92re ready to submit the issue, click on the =93Create Ticket= =94 button. 7. If you want to update an issue, go to the "View Tickets" page: htt= p://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the ticket # you = want to update, and then modify the ticket fields as required From paul.congdon@hp.com Wed May 9 12:37:14 2012 Return-Path: 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 9CEC421F84C3 for ; Wed, 9 May 2012 12:37:14 -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 nIR4ctuZpNRU for ; Wed, 9 May 2012 12:37:13 -0700 (PDT) Received: from g6t0186.atlanta.hp.com (g6t0186.atlanta.hp.com [15.193.32.63]) by ietfa.amsl.com (Postfix) with ESMTP id 1309E21F8499 for ; Wed, 9 May 2012 12:37:13 -0700 (PDT) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0186.atlanta.hp.com (Postfix) with ESMTPS id 8B4B92C1AF; Wed, 9 May 2012 19:37:12 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.2.283.4; Wed, 9 May 2012 19:36:04 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Wed, 9 May 2012 20:36:04 +0100 From: "Congdon, Paul T (HPLabs)" To: "Sanchez, Mauricio (HP Networking)" , "Romascanu, Dan (Dan)" , "radext@ietf.org" Date: Wed, 9 May 2012 20:35:57 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Thread-Index: Ac0uDNHyJawaGcWNQPSdVGXqDBqrdQADhlrQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_" MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 19:37:14 -0000 --_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable They have been contacted. I forwarded to the 802 EC yesterday From: Sanchez, Mauricio (HP Networking) Sent: Wednesday, May 09, 2012 10:55 AM To: Romascanu, Dan (Dan); Congdon, Paul T (HPLabs); radext@ietf.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" Between the both of you it sounds like the appropriate groups in IEEE have = or will be contacted soon. Correct? -MS From: , "dromasca@avaya.com" > To: "Congdon, Paul T (HPLabs)" >, Mauricio Sanchez >, "radext@ietf.org" > Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" Yes, please forward to the EC reflector. Thanks, Dan -----Original Message----- From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] Sent: Tue 5/8/2012 8:33 PM To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); radext@ietf.or= g Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" I typically forward these type of announcements to the EC reflector and cal= l attention to the appropriate WGs. There are likely other wireless groups= that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radex= t-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@iet= f.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Ne= tworks" Good point - can you forward to their reflector or do you know anybody who can do it? Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" > > You may also want to include 802.11 > > Paul > > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:r= adext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext --_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable RE: [radext] RADEXT WG Last Call: &qu= ot;RADIUS Attributes forIEEE802Networks"

They have been contacted.  I forwarded to the 802 EC yester= day

 

From: Sanchez, Mauricio (HP Networki= ng)
Sent: Wednesday, May 09, 2012 10:55 AM
To: Romasca= nu, Dan (Dan); Congdon, Paul T (HPLabs); radext@ietf.org
Subject:= Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networ= ks"

 <= /o:p>

Between the both of you i= t sounds like the appropriate groups in IEEE have or will be contacted soon= . Correct?

&= nbsp;

-MS

 

=  

From: = <Romascanu>, "dromasca@avaya.com" <= dromasca@avaya.com>
To: "Congdon, Paul T (HPLabs)&quo= t; <paul.congdon@hp.com>, = Mauricio Sanchez <mauricio.sa= nchez@hp.com>, "radext@ietf.= org" <radext@ietf.org>= ;
Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attribu= tes forIEEE802Networks"

 

Yes, please forward to the EC reflector.

Thanks,=

Dan



-----Original Message-----
From: Congdon, Pau= l T (HPLabs) [mailto:paul.congdon@hp= .com]
Sent: Tue 5/8/2012 8:33 PM
To: Romascanu, Dan (Dan); Sanche= z, Mauricio (HP Networking); radext@ietf= .org
Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attribu= tes forIEEE802Networks"

I typically forward these type of annou= ncements to the EC reflector and call attention to the appropriate WGs.&nbs= p; There are likely other wireless groups that have interest.  I can f= orward for you.
Paul

-----Original Message-----
From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Beh= alf Of Romascanu, Dan (Dan)
Sent: Tuesday, May 08, 2012 8:30 AM
To: C= ongdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@ietf.org
Subject: Re: [radext] RADEXT WG = Last Call: "RADIUS Attributes for IEEE802Networks"

Good po= int - can you forward to their reflector or do you know anybody
who can = do it?

Dan




> -----Original Message-----
>= ; From: Congdon, Paul T (HPLabs) [ma= ilto:paul.congdon@hp.com]
> Sent: Tuesday, May 08, 2012 6:26 PM> To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking);
>= radext@ietf.org
> Subject: Re= : [radext] RADEXT WG Last Call: "RADIUS Attributes for
> IEEE802= Networks"
>
> You may also want to include 802.11
><= br>> Paul
>
> -- Sent from my HP TouchPad
> __________= ______________________
> On May 8, 2012 1:47 AM, Romascanu, Dan (Dan)= <dromasca@avaya.com>
&g= t; wrote:
> FYI - I forwarded the WGLC announcement to the IEEE 802.1= reflector. I
> believe having experts from the IEEE 802.1 WG review = and comment on
> this
> document would be very useful.
><= br>> Regards,
>
> Dan
>
>
>
>
>= ; > -----Original Message-----
> > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On
> > Behal= f Of Sanchez, Mauricio (HP Networking)
> > Sent: Tuesday, May 08, = 2012 12:46 AM
> > To: radext@ie= tf.org
> > Subject: [radext] RADEXT WG Last Call: "RADIUS= Attributes for IEEE
> > 802Networks"
> >
> &g= t; This is an announcement of RADEXT WG last call on "RADIUS Attribute= s
> > for IEEE 802 Networks", prior to sending the document t= o the IESG
for
> > publication as a proposed standard RFC.
&= gt; >
> > The document is available for inspection here:
>= ; > ht= tp://tools.ietf.org/id/draft-ietf-radext-ieee802ext
> >
>= ; > The RADEXT WG last call will last until Monday May 21, 2012. &n= bsp; If
you
> > have comments on the document, please file usin= g TRAC system.  See
> > below for summary of instructions.> >
> > Thanks,
> > Mauricio and Jouni
> >= ;
> > 1.       To submit an issue in= TRAC, you first need to login to the
> > RADEXT WG site on the to= ols server:
> > http://tools.ietf.org/wg/radext/trac/login
> > 2. &n= bsp;     If you don't already have a login ID, you can = obtain one by
> > navigating to this site:   http://trac.tools.ietf.org/newlogin
> > 3.       Once you have obtaine= d an account, and have logged in, you
> can
> > file an issu= e by navigating to the  ticket entry
> > form:http://trac.tools.ietf.org= /wg/radext/trac/newticket
> > 4.     =   When opening an issue:
> > a.     =   The Type: field should be set to "defect" for an issue wit= h
> > the current document text, or "enhancement" for a = proposed addition
> of
> > functionality (such as an additio= nal requirement).
> > b.      The Priorit= y: field is set based on the severity of the
> Issue.
> > Fo= r example, editorial issues are typically "minor" or "trivia= l".
> > c.       The Milestone:= field should be set to milestone1 (useless,
I
> > know).
&g= t; > d.      The Component: field should be set= to the document you are
> > filing the issue on.
> > e.&= nbsp;     The Version: field should be set to "1.0= ".
> > f.        The Sever= ity: field should be set to based on the status
of
> > the docu= ment (e.g. "In WG Last Call" for a document in WG last call)
&= gt; > g.        The Keywords: and CC:= fields can be left blank unless
> > inspiration seizes you.
&g= t; > h.      The Assign To: field is generally = filled in with the email
> > address of the editor.
> > 5= .       Typically it won't be necessary to en= close a file with the
> > ticket, but if you need to, select "= ;I have files to attach to this
> > ticket".
> > 6.&= nbsp;      If you want to preview your Issue, clic= k on the "Preview"
> > button.  When you're ready t= o submit the issue, click on the "Create
> > Ticket" but= ton.
> > 7.       If you want to upd= ate an issue, go to the "View Tickets"
> page:
> >= http://trac= .tools.ietf.org/wg/radext/trac/report/1  Click on the
> tick= et
> > # you want to update, and then modify the ticket fields as = required
> > _______________________________________________
&g= t; > radext mailing list
> > radext@ietf.org
> > https://www.ietf.org/mailman/listinfo/radext
> __= _____________________________________________
> radext mailing list> radext@ietf.org
> https://www.ietf.org/ma= ilman/listinfo/radext
______________________________________________= _
radext mailing list
radext@ietf.= org
https:/= /www.ietf.org/mailman/listinfo/radext

=
= --_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_-- From radext-bounces@ietf.org Wed May 9 12:37:16 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 552EB21F84C3; Wed, 9 May 2012 12:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336592236; bh=DF0lGxv6q824O3faL1cWtrmt98+Fkdj9R16NQzsPsTk=; h=From:To:Date:Message-ID:References:In-Reply-To:MIME-Version: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Sender; b=YZELEslrGBCIkhAubeOiwbhdyqXSn6/cyMAS9EGIY/wCdlQI6LITIUpZtj6O7OfYI vjRoiDUbjH7EonzEE2tHdasBcxN7V3QtZqT2h7Gh7OqOXAEmR9UOboQz0cSamQqxRR wVrDXyx/74y+VajlENlJfbuVB104Aho4nx4NivLc= 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 9CEC421F84C3 for ; Wed, 9 May 2012 12:37:14 -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 nIR4ctuZpNRU for ; Wed, 9 May 2012 12:37:13 -0700 (PDT) Received: from g6t0186.atlanta.hp.com (g6t0186.atlanta.hp.com [15.193.32.63]) by ietfa.amsl.com (Postfix) with ESMTP id 1309E21F8499 for ; Wed, 9 May 2012 12:37:13 -0700 (PDT) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0186.atlanta.hp.com (Postfix) with ESMTPS id 8B4B92C1AF; Wed, 9 May 2012 19:37:12 +0000 (UTC) Received: from G6W0644.americas.hpqcorp.net (16.230.34.80) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.2.283.4; Wed, 9 May 2012 19:36:04 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G6W0644.americas.hpqcorp.net ([16.230.34.80]) with mapi; Wed, 9 May 2012 20:36:04 +0100 From: "Congdon, Paul T (HPLabs)" To: "Sanchez, Mauricio (HP Networking)" , "Romascanu, Dan (Dan)" , "radext@ietf.org" Date: Wed, 9 May 2012 20:35:57 +0100 Thread-Topic: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" Thread-Index: Ac0uDNHyJawaGcWNQPSdVGXqDBqrdQADhlrQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networks" X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7994902990586040348==" Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org --===============7994902990586040348== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_" --_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable They have been contacted. I forwarded to the 802 EC yesterday From: Sanchez, Mauricio (HP Networking) Sent: Wednesday, May 09, 2012 10:55 AM To: Romascanu, Dan (Dan); Congdon, Paul T (HPLabs); radext@ietf.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" Between the both of you it sounds like the appropriate groups in IEEE have = or will be contacted soon. Correct? -MS From: , "dromasca@avaya.com" > To: "Congdon, Paul T (HPLabs)" >, Mauricio Sanchez >, "radext@ietf.org" > Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" Yes, please forward to the EC reflector. Thanks, Dan -----Original Message----- From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] Sent: Tue 5/8/2012 8:33 PM To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); radext@ietf.or= g Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Net= works" I typically forward these type of announcements to the EC reflector and cal= l attention to the appropriate WGs. There are likely other wireless groups= that have interest. I can forward for you. Paul -----Original Message----- From: radext-bounces@ietf.org [mailto:radex= t-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan) Sent: Tuesday, May 08, 2012 8:30 AM To: Congdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@iet= f.org Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE802Ne= tworks" Good point - can you forward to their reflector or do you know anybody who can do it? Dan > -----Original Message----- > From: Congdon, Paul T (HPLabs) [mailto:paul.congdon@hp.com] > Sent: Tuesday, May 08, 2012 6:26 PM > To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking); > radext@ietf.org > Subject: Re: [radext] RADEXT WG Last Call: "RADIUS Attributes for > IEEE802Networks" > > You may also want to include 802.11 > > Paul > > -- Sent from my HP TouchPad > ________________________________ > On May 8, 2012 1:47 AM, Romascanu, Dan (Dan) > > wrote: > FYI - I forwarded the WGLC announcement to the IEEE 802.1 reflector. I > believe having experts from the IEEE 802.1 WG review and comment on > this > document would be very useful. > > Regards, > > Dan > > > > > > -----Original Message----- > > From: radext-bounces@ietf.org [mailto:r= adext-bounces@ietf.org] On > > Behalf Of Sanchez, Mauricio (HP Networking) > > Sent: Tuesday, May 08, 2012 12:46 AM > > To: radext@ietf.org > > Subject: [radext] RADEXT WG Last Call: "RADIUS Attributes for IEEE > > 802Networks" > > > > This is an announcement of RADEXT WG last call on "RADIUS Attributes > > for IEEE 802 Networks", prior to sending the document to the IESG for > > publication as a proposed standard RFC. > > > > The document is available for inspection here: > > http://tools.ietf.org/id/draft-ietf-radext-ieee802ext > > > > The RADEXT WG last call will last until Monday May 21, 2012. If you > > have comments on the document, please file using TRAC system. See > > below for summary of instructions. > > > > Thanks, > > Mauricio and Jouni > > > > 1. To submit an issue in TRAC, you first need to login to the > > RADEXT WG site on the tools server: > > http://tools.ietf.org/wg/radext/trac/login > > 2. If you don't already have a login ID, you can obtain one by > > navigating to this site: http://trac.tools.ietf.org/newlogin > > 3. Once you have obtained an account, and have logged in, you > can > > file an issue by navigating to the ticket entry > > form:http://trac.tools.ietf.org/wg/radext/trac/newticket > > 4. When opening an issue: > > a. The Type: field should be set to "defect" for an issue with > > the current document text, or "enhancement" for a proposed addition > of > > functionality (such as an additional requirement). > > b. The Priority: field is set based on the severity of the > Issue. > > For example, editorial issues are typically "minor" or "trivial". > > c. The Milestone: field should be set to milestone1 (useless, I > > know). > > d. The Component: field should be set to the document you are > > filing the issue on. > > e. The Version: field should be set to "1.0". > > f. The Severity: field should be set to based on the status of > > the document (e.g. "In WG Last Call" for a document in WG last call) > > g. The Keywords: and CC: fields can be left blank unless > > inspiration seizes you. > > h. The Assign To: field is generally filled in with the email > > address of the editor. > > 5. Typically it won't be necessary to enclose a file with the > > ticket, but if you need to, select "I have files to attach to this > > ticket". > > 6. If you want to preview your Issue, click on the "Preview" > > button. When you're ready to submit the issue, click on the "Create > > Ticket" button. > > 7. If you want to update an issue, go to the "View Tickets" > page: > > http://trac.tools.ietf.org/wg/radext/trac/report/1 Click on the > ticket > > # you want to update, and then modify the ticket fields as required > > _______________________________________________ > > radext mailing list > > radext@ietf.org > > https://www.ietf.org/mailman/listinfo/radext > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext --_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable RE: [radext] RADEXT WG Last Call: &qu= ot;RADIUS Attributes forIEEE802Networks"

They have been contacted.  I forwarded to the 802 EC yester= day

 

From: Sanchez, Mauricio (HP Networki= ng)
Sent: Wednesday, May 09, 2012 10:55 AM
To: Romasca= nu, Dan (Dan); Congdon, Paul T (HPLabs); radext@ietf.org
Subject:= Re: [radext] RADEXT WG Last Call: "RADIUS Attributes forIEEE802Networ= ks"

 <= /o:p>

Between the both of you i= t sounds like the appropriate groups in IEEE have or will be contacted soon= . Correct?

&= nbsp;

-MS

 

=  

From: = <Romascanu>, "dromasca@avaya.com" <= dromasca@avaya.com>
To: "Congdon, Paul T (HPLabs)&quo= t; <paul.congdon@hp.com>, = Mauricio Sanchez <mauricio.sa= nchez@hp.com>, "radext@ietf.= org" <radext@ietf.org>= ;
Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attribu= tes forIEEE802Networks"

 

Yes, please forward to the EC reflector.

Thanks,=

Dan



-----Original Message-----
From: Congdon, Pau= l T (HPLabs) [mailto:paul.congdon@hp= .com]
Sent: Tue 5/8/2012 8:33 PM
To: Romascanu, Dan (Dan); Sanche= z, Mauricio (HP Networking); radext@ietf= .org
Subject: RE: [radext] RADEXT WG Last Call: "RADIUS Attribu= tes forIEEE802Networks"

I typically forward these type of annou= ncements to the EC reflector and call attention to the appropriate WGs.&nbs= p; There are likely other wireless groups that have interest.  I can f= orward for you.
Paul

-----Original Message-----
From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Beh= alf Of Romascanu, Dan (Dan)
Sent: Tuesday, May 08, 2012 8:30 AM
To: C= ongdon, Paul T (HPLabs); Sanchez, Mauricio (HP Networking); radext@ietf.org
Subject: Re: [radext] RADEXT WG = Last Call: "RADIUS Attributes for IEEE802Networks"

Good po= int - can you forward to their reflector or do you know anybody
who can = do it?

Dan




> -----Original Message-----
>= ; From: Congdon, Paul T (HPLabs) [ma= ilto:paul.congdon@hp.com]
> Sent: Tuesday, May 08, 2012 6:26 PM> To: Romascanu, Dan (Dan); Sanchez, Mauricio (HP Networking);
>= radext@ietf.org
> Subject: Re= : [radext] RADEXT WG Last Call: "RADIUS Attributes for
> IEEE802= Networks"
>
> You may also want to include 802.11
><= br>> Paul
>
> -- Sent from my HP TouchPad
> __________= ______________________
> On May 8, 2012 1:47 AM, Romascanu, Dan (Dan)= <dromasca@avaya.com>
&g= t; wrote:
> FYI - I forwarded the WGLC announcement to the IEEE 802.1= reflector. I
> believe having experts from the IEEE 802.1 WG review = and comment on
> this
> document would be very useful.
><= br>> Regards,
>
> Dan
>
>
>
>
>= ; > -----Original Message-----
> > From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On
> > Behal= f Of Sanchez, Mauricio (HP Networking)
> > Sent: Tuesday, May 08, = 2012 12:46 AM
> > To: radext@ie= tf.org
> > Subject: [radext] RADEXT WG Last Call: "RADIUS= Attributes for IEEE
> > 802Networks"
> >
> &g= t; This is an announcement of RADEXT WG last call on "RADIUS Attribute= s
> > for IEEE 802 Networks", prior to sending the document t= o the IESG
for
> > publication as a proposed standard RFC.
&= gt; >
> > The document is available for inspection here:
>= ; > ht= tp://tools.ietf.org/id/draft-ietf-radext-ieee802ext
> >
>= ; > The RADEXT WG last call will last until Monday May 21, 2012. &n= bsp; If
you
> > have comments on the document, please file usin= g TRAC system.  See
> > below for summary of instructions.> >
> > Thanks,
> > Mauricio and Jouni
> >= ;
> > 1.       To submit an issue in= TRAC, you first need to login to the
> > RADEXT WG site on the to= ols server:
> > http://tools.ietf.org/wg/radext/trac/login
> > 2. &n= bsp;     If you don't already have a login ID, you can = obtain one by
> > navigating to this site:   http://trac.tools.ietf.org/newlogin
> > 3.       Once you have obtaine= d an account, and have logged in, you
> can
> > file an issu= e by navigating to the  ticket entry
> > form:http://trac.tools.ietf.org= /wg/radext/trac/newticket
> > 4.     =   When opening an issue:
> > a.     =   The Type: field should be set to "defect" for an issue wit= h
> > the current document text, or "enhancement" for a = proposed addition
> of
> > functionality (such as an additio= nal requirement).
> > b.      The Priorit= y: field is set based on the severity of the
> Issue.
> > Fo= r example, editorial issues are typically "minor" or "trivia= l".
> > c.       The Milestone:= field should be set to milestone1 (useless,
I
> > know).
&g= t; > d.      The Component: field should be set= to the document you are
> > filing the issue on.
> > e.&= nbsp;     The Version: field should be set to "1.0= ".
> > f.        The Sever= ity: field should be set to based on the status
of
> > the docu= ment (e.g. "In WG Last Call" for a document in WG last call)
&= gt; > g.        The Keywords: and CC:= fields can be left blank unless
> > inspiration seizes you.
&g= t; > h.      The Assign To: field is generally = filled in with the email
> > address of the editor.
> > 5= .       Typically it won't be necessary to en= close a file with the
> > ticket, but if you need to, select "= ;I have files to attach to this
> > ticket".
> > 6.&= nbsp;      If you want to preview your Issue, clic= k on the "Preview"
> > button.  When you're ready t= o submit the issue, click on the "Create
> > Ticket" but= ton.
> > 7.       If you want to upd= ate an issue, go to the "View Tickets"
> page:
> >= http://trac= .tools.ietf.org/wg/radext/trac/report/1  Click on the
> tick= et
> > # you want to update, and then modify the ticket fields as = required
> > _______________________________________________
&g= t; > radext mailing list
> > radext@ietf.org
> > https://www.ietf.org/mailman/listinfo/radext
> __= _____________________________________________
> radext mailing list> radext@ietf.org
> https://www.ietf.org/ma= ilman/listinfo/radext
______________________________________________= _
radext mailing list
radext@ietf.= org
https:/= /www.ietf.org/mailman/listinfo/radext

=
= --_000_FF279C1430421C43B7E0C519F5D50FA3521EA04368GVW0671EXCame_-- --===============7994902990586040348== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext --===============7994902990586040348==-- From leaf.y.yeh@huawei.com Fri May 11 03:48:11 2012 Return-Path: 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 82D7621F85E5 for ; Fri, 11 May 2012 03:48:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.567 X-Spam-Level: X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599] 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 ykc0260eG8yd for ; Fri, 11 May 2012 03:48:10 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id BAAE221F8570 for ; Fri, 11 May 2012 03:48:10 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFV12054; Fri, 11 May 2012 06:48:10 -0400 (EDT) Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 May 2012 03:44:27 -0700 Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 May 2012 03:44:25 -0700 Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.168]) by szxeml413-hub.china.huawei.com ([10.82.67.152]) with mapi id 14.01.0323.003; Fri, 11 May 2012 18:44:23 +0800 From: Leaf yeh To: jouni korhonen , "radext@ietf.org" Thread-Topic: I-D Action: draft-ietf-radext-ipv6-access-07.txt Thread-Index: AQHNLFneQkQleKjX90CL1w6gppUCXZbETbjA Date: Fri, 11 May 2012 10:44:22 +0000 Message-ID: References: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.70.39.132] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Cc: Wojciech Dec Subject: Re: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2012 10:48:11 -0000 SSdkIHJlYWxseSBsaWtlIHRvIHNlZSB0aGUgYWR2YW5jaW5nIG9mIHRoaXMgZG9jdW1lbnQsIGJl Y2F1c2UgSSBoYXZlIGEgZHJhZnQgKGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh ZnQtaWV0Zi1kaGMtZGhjcHY2LXJhZGl1cy1vcHQvKSwgd2hpY2ggaGFzIHR1cm5lZCB0byBiZSBk cmFmdC1pZXRmLCBoYXMgcmVmZXJyZWQgdG8gdGhlIGF0dHJpYnV0ZXMgZGVmaW5lZCBpbiB0aGlz IGRyYWZ0Lg0KDQpDb21tZW50cyBmb3IgZGlzY3Vzc2lvbiBvbiB0aGlzIGRyYWZ0Og0KDQoxLiBB YnN0cmFjdA0KDQo8cXVvdGU+IFRoZSBhdHRyaWJ1dGVzLCB3aGljaCBhcmUNCnVzZWQgZm9yIGF1 dGhvcml6YXRpb24gYW5kIGFjY291bnRpbmcsIGVuYWJsZSBhc3NpZ25tZW50IG9mIGEgaG9zdA0K SVB2NiBhZGRyZXNzIGFuZCBJUHY2IEROUyBzZXJ2ZXIgYWRkcmVzcyB2aWEgREhDUHY2OyAuLi4g PC9xdW90ZT4NCg0KUGVyIHRoZSBzZWN0aW9uIDEgJiAyLjIsIEROUy1TZXJ2ZXItSVB2Ni1BZGRy ZXNzIGlzIG5vdCBvbmx5IHVzZWQgYnkgREhDUHY2LCBidXQgYWxzbyBieSBSQS4gUmlnaHQ/DQoN Cg0KMi4gSW50cm9kdWN0aW9uDQo8cXVvdGU+IEFzc2lnbm1lbnQgb2YgYW4gSVB2NiBETlMgc2Vy dmVyIGFkZHJlc3MsIHZpYSBESENQdjYgb3IgW1JGQzUwMDZdLiA8L3F1b3RlPg0KMi4yICBSZWN1 cnNpdmUgRE5TIFNlcnZlcnMNCjxxdW90ZT5UaGUgSVB2NiBhZGRyZXNzIG9mIGEgRE5TIHNlcnZl ciBjYW4gYWxzbw0KYmUgY29udmV5ZWQgdG8gdGhlIGhvc3QgdXNpbmcgSUNNUHY2IHdpdGggUm91 dGVyIEFkdmVydGlzZW1lbnRzLCB2aWENCnRoZSBleHBlcmltZW50YWwgW1JGQzUwMDZdIG9wdGlv bi4gPC9xdW90ZT4NCg0KUkZDNTAwNiBoYXMgb2Jzb2xldGVkIGJ5IFJGQzYxMDYuDQoNCg0KMy4g RGVwbG95bWVudCBTY2VuYXJpb3MNCg0KPHF1b3RlPi4uLkZpZ3VyZSAxLiBJdA0KaXMgY29tcG9z ZWQgb2YgYSBJUCBSb3V0aW5nIFJlc2lkZW50aWFsIEdhdGV3YXkgKFJHKSBvciBob3N0LCBhIExh eWVyDQoyIEFjY2Vzcy1Ob2RlIChlLmcuIGEgRFNMQU0pLCBvbmUgb3IgbW9yZSBJUCBOZXR3b3Jr IEFjY2VzcyBTZXJ2ZXJzDQooTkFTZXMpLCBhbmQgYW4gQUFBIHNlcnZlci4gVGhlIFJHIG9yIGhv c3QgY2FuIGJlIGV4cGVjdGVkIHRvIGJlDQptdWx0aSBob21lZCB0byBvbmUgb3IgbW9yZSBOQVNl cy4gPC9xdW90ZT4NCg0KSSBjYW4ndCBmaW5kIG11bHRpcGxlIE5BU2VzIGluIHRoZSBGaWcuIDEu DQoNCjxxdW90ZT4uLi5GaWd1cmUgMTwvcXVvdGU+DQoNCkNhbiB0aGUgZGVub3RhdGlvbiBvZiBB TiBiZSByZXBsYWNlZCBieSAoTGF5ZXItMiBicm9hZGJhbmQpIEFjY2VzcyBOZXR3b3JrIGFuZCB3 ZSBkb24ndCBtZW50aW9uIChEU0wpIGFuZCAoRXRoZXJuZXQpIGluIEZpZy4xPw0KDQoNCjIuMSBJ UHY2IEFkZHJlc3MgQXNzaWdubWVudA0KDQo8cXVvdGU+REhDUHY2IFtSRkMzMzE1XSBwcm92aWRl cyBhIG1lY2hhbmlzbSB0byBhc3NpZ24gb25lIG9yIG1vcmUgb3Igbm9uLXRlbXBvcmFyeQ0KSVB2 NiBhZGRyZXNzZXMgdG8gaG9zdHMuIDwvcXVvdGU+DQoNClR5cG8gLSAxIG1vcmUgJ29yJyBpbiB0 aGUgYWJvdmUgc2VudGVuY2UuDQoNCg0KMi40ICBEZWxlZ2F0ZWQgSVB2NiBQcmVmaXggUG9vbA0K DQo8cXVvdGU+U2luY2UgREhDUHY2IFByZWZpeCBEZWxlZ2F0aW9uIGNhbiBjb25jZWl2YWJseSBi ZSB1c2VkIG9uIHRoZSBzYW1lDQpuZXR3b3JrIGFzIFNMQUFDLCBpdCBpcyBwb3NzaWJsZSBmb3Ig dGhlIERlbGVnYXRlZC1JUHY2LVByZWZpeC1Qb29sDQphbmQgRnJhbWVkLUlQdjYtUG9vbCBhdHRy aWJ1dGVzIHRvIGJlIGluY2x1ZGVkIHdpdGhpbiB0aGUgc2FtZQ0KcGFja2V0LiBUbyBhdm9pZCBh bWJpZ3VpdHkgaW4gdGhpcyBzY2VuYXJpbywgdXNlIG9mIHRoZSBEZWxlZ2F0ZWQtDQpJUHY2LVBy ZWZpeC1Qb29sIGF0dHJpYnV0ZSBzaG91bGQgYmUgcmVzdHJpY3RlZCB0byBhdXRob3JpemF0aW9u IGFuZA0KYWNjb3VudGluZyBvZiBwcmVmaXggcG9vbHMgdXNlZCBpbiBESENQdjYgUHJlZml4IERl bGVnYXRpb24gYW5kIHRoZQ0KRnJhbWVkLUlQdjYtUG9vbCBhdHRyaWJ1dGUgc2hvdWxkIGJlIHVz ZWQgZm9yIGF1dGhvcml6YXRpb24gYW5kDQphY2NvdW50aW5nIG9mIHByZWZpeCBwb29scyB1c2Vk IGluIFNMQUFDLiA8L3F1b3RlPg0KDQpJIGFtIHN0aWxsIG5vdCBzdXJlIHdoeSB3ZSBjYW4ndCB1 c2UgMnggRnJhbWVkLVBvb2wgKDg4IGRlZmluZWQgaW4gUkZDMjg2OSkgYXR0cmlidXRlcyBmb3Ig dGhpcyBjYXNlPyBPbmUgRnJhbWVkLVBvb2wgKDg4KSBpcyBmb3IgREhDUHY2LCB0aGUgb3RoZXIg RnJhbWVkLVBvb2wgKDg4KSBpcyBmb3IgU0xBQUMuDQoNCkkgcXVvdGUgdGhlIGRlc2NyaXB0aW9u IG9mICdGcmFtZWQtUG9vbCcgaW4gUkZDMjg2OSBoZXJlLCAnVGhpcyBBdHRyaWJ1dGUgY29udGFp bnMgdGhlIG5hbWUgb2YgYW4gYXNzaWduZWQgYWRkcmVzcyBwb29sIHRoYXQNClNIT1VMRCBiZSB1 c2VkIHRvIGFzc2lnbiBhbiBhZGRyZXNzIGZvciB0aGUgdXNlci4gSWYgYSBOQVMgZG9lcw0Kbm90 IHN1cHBvcnQgbXVsdGlwbGUgYWRkcmVzcyBwb29scywgdGhlIE5BUyBzaG91bGQgaWdub3JlIHRo aXMNCkF0dHJpYnV0ZS4gQWRkcmVzcyBwb29scyBhcmUgdXN1YWxseSB1c2VkIGZvciBJUCBhZGRy ZXNzZXMsIGJ1dA0KY2FuIGJlIHVzZWQgZm9yIG90aGVyIHByb3RvY29scyBpZiB0aGUgTkFTIHN1 cHBvcnRzIHBvb2xzIGZvcg0KdGhvc2UgcHJvdG9jb2xzLicNCg0KDQoyLjUgIFN0YXRlZnVsIElQ djYgYWRkcmVzcyBQb29sDQoNCkkgc3RpbGwgaGF2ZSBub3QgZ290IHRoZSByZWFzb24gd2h5IHdl IGNhbid0IHVzZSAnRnJhbWUtUG9vbCcgaW5zdGVhZCBvZiB0aGlzIG5ldyBhdHRyaWJ1dGUuDQoN Cg0KQmVzdCBSZWdhcmRzLA0KTGVhZg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG cm9tOiBqb3VuaSBrb3Job25lbiBbbWFpbHRvOmpvdW5pLm5vc3BhbUBnbWFpbC5jb21dIA0KU2Vu dDogTW9uZGF5LCBNYXkgMDcsIDIwMTIgMTA6MDEgUE0NClRvOiByYWRleHRAaWV0Zi5vcmcNCkNj OiBMZWFmIHllaDsgV29qY2llY2ggRGVjDQpTdWJqZWN0OiBSZTogSS1EIEFjdGlvbjogZHJhZnQt aWV0Zi1yYWRleHQtaXB2Ni1hY2Nlc3MtMDcudHh0DQoNCkZvbGtzLA0KDQpUaGUgSS1EIGhhcyBi ZWVuIHJldmlzZWQgdG8gcmVmbGVjdCB0aGUgY29tbWVudHMgcmVnYXJkaW5nIHRoZSANCmF0dHJp YnV0ZSBmb3JtYXQgYW5kIHRoZSBleGFtcGxlIGJyb2FkYmFuZCBuZXR3b3JrIHNjZW5hcmlvLg0K RXZlcnlib2R5IGhhcHB5IHdpdGggdGhlIGNoYW5nZXMgaW4gU2VjdGlvbnMgMiwgMi4zIGFuZCAz LjMgPw0KDQotIEpvdW5pICYgTWF1cmljaW8NCg0KDQpPbiBNYXkgNywgMjAxMiwgYXQgMzowMSBQ TSwgaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIHdyb3RlOg0KDQo+IA0KPiBBIE5ldyBJbnRlcm5l dC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGly ZWN0b3JpZXMuIFRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIFJBRElVUyBFWFRlbnNp b25zIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQo+IA0KPiAJVGl0bGUgICAgICAgICAgIDog UkFESVVTIGF0dHJpYnV0ZXMgZm9yIElQdjYgQWNjZXNzIE5ldHdvcmtzDQo+IAlBdXRob3Iocykg ICAgICAgOiBCZW5vaXQgTG91cmRlbGV0DQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBXb2pj aWVjaCBEZWMNCj4gICAgICAgICAgICAgICAgICAgICAgICAgIEJlaGNldCBTYXJpa2F5YQ0KPiAg ICAgICAgICAgICAgICAgICAgICAgICAgR2xlbiBab3JuDQo+ICAgICAgICAgICAgICAgICAgICAg ICAgICBEYXZpZCBNaWxlcw0KPiAJRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi1yYWRleHQt aXB2Ni1hY2Nlc3MtMDcudHh0DQo+IAlQYWdlcyAgICAgICAgICAgOiAxNA0KPiAJRGF0ZSAgICAg ICAgICAgIDogMjAxMi0wNS0wNw0KPiANCj4gICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhZGRp dGlvbmFsIElQdjYgUkFESVVTIGF0dHJpYnV0ZXMgdXNlZnVsIGluDQo+ICAgcmVzaWRlbnRpYWwg YnJvYWRiYW5kIG5ldHdvcmsgZGVwbG95bWVudHMuICBUaGUgYXR0cmlidXRlcywgd2hpY2ggYXJl DQo+ICAgdXNlZCBmb3IgYXV0aG9yaXphdGlvbiBhbmQgYWNjb3VudGluZywgZW5hYmxlIGFzc2ln bm1lbnQgb2YgYSBob3N0DQo+ICAgSVB2NiBhZGRyZXNzIGFuZCBJUHY2IEROUyBzZXJ2ZXIgYWRk cmVzcyB2aWEgREhDUHY2OyBhc3NpZ25tZW50IG9mIGFuDQo+ICAgSVB2NiByb3V0ZSBhbm5vdW5j ZWQgdmlhIHJvdXRlciBhZHZlcnRpc2VtZW50OyBhc3NpZ25tZW50IG9mIGEgbmFtZWQNCj4gICBJ UHY2IGRlbGVnYXRlZCBwcmVmaXggcG9vbDsgYW5kIGFzc2lnbm1lbnQgb2YgYSBuYW1lZCBJUHY2 IHBvb2wgZm9yDQo+ICAgaG9zdCBESENQdjYgYWRkcmVzc2luZy4NCj4gDQoNCg== From radext-bounces@ietf.org Fri May 11 03:48:13 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD8E21F85E5; Fri, 11 May 2012 03:48:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336733293; bh=rxXOIsDy3EdWa9PsVwmHWaZ2abY7RnLJGmWRDoiVmdw=; h=From:To:Date:Message-ID:References:In-Reply-To:MIME-Version:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=vR9OYgilcGMqFbSXv/az7gFs0NGCxizrnJfjdaPn4gaoUcdtXDAUBfdSfJo7glGVc ihxTrJ+fpinxEtnzJOLORK+G08uzr2RysRf2XASmhmm2wqyCCjE4HNiEkvOr72O63N tDuYz9rXSZuZj6RMFLVdQXPlMwwpDfejimniHNaE= 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 82D7621F85E5 for ; Fri, 11 May 2012 03:48:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.567 X-Spam-Level: X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599] 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 ykc0260eG8yd for ; Fri, 11 May 2012 03:48:10 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id BAAE221F8570 for ; Fri, 11 May 2012 03:48:10 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFV12054; Fri, 11 May 2012 06:48:10 -0400 (EDT) Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 May 2012 03:44:27 -0700 Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 May 2012 03:44:25 -0700 Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.168]) by szxeml413-hub.china.huawei.com ([10.82.67.152]) with mapi id 14.01.0323.003; Fri, 11 May 2012 18:44:23 +0800 From: Leaf yeh To: jouni korhonen , "radext@ietf.org" Thread-Topic: I-D Action: draft-ietf-radext-ipv6-access-07.txt Thread-Index: AQHNLFneQkQleKjX90CL1w6gppUCXZbETbjA Date: Fri, 11 May 2012 10:44:22 +0000 Message-ID: References: <20120507120127.8643.10103.idtracker@ietfa.amsl.com> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.70.39.132] MIME-Version: 1.0 X-CFilter-Loop: Reflected Cc: Wojciech Dec Subject: Re: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org I'd really like to see the advancing of this document, because I have a draft (http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-radius-opt/), which has turned to be draft-ietf, has referred to the attributes defined in this draft. Comments for discussion on this draft: 1. Abstract The attributes, which are used for authorization and accounting, enable assignment of a host IPv6 address and IPv6 DNS server address via DHCPv6; ... Per the section 1 & 2.2, DNS-Server-IPv6-Address is not only used by DHCPv6, but also by RA. Right? 2. Introduction Assignment of an IPv6 DNS server address, via DHCPv6 or [RFC5006]. 2.2 Recursive DNS Servers The IPv6 address of a DNS server can also be conveyed to the host using ICMPv6 with Router Advertisements, via the experimental [RFC5006] option. RFC5006 has obsoleted by RFC6106. 3. Deployment Scenarios ...Figure 1. It is composed of a IP Routing Residential Gateway (RG) or host, a Layer 2 Access-Node (e.g. a DSLAM), one or more IP Network Access Servers (NASes), and an AAA server. The RG or host can be expected to be multi homed to one or more NASes. I can't find multiple NASes in the Fig. 1. ...Figure 1 Can the denotation of AN be replaced by (Layer-2 broadband) Access Network and we don't mention (DSL) and (Ethernet) in Fig.1? 2.1 IPv6 Address Assignment DHCPv6 [RFC3315] provides a mechanism to assign one or more or non-temporary IPv6 addresses to hosts. Typo - 1 more 'or' in the above sentence. 2.4 Delegated IPv6 Prefix Pool Since DHCPv6 Prefix Delegation can conceivably be used on the same network as SLAAC, it is possible for the Delegated-IPv6-Prefix-Pool and Framed-IPv6-Pool attributes to be included within the same packet. To avoid ambiguity in this scenario, use of the Delegated- IPv6-Prefix-Pool attribute should be restricted to authorization and accounting of prefix pools used in DHCPv6 Prefix Delegation and the Framed-IPv6-Pool attribute should be used for authorization and accounting of prefix pools used in SLAAC. I am still not sure why we can't use 2x Framed-Pool (88 defined in RFC2869) attributes for this case? One Framed-Pool (88) is for DHCPv6, the other Framed-Pool (88) is for SLAAC. I quote the description of 'Framed-Pool' in RFC2869 here, 'This Attribute contains the name of an assigned address pool that SHOULD be used to assign an address for the user. If a NAS does not support multiple address pools, the NAS should ignore this Attribute. Address pools are usually used for IP addresses, but can be used for other protocols if the NAS supports pools for those protocols.' 2.5 Stateful IPv6 address Pool I still have not got the reason why we can't use 'Frame-Pool' instead of this new attribute. Best Regards, Leaf -----Original Message----- From: jouni korhonen [mailto:jouni.nospam@gmail.com] Sent: Monday, May 07, 2012 10:01 PM To: radext@ietf.org Cc: Leaf yeh; Wojciech Dec Subject: Re: I-D Action: draft-ietf-radext-ipv6-access-07.txt Folks, The I-D has been revised to reflect the comments regarding the attribute format and the example broadband network scenario. Everybody happy with the changes in Sections 2, 2.3 and 3.3 ? - Jouni & Mauricio On May 7, 2012, at 3:01 PM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RADIUS EXTensions Working Group of the IETF. > > Title : RADIUS attributes for IPv6 Access Networks > Author(s) : Benoit Lourdelet > Wojciech Dec > Behcet Sarikaya > Glen Zorn > David Miles > Filename : draft-ietf-radext-ipv6-access-07.txt > Pages : 14 > Date : 2012-05-07 > > This document specifies additional IPv6 RADIUS attributes useful in > residential broadband network deployments. The attributes, which are > used for authorization and accounting, enable assignment of a host > IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an > IPv6 route announced via router advertisement; assignment of a named > IPv6 delegated prefix pool; and assignment of a named IPv6 pool for > host DHCPv6 addressing. > _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Fri May 11 04:28:16 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E5521F860B; Fri, 11 May 2012 04:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336735696; bh=LtIf7FBtZvnqg3ldZNMZ213sZo6152nyeXn5AA2twh0=; h=Date:From:To:Message-ID:In-Reply-To:Mime-version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=y7VzkonB/RJ5MwjCISriqqutJ3ZVZOkwFQeL7NrlhYQZnTADbu4y/M8+ZeadN8nv+ 37vjin4rWaqIKMFwMOAOEHT/qR2QRTOGGGE7dbRtm4TU2SYUMavHLnu0dyXgpQDEYD FBw92ieFJLlaslsryntQ0uEdeGjCmj+lbMOmnIew= 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 7830921F860B for ; Fri, 11 May 2012 04:28:15 -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, 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 daKAMAo0xxVU for ; Fri, 11 May 2012 04:28:14 -0700 (PDT) Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 85DF821F8606 for ; Fri, 11 May 2012 04:28:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wdec@cisco.com; l=2034; q=dns/txt; s=iport; t=1336735694; x=1337945294; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=vOtAh0RR5Elsr//wA0u0PQVOkruZUQSM9sXXg244nAA=; b=YQ2XZn/0c/FwGrebhYcEqc0FEK08p9UNQp2M4AICcm1fKUjCm4NCL7Tk xje1xRJpf38mpKZ3vNF2jIQZZRDQD7dKOExL6w3SLmzA1uCarA5B0+ake 3sukiN3QqTFRBVf9ETZMoFupCQuATHMQOsJ+Tigno4Xpkww3KM72n7SfE M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAOj2rE+Q/khL/2dsb2JhbABEsgcBAYIbgQeCFQEBAQMBEgEKHQIBMRANAQiBHQIEARIJGYdnBQuaeaAbixcZhgQElX2BEY1GgWmCa4Fd X-IronPort-AV: E=Sophos;i="4.75,570,1330905600"; d="scan'208";a="72976935" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 11 May 2012 11:28:13 +0000 Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q4BBSDjJ025222; Fri, 11 May 2012 11:28:13 GMT Received: from xmb-ams-112.cisco.com ([144.254.74.87]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 11 May 2012 13:28:13 +0200 Received: from 10.61.100.51 ([10.61.100.51]) by XMB-AMS-112.cisco.com ([144.254.74.87]) with Microsoft Exchange Server HTTP-DAV ; Fri, 11 May 2012 11:28:12 +0000 User-Agent: Microsoft-Entourage/12.32.0.111121 Date: Fri, 11 May 2012 13:28:09 +0200 From: Wojciech Dec To: Leaf yeh , jouni korhonen , "radext@ietf.org" Message-ID: Thread-Topic: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt Thread-Index: AQHNLFneQkQleKjX90CL1w6gppUCXZbETbjAgAAr3GA= In-Reply-To: Mime-version: 1.0 X-OriginalArrivalTime: 11 May 2012 11:28:13.0562 (UTC) FILETIME=[26FA45A0:01CD2F69] Subject: Re: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Hello Leaf, Thanks for your feedback. We'll make the necessary editorial changes and resubmit the draft. Answering to some of your specific queries below, and also call for the chairs attention and guidance if appropriate here. On 11/05/2012 12:44, "Leaf yeh" wrote: > 2.4 Delegated IPv6 Prefix Pool > > Since DHCPv6 Prefix Delegation can conceivably be used on the same > network as SLAAC, it is possible for the Delegated-IPv6-Prefix-Pool > and Framed-IPv6-Pool attributes to be included within the same > packet. To avoid ambiguity in this scenario, use of the Delegated- > IPv6-Prefix-Pool attribute should be restricted to authorization and > accounting of prefix pools used in DHCPv6 Prefix Delegation and the > Framed-IPv6-Pool attribute should be used for authorization and > accounting of prefix pools used in SLAAC. > > I am still not sure why we can't use 2x Framed-Pool (88 defined in RFC2869) > attributes for this case? One Framed-Pool (88) is for DHCPv6, the other > Framed-Pool (88) is for SLAAC. This point and specific question has been discussed both on the mailing list and during the IETF 82 meeting and consensus established as per the meeting minutes (see point 2): http://tools.ietf.org/wg/radext/minutes?item=minutes82.html http://www.ietf.org/mail-archive/web/radext/current/msg02318.html > > I quote the description of 'Framed-Pool' in RFC2869 here, 'This Attribute > contains the name of an assigned address pool that > SHOULD be used to assign an address for the user. If a NAS does > not support multiple address pools, the NAS should ignore this > Attribute. Address pools are usually used for IP addresses, but > can be used for other protocols if the NAS supports pools for > those protocols.' > > > 2.5 Stateful IPv6 address Pool > > I still have not got the reason why we can't use 'Frame-Pool' instead of this > new attribute. This is the same question, and same answer applies. Thanks, Woj. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From wdec@cisco.com Fri May 11 04:28:15 2012 Return-Path: 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 7830921F860B for ; Fri, 11 May 2012 04:28:15 -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, 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 daKAMAo0xxVU for ; Fri, 11 May 2012 04:28:14 -0700 (PDT) Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 85DF821F8606 for ; Fri, 11 May 2012 04:28:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wdec@cisco.com; l=2034; q=dns/txt; s=iport; t=1336735694; x=1337945294; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=vOtAh0RR5Elsr//wA0u0PQVOkruZUQSM9sXXg244nAA=; b=YQ2XZn/0c/FwGrebhYcEqc0FEK08p9UNQp2M4AICcm1fKUjCm4NCL7Tk xje1xRJpf38mpKZ3vNF2jIQZZRDQD7dKOExL6w3SLmzA1uCarA5B0+ake 3sukiN3QqTFRBVf9ETZMoFupCQuATHMQOsJ+Tigno4Xpkww3KM72n7SfE M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAOj2rE+Q/khL/2dsb2JhbABEsgcBAYIbgQeCFQEBAQMBEgEKHQIBMRANAQiBHQIEARIJGYdnBQuaeaAbixcZhgQElX2BEY1GgWmCa4Fd X-IronPort-AV: E=Sophos;i="4.75,570,1330905600"; d="scan'208";a="72976935" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 11 May 2012 11:28:13 +0000 Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q4BBSDjJ025222; Fri, 11 May 2012 11:28:13 GMT Received: from xmb-ams-112.cisco.com ([144.254.74.87]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 11 May 2012 13:28:13 +0200 Received: from 10.61.100.51 ([10.61.100.51]) by XMB-AMS-112.cisco.com ([144.254.74.87]) with Microsoft Exchange Server HTTP-DAV ; Fri, 11 May 2012 11:28:12 +0000 User-Agent: Microsoft-Entourage/12.32.0.111121 Date: Fri, 11 May 2012 13:28:09 +0200 From: Wojciech Dec To: Leaf yeh , jouni korhonen , "radext@ietf.org" Message-ID: Thread-Topic: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt Thread-Index: AQHNLFneQkQleKjX90CL1w6gppUCXZbETbjAgAAr3GA= In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 May 2012 11:28:13.0562 (UTC) FILETIME=[26FA45A0:01CD2F69] Subject: Re: [radext] I-D Action: draft-ietf-radext-ipv6-access-07.txt X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2012 11:28:15 -0000 Hello Leaf, Thanks for your feedback. We'll make the necessary editorial changes and resubmit the draft. Answering to some of your specific queries below, and also call for the chairs attention and guidance if appropriate here. On 11/05/2012 12:44, "Leaf yeh" wrote: > 2.4 Delegated IPv6 Prefix Pool > > Since DHCPv6 Prefix Delegation can conceivably be used on the same > network as SLAAC, it is possible for the Delegated-IPv6-Prefix-Pool > and Framed-IPv6-Pool attributes to be included within the same > packet. To avoid ambiguity in this scenario, use of the Delegated- > IPv6-Prefix-Pool attribute should be restricted to authorization and > accounting of prefix pools used in DHCPv6 Prefix Delegation and the > Framed-IPv6-Pool attribute should be used for authorization and > accounting of prefix pools used in SLAAC. > > I am still not sure why we can't use 2x Framed-Pool (88 defined in RFC2869) > attributes for this case? One Framed-Pool (88) is for DHCPv6, the other > Framed-Pool (88) is for SLAAC. This point and specific question has been discussed both on the mailing list and during the IETF 82 meeting and consensus established as per the meeting minutes (see point 2): http://tools.ietf.org/wg/radext/minutes?item=minutes82.html http://www.ietf.org/mail-archive/web/radext/current/msg02318.html > > I quote the description of 'Framed-Pool' in RFC2869 here, 'This Attribute > contains the name of an assigned address pool that > SHOULD be used to assign an address for the user. If a NAS does > not support multiple address pools, the NAS should ignore this > Attribute. Address pools are usually used for IP addresses, but > can be used for other protocols if the NAS supports pools for > those protocols.' > > > 2.5 Stateful IPv6 address Pool > > I still have not got the reason why we can't use 'Frame-Pool' instead of this > new attribute. This is the same question, and same answer applies. Thanks, Woj. From jsalowey@cisco.com Mon May 14 13:04:24 2012 Return-Path: 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 4726021F8864 for ; Mon, 14 May 2012 13:04:24 -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 0hn8Qkr-AYkZ for ; Mon, 14 May 2012 13:04:23 -0700 (PDT) Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 70C5B21F885E for ; Mon, 14 May 2012 13:04:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsalowey@cisco.com; l=4869; q=dns/txt; s=iport; t=1337025863; x=1338235463; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=2Y3Q/Y2QXuE/ESVS2WGPq3hYN1C8HJ56sn0bHLX7BXs=; b=B2Crb4mgbFJ49tGH2JRP50htsuM2MlFBSXDdfAn3v3pQ9VabnWuTL2A/ VZkI2jq+LMyKG8mJDkF2hCOt7mP8tkNne8638h3EL+XpLZ99mis/oQj0a YiXzX8dPRWL9ExaaHouN8fJdUt0pPMWyERf6vHGUGPjNWm4VfG4q0II7T c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMFAN1jsU+rRDoI/2dsb2JhbABEgx6wVYEHghUBAQEDAQEBAQ8BWwsQCw4XIScwBhMih2cEDJpwn20EixoThQpjBIhkiS6Da4V1iGKBaYMJgTY X-IronPort-AV: E=Sophos;i="4.75,588,1330905600"; d="scan'208";a="41649084" Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 14 May 2012 20:02:07 +0000 Received: from [10.33.251.111] ([10.33.251.111]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q4EK25W1028136; Mon, 14 May 2012 20:02:06 GMT Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: Joe Salowey In-Reply-To: <20120508223521.GA20470@w1.fi> Date: Mon, 14 May 2012 13:02:08 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> <20120508223521.GA20470@w1.fi> To: Jouni Malinen X-Mailer: Apple Mail (2.1084) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 20:04:24 -0000 Hi Jouni, Thanks for the comments. Response inline below. Cheers, Joe On May 8, 2012, at 3:35 PM, Jouni Malinen wrote: >> 2.9. WLAN-Reason-Code >=20 >> A summary of the WLAN-Reason-Code Attribute format is shown below. = The fields are transmitted from left to right. >>=20 >> 0 1 2 3=20 >> 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 | Value | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 >> The Value field is two octets containing a 16-bit unsigned integer = drawn from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The = value=92s least significant octet is contained in bits 23-16 and most = significant octet in bits 31-24 (network octet order). Note: not all = reason codes defined in the Table 8-36 are expected to be used by an AS. >=20 > Hmm.. Is this really suggesting a RADIUS attribute that is using = little > endian byte order? Aren't pretty pretty much all other RADIUS = attributes > defined using big endian byte order? While I can understand that this > comes from the IEEE 802.11 side where the Reason Code is indeed little > endian, this type of difference between RADIUS attributes is just = asking > for issues.. >=20 [Joe] I think I agree that we need to be specific about the byte order = and I agree that we should be using big-endian order.=20 >> [Note]: the importance of including this attribute is for = authentication and authorization of mobile devices in public Wi-Fi = access; it is important to inform the mobile when authorization is = denied, even though authentication may have been successful. This can = occur for AS policy reasons or for reasons related to the user=92s = subscription. The following Reason codes for public Wi-Fi access = networks were added by the IEEE 802.11u-2011 amendment: >=20 > That IEEE 802.11u-2011 reference should be replaced with a reference = to > IEEE Std 802.11-2012. >=20 >> Reason >> Value Description >> 27 Disassociated because session terminated by SP request >> 28 Disassociated because of lack of SP roaming agreement >> 29 Requested service rejected because of SP cipher suite or AKM = requirement >> 30 Requested service not authorized in this location >=20 > Is Reason Code the best place for sending this information? It is a = bit > difficult to extend this with any new potentially needed value while > something like EAP notifications could be work better for this. >=20 [Joe] I think there is a tradeoff here. THere is a field already = defined for this in 802.11 that can be extended with existing error = codes. These error codes are can be used by the mobile in whatever way = it fits. EAP notifications are limited to text strings for display = which limits how the mobile can use them and introduces language and = encoding issues. =20 >> 2.10. WLAN-Pairwise-Cipher >>=20 >> Description >>=20 >> The WLAN-Pairwise-Cipher Attribute contains information on the = pairwise cipher suite used to establish the robust security network = association (RSNA) between the AP and mobile device. >>=20 >> A WLAN-Pairwise-Cipher Attribute SHOULD be included within an = Access-Request packet. A summary of the WLAN-Pairwise-Cipher Attribute = format is shown below. The fields are transmitted from left to right. >=20 > Is there some general text pointing out that these attributes are > applicable only for the case of IEEE 802.11 networks? This SHOULD > statement could be interpreted as a strong recommendation for any NAS = to > include the attribute while it should really only apply to the case > where the connection is an IEEE 802.11 RSNA. >=20 [Joe] Good point.=20 >> 2.11. WLAN-Group-Cipher >>=20 >> Description >>=20 >> The WLAN-Group-Cipher Attribute contains information on the group = cipher suite used to establish the robust security network association = (RSNA) between the AP and mobile device. >=20 > If we are adding this, we could as well add WLAN-Group-Mgmt-Cipher = from > IEEE 802.11w (now in IEEE Std 802.11-2012) to cover the case of > protected management frames. Though, this would also need another > attribute to indicate whether the station negotiated use of the > mechanism. >=20 [Joe] We can add this. Why couldn't the presence of the attribute be = used to indicate that the station negotiated use of the mechanism? > --=20 > Jouni Malinen PGP id = EFC895FA > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Mon May 14 13:04:26 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F32821F8864; Mon, 14 May 2012 13:04:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337025866; bh=r5/7fbNLlmqlI+DJi7Vh12Zh0OVy4OnAxGVlcrb7nYM=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=aUOsZBha54iPk6a/NHUpFSRTJkqdxmWDvNFgfuR6RbOv9LZnAj/1qy90PCF0/a76T CL064G4eebA9NyCbCFWYBpkEC5mF56H9DInsnPjaBfVvQ+HKQxXu8EaYNu6kbPfA5s E9YLTdXDJx9A3QRqS1YBhV+nGHKA6omhJ83tzaWc= 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 4726021F8864 for ; Mon, 14 May 2012 13:04:24 -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 0hn8Qkr-AYkZ for ; Mon, 14 May 2012 13:04:23 -0700 (PDT) Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 70C5B21F885E for ; Mon, 14 May 2012 13:04:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsalowey@cisco.com; l=4869; q=dns/txt; s=iport; t=1337025863; x=1338235463; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=2Y3Q/Y2QXuE/ESVS2WGPq3hYN1C8HJ56sn0bHLX7BXs=; b=B2Crb4mgbFJ49tGH2JRP50htsuM2MlFBSXDdfAn3v3pQ9VabnWuTL2A/ VZkI2jq+LMyKG8mJDkF2hCOt7mP8tkNne8638h3EL+XpLZ99mis/oQj0a YiXzX8dPRWL9ExaaHouN8fJdUt0pPMWyERf6vHGUGPjNWm4VfG4q0II7T c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMFAN1jsU+rRDoI/2dsb2JhbABEgx6wVYEHghUBAQEDAQEBAQ8BWwsQCw4XIScwBhMih2cEDJpwn20EixoThQpjBIhkiS6Da4V1iGKBaYMJgTY X-IronPort-AV: E=Sophos;i="4.75,588,1330905600"; d="scan'208";a="41649084" Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 14 May 2012 20:02:07 +0000 Received: from [10.33.251.111] ([10.33.251.111]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q4EK25W1028136; Mon, 14 May 2012 20:02:06 GMT Mime-Version: 1.0 (Apple Message framework v1084) From: Joe Salowey In-Reply-To: <20120508223521.GA20470@w1.fi> Date: Mon, 14 May 2012 13:02:08 -0700 Message-Id: References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> <20120508223521.GA20470@w1.fi> To: Jouni Malinen X-Mailer: Apple Mail (2.1084) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Hi Jouni, Thanks for the comments. Response inline below. Cheers, Joe On May 8, 2012, at 3:35 PM, Jouni Malinen wrote: >> 2.9. WLAN-Reason-Code > = >> A summary of the WLAN-Reason-Code 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 | Value | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > = >> The Value field is two octets containing a 16-bit unsigned integer drawn= from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The value=92s leas= t significant octet is contained in bits 23-16 and most significant octet i= n bits 31-24 (network octet order). Note: not all reason codes defined in = the Table 8-36 are expected to be used by an AS. > = > Hmm.. Is this really suggesting a RADIUS attribute that is using little > endian byte order? Aren't pretty pretty much all other RADIUS attributes > defined using big endian byte order? While I can understand that this > comes from the IEEE 802.11 side where the Reason Code is indeed little > endian, this type of difference between RADIUS attributes is just asking > for issues.. > = [Joe] I think I agree that we need to be specific about the byte order an= d I agree that we should be using big-endian order. = >> [Note]: the importance of including this attribute is for authentication= and authorization of mobile devices in public Wi-Fi access; it is importan= t to inform the mobile when authorization is denied, even though authentica= tion may have been successful. This can occur for AS policy reasons or for= reasons related to the user=92s subscription. The following Reason codes = for public Wi-Fi access networks were added by the IEEE 802.11u-2011 amendm= ent: > = > That IEEE 802.11u-2011 reference should be replaced with a reference to > IEEE Std 802.11-2012. > = >> Reason >> Value Description >> 27 Disassociated because session terminated by SP request >> 28 Disassociated because of lack of SP roaming agreement >> 29 Requested service rejected because of SP cipher suite or AKM req= uirement >> 30 Requested service not authorized in this location > = > Is Reason Code the best place for sending this information? It is a bit > difficult to extend this with any new potentially needed value while > something like EAP notifications could be work better for this. > = [Joe] I think there is a tradeoff here. THere is a field already defined = for this in 802.11 that can be extended with existing error codes. These e= rror codes are can be used by the mobile in whatever way it fits. EAP no= tifications are limited to text strings for display which limits how the mo= bile can use them and introduces language and encoding issues. = >> 2.10. WLAN-Pairwise-Cipher >> = >> Description >> = >> The WLAN-Pairwise-Cipher Attribute contains information on the pairwise = cipher suite used to establish the robust security network association (RSN= A) between the AP and mobile device. >> = >> A WLAN-Pairwise-Cipher Attribute SHOULD be included within an Access-Req= uest packet. A summary of the WLAN-Pairwise-Cipher Attribute format is sho= wn below. The fields are transmitted from left to right. > = > Is there some general text pointing out that these attributes are > applicable only for the case of IEEE 802.11 networks? This SHOULD > statement could be interpreted as a strong recommendation for any NAS to > include the attribute while it should really only apply to the case > where the connection is an IEEE 802.11 RSNA. > = [Joe] Good point. = >> 2.11. WLAN-Group-Cipher >> = >> Description >> = >> The WLAN-Group-Cipher Attribute contains information on the group cipher= suite used to establish the robust security network association (RSNA) bet= ween the AP and mobile device. > = > If we are adding this, we could as well add WLAN-Group-Mgmt-Cipher from > IEEE 802.11w (now in IEEE Std 802.11-2012) to cover the case of > protected management frames. Though, this would also need another > attribute to indicate whether the station negotiated use of the > mechanism. > = [Joe] We can add this. Why couldn't the presence of the attribute be used = to indicate that the station negotiated use of the mechanism? > -- = > Jouni Malinen PGP id EFC895FA > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From jsalowey@cisco.com Mon May 14 13:13:54 2012 Return-Path: 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 5AAF021F8897 for ; Mon, 14 May 2012 13:13:54 -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 CJSugjEIpAKD for ; Mon, 14 May 2012 13:13:53 -0700 (PDT) Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 8569B21F8892 for ; Mon, 14 May 2012 13:13:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsalowey@cisco.com; l=2410; q=dns/txt; s=iport; t=1337026433; x=1338236033; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=IoufyycdnNkQj6TFq+HPLJJIRj5XKUX7JSLwzhHDvMk=; b=gm7RO3v4iB+V4VLHh+td5xpJtAbK+T3QCIx5iCagCo3R+xIwHfU8sKaW C97B5V8sBI201PCWu7uCqFo163WVTwVDmBYETeJW7QHom27JYUOnuIB3h OuYB+/ZjxvQZjIKtY/E4D4qjsBrAYJJvrfVq/vnsVO8C/t608GJUFtl2y 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMFADBnsU+rRDoH/2dsb2JhbABEgx6wVYEHghUBAQEDAQEBAQ8BJzQDCAULC0YnMAYTIodnBAyaZp9wixqFHWMEiGSNGYERhGSIYoFpgwk X-IronPort-AV: E=Sophos;i="4.75,588,1330905600"; d="scan'208";a="42189202" Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 14 May 2012 20:13:53 +0000 Received: from [10.33.251.111] ([10.33.251.111]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q4EKDJgj020722; Mon, 14 May 2012 20:13:52 GMT Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Joe Salowey In-Reply-To: Date: Mon, 14 May 2012 13:13:55 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> To: "" X-Mailer: Apple Mail (2.1084) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 20:13:54 -0000 Hi Lionel, Thanks for the quick review, responses below. Cheers, Joe On May 8, 2012, at 6:06 PM, = wrote: > Here are some questions/comments on these proposed attributes. >=20 > Regards, >=20 > Lionel >=20 > 2.9. WLAN-Reason-Code >=20 > [Lionel] what about reusing Message-Reply attribute in Access-Reject = and > define additional values for Acct-Terminate-Cause used in > Disconnect-Reject (as described in > http://tools.ietf.org/html/rfc3580#section-2.1) ? =20 >=20 [Joe] We could overload the message-reply attribute, but we would need = to define how to map the text in the message-reply attribute into the = 802.11 response. It seemed better to use a new attribute for this. =20 >=20 > 2.10. WLAN-Pairwise-Cipher=20 > 2.11. WLAN-Group-Cipher > 2.12. WLAN-AKM-Suite >=20 > [Lionel] If my understanding is correct, it is expected that the AAA > server could reject the access authorization request based on these > attributes describing the existing RSNA between the AP and mobile = node. > If the resulting RSNA is not suitable for the SP, I'm not sure if that > this is something that should/could be managed per user authorization > request but rather via local policies or SLA between partners. =20 >=20 [Joe] I think this information would be useful for both enterprise and = SP AAA. I think that you are correct that in many cases the policy = would not be varied on a per user basis, Even if per-user = authorization is not used, it is still useful to know what ciphers are = negotiated for auditing and channel bindings. >=20 > 2.12. WLAN-RF-Band >=20 > The WLAN-RF-Band Attribute contains information on the RF band used by > the AP for transmission and reception of information to and from the > mobile device. This information can be used, for example, to provide = a > relative quality of experience indication for the mobile device's user > (i.e., some RF bands have more interference than others). >=20 > [Lionel] if it is an indication for the user, why is it intended to > provide this information to the AAA server? >=20 [Joe] Good question. I think that text is erroneous and should be = removed. =20 > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Mon May 14 13:13:55 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64A9421F8897; Mon, 14 May 2012 13:13:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337026435; bh=0knhkIJ+wStAK2lucU4teV6hLGNOr8t43OnSx1wY4aQ=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=bki+8SuCb2qvJJ3hyUzdI5lCX/dNUWWgQK2D5jUajguEEhNoTiEU0PYP5hf2RzRjT FQCDkbNLtcumHF2uQF/4ALLyKHRWcRP5tsNgnFRt30vZIIgW9ESStMcJMdXST2npbM nGjokfE7NFCac7rit6uqtqhKBQgxTE1zUp+hJFAg= 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 5AAF021F8897 for ; Mon, 14 May 2012 13:13:54 -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 CJSugjEIpAKD for ; Mon, 14 May 2012 13:13:53 -0700 (PDT) Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 8569B21F8892 for ; Mon, 14 May 2012 13:13:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsalowey@cisco.com; l=2410; q=dns/txt; s=iport; t=1337026433; x=1338236033; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=IoufyycdnNkQj6TFq+HPLJJIRj5XKUX7JSLwzhHDvMk=; b=gm7RO3v4iB+V4VLHh+td5xpJtAbK+T3QCIx5iCagCo3R+xIwHfU8sKaW C97B5V8sBI201PCWu7uCqFo163WVTwVDmBYETeJW7QHom27JYUOnuIB3h OuYB+/ZjxvQZjIKtY/E4D4qjsBrAYJJvrfVq/vnsVO8C/t608GJUFtl2y 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMFADBnsU+rRDoH/2dsb2JhbABEgx6wVYEHghUBAQEDAQEBAQ8BJzQDCAULC0YnMAYTIodnBAyaZp9wixqFHWMEiGSNGYERhGSIYoFpgwk X-IronPort-AV: E=Sophos;i="4.75,588,1330905600"; d="scan'208";a="42189202" Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 14 May 2012 20:13:53 +0000 Received: from [10.33.251.111] ([10.33.251.111]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q4EKDJgj020722; Mon, 14 May 2012 20:13:52 GMT Mime-Version: 1.0 (Apple Message framework v1084) From: Joe Salowey In-Reply-To: Date: Mon, 14 May 2012 13:13:55 -0700 Message-Id: References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> To: "" X-Mailer: Apple Mail (2.1084) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Hi Lionel, Thanks for the quick review, responses below. Cheers, Joe On May 8, 2012, at 6:06 PM, wrote: > Here are some questions/comments on these proposed attributes. > > Regards, > > Lionel > > 2.9. WLAN-Reason-Code > > [Lionel] what about reusing Message-Reply attribute in Access-Reject and > define additional values for Acct-Terminate-Cause used in > Disconnect-Reject (as described in > http://tools.ietf.org/html/rfc3580#section-2.1) ? > [Joe] We could overload the message-reply attribute, but we would need to define how to map the text in the message-reply attribute into the 802.11 response. It seemed better to use a new attribute for this. > > 2.10. WLAN-Pairwise-Cipher > 2.11. WLAN-Group-Cipher > 2.12. WLAN-AKM-Suite > > [Lionel] If my understanding is correct, it is expected that the AAA > server could reject the access authorization request based on these > attributes describing the existing RSNA between the AP and mobile node. > If the resulting RSNA is not suitable for the SP, I'm not sure if that > this is something that should/could be managed per user authorization > request but rather via local policies or SLA between partners. > [Joe] I think this information would be useful for both enterprise and SP AAA. I think that you are correct that in many cases the policy would not be varied on a per user basis, Even if per-user authorization is not used, it is still useful to know what ciphers are negotiated for auditing and channel bindings. > > 2.12. WLAN-RF-Band > > The WLAN-RF-Band Attribute contains information on the RF band used by > the AP for transmission and reception of information to and from the > mobile device. This information can be used, for example, to provide a > relative quality of experience indication for the mobile device's user > (i.e., some RF bands have more interference than others). > > [Lionel] if it is an indication for the user, why is it intended to > provide this information to the AAA server? > [Joe] Good question. I think that text is erroneous and should be removed. > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From j@w1.fi Mon May 14 13:50:07 2012 Return-Path: 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 B40AE21F886F for ; Mon, 14 May 2012 13:50:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 IY74rCoiViaV for ; Mon, 14 May 2012 13:50:06 -0700 (PDT) Received: from jmaline2.user.openhosting.com (kvm.w1.fi [128.177.28.162]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCEA21F8851 for ; Mon, 14 May 2012 13:50:06 -0700 (PDT) Received: from jm (airband-63-133-138-149.airband.net [63.133.138.149] (may be forged)) (authenticated bits=0) by jmaline2.user.openhosting.com (8.13.8/8.13.8) with ESMTP id q4EKlLmr001805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2012 16:47:21 -0400 Received: by jm (sSMTP sendmail emulation); Mon, 14 May 2012 16:49:55 -0400 Date: Mon, 14 May 2012 16:49:55 -0400 From: Jouni Malinen To: Joe Salowey Message-ID: <20120514204955.GA5721@w1.fi> References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> <20120508223521.GA20470@w1.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 20:50:08 -0000 On Mon, May 14, 2012 at 01:02:08PM -0700, Joe Salowey wrote: > >> 2.11. WLAN-Group-Cipher > > If we are adding this, we could as well add WLAN-Group-Mgmt-Cipher from > > IEEE 802.11w (now in IEEE Std 802.11-2012) to cover the case of > > protected management frames. Though, this would also need another > > attribute to indicate whether the station negotiated use of the > > mechanism. > [Joe] We can add this. Why couldn't the presence of the attribute be used to indicate that the station negotiated use of the mechanism? It could. Though, it would be a bit confusing in this particular case since the group management cipher suite is an attribute of the BSS (AP configuration) while the negotiation here is referring to whether the station negotiated to use management frame protection during association. -- Jouni Malinen PGP id EFC895FA From radext-bounces@ietf.org Mon May 14 13:50:09 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B824E21F8877; Mon, 14 May 2012 13:50:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337028609; bh=4fURdpDEqceApKbULQaiqGpvIKNjEI+Sc6qPnCr6bEY=; h=Date:From:To:Message-ID:References:MIME-Version:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=wVi7u2TfvA8fFsi69krPKrz7bZ4lNNvwSPB+VS9sucsb+014P8YUMG9R5CupMdJfQ repPFw6eWUJvAZeYVALhrO0DDRK0+4620Em0FTba+O2II+V9leB5K/OqLIkexlVuyT ybpfYY/+jpTKs7eyJ3mlkEoa3NE9HAiov9oypOE8= 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 B40AE21F886F for ; Mon, 14 May 2012 13:50:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] 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 IY74rCoiViaV for ; Mon, 14 May 2012 13:50:06 -0700 (PDT) Received: from jmaline2.user.openhosting.com (kvm.w1.fi [128.177.28.162]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCEA21F8851 for ; Mon, 14 May 2012 13:50:06 -0700 (PDT) Received: from jm (airband-63-133-138-149.airband.net [63.133.138.149] (may be forged)) (authenticated bits=0) by jmaline2.user.openhosting.com (8.13.8/8.13.8) with ESMTP id q4EKlLmr001805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2012 16:47:21 -0400 Received: by jm (sSMTP sendmail emulation); Mon, 14 May 2012 16:49:55 -0400 Date: Mon, 14 May 2012 16:49:55 -0400 From: Jouni Malinen To: Joe Salowey Message-ID: <20120514204955.GA5721@w1.fi> References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> <20120508223521.GA20470@w1.fi> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org On Mon, May 14, 2012 at 01:02:08PM -0700, Joe Salowey wrote: > >> 2.11. WLAN-Group-Cipher > > If we are adding this, we could as well add WLAN-Group-Mgmt-Cipher from > > IEEE 802.11w (now in IEEE Std 802.11-2012) to cover the case of > > protected management frames. Though, this would also need another > > attribute to indicate whether the station negotiated use of the > > mechanism. > [Joe] We can add this. Why couldn't the presence of the attribute be used to indicate that the station negotiated use of the mechanism? It could. Though, it would be a bit confusing in this particular case since the group management cipher suite is an attribute of the BSS (AP configuration) while the negotiation here is referring to whether the station negotiated to use management frame protection during association. -- Jouni Malinen PGP id EFC895FA _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From jouni.nospam@gmail.com Mon May 14 15:29:13 2012 Return-Path: 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 5F50221F847D for ; Mon, 14 May 2012 15:29:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 oyYI2ht1slDG for ; Mon, 14 May 2012 15:29:12 -0700 (PDT) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD9A21F843E for ; Mon, 14 May 2012 15:29:11 -0700 (PDT) Received: by lagv3 with SMTP id v3so2765891lag.31 for ; Mon, 14 May 2012 15:29:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=1NZFiAsbjUyxjSAEJGpn1skMRKNWvY/fmdYyMbCi2vw=; b=ds/6rBj2BQ09qLBqSo3tEdU9lz6/3NX8KjGQEhNl+6eT1RjZGxP6usao1FSTNKzPBE iu276Z/rVHoYKno7xkYGmmaISFJQLFJLLcxvKZButZ5HwTz0ReaqQZis2PPFC5jwmmNV Ha2pW2N82kBO1A78U37SCNKOv+rzkGuApG4PsnJilzfAlLTJbi+rDa9LKPMCiMbx9+po isnj0GhEn5KMn3ufKJcf0ad4erkJABM5VSjvWdU/Yp2n+GPNBx8kLwejHQnPRUfZ0B0Z vCvjyuWsuoZE6aRm03B4CAq1NNTbMdK9Ntr7vEEMr70cw5Do+z1Ie6ZuOdOeMwxJF0lO gP1w== Received: by 10.152.112.161 with SMTP id ir1mr10100290lab.13.1337034550968; Mon, 14 May 2012 15:29:10 -0700 (PDT) Received: from a88-114-71-183.elisa-laajakaista.fi (a88-114-71-183.elisa-laajakaista.fi. [88.114.71.183]) by mx.google.com with ESMTPS id mg19sm20836601lab.8.2012.05.14.15.29.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 May 2012 15:29:09 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: jouni korhonen In-Reply-To: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> Date: Tue, 15 May 2012 01:29:07 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <1C07F2D7-FE2F-4761-83FA-8A014556A8A6@gmail.com> References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> To: Joe Salowey X-Mailer: Apple Mail (2.1084) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 22:29:13 -0000 Jouni had a question regarding the SSID encoding: = http://www.ietf.org/mail-archive/web/radext/current/msg07538.html Do you think we need to indicate the SSID encoding? - the other Jouni On May 9, 2012, at 12:09 AM, Joe Salowey wrote: > I've received a few off list suggestions for additional RADIUS = attributes to add to RADIUS Attributes for IEEE 802 Networks. These = include >=20 > 1. WLAN-Reason-Code - used to transmit the reason for = authentication failure from AAA to AP in an Access-Reject. The code is = included in reason code of a Disassociation or De-authentication Frame > 2. WLAN-Pairwise-Cipher - communicates the negotiated pairwise = cipher from the AP to the AAA. > 3. WLAN-Group-Cipher - communicates the negotiated group cipher from = the AP to the AAA.=20 > 4. WLAN-AKM-Suite - contains information on the authentication and = key management suite negotiated buy the AP.=20 > 5. WLAN-RF-Band - contains information on the RF band used by the AP. = =20 >=20 > Below is suggested text for these attributes from Dave Stephenson: >=20 > Thanks, >=20 > Joe >=20 > 2.9. WLAN-Reason-Code >=20 > Description >=20 > The WLAN-Reason-Code Attribute contains information on the reason for = authorization failure subsequent to a mobile device=92s authentication = request towards a Wi-Fi access network. >=20 > A WLAN-Reason-Code Attribute MAY be included within an Access-Reject = or Disconnect-Request packet. Upon receipt of an Access-Reject packet, = the WLAN-Reason-Code value is copied by the Authenticator / AP into the = Reason code field of a Disassociation or Deauthentication frame (see = clause 8.3.3.4 and 8.3.3.12 respectively in IEEE 802.11-2012), which is = subsequently transmitted to the Supplicant / mobile device. A summary = of the WLAN-Reason-Code Attribute format is shown below. The fields are = transmitted from left to right. >=20 > 0 1 2 3=20 > 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 | Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Code > tbd8 >=20 > Length > =3D2 >=20 > Value > The Value field is two octets containing a 16-bit unsigned integer = drawn from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The = value=92s least significant octet is contained in bits 23-16 and most = significant octet in bits 31-24 (network octet order). Note: not all = reason codes defined in the Table 8-36 are expected to be used by an AS. >=20 > [Note]: the importance of including this attribute is for = authentication and authorization of mobile devices in public Wi-Fi = access; it is important to inform the mobile when authorization is = denied, even though authentication may have been successful. This can = occur for AS policy reasons or for reasons related to the user=92s = subscription. The following Reason codes for public Wi-Fi access = networks were added by the IEEE 802.11u-2011 amendment: >=20 > Reason > Code > Value Description > 27 Disassociated because session terminated by SP request > 28 Disassociated because of lack of SP roaming agreement > 29 Requested service rejected because of SP cipher suite or AKM = requirement > 30 Requested service not authorized in this location >=20 >=20 >=20 >=20 > 2.10. WLAN-Pairwise-Cipher >=20 > Description >=20 > The WLAN-Pairwise-Cipher Attribute contains information on the = pairwise cipher suite used to establish the robust security network = association (RSNA) between the AP and mobile device. >=20 > A WLAN-Pairwise-Cipher Attribute SHOULD be included within an = Access-Request packet. A summary of the WLAN-Pairwise-Cipher Attribute = format is shown below. The fields are transmitted from left to right. >=20 > 0 1 2 3=20 > 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 | Value =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Code > tbd9 >=20 > Length > =3D4 >=20 > Value > The Value field is four octets formatted in accordance with Figure = 8-187 with values drawn from Table 8-99 of IEEE 802.11-2012. >=20 >=20 >=20 >=20 > 2.11. WLAN-Group-Cipher >=20 > Description >=20 > The WLAN-Group-Cipher Attribute contains information on the group = cipher suite used to establish the robust security network association = (RSNA) between the AP and mobile device. >=20 > A WLAN-Group-Cipher Attribute SHOULD be included within an = Access-Request packet. A summary of the WLAN-Group-Cipher Attribute = format is shown below. The fields are transmitted from left to right. >=20 > 0 1 2 3=20 > 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 | Value =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Code > tbd10 >=20 > Length > =3D4 >=20 > Value > The Value field is four octets formatted in accordance with Figure = 8-187 with values drawn from Table 8-99 of IEEE 802.11-2012. >=20 >=20 >=20 >=20 > 2.12. WLAN-AKM-Suite >=20 > Description >=20 > The WLAN-AKM-Suite Attribute contains information on the = authentication and key management suite used to establish the robust = security network association (RSNA) between the AP and mobile device. >=20 > A WLAN-AKM-Suite Attribute SHOULD be included within an Access-Request = packet. A summary of the WLAN-AKM-Suite Attribute format is shown = below. The fields are transmitted from left to right. >=20 > 0 1 2 3=20 > 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 | Value =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Code > tbd11 >=20 > Length > =3D4 >=20 > Value > The Value field is four octets formatted in accordance with Figure = 8-187 with values drawn from Table 8-101 of IEEE 802.11-2012. >=20 >=20 >=20 >=20 > 2.12. WLAN-RF-Band >=20 > Description >=20 > The WLAN-RF-Band Attribute contains information on the RF band used by = the AP for transmission and reception of information to and from the = mobile device. This information can be used, for example, to provide a = relative quality of experience indication for the mobile device=92s user = (i.e., some RF bands have more interference than others). >=20 > A WLAN-RF-Band Attribute SHOULD be included within an Access-Request = packet. A summary of the WLAN-RF-Band Attribute format is shown below. = The fields are transmitted from left to right. >=20 > 0 1 2 3=20 > 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 | Value | Reserved | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Code > tbd12 >=20 > Length > =3D2 >=20 > Value > The Value field is 1 octet having a value chosen from the table below: > Band ID value Meaning > 0 TV white spaces > 1 Sub-1 GHz (excluding TV white spaces) > 2 2.4 GHz > 3 3.6 GHz > 4 4.9 and 5 GHz > 5 60 GHz > 6-255 Reserved >=20 >=20 > [Note]: this table was copied from IEEE 802.11ad-d5. I=92m not sure = of the relative publication dates of this internet draft and IEEE = 802.11ad-d5. Since it=92s generally not recommended to reference a = draft specification in an RFC, I=92ve copied the table. If we discover = that the IEEE document will be published in time, then we could deleted = the table and instead reference Table 8-53a in IEEE 802.11ad. >=20 >=20 >=20 > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Mon May 14 15:29:15 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3A5C21F847D; Mon, 14 May 2012 15:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337034555; bh=YxmeWFKvzwIf6EJgOUiLeXC9XgMe7gzHtwHLw3FML0c=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=nMTta69W9QUSfIEWFKx+yxf3pfLYQ5Ay/e0V1KybEAbvdZVkd51OEZZGc4oTpTIFa FWIttZTHQ/s8TMo4Xz1lULPIghTZG7JvoWpksfwOjdv59tG5jdaBi0MDHTl/++XYA0 IyTBsFREN60XlK0522scAWLvghtQBIU9JJB3FVhE= 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 5F50221F847D for ; Mon, 14 May 2012 15:29:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 oyYI2ht1slDG for ; Mon, 14 May 2012 15:29:12 -0700 (PDT) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD9A21F843E for ; Mon, 14 May 2012 15:29:11 -0700 (PDT) Received: by lagv3 with SMTP id v3so2765891lag.31 for ; Mon, 14 May 2012 15:29:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=1NZFiAsbjUyxjSAEJGpn1skMRKNWvY/fmdYyMbCi2vw=; b=ds/6rBj2BQ09qLBqSo3tEdU9lz6/3NX8KjGQEhNl+6eT1RjZGxP6usao1FSTNKzPBE iu276Z/rVHoYKno7xkYGmmaISFJQLFJLLcxvKZButZ5HwTz0ReaqQZis2PPFC5jwmmNV Ha2pW2N82kBO1A78U37SCNKOv+rzkGuApG4PsnJilzfAlLTJbi+rDa9LKPMCiMbx9+po isnj0GhEn5KMn3ufKJcf0ad4erkJABM5VSjvWdU/Yp2n+GPNBx8kLwejHQnPRUfZ0B0Z vCvjyuWsuoZE6aRm03B4CAq1NNTbMdK9Ntr7vEEMr70cw5Do+z1Ie6ZuOdOeMwxJF0lO gP1w== Received: by 10.152.112.161 with SMTP id ir1mr10100290lab.13.1337034550968; Mon, 14 May 2012 15:29:10 -0700 (PDT) Received: from a88-114-71-183.elisa-laajakaista.fi (a88-114-71-183.elisa-laajakaista.fi. [88.114.71.183]) by mx.google.com with ESMTPS id mg19sm20836601lab.8.2012.05.14.15.29.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 May 2012 15:29:09 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) From: jouni korhonen In-Reply-To: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> Date: Tue, 15 May 2012 01:29:07 +0300 Message-Id: <1C07F2D7-FE2F-4761-83FA-8A014556A8A6@gmail.com> References: <0228FDA9-7ACA-43F5-AE61-3CBAB0B1C84A@cisco.com> To: Joe Salowey X-Mailer: Apple Mail (2.1084) Cc: radext@ietf.org Subject: Re: [radext] Additional 802.11 attributes X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Jouni had a question regarding the SSID encoding: http://www.ietf.org/mail-archive/web/radext/current/msg07538.html Do you think we need to indicate the SSID encoding? - the other Jouni On May 9, 2012, at 12:09 AM, Joe Salowey wrote: > I've received a few off list suggestions for additional RADIUS attributes= to add to RADIUS Attributes for IEEE 802 Networks. These include > = > 1. WLAN-Reason-Code - used to transmit the reason for authentication f= ailure from AAA to AP in an Access-Reject. The code is included in reason = code of a Disassociation or De-authentication Frame > 2. WLAN-Pairwise-Cipher - communicates the negotiated pairwise cipher f= rom the AP to the AAA. > 3. WLAN-Group-Cipher - communicates the negotiated group cipher from the= AP to the AAA. = > 4. WLAN-AKM-Suite - contains information on the authentication and key m= anagement suite negotiated buy the AP. = > 5. WLAN-RF-Band - contains information on the RF band used by the AP. = > = > Below is suggested text for these attributes from Dave Stephenson: > = > Thanks, > = > Joe > = > 2.9. WLAN-Reason-Code > = > Description > = > The WLAN-Reason-Code Attribute contains information on the reason for aut= horization failure subsequent to a mobile device=92s authentication request= towards a Wi-Fi access network. > = > A WLAN-Reason-Code Attribute MAY be included within an Access-Reject or D= isconnect-Request packet. Upon receipt of an Access-Reject packet, the WLA= N-Reason-Code value is copied by the Authenticator / AP into the Reason cod= e field of a Disassociation or Deauthentication frame (see clause 8.3.3.4 a= nd 8.3.3.12 respectively in IEEE 802.11-2012), which is subsequently transm= itted to the Supplicant / mobile device. A summary of the WLAN-Reason-Code= 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 | Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > = > Code > tbd8 > = > Length > =3D2 > = > Value > The Value field is two octets containing a 16-bit unsigned integer drawn = from Table 8-36 in clause 8.4.1.7 of IEEE 802.11-2012. The value=92s least= significant octet is contained in bits 23-16 and most significant octet in= bits 31-24 (network octet order). Note: not all reason codes defined in t= he Table 8-36 are expected to be used by an AS. > = > [Note]: the importance of including this attribute is for authentication = and authorization of mobile devices in public Wi-Fi access; it is important= to inform the mobile when authorization is denied, even though authenticat= ion may have been successful. This can occur for AS policy reasons or for = reasons related to the user=92s subscription. The following Reason codes f= or public Wi-Fi access networks were added by the IEEE 802.11u-2011 amendme= nt: > = > Reason > Code > Value Description > 27 Disassociated because session terminated by SP request > 28 Disassociated because of lack of SP roaming agreement > 29 Requested service rejected because of SP cipher suite or AKM requ= irement > 30 Requested service not authorized in this location > = > = > = > = > 2.10. WLAN-Pairwise-Cipher > = > Description > = > The WLAN-Pairwise-Cipher Attribute contains information on the pairwise c= ipher suite used to establish the robust security network association (RSNA= ) between the AP and mobile device. > = > A WLAN-Pairwise-Cipher Attribute SHOULD be included within an Access-Requ= est packet. A summary of the WLAN-Pairwise-Cipher Attribute format is show= n 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 | Value = > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > = > Code > tbd9 > = > Length > =3D4 > = > Value > The Value field is four octets formatted in accordance with Figure 8-187 = with values drawn from Table 8-99 of IEEE 802.11-2012. > = > = > = > = > 2.11. WLAN-Group-Cipher > = > Description > = > The WLAN-Group-Cipher Attribute contains information on the group cipher = suite used to establish the robust security network association (RSNA) betw= een the AP and mobile device. > = > A WLAN-Group-Cipher Attribute SHOULD be included within an Access-Request= packet. A summary of the WLAN-Group-Cipher Attribute format is shown belo= w. 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 | Value = > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > = > Code > tbd10 > = > Length > =3D4 > = > Value > The Value field is four octets formatted in accordance with Figure 8-187 = with values drawn from Table 8-99 of IEEE 802.11-2012. > = > = > = > = > 2.12. WLAN-AKM-Suite > = > Description > = > The WLAN-AKM-Suite Attribute contains information on the authentication a= nd key management suite used to establish the robust security network assoc= iation (RSNA) between the AP and mobile device. > = > A WLAN-AKM-Suite Attribute SHOULD be included within an Access-Request pa= cket. A summary of the WLAN-AKM-Suite Attribute format is shown below. Th= e 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 | Value = > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > Value | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > = > Code > tbd11 > = > Length > =3D4 > = > Value > The Value field is four octets formatted in accordance with Figure 8-187 = with values drawn from Table 8-101 of IEEE 802.11-2012. > = > = > = > = > 2.12. WLAN-RF-Band > = > Description > = > The WLAN-RF-Band Attribute contains information on the RF band used by th= e AP for transmission and reception of information to and from the mobile d= evice. This information can be used, for example, to provide a relative qu= ality of experience indication for the mobile device=92s user (i.e., some R= F bands have more interference than others). > = > A WLAN-RF-Band Attribute SHOULD be included within an Access-Request pack= et. A summary of the WLAN-RF-Band Attribute format is shown below. The fi= elds 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 | Value | Reserved | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > = > Code > tbd12 > = > Length > =3D2 > = > Value > The Value field is 1 octet having a value chosen from the table below: > Band ID value Meaning > 0 TV white spaces > 1 Sub-1 GHz (excluding TV white spaces) > 2 2.4 GHz > 3 3.6 GHz > 4 4.9 and 5 GHz > 5 60 GHz > 6-255 Reserved > = > = > [Note]: this table was copied from IEEE 802.11ad-d5. I=92m not sure of t= he relative publication dates of this internet draft and IEEE 802.11ad-d5. = Since it=92s generally not recommended to reference a draft specification = in an RFC, I=92ve copied the table. If we discover that the IEEE document = will be published in time, then we could deleted the table and instead refe= rence Table 8-53a in IEEE 802.11ad. > = > = > = > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Mon May 21 06:30:00 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0855321F84FC; Mon, 21 May 2012 06:30:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337607000; bh=b5kxfhIJOuFKYFkLbuVs3xHIxu61DDUbyf0HoA4QxKs=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=UHSVWyXg5dW1qKkevhI4JB15R4EMSlGJgJoS+UVArxMtOzbv6IeR05Y9AJXxWIxNM 1KWgDWx3BrKl+O3bDn6pBhh1P6tD/e22QZC7Gg0Pr0NaZBxtSH965eAgvLFzYybu2D L1ovdgOzM3b/QNshj7NDdGkFRvimhgQV+LFvGl1w= 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 5784921F84FC for ; Mon, 21 May 2012 06:29:59 -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 Rjvcr2A2PQCq for ; Mon, 21 May 2012 06:29:58 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id BF70E21F84CE for ; Mon, 21 May 2012 06:29:58 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSgP-00026N-Gw; Mon, 21 May 2012 09:29:58 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:29:57 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/110 Message-ID: <059.84f4126e3e16f72b0f8f2b44371dd6f5@trac.tools.ietf.org> X-Trac-Ticket-ID: 110 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #110: syntax problem X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExMDogc3ludGF4IHByb2JsZW0KCiBzZWNvbmQgcGhyYXNlIGluIHRoZSBBYnN0cmFjdCBpcyBi cm9rZW4uCgogPiBUaGlzIGRvY3VtZW50IHByb3Bvc2VzIGFkZGl0aW9uYWwgYXR0cmlidXRlcyBm b3IgdXNlIHdpdGhpbgogICAgSUVFRSA4MDIgbmV0d29ya3MsIGFzIHdlbGwgYXMgcHJvdmlkaW5n IGNsYXJpZmljYXRpb25zIG9uIHRoZSB1c2FnZQogICAgb2YgdGhlIEVBUC1LZXktTmFtZSBhdHRy aWJ1dGUsIHVwZGF0aW5nIFJGQyA0MDcyLgoKCiBwcm9iYWJseSBzL3Byb3ZpZGluZy9wcm92aWRl cwoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tCiBS ZXBvcnRlcjogIGRyb21hc2NhQOKApiAgICAgICB8ICAgICAgT3duZXI6CiAgICAgVHlwZTogIGRl ZmVjdCAgICAgICAgICAgfCAgICAgU3RhdHVzOiAgbmV3CiBQcmlvcml0eTogIG1pbm9yICAgICAg ICAgICAgfCAgTWlsZXN0b25lOgpDb21wb25lbnQ6ICBJRUVFODAyLUF0dHJzICAgIHwgICAgVmVy c2lvbjogIDEuMAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0IENhbGwgIHwgICBLZXl3b3JkczoKLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0KClRpY2tldCBVUkw6 IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTEwPgpy YWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRA aWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Mon May 21 06:29:59 2012 Return-Path: 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 5784921F84FC for ; Mon, 21 May 2012 06:29:59 -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 Rjvcr2A2PQCq for ; Mon, 21 May 2012 06:29:58 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id BF70E21F84CE for ; Mon, 21 May 2012 06:29:58 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSgP-00026N-Gw; Mon, 21 May 2012 09:29:58 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:29:57 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/110 Message-ID: <059.84f4126e3e16f72b0f8f2b44371dd6f5@trac.tools.ietf.org> X-Trac-Ticket-ID: 110 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #110: syntax problem X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 13:29:59 -0000 #110: syntax problem second phrase in the Abstract is broken. > This document proposes additional attributes for use within IEEE 802 networks, as well as providing clarifications on the usage of the EAP-Key-Name attribute, updating RFC 4072. probably s/providing/provides -- -----------------------------+----------------- Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+----------------- Ticket URL: radext From trac+radext@trac.tools.ietf.org Mon May 21 06:36:32 2012 Return-Path: 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 E5C1221F8620 for ; Mon, 21 May 2012 06:36:32 -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 qlZkiCbIsOr4 for ; Mon, 21 May 2012 06:36:32 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7574721F8573 for ; Mon, 21 May 2012 06:36:32 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSml-0004Ps-Lh; Mon, 21 May 2012 09:36:32 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:36:31 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/111 Message-ID: <059.27ec37307bb33d89f8c0f2e973200aaf@trac.tools.ietf.org> X-Trac-Ticket-ID: 111 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #111: Definitions for 802 or 802.11? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 13:36:33 -0000 #111: Definitions for 802 or 802.11? The document according to the title and abstract is general for IEEE 802 networks. However the definitions of Station and Supplicant in section 1.1 sre 802.11 specific. -- -----------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: major | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Mon May 21 06:36:40 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E83721F859E; Mon, 21 May 2012 06:36:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337607400; bh=9PjB0iEIyzFpHiByn5qquvZAaz2TMOo4K5ZPnDQWCyw=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=sIO2HD+ZdieQV0rnt3I3jKgjl8llsAg+SvYAT9QvKJaLLUPJdTzVkM8m944lK86Qj 369CPr7Of0d23h+oOkOJmqQT840sa2TPTXjIrf3WKKnoS3H/iQEa6P677zUSH9bGrR vhxvFo2CIkisQt9taNNhewAp+3agXm8aNPRsdopU= 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 E5C1221F8620 for ; Mon, 21 May 2012 06:36:32 -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 qlZkiCbIsOr4 for ; Mon, 21 May 2012 06:36:32 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7574721F8573 for ; Mon, 21 May 2012 06:36:32 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSml-0004Ps-Lh; Mon, 21 May 2012 09:36:32 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:36:31 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/111 Message-ID: <059.27ec37307bb33d89f8c0f2e973200aaf@trac.tools.ietf.org> X-Trac-Ticket-ID: 111 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #111: Definitions for 802 or 802.11? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExMTogRGVmaW5pdGlvbnMgZm9yIDgwMiBvciA4MDIuMTE/CgogVGhlIGRvY3VtZW50IGFjY29y ZGluZyB0byB0aGUgdGl0bGUgYW5kIGFic3RyYWN0IGlzIGdlbmVyYWwgZm9yIElFRUUgODAyCiBu ZXR3b3Jrcy4gSG93ZXZlciB0aGUgZGVmaW5pdGlvbnMgb2YgU3RhdGlvbiBhbmQgU3VwcGxpY2Fu dCBpbiBzZWN0aW9uIDEuMQogc3JlIDgwMi4xMSBzcGVjaWZpYy4KCi0tIAotLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KIFJlcG9ydGVyOiAgZHJv bWFzY2FA4oCmICAgICAgIHwgICAgICBPd25lcjoKICAgICBUeXBlOiAgZGVmZWN0ICAgICAgICAg ICB8ICAgICBTdGF0dXM6ICBuZXcKIFByaW9yaXR5OiAgbWFqb3IgICAgICAgICAgICB8ICBNaWxl c3RvbmU6ICBtaWxlc3RvbmUxCkNvbXBvbmVudDogIElFRUU4MDItQXR0cnMgICAgfCAgICBWZXJz aW9uOiAgMS4wCiBTZXZlcml0eTogIEluIFdHIExhc3QgQ2FsbCAgfCAgIEtleXdvcmRzOgotLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KClRpY2tl dCBVUkw6IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQv MTExPgpyYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApy YWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRl eHQK From trac+radext@trac.tools.ietf.org Mon May 21 06:36:52 2012 Return-Path: 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 C961621F8639 for ; Mon, 21 May 2012 06:36:52 -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 67Vm-k3MP-UX for ; Mon, 21 May 2012 06:36:52 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD5221F863E for ; Mon, 21 May 2012 06:36:50 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSn4-00052C-2e; Mon, 21 May 2012 09:36:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:36:50 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/111#comment:1 Message-ID: <074.a0590a6337259272790f8d178c50b5e0@trac.tools.ietf.org> References: <059.27ec37307bb33d89f8c0f2e973200aaf@trac.tools.ietf.org> X-Trac-Ticket-ID: 111 In-Reply-To: <059.27ec37307bb33d89f8c0f2e973200aaf@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #111: Definitions for 802 or 802.11? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 13:36:52 -0000 #111: Definitions for 802 or 802.11? Description changed by dromasca@…: Old description: > The document according to the title and abstract is general for IEEE 802 > networks. However the definitions of Station and Supplicant in section > 1.1 sre 802.11 specific. New description: The document according to the title and abstract is general for IEEE 802 networks. However the definitions of Station and Supplicant in section 1.1 are 802.11 specific. -- -- -----------------------------+------------------------- Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: major | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------- Ticket URL: radext From radext-bounces@ietf.org Mon May 21 06:36:54 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3478921F863E; Mon, 21 May 2012 06:36:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337607414; bh=cno3BQM04Cg5lz4Qle3r2KUWfmq77NFEVfbukzQjY2o=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To:Cc: Subject:Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:Content-Type:Content-Transfer-Encoding: Sender; b=wxkq4rP0oJFubtHkXokFG+54d15mxDFEW8YXMSSSSbvRqp7/9YQ7MvMr6FAeETpBC f8KylxBDmBd8BjATolrUya3cHJtATRmQswM3/vDkGsYy9bYIYZsGupM9pWcimNYeLb BbnXWsNIY9EARn62Zvoz4KN9j86D3tLQu20AI6/E= 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 C961621F8639 for ; Mon, 21 May 2012 06:36:52 -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 67Vm-k3MP-UX for ; Mon, 21 May 2012 06:36:52 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD5221F863E for ; Mon, 21 May 2012 06:36:50 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSn4-00052C-2e; Mon, 21 May 2012 09:36:50 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:36:50 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/111#comment:1 Message-ID: <074.a0590a6337259272790f8d178c50b5e0@trac.tools.ietf.org> References: <059.27ec37307bb33d89f8c0f2e973200aaf@trac.tools.ietf.org> X-Trac-Ticket-ID: 111 In-Reply-To: <059.27ec37307bb33d89f8c0f2e973200aaf@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #111: Definitions for 802 or 802.11? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExMTogRGVmaW5pdGlvbnMgZm9yIDgwMiBvciA4MDIuMTE/CgpEZXNjcmlwdGlvbiBjaGFuZ2Vk IGJ5IGRyb21hc2NhQOKApjoKCk9sZCBkZXNjcmlwdGlvbjoKCj4gVGhlIGRvY3VtZW50IGFjY29y ZGluZyB0byB0aGUgdGl0bGUgYW5kIGFic3RyYWN0IGlzIGdlbmVyYWwgZm9yIElFRUUgODAyCj4g bmV0d29ya3MuIEhvd2V2ZXIgdGhlIGRlZmluaXRpb25zIG9mIFN0YXRpb24gYW5kIFN1cHBsaWNh bnQgaW4gc2VjdGlvbgo+IDEuMSBzcmUgODAyLjExIHNwZWNpZmljLgoKTmV3IGRlc2NyaXB0aW9u OgoKIFRoZSBkb2N1bWVudCBhY2NvcmRpbmcgdG8gdGhlIHRpdGxlIGFuZCBhYnN0cmFjdCBpcyBn ZW5lcmFsIGZvciBJRUVFIDgwMgogbmV0d29ya3MuIEhvd2V2ZXIgdGhlIGRlZmluaXRpb25zIG9m IFN0YXRpb24gYW5kIFN1cHBsaWNhbnQgaW4gc2VjdGlvbiAxLjEKIGFyZSA4MDIuMTEgc3BlY2lm aWMuCgotLQoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0KIFJlcG9ydGVyOiAgZHJvbWFzY2FA4oCmICAgICAgIHwgICAgICAgT3duZXI6 CiAgICAgVHlwZTogIGRlZmVjdCAgICAgICAgICAgfCAgICAgIFN0YXR1czogIG5ldwogUHJpb3Jp dHk6ICBtYWpvciAgICAgICAgICAgIHwgICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCkNvbXBvbmVu dDogIElFRUU4MDItQXR0cnMgICAgfCAgICAgVmVyc2lvbjogIDEuMAogU2V2ZXJpdHk6ICBJbiBX RyBMYXN0IENhbGwgIHwgIFJlc29sdXRpb246CiBLZXl3b3JkczogICAgICAgICAgICAgICAgICAg fAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t CgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFkZXh0L3RyYWMv dGlja2V0LzExMSNjb21tZW50OjE+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4 dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRl eHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls bWFuL2xpc3RpbmZvL3JhZGV4dAo= From radext-bounces@ietf.org Mon May 21 06:46:31 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F3F21F8562; Mon, 21 May 2012 06:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337607991; bh=XiEwoepQudcNIccxIvW6r/C/IMoIbmO0axVkTyhvFAI=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=jdAuDX54TVjlAVTJjZfLcTXudFieyRVMnhmocAjtTBc6Nkr/mzjz58gMFzfD6Vlih rXMG2Ra3MHyXP1fDaQJzkzVkLM8XS/RCjjqqp6MyqqKlUgyhtqQVDLVTnlrAkDjAw6 yTfpT4g70pHN3Tc2NM9fAT6hEBJl91RyfOJurwS0= 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 63F7F21F8562 for ; Mon, 21 May 2012 06:46:30 -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=[AWL=0.000, 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 B9oHlOs2BvPl for ; Mon, 21 May 2012 06:46:30 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id E101421F855B for ; Mon, 21 May 2012 06:46:29 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSwO-0001YA-Q5; Mon, 21 May 2012 09:46:28 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:46:28 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/112 Message-ID: <059.11906697f7d67bdd491bfd8ebfe1fb8c@trac.tools.ietf.org> X-Trac-Ticket-ID: 112 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #112: define or refer 'privilege attacks' X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExMjogZGVmaW5lIG9yIHJlZmVyICdwcml2aWxlZ2UgYXR0YWNrcycKCiBVbmxlc3MgaXQncyBh IHZlcnkgY29tbW9uIHR5cGUgb2YgYXR0YWNrIHBsZWFzZSBkZWZpbmUgb3IgcHJvdmlkZSBhCiBj bGFyaWZpY2F0aW9uIGZvciB3aGF0IG1lYW5zICdhdm9pZCBlbGV2YXRpb24gb2YgcHJpdmlsZWdl IGF0dGFja3MnIGluIDIuMQoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICAgICAgfCAgICAg IE93bmVyOgogICAgIFR5cGU6ICBlbmhhbmNlbWVudCAgICAgIHwgICAgIFN0YXR1czogIG5ldwog UHJpb3JpdHk6ICBtaW5vciAgICAgICAgICAgIHwgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEKQ29t cG9uZW50OiAgSUVFRTgwMi1BdHRycyAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAg SW4gV0cgTGFzdCBDYWxsICB8ICAgS2V5d29yZHM6Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRv b2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMTI+CnJhZGV4dCA8aHR0cDovL3Rv b2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Mon May 21 06:46:30 2012 Return-Path: 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 63F7F21F8562 for ; Mon, 21 May 2012 06:46:30 -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=[AWL=0.000, 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 B9oHlOs2BvPl for ; Mon, 21 May 2012 06:46:30 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id E101421F855B for ; Mon, 21 May 2012 06:46:29 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWSwO-0001YA-Q5; Mon, 21 May 2012 09:46:28 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:46:28 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/112 Message-ID: <059.11906697f7d67bdd491bfd8ebfe1fb8c@trac.tools.ietf.org> X-Trac-Ticket-ID: 112 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #112: define or refer 'privilege attacks' X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 13:46:30 -0000 #112: define or refer 'privilege attacks' Unless it's a very common type of attack please define or provide a clarification for what means 'avoid elevation of privilege attacks' in 2.1 -- -----------------------------+------------------------ Reporter: dromasca@… | Owner: Type: enhancement | Status: new Priority: minor | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+------------------------ Ticket URL: radext From trac+radext@trac.tools.ietf.org Mon May 21 06:56:07 2012 Return-Path: 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 DE9EF21F85A0 for ; Mon, 21 May 2012 06:56:07 -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 kwdklndg+EjN for ; Mon, 21 May 2012 06:56:07 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 6914721F84FE for ; Mon, 21 May 2012 06:56:07 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWT5h-0003fm-8Y; Mon, 21 May 2012 09:56:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:56:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/113 Message-ID: <059.64b26be64510cc5c5bcfe0b38d0911b2@trac.tools.ietf.org> X-Trac-Ticket-ID: 113 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #113: expand PMK at first occurence X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 13:56:08 -0000 #113: expand PMK at first occurence -- -----------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Mon May 21 06:56:08 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B604021F85A0; Mon, 21 May 2012 06:56:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337608568; bh=aNOWZXQf+GVsuq/il7j/hZ8TrthfRLZI9Alt/wN397w=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=QGGWx2qNP3qTJ2fgImfTHPOhxBeC+ZuevDYHUtRHTlGKfKwqsSSET+19j1jVQTSUE 6pZdLYLuuS39wvTKxGCjpxCZR2wUrfcGP95nNWrsh8KdCB4ZtqA+ZAqLKohAo2Zl6M GMfNLc62j1Pix8K8O8NXEFE83b4NfUQ5kBFz8Vgk= 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 DE9EF21F85A0 for ; Mon, 21 May 2012 06:56:07 -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 kwdklndg+EjN for ; Mon, 21 May 2012 06:56:07 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 6914721F84FE for ; Mon, 21 May 2012 06:56:07 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWT5h-0003fm-8Y; Mon, 21 May 2012 09:56:05 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 13:56:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/113 Message-ID: <059.64b26be64510cc5c5bcfe0b38d0911b2@trac.tools.ietf.org> X-Trac-Ticket-ID: 113 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #113: expand PMK at first occurence X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExMzogZXhwYW5kIFBNSyBhdCBmaXJzdCBvY2N1cmVuY2UKCgoKLS0gCi0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9t YXNjYUDigKYgICAgICAgfCAgICAgIE93bmVyOgogICAgIFR5cGU6ICBkZWZlY3QgICAgICAgICAg IHwgICAgIFN0YXR1czogIG5ldwogUHJpb3JpdHk6ICBtaW5vciAgICAgICAgICAgIHwgIE1pbGVz dG9uZTogIG1pbGVzdG9uZTEKQ29tcG9uZW50OiAgSUVFRTgwMi1BdHRycyAgICB8ICAgIFZlcnNp b246ICAxLjAKIFNldmVyaXR5OiAgSW4gV0cgTGFzdCBDYWxsICB8ICAgS2V5d29yZHM6Ci0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0 IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8x MTM+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJh ZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4 dAo= From radext-bounces@ietf.org Mon May 21 07:00:43 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08A621F8680; Mon, 21 May 2012 07:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337608843; bh=PTx7kEdWvBUymVvDbOVnqPhfT90UPzOmjXJuzZCy72U=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=iIky7QEIZ172xgtsji9vLpnt+zWsbqPJ8WgDHwWH4W5torgxuzs4SxMP4j2fPxpOQ wENX4hbL5MSxE4URSSeFl8CDrq41zcvV2U/HTJN2P5v5qiDTf1Wp2nFwI4aFnp3L4S i2pMPIzWsqxQ8n5XWczXkKX9DX/uXAQnOnhVzkXg= 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 4C5B121F8680 for ; Mon, 21 May 2012 07:00:43 -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=[AWL=0.000, 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 6EU56ePq9PAL for ; Mon, 21 May 2012 07:00:42 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id CA08021F8673 for ; Mon, 21 May 2012 07:00:42 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWTA9-0006X6-Mo; Mon, 21 May 2012 10:00:42 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 14:00:41 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/114 Message-ID: <059.b2f1d9f03e1605809bcdd9f0956fccf7@trac.tools.ietf.org> X-Trac-Ticket-ID: 114 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #114: encoding the IEEE 802.11 SSID X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExNDogZW5jb2RpbmcgdGhlIElFRUUgODAyLjExIFNTSUQKCiBJbiAyLjc6CgogPiBUaGUgTmV0 d29yay1JZC1OYW1lIEF0dHJpYnV0ZSBTSE9VTEQgTk9UIGJlIHVzZWQgdG8gZW5jb2RlIHRoZSBJ RUVFCiA4MDIuMTEgU1NJRDsgYXMgbm90ZWQgaW4gW1JGQzM1ODBdLCB0aGUgQ2FsbGVkLVN0YXRp b24tSWQgQXR0cmlidXRlIGlzCiB1c2VkIGZvciB0aGlzIHB1cnBvc2UuCgogSXMgdGhlcmUgYW55 IGNhc2Ugb2YgZXhjZXB0aW9uPyBJIGFtIHRyeWluZyB0byB1bmRlcnN0YW5kIHdoeSBTSE9VTEQg Tk9UCiBhbmQgbm90IE1VU1QgTk9ULgoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t Ky0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICAgICAg fCAgICAgIE93bmVyOgogICAgIFR5cGU6ICBkZWZlY3QgICAgICAgICAgIHwgICAgIFN0YXR1czog IG5ldwogUHJpb3JpdHk6ICBtYWpvciAgICAgICAgICAgIHwgIE1pbGVzdG9uZTogIG1pbGVzdG9u ZTEKQ29tcG9uZW50OiAgSUVFRTgwMi1BdHRycyAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVy aXR5OiAgSW4gV0cgTGFzdCBDYWxsICB8ICAgS2V5d29yZHM6Ci0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90 cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMTQ+CnJhZGV4dCA8aHR0 cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpo dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Mon May 21 07:00:43 2012 Return-Path: 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 4C5B121F8680 for ; Mon, 21 May 2012 07:00:43 -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=[AWL=0.000, 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 6EU56ePq9PAL for ; Mon, 21 May 2012 07:00:42 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id CA08021F8673 for ; Mon, 21 May 2012 07:00:42 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWTA9-0006X6-Mo; Mon, 21 May 2012 10:00:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 14:00:41 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/114 Message-ID: <059.b2f1d9f03e1605809bcdd9f0956fccf7@trac.tools.ietf.org> X-Trac-Ticket-ID: 114 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #114: encoding the IEEE 802.11 SSID X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 14:00:43 -0000 #114: encoding the IEEE 802.11 SSID In 2.7: > The Network-Id-Name Attribute SHOULD NOT be used to encode the IEEE 802.11 SSID; as noted in [RFC3580], the Called-Station-Id Attribute is used for this purpose. Is there any case of exception? I am trying to understand why SHOULD NOT and not MUST NOT. -- -----------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: major | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Mon May 21 07:19:41 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D31F21F855A; Mon, 21 May 2012 07:19:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337609981; bh=xf8+FWR/Me+rdXkrq5VZd11cKVsbP3Eme5rINOw5ofw=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=IeKYzzSzQU4vayP104jokBmTDgNdoysbyDDZE0Fw2FnPj+pGca6va3Wq5Mu5lxxEz SYD9SwY2n6bkRGQdRiqwPPBOYKQcVTrEcH3P2RQqhkfc4dcbsVUCa3ZFi302PSej9O IVIk1A/8vkK6JEgUS6In4oTokxwwPLDzwPXVpuDk= 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 EEFEB21F855A for ; Mon, 21 May 2012 07:19:39 -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=[AWL=0.000, 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 EvHJuC37trcb for ; Mon, 21 May 2012 07:19:39 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 8105C21F84A1 for ; Mon, 21 May 2012 07:19:39 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWTSU-0007wd-DJ; Mon, 21 May 2012 10:19:38 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 14:19:38 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/115 Message-ID: <059.fd1ba7a330483bf4d9ea291c1e01286d@trac.tools.ietf.org> X-Trac-Ticket-ID: 115 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #115: tables are not numbered X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExNTogdGFibGVzIGFyZSBub3QgbnVtYmVyZWQKCiBwbGVhc2UgbnVtYmVyIHRhYmxlcyBpbiB0 aGUgZG9jdW1lbnQgc28gdGhhdCB0aGVpciBjb250ZW50IGNhbiBiZSBlYXNpZXIKIGxvY2F0ZWQg YW5kIHJlZmVyZWQKCi0tIAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgICAgfCAgICAgIE93bmVyOgog ICAgIFR5cGU6ICBkZWZlY3QgICAgICAgICB8ICAgICBTdGF0dXM6ICBuZXcKIFByaW9yaXR5OiAg bWlub3IgICAgICAgICAgfCAgTWlsZXN0b25lOiAgbWlsZXN0b25lMQpDb21wb25lbnQ6ICBJRUVF ODAyLUF0dHJzICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAgLSAgICAgICAgICAgICAg fCAgIEtleXdvcmRzOgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFk ZXh0L3RyYWMvdGlja2V0LzExNT4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0 Lz4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4 dCBtYWlsaW5nIGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt YW4vbGlzdGluZm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Mon May 21 07:19:39 2012 Return-Path: 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 EEFEB21F855A for ; Mon, 21 May 2012 07:19:39 -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=[AWL=0.000, 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 EvHJuC37trcb for ; Mon, 21 May 2012 07:19:39 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 8105C21F84A1 for ; Mon, 21 May 2012 07:19:39 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWTSU-0007wd-DJ; Mon, 21 May 2012 10:19:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 14:19:38 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/115 Message-ID: <059.fd1ba7a330483bf4d9ea291c1e01286d@trac.tools.ietf.org> X-Trac-Ticket-ID: 115 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #115: tables are not numbered X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 14:19:40 -0000 #115: tables are not numbered please number tables in the document so that their content can be easier located and refered -- ---------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: - | Keywords: ---------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Mon May 21 07:22:11 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6190221F8567; Mon, 21 May 2012 07:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337610131; bh=bzYmdiahksfRjhD9pXjPXcMeRolO78WCJaPIMpbi/+g=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=bH67QC3wk8qrEhl4dfKo8VP7x1heA0Vaq9V8hhJHaZVxu905zDHHFcwKvNiUEvW9o nOSTwJLafaPguJDi5F+42YbPA5s705tyw01V+iYn6a5hwdCnaWRkHVg5eYiYpCncR3 t8NM7e3vh3SB6TW+ka0dL9glFbDLaGrjqLsxBbcU= 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 0EA5F21F855B for ; Mon, 21 May 2012 07:22:10 -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 p0t65XfpU4KZ for ; Mon, 21 May 2012 07:22:09 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 751C621F8567 for ; Mon, 21 May 2012 07:22:09 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWTUv-000598-59; Mon, 21 May 2012 10:22:09 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 14:22:09 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/116 Message-ID: <059.fabde32f44d367ef213c1225b31d24a8@trac.tools.ietf.org> X-Trac-Ticket-ID: 116 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #116: typos in the table in section 4 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExNjogdHlwb3MgaW4gdGhlIHRhYmxlIGluIHNlY3Rpb24gNAoKIEluIHRoZSB0YWJsZSBpbiBz ZWN0aW9uIDQgaXMgVVRGOFN0cmluIGEgdHlwbywgc2hvdWxkIGl0IGJlIFVURjhTdHJpbmc/Cgot LSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t CiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgICAgICB8ICAgICAgT3duZXI6CiAgICAgVHlwZTog IGRlZmVjdCAgICAgICAgICAgfCAgICAgU3RhdHVzOiAgbmV3CiBQcmlvcml0eTogIG1pbm9yICAg ICAgICAgICAgfCAgTWlsZXN0b25lOiAgbWlsZXN0b25lMQpDb21wb25lbnQ6ICBJRUVFODAyLUF0 dHJzICAgIHwgICAgVmVyc2lvbjogIDEuMAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0IENhbGwgIHwg ICBLZXl3b3JkczoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFk ZXh0L3RyYWMvdGlja2V0LzExNj4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0 Lz4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4 dCBtYWlsaW5nIGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt YW4vbGlzdGluZm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Mon May 21 07:22:10 2012 Return-Path: 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 0EA5F21F855B for ; Mon, 21 May 2012 07:22:10 -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 p0t65XfpU4KZ for ; Mon, 21 May 2012 07:22:09 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 751C621F8567 for ; Mon, 21 May 2012 07:22:09 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SWTUv-000598-59; Mon, 21 May 2012 10:22:09 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Mon, 21 May 2012 14:22:09 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/116 Message-ID: <059.fabde32f44d367ef213c1225b31d24a8@trac.tools.ietf.org> X-Trac-Ticket-ID: 116 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #116: typos in the table in section 4 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 14:22:10 -0000 #116: typos in the table in section 4 In the table in section 4 is UTF8Strin a typo, should it be UTF8String? -- -----------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: IEEE802-Attrs | Version: 1.0 Severity: In WG Last Call | Keywords: -----------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Tue May 22 10:42:58 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 034C221F867E; Tue, 22 May 2012 10:42:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337708578; bh=CPHiAFMMHQ4KdmbJgikCyQeEcJKwAjt72lgWcnqqZ+Y=; h=From:To:Date:Message-ID:In-Reply-To:MIME-Version:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=zaDnelInDrZMJiDenhDCDE7Rp/Fg5JS9R1EUcK9lPXG3LuuxU1oP3+ctgX5G4IVII mgNBxrXFdglRIvGHnGbUIZI9/Z/NPHpC1JpZrlXW6IXeehdatLy4DfSAiHtNHHAVXv C/p3Tquq0Ym0lpzpJmJGztcwhWdU7G5QvEbYXhKQ= 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 F0F5721F867E for ; Tue, 22 May 2012 10:42:56 -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 J7uqDvQ0rzzs for ; Tue, 22 May 2012 10:42:56 -0700 (PDT) Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com [15.216.28.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4BD21F867D for ; Tue, 22 May 2012 10:42:55 -0700 (PDT) Received: from G5W2206G.americas.hpqcorp.net (g5w2206g.atlanta.hp.com [16.228.43.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0027.austin.hp.com (Postfix) with ESMTPS id 7B38B380A1 for ; Tue, 22 May 2012 17:42:49 +0000 (UTC) Received: from G5W0602.americas.hpqcorp.net (16.228.9.185) by G5W2206G.americas.hpqcorp.net (16.228.43.185) with Microsoft SMTP Server (TLS) id 14.2.283.4; Tue, 22 May 2012 17:41:15 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0602.americas.hpqcorp.net ([16.228.9.185]) with mapi; Tue, 22 May 2012 18:41:15 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Tue, 22 May 2012 18:41:14 +0100 Thread-Topic: [radext] RADEXT charter Thread-Index: Ac04QhYakOtJcjq8RK+OKuqlL8wKxg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Gentle reminder that we would appreciate hearing your thoughts, either positive or negative, on proposal below. Thanks, Mauricio and Jouni On 5/9/12 10:54 AM, "Sanchez, Mauricio (HP Networking)" wrote: >We have been discussing rechartering on and off since January. Below is >an updated proposal that we would appreciate your review and feedback. >The changes can be summarized as follows: > > * Updating completed work items and casting new dates for work items >not accomplished per the dates in existing charter > * Addition of network access identifier work item > * Addition of traffic accounting work item > * Addition of packet fragmentation work item > >Thanks, >Mauricio and Jouni > >--------------------------------------------- >Description of Working Group > >The RADIUS Extensions Working Group will focus on extensions to the >RADIUS protocol required to expand and enrich the standard attribute >space, address cryptographic algorithm agility, use of new secure >transports and clarify its usage and definition. > >In order to enable interoperation of heterogeneous RADIUS/Diameter >deployments, all RADEXT WG work items MUST contain a Diameter >compatibility section, outlining how interoperability with Diameter will >be maintained. >Furthermore, to ensure backward compatibility with existing RADIUS >implementations, as well as compatibility between RADIUS and Diameter, >the following restrictions are imposed on extensions considered by the >RADEXT WG: > >- All documents produced MUST specify means of interoperation with legacy >RADIUS and, if possible, be backward compatible with existing RADIUS >RFCs, including RFCs 2865-2869, 3162, 3575, 3579, 3580, 4668-4673,4675, >5080, 5090, 5176 and 6158. Transport profiles should, if possible, be >compatible with RFC 3539. > >- All RADIUS work MUST be compatible with equivalent facilities in >Diameter. Where possible, new attributes should be defined so that the >same attribute can be used in both RADIUS and Diameter without >translation. In other cases a translation considerations section should >be included in the specification. > >Work Items >The immediate goals of the RADEXT working group are to address the >following issues: >- RADIUS attribute space extension. The standard RADIUS attribute space >is currently being depleted. This document will provide additional >standard attribute space, while maintaining backward compatibility with >existing attributes. > >- IEEE 802 attributes. New attributes have been proposed to support IEEE >802 standards for wired and wireless LANs. This work item will support >authentication, authorization and accounting attributes needed by IEEE >802 groups including IEEE 802.1, IEEE 802.11 and IEEE 802.16. > >- New RADIUS transports. A reliable transport profile for RADIUS will be >developed, as well as specifications for Secure transports, including >TCP/TLS (RADSEC) and UDP/DTLS. > >- Update and clarification of Network Access Identifiers (RFC4282).This >work item will correct and clarify issues present with RFC4282 in two >phases. In first phase, RFC4282bis will be issued to eliminate >fundamental incompatibilities with RADIUS around character encoding and >NAI modifications by proxies. In second phase, a fresh review of NAI >internationalization requirements and behavior will be undertaken with a >clear goal of maintaining compatibility with RADIUS. > >- RADIUS Accounting Extensions for Traffic Statistics. This work item >will specify RADIUS accounting attributes for differentiated accounting >polices and traffic recording. > >- Fragmentation of RADIUS packets to support exchanges exceeding the >existing 4KB limit imposed by RFC2865. > > >Goals and Milestones >Done Updates to RFC 2618-2621 RADIUS MIBs submitted for publication >Done SIP RADIUS authentication draft submitted as a Proposed Standard RFC >Done RFC 2486bis submitted as a Proposed Standard RFC >Done RFC 3576 MIBs submitted as an Informational RFC >Done RADIUS VLAN and Priority Attributes draft submitted as a Proposed >Standard RFC (reduced in scope) >Done RADIUS Implementation Issues and Fixes draft submitted as an >Informational RFC >Done RADIUS Filtering Attributes draft submitted as a Proposed Standard >RFC (split out from VLAN & Priority draft) >Done RFC 3576bis submitted as an Informational RFC (split out from Issues >& Fixes draft) >Done RADIUS Redirection Attributes draft submitted as a Proposed Standard >RFC (split out from VLAN & Priority draft) >Done RADIUS Design Guidelines submitted as a Best Current Practice RFC >Done RADIUS Management Authorization I-D submitted as a Proposed Standard >RFC >Done Reliable Transport Profile for RADIUS I-D submitted as a Proposed >Standard RFC >Done Status-Server I-D submitted as a Proposed Standard RFC >Done RADIUS Crypto-agility Requirements submitted as an Informational RFC >Done RADSEC (RADIUS over TCP/TLS) draft submitted as an Experimental RFC >May 2012 IPv6 Access I-D submitted as a Proposed Standard RFC >May 2012 Extended Attributes I-D submitted as a Proposed Standard RFC >Jun 2012 Dynamic Discovery I-D submitted as a Proposed Standard RFC >Jun 2012 IEEE 802 Attributes I-D submitted as a Proposed Standard RFC >Aug 2012 RADIUS over DTLS I-D submitted as an Experimental RFC >Nov 2012 Traffic Statistics Attribute I-D submitted as a Proposed >Standard RFC >Nov 2012 RADIUS packet fragmentation submitted as an Experimental RFC >Nov 2012 RFC 4282bis submitted as a Proposed Standard RFC >Apr 2013 RADIUS support for NAI Internationalization I-D submitted as a >Proposed Standard RFC >_______________________________________________ >radext mailing list >radext@ietf.org >https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From mauricio.sanchez@hp.com Tue May 22 10:42:57 2012 Return-Path: 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 F0F5721F867E for ; Tue, 22 May 2012 10:42:56 -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 J7uqDvQ0rzzs for ; Tue, 22 May 2012 10:42:56 -0700 (PDT) Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com [15.216.28.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4BD21F867D for ; Tue, 22 May 2012 10:42:55 -0700 (PDT) Received: from G5W2206G.americas.hpqcorp.net (g5w2206g.atlanta.hp.com [16.228.43.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0027.austin.hp.com (Postfix) with ESMTPS id 7B38B380A1 for ; Tue, 22 May 2012 17:42:49 +0000 (UTC) Received: from G5W0602.americas.hpqcorp.net (16.228.9.185) by G5W2206G.americas.hpqcorp.net (16.228.43.185) with Microsoft SMTP Server (TLS) id 14.2.283.4; Tue, 22 May 2012 17:41:15 +0000 Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.3]) by G5W0602.americas.hpqcorp.net ([16.228.9.185]) with mapi; Tue, 22 May 2012 18:41:15 +0100 From: "Sanchez, Mauricio (HP Networking)" To: "radext@ietf.org" Date: Tue, 22 May 2012 18:41:14 +0100 Thread-Topic: [radext] RADEXT charter Thread-Index: Ac04QhYakOtJcjq8RK+OKuqlL8wKxg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2012 17:42:57 -0000 Gentle reminder that we would appreciate hearing your thoughts, either positive or negative, on proposal below. Thanks, Mauricio and Jouni=20 On 5/9/12 10:54 AM, "Sanchez, Mauricio (HP Networking)" wrote: >We have been discussing rechartering on and off since January. Below is >an updated proposal that we would appreciate your review and feedback. >The changes can be summarized as follows: > > * Updating completed work items and casting new dates for work items >not accomplished per the dates in existing charter > * Addition of network access identifier work item > * Addition of traffic accounting work item > * Addition of packet fragmentation work item > >Thanks, >Mauricio and Jouni > >--------------------------------------------- >Description of Working Group > >The RADIUS Extensions Working Group will focus on extensions to the >RADIUS protocol required to expand and enrich the standard attribute >space, address cryptographic algorithm agility, use of new secure >transports and clarify its usage and definition. > >In order to enable interoperation of heterogeneous RADIUS/Diameter >deployments, all RADEXT WG work items MUST contain a Diameter >compatibility section, outlining how interoperability with Diameter will >be maintained. >Furthermore, to ensure backward compatibility with existing RADIUS >implementations, as well as compatibility between RADIUS and Diameter, >the following restrictions are imposed on extensions considered by the >RADEXT WG: > >- All documents produced MUST specify means of interoperation with legacy >RADIUS and, if possible, be backward compatible with existing RADIUS >RFCs, including RFCs 2865-2869, 3162, 3575, 3579, 3580, 4668-4673,4675, >5080, 5090, 5176 and 6158. Transport profiles should, if possible, be >compatible with RFC 3539. > >- All RADIUS work MUST be compatible with equivalent facilities in >Diameter. Where possible, new attributes should be defined so that the >same attribute can be used in both RADIUS and Diameter without >translation. In other cases a translation considerations section should >be included in the specification. > >Work Items >The immediate goals of the RADEXT working group are to address the >following issues: >- RADIUS attribute space extension. The standard RADIUS attribute space >is currently being depleted. This document will provide additional >standard attribute space, while maintaining backward compatibility with >existing attributes. > >- IEEE 802 attributes. New attributes have been proposed to support IEEE >802 standards for wired and wireless LANs. This work item will support >authentication, authorization and accounting attributes needed by IEEE >802 groups including IEEE 802.1, IEEE 802.11 and IEEE 802.16. > >- New RADIUS transports. A reliable transport profile for RADIUS will be >developed, as well as specifications for Secure transports, including >TCP/TLS (RADSEC) and UDP/DTLS. > >- Update and clarification of Network Access Identifiers (RFC4282).This >work item will correct and clarify issues present with RFC4282 in two >phases. In first phase, RFC4282bis will be issued to eliminate >fundamental incompatibilities with RADIUS around character encoding and >NAI modifications by proxies. In second phase, a fresh review of NAI >internationalization requirements and behavior will be undertaken with a >clear goal of maintaining compatibility with RADIUS. > >- RADIUS Accounting Extensions for Traffic Statistics. This work item >will specify RADIUS accounting attributes for differentiated accounting >polices and traffic recording. > >- Fragmentation of RADIUS packets to support exchanges exceeding the >existing 4KB limit imposed by RFC2865. > > >Goals and Milestones >Done Updates to RFC 2618-2621 RADIUS MIBs submitted for publication >Done SIP RADIUS authentication draft submitted as a Proposed Standard RFC >Done RFC 2486bis submitted as a Proposed Standard RFC >Done RFC 3576 MIBs submitted as an Informational RFC >Done RADIUS VLAN and Priority Attributes draft submitted as a Proposed >Standard RFC (reduced in scope) >Done RADIUS Implementation Issues and Fixes draft submitted as an >Informational RFC >Done RADIUS Filtering Attributes draft submitted as a Proposed Standard >RFC (split out from VLAN & Priority draft) >Done RFC 3576bis submitted as an Informational RFC (split out from Issues >& Fixes draft) >Done RADIUS Redirection Attributes draft submitted as a Proposed Standard >RFC (split out from VLAN & Priority draft) >Done RADIUS Design Guidelines submitted as a Best Current Practice RFC >Done RADIUS Management Authorization I-D submitted as a Proposed Standard >RFC >Done Reliable Transport Profile for RADIUS I-D submitted as a Proposed >Standard RFC >Done Status-Server I-D submitted as a Proposed Standard RFC >Done RADIUS Crypto-agility Requirements submitted as an Informational RFC >Done RADSEC (RADIUS over TCP/TLS) draft submitted as an Experimental RFC >May 2012 IPv6 Access I-D submitted as a Proposed Standard RFC >May 2012 Extended Attributes I-D submitted as a Proposed Standard RFC >Jun 2012 Dynamic Discovery I-D submitted as a Proposed Standard RFC >Jun 2012 IEEE 802 Attributes I-D submitted as a Proposed Standard RFC >Aug 2012 RADIUS over DTLS I-D submitted as an Experimental RFC >Nov 2012 Traffic Statistics Attribute I-D submitted as a Proposed >Standard RFC >Nov 2012 RADIUS packet fragmentation submitted as an Experimental RFC >Nov 2012 RFC 4282bis submitted as a Proposed Standard RFC >Apr 2013 RADIUS support for NAI Internationalization I-D submitted as a >Proposed Standard RFC >_______________________________________________ >radext mailing list >radext@ietf.org >https://www.ietf.org/mailman/listinfo/radext From aland@deployingradius.com Tue May 22 12:46:46 2012 Return-Path: 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 D9A9B21F8647 for ; Tue, 22 May 2012 12:46:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.11 X-Spam-Level: X-Spam-Status: No, score=-101.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 L21gj0Pk6yDS for ; Tue, 22 May 2012 12:46:46 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 4C10721F8609 for ; Tue, 22 May 2012 12:46:46 -0700 (PDT) Message-ID: <4FBBED0A.2050606@deployingradius.com> Date: Tue, 22 May 2012 21:46:18 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Sanchez, Mauricio (HP Networking)" References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "radext@ietf.org" Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2012 19:46:47 -0000 Sanchez, Mauricio (HP Networking) wrote: > Gentle reminder that we would appreciate hearing your thoughts, either > positive or negative, on proposal below. It looks good. I would tentatively propose discussion of 5176 and proxying of CoA packets. The document is essentially silent on proxying. The main open problem is: - how do you proxy CoA packets across multiple hops? Alan DeKok. From radext-bounces@ietf.org Tue May 22 12:46:48 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4B9D21F8647; Tue, 22 May 2012 12:46:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337716008; bh=0UcH7NoDJM3lSXuswSKt4YZT0Vgu/KW1uLiCGVFgfHs=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=YivqUMzywp7L+hZc7R5fU72Vnd4b97b57d69CkNAo4Kp4k3MUfrvZbm/lPPd2gmqZ 86y2gf8eZ45QkbidrlLMT0JiQ/qs2bMjagQ38R5wmCfAN3wGF/jM3g7JlwSmA1vFeV q6a/xI8Adx3it+3cjs6W12eHMT5q/uJAG0gLuO8Y= 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 D9A9B21F8647 for ; Tue, 22 May 2012 12:46:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.11 X-Spam-Level: X-Spam-Status: No, score=-101.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 L21gj0Pk6yDS for ; Tue, 22 May 2012 12:46:46 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 4C10721F8609 for ; Tue, 22 May 2012 12:46:46 -0700 (PDT) Message-ID: <4FBBED0A.2050606@deployingradius.com> Date: Tue, 22 May 2012 21:46:18 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Sanchez, Mauricio (HP Networking)" References: In-Reply-To: X-Enigmail-Version: 0.96.0 Cc: "radext@ietf.org" Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Sanchez, Mauricio (HP Networking) wrote: > Gentle reminder that we would appreciate hearing your thoughts, either > positive or negative, on proposal below. It looks good. I would tentatively propose discussion of 5176 and proxying of CoA packets. The document is essentially silent on proxying. The main open problem is: - how do you proxy CoA packets across multiple hops? Alan DeKok. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From stefan.winter@restena.lu Wed May 23 04:34:52 2012 Return-Path: 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 9643021F84FC for ; Wed, 23 May 2012 04:34:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 GjOsg7PqsqLM for ; Wed, 23 May 2012 04:34:52 -0700 (PDT) Received: from legolas.restena.lu (legolas.restena.lu [IPv6:2001:a18:1::34]) by ietfa.amsl.com (Postfix) with ESMTP id D91EF21F84A0 for ; Wed, 23 May 2012 04:34:51 -0700 (PDT) Received: from legolas.restena.lu (localhost [127.0.0.1]) by legolas.restena.lu (Postfix) with ESMTP id 89CD19DD22 for ; Wed, 23 May 2012 13:34:49 +0200 (CEST) Received: from [158.64.15.212] (212-15.vpn.restena.lu [158.64.15.212]) by legolas.restena.lu (Postfix) with ESMTPSA id 535749DD14 for ; Wed, 23 May 2012 13:34:49 +0200 (CEST) Message-ID: <4FBCCB57.7010606@restena.lu> Date: Wed, 23 May 2012 13:34:47 +0200 From: Stefan Winter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: radext@ietf.org References: <4FBBED0A.2050606@deployingradius.com> In-Reply-To: <4FBBED0A.2050606@deployingradius.com> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 11:34:52 -0000 Hi, on that topic, I've been wondering what good dynamic discovery can do here. The current draft only enables lookup of home servers for auth/acct purposes. It *could* be used the other way around though: when a user has logged in somewhere, and the "somewhere" includes the Operator-Name attribute (DNS-style), the home server could lookup the Operator-Name content in DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to. That would need lots of new text in the dyndisc draft - but I'm at it anyway, so if there's some support for the idea on the list, this could go in... Greetings, Stefan Winter On 22.05.12 21:46, Alan DeKok wrote: > Sanchez, Mauricio (HP Networking) wrote: >> Gentle reminder that we would appreciate hearing your thoughts, either >> positive or negative, on proposal below. > It looks good. > > I would tentatively propose discussion of 5176 and proxying of CoA > packets. The document is essentially silent on proxying. The main open > problem is: > > - how do you proxy CoA packets across multiple hops? > > Alan DeKok. > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Wed May 23 04:34:54 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7F021F84FC; Wed, 23 May 2012 04:34:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337772894; bh=zWlxUNXISFZPSKYi6xYYnr9Ik7WZXeirvdDwjZ4r5bA=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=zMN2NuRxCdFw6V7mfLuWDcxIzGjtn4bvvp0tzNJ9UAdddRnUl/AI6Gg4llsxgJm2C GvMmvCb4di8Ee/CB1021pbfNEyKkdLlUAzXw7KW7POYic6wx6WEukrlZ3m8FOWVjLJ Osd8VmaxYIcgeLhoehMnIzWNfb/wF17Y3gR8Z4xA= 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 9643021F84FC for ; Wed, 23 May 2012 04:34:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 GjOsg7PqsqLM for ; Wed, 23 May 2012 04:34:52 -0700 (PDT) Received: from legolas.restena.lu (legolas.restena.lu [IPv6:2001:a18:1::34]) by ietfa.amsl.com (Postfix) with ESMTP id D91EF21F84A0 for ; Wed, 23 May 2012 04:34:51 -0700 (PDT) Received: from legolas.restena.lu (localhost [127.0.0.1]) by legolas.restena.lu (Postfix) with ESMTP id 89CD19DD22 for ; Wed, 23 May 2012 13:34:49 +0200 (CEST) Received: from [158.64.15.212] (212-15.vpn.restena.lu [158.64.15.212]) by legolas.restena.lu (Postfix) with ESMTPSA id 535749DD14 for ; Wed, 23 May 2012 13:34:49 +0200 (CEST) Message-ID: <4FBCCB57.7010606@restena.lu> Date: Wed, 23 May 2012 13:34:47 +0200 From: Stefan Winter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: radext@ietf.org References: <4FBBED0A.2050606@deployingradius.com> In-Reply-To: <4FBBED0A.2050606@deployingradius.com> X-Enigmail-Version: 1.4.1 X-Virus-Scanned: ClamAV Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Hi, on that topic, I've been wondering what good dynamic discovery can do here. The current draft only enables lookup of home servers for auth/acct purposes. It *could* be used the other way around though: when a user has logged in somewhere, and the "somewhere" includes the Operator-Name attribute (DNS-style), the home server could lookup the Operator-Name content in DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to. That would need lots of new text in the dyndisc draft - but I'm at it anyway, so if there's some support for the idea on the list, this could go in... Greetings, Stefan Winter On 22.05.12 21:46, Alan DeKok wrote: > Sanchez, Mauricio (HP Networking) wrote: >> Gentle reminder that we would appreciate hearing your thoughts, either >> positive or negative, on proposal below. > It looks good. > > I would tentatively propose discussion of 5176 and proxying of CoA > packets. The document is essentially silent on proxying. The main open > problem is: > > - how do you proxy CoA packets across multiple hops? > > Alan DeKok. > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From radext-bounces@ietf.org Wed May 23 06:07:28 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDC821F8738; Wed, 23 May 2012 06:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337778448; bh=uXe6trKGlXgOxyyhBgPcgVvqOLL270xg1nZ99aMt+CQ=; h=References:In-Reply-To:MIME-Version:From:Date:To:Message-ID: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Sender; b=CkI9/mWA3V1bngHq3DFRrtzs0cPaw06mp3X14frh90VyWNXlvAJ5mu+CBuYnje7VF kw0nCQ9ERufkhMrVh0JM2iAzYHgPsuPeFYWZTn10qwv1JmnTeNpcbchy3DaMifwf6x eoDz0PJyUAkzoIliYTHx1Rv0wNHWPy5waTNNx3Oo= 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 AF43A21F8738 for ; Wed, 23 May 2012 06:07:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.264 X-Spam-Level: X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] 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 6AqN9oft4w0J for ; Wed, 23 May 2012 06:07:27 -0700 (PDT) Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 078D821F8737 for ; Wed, 23 May 2012 06:07:26 -0700 (PDT) Received: from [10.254.252.134] (149-177.islandssimi.is [213.176.149.177]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 8727E20576; Wed, 23 May 2012 09:07:21 -0400 (EDT) References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> User-Agent: K-9 Mail for Android In-Reply-To: <4FBCCB57.7010606@restena.lu> MIME-Version: 1.0 From: Sam Hartman Date: Wed, 23 May 2012 13:07:04 +0000 To: Stefan Winter ,radext@ietf.org Message-ID: Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8071550901825583503==" Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org --===============8071550901825583503== Content-Type: multipart/alternative; boundary="----9W660FAPDOWYC1KGUU7A70V9IL4R4C" ------9W660FAPDOWYC1KGUU7A70V9IL4R4C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I just want to confirm that the work to permit fragmentation of RADIUS messages would be within scope -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Stefan Winter wrote: Hi, on that topic, I've been wondering what good dynamic discovery can do here. The current draft only enables lookup of home servers for auth/acct purposes. It *could* be used the other way around though: when a user has logged in somewhere, and the "somewhere" includes the Operator-Name attribute (DNS-style), the home server could lookup the Operator-Name content in DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to. That would need lots of new text in the dyndisc draft - but I'm at it anyway, so if there's some support for the idea on the list, this could go in... Greetings, Stefan Winter On 22.05.12 21:46, Alan DeKok wrote: > Sanchez, Mauricio (HP Networking) wrote: >> Gentle reminder that we would appreciate hearing your thoughts, either >> positive or negative, on proposal below. > It looks good. > > I would tentatively propose discussion of 5176 and proxying of CoA > packets. The document is essentially silent on proxying. The main open > problem is: > > - how do you proxy CoA packets across multiple hops? > > Alan DeKok. >_____________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _____________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext ------9W660FAPDOWYC1KGUU7A70V9IL4R4C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit I just want to confirm that the work to permit fragmentation of RADIUS messages would be within scope
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Stefan Winter <stefan.winter@restena.lu> wrote:
Hi,

on that topic, I've been wondering what good dynamic discovery can do here.

The current draft only enables lookup of home servers for auth/acct
purposes.

It *could* be used the other way around though: when a user has logged
in somewhere, and the "somewhere" includes the Operator-Name attribute
(DNS-style), the home server could lookup the Operator-Name content in
DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to.

That would need lots of new text in the dyndisc draft - but I'm at it
anyway, so if there's some support for the idea on the list, this could
go in...

Greetings,

Stefan Winter

On 22.05.12 21:46, Alan DeKok wrote:
> Sanchez, Mauricio (HP Networking) wrote:
>> Gentle reminder that we would appreciate hearing your thoughts, either
>> positive or negative, on proposal below.
>   It looks good.
>
>   I would tentatively propose discussion of 5176 and proxying of CoA
> packets.  The document is essentially silent on proxying.  The main open
> problem is:
>
>  - how do you proxy CoA packets across multiple hops?
>
>   Alan DeKok.
>

> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext


radext mailing list
radext@ietf.org
https://www.ietf.org/mailman/listinfo/radext

------9W660FAPDOWYC1KGUU7A70V9IL4R4C-- --===============8071550901825583503== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext --===============8071550901825583503==-- From hartmans@painless-security.com Wed May 23 06:07:27 2012 Return-Path: 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 AF43A21F8738 for ; Wed, 23 May 2012 06:07:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.264 X-Spam-Level: X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] 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 6AqN9oft4w0J for ; Wed, 23 May 2012 06:07:27 -0700 (PDT) Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 078D821F8737 for ; Wed, 23 May 2012 06:07:26 -0700 (PDT) Received: from [10.254.252.134] (149-177.islandssimi.is [213.176.149.177]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 8727E20576; Wed, 23 May 2012 09:07:21 -0400 (EDT) References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> User-Agent: K-9 Mail for Android In-Reply-To: <4FBCCB57.7010606@restena.lu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----9W660FAPDOWYC1KGUU7A70V9IL4R4C" From: Sam Hartman Date: Wed, 23 May 2012 13:07:04 +0000 To: Stefan Winter ,radext@ietf.org Message-ID: Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:07:27 -0000 ------9W660FAPDOWYC1KGUU7A70V9IL4R4C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I just want to confirm that the work to permit fragmentation of RADIUS messages would be within scope -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Stefan Winter wrote: Hi, on that topic, I've been wondering what good dynamic discovery can do here. The current draft only enables lookup of home servers for auth/acct purposes. It *could* be used the other way around though: when a user has logged in somewhere, and the "somewhere" includes the Operator-Name attribute (DNS-style), the home server could lookup the Operator-Name content in DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to. That would need lots of new text in the dyndisc draft - but I'm at it anyway, so if there's some support for the idea on the list, this could go in... Greetings, Stefan Winter On 22.05.12 21:46, Alan DeKok wrote: > Sanchez, Mauricio (HP Networking) wrote: >> Gentle reminder that we would appreciate hearing your thoughts, either >> positive or negative, on proposal below. > It looks good. > > I would tentatively propose discussion of 5176 and proxying of CoA > packets. The document is essentially silent on proxying. The main open > problem is: > > - how do you proxy CoA packets across multiple hops? > > Alan DeKok. >_____________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext _____________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext ------9W660FAPDOWYC1KGUU7A70V9IL4R4C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit I just want to confirm that the work to permit fragmentation of RADIUS messages would be within scope
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Stefan Winter <stefan.winter@restena.lu> wrote:
Hi,

on that topic, I've been wondering what good dynamic discovery can do here.

The current draft only enables lookup of home servers for auth/acct
purposes.

It *could* be used the other way around though: when a user has logged
in somewhere, and the "somewhere" includes the Operator-Name attribute
(DNS-style), the home server could lookup the Operator-Name content in
DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to.

That would need lots of new text in the dyndisc draft - but I'm at it
anyway, so if there's some support for the idea on the list, this could
go in...

Greetings,

Stefan Winter

On 22.05.12 21:46, Alan DeKok wrote:
> Sanchez, Mauricio (HP Networking) wrote:
>> Gentle reminder that we would appreciate hearing your thoughts, either
>> positive or negative, on proposal below.
>   It looks good.
>
>   I would tentatively propose discussion of 5176 and proxying of CoA
> packets.  The document is essentially silent on proxying.  The main open
> problem is:
>
>  - how do you proxy CoA packets across multiple hops?
>
>   Alan DeKok.
>

> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext


radext mailing list
radext@ietf.org
https://www.ietf.org/mailman/listinfo/radext

------9W660FAPDOWYC1KGUU7A70V9IL4R4C-- From radext-bounces@ietf.org Wed May 23 06:10:18 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F229F21F8547; Wed, 23 May 2012 06:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337778618; bh=BnLhvpWdtqepdtna9dvWBSOJurcyFTk9sENiOMfgU1c=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=RAZZ601rj8mK+VRVTb1wF8bOrJ4aPrGFo8HLRzWDZSLsnLEBcD2ALCRzlm4y7XERl x+fxS3piW0WQs5AvhuvIlhnYXwC6nrM/9PVhwG+zRVWSADt4ncMvYWNfEA0JZnrhft q/d/mQT+ffkODZikbwmiI8E3b6yq0XJ8m6ja5GeM= 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 C5CF121F8526 for ; Wed, 23 May 2012 06:10:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.855 X-Spam-Level: X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=0.745, 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 KuBchdf3Lqgd for ; Wed, 23 May 2012 06:10:16 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3D09421F84EA for ; Wed, 23 May 2012 06:10:16 -0700 (PDT) Message-ID: <4FBCE19C.5000503@deployingradius.com> Date: Wed, 23 May 2012 15:09:48 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Sam Hartman References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> In-Reply-To: X-Enigmail-Version: 0.96.0 Cc: Stefan Winter , radext@ietf.org Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Sam Hartman wrote: > I just want to confirm that the work to permit fragmentation of RADIUS > messages would be within scope I believe it should be. This is covered in the topic of "address packets longer than 4K" Alan DeKok. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From aland@deployingradius.com Wed May 23 06:10:16 2012 Return-Path: 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 C5CF121F8526 for ; Wed, 23 May 2012 06:10:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.855 X-Spam-Level: X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=0.745, 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 KuBchdf3Lqgd for ; Wed, 23 May 2012 06:10:16 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3D09421F84EA for ; Wed, 23 May 2012 06:10:16 -0700 (PDT) Message-ID: <4FBCE19C.5000503@deployingradius.com> Date: Wed, 23 May 2012 15:09:48 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Sam Hartman References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Stefan Winter , radext@ietf.org Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:10:16 -0000 Sam Hartman wrote: > I just want to confirm that the work to permit fragmentation of RADIUS > messages would be within scope I believe it should be. This is covered in the topic of "address packets longer than 4K" Alan DeKok. From trac+radext@trac.tools.ietf.org Wed May 23 06:17:04 2012 Return-Path: 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 47A0921F854E for ; Wed, 23 May 2012 06:17:04 -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 h3bftfkc8QpL for ; Wed, 23 May 2012 06:17:03 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id CF1F121F84FF for ; Wed, 23 May 2012 06:17:03 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBQp-0007zT-MB; Wed, 23 May 2012 09:16:51 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:16:51 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/117 Message-ID: <059.aca87fad3b5018cbcd2fffce863ddffc@trac.tools.ietf.org> X-Trac-Ticket-ID: 117 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523131703.CF1F121F84FF@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:17:03 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #117: typo X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:17:04 -0000 #117: typo typo in the introduction 'imnpractical' -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: trivial | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:17:06 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B58321F854E; Wed, 23 May 2012 06:17:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337779026; bh=R8T8hgZ7KDrmE7frJiwh+jB3mgg42bGa7Ce4Yr0WRi4=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=KPzE3kARqS4cIGK7+GRWUqdRXvTuF1FposAV/yOYdLivD3dfRtFE/cxmU/ohkXu4W TwEJEgBqNg16F4fDGcAYgcpfXEKTlLOSuTKkyJkqQMMDrXcPEONYEUYO0ejkqcjHk3 /1EGU4Ywd/cWdB8IP1Tdppgr2hgyk0AjzRDFh8oU= 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 47A0921F854E for ; Wed, 23 May 2012 06:17:04 -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 h3bftfkc8QpL for ; Wed, 23 May 2012 06:17:03 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id CF1F121F84FF for ; Wed, 23 May 2012 06:17:03 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBQp-0007zT-MB; Wed, 23 May 2012 09:16:51 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:16:51 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/117 Message-ID: <059.aca87fad3b5018cbcd2fffce863ddffc@trac.tools.ietf.org> X-Trac-Ticket-ID: 117 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523131703.CF1F121F84FF@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:17:03 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #117: typo X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExNzogdHlwbwoKIHR5cG8gaW4gdGhlIGludHJvZHVjdGlvbiAnaW1ucHJhY3RpY2FsJwoKLS0g Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICB8ICAgICAgT3du ZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8 ICBleHRlbnNpb25zQOKApgogUHJpb3JpdHk6ICB0cml2aWFsICAgICAgfCAgICAgU3RhdHVzOiAg bmV3CkNvbXBvbmVudDogIHJhZGl1cy0gICAgICB8ICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCiAg ZXh0ZW5zaW9ucyAgICAgICAgICAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAgSW4g V0cgTGFzdCAgIHwgICBLZXl3b3JkczoKICBDYWxsICAgICAgICAgICAgICAgICAgIHwKLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cv cmFkZXh0L3RyYWMvdGlja2V0LzExNz4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFk ZXh0Lz4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJh ZGV4dCBtYWlsaW5nIGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21h aWxtYW4vbGlzdGluZm8vcmFkZXh0Cg== From radext-bounces@ietf.org Wed May 23 06:28:06 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279F321F8604; Wed, 23 May 2012 06:28:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337779686; bh=sFu4KV56q3Ls67OqxaHisv9mxJbphrtuKrlYTzXj374=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=MMoVO1I4+0HSp/EtkRLi0/oSuf3iid9ZoP6Pqe8JfG1h/i7PvBuSoc6L9mAmwDmc2 0v6dg0g39sPpsitDxnGTTJy3+Ms2nFD2HYE78WOQ8jM2aaFnJEesXq+AqTeby7pQvl Iu3wWvOi1ynMVbBVK+iVErEPzEw05mvqlF3GcPPI= 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 7599621F8604 for ; Wed, 23 May 2012 06:28:05 -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=[AWL=0.000, 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 XIHd9k-WwsTQ for ; Wed, 23 May 2012 06:28:04 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 817D521F85D8 for ; Wed, 23 May 2012 06:28:04 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBbW-0004Js-HN; Wed, 23 May 2012 09:27:54 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:27:54 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/118 Message-ID: <059.4adbe55b2f2b7d5de3cae0253f7298b8@trac.tools.ietf.org> X-Trac-Ticket-ID: 118 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523132804.817D521F85D8@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:28:04 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #118: terminology refering BCP 26 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExODogdGVybWlub2xvZ3kgcmVmZXJpbmcgQkNQIDI2CgogSW4gU2VjdGlvbiAxLjI6CgogPiAg ICBUaGUgZm9sbG93aW5nIHRlcm1zIGFyZSB1c2VkIGhlcmUgd2l0aCB0aGUgbWVhbmluZ3MgZGVm aW5lZCBpbiBCQ1AKIDI2OiAgIm5hbWUgc3BhY2UiLCAiYXNzaWduZWQgdmFsdWUiLCAicmVnaXN0 cmF0aW9uIi4KCiA+ICAgICBUaGUgZm9sbG93aW5nIHRlcm1zIGFyZSB1c2VkIGhlcmUgd2l0aCB0 aGUgbWVhbmluZ3MgZGVmaW5lZCBpbiBCQ1AKIDI2OiAgIlByaXZhdGUgVXNlIiwgIlJlc2VydmVk IiwgIlVuYXNzaWduZWQiLgoKIFdoeSB0aGUgZGl2aXNpb24gaW4gdHdvIHNlcGFyYXRlIGdyb3Vw aW5ncz8gQkNQIDI2IGlzIHJlZmVyZW5jZSBbUkZDNTIyNl0KIC0gdGhpcyBzaG91bGQgYmUgbWFy a2VkCgotLSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgIHwg ICAgICBPd25lcjogIGRyYWZ0LWlldGYtcmFkZXh0LXJhZGl1cy0KICAgICBUeXBlOiAgZGVmZWN0 ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCmCiBQcmlvcml0eTogIHRyaXZpYWwgICAgICB8ICAgICBT dGF0dXM6ICBuZXcKQ29tcG9uZW50OiAgcmFkaXVzLSAgICAgIHwgIE1pbGVzdG9uZTogIG1pbGVz dG9uZTEKICBleHRlbnNpb25zICAgICAgICAgICAgIHwgICAgVmVyc2lvbjogIDEuMAogU2V2ZXJp dHk6ICBJbiBXRyBMYXN0ICAgfCAgIEtleXdvcmRzOgogIENhbGwgICAgICAgICAgICAgICAgICAg fAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0KClRpY2tldCBVUkw6IDxodHRwOi8vdHJhYy50b29scy5pZXRm Lm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTE4PgpyYWRleHQgPGh0dHA6Ly90b29scy5pZXRm Lm9yZy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0 Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Wed May 23 06:28:05 2012 Return-Path: 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 7599621F8604 for ; Wed, 23 May 2012 06:28:05 -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=[AWL=0.000, 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 XIHd9k-WwsTQ for ; Wed, 23 May 2012 06:28:04 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 817D521F85D8 for ; Wed, 23 May 2012 06:28:04 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBbW-0004Js-HN; Wed, 23 May 2012 09:27:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:27:54 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/118 Message-ID: <059.4adbe55b2f2b7d5de3cae0253f7298b8@trac.tools.ietf.org> X-Trac-Ticket-ID: 118 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523132804.817D521F85D8@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:28:04 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #118: terminology refering BCP 26 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:28:05 -0000 #118: terminology refering BCP 26 In Section 1.2: > The following terms are used here with the meanings defined in BCP 26: "name space", "assigned value", "registration". > The following terms are used here with the meanings defined in BCP 26: "Private Use", "Reserved", "Unassigned". Why the division in two separate groupings? BCP 26 is reference [RFC5226] - this should be marked -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: trivial | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From trac+radext@trac.tools.ietf.org Wed May 23 06:35:05 2012 Return-Path: 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 B9A4F21F854F for ; Wed, 23 May 2012 06:35:05 -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=[AWL=0.000, 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 W9oH+GXwh8GO for ; Wed, 23 May 2012 06:35:05 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6B421F854E for ; Wed, 23 May 2012 06:35:05 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBiJ-0001i8-AX; Wed, 23 May 2012 09:34:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:34:55 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/119 Message-ID: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> X-Trac-Ticket-ID: 119 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523133505.4C6B421F854E@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:35:05 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:35:05 -0000 #119: 'levels of compliance'? I am uneasy about defining 'levels of compliance' as in section 1.3: > An implementation is not compliant if it fails to satisfy one or more of the must or must not requirements for the protocols it implements. An implementation that satisfies all the MUST, MUST NOT, SHOULD, and SHOULD NOT requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the MUST and MUST NOT requirements but not all the SHOULD or SHOULD NOT requirements for its protocols is said to be "conditionally compliant". What purpose does this serve? Do we have this in other RADIUS / RADEXT documents, are these specific to RADIUS? -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: major | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:35:07 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2110021F8573; Wed, 23 May 2012 06:35:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337780107; bh=crUyciBha1sX09Rlup93qiQSfH6Q5oVCo2E4lPdvUg8=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=U+y6NH4e+GvfeuY7QdM/puB5m08Fm783L1l8o1lpk6QsxtgK/8Z74bbioQiAHgwNC XUAVgkQ9H7pGUi4ua+7zJBLpI6fZSgdZs7pHUOH9nbco/0SFd1yloU2em/rzXFz+NR aE3kxWXJnCOATUbuL2VZ6JHpmMwajw5WWP3XwlYc= 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 B9A4F21F854F for ; Wed, 23 May 2012 06:35:05 -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=[AWL=0.000, 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 W9oH+GXwh8GO for ; Wed, 23 May 2012 06:35:05 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6B421F854E for ; Wed, 23 May 2012 06:35:05 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBiJ-0001i8-AX; Wed, 23 May 2012 09:34:55 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:34:55 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/119 Message-ID: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> X-Trac-Ticket-ID: 119 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523133505.4C6B421F854E@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:35:05 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExOTogJ2xldmVscyBvZiBjb21wbGlhbmNlJz8KCiBJIGFtIHVuZWFzeSBhYm91dCBkZWZpbmlu ZyAnbGV2ZWxzIG9mIGNvbXBsaWFuY2UnIGFzIGluIHNlY3Rpb24gMS4zOgoKID4gQW4gaW1wbGVt ZW50YXRpb24gaXMgbm90IGNvbXBsaWFudCBpZiBpdCBmYWlscyB0byBzYXRpc2Z5IG9uZSBvciBt b3JlIG9mCiB0aGUgbXVzdCBvciBtdXN0IG5vdCByZXF1aXJlbWVudHMgZm9yIHRoZSBwcm90b2Nv bHMgaXQgaW1wbGVtZW50cy4gQW4KIGltcGxlbWVudGF0aW9uIHRoYXQgc2F0aXNmaWVzIGFsbCB0 aGUgTVVTVCwgTVVTVCBOT1QsIFNIT1VMRCwgYW5kIFNIT1VMRAogTk9UIHJlcXVpcmVtZW50cyBm b3IgaXRzIHByb3RvY29scyBpcyBzYWlkIHRvIGJlICJ1bmNvbmRpdGlvbmFsbHkKIGNvbXBsaWFu dCI7IG9uZSB0aGF0IHNhdGlzZmllcyBhbGwgdGhlIE1VU1QgYW5kIE1VU1QgTk9UIHJlcXVpcmVt ZW50cyBidXQKIG5vdCBhbGwgdGhlIFNIT1VMRCBvciBTSE9VTEQgTk9UIHJlcXVpcmVtZW50cyBm b3IgaXRzIHByb3RvY29scyBpcyBzYWlkIHRvCiBiZSAiY29uZGl0aW9uYWxseSBjb21wbGlhbnQi LgoKIFdoYXQgcHVycG9zZSBkb2VzIHRoaXMgc2VydmU/IERvIHdlIGhhdmUgdGhpcyBpbiBvdGhl ciBSQURJVVMgLyBSQURFWFQKIGRvY3VtZW50cywgYXJlIHRoZXNlIHNwZWNpZmljIHRvIFJBRElV Uz8KCi0tIAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KIFJlcG9ydGVyOiAgZHJvbWFzY2FA4oCmICAgfCAg ICAgIE93bmVyOiAgZHJhZnQtaWV0Zi1yYWRleHQtcmFkaXVzLQogICAgIFR5cGU6ICBkZWZlY3Qg ICAgICAgfCAgZXh0ZW5zaW9uc0DigKYKIFByaW9yaXR5OiAgbWFqb3IgICAgICAgIHwgICAgIFN0 YXR1czogIG5ldwpDb21wb25lbnQ6ICByYWRpdXMtICAgICAgfCAgTWlsZXN0b25lOiAgbWlsZXN0 b25lMQogIGV4dGVuc2lvbnMgICAgICAgICAgICAgfCAgICBWZXJzaW9uOiAgMS4wCiBTZXZlcml0 eTogIEluIFdHIExhc3QgICB8ICAgS2V5d29yZHM6CiAgQ2FsbCAgICAgICAgICAgICAgICAgICB8 Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYu b3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMTk+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYu b3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRm Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From radext-bounces@ietf.org Wed May 23 06:40:26 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B7A21F86F6; Wed, 23 May 2012 06:40:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337780426; bh=sqTQbk6e3+Zi3D2w+AQ957ye0qlE6agkD049QhdGI+E=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=gKyg7My0+Uk351cjDLmWySKXfngL4WbCpuKsI+2p7k+QceMHMzyKtKxfgsCR71LqV g+8y+LEq7jZ+WEbH2dChupGnuAi0CURx6uf6gwQjT8g1v24b6i7X6+EfOa5j35cLAZ p9PVPSqwMQ+w9EN+VCsg+oiwEIKf7WTLtD03j+/o= 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 E66F021F86F5 for ; Wed, 23 May 2012 06:40:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.227 X-Spam-Level: X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 fSDQyADW8soG for ; Wed, 23 May 2012 06:40:24 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC6E21F86F4 for ; Wed, 23 May 2012 06:40:22 -0700 (PDT) Message-ID: <4FBCE8AB.3040702@deployingradius.com> Date: Wed, 23 May 2012 15:39:55 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Stefan Winter References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> In-Reply-To: <4FBCCB57.7010606@restena.lu> X-Enigmail-Version: 0.96.0 Cc: radext@ietf.org Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Stefan Winter wrote: > on that topic, I've been wondering what good dynamic discovery can do here. Something, I'm sure. :) > The current draft only enables lookup of home servers for auth/acct > purposes. > > It *could* be used the other way around though: when a user has logged > in somewhere, and the "somewhere" includes the Operator-Name attribute > (DNS-style), the home server could lookup the Operator-Name content in > DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to. > > That would need lots of new text in the dyndisc draft - but I'm at it > anyway, so if there's some support for the idea on the list, this could > go in... I'd prefer to publish the document now. Get it done, published, and deployed. We can then have a separate document which addresses CoA proxying. It can leverage 5580, and the dynamic discovery document. For anyone with spare time, see the git "master" branch on: https://github.com/alandekok/freeradius-server/ It has preliminary support for CoA proxying via Operator-Name. This should be sufficient for multi-hop CoA proxying. The remaining issue is how to get from the "local" RADIUS proxy to the NAS. Using Operator-Name won't work, as the "local" proxy is authoritative for that realm. Something else is needed, like a NAS identifier. We could use NAS-IP-Address. But that could have been changed or deleted by anyone. Maybe NAS-Identifier is a better choice. Alan DeKok. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From aland@deployingradius.com Wed May 23 06:40:24 2012 Return-Path: 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 E66F021F86F5 for ; Wed, 23 May 2012 06:40:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.227 X-Spam-Level: X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 fSDQyADW8soG for ; Wed, 23 May 2012 06:40:24 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC6E21F86F4 for ; Wed, 23 May 2012 06:40:22 -0700 (PDT) Message-ID: <4FBCE8AB.3040702@deployingradius.com> Date: Wed, 23 May 2012 15:39:55 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Stefan Winter References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> In-Reply-To: <4FBCCB57.7010606@restena.lu> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: radext@ietf.org Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:40:25 -0000 Stefan Winter wrote: > on that topic, I've been wondering what good dynamic discovery can do here. Something, I'm sure. :) > The current draft only enables lookup of home servers for auth/acct > purposes. > > It *could* be used the other way around though: when a user has logged > in somewhere, and the "somewhere" includes the Operator-Name attribute > (DNS-style), the home server could lookup the Operator-Name content in > DNS (NAPTR entry TBD) to find out where to send CoA packets for his user to. > > That would need lots of new text in the dyndisc draft - but I'm at it > anyway, so if there's some support for the idea on the list, this could > go in... I'd prefer to publish the document now. Get it done, published, and deployed. We can then have a separate document which addresses CoA proxying. It can leverage 5580, and the dynamic discovery document. For anyone with spare time, see the git "master" branch on: https://github.com/alandekok/freeradius-server/ It has preliminary support for CoA proxying via Operator-Name. This should be sufficient for multi-hop CoA proxying. The remaining issue is how to get from the "local" RADIUS proxy to the NAS. Using Operator-Name won't work, as the "local" proxy is authoritative for that realm. Something else is needed, like a NAS identifier. We could use NAS-IP-Address. But that could have been changed or deleted by anyone. Maybe NAS-Identifier is a better choice. Alan DeKok. From radext-bounces@ietf.org Wed May 23 06:43:31 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2594121F8705; Wed, 23 May 2012 06:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337780611; bh=8qBTYrnKD9rrcpOOvztZUW+wXuMH+bcW129d+7fLwhQ=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=cfOLcMnK/nE0iO6i0ixZCY4r8yU+rsmjomnwdL/oXKkUDFsGfpJl25dM2h7aJm7UO T8XEfdGj9T75MTUoV6RNnHWQT3pB7aPUrJctTv6ruf9X2K4Z84WxwCNq50DB7IkQAy 8XvxRcRKcCugPkhnvon83FfF2CpNV5pEH20q27Ns= 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 9BCB821F8703 for ; Wed, 23 May 2012 06:43:29 -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=[AWL=0.000, 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 q5DpygEJNPIs for ; Wed, 23 May 2012 06:43:29 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 170CC21F8701 for ; Wed, 23 May 2012 06:43:29 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBqT-00032V-0p; Wed, 23 May 2012 09:43:21 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:43:20 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/120 Message-ID: <059.24d486b066046e8a681cdcacd8f8c959@trac.tools.ietf.org> X-Trac-Ticket-ID: 120 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523134329.170CC21F8701@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:43:29 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #120: ambiguity in the definition of Extended Type X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyMDogYW1iaWd1aXR5IGluIHRoZSBkZWZpbml0aW9uIG9mIEV4dGVuZGVkIFR5cGUKCiBJbiBT ZWN0aW9uIDIuMToKCiA+ICAgIFRoZSBhZGRpdGlvbiBvZiB0aGUgRXh0ZW5kZWQtVHlwZSBmaWVs ZCBkZWNyZWFzZXMgdGhlIG1heGltdW0gbGVuZ3RoCiBmb3IgYXR0cmlidXRlcyBvZiB0eXBlICJ0 ZXh0IiBvciAic3RyaW5nIiBmcm9tIDI1MyB0byAyNTIgb2N0ZXRzLiAgV2hlcmUKIGFuIEF0dHJp YnV0ZSBuZWVkcyB0byBjYXJyeSBtb3JlIHRoYW4gMjUyIG9jdGV0cyBvZiBkYXRhLCB0aGUgIkxv bmcKIEV4dGVuZGVkIFR5cGUiIGZvcm1hdCBzaG91bGQgYmUgdXNlZC4KCiBJIHN1Z2dlc3Q6IFdo ZXJlIHN1Y2ggYW4gQXR0cmlidXRlIG5lZWRzIHRvIGNhcnJ5IG1vcmUgdGhhbiAyNTIgb2N0ZXRz IG9mCiBkYXRhLCB0aGUgIkxvbmcgRXh0ZW5kZWQgVHlwZSIgZm9ybWF0IFNIT1VMRCBiZSB1c2Vk LgoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICB8ICAg ICAgT3duZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAg ICAgICB8ICBleHRlbnNpb25zQOKApgogUHJpb3JpdHk6ICBtaW5vciAgICAgICAgfCAgICAgU3Rh dHVzOiAgbmV3CkNvbXBvbmVudDogIHJhZGl1cy0gICAgICB8ICBNaWxlc3RvbmU6ICBtaWxlc3Rv bmUxCiAgZXh0ZW5zaW9ucyAgICAgICAgICAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5 OiAgSW4gV0cgTGFzdCAgIHwgICBLZXl3b3JkczoKICBDYWxsICAgICAgICAgICAgICAgICAgIHwK LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5v cmcvd2cvcmFkZXh0L3RyYWMvdGlja2V0LzEyMD4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5v cmcvcmFkZXh0Lz4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fCnJhZGV4dCBtYWlsaW5nIGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYu b3JnL21haWxtYW4vbGlzdGluZm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Wed May 23 06:43:29 2012 Return-Path: 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 9BCB821F8703 for ; Wed, 23 May 2012 06:43:29 -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=[AWL=0.000, 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 q5DpygEJNPIs for ; Wed, 23 May 2012 06:43:29 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 170CC21F8701 for ; Wed, 23 May 2012 06:43:29 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBqT-00032V-0p; Wed, 23 May 2012 09:43:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:43:20 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/120 Message-ID: <059.24d486b066046e8a681cdcacd8f8c959@trac.tools.ietf.org> X-Trac-Ticket-ID: 120 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523134329.170CC21F8701@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:43:29 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #120: ambiguity in the definition of Extended Type X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:43:29 -0000 #120: ambiguity in the definition of Extended Type In Section 2.1: > The addition of the Extended-Type field decreases the maximum length for attributes of type "text" or "string" from 253 to 252 octets. Where an Attribute needs to carry more than 252 octets of data, the "Long Extended Type" format should be used. I suggest: Where such an Attribute needs to carry more than 252 octets of data, the "Long Extended Type" format SHOULD be used. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: minor | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From trac+radext@trac.tools.ietf.org Wed May 23 06:49:51 2012 Return-Path: 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 A74D721F843E for ; Wed, 23 May 2012 06:49:51 -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=[AWL=0.000, 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 186zIPfMcQLZ for ; Wed, 23 May 2012 06:49:51 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 56A3021F857F for ; Wed, 23 May 2012 06:49:44 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBwW-0002P4-O1; Wed, 23 May 2012 09:49:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:49:36 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/121 Message-ID: <059.dbb78a615a69c01870660add53891380@trac.tools.ietf.org> X-Trac-Ticket-ID: 121 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523134944.56A3021F857F@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:49:44 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #121: inconsistent formulation X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:49:51 -0000 #121: inconsistent formulation In Section 2.2 when defining M (More) field: > If a client or server receives an attribute fragment with the "More" field set (1), but for which no subsequent fragment can be found, then the fragmented attribute is deemed to be an "invalid attribute", and handled as per Section 2.7, below. To be consistent with previous text: s/is deemed to be/MUST be deemed to be/ I actually would prefer 'considered' to 'deemed' in all places, but this is a minor language preference of a non-English speaker. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: minor | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:49:53 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84A7C21F847B; Wed, 23 May 2012 06:49:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337780993; bh=dhlX0fNYANwxVePNqkVS2eTldDGh5+6h79DkNHGbQ1U=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=fa/q8o09UU5JC3QQsVzFp9UrFysBMMYSS686gHyEURysXGzOEkQ8RKoz6E2UYDIA9 PAn9qH7RG1ysnGYb/SfwMuLdrm5KQHk5GOqJiRk1U2/qnLDkcdVenYegPG37/6AbJg YH0ORhJkcjecE5+xTB6aTU9YsZMw0FVWhSVqFecc= 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 A74D721F843E for ; Wed, 23 May 2012 06:49:51 -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=[AWL=0.000, 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 186zIPfMcQLZ for ; Wed, 23 May 2012 06:49:51 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 56A3021F857F for ; Wed, 23 May 2012 06:49:44 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXBwW-0002P4-O1; Wed, 23 May 2012 09:49:36 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:49:36 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/121 Message-ID: <059.dbb78a615a69c01870660add53891380@trac.tools.ietf.org> X-Trac-Ticket-ID: 121 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523134944.56A3021F857F@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:49:44 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #121: inconsistent formulation X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyMTogaW5jb25zaXN0ZW50IGZvcm11bGF0aW9uCgogSW4gU2VjdGlvbiAyLjIgd2hlbiBkZWZp bmluZyBNIChNb3JlKSBmaWVsZDoKCiA+ICAgICBJZiBhIGNsaWVudCBvciBzZXJ2ZXIgcmVjZWl2 ZXMgYW4gYXR0cmlidXRlIGZyYWdtZW50IHdpdGggdGhlICJNb3JlIgogZmllbGQgc2V0ICgxKSwg YnV0IGZvciB3aGljaCBubyBzdWJzZXF1ZW50IGZyYWdtZW50IGNhbiBiZSBmb3VuZCwgdGhlbiB0 aGUKIGZyYWdtZW50ZWQgYXR0cmlidXRlIGlzIGRlZW1lZCB0byBiZSBhbiAiaW52YWxpZCBhdHRy aWJ1dGUiLCBhbmQgaGFuZGxlZAogYXMgcGVyIFNlY3Rpb24gMi43LCBiZWxvdy4KCiBUbyBiZSBj b25zaXN0ZW50IHdpdGggcHJldmlvdXMgdGV4dDogcy9pcyBkZWVtZWQgdG8gYmUvTVVTVCBiZSBk ZWVtZWQgdG8KIGJlLwoKIEkgYWN0dWFsbHkgd291bGQgcHJlZmVyICdjb25zaWRlcmVkJyB0byAn ZGVlbWVkJyBpbiBhbGwgcGxhY2VzLCBidXQgdGhpcwogaXMgYSBtaW5vciBsYW5ndWFnZSBwcmVm ZXJlbmNlIG9mIGEgbm9uLUVuZ2xpc2ggc3BlYWtlci4KCi0tIAotLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0K IFJlcG9ydGVyOiAgZHJvbWFzY2FA4oCmICAgfCAgICAgIE93bmVyOiAgZHJhZnQtaWV0Zi1yYWRl eHQtcmFkaXVzLQogICAgIFR5cGU6ICBkZWZlY3QgICAgICAgfCAgZXh0ZW5zaW9uc0DigKYKIFBy aW9yaXR5OiAgbWlub3IgICAgICAgIHwgICAgIFN0YXR1czogIG5ldwpDb21wb25lbnQ6ICByYWRp dXMtICAgICAgfCAgTWlsZXN0b25lOiAgbWlsZXN0b25lMQogIGV4dGVuc2lvbnMgICAgICAgICAg ICAgfCAgICBWZXJzaW9uOiAgMS4wCiBTZXZlcml0eTogIEluIFdHIExhc3QgICB8ICAgS2V5d29y ZHM6CiAgQ2FsbCAgICAgICAgICAgICAgICAgICB8Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0 IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8x MjE+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJh ZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4 dAo= From trac+radext@trac.tools.ietf.org Wed May 23 06:55:53 2012 Return-Path: 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 5E98121F845C for ; Wed, 23 May 2012 06:55:53 -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=[AWL=0.000, 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 JIro0OMRmbwn for ; Wed, 23 May 2012 06:55:53 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2EB21F86F7 for ; Wed, 23 May 2012 06:55:52 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC2S-0006FP-Ou; Wed, 23 May 2012 09:55:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:55:44 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/120#comment:1 Message-ID: <074.ff2a430a9261e9d2d6a7f661f9b01264@trac.tools.ietf.org> References: <059.24d486b066046e8a681cdcacd8f8c959@trac.tools.ietf.org> X-Trac-Ticket-ID: 120 In-Reply-To: <059.24d486b066046e8a681cdcacd8f8c959@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523135552.2B2EB21F86F7@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:55:52 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #120: ambiguity in the definition of Extended Type X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:55:53 -0000 #120: ambiguity in the definition of Extended Type Comment (by aland@…): I agree with this. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: minor | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:55:54 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E24E521F8700; Wed, 23 May 2012 06:55:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781354; bh=Lntlwveowd6Br1HtZt41Pc23qEmCymR1jEtdDAGk2Rs=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=lW95i4eA6AIsbqzsrGFH6LVSUZ/++trcVrjCq3RYk05t5QYkOlWp3LOmQ6X07gpZw 4rVGAV4KbBPr/lLn3l6x5MHY8bifh0fosy9WMixJc6FpVzP0J46A7ozdap6PIg0mSJ y7nCHlGWLnXOsPNsF7/GYO18hS65Rg2bGxPmOMMM= 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 5E98121F845C for ; Wed, 23 May 2012 06:55:53 -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=[AWL=0.000, 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 JIro0OMRmbwn for ; Wed, 23 May 2012 06:55:53 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2EB21F86F7 for ; Wed, 23 May 2012 06:55:52 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC2S-0006FP-Ou; Wed, 23 May 2012 09:55:44 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:55:44 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/120#comment:1 Message-ID: <074.ff2a430a9261e9d2d6a7f661f9b01264@trac.tools.ietf.org> References: <059.24d486b066046e8a681cdcacd8f8c959@trac.tools.ietf.org> X-Trac-Ticket-ID: 120 In-Reply-To: <059.24d486b066046e8a681cdcacd8f8c959@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523135552.2B2EB21F86F7@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:55:52 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #120: ambiguity in the definition of Extended Type X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyMDogYW1iaWd1aXR5IGluIHRoZSBkZWZpbml0aW9uIG9mIEV4dGVuZGVkIFR5cGUKCgpDb21t ZW50IChieSBhbGFuZEDigKYpOgoKIEkgYWdyZWUgd2l0aCB0aGlzLgoKLS0gCi0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICB8ICAgICAgIE93bmVyOiAgZHJhZnQt aWV0Zi1yYWRleHQtcmFkaXVzLQogICAgIFR5cGU6ICBkZWZlY3QgICAgICAgfCAgZXh0ZW5zaW9u c0DigKYKIFByaW9yaXR5OiAgbWlub3IgICAgICAgIHwgICAgICBTdGF0dXM6ICBuZXcKQ29tcG9u ZW50OiAgcmFkaXVzLSAgICAgIHwgICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCiAgZXh0ZW5zaW9u cyAgICAgICAgICAgICB8ICAgICBWZXJzaW9uOiAgMS4wCiBTZXZlcml0eTogIEluIFdHIExhc3Qg ICB8ICBSZXNvbHV0aW9uOgogIENhbGwgICAgICAgICAgICAgICAgICAgfAogS2V5d29yZHM6ICAg ICAgICAgICAgICAgfAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KClRpY2tldCBVUkw6IDxodHRwOi8vdHJh Yy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTIwI2NvbW1lbnQ6MT4KcmFk ZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0Lz4KCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4dCBtYWlsaW5nIGxpc3QKcmFkZXh0QGll dGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Wed May 23 06:56:32 2012 Return-Path: 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 568D321F86C1 for ; Wed, 23 May 2012 06:56:32 -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 aTzWXWTAnP6U for ; Wed, 23 May 2012 06:56:32 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id E316621F8466 for ; Wed, 23 May 2012 06:56:31 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC3B-0006Ka-Um; Wed, 23 May 2012 09:56:29 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:56:29 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/117#comment:1 Message-ID: <074.4405d4804c5c83118feef8fcfb3797f1@trac.tools.ietf.org> References: <059.aca87fad3b5018cbcd2fffce863ddffc@trac.tools.ietf.org> X-Trac-Ticket-ID: 117 In-Reply-To: <059.aca87fad3b5018cbcd2fffce863ddffc@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523135631.E316621F8466@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:56:31 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #117: typo X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:56:32 -0000 #117: typo Comment (by aland@…): I agree with this. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: trivial | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:56:34 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 624CB21F86C1; Wed, 23 May 2012 06:56:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781394; bh=1ri++54AJ/w7EnGAKKXWYeKu1+kSDXuuY9z46ckGB+o=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=o9kt8Ay+/AQjE1zxFvY/f0zBM00Oq06GZ4LqI9pkKfqu2Sg6Xso1k0vNcN73/SoVB K7q1ajOMQcDS6dEjqobsPC+HYuxIxKnZTIF+jzoPkUOmmxCzYO6cgq4f/LJBjWvxyd EF07SqmmldX+0tD88638MSG9EdmDWTdzvKMmY1Ko= 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 568D321F86C1 for ; Wed, 23 May 2012 06:56:32 -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 aTzWXWTAnP6U for ; Wed, 23 May 2012 06:56:32 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id E316621F8466 for ; Wed, 23 May 2012 06:56:31 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC3B-0006Ka-Um; Wed, 23 May 2012 09:56:29 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:56:29 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/117#comment:1 Message-ID: <074.4405d4804c5c83118feef8fcfb3797f1@trac.tools.ietf.org> References: <059.aca87fad3b5018cbcd2fffce863ddffc@trac.tools.ietf.org> X-Trac-Ticket-ID: 117 In-Reply-To: <059.aca87fad3b5018cbcd2fffce863ddffc@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523135631.E316621F8466@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:56:31 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #117: typo X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExNzogdHlwbwoKCkNvbW1lbnQgKGJ5IGFsYW5kQOKApik6CgogSSBhZ3JlZSB3aXRoIHRoaXMu CgotLSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgIHwgICAg ICAgT3duZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAg ICAgICB8ICBleHRlbnNpb25zQOKApgogUHJpb3JpdHk6ICB0cml2aWFsICAgICAgfCAgICAgIFN0 YXR1czogIG5ldwpDb21wb25lbnQ6ICByYWRpdXMtICAgICAgfCAgIE1pbGVzdG9uZTogIG1pbGVz dG9uZTEKICBleHRlbnNpb25zICAgICAgICAgICAgIHwgICAgIFZlcnNpb246ICAxLjAKIFNldmVy aXR5OiAgSW4gV0cgTGFzdCAgIHwgIFJlc29sdXRpb246CiAgQ2FsbCAgICAgICAgICAgICAgICAg ICB8CiBLZXl3b3JkczogICAgICAgICAgICAgICB8Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0 IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8x MTcjY29tbWVudDoxPgpyYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxp bmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0 aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Wed May 23 06:58:40 2012 Return-Path: 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 AD3D621F86F7 for ; Wed, 23 May 2012 06:58:40 -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=[AWL=0.000, 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 5RXOZatIogct for ; Wed, 23 May 2012 06:58:40 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id E992521F848C for ; Wed, 23 May 2012 06:58:39 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC5F-0006P0-HZ; Wed, 23 May 2012 09:58:37 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:58:37 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/118#comment:1 Message-ID: <074.7ddff0a511b4e5bf20dcc560d497dce4@trac.tools.ietf.org> References: <059.4adbe55b2f2b7d5de3cae0253f7298b8@trac.tools.ietf.org> X-Trac-Ticket-ID: 118 In-Reply-To: <059.4adbe55b2f2b7d5de3cae0253f7298b8@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523135839.E992521F848C@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:58:39 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #118: terminology refering BCP 26 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:58:41 -0000 #118: terminology refering BCP 26 Comment (by aland@…): I'll change the text to: The following terms are used here with the meanings defined in BCP 26 [RFC5226]: "name space", "assigned value", "registration", "Private Use", "Reserved", "Unassigned", "IETF Review", and "Standards Action". -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: trivial | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:58:42 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F400821F86FE; Wed, 23 May 2012 06:58:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781522; bh=HYiDuqSo8rVQuejLxzw5b6wIqoa5FviF/8v3xdyA7z0=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=W0wNjhWQzC95HgyFX/fvZdXgzN5S8ZdHMIVPAgi/4Y5fgekEWt1nwWicC8dmU8OfH NygFOo6AyRBH881SBBrFit77htQhujZu5GI63/IXJgpwGL4J51XB1OnQCWJZ5pPv/e v+UIcWny/bRxQ261kwoH9kWOXiMgF0wg1eq5FkzU= 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 AD3D621F86F7 for ; Wed, 23 May 2012 06:58:40 -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=[AWL=0.000, 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 5RXOZatIogct for ; Wed, 23 May 2012 06:58:40 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id E992521F848C for ; Wed, 23 May 2012 06:58:39 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC5F-0006P0-HZ; Wed, 23 May 2012 09:58:37 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:58:37 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/118#comment:1 Message-ID: <074.7ddff0a511b4e5bf20dcc560d497dce4@trac.tools.ietf.org> References: <059.4adbe55b2f2b7d5de3cae0253f7298b8@trac.tools.ietf.org> X-Trac-Ticket-ID: 118 In-Reply-To: <059.4adbe55b2f2b7d5de3cae0253f7298b8@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523135839.E992521F848C@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 06:58:39 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #118: terminology refering BCP 26 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExODogdGVybWlub2xvZ3kgcmVmZXJpbmcgQkNQIDI2CgoKQ29tbWVudCAoYnkgYWxhbmRA4oCm KToKCiBJJ2xsIGNoYW5nZSB0aGUgdGV4dCB0bzoKCiBUaGUgZm9sbG93aW5nIHRlcm1zIGFyZSB1 c2VkIGhlcmUgd2l0aCB0aGUgbWVhbmluZ3MgZGVmaW5lZCBpbiBCQ1AgMjYKIFtSRkM1MjI2XTog Im5hbWUgc3BhY2UiLCAiYXNzaWduZWQgdmFsdWUiLCAicmVnaXN0cmF0aW9uIiwgIlByaXZhdGUK IFVzZSIsICJSZXNlcnZlZCIsICJVbmFzc2lnbmVkIiwgIklFVEYgUmV2aWV3IiwgYW5kICJTdGFu ZGFyZHMgQWN0aW9uIi4KCi0tIAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KIFJlcG9ydGVyOiAgZHJvbWFz Y2FA4oCmICAgfCAgICAgICBPd25lcjogIGRyYWZ0LWlldGYtcmFkZXh0LXJhZGl1cy0KICAgICBU eXBlOiAgZGVmZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCmCiBQcmlvcml0eTogIHRyaXZpYWwg ICAgICB8ICAgICAgU3RhdHVzOiAgbmV3CkNvbXBvbmVudDogIHJhZGl1cy0gICAgICB8ICAgTWls ZXN0b25lOiAgbWlsZXN0b25lMQogIGV4dGVuc2lvbnMgICAgICAgICAgICAgfCAgICAgVmVyc2lv bjogIDEuMAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0ICAgfCAgUmVzb2x1dGlvbjoKICBDYWxsICAg ICAgICAgICAgICAgICAgIHwKIEtleXdvcmRzOiAgICAgICAgICAgICAgIHwKLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFkZXh0 L3RyYWMvdGlja2V0LzExOCNjb21tZW50OjE+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYub3Jn L3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Wed May 23 06:58:48 2012 Return-Path: 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 F107F21F86F7 for ; Wed, 23 May 2012 06:58:47 -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 1-eTf3RzDv+A for ; Wed, 23 May 2012 06:58:47 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2F02D21F848C for ; Wed, 23 May 2012 06:58:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC5M-0006PB-GY; Wed, 23 May 2012 09:58:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:58:44 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/122 Message-ID: <059.4466e9f5a192fb115d896d5abab0ac0c@trac.tools.ietf.org> X-Trac-Ticket-ID: 122 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #122: IANA policy described in 2.3 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 13:58:48 -0000 #122: IANA policy described in 2.3 In section 2.3: > Up-to-date values of this field are specified by IANA. IANA does not write specifications, better say 'Up-to-date values of this field are being added according to the policies and rules described in Section 10'. -- ---------------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: extended-attributes | Version: 1.0 Severity: In WG Last Call | Keywords: ---------------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Wed May 23 06:58:51 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9272E21F86F7; Wed, 23 May 2012 06:58:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781531; bh=MnDMBqgRHyYllB/J41psgvuS40gO9nmrLNrgtYwdqes=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=Q0Ww8pBrH7jcH3KIZScihf51D2A5HIUPD4I/0MaD2p8daBFBdfuDPBdShgjW0Ca/h jNz05LaCKTRR7VcyhfQsh5GVyyA01Y0s2M+QXur9WKh1YBxs84qQC3FuiRxM9wVpvd 8P1vfhNMKiv4pZq1MhD3mKlv1DiNAmTCHDA4jiQQ= 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 F107F21F86F7 for ; Wed, 23 May 2012 06:58:47 -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 1-eTf3RzDv+A for ; Wed, 23 May 2012 06:58:47 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2F02D21F848C for ; Wed, 23 May 2012 06:58:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC5M-0006PB-GY; Wed, 23 May 2012 09:58:44 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 13:58:44 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/122 Message-ID: <059.4466e9f5a192fb115d896d5abab0ac0c@trac.tools.ietf.org> X-Trac-Ticket-ID: 122 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #122: IANA policy described in 2.3 X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyMjogSUFOQSBwb2xpY3kgZGVzY3JpYmVkIGluIDIuMwoKIEluIHNlY3Rpb24gMi4zOgoKID4g VXAtdG8tZGF0ZSB2YWx1ZXMgb2YgdGhpcyBmaWVsZCBhcmUgc3BlY2lmaWVkIGJ5IElBTkEuCgog SUFOQSBkb2VzIG5vdCB3cml0ZSBzcGVjaWZpY2F0aW9ucywgYmV0dGVyIHNheSAnVXAtdG8tZGF0 ZSB2YWx1ZXMgb2YgdGhpcwogZmllbGQgYXJlIGJlaW5nIGFkZGVkIGFjY29yZGluZyB0byB0aGUg cG9saWNpZXMgYW5kIHJ1bGVzIGRlc2NyaWJlZCBpbgogU2VjdGlvbiAxMCcuCgotLSAKLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogUmVw b3J0ZXI6ICBkcm9tYXNjYUDigKYgICAgICAgICAgIHwgICAgICBPd25lcjoKICAgICBUeXBlOiAg ZGVmZWN0ICAgICAgICAgICAgICAgfCAgICAgU3RhdHVzOiAgbmV3CiBQcmlvcml0eTogIG1pbm9y ICAgICAgICAgICAgICAgIHwgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEKQ29tcG9uZW50OiAgZXh0 ZW5kZWQtYXR0cmlidXRlcyAgfCAgICBWZXJzaW9uOiAgMS4wCiBTZXZlcml0eTogIEluIFdHIExh c3QgQ2FsbCAgICAgIHwgICBLZXl3b3JkczoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRv b2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMjI+CnJhZGV4dCA8aHR0cDovL3Rv b2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Wed May 23 07:01:43 2012 Return-Path: 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 43D9321F86AD for ; Wed, 23 May 2012 07:01:43 -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 6JMnV2OKJJ9e for ; Wed, 23 May 2012 07:01:42 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id CFE7821F85D8 for ; Wed, 23 May 2012 07:01:42 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC8A-0002N3-3a; Wed, 23 May 2012 10:01:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:01:38 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/119#comment:1 Message-ID: <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> References: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> X-Trac-Ticket-ID: 119 In-Reply-To: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523140142.CFE7821F85D8@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:01:42 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:01:43 -0000 #119: 'levels of compliance'? Comment (by aland@…): This text is also in RFC 2865 Section 1.1. The text may not be strictly necessary. I'm open to feedback. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: major | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 07:01:50 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 078A421F86AD; Wed, 23 May 2012 07:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781710; bh=kbdk0B9c/tMxM7FCA6c54DaeKRT0HVxWjF2KxejKboo=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=lrA4uN64yBDDYx7Tk0XZH3jJgKO9pk7bsyZ0udMCc/Ik3Nllk6olISXujWJoqKYA8 3STCk2jyuazXc2UtbtnLm6vYVjNt9A6edZ3Kdvc6bmOZtXsubg7fsWzibotsogTiu/ UXqq4C1+Sl3LDrjfI3sAlsqs5HRnK8pSYjEfCbeY= 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 43D9321F86AD for ; Wed, 23 May 2012 07:01:43 -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 6JMnV2OKJJ9e for ; Wed, 23 May 2012 07:01:42 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id CFE7821F85D8 for ; Wed, 23 May 2012 07:01:42 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXC8A-0002N3-3a; Wed, 23 May 2012 10:01:38 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:01:38 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/119#comment:1 Message-ID: <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> References: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> X-Trac-Ticket-ID: 119 In-Reply-To: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523140142.CFE7821F85D8@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:01:42 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzExOTogJ2xldmVscyBvZiBjb21wbGlhbmNlJz8KCgpDb21tZW50IChieSBhbGFuZEDigKYpOgoK IFRoaXMgdGV4dCBpcyBhbHNvIGluIFJGQyAyODY1IFNlY3Rpb24gMS4xLgoKIFRoZSB0ZXh0IG1h eSBub3QgYmUgc3RyaWN0bHkgbmVjZXNzYXJ5LiAgSSdtIG9wZW4gdG8gZmVlZGJhY2suCgotLSAK LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgIHwgICAgICAgT3du ZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8 ICBleHRlbnNpb25zQOKApgogUHJpb3JpdHk6ICBtYWpvciAgICAgICAgfCAgICAgIFN0YXR1czog IG5ldwpDb21wb25lbnQ6ICByYWRpdXMtICAgICAgfCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEK ICBleHRlbnNpb25zICAgICAgICAgICAgIHwgICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAg SW4gV0cgTGFzdCAgIHwgIFJlc29sdXRpb246CiAgQ2FsbCAgICAgICAgICAgICAgICAgICB8CiBL ZXl3b3JkczogICAgICAgICAgICAgICB8Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDog PGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMTkjY29t bWVudDoxPgpyYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlz dApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9y YWRleHQK From radext-bounces@ietf.org Wed May 23 07:03:48 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F35821F86F7; Wed, 23 May 2012 07:03:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781828; bh=cMMShH4Jc6XS9r0mNSHEm7W5d+iIRlqK/gX1xSacGY4=; h=MIME-Version:Date:Message-ID:In-Reply-To:References:From:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=Tui76gC1LS0CfYooLqJz0MGN3DrF3JyQPyeOATLURkzqSYyf+BLtPTGTACDtNGLCA SekdTslCasQHrPRv0UXFWjPBfp8rg3Xbqcm5c2HtGhcZfcvFTtOVkwnF1r0aa6LdUE 4rd1uE4ZdC32Erv0L8pvzwPqIP+T/ud4Ao3u4/uk= 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 885B921F86F7 for ; Wed, 23 May 2012 07:03:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.499 X-Spam-Level: X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 f3Bk3M0bsCst for ; Wed, 23 May 2012 07:03:47 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id BB51A21F86C5 for ; Wed, 23 May 2012 07:03:46 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFAFTtvE/GmAcF/2dsb2JhbABDhS+tc4ERgQeCFQEBAQEDAQEBDxENBDoXBAIBCA0EBAEBAwIGBgwLAQICAgEBJR8JCAEBBAESCBqHbAudOYockm2BJolpJIQIMmIDliuEYoUJhHaCbA X-IronPort-AV: E=Sophos;i="4.75,645,1330923600"; d="scan'208";a="307777149" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 May 2012 10:02:00 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 May 2012 10:01:40 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 23 May 2012 16:03:41 +0200 Message-ID: In-Reply-To: <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] #119: 'levels of compliance'? Thread-Index: Ac047J1UVQV1RlfnQ6iL3Vzzm5onNgAABTsA References: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> From: "Romascanu, Dan (Dan)" To: , , Subject: Re: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org SSBtaXNzZWQgdGhhdC4gQXJlIHBlb3BsZSByZWFsbHkgdXNpbmcgaXQ/IElmIHllcywgSSB3b3Vs ZCBpbmRpY2F0ZSB0aGUgb3JpZ2luLCBpdCBzdWRkZW5seSBzdHJpa2VzIG1lIHRoYXQgUkFESVVT IGhhcyB0aGlzIGNvbmNlcHQgd2hpY2ggSSBkbyBub3QgcmVtZW1iZXIgaGF2aW5nIGJlZW4gYWRv cHRlZCBieSBvdGhlciBJRVRGIHN0YW5kYXJkcy4gDQoNClJlZ2FyZHMsDQoNCkRhbg0KDQoNCg0K DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHJhZGV4dC1ib3VuY2VzQGll dGYub3JnIFttYWlsdG86cmFkZXh0LWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+IEJlaGFsZiBPZiBy YWRleHQgaXNzdWUgdHJhY2tlcg0KPiBTZW50OiBXZWRuZXNkYXksIE1heSAyMywgMjAxMiA1OjAy IFBNDQo+IFRvOiBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtZXh0ZW5zaW9uc0B0b29scy5pZXRm Lm9yZzsNCj4gYWxhbmRAZGVwbG95aW5ncmFkaXVzLmNvbQ0KPiBDYzogcmFkZXh0QGlldGYub3Jn DQo+IFN1YmplY3Q6IFJlOiBbcmFkZXh0XSAjMTE5OiAnbGV2ZWxzIG9mIGNvbXBsaWFuY2UnPw0K PiANCj4gIzExOTogJ2xldmVscyBvZiBjb21wbGlhbmNlJz8NCj4gDQo+IA0KPiBDb21tZW50IChi eSBhbGFuZEDigKYpOg0KPiANCj4gIFRoaXMgdGV4dCBpcyBhbHNvIGluIFJGQyAyODY1IFNlY3Rp b24gMS4xLg0KPiANCj4gIFRoZSB0ZXh0IG1heSBub3QgYmUgc3RyaWN0bHkgbmVjZXNzYXJ5LiAg SSdtIG9wZW4gdG8gZmVlZGJhY2suDQo+IA0KPiAtLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiAtLS0t DQo+ICBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgIHwgICAgICAgT3duZXI6ICBkcmFmdC1pZXRm LXJhZGV4dC1yYWRpdXMtDQo+ICAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRlbnNpb25z QOKApg0KPiAgUHJpb3JpdHk6ICBtYWpvciAgICAgICAgfCAgICAgIFN0YXR1czogIG5ldw0KPiBD b21wb25lbnQ6ICByYWRpdXMtICAgICAgfCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTENCj4gICBl eHRlbnNpb25zICAgICAgICAgICAgIHwgICAgIFZlcnNpb246ICAxLjANCj4gIFNldmVyaXR5OiAg SW4gV0cgTGFzdCAgIHwgIFJlc29sdXRpb246DQo+ICAgQ2FsbCAgICAgICAgICAgICAgICAgICB8 DQo+ICBLZXl3b3JkczogICAgICAgICAgICAgICB8DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0tLS0N Cj4gDQo+IFRpY2tldCBVUkw6DQo+IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRl eHQvdHJhYy90aWNrZXQvMTE5I2NvbW1lbnQ6MT4NCj4gcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0 Zi5vcmcvcmFkZXh0Lz4NCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fDQo+IHJhZGV4dCBtYWlsaW5nIGxpc3QNCj4gcmFkZXh0QGlldGYub3JnDQo+ IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmFkZXh0DQpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0 CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Jh ZGV4dAo= From dromasca@avaya.com Wed May 23 07:03:47 2012 Return-Path: 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 885B921F86F7 for ; Wed, 23 May 2012 07:03:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.499 X-Spam-Level: X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 f3Bk3M0bsCst for ; Wed, 23 May 2012 07:03:47 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id BB51A21F86C5 for ; Wed, 23 May 2012 07:03:46 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFAFTtvE/GmAcF/2dsb2JhbABDhS+tc4ERgQeCFQEBAQEDAQEBDxENBDoXBAIBCA0EBAEBAwIGBgwLAQICAgEBJR8JCAEBBAESCBqHbAudOYockm2BJolpJIQIMmIDliuEYoUJhHaCbA X-IronPort-AV: E=Sophos;i="4.75,645,1330923600"; d="scan'208";a="307777149" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 May 2012 10:02:00 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 May 2012 10:01:40 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Date: Wed, 23 May 2012 16:03:41 +0200 Message-ID: In-Reply-To: <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] #119: 'levels of compliance'? Thread-Index: Ac047J1UVQV1RlfnQ6iL3Vzzm5onNgAABTsA References: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> From: "Romascanu, Dan (Dan)" To: , , Subject: Re: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:03:47 -0000 SSBtaXNzZWQgdGhhdC4gQXJlIHBlb3BsZSByZWFsbHkgdXNpbmcgaXQ/IElmIHllcywgSSB3b3Vs ZCBpbmRpY2F0ZSB0aGUgb3JpZ2luLCBpdCBzdWRkZW5seSBzdHJpa2VzIG1lIHRoYXQgUkFESVVT IGhhcyB0aGlzIGNvbmNlcHQgd2hpY2ggSSBkbyBub3QgcmVtZW1iZXIgaGF2aW5nIGJlZW4gYWRv cHRlZCBieSBvdGhlciBJRVRGIHN0YW5kYXJkcy4gDQoNClJlZ2FyZHMsDQoNCkRhbg0KDQoNCg0K DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHJhZGV4dC1ib3VuY2VzQGll dGYub3JnIFttYWlsdG86cmFkZXh0LWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+IEJlaGFsZiBPZiBy YWRleHQgaXNzdWUgdHJhY2tlcg0KPiBTZW50OiBXZWRuZXNkYXksIE1heSAyMywgMjAxMiA1OjAy IFBNDQo+IFRvOiBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtZXh0ZW5zaW9uc0B0b29scy5pZXRm Lm9yZzsNCj4gYWxhbmRAZGVwbG95aW5ncmFkaXVzLmNvbQ0KPiBDYzogcmFkZXh0QGlldGYub3Jn DQo+IFN1YmplY3Q6IFJlOiBbcmFkZXh0XSAjMTE5OiAnbGV2ZWxzIG9mIGNvbXBsaWFuY2UnPw0K PiANCj4gIzExOTogJ2xldmVscyBvZiBjb21wbGlhbmNlJz8NCj4gDQo+IA0KPiBDb21tZW50IChi eSBhbGFuZEDigKYpOg0KPiANCj4gIFRoaXMgdGV4dCBpcyBhbHNvIGluIFJGQyAyODY1IFNlY3Rp b24gMS4xLg0KPiANCj4gIFRoZSB0ZXh0IG1heSBub3QgYmUgc3RyaWN0bHkgbmVjZXNzYXJ5LiAg SSdtIG9wZW4gdG8gZmVlZGJhY2suDQo+IA0KPiAtLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiAtLS0t DQo+ICBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgIHwgICAgICAgT3duZXI6ICBkcmFmdC1pZXRm LXJhZGV4dC1yYWRpdXMtDQo+ICAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRlbnNpb25z QOKApg0KPiAgUHJpb3JpdHk6ICBtYWpvciAgICAgICAgfCAgICAgIFN0YXR1czogIG5ldw0KPiBD b21wb25lbnQ6ICByYWRpdXMtICAgICAgfCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTENCj4gICBl eHRlbnNpb25zICAgICAgICAgICAgIHwgICAgIFZlcnNpb246ICAxLjANCj4gIFNldmVyaXR5OiAg SW4gV0cgTGFzdCAgIHwgIFJlc29sdXRpb246DQo+ICAgQ2FsbCAgICAgICAgICAgICAgICAgICB8 DQo+ICBLZXl3b3JkczogICAgICAgICAgICAgICB8DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0tLS0N Cj4gDQo+IFRpY2tldCBVUkw6DQo+IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRl eHQvdHJhYy90aWNrZXQvMTE5I2NvbW1lbnQ6MT4NCj4gcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0 Zi5vcmcvcmFkZXh0Lz4NCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fDQo+IHJhZGV4dCBtYWlsaW5nIGxpc3QNCj4gcmFkZXh0QGlldGYub3JnDQo+ IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmFkZXh0DQo= From radext-bounces@ietf.org Wed May 23 07:05:49 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32CC521F8603; Wed, 23 May 2012 07:05:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337781949; bh=jF+rf+nYGNz2VT7Es6lgbFrfrZ/LUgME3FNmKHx/Uow=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=hslVIDzvlCnEhu9AFZyzNhSytFKKfhMiebJ0iZTLEt6/rnfVtEFPKXRDXZr+YnydZ OZ/L+7XaCxgAVWf2DtoV/LiR/NqmOwhZ6hgROuc/6AzE1O5Ynp6q3CFUtPO/V4JRtr J9KvQ1j4tKerDBhq8b7bTpn0ZjTU5iqGKFXgVcq0= 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 45E9A21F8603 for ; Wed, 23 May 2012 07:05:48 -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=[AWL=0.000, 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 7NFMBbepGyDc for ; Wed, 23 May 2012 07:05:47 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id C307B21F84D0 for ; Wed, 23 May 2012 07:05:47 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCC8-0007G9-UM; Wed, 23 May 2012 10:05:44 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:05:44 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/123 Message-ID: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> X-Trac-Ticket-ID: 123 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523140547.C307B21F84D0@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:05:47 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyMzogbmVzdGluZyBkZXB0aAoKIEluIFNlY3Rpb24gMi4zLjE6CgogPiBIb3dldmVyLCBuZXN0 aW5nIGRlcHRocyBvZiBtb3JlIHRoYW4gNCBhcmUgTk9UIFJFQ09NTUVOREVELgoKIFdoZXJlIGRv ZXMgdGhpcyBjb21lIGZyb20sIHdoeSA0IGFuZCBub3QgMyBvciA1PyBJIG1lYW4sIGlmIHRoaXMg aXMgZm9yCiBjbGFyaXR5IGFuZC9vciB0byBhdm9pZCBjb21wbGV4aXR5LCBidXQgaXQncyBtb3Jl IGxpa2UgYSBydWxlIG9mIHRodW1iLAogdGhhbiBtYXliZSBpdCBuZWVkcyBub3QgYmUgY2FwaXRh bGl6ZWQuCgotLSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAg IHwgICAgICBPd25lcjogIGRyYWZ0LWlldGYtcmFkZXh0LXJhZGl1cy0KICAgICBUeXBlOiAgZGVm ZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCmCiBQcmlvcml0eTogIG1ham9yICAgICAgICB8ICAg ICBTdGF0dXM6ICBuZXcKQ29tcG9uZW50OiAgcmFkaXVzLSAgICAgIHwgIE1pbGVzdG9uZTogIG1p bGVzdG9uZTEKICBleHRlbnNpb25zICAgICAgICAgICAgIHwgICAgVmVyc2lvbjogIDEuMAogU2V2 ZXJpdHk6ICBJbiBXRyBMYXN0ICAgfCAgIEtleXdvcmRzOgogIENhbGwgICAgICAgICAgICAgICAg ICAgfAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KClRpY2tldCBVUkw6IDxodHRwOi8vdHJhYy50b29scy5p ZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTIzPgpyYWRleHQgPGh0dHA6Ly90b29scy5p ZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cu aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Wed May 23 07:05:48 2012 Return-Path: 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 45E9A21F8603 for ; Wed, 23 May 2012 07:05:48 -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=[AWL=0.000, 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 7NFMBbepGyDc for ; Wed, 23 May 2012 07:05:47 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id C307B21F84D0 for ; Wed, 23 May 2012 07:05:47 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCC8-0007G9-UM; Wed, 23 May 2012 10:05:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:05:44 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/123 Message-ID: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> X-Trac-Ticket-ID: 123 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523140547.C307B21F84D0@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:05:47 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:05:48 -0000 #123: nesting depth In Section 2.3.1: > However, nesting depths of more than 4 are NOT RECOMMENDED. Where does this come from, why 4 and not 3 or 5? I mean, if this is for clarity and/or to avoid complexity, but it's more like a rule of thumb, than maybe it needs not be capitalized. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: major | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 07:10:06 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE71F21F854F; Wed, 23 May 2012 07:10:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337782206; bh=DDVr0XbDzZZmgm9oG3zNvfY1+5MOvpxk6mKMAa81a5c=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=aIEqEB3swwBShiDvFLqTWijYVOqmlfW4ADYid/fCmuBF25S6MESO1JpKCK7/dU933 Ii/trwgBCa7UBXTL4Km+y7K/cM8C7YcpnjDGBUM4gXXTq6qOsq16VhXE9uCMjAQSUv mXMvq9EdJscmtzv1/8tooKRtmzr6BxzOM8yuANd8= 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 C8E5B21F853F for ; Wed, 23 May 2012 07:10:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.351 X-Spam-Level: X-Spam-Status: No, score=-102.351 tagged_above=-999 required=5 tests=[AWL=0.248, 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 mOCnfgV92ytu for ; Wed, 23 May 2012 07:10:05 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE7B21F8518 for ; Wed, 23 May 2012 07:10:05 -0700 (PDT) Message-ID: <4FBCEFA2.6070901@deployingradius.com> Date: Wed, 23 May 2012 16:09:38 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Cc: radext@ietf.org, draft-ietf-radext-radius-extensions@tools.ietf.org Subject: Re: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Romascanu, Dan (Dan) wrote: > I missed that. Are people really using it? That's a hard question to answer. In practice, no one seems to care about RADIUS compliance. > If yes, I would indicate the origin, it suddenly strikes me that RADIUS has this concept which I do not remember having been adopted by other IETF standards. I'm OK with deleting the text. Alan DeKok. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From aland@deployingradius.com Wed May 23 07:10:05 2012 Return-Path: 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 C8E5B21F853F for ; Wed, 23 May 2012 07:10:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.351 X-Spam-Level: X-Spam-Status: No, score=-102.351 tagged_above=-999 required=5 tests=[AWL=0.248, 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 mOCnfgV92ytu for ; Wed, 23 May 2012 07:10:05 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE7B21F8518 for ; Wed, 23 May 2012 07:10:05 -0700 (PDT) Message-ID: <4FBCEFA2.6070901@deployingradius.com> Date: Wed, 23 May 2012 16:09:38 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: <059.a16879c6ad91fd9548e3a9582f98309f@trac.tools.ietf.org> <074.fc7e528c122fe687b93c49eb2df5615a@trac.tools.ietf.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: radext@ietf.org, draft-ietf-radext-radius-extensions@tools.ietf.org Subject: Re: [radext] #119: 'levels of compliance'? X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:10:05 -0000 Romascanu, Dan (Dan) wrote: > I missed that. Are people really using it? That's a hard question to answer. In practice, no one seems to care about RADIUS compliance. > If yes, I would indicate the origin, it suddenly strikes me that RADIUS has this concept which I do not remember having been adopted by other IETF standards. I'm OK with deleting the text. Alan DeKok. From trac+radext@trac.tools.ietf.org Wed May 23 07:13:10 2012 Return-Path: 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 9049421F8694 for ; Wed, 23 May 2012 07:13:10 -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 mU4xgVKJ457o for ; Wed, 23 May 2012 07:13:10 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 1998C21F854F for ; Wed, 23 May 2012 07:13:09 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCJE-0008G6-JB; Wed, 23 May 2012 10:13:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:13:04 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/123#comment:1 Message-ID: <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> References: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> X-Trac-Ticket-ID: 123 In-Reply-To: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523141310.1998C21F854F@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:13:09 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:13:10 -0000 #123: nesting depth Comment (by aland@…): The rule of thumb comes from a few areas. WiMAX / 3GPP has been using nested attributes. They haven't seen a need for depths of more than 4, IIRC. I can't think of many uses, either. Another is implementations. (sadly) Some implementations use 32-bit integers to refer to RADIUS attributes. Encouraging unlimited nesting would require large changes to those implementations. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: major | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 07:13:11 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD3221F8694; Wed, 23 May 2012 07:13:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337782391; bh=Z49ERTTdevjuP7kkcJ/ZUQSW8UgCDBnS+kgfynpq5Pc=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=Qe7xa9bAjkEwcjpRq5wBvPexgCMNg64T1OC3Rwh2SbMF2In7wPloFd5B7e1FgQo5V jCEOSKctqKI14otLYf1HdjKQh+zbCX4YMcKP1xp3CR7F3zPR7MgGTc2Fn+o/QTBjWH kdYGQGT85GXxNtQk7CvFn/CA+WMYQ2AqA8REe81c= 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 9049421F8694 for ; Wed, 23 May 2012 07:13:10 -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 mU4xgVKJ457o for ; Wed, 23 May 2012 07:13:10 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 1998C21F854F for ; Wed, 23 May 2012 07:13:09 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCJE-0008G6-JB; Wed, 23 May 2012 10:13:05 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:13:04 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/123#comment:1 Message-ID: <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> References: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> X-Trac-Ticket-ID: 123 In-Reply-To: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523141310.1998C21F854F@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:13:09 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyMzogbmVzdGluZyBkZXB0aAoKCkNvbW1lbnQgKGJ5IGFsYW5kQOKApik6CgogVGhlIHJ1bGUg b2YgdGh1bWIgY29tZXMgZnJvbSBhIGZldyBhcmVhcy4KCiBXaU1BWCAvIDNHUFAgaGFzIGJlZW4g dXNpbmcgbmVzdGVkIGF0dHJpYnV0ZXMuICBUaGV5IGhhdmVuJ3Qgc2VlbiBhIG5lZWQKIGZvciBk ZXB0aHMgb2YgbW9yZSB0aGFuIDQsIElJUkMuICBJIGNhbid0IHRoaW5rIG9mIG1hbnkgdXNlcywg ZWl0aGVyLgoKIEFub3RoZXIgaXMgaW1wbGVtZW50YXRpb25zLiAgKHNhZGx5KSAgU29tZSBpbXBs ZW1lbnRhdGlvbnMgdXNlIDMyLWJpdAogaW50ZWdlcnMgdG8gcmVmZXIgdG8gUkFESVVTIGF0dHJp YnV0ZXMuICBFbmNvdXJhZ2luZyB1bmxpbWl0ZWQgbmVzdGluZwogd291bGQgcmVxdWlyZSBsYXJn ZSBjaGFuZ2VzIHRvIHRob3NlIGltcGxlbWVudGF0aW9ucy4KCi0tIAotLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0KIFJlcG9ydGVyOiAgZHJvbWFzY2FA4oCmICAgfCAgICAgICBPd25lcjogIGRyYWZ0LWlldGYt cmFkZXh0LXJhZGl1cy0KICAgICBUeXBlOiAgZGVmZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCm CiBQcmlvcml0eTogIG1ham9yICAgICAgICB8ICAgICAgU3RhdHVzOiAgbmV3CkNvbXBvbmVudDog IHJhZGl1cy0gICAgICB8ICAgTWlsZXN0b25lOiAgbWlsZXN0b25lMQogIGV4dGVuc2lvbnMgICAg ICAgICAgICAgfCAgICAgVmVyc2lvbjogIDEuMAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0ICAgfCAg UmVzb2x1dGlvbjoKICBDYWxsICAgICAgICAgICAgICAgICAgIHwKIEtleXdvcmRzOiAgICAgICAg ICAgICAgIHwKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9v bHMuaWV0Zi5vcmcvd2cvcmFkZXh0L3RyYWMvdGlja2V0LzEyMyNjb21tZW50OjE+CnJhZGV4dCA8 aHR0cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+CgpfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9y ZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From radext-bounces@ietf.org Wed May 23 07:28:16 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1163921F86AA; Wed, 23 May 2012 07:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337783296; bh=TzpHKlEGHeLBS1lgMQwYW3rJdCI+Xiw3sWONqVXSl3U=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=nRq5tMQziMhxeaOsItHi/kR5keEaE4rrKHx82E5ah3Ogghqflo+umT4RTdHcz7elQ x32snKVqahmFZV+7kePdBOmuvY6Zwr+/RA0Wf2rIRb6Wy4eCTZ4F4VIyYLxqKjNK5J 5Xnx0vXEYBuhpj8mBDzWlLI67rJTtrBpte8ORPLE= 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 61ECA21F86AA for ; Wed, 23 May 2012 07:28:15 -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=[AWL=0.000, 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 SpUzDXHSlpiF for ; Wed, 23 May 2012 07:28:15 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id DCD5321F8648 for ; Wed, 23 May 2012 07:28:14 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCXl-0007KS-DV; Wed, 23 May 2012 10:28:05 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:28:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/124 Message-ID: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> X-Trac-Ticket-ID: 124 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523142814.DCD5321F8648@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:28:14 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #124: private enterprise numbers X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyNDogcHJpdmF0ZSBlbnRlcnByaXNlIG51bWJlcnMKCiBJbiBzZWN0aW9uIDIuNCwgd2hlbiBk ZWZpbmluZyBWZW5kb3ItSWQ6CgogPiBUaGUgaGlnaC1vcmRlciBvY3RldCBpcyAwIGFuZCB0aGUg bG93LW9yZGVyIDMgb2N0ZXRzIGFyZSB0aGUgU01JIE5ldHdvcmsKIE1hbmFnZW1lbnQgUHJpdmF0 ZSBFbnRlcnByaXNlIENvZGUgb2YgdGhlIFZlbmRvciBpbiBuZXR3b3JrIGJ5dGUgb3JkZXIuCgog VGhlcmUgc2VlbXMgdG8gYmUgYW4gYXNzdW1wdGlvbiBoZXJlIHRoYXQgUEVOcyBhcmUgbGltaXRl ZCB0byAzIG9jdGV0cyAtCiB0aGlzIGlzIG5vdCB0cnVlLiBBY3R1YWxseSBkaXNjdXNzaW9ucyBh cm91bmQgaHR0cDovL3d3dy5pZXRmLm9yZy9pZAogL2RyYWZ0LWxpYW5nLWlhbmEtcGVuLTAwLnR4 dCBxdWVzdGlvbiB3aGV0aGVyIDMyIGJpdHMgaXMgZW5vdWdoLiBJIHN1Z2dlc3QKIHRvIHVzZSBh bGwgNCBvY3RldHMuCgotLSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2Nh QOKApiAgIHwgICAgICBPd25lcjogIGRyYWZ0LWlldGYtcmFkZXh0LXJhZGl1cy0KICAgICBUeXBl OiAgZGVmZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCmCiBQcmlvcml0eTogIGJsb2NrZXIgICAg ICB8ICAgICBTdGF0dXM6ICBuZXcKQ29tcG9uZW50OiAgcmFkaXVzLSAgICAgIHwgIE1pbGVzdG9u ZTogIG1pbGVzdG9uZTEKICBleHRlbnNpb25zICAgICAgICAgICAgIHwgICAgVmVyc2lvbjogIDEu MAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0ICAgfCAgIEtleXdvcmRzOgogIENhbGwgICAgICAgICAg ICAgICAgICAgfAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KClRpY2tldCBVUkw6IDxodHRwOi8vdHJhYy50 b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTI0PgpyYWRleHQgPGh0dHA6Ly90 b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Wed May 23 07:28:15 2012 Return-Path: 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 61ECA21F86AA for ; Wed, 23 May 2012 07:28:15 -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=[AWL=0.000, 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 SpUzDXHSlpiF for ; Wed, 23 May 2012 07:28:15 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id DCD5321F8648 for ; Wed, 23 May 2012 07:28:14 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCXl-0007KS-DV; Wed, 23 May 2012 10:28:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:28:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/124 Message-ID: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> X-Trac-Ticket-ID: 124 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523142814.DCD5321F8648@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:28:14 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #124: private enterprise numbers X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:28:15 -0000 #124: private enterprise numbers In section 2.4, when defining Vendor-Id: > The high-order octet is 0 and the low-order 3 octets are the SMI Network Management Private Enterprise Code of the Vendor in network byte order. There seems to be an assumption here that PENs are limited to 3 octets - this is not true. Actually discussions around http://www.ietf.org/id /draft-liang-iana-pen-00.txt question whether 32 bits is enough. I suggest to use all 4 octets. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: blocker | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 07:30:32 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D48F21F86EB; Wed, 23 May 2012 07:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337783432; bh=B9Xt0/SCapx51jDoqtLZXqHoOGW0rubvHSD+cg6qgaE=; h=MIME-Version:Date:Message-ID:In-Reply-To:References:From:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=sBL802JlhaWTFBNPmttxp5ZvPWqOxUJkSsBcQ/urqViQ8FhzHbiAQOkZCdsm32/sR zpn3AHg5N2UzF6WzpSF+4GLCuEVCdt9Nln1sQG//44JSqIrfk5syK5zqCGQDgtZOG0 GuiYBc3EhUv0tVQpM8KrVXISLMNF6FQrnuNkNduU= 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 0571521F86F0 for ; Wed, 23 May 2012 07:30:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.01 X-Spam-Level: X-Spam-Status: No, score=-103.01 tagged_above=-999 required=5 tests=[AWL=-0.411, 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 PRFA07bccx5P for ; Wed, 23 May 2012 07:30:31 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5C13321F86EB for ; Wed, 23 May 2012 07:30:31 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFAD70vE+HCzI1/2dsb2JhbABEhS+tc4ESgQeCFQEBAQEDAQEBDxENBDoXBAIBCA0EBAEBAwIGBgwLAQICAgEBJR8JCAEBBAESCBqHbAudP4ockm2BJolpJIQIMmIDliuEYoUJhHaCbA X-IronPort-AV: E=Sophos;i="4.75,645,1330923600"; d="scan'208";a="10659765" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 23 May 2012 10:28:50 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 May 2012 10:12:44 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 23 May 2012 16:30:27 +0200 Message-ID: In-Reply-To: <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] #123: nesting depth Thread-Index: Ac047jJuz4WpR1A+TkWDB4UA+7WVDgAAjT/g References: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> From: "Romascanu, Dan (Dan)" To: , , Subject: Re: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org SSBhbSBub3QgaW4gZmF2b3Igb2YgZW5jb3VyYWdpbmcgdW5saW1pdGVkIG5lc3RpbmcuIEkgcXVl c3Rpb24gd2hldGhlciB1c2luZyBjYXBpdGFsaXphdGlvbiBpcyBhcHByb3ByaWF0ZSB3aGVuIHRo ZSBsaW1pdGF0aW9uIGRvZXMgbm90IHNlZW0gdG8gcmVzdWx0IGZyb20gcmVzdHJpY3Rpb24gaW4g dGhlIHByb3RvY29sLiANCg0KUmVnYXJkcywNCg0KRGFuDQoNCg0KDQoNCj4gLS0tLS1PcmlnaW5h bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogcmFkZXh0LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpy YWRleHQtYm91bmNlc0BpZXRmLm9yZ10gT24NCj4gQmVoYWxmIE9mIHJhZGV4dCBpc3N1ZSB0cmFj a2VyDQo+IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDIzLCAyMDEyIDU6MTMgUE0NCj4gVG86IGRyYWZ0 LWlldGYtcmFkZXh0LXJhZGl1cy1leHRlbnNpb25zQHRvb2xzLmlldGYub3JnOw0KPiBhbGFuZEBk ZXBsb3lpbmdyYWRpdXMuY29tDQo+IENjOiByYWRleHRAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6 IFtyYWRleHRdICMxMjM6IG5lc3RpbmcgZGVwdGgNCj4gDQo+ICMxMjM6IG5lc3RpbmcgZGVwdGgN Cj4gDQo+IA0KPiBDb21tZW50IChieSBhbGFuZEDigKYpOg0KPiANCj4gIFRoZSBydWxlIG9mIHRo dW1iIGNvbWVzIGZyb20gYSBmZXcgYXJlYXMuDQo+IA0KPiAgV2lNQVggLyAzR1BQIGhhcyBiZWVu IHVzaW5nIG5lc3RlZCBhdHRyaWJ1dGVzLiAgVGhleSBoYXZlbid0IHNlZW4gYQ0KPiBuZWVkDQo+ ICBmb3IgZGVwdGhzIG9mIG1vcmUgdGhhbiA0LCBJSVJDLiAgSSBjYW4ndCB0aGluayBvZiBtYW55 IHVzZXMsIGVpdGhlci4NCj4gDQo+ICBBbm90aGVyIGlzIGltcGxlbWVudGF0aW9ucy4gIChzYWRs eSkgIFNvbWUgaW1wbGVtZW50YXRpb25zIHVzZSAzMi1iaXQNCj4gIGludGVnZXJzIHRvIHJlZmVy IHRvIFJBRElVUyBhdHRyaWJ1dGVzLiAgRW5jb3VyYWdpbmcgdW5saW1pdGVkIG5lc3RpbmcNCj4g IHdvdWxkIHJlcXVpcmUgbGFyZ2UgY2hhbmdlcyB0byB0aG9zZSBpbXBsZW1lbnRhdGlvbnMuDQo+ IA0KPiAtLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiAtLS0tDQo+ICBSZXBvcnRlcjogIGRyb21hc2Nh QOKApiAgIHwgICAgICAgT3duZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtDQo+ICAgICAg VHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRlbnNpb25zQOKApg0KPiAgUHJpb3JpdHk6ICBtYWpv ciAgICAgICAgfCAgICAgIFN0YXR1czogIG5ldw0KPiBDb21wb25lbnQ6ICByYWRpdXMtICAgICAg fCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTENCj4gICBleHRlbnNpb25zICAgICAgICAgICAgIHwg ICAgIFZlcnNpb246ICAxLjANCj4gIFNldmVyaXR5OiAgSW4gV0cgTGFzdCAgIHwgIFJlc29sdXRp b246DQo+ICAgQ2FsbCAgICAgICAgICAgICAgICAgICB8DQo+ICBLZXl3b3JkczogICAgICAgICAg ICAgICB8DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0tLS0NCj4gDQo+IFRpY2tldCBVUkw6DQo+IDxo dHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTIzI2NvbW1l bnQ6MT4NCj4gcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0Lz4NCj4gDQo+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IHJhZGV4dCBt YWlsaW5nIGxpc3QNCj4gcmFkZXh0QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h aWxtYW4vbGlzdGluZm8vcmFkZXh0DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpyYWRleHQgbWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4dAo= From dromasca@avaya.com Wed May 23 07:30:32 2012 Return-Path: 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 0571521F86F0 for ; Wed, 23 May 2012 07:30:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.01 X-Spam-Level: X-Spam-Status: No, score=-103.01 tagged_above=-999 required=5 tests=[AWL=-0.411, 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 PRFA07bccx5P for ; Wed, 23 May 2012 07:30:31 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5C13321F86EB for ; Wed, 23 May 2012 07:30:31 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFAD70vE+HCzI1/2dsb2JhbABEhS+tc4ESgQeCFQEBAQEDAQEBDxENBDoXBAIBCA0EBAEBAwIGBgwLAQICAgEBJR8JCAEBBAESCBqHbAudP4ockm2BJolpJIQIMmIDliuEYoUJhHaCbA X-IronPort-AV: E=Sophos;i="4.75,645,1330923600"; d="scan'208";a="10659765" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 23 May 2012 10:28:50 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 May 2012 10:12:44 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Date: Wed, 23 May 2012 16:30:27 +0200 Message-ID: In-Reply-To: <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] #123: nesting depth Thread-Index: Ac047jJuz4WpR1A+TkWDB4UA+7WVDgAAjT/g References: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> From: "Romascanu, Dan (Dan)" To: , , Subject: Re: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:30:32 -0000 SSBhbSBub3QgaW4gZmF2b3Igb2YgZW5jb3VyYWdpbmcgdW5saW1pdGVkIG5lc3RpbmcuIEkgcXVl c3Rpb24gd2hldGhlciB1c2luZyBjYXBpdGFsaXphdGlvbiBpcyBhcHByb3ByaWF0ZSB3aGVuIHRo ZSBsaW1pdGF0aW9uIGRvZXMgbm90IHNlZW0gdG8gcmVzdWx0IGZyb20gcmVzdHJpY3Rpb24gaW4g dGhlIHByb3RvY29sLiANCg0KUmVnYXJkcywNCg0KRGFuDQoNCg0KDQoNCj4gLS0tLS1PcmlnaW5h bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogcmFkZXh0LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpy YWRleHQtYm91bmNlc0BpZXRmLm9yZ10gT24NCj4gQmVoYWxmIE9mIHJhZGV4dCBpc3N1ZSB0cmFj a2VyDQo+IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDIzLCAyMDEyIDU6MTMgUE0NCj4gVG86IGRyYWZ0 LWlldGYtcmFkZXh0LXJhZGl1cy1leHRlbnNpb25zQHRvb2xzLmlldGYub3JnOw0KPiBhbGFuZEBk ZXBsb3lpbmdyYWRpdXMuY29tDQo+IENjOiByYWRleHRAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6 IFtyYWRleHRdICMxMjM6IG5lc3RpbmcgZGVwdGgNCj4gDQo+ICMxMjM6IG5lc3RpbmcgZGVwdGgN Cj4gDQo+IA0KPiBDb21tZW50IChieSBhbGFuZEDigKYpOg0KPiANCj4gIFRoZSBydWxlIG9mIHRo dW1iIGNvbWVzIGZyb20gYSBmZXcgYXJlYXMuDQo+IA0KPiAgV2lNQVggLyAzR1BQIGhhcyBiZWVu IHVzaW5nIG5lc3RlZCBhdHRyaWJ1dGVzLiAgVGhleSBoYXZlbid0IHNlZW4gYQ0KPiBuZWVkDQo+ ICBmb3IgZGVwdGhzIG9mIG1vcmUgdGhhbiA0LCBJSVJDLiAgSSBjYW4ndCB0aGluayBvZiBtYW55 IHVzZXMsIGVpdGhlci4NCj4gDQo+ICBBbm90aGVyIGlzIGltcGxlbWVudGF0aW9ucy4gIChzYWRs eSkgIFNvbWUgaW1wbGVtZW50YXRpb25zIHVzZSAzMi1iaXQNCj4gIGludGVnZXJzIHRvIHJlZmVy IHRvIFJBRElVUyBhdHRyaWJ1dGVzLiAgRW5jb3VyYWdpbmcgdW5saW1pdGVkIG5lc3RpbmcNCj4g IHdvdWxkIHJlcXVpcmUgbGFyZ2UgY2hhbmdlcyB0byB0aG9zZSBpbXBsZW1lbnRhdGlvbnMuDQo+ IA0KPiAtLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiAtLS0tDQo+ICBSZXBvcnRlcjogIGRyb21hc2Nh QOKApiAgIHwgICAgICAgT3duZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtDQo+ICAgICAg VHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRlbnNpb25zQOKApg0KPiAgUHJpb3JpdHk6ICBtYWpv ciAgICAgICAgfCAgICAgIFN0YXR1czogIG5ldw0KPiBDb21wb25lbnQ6ICByYWRpdXMtICAgICAg fCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTENCj4gICBleHRlbnNpb25zICAgICAgICAgICAgIHwg ICAgIFZlcnNpb246ICAxLjANCj4gIFNldmVyaXR5OiAgSW4gV0cgTGFzdCAgIHwgIFJlc29sdXRp b246DQo+ICAgQ2FsbCAgICAgICAgICAgICAgICAgICB8DQo+ICBLZXl3b3JkczogICAgICAgICAg ICAgICB8DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0tLS0NCj4gDQo+IFRpY2tldCBVUkw6DQo+IDxo dHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNrZXQvMTIzI2NvbW1l bnQ6MT4NCj4gcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0Lz4NCj4gDQo+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IHJhZGV4dCBt YWlsaW5nIGxpc3QNCj4gcmFkZXh0QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h aWxtYW4vbGlzdGluZm8vcmFkZXh0DQo= From radext-bounces@ietf.org Wed May 23 07:40:07 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB7E21F8550; Wed, 23 May 2012 07:40:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337784007; bh=e4iiA71Df6Bnp6um4LiMDS7/FCWWgDBvGWLTsYghJOU=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=h8DJ+UucDaXZe/IOve+1Y9Xa/wAU3UyfdbeGoMDTg6Px+BzZ9armoTZrF4PXJwub7 vKpX0O9jknhsF722upD/n6RWLIeBaQuf5Z1O33zRUPOdCqR52Rl8iLmnY2tt3gDPBM IZAsvW2g4NQSugMcXK20IJYkSnGsUYmIb+3OxzBE= 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 D7B5F21F853C for ; Wed, 23 May 2012 07:40:04 -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 ScIywbCdYoRZ for ; Wed, 23 May 2012 07:40:04 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id BC0D821F8501 for ; Wed, 23 May 2012 07:39:59 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCjC-0005SD-BQ; Wed, 23 May 2012 10:39:54 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:39:54 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/124#comment:1 Message-ID: <074.ba81bddb8f76876e38778bc50c01edcc@trac.tools.ietf.org> References: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> X-Trac-Ticket-ID: 124 In-Reply-To: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523143959.BC0D821F8501@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:39:59 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #124: private enterprise numbers X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyNDogcHJpdmF0ZSBlbnRlcnByaXNlIG51bWJlcnMKCgpDb21tZW50IChieSBhbGFuZEDigKYp OgoKIEkgc3VnZ2VzdCBjaGFuZ2luZyB0aGlzIHRleHQgdG86CgogLS0tCiBUaGUgNCBvY3RldHMg YXJlIHRoZSBTTUkgTmV0d29yayBNYW5hZ2VtZW50IFByaXZhdGUgRW50ZXJwcmlzZSBDb2RlIG9m CiB0aGUgVmVuZG9yIGluIG5ldHdvcmsgYnl0ZSBvcmRlci4KCiBOb3RlIHRoYXQgdGhpcyBpcyBh IGNoYW5nZSBmcm9tIFtSRkMyODY1XSwgd2hlcmUgdGhlIFZlbmRvci1JZCBpcwogZXhwbGljaXRs eSAzIG9jdGV0cy4KIC0tLQoKIGZpeGluZyBSRkMgMjg2NSBpcyBhbm90aGVyIGlzc3VlIGVudGly ZWx5LgoKLS0gCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICB8 ICAgICAgIE93bmVyOiAgZHJhZnQtaWV0Zi1yYWRleHQtcmFkaXVzLQogICAgIFR5cGU6ICBkZWZl Y3QgICAgICAgfCAgZXh0ZW5zaW9uc0DigKYKIFByaW9yaXR5OiAgYmxvY2tlciAgICAgIHwgICAg ICBTdGF0dXM6ICBuZXcKQ29tcG9uZW50OiAgcmFkaXVzLSAgICAgIHwgICBNaWxlc3RvbmU6ICBt aWxlc3RvbmUxCiAgZXh0ZW5zaW9ucyAgICAgICAgICAgICB8ICAgICBWZXJzaW9uOiAgMS4wCiBT ZXZlcml0eTogIEluIFdHIExhc3QgICB8ICBSZXNvbHV0aW9uOgogIENhbGwgICAgICAgICAgICAg ICAgICAgfAogS2V5d29yZHM6ICAgICAgICAgICAgICAgfAotLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KClRp Y2tldCBVUkw6IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90aWNr ZXQvMTI0I2NvbW1lbnQ6MT4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0Lz4K Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4dCBt YWlsaW5nIGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v bGlzdGluZm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Wed May 23 07:40:04 2012 Return-Path: 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 D7B5F21F853C for ; Wed, 23 May 2012 07:40:04 -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 ScIywbCdYoRZ for ; Wed, 23 May 2012 07:40:04 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id BC0D821F8501 for ; Wed, 23 May 2012 07:39:59 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXCjC-0005SD-BQ; Wed, 23 May 2012 10:39:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 14:39:54 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/124#comment:1 Message-ID: <074.ba81bddb8f76876e38778bc50c01edcc@trac.tools.ietf.org> References: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> X-Trac-Ticket-ID: 124 In-Reply-To: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523143959.BC0D821F8501@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 07:39:59 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #124: private enterprise numbers X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:40:05 -0000 #124: private enterprise numbers Comment (by aland@…): I suggest changing this text to: --- The 4 octets are the SMI Network Management Private Enterprise Code of the Vendor in network byte order. Note that this is a change from [RFC2865], where the Vendor-Id is explicitly 3 octets. --- fixing RFC 2865 is another issue entirely. -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: blocker | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From aland@deployingradius.com Wed May 23 07:41:50 2012 Return-Path: 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 42BA421F86EF for ; Wed, 23 May 2012 07:41:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.413 X-Spam-Level: X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 uwU5YSsQe-6V for ; Wed, 23 May 2012 07:41:49 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC5121F8550 for ; Wed, 23 May 2012 07:41:49 -0700 (PDT) Message-ID: <4FBCF712.3000508@deployingradius.com> Date: Wed, 23 May 2012 16:41:22 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: radext@ietf.org, draft-ietf-radext-radius-extensions@tools.ietf.org Subject: Re: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:41:50 -0000 Romascanu, Dan (Dan) wrote: > I am not in favor of encouraging unlimited nesting. I question whether using capitalization is appropriate when the limitation does not seem to result from restriction in the protocol. I'm open to changes. The text came about as a result of discussion on the WG list. Alan DeKok. From radext-bounces@ietf.org Wed May 23 07:41:51 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5A321F86EF; Wed, 23 May 2012 07:41:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337784111; bh=qcs4EtoEptI6mntO769a8Gjw0+pc9WM9cyZ7QrHGN00=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=YlOoXuGclXoA8dchrQMzKVV2DqE7RcOZQtmGIKqLgSPz0HdxdT4HPfXHTDuI8Jb4y vzBmDrCVQPMV5scVhyNQ/f1YULSbQ5emJ8fu7FhRsM0DlwazQ+xGpT1XR3eBt+Qdbr GOsf/DXxSLqHSq7YdIwZT2W3POoJTuI2wEl4DZmw= 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 42BA421F86EF for ; Wed, 23 May 2012 07:41:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.413 X-Spam-Level: X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 uwU5YSsQe-6V for ; Wed, 23 May 2012 07:41:49 -0700 (PDT) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC5121F8550 for ; Wed, 23 May 2012 07:41:49 -0700 (PDT) Message-ID: <4FBCF712.3000508@deployingradius.com> Date: Wed, 23 May 2012 16:41:22 +0200 From: Alan DeKok User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: <059.9b00f112d4278a53c8e970042ae43c6b@trac.tools.ietf.org> <074.847317b3e72013ef6e1f4329d8c78fd3@trac.tools.ietf.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Cc: radext@ietf.org, draft-ietf-radext-radius-extensions@tools.ietf.org Subject: Re: [radext] #123: nesting depth X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org Romascanu, Dan (Dan) wrote: > I am not in favor of encouraging unlimited nesting. I question whether using capitalization is appropriate when the limitation does not seem to result from restriction in the protocol. I'm open to changes. The text came about as a result of discussion on the WG list. Alan DeKok. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From dromasca@avaya.com Wed May 23 07:42:55 2012 Return-Path: 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 6050321F8760 for ; Wed, 23 May 2012 07:42:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.469 X-Spam-Level: X-Spam-Status: No, score=-103.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 NoX9tuTRRGPl for ; Wed, 23 May 2012 07:42:54 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDB621F8721 for ; Wed, 23 May 2012 07:42:53 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFAJz2vE+HCzI1/2dsb2JhbABEhS+tc4ESgQeCFQEBAQEDAQEBDxENBDoXBAIBCA0EBAEBAwIGBgwLAQICAgEBJR8JCAEBBAESCBqHbAudQoocknCBJolpJIQIMmIDliuEYoUJhHaCbA X-IronPort-AV: E=Sophos;i="4.75,645,1330923600"; d="scan'208";a="307786830" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 May 2012 10:41:07 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 May 2012 10:25:04 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Date: Wed, 23 May 2012 16:42:47 +0200 Message-ID: In-Reply-To: <074.ba81bddb8f76876e38778bc50c01edcc@trac.tools.ietf.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] #124: private enterprise numbers Thread-Index: Ac048fxcf6QV3miFTkuB/lrJX0F3/QAABhDw References: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> <074.ba81bddb8f76876e38778bc50c01edcc@trac.tools.ietf.org> From: "Romascanu, Dan (Dan)" To: , , Subject: Re: [radext] #124: private enterprise numbers X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 14:42:55 -0000 SW5kZWVkLCB0aGUgc2l0dWF0aW9uIHdpdGggW1JGQzI4NjVdIGltcGxlbWVudGF0aW9ucyBWZW5k b3ItSWQgZmllbGQgd2hlbiBQRU5zIHdpbGwgZXhjZWVkIHZhbHVlcyB0aGF0IGNhbiBiZSBjb2Rl ZCB3aXRoIHRocmVlIG9jdGV0cyBuZWVkcyB0byBiZSBjb25zaWRlcmVkIHNlcGFyYXRlbHkuIA0K DQpEYW4NCg0KDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiByYWRl eHQtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnJhZGV4dC1ib3VuY2VzQGlldGYub3JnXSBPbg0K PiBCZWhhbGYgT2YgcmFkZXh0IGlzc3VlIHRyYWNrZXINCj4gU2VudDogV2VkbmVzZGF5LCBNYXkg MjMsIDIwMTIgNTo0MCBQTQ0KPiBUbzogZHJhZnQtaWV0Zi1yYWRleHQtcmFkaXVzLWV4dGVuc2lv bnNAdG9vbHMuaWV0Zi5vcmc7DQo+IGFsYW5kQGRlcGxveWluZ3JhZGl1cy5jb20NCj4gQ2M6IHJh ZGV4dEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3JhZGV4dF0gIzEyNDogcHJpdmF0ZSBlbnRl cnByaXNlIG51bWJlcnMNCj4gDQo+ICMxMjQ6IHByaXZhdGUgZW50ZXJwcmlzZSBudW1iZXJzDQo+ IA0KPiANCj4gQ29tbWVudCAoYnkgYWxhbmRA4oCmKToNCj4gDQo+ICBJIHN1Z2dlc3QgY2hhbmdp bmcgdGhpcyB0ZXh0IHRvOg0KPiANCj4gIC0tLQ0KPiAgVGhlIDQgb2N0ZXRzIGFyZSB0aGUgU01J IE5ldHdvcmsgTWFuYWdlbWVudCBQcml2YXRlIEVudGVycHJpc2UgQ29kZSBvZg0KPiAgdGhlIFZl bmRvciBpbiBuZXR3b3JrIGJ5dGUgb3JkZXIuDQo+IA0KPiAgTm90ZSB0aGF0IHRoaXMgaXMgYSBj aGFuZ2UgZnJvbSBbUkZDMjg2NV0sIHdoZXJlIHRoZSBWZW5kb3ItSWQgaXMNCj4gIGV4cGxpY2l0 bHkgMyBvY3RldHMuDQo+ICAtLS0NCj4gDQo+ICBmaXhpbmcgUkZDIDI4NjUgaXMgYW5vdGhlciBp c3N1ZSBlbnRpcmVseS4NCj4gDQo+IC0tDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0tLS0NCj4gIFJl cG9ydGVyOiAgZHJvbWFzY2FA4oCmICAgfCAgICAgICBPd25lcjogIGRyYWZ0LWlldGYtcmFkZXh0 LXJhZGl1cy0NCj4gICAgICBUeXBlOiAgZGVmZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCmDQo+ ICBQcmlvcml0eTogIGJsb2NrZXIgICAgICB8ICAgICAgU3RhdHVzOiAgbmV3DQo+IENvbXBvbmVu dDogIHJhZGl1cy0gICAgICB8ICAgTWlsZXN0b25lOiAgbWlsZXN0b25lMQ0KPiAgIGV4dGVuc2lv bnMgICAgICAgICAgICAgfCAgICAgVmVyc2lvbjogIDEuMA0KPiAgU2V2ZXJpdHk6ICBJbiBXRyBM YXN0ICAgfCAgUmVzb2x1dGlvbjoNCj4gICBDYWxsICAgICAgICAgICAgICAgICAgIHwNCj4gIEtl eXdvcmRzOiAgICAgICAgICAgICAgIHwNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gLS0tLQ0KPiANCj4g VGlja2V0IFVSTDoNCj4gPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFj L3RpY2tldC8xMjQjY29tbWVudDoxPg0KPiByYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9y YWRleHQvPg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18NCj4gcmFkZXh0IG1haWxpbmcgbGlzdA0KPiByYWRleHRAaWV0Zi5vcmcNCj4gaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQNCg== From radext-bounces@ietf.org Wed May 23 07:42:56 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D706121F8763; Wed, 23 May 2012 07:42:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337784176; bh=M5k9S4Yw/lJRHz/TSwI8Wiq5ptTdMRcI+HuIT/gMZWw=; h=MIME-Version:Date:Message-ID:In-Reply-To:References:From:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=vzcs+j7H78StqbvC8l43JDuXgguiGaC/cBzYoXPLsaISBv0/k8wu9BrFyAz7npKhU 0gkKtOSDHaXC4jmuRHzofceuAVbmJXIjd224Oyvt7HZRsB9lhvYB0W6T63LIN89x6J 4u4U6AXxDJzozhVEJb3teCblSZqL80RNQEiv9Luo= 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 6050321F8760 for ; Wed, 23 May 2012 07:42:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.469 X-Spam-Level: X-Spam-Status: No, score=-103.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 NoX9tuTRRGPl for ; Wed, 23 May 2012 07:42:54 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDB621F8721 for ; Wed, 23 May 2012 07:42:53 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFAJz2vE+HCzI1/2dsb2JhbABEhS+tc4ESgQeCFQEBAQEDAQEBDxENBDoXBAIBCA0EBAEBAwIGBgwLAQICAgEBJR8JCAEBBAESCBqHbAudQoocknCBJolpJIQIMmIDliuEYoUJhHaCbA X-IronPort-AV: E=Sophos;i="4.75,645,1330923600"; d="scan'208";a="307786830" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 May 2012 10:41:07 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 May 2012 10:25:04 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 23 May 2012 16:42:47 +0200 Message-ID: In-Reply-To: <074.ba81bddb8f76876e38778bc50c01edcc@trac.tools.ietf.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [radext] #124: private enterprise numbers Thread-Index: Ac048fxcf6QV3miFTkuB/lrJX0F3/QAABhDw References: <059.78c61f51f46a8117d134457d233fdafd@trac.tools.ietf.org> <074.ba81bddb8f76876e38778bc50c01edcc@trac.tools.ietf.org> From: "Romascanu, Dan (Dan)" To: , , Subject: Re: [radext] #124: private enterprise numbers X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org SW5kZWVkLCB0aGUgc2l0dWF0aW9uIHdpdGggW1JGQzI4NjVdIGltcGxlbWVudGF0aW9ucyBWZW5k b3ItSWQgZmllbGQgd2hlbiBQRU5zIHdpbGwgZXhjZWVkIHZhbHVlcyB0aGF0IGNhbiBiZSBjb2Rl ZCB3aXRoIHRocmVlIG9jdGV0cyBuZWVkcyB0byBiZSBjb25zaWRlcmVkIHNlcGFyYXRlbHkuIA0K DQpEYW4NCg0KDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiByYWRl eHQtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnJhZGV4dC1ib3VuY2VzQGlldGYub3JnXSBPbg0K PiBCZWhhbGYgT2YgcmFkZXh0IGlzc3VlIHRyYWNrZXINCj4gU2VudDogV2VkbmVzZGF5LCBNYXkg MjMsIDIwMTIgNTo0MCBQTQ0KPiBUbzogZHJhZnQtaWV0Zi1yYWRleHQtcmFkaXVzLWV4dGVuc2lv bnNAdG9vbHMuaWV0Zi5vcmc7DQo+IGFsYW5kQGRlcGxveWluZ3JhZGl1cy5jb20NCj4gQ2M6IHJh ZGV4dEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3JhZGV4dF0gIzEyNDogcHJpdmF0ZSBlbnRl cnByaXNlIG51bWJlcnMNCj4gDQo+ICMxMjQ6IHByaXZhdGUgZW50ZXJwcmlzZSBudW1iZXJzDQo+ IA0KPiANCj4gQ29tbWVudCAoYnkgYWxhbmRA4oCmKToNCj4gDQo+ICBJIHN1Z2dlc3QgY2hhbmdp bmcgdGhpcyB0ZXh0IHRvOg0KPiANCj4gIC0tLQ0KPiAgVGhlIDQgb2N0ZXRzIGFyZSB0aGUgU01J IE5ldHdvcmsgTWFuYWdlbWVudCBQcml2YXRlIEVudGVycHJpc2UgQ29kZSBvZg0KPiAgdGhlIFZl bmRvciBpbiBuZXR3b3JrIGJ5dGUgb3JkZXIuDQo+IA0KPiAgTm90ZSB0aGF0IHRoaXMgaXMgYSBj aGFuZ2UgZnJvbSBbUkZDMjg2NV0sIHdoZXJlIHRoZSBWZW5kb3ItSWQgaXMNCj4gIGV4cGxpY2l0 bHkgMyBvY3RldHMuDQo+ICAtLS0NCj4gDQo+ICBmaXhpbmcgUkZDIDI4NjUgaXMgYW5vdGhlciBp c3N1ZSBlbnRpcmVseS4NCj4gDQo+IC0tDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0tLS0NCj4gIFJl cG9ydGVyOiAgZHJvbWFzY2FA4oCmICAgfCAgICAgICBPd25lcjogIGRyYWZ0LWlldGYtcmFkZXh0 LXJhZGl1cy0NCj4gICAgICBUeXBlOiAgZGVmZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA4oCmDQo+ ICBQcmlvcml0eTogIGJsb2NrZXIgICAgICB8ICAgICAgU3RhdHVzOiAgbmV3DQo+IENvbXBvbmVu dDogIHJhZGl1cy0gICAgICB8ICAgTWlsZXN0b25lOiAgbWlsZXN0b25lMQ0KPiAgIGV4dGVuc2lv bnMgICAgICAgICAgICAgfCAgICAgVmVyc2lvbjogIDEuMA0KPiAgU2V2ZXJpdHk6ICBJbiBXRyBM YXN0ICAgfCAgUmVzb2x1dGlvbjoNCj4gICBDYWxsICAgICAgICAgICAgICAgICAgIHwNCj4gIEtl eXdvcmRzOiAgICAgICAgICAgICAgIHwNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gLS0tLQ0KPiANCj4g VGlja2V0IFVSTDoNCj4gPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90cmFj L3RpY2tldC8xMjQjY29tbWVudDoxPg0KPiByYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9y YWRleHQvPg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18NCj4gcmFkZXh0IG1haWxpbmcgbGlzdA0KPiByYWRleHRAaWV0Zi5vcmcNCj4gaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQNCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4dCBtYWlsaW5nIGxpc3QKcmFkZXh0 QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmFkZXh0Cg== From radext-bounces@ietf.org Wed May 23 08:11:23 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352CF21F873A; Wed, 23 May 2012 08:11:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337785883; bh=gkDrGNKwvx6bh1Tg7dhwXON82p5QzorSo/3ZOCz/fdQ=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=eAx2zIdoZX2wP8U0fm382S7NrxsY6xYVkYyQP9JyJhMLxVFXsnod6+tQ7yVoIJsPf 1BaQLA2zjQX+06u4HAvH/2m82ix77nNf1c6VLpx0VMlJs2MHIsYsVcyHrB48zQyMFs CJSELQFWtH1vKFY3EnP+rj5s3SuolWlcBWssWfWQ= 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 2299E21F873A for ; Wed, 23 May 2012 08:11:21 -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=[AWL=0.000, 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 46U0khFMbL3o for ; Wed, 23 May 2012 08:11:16 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 6865421F8726 for ; Wed, 23 May 2012 08:11:16 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDDO-0001Sa-Kv; Wed, 23 May 2012 11:11:06 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:11:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/125 Message-ID: <059.373194f26e7133987c321922c27b4edb@trac.tools.ietf.org> X-Trac-Ticket-ID: 125 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523151116.6865421F8726@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 08:11:16 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #125: vendor-ID fields X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyNTogdmVuZG9yLUlEIGZpZWxkcwoKIEFsbCB2ZW5kb3ItSUQgZmllbGRzIGluIHRoZSBFeHRl bmRlZC1WZW5kb3ItU3BlY2lmaWMgYXR0cmlidXRlcyBhcmUKIGRlZmluZWQgMyBvY3RldHMuIEkg dW5kZXJzdGFuZCB0aGF0IHRoaXMgbGltaXRhdGlvbiBpcyBjb25zaXN0ZW50IHdpdGggdGhlCiB3 YXkgUkZDIDI4NjUgZGVmaW5lcyBWZW5kb3ItSUQgYnV0IHRoaXMgd2lsbCBjcmVhdGUgcHJvYmxl bXMgd2hlbiB0aGUKIDIqKjI0IG1hcmsgaXMgaGl0LiBJIHNlZSBubyByZWFzb24gbm90IHRvIHVz ZSBhbGwgdGhlIDQgb2N0ZXRzICh3aGljaCBhcmUKIGFueXdheSBkZWZpbmVkKQoKLS0gCi0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICB8ICAgICAgT3duZXI6ICBk cmFmdC1pZXRmLXJhZGV4dC1yYWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRl bnNpb25zQOKApgogUHJpb3JpdHk6ICBjcml0aWNhbCAgICAgfCAgICAgU3RhdHVzOiAgbmV3CkNv bXBvbmVudDogIHJhZGl1cy0gICAgICB8ICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCiAgZXh0ZW5z aW9ucyAgICAgICAgICAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAgSW4gV0cgTGFz dCAgIHwgICBLZXl3b3JkczoKICBDYWxsICAgICAgICAgICAgICAgICAgIHwKLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tCgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFkZXh0 L3RyYWMvdGlja2V0LzEyNT4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0Lz4K Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4dCBt YWlsaW5nIGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v bGlzdGluZm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Wed May 23 08:11:21 2012 Return-Path: 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 2299E21F873A for ; Wed, 23 May 2012 08:11:21 -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=[AWL=0.000, 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 46U0khFMbL3o for ; Wed, 23 May 2012 08:11:16 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 6865421F8726 for ; Wed, 23 May 2012 08:11:16 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDDO-0001Sa-Kv; Wed, 23 May 2012 11:11:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:11:05 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/125 Message-ID: <059.373194f26e7133987c321922c27b4edb@trac.tools.ietf.org> X-Trac-Ticket-ID: 125 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523151116.6865421F8726@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 08:11:16 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #125: vendor-ID fields X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 15:11:21 -0000 #125: vendor-ID fields All vendor-ID fields in the Extended-Vendor-Specific attributes are defined 3 octets. I understand that this limitation is consistent with the way RFC 2865 defines Vendor-ID but this will create problems when the 2**24 mark is hit. I see no reason not to use all the 4 octets (which are anyway defined) -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: critical | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From trac+radext@trac.tools.ietf.org Wed May 23 08:17:19 2012 Return-Path: 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 23E6A21F8732 for ; Wed, 23 May 2012 08:17:19 -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 lyCYMjPqubpd for ; Wed, 23 May 2012 08:17:18 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 96E5F21F872A for ; Wed, 23 May 2012 08:17:18 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDJN-0003yu-Vo; Wed, 23 May 2012 11:17:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:17:17 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/126 Message-ID: <059.464a57bf81f760986a5e078fc89efdd7@trac.tools.ietf.org> X-Trac-Ticket-ID: 126 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #126: 'traditional RADIUS' X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 15:17:19 -0000 #126: 'traditional RADIUS' It's a terminology issue, but it would be good to define more exactly what is meant by 'traditional RADIUS' in section 5 - everything RADIUS before this document, 2865 and a number of specific extensions, or just 2865? -- ---------------------------------+------------------------ Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: extended-attributes | Version: 1.0 Severity: In WG Last Call | Keywords: ---------------------------------+------------------------ Ticket URL: radext From radext-bounces@ietf.org Wed May 23 08:17:20 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0EBB21F8732; Wed, 23 May 2012 08:17:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337786240; bh=0qFXXkj523f3ocM/H3p3J8kngAKq0E55hgV1w5d4kiw=; h=MIME-Version:From:To:Date:Message-ID:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=ooeaDKK9LZmJcMC9z7BnYcHgjWs32KGzMbO6qHhDAYDGn+mAs8LnhEFJMmynbs1+q GgdX4CA2ks2TI5ikKfa4vZASMcm8eOce2c8+XiTz1VEkidcfs6j6st22uh4WpHC+3L Rfn92NN1WbwVvnNFrW1RyvwXsWFDWn946ZNg3iS8= 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 23E6A21F8732 for ; Wed, 23 May 2012 08:17:19 -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 lyCYMjPqubpd for ; Wed, 23 May 2012 08:17:18 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 96E5F21F872A for ; Wed, 23 May 2012 08:17:18 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDJN-0003yu-Vo; Wed, 23 May 2012 11:17:18 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:17:17 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/126 Message-ID: <059.464a57bf81f760986a5e078fc89efdd7@trac.tools.ietf.org> X-Trac-Ticket-ID: 126 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: [radext] #126: 'traditional RADIUS' X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyNjogJ3RyYWRpdGlvbmFsIFJBRElVUycKCiBJdCdzIGEgdGVybWlub2xvZ3kgaXNzdWUsIGJ1 dCBpdCB3b3VsZCBiZSBnb29kIHRvIGRlZmluZSBtb3JlIGV4YWN0bHkgd2hhdAogaXMgbWVhbnQg YnkgJ3RyYWRpdGlvbmFsIFJBRElVUycgaW4gc2VjdGlvbiA1IC0gZXZlcnl0aGluZyBSQURJVVMg YmVmb3JlCiB0aGlzIGRvY3VtZW50LCAyODY1IGFuZCBhIG51bWJlciBvZiBzcGVjaWZpYyBleHRl bnNpb25zLCBvciBqdXN0IDI4NjU/CgotLSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICAg ICAgICAgIHwgICAgICBPd25lcjoKICAgICBUeXBlOiAgZGVmZWN0ICAgICAgICAgICAgICAgfCAg ICAgU3RhdHVzOiAgbmV3CiBQcmlvcml0eTogIG1pbm9yICAgICAgICAgICAgICAgIHwgIE1pbGVz dG9uZTogIG1pbGVzdG9uZTEKQ29tcG9uZW50OiAgZXh0ZW5kZWQtYXR0cmlidXRlcyAgfCAgICBW ZXJzaW9uOiAgMS4wCiBTZXZlcml0eTogIEluIFdHIExhc3QgQ2FsbCAgICAgIHwgICBLZXl3b3Jk czoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4dC90 cmFjL3RpY2tldC8xMjY+CnJhZGV4dCA8aHR0cDovL3Rvb2xzLmlldGYub3JnL3JhZGV4dC8+Cgpf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQgbWFp bGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp c3RpbmZvL3JhZGV4dAo= From trac+radext@trac.tools.ietf.org Wed May 23 08:28:21 2012 Return-Path: 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 29BDF21F8777 for ; Wed, 23 May 2012 08:28:21 -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=[AWL=0.000, 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 WCTcZ5ti3ke5 for ; Wed, 23 May 2012 08:28:20 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id A324121F876F for ; Wed, 23 May 2012 08:28:20 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDTx-0000tb-0t; Wed, 23 May 2012 11:28:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:28:12 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/127 Message-ID: <059.75de6079ae95ed4e8eb03a6c7a1b71df@trac.tools.ietf.org> X-Trac-Ticket-ID: 127 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523152820.A324121F876F@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 08:28:20 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #127: attribute allocation flag X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 15:28:21 -0000 #127: attribute allocation flag In Section 5.1: > We RECOMMEND that RADIUS client and server implementations delete all references to these improperly defined attributes. Failing that, we RECOMMEND that RADIUS server implementations have a per-client configurable flag which indicates which type of attributes are being sent from the client. If the flag is set one way, the conflicting attributes can be interpreted as being improperly defined Vendor Specific Attributes. If the flag is set the other way, the attributes MUST be interpreted as being of the Extended Attributes format. The default SHOULD be to interpret the attributes as being of the Extended Attributes format. I suggest a more clear language, i.e a name for the flag and for the two states rather than 'one way', 'the other way'. For example 'Client- Extended-Attributes' / 'Standard-Extended-Attributes' (default) / 'Non- Standard-Vendor-Specific-Attributes' / -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: minor | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 08:28:23 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E714E21F8777; Wed, 23 May 2012 08:28:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337786902; bh=+V8cmSuvsOAEALWpuz/qZLTreFLZzzo2BnRLzaeEX9Y=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=U0ndfuKTYhkueKm/0V+kt6yH4QQXbFTzGjqTeHq16qyYMKdy4tfMxcY+Nyroc2Fvo DaiuJIh4HutKV5f2aEKiLqYcioWMpc0mu+1lCNOuZ5ei6cHLH++ub67S6crgySmh5Z vYs70hoaPYUmfeLfYxrREvpslymh8IV4uHktMbTU= 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 29BDF21F8777 for ; Wed, 23 May 2012 08:28:21 -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=[AWL=0.000, 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 WCTcZ5ti3ke5 for ; Wed, 23 May 2012 08:28:20 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id A324121F876F for ; Wed, 23 May 2012 08:28:20 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDTx-0000tb-0t; Wed, 23 May 2012 11:28:13 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:28:12 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/127 Message-ID: <059.75de6079ae95ed4e8eb03a6c7a1b71df@trac.tools.ietf.org> X-Trac-Ticket-ID: 127 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523152820.A324121F876F@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 08:28:20 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #127: attribute allocation flag X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyNzogYXR0cmlidXRlIGFsbG9jYXRpb24gZmxhZwoKIEluIFNlY3Rpb24gNS4xOgoKID4gIFdl IFJFQ09NTUVORCB0aGF0IFJBRElVUyBjbGllbnQgYW5kIHNlcnZlciBpbXBsZW1lbnRhdGlvbnMg ZGVsZXRlIGFsbAogcmVmZXJlbmNlcyB0byB0aGVzZSBpbXByb3Blcmx5IGRlZmluZWQgYXR0cmli dXRlcy4gIEZhaWxpbmcgdGhhdCwgd2UKIFJFQ09NTUVORCB0aGF0IFJBRElVUyBzZXJ2ZXIgaW1w bGVtZW50YXRpb25zIGhhdmUgYSBwZXItY2xpZW50CiBjb25maWd1cmFibGUgZmxhZyB3aGljaCBp bmRpY2F0ZXMgd2hpY2ggdHlwZSBvZiBhdHRyaWJ1dGVzIGFyZSBiZWluZyBzZW50CiBmcm9tIHRo ZSBjbGllbnQuICBJZiB0aGUgZmxhZyBpcyBzZXQgb25lIHdheSwgdGhlIGNvbmZsaWN0aW5nIGF0 dHJpYnV0ZXMKIGNhbiBiZSBpbnRlcnByZXRlZCBhcyBiZWluZyBpbXByb3Blcmx5IGRlZmluZWQg VmVuZG9yIFNwZWNpZmljIEF0dHJpYnV0ZXMuCiBJZiB0aGUgZmxhZyBpcyBzZXQgdGhlIG90aGVy IHdheSwgdGhlIGF0dHJpYnV0ZXMgTVVTVCBiZSBpbnRlcnByZXRlZCBhcwogYmVpbmcgb2YgdGhl IEV4dGVuZGVkIEF0dHJpYnV0ZXMgZm9ybWF0LiAgVGhlIGRlZmF1bHQgU0hPVUxEIGJlIHRvCiBp bnRlcnByZXQgdGhlIGF0dHJpYnV0ZXMgYXMgYmVpbmcgb2YgdGhlIEV4dGVuZGVkIEF0dHJpYnV0 ZXMgZm9ybWF0LgoKIEkgc3VnZ2VzdCBhIG1vcmUgY2xlYXIgbGFuZ3VhZ2UsIGkuZSBhIG5hbWUg Zm9yIHRoZSBmbGFnIGFuZCBmb3IgdGhlIHR3bwogc3RhdGVzIHJhdGhlciB0aGFuICdvbmUgd2F5 JywgJ3RoZSBvdGhlciB3YXknLiBGb3IgZXhhbXBsZSAnQ2xpZW50LQogRXh0ZW5kZWQtQXR0cmli dXRlcycgLyAnU3RhbmRhcmQtRXh0ZW5kZWQtQXR0cmlidXRlcycgKGRlZmF1bHQpIC8gJ05vbi0K IFN0YW5kYXJkLVZlbmRvci1TcGVjaWZpYy1BdHRyaWJ1dGVzJyAvCgotLSAKLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tCiBSZXBvcnRlcjogIGRyb21hc2NhQOKApiAgIHwgICAgICBPd25lcjogIGRyYWZ0LWll dGYtcmFkZXh0LXJhZGl1cy0KICAgICBUeXBlOiAgZGVmZWN0ICAgICAgIHwgIGV4dGVuc2lvbnNA 4oCmCiBQcmlvcml0eTogIG1pbm9yICAgICAgICB8ICAgICBTdGF0dXM6ICBuZXcKQ29tcG9uZW50 OiAgcmFkaXVzLSAgICAgIHwgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEKICBleHRlbnNpb25zICAg ICAgICAgICAgIHwgICAgVmVyc2lvbjogIDEuMAogU2V2ZXJpdHk6ICBJbiBXRyBMYXN0ICAgfCAg IEtleXdvcmRzOgogIENhbGwgICAgICAgICAgICAgICAgICAgfAotLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0K ClRpY2tldCBVUkw6IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9yYWRleHQvdHJhYy90 aWNrZXQvMTI3PgpyYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcg bGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m by9yYWRleHQK From radext-bounces@ietf.org Wed May 23 08:54:47 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7A121F8516; Wed, 23 May 2012 08:54:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337788487; bh=LC8JCMA+AbMc5Ncq9MpdgOuYtU6ZcbtBKuG8dQVuiKU=; h=MIME-Version:From:To:Date:Message-ID:Resent-To:Resent-Message-Id: Resent-Date:Resent-From:Cc:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=XAlPF7yOUkViaHb5/FCM71FtWxRFWkwx0B0dqbEJuOeuRgbdo8s0vHvrMV4ATsQqA xZqirAKmiNyT9EwfBILeJ34lHfd6iqb01c8NVzPQFtHJKFnZeIxGbk4fN/UWhlpD1/ RtbjxOea8d0nIkyC/4jeL/tSIT9ISEfig/ijuIOg= 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 77DD521F841E for ; Wed, 23 May 2012 08:54:46 -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=[AWL=0.000, 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 FPZLYgNIrETD for ; Wed, 23 May 2012 08:54:46 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 00DE821F8715 for ; Wed, 23 May 2012 08:54:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDtS-0000te-SK; Wed, 23 May 2012 11:54:35 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:54:34 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/128 Message-ID: <059.76254e126f8279a32f64f9a037b86828@trac.tools.ietf.org> X-Trac-Ticket-ID: 128 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523155446.00DE821F8715@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 08:54:45 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #128: editorial X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyODogZWRpdG9yaWFsCgogSW4gU2VjdGlvbiA2Ljc6CgogPiBSQURJVVMgY2xpZW50IGltcGxl bWVudGF0aW9ucyBTSE9VTEQgc3VwcG9ydCB0aGlzIHNwZWNpZmljYXRpb24gYXMgc29vbgogYXMg cG9zc2libGUuCgogPiBSQURJVVMgc2VydmVyIGltcGxlbWVudGF0aW9ucyBTSE9VTEQgc3VwcG9y dCB0aGlzIHNwZWNpZmljYXRpb24gYXMgc29vbgogYXMgcG9zc2libGUuCgogSSB3b3VsZCBkcm9w ICdhcyBzb29uIGFzIHBvc3NpYmxlJyBpbiBib3RoIHNlbnRlbmNlcwoKLS0gCi0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLQogUmVwb3J0ZXI6ICBkcm9tYXNjYUDigKYgICB8ICAgICAgT3duZXI6ICBkcmFmdC1p ZXRmLXJhZGV4dC1yYWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRlbnNpb25z QOKApgogUHJpb3JpdHk6ICB0cml2aWFsICAgICAgfCAgICAgU3RhdHVzOiAgbmV3CkNvbXBvbmVu dDogIHJhZGl1cy0gICAgICB8ICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCiAgZXh0ZW5zaW9ucyAg ICAgICAgICAgICB8ICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAgSW4gV0cgTGFzdCAgIHwg ICBLZXl3b3JkczoKICBDYWxsICAgICAgICAgICAgICAgICAgIHwKLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t CgpUaWNrZXQgVVJMOiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvcmFkZXh0L3RyYWMv dGlja2V0LzEyOD4KcmFkZXh0IDxodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmFkZXh0Lz4KCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJhZGV4dCBtYWlsaW5n IGxpc3QKcmFkZXh0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu Zm8vcmFkZXh0Cg== From trac+radext@trac.tools.ietf.org Wed May 23 08:54:46 2012 Return-Path: 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 77DD521F841E for ; Wed, 23 May 2012 08:54:46 -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=[AWL=0.000, 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 FPZLYgNIrETD for ; Wed, 23 May 2012 08:54:46 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 00DE821F8715 for ; Wed, 23 May 2012 08:54:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXDtS-0000te-SK; Wed, 23 May 2012 11:54:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com X-Trac-Project: radext Date: Wed, 23 May 2012 15:54:34 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/128 Message-ID: <059.76254e126f8279a32f64f9a037b86828@trac.tools.ietf.org> X-Trac-Ticket-ID: 128 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, dromasca@avaya.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523155446.00DE821F8715@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 08:54:45 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: [radext] #128: editorial X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 15:54:46 -0000 #128: editorial In Section 6.7: > RADIUS client implementations SHOULD support this specification as soon as possible. > RADIUS server implementations SHOULD support this specification as soon as possible. I would drop 'as soon as possible' in both sentences -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: trivial | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Keywords: Call | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 09:02:26 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2186721F86DF; Wed, 23 May 2012 09:02:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337788946; bh=QjhvNP+Ko64f4ncx4iatkFX/Tsb4q0oKvqtQdxCQW10=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender; b=E34ImcMpDRDPN4JEdaA35izsRNBjQ4SbZY1H7wwPMi2304q4/ju3LQOefLDb11bwy 9BvfVSveVkkxqML2RJoBtW087U48OFjBOqtoWZHDQ8m8hHsHWbVP9S0nU2GNb7/3cZ 2It//Xig3X4E7xZogF5pn0gCpBlVlmUP8ocmK2ss= 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 8BF7821F86DF for ; Wed, 23 May 2012 09:02:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 vLANXPilcAYy for ; Wed, 23 May 2012 09:02:25 -0700 (PDT) Received: from xenon12.um.es (xenon12.um.es [155.54.212.166]) by ietfa.amsl.com (Postfix) with ESMTP id E74D321F86D4 for ; Wed, 23 May 2012 09:02:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by xenon12.um.es (Postfix) with ESMTP id 978344BD93 for ; Wed, 23 May 2012 18:02:23 +0200 (CEST) X-Virus-Scanned: by antispam in UMU at xenon12.um.es Received: from xenon12.um.es ([127.0.0.1]) by localhost (xenon12.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bACNiuvI0rTA for ; Wed, 23 May 2012 18:02:23 +0200 (CEST) Received: from [155.54.205.90] (inf-205-90.inf.um.es [155.54.205.90]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: alex) by xenon12.um.es (Postfix) with ESMTPSA id E28734BD31 for ; Wed, 23 May 2012 18:02:18 +0200 (CEST) Message-ID: <4FBD0A0A.2050804@um.es> Date: Wed, 23 May 2012 18:02:18 +0200 From: Alejandro Perez Mendez User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: radext@ietf.org References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> <4FBCE19C.5000503@deployingradius.com> In-Reply-To: <4FBCE19C.5000503@deployingradius.com> Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org SGVsbG8sCgpJIGJlbGlldmUgaXQgdG9vLiBJbmRlZWQsIHdlIGFyZSBwcmVwYXJpbmcgYW4gdXBk YXRlZCB2ZXJzaW9uIG9mIHRoZSAKZnJhZ21lbnRhdGlvbiBkcmFmdCwgdGhhdCB3aWxsIGJlIHJl YWR5IHNvb24uCgpSZWdhcmRzLApBbGVqYW5kcm8KCkVsIDIzLzA1LzEyIDE1OjA5LCBBbGFuIERl S29rIGVzY3JpYmnDszoKPiBTYW0gSGFydG1hbiB3cm90ZToKPj4gSSBqdXN0IHdhbnQgdG8gY29u ZmlybSB0aGF0IHRoZSB3b3JrIHRvIHBlcm1pdCBmcmFnbWVudGF0aW9uIG9mIFJBRElVUwo+PiBt ZXNzYWdlcyB3b3VsZCBiZSB3aXRoaW4gc2NvcGUKPiAgICBJIGJlbGlldmUgaXQgc2hvdWxkIGJl Lgo+Cj4gICAgVGhpcyBpcyBjb3ZlcmVkIGluIHRoZSB0b3BpYyBvZiAiYWRkcmVzcyBwYWNrZXRz IGxvbmdlciB0aGFuIDRLIgo+Cj4gICAgQWxhbiBEZUtvay4KPiBfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IHJhZGV4dCBtYWlsaW5nIGxpc3QKPiByYWRl eHRAaWV0Zi5vcmcKPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JhZGV4 dApfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyYWRleHQg bWFpbGluZyBsaXN0CnJhZGV4dEBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu L2xpc3RpbmZvL3JhZGV4dAo= From alex@um.es Wed May 23 09:02:25 2012 Return-Path: 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 8BF7821F86DF for ; Wed, 23 May 2012 09:02:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 vLANXPilcAYy for ; Wed, 23 May 2012 09:02:25 -0700 (PDT) Received: from xenon12.um.es (xenon12.um.es [155.54.212.166]) by ietfa.amsl.com (Postfix) with ESMTP id E74D321F86D4 for ; Wed, 23 May 2012 09:02:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by xenon12.um.es (Postfix) with ESMTP id 978344BD93 for ; Wed, 23 May 2012 18:02:23 +0200 (CEST) X-Virus-Scanned: by antispam in UMU at xenon12.um.es Received: from xenon12.um.es ([127.0.0.1]) by localhost (xenon12.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bACNiuvI0rTA for ; Wed, 23 May 2012 18:02:23 +0200 (CEST) Received: from [155.54.205.90] (inf-205-90.inf.um.es [155.54.205.90]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: alex) by xenon12.um.es (Postfix) with ESMTPSA id E28734BD31 for ; Wed, 23 May 2012 18:02:18 +0200 (CEST) Message-ID: <4FBD0A0A.2050804@um.es> Date: Wed, 23 May 2012 18:02:18 +0200 From: Alejandro Perez Mendez User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: radext@ietf.org References: <4FBBED0A.2050606@deployingradius.com> <4FBCCB57.7010606@restena.lu> <4FBCE19C.5000503@deployingradius.com> In-Reply-To: <4FBCE19C.5000503@deployingradius.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [radext] RADEXT charter X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 16:02:25 -0000 Hello, I believe it too. Indeed, we are preparing an updated version of the fragmentation draft, that will be ready soon. Regards, Alejandro El 23/05/12 15:09, Alan DeKok escribió: > Sam Hartman wrote: >> I just want to confirm that the work to permit fragmentation of RADIUS >> messages would be within scope > I believe it should be. > > This is covered in the topic of "address packets longer than 4K" > > Alan DeKok. > _______________________________________________ > radext mailing list > radext@ietf.org > https://www.ietf.org/mailman/listinfo/radext From trac+radext@trac.tools.ietf.org Wed May 23 12:10:36 2012 Return-Path: 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 E554121F8714 for ; Wed, 23 May 2012 12:10:36 -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=[AWL=0.000, 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 UWrHpcRacJ6Q for ; Wed, 23 May 2012 12:10:32 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id D0A6721F8713 for ; Wed, 23 May 2012 12:10:31 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXGx3-0001QR-AP; Wed, 23 May 2012 15:10:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 19:10:28 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/126#comment:1 Message-ID: <074.77b6237e86bcfb727be6fb0307930334@trac.tools.ietf.org> References: <059.464a57bf81f760986a5e078fc89efdd7@trac.tools.ietf.org> X-Trac-Ticket-ID: 126 In-Reply-To: <059.464a57bf81f760986a5e078fc89efdd7@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #126: 'traditional RADIUS' X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 19:10:37 -0000 #126: 'traditional RADIUS' Comment (by aland@…): I'll change this to: --- There are a number of potential compatibility issues with traditional RADIUS, as defined in [RFC6158] and earlier. This section describes them. --- i.e. RADIUS before TLS && TCP. -- ---------------------------------+------------------------- Reporter: dromasca@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: extended-attributes | Version: 1.0 Severity: In WG Last Call | Resolution: Keywords: | ---------------------------------+------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 12:10:38 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB9D21F8717; Wed, 23 May 2012 12:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337800238; bh=OBMtBrypGkS41LeufLZ2BnPx7FN5zeGUHZSeVZec6vA=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To:Cc: Subject:Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:Content-Type:Content-Transfer-Encoding: Sender; b=jzo5jtxGnbaXulHcmiYkCXoDhWJcYTPWFpB9nhBLXtLN5SOgoHRf4nfOaQqoLhJ+B lQk0XakYA9raOcYFJDX+0QVvcKNbKXWJbhg0/Xq5OZSLSKvAzzOt3xXY7nEdM3r4D/ fXTrkGTikplW7hnEo+Oz12CLohgH4xv/2jn65wm0= 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 E554121F8714 for ; Wed, 23 May 2012 12:10:36 -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=[AWL=0.000, 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 UWrHpcRacJ6Q for ; Wed, 23 May 2012 12:10:32 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id D0A6721F8713 for ; Wed, 23 May 2012 12:10:31 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXGx3-0001QR-AP; Wed, 23 May 2012 15:10:30 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 19:10:28 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/126#comment:1 Message-ID: <074.77b6237e86bcfb727be6fb0307930334@trac.tools.ietf.org> References: <059.464a57bf81f760986a5e078fc89efdd7@trac.tools.ietf.org> X-Trac-Ticket-ID: 126 In-Reply-To: <059.464a57bf81f760986a5e078fc89efdd7@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: radext@ietf.org Subject: Re: [radext] #126: 'traditional RADIUS' X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyNjogJ3RyYWRpdGlvbmFsIFJBRElVUycKCgpDb21tZW50IChieSBhbGFuZEDigKYpOgoKIEkn bGwgY2hhbmdlIHRoaXMgdG86CgogLS0tCiBUaGVyZSBhcmUgYSBudW1iZXIgb2YgcG90ZW50aWFs IGNvbXBhdGliaWxpdHkgaXNzdWVzIHdpdGggdHJhZGl0aW9uYWwKIFJBRElVUywgYXMgZGVmaW5l ZCBpbiBbUkZDNjE1OF0gYW5kIGVhcmxpZXIuICBUaGlzIHNlY3Rpb24gZGVzY3JpYmVzCiB0aGVt LgogLS0tCgogaS5lLiBSQURJVVMgYmVmb3JlIFRMUyAmJiBUQ1AuCgotLSAKLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KIFJlcG9ydGVy OiAgZHJvbWFzY2FA4oCmICAgICAgICAgICB8ICAgICAgIE93bmVyOgogICAgIFR5cGU6ICBkZWZl Y3QgICAgICAgICAgICAgICB8ICAgICAgU3RhdHVzOiAgbmV3CiBQcmlvcml0eTogIG1pbm9yICAg ICAgICAgICAgICAgIHwgICBNaWxlc3RvbmU6ICBtaWxlc3RvbmUxCkNvbXBvbmVudDogIGV4dGVu ZGVkLWF0dHJpYnV0ZXMgIHwgICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAgSW4gV0cgTGFz dCBDYWxsICAgICAgfCAgUmVzb2x1dGlvbjoKIEtleXdvcmRzOiAgICAgICAgICAgICAgICAgICAg ICAgfAotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3JhZGV4 dC90cmFjL3RpY2tldC8xMjYjY29tbWVudDoxPgpyYWRleHQgPGh0dHA6Ly90b29scy5pZXRmLm9y Zy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5v cmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From trac+radext@trac.tools.ietf.org Wed May 23 12:13:45 2012 Return-Path: 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 85B8C21F8732 for ; Wed, 23 May 2012 12:13:45 -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 B76VL2Y9BL2y for ; Wed, 23 May 2012 12:13:45 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 15EEA21F8713 for ; Wed, 23 May 2012 12:13:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXH07-0002WC-Hl; Wed, 23 May 2012 15:13:39 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 19:13:39 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/128#comment:1 Message-ID: <074.55f7c48652f7db9a56f3c3b6e0113c65@trac.tools.ietf.org> References: <059.76254e126f8279a32f64f9a037b86828@trac.tools.ietf.org> X-Trac-Ticket-ID: 128 In-Reply-To: <059.76254e126f8279a32f64f9a037b86828@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523191345.15EEA21F8713@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 12:13:45 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #128: editorial X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 19:13:45 -0000 #128: editorial Comment (by aland@…): That leaves the recommendations toothless. Of course people SHOULD implement the document. The alternative would be to not publish it. Perhaps adding an explanation: --- * RADIUS client implementations SHOULD support this specification as soon as possible, in order to permit the easy deployment of specifications using the changes defined herein. * RADIUS server implementations SHOULD support this specification as soon as possible, in order to permit the easy deployment of specifications using the changes defined herein. --- -- -------------------------+------------------------------------------------- Reporter: dromasca@… | Owner: draft-ietf-radext-radius- Type: defect | extensions@… Priority: trivial | Status: new Component: radius- | Milestone: milestone1 extensions | Version: 1.0 Severity: In WG Last | Resolution: Call | Keywords: | -------------------------+------------------------------------------------- Ticket URL: radext From radext-bounces@ietf.org Wed May 23 12:13:47 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E2C21F8736; Wed, 23 May 2012 12:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1337800427; bh=tiv4lek5DGsTC0lKsWbCB19VuXn5MfS44DiDUGUBkHc=; h=MIME-Version:From:To:Date:Message-ID:References:In-Reply-To: Resent-To:Resent-Message-Id:Resent-Date:Resent-From:Cc:Subject: Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=ui1mFHhIc+XpQWws3lE84I1xHVCzu4ks2cpPcmK+T7LeDU2iVAxeOWOL4E9/px/Lb rSmKH691mASJLX60SxmY3w1oR1YvUUtJcDJPRwsk4qlhFsfmHl3yWoai9x4XrPwigD ugKjz5NmE5Ni2ZpYorWtMZSaVHRewNhCAmI9KdcQ= 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 85B8C21F8732 for ; Wed, 23 May 2012 12:13:45 -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 B76VL2Y9BL2y for ; Wed, 23 May 2012 12:13:45 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 15EEA21F8713 for ; Wed, 23 May 2012 12:13:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SXH07-0002WC-Hl; Wed, 23 May 2012 15:13:39 -0400 MIME-Version: 1.0 From: "radext issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com X-Trac-Project: radext Date: Wed, 23 May 2012 19:13:39 -0000 X-URL: http://tools.ietf.org/radext/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/128#comment:1 Message-ID: <074.55f7c48652f7db9a56f3c3b6e0113c65@trac.tools.ietf.org> References: <059.76254e126f8279a32f64f9a037b86828@trac.tools.ietf.org> X-Trac-Ticket-ID: 128 In-Reply-To: <059.76254e126f8279a32f64f9a037b86828@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-radext-radius-extensions@tools.ietf.org, aland@deployingradius.com, radext@ietf.org X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120523191345.15EEA21F8713@ietfa.amsl.com> Resent-Date: Wed, 23 May 2012 12:13:45 -0700 (PDT) Resent-From: trac+radext@trac.tools.ietf.org Cc: radext@ietf.org Subject: Re: [radext] #128: editorial X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Reply-To: radext@ietf.org List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org IzEyODogZWRpdG9yaWFsCgoKQ29tbWVudCAoYnkgYWxhbmRA4oCmKToKCiBUaGF0IGxlYXZlcyB0 aGUgcmVjb21tZW5kYXRpb25zIHRvb3RobGVzcy4gIE9mIGNvdXJzZSBwZW9wbGUgU0hPVUxECiBp bXBsZW1lbnQgdGhlIGRvY3VtZW50LiAgVGhlIGFsdGVybmF0aXZlIHdvdWxkIGJlIHRvIG5vdCBw dWJsaXNoIGl0LgoKIFBlcmhhcHMgYWRkaW5nIGFuIGV4cGxhbmF0aW9uOgoKIC0tLQogKiBSQURJ VVMgY2xpZW50IGltcGxlbWVudGF0aW9ucyBTSE9VTEQgc3VwcG9ydCB0aGlzIHNwZWNpZmljYXRp b24KICAgYXMgc29vbiBhcyBwb3NzaWJsZSwgaW4gb3JkZXIgdG8gcGVybWl0IHRoZSBlYXN5IGRl cGxveW1lbnQKICAgb2Ygc3BlY2lmaWNhdGlvbnMgdXNpbmcgdGhlIGNoYW5nZXMgZGVmaW5lZCBo ZXJlaW4uCgogKiBSQURJVVMgc2VydmVyIGltcGxlbWVudGF0aW9ucyBTSE9VTEQgc3VwcG9ydCB0 aGlzIHNwZWNpZmljYXRpb24KICAgYXMgc29vbiBhcyBwb3NzaWJsZSwgaW4gb3JkZXIgdG8gcGVy bWl0IHRoZSBlYXN5IGRlcGxveW1lbnQKICAgb2Ygc3BlY2lmaWNhdGlvbnMgdXNpbmcgdGhlIGNo YW5nZXMgZGVmaW5lZCBoZXJlaW4uCgogLS0tCgotLSAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiBSZXBv cnRlcjogIGRyb21hc2NhQOKApiAgIHwgICAgICAgT3duZXI6ICBkcmFmdC1pZXRmLXJhZGV4dC1y YWRpdXMtCiAgICAgVHlwZTogIGRlZmVjdCAgICAgICB8ICBleHRlbnNpb25zQOKApgogUHJpb3Jp dHk6ICB0cml2aWFsICAgICAgfCAgICAgIFN0YXR1czogIG5ldwpDb21wb25lbnQ6ICByYWRpdXMt ICAgICAgfCAgIE1pbGVzdG9uZTogIG1pbGVzdG9uZTEKICBleHRlbnNpb25zICAgICAgICAgICAg IHwgICAgIFZlcnNpb246ICAxLjAKIFNldmVyaXR5OiAgSW4gV0cgTGFzdCAgIHwgIFJlc29sdXRp b246CiAgQ2FsbCAgICAgICAgICAgICAgICAgICB8CiBLZXl3b3JkczogICAgICAgICAgICAgICB8 Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLQoKVGlja2V0IFVSTDogPGh0dHA6Ly90cmFjLnRvb2xzLmlldGYu b3JnL3dnL3JhZGV4dC90cmFjL3RpY2tldC8xMjgjY29tbWVudDoxPgpyYWRleHQgPGh0dHA6Ly90 b29scy5pZXRmLm9yZy9yYWRleHQvPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18KcmFkZXh0IG1haWxpbmcgbGlzdApyYWRleHRAaWV0Zi5vcmcKaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yYWRleHQK From wwwrun@rfc-editor.org Tue May 29 09:39:02 2012 Return-Path: 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 EE5F721F8741; Tue, 29 May 2012 09:39:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.899 X-Spam-Level: X-Spam-Status: No, score=-102.899 tagged_above=-999 required=5 tests=[AWL=2.777, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, 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 Wpz3TYArQL31; Tue, 29 May 2012 09:39:00 -0700 (PDT) Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id DCD1321F86D1; Tue, 29 May 2012 09:39:00 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 83108B1E00A; Tue, 29 May 2012 09:38:25 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20120529163825.83108B1E00A@rfc-editor.org> Date: Tue, 29 May 2012 09:38:25 -0700 (PDT) Cc: radext@ietf.org, rfc-editor@rfc-editor.org Subject: [radext] RFC 6613 on RADIUS over TCP X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2012 16:39:03 -0000 A new Request for Comments is now available in online RFC libraries. RFC 6613 Title: RADIUS over TCP Author: A. DeKok Status: Experimental Stream: IETF Date: May 2012 Mailbox: aland@freeradius.org Pages: 16 Characters: 37646 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-radext-tcp-transport-09.txt URL: http://www.rfc-editor.org/rfc/rfc6613.txt The Remote Authentication Dial-In User Server (RADIUS) protocol has, until now, required the User Datagram Protocol (UDP) as the underlying transport layer. This document defines RADIUS over the Transmission Control Protocol (RADIUS/TCP), in order to address handling issues related to RADIUS over Transport Layer Security (RADIUS/TLS). It permits TCP to be used as a transport protocol for RADIUS only when a transport layer such as TLS or IPsec provides confidentiality and security. This document defines an Experimental Protocol for the Internet community. This document is a product of the RADIUS EXTensions Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From radext-bounces@ietf.org Tue May 29 09:39:04 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45C7821F8741; Tue, 29 May 2012 09:39:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1338309544; bh=FF2KzfHZbp67dB8XoiVpZaCXJUDJBxiCRMUSgUW/xws=; h=To:From:Message-Id:Date:Cc:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:MIME-Version: Content-Type:Content-Transfer-Encoding:Sender; b=QHglDhiwe0T46QJE3i4nYbv/dADz812GitTtDyZVspaJD+6Nhefil8yETvjh0UGXB oyby0A/NXpNoIzdV+lfWq8zrD24fQcVwm56eR/PKJvRDgKAENSLzJDxeL8fNlN1Ogv qI1rrf7PU5FHItOxSgpJSxSyEaXE9oMJH1eOOB4o= 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 EE5F721F8741; Tue, 29 May 2012 09:39:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.899 X-Spam-Level: X-Spam-Status: No, score=-102.899 tagged_above=-999 required=5 tests=[AWL=2.777, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, 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 Wpz3TYArQL31; Tue, 29 May 2012 09:39:00 -0700 (PDT) Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id DCD1321F86D1; Tue, 29 May 2012 09:39:00 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 83108B1E00A; Tue, 29 May 2012 09:38:25 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20120529163825.83108B1E00A@rfc-editor.org> Date: Tue, 29 May 2012 09:38:25 -0700 (PDT) Cc: radext@ietf.org, rfc-editor@rfc-editor.org Subject: [radext] RFC 6613 on RADIUS over TCP X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 6613 Title: RADIUS over TCP Author: A. DeKok Status: Experimental Stream: IETF Date: May 2012 Mailbox: aland@freeradius.org Pages: 16 Characters: 37646 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-radext-tcp-transport-09.txt URL: http://www.rfc-editor.org/rfc/rfc6613.txt The Remote Authentication Dial-In User Server (RADIUS) protocol has, until now, required the User Datagram Protocol (UDP) as the underlying transport layer. This document defines RADIUS over the Transmission Control Protocol (RADIUS/TCP), in order to address handling issues related to RADIUS over Transport Layer Security (RADIUS/TLS). It permits TCP to be used as a transport protocol for RADIUS only when a transport layer such as TLS or IPsec provides confidentiality and security. This document defines an Experimental Protocol for the Internet community. This document is a product of the RADIUS EXTensions Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext From wwwrun@rfc-editor.org Tue May 29 09:39:17 2012 Return-Path: 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 1572F21F8768; Tue, 29 May 2012 09:39:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.131 X-Spam-Level: X-Spam-Status: No, score=-103.131 tagged_above=-999 required=5 tests=[AWL=2.546, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, 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 1y38KHzpnCrC; Tue, 29 May 2012 09:39:16 -0700 (PDT) Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 27E7F21F87B8; Tue, 29 May 2012 09:39:16 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id B62F2B1E00B; Tue, 29 May 2012 09:38:40 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20120529163840.B62F2B1E00B@rfc-editor.org> Date: Tue, 29 May 2012 09:38:40 -0700 (PDT) Cc: radext@ietf.org, rfc-editor@rfc-editor.org Subject: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2012 16:39:17 -0000 A new Request for Comments is now available in online RFC libraries. RFC 6614 Title: Transport Layer Security (TLS) Encryption for RADIUS Author: S. Winter, M. McCauley, S. Venaas, K. Wierenga Status: Experimental Stream: IETF Date: May 2012 Mailbox: stefan.winter@restena.lu, mikem@open.com.au, stig@cisco.com, klaas@cisco.com Pages: 22 Characters: 48004 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-radext-radsec-12.txt URL: http://www.rfc-editor.org/rfc/rfc6614.txt This document specifies a transport profile for RADIUS using Transport Layer Security (TLS) over TCP as the transport protocol. This enables dynamic trust relationships between RADIUS servers. [STANDARDS-TRACK] This document is a product of the RADIUS EXTensions Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From radext-bounces@ietf.org Tue May 29 09:39:20 2012 Return-Path: X-Original-To: radext-archive-IeZ9sae2@lists.ietf.org Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD2C121F87C3; Tue, 29 May 2012 09:39:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1338309560; bh=h2ATRljUP3oEpPUfXifRc4HGIC7DWUCMFzYCh+7QeJE=; h=To:From:Message-Id:Date:Cc:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:MIME-Version: Content-Type:Content-Transfer-Encoding:Sender; b=AWmV2Mf62xAvhXXIc8Fc1Ml3UMfTY44hV2wfXr+NUJi1D4ob2rplQ7C/dNaqFdH5Q nrGKhAe8b9lrsbrbU5jHx/MvbOuVWuvx3qKhSJvHFqo/LBimDLIiKlAvwr743vrYZt vefHPlSTTpYjtIXhqDAP/3pwugvGZmztEgH36jE4= 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 1572F21F8768; Tue, 29 May 2012 09:39:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.131 X-Spam-Level: X-Spam-Status: No, score=-103.131 tagged_above=-999 required=5 tests=[AWL=2.546, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, 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 1y38KHzpnCrC; Tue, 29 May 2012 09:39:16 -0700 (PDT) Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 27E7F21F87B8; Tue, 29 May 2012 09:39:16 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id B62F2B1E00B; Tue, 29 May 2012 09:38:40 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20120529163840.B62F2B1E00B@rfc-editor.org> Date: Tue, 29 May 2012 09:38:40 -0700 (PDT) Cc: radext@ietf.org, rfc-editor@rfc-editor.org Subject: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS X-BeenThere: radext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: RADIUS EXTensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: radext-bounces@ietf.org Errors-To: radext-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 6614 Title: Transport Layer Security (TLS) Encryption for RADIUS Author: S. Winter, M. McCauley, S. Venaas, K. Wierenga Status: Experimental Stream: IETF Date: May 2012 Mailbox: stefan.winter@restena.lu, mikem@open.com.au, stig@cisco.com, klaas@cisco.com Pages: 22 Characters: 48004 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-radext-radsec-12.txt URL: http://www.rfc-editor.org/rfc/rfc6614.txt This document specifies a transport profile for RADIUS using Transport Layer Security (TLS) over TCP as the transport protocol. This enables dynamic trust relationships between RADIUS servers. [STANDARDS-TRACK] This document is a product of the RADIUS EXTensions Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext