
From owner-radiusext@ops.ietf.org  Wed Jun  2 08:04:17 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40B6128C0F6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 08:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.689
X-Spam-Level: 
X-Spam-Status: No, score=-0.689 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-sGWpXFeY8t for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 08:04:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DD48F3A69E0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  2 Jun 2010 08:04:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OJpN3-000EeK-O1 for radiusext-data0@psg.com; Wed, 02 Jun 2010 14:56:41 +0000
Received: from [198.152.71.100] (helo=de307622-de-outbound.net.avaya.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <dromasca@avaya.com>) id 1OJpN0-000Ecu-Cp for radiusext@ops.ietf.org; Wed, 02 Jun 2010 14:56:38 +0000
X-IronPort-AV: E=Sophos;i="4.53,347,1272859200";  d="scan'208";a="191563323"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 02 Jun 2010 10:56:30 -0400
X-IronPort-AV: E=Sophos;i="4.53,347,1272859200";  d="scan'208";a="480260585"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Jun 2010 10:56:28 -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
Subject: FEDAUTH BOF request
Date: Wed, 2 Jun 2010 16:56:17 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: FEDAUTH BOF request
Thread-Index: AcsCY8D3YG4qrCIAT927dkDMQ1m8hw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>, "radext mailing list" <radiusext@ops.ietf.org>, <aaa-doctors@ietf.org>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.=20

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun  2 08:18:05 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BEC228C117 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 08:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.947
X-Spam-Level: 
X-Spam-Status: No, score=-2.947 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glmtYRZ7vzlr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 08:18:04 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 294553A6A07 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  2 Jun 2010 08:18:04 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OJpex-000Iac-Rt for radiusext-data0@psg.com; Wed, 02 Jun 2010 15:15:11 +0000
Received: from [216.82.254.195] (helo=mail200.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OJpep-000IYz-U0 for radiusext@ops.ietf.org; Wed, 02 Jun 2010 15:15:04 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-4.tower-200.messagelabs.com!1275491692!51136540!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 18145 invoked from network); 2 Jun 2010 15:14:53 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-4.tower-200.messagelabs.com with RC4-SHA encrypted SMTP; 2 Jun 2010 15:14:53 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Wed, 2 Jun 2010 11:14:52 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Wed, 2 Jun 2010 11:14:51 -0400
Subject: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsCZljknF/AXCfARZua6Gos5EBBoA==
Message-ID: <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com>
In-Reply-To: <4BC875D5.1060802@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Section 1.2

Issue 1:
Special language is provided for "MUST" "MUST-NOT"  do we need to state the=
 same for "SHALL" and "SHALL-NOT"?  I am not sure because I haven't checked=
. =20

Section 1.3.1

Issue 2:
"We do not forbid these specifications, but it is
   RECOMMENDED that they are created only if they have a limited scope
   of applicability, and all new attributes defined in those
   specifications are VSAs."

What is meant by "limited scope of applicability"?  Is it limited scope of =
applicability within the SDO?  I would think not.  It is already stated in =
this section that - SDO can design for their own purposes in several places=
 in this section:

 "By
   articulating guidelines for RADIUS attribute design, this document
   enables SDOs out of the IETF to design their own RADIUS attributes
   within the Vendor-Specific Attribute (VSA) space."

Is "limited scope of applicability" over and above that?  The basic problem=
 is that we have lots of text that is repeating in this section.

Issue 3:

I disagree that:

 * use only the "basic data types" (see below) for all VSAs;

Please delete that.  Since the next bullet=20

Actually, the last bullet suffices:

  * follow the guidelines given in this document.

I suggest getting rid of the bullets and just state:

 It is RECOMMENDED that SDOs and vendors seek review of RADIUS
   attribute specifications from the IETF.  However, specifications do
   not require IETF review when they follow the guidelines given this docum=
ent.

Issue: 4:

Section 2.1

Change:

 All other data formats are defined to be "complex data types", and
   are NOT RECOMMENDED for normal use.  Nested attributes, or attributes
   grouped via methods other than defined in [RFC2868] do not qualify as
   "basic data types", and SHOULD NOT be used.

To
 All other data formats are defined to be "complex data types", and
   are NOT RECOMMENDED for normal use including nested attributes, or attri=
butes
   grouped via methods other than defined in [RFC2868].

I think the document asserts already that complex data types should not be =
used.

Issue 5:

Section 2.2

The following text does not make sense:

" Vendors therefore SHOULD NOT use multiple
   formats for VSAs that are associated with a particular Vendor Id.  A
   vendor wishing to use multiple VSA formats SHOULD request one Vendor
   Id for each VSA format that they will use."

If a vendor defines two VSAs one of a basic type and another of a non-basic=
 type they should not require a new vendor id.  Please delete this recommen=
dation.

Issue 6:
 Section 3.2

" These approaches are often incompatible, leading to
   additional complexity in RADIUS implementations."

But they dont have to be compatible.

Get rid of that statement.

Issue 7:

Section 3.3.3:
Is repeating text in previous sections: 1.3.1

The level of repetition in this document is very high. Points are stated an=
d restated and restated.  It is very exhausting to read.


Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun  2 21:06:38 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BBE13A6929 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 21:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.767
X-Spam-Level: 
X-Spam-Status: No, score=-99.767 tagged_above=-999 required=5 tests=[AWL=0.728, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ccjoose56UQ1 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 21:06:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2FA1F3A6835 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  2 Jun 2010 21:06:37 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK1dt-000Llu-2H for radiusext-data0@psg.com; Thu, 03 Jun 2010 04:02:53 +0000
Received: from [119.145.14.67] (helo=szxga04-in.huawei.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <tena@huawei.com>) id 1OK1dp-000Llb-1g for radiusext@ops.ietf.org; Thu, 03 Jun 2010 04:02:49 +0000
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00JJE78M6Y@szxga04-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 12:02:46 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00AXX78MAP@szxga04-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 12:02:46 +0800 (CST)
Received: from z00147053k ([10.70.39.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3F00HS878LTS@szxml04-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 12:02:46 +0800 (CST)
Date: Thu, 03 Jun 2010 12:02:46 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: FEDAUTH BOF request
To: aaa-doctors@ietf.org, radext mailing list <radiusext@ops.ietf.org>, dime@ietf.org, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-id: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Comments are below.
1. This might be of interest to ngHLR (Unified Subscriber Center) kind of 
solutions who provide Identity Management services
2. From protocol side, I think it may be more interesting for RADIUS as I 
doubt the suitability of Diameter for this.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
<aaa-doctors@ietf.org>
Sent: Wednesday, June 02, 2010 10:56 PM
Subject: FEDAUTH BOF request


Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun  2 22:07:45 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5625A3A69C5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 22:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.258
X-Spam-Level: 
X-Spam-Status: No, score=-0.258 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rf2ouaPP1O4d for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 22:07:42 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 050123A6A67 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  2 Jun 2010 22:07:40 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK2aT-0002Dn-M8 for radiusext-data0@psg.com; Thu, 03 Jun 2010 05:03:25 +0000
Received: from [65.55.111.88] (helo=blu0-omc2-s13.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OK2aP-0002D1-UM for radiusext@ops.ietf.org; Thu, 03 Jun 2010 05:03:22 +0000
Received: from BLU137-W35 ([65.55.111.72]) by blu0-omc2-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 2 Jun 2010 22:03:20 -0700
Message-ID: <BLU137-W350A9D16B24A7A1F9D76F193D10@phx.gbl>
Content-Type: multipart/alternative; boundary="_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_"
X-Originating-IP: [64.134.138.42]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, <dime@ietf.org>, "dromasca@avaya.com" <dromasca@avaya.com>
Subject: RE: FEDAUTH BOF request
Date: Wed, 2 Jun 2010 22:03:16 -0700
Importance: Normal
In-Reply-To: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>,<F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Jun 2010 05:03:20.0939 (UTC) FILETIME=[163CA3B0:01CB02DA]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Tina said:=20

> Comments are below.
> 1. This might be of interest to ngHLR (Unified Subscriber Center) kind of=
=20
> solutions who provide Identity Management services
> 2. From protocol side=2C I think it may be more interesting for RADIUS as=
 I  doubt the suitability of Diameter for this.

Not sure why RADIUS would be more suitable than Diameter for carrying large=
 payloads such as SAML assertions.  The 4096 octet RADIUS PDU limit is not =
transport-specific -- that is=2C transporting the RADIUS payload over TCP d=
oes not solve the problem.=20

=20
> ----- Original Message -----=20
> From: "Romascanu=2C Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>=3B "radext mailing list" <radiusext@ops.ietf.org>=3B=
=20
> <aaa-doctors@ietf.org>
> Sent: Wednesday=2C June 02=2C 2010 10:56 PM
> Subject: FEDAUTH BOF request
>=20
>=20
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
>=20
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/=2C and more information abou=
t
> this BOF or other BOF requests can be examined  at
> http://trac.tools.ietf.org/bof/trac/
>=20
> Dan
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Tina said: <br><br>&gt=3B Comments are below.<br>&gt=3B 1. This might be of=
 interest to ngHLR (Unified Subscriber Center) kind of <br>&gt=3B solutions=
 who provide Identity Management services<br>&gt=3B 2. From protocol side=
=2C I think it may be more interesting for RADIUS as I&nbsp=3B doubt the su=
itability of Diameter for this.<br><br>Not sure why RADIUS would be more su=
itable than Diameter for carrying large payloads such as SAML assertions.&n=
bsp=3B The 4096 octet RADIUS PDU limit is not transport-specific -- that is=
=2C transporting the RADIUS payload over TCP does not solve the problem. <b=
r><br>&nbsp=3B<br>&gt=3B ----- Original Message ----- <br>&gt=3B From: "Rom=
ascanu=2C Dan (Dan)" &lt=3Bdromasca@avaya.com&gt=3B<br>&gt=3B To: &lt=3Bdim=
e@ietf.org&gt=3B=3B "radext mailing list" &lt=3Bradiusext@ops.ietf.org&gt=
=3B=3B <br>&gt=3B &lt=3Baaa-doctors@ietf.org&gt=3B<br>&gt=3B Sent: Wednesda=
y=2C June 02=2C 2010 10:56 PM<br>&gt=3B Subject: FEDAUTH BOF request<br>&gt=
=3B <br>&gt=3B <br>&gt=3B Diameter and RADIUS experts should pay attention =
to the request to hold<br>&gt=3B a Federated Authentication (FEDAUTH) BOF w=
hich will be discussed this<br>&gt=3B morning by the IAB and the IESG.<br>&=
gt=3B <br>&gt=3B The Draft Charter is available at<br>&gt=3B http://www.pro=
ject-moonshot.org/bof/charter/=2C and more information about<br>&gt=3B this=
 BOF or other BOF requests can be examined  at<br>&gt=3B http://trac.tools.=
ietf.org/bof/trac/<br>&gt=3B <br>&gt=3B Dan<br>&gt=3B <br>&gt=3B --<br>&gt=
=3B to unsubscribe send a message to radiusext-request@ops.ietf.org with<br=
>&gt=3B the word 'unsubscribe' in a single line as the message text body.<b=
r>&gt=3B archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br>&gt=3B <br=
>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscribe send a message to=
 radiusext-request@ops.ietf.org with<br>&gt=3B the word 'unsubscribe' in a =
single line as the message text body.<br>&gt=3B archive: &lt=3Bhttp://psg.c=
om/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun  2 22:32:54 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 213853A6963 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 22:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.28
X-Spam-Level: 
X-Spam-Status: No, score=-0.28 tagged_above=-999 required=5 tests=[AWL=0.214, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iXX7vAs+Etx8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  2 Jun 2010 22:32:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 430683A63CA for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  2 Jun 2010 22:31:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK2wr-0004um-CE for radiusext-data0@psg.com; Thu, 03 Jun 2010 05:26:33 +0000
Received: from [65.55.111.110] (helo=blu0-omc2-s35.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OK2wl-0004t0-Ir for radiusext@ops.ietf.org; Thu, 03 Jun 2010 05:26:27 +0000
Received: from BLU137-W24 ([65.55.111.72]) by blu0-omc2-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 2 Jun 2010 22:26:26 -0700
Message-ID: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
Content-Type: multipart/alternative; boundary="_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_"
X-Originating-IP: [64.134.138.42]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, <dime@ietf.org>, "dromasca@avaya.com" <dromasca@avaya.com>
Subject: RE: FEDAUTH BOF request
Date: Wed, 2 Jun 2010 22:26:26 -0700
Importance: Normal
In-Reply-To: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>,<F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Jun 2010 05:26:26.0401 (UTC) FILETIME=[50095D10:01CB02DD]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Let me provide a bit of  context about what I think the problem is here.=20

As noted by Sam in a previous conversation=2C the basic use case is "cloud =
services"=2C where an education institution or enterprise is making use of =
hosted services.  In these situations=2C the institution may not just want =
the service provider to host an application=2C but may want to keep their c=
redentials local=2C rather than hosting this in the cloud as well.=20

In the original Moonshot investigation=2C Kerberos was considered as a pote=
ntial solution.  However=2C while Kerberos is well understood from a securi=
ty point of view=2C and could relatively easily be modified to support EAP-=
based pre-auth (numerous proposals for this have been advanced and in some =
cases implemented)  Kerberos federation has not been widely deployed.=20

One of the basic problems with putting a KDC on the Internet is that there =
is no easy way to protect it=2C since both clients and other KDCs may need =
to send packets to and from the KDC.  For this reason if there are roaming =
clients there is no easy way to filter traffic to/from the KDC.  In additio=
n=2C the Kerberos protocol is vulnerable to passive attacks in the absence =
of extensions such as PKINIT or Kerberos Hardening.=20

In contrast=2C the AAA roaming model has been widely deployed=2C in part be=
cause it is much easier to protect a AAA server.  AAA servers only talk to =
AAA clients=2C not to users directly.  This means that it is typically poss=
ible to filter traffic to the AAA server so that only packets originating f=
rom legitimate AAA clients can be sent to/from the AAA server.  =20

In addition to these basic security issues=2C the AAA delegation model is m=
uch simpler than Kerberos.  Obtaining a Kerberos TGT for a local realm invo=
lves first obtaining a TGT from a "home" realm and then requesting a TGT fo=
r the local realm.  This involves multiple exchanges=2C and as noted earlie=
r requires both the local KDC and the home KDC to be available over the Int=
ernet.  In contrast=2C a AAA client implicitly delegates authority to the A=
AA server for the Accept/Reject decision=2C so that explicit trust relation=
ships don't need to be configured.  As long as the AAA client can reach the=
 AAA server via a chain of proxies the trust relationship can succeed.=20

Given these basic characteristics of Kerberos and AAA delegation=2C the Moo=
nshot team has decided that a AAA-based approach to delegation is more like=
ly to be widely deployed than a Kerberos-based one.  My take on this is tha=
t this assessment is probably realistic.=20

Where I get lost is making the leap between the AAA delegation model and us=
e of EAP.  As we saw with Digest authentication (RFC 5090)=2C it is possibl=
e to extend AAA to support application-layer authentication without use of =
EAP.  For example=2C using AAA to carry GSS-API payloads would not require =
much more than defining a GSS-Message attribute.  EAP has no unique propert=
ies that make it more suitable for use with AAA.  In fact=2C I would argue =
that the fit between EAP and AAA has always been tenuous at best -- witness=
 the issues encountered in federated EAP authentication that RADSEC has bee=
n needed to address. =20

In particular=2C the problems of EAP auth (e.g. multiple round-trips=2C gen=
eral fragility in federated uses) become highly toxic when applied to Realt=
ime applications such as XMPP and SIP.  As we have learned=2C Digest auth (=
RFC 5090) has not been widely deployed=2C in part because of concern about =
the additional latency added by a AAA exchange.  For users of real-time app=
lications=2C additional latency is a basic=2C non-negotiable goal.  If the =
relatively modest number of exchanges implied by RFC 5090 were intolerable =
in realtime applications=2C  how can we expect EAP exchanges (which can inv=
olve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The a=
nswer unfortunately=2C is that there is no chance at all. =20

So in summary=2C I believe that some aspects of the problem statement make =
sense=2C but that a solution has been chosen prematurely.  The right way to=
 move forward in a situation like this is to begin with a problem statement=
=2C which should include carefully validating the uses cases. =20
 =20

> ----- Original Message -----=20
> From: "Romascanu=2C Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>=3B "radext mailing list" <radiusext@ops.ietf.org>=3B=
=20
> <aaa-doctors@ietf.org>
> Sent: Wednesday=2C June 02=2C 2010 10:56 PM
> Subject: FEDAUTH BOF request
>=20
>=20
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
>=20
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/=2C and more information abou=
t
> this BOF or other BOF requests can be examined  at
> http://trac.tools.ietf.org/bof/trac/
>=20
> Dan
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Let me provide a bit of&nbsp=3B context about what I think the problem is h=
ere. <br><br>As noted by Sam in a previous conversation=2C the basic use ca=
se is "cloud services"=2C where an education institution or enterprise is m=
aking use of hosted services.&nbsp=3B In these situations=2C the institutio=
n may not just want the service provider to host an application=2C but may =
want to keep their credentials local=2C rather than hosting this in the clo=
ud as well. <br><br>In the original Moonshot investigation=2C Kerberos was =
considered as a potential solution.&nbsp=3B However=2C while Kerberos is we=
ll understood from a security point of view=2C and could relatively easily =
be modified to support EAP-based pre-auth (numerous proposals for this have=
 been advanced and in some cases implemented)&nbsp=3B Kerberos federation h=
as not been widely deployed. <br><br>One of the basic problems with putting=
 a KDC on the Internet is that there is no easy way to protect it=2C since =
both clients and other KDCs may need to send packets to and from the KDC.&n=
bsp=3B For this reason if there are roaming clients there is no easy way to=
 filter traffic to/from the KDC.&nbsp=3B In addition=2C the Kerberos protoc=
ol is vulnerable to passive attacks in the absence of extensions such as PK=
INIT or Kerberos Hardening. <br><br>In contrast=2C the AAA roaming model ha=
s been widely deployed=2C in part because it is much easier to protect a AA=
A server.&nbsp=3B AAA servers only talk to AAA clients=2C not to users dire=
ctly.&nbsp=3B This means that it is typically possible to filter traffic to=
 the AAA server so that only packets originating from legitimate AAA client=
s can be sent to/from the AAA server.&nbsp=3B&nbsp=3B <br><br>In addition t=
o these basic security issues=2C the AAA delegation model is much simpler t=
han Kerberos.&nbsp=3B Obtaining a Kerberos TGT for a local realm involves f=
irst obtaining a TGT from a "home" realm and then requesting a TGT for the =
local realm.&nbsp=3B This involves multiple exchanges=2C and as noted earli=
er requires both the local KDC and the home KDC to be available over the In=
ternet.&nbsp=3B In contrast=2C a AAA client implicitly delegates authority =
to the AAA server for the Accept/Reject decision=2C so that explicit trust =
relationships don't need to be configured.&nbsp=3B As long as the AAA clien=
t can reach the AAA server via a chain of proxies the trust relationship ca=
n succeed. <br><br>Given these basic characteristics of Kerberos and AAA de=
legation=2C the Moonshot team has decided that a AAA-based approach to dele=
gation is more likely to be widely deployed than a Kerberos-based one.&nbsp=
=3B My take on this is that this assessment is probably realistic. <br><br>=
Where I get lost is making the leap between the AAA delegation model and us=
e of EAP.&nbsp=3B As we saw with Digest authentication (RFC 5090)=2C it is =
possible to extend AAA to support application-layer authentication without =
use of EAP.&nbsp=3B For example=2C using AAA to carry GSS-API payloads woul=
d not require much more than defining a GSS-Message attribute.&nbsp=3B EAP =
has no unique properties that make it more suitable for use with AAA.&nbsp=
=3B In fact=2C I would argue that the fit between EAP and AAA has always be=
en tenuous at best -- witness the issues encountered in federated EAP authe=
ntication that RADSEC has been needed to address.&nbsp=3B <br><br>In partic=
ular=2C the problems of EAP auth (e.g. multiple round-trips=2C general frag=
ility in federated uses) become highly toxic when applied to Realtime appli=
cations such as XMPP and SIP.&nbsp=3B As we have learned=2C Digest auth (RF=
C 5090) has not been widely deployed=2C in part because of concern about th=
e additional latency added by a AAA exchange.&nbsp=3B For users of real-tim=
e applications=2C additional latency is a basic=2C non-negotiable goal.&nbs=
p=3B If the relatively modest number of exchanges implied by RFC 5090 were =
intolerable in realtime applications=2C&nbsp=3B how can we expect EAP excha=
nges (which can involve 4-5 times the number of roundtrips of RFC 5090) to =
be deployed?&nbsp=3B The answer unfortunately=2C is that there is no chance=
 at all.&nbsp=3B <br><br>So in summary=2C I believe that some aspects of th=
e problem statement make sense=2C but that a solution has been chosen prema=
turely.&nbsp=3B The right way to move forward in a situation like this is t=
o begin with a problem statement=2C which should include carefully validati=
ng the uses cases.&nbsp=3B <br>&nbsp=3B <br><br>&gt=3B ----- Original Messa=
ge ----- <br>&gt=3B From: "Romascanu=2C Dan (Dan)" &lt=3Bdromasca@avaya.com=
&gt=3B<br>&gt=3B To: &lt=3Bdime@ietf.org&gt=3B=3B "radext mailing list" &lt=
=3Bradiusext@ops.ietf.org&gt=3B=3B <br>&gt=3B &lt=3Baaa-doctors@ietf.org&gt=
=3B<br>&gt=3B Sent: Wednesday=2C June 02=2C 2010 10:56 PM<br>&gt=3B Subject=
: FEDAUTH BOF request<br>&gt=3B <br>&gt=3B <br>&gt=3B Diameter and RADIUS e=
xperts should pay attention to the request to hold<br>&gt=3B a Federated Au=
thentication (FEDAUTH) BOF which will be discussed this<br>&gt=3B morning b=
y the IAB and the IESG.<br>&gt=3B <br>&gt=3B The Draft Charter is available=
 at<br>&gt=3B http://www.project-moonshot.org/bof/charter/=2C and more info=
rmation about<br>&gt=3B this BOF or other BOF requests can be examined  at<=
br>&gt=3B http://trac.tools.ietf.org/bof/trac/<br>&gt=3B <br>&gt=3B Dan<br>=
&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscribe send a message to radiusext-r=
equest@ops.ietf.org with<br>&gt=3B the word 'unsubscribe' in a single line =
as the message text body.<br>&gt=3B archive: &lt=3Bhttp://psg.com/lists/rad=
iusext/&gt=3B<br>&gt=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&gt=3B to un=
subscribe send a message to radiusext-request@ops.ietf.org with<br>&gt=3B t=
he word 'unsubscribe' in a single line as the message text body.<br>&gt=3B =
archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 02:09:35 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C62428C0F3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 02:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhFQrIEPMf5Q for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 02:09:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DF2C93A6867 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 02:09:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK6K5-0008v3-Vw for radiusext-data0@psg.com; Thu, 03 Jun 2010 09:02:45 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OK6K0-0008s9-2a for radiusext@ops.ietf.org; Thu, 03 Jun 2010 09:02:40 +0000
Received: from wlan78-40.tnc2010.litnet.lt (wlan78-40.tnc2010.litnet.lt [158.129.78.40]) by liberty.deployingradius.com (Postfix) with ESMTPSA id 497FA12343B5; Thu,  3 Jun 2010 10:58:29 +0200 (CEST)
Message-ID: <4C076FAB.2070001@deployingradius.com>
Date: Thu, 03 Jun 2010 11:02:35 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Avi review of I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com>
In-Reply-To: <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> Section 1.2
> 
> Issue 1:
> Special language is provided for "MUST" "MUST-NOT"  do we need to state the same for "SHALL" and "SHALL-NOT"?  I am not sure because I haven't checked.  

  It is not necessary.  The special language for "MUST" and "MUST NOT"
is there because there were concerns that the document didn't state
clearly enough that it had no new normative requirements on RADIUS.

  i.e. that text is explanatory, and has no meaning other than to
clarify the role of the document for the reader.  The normal RFC 2119
meanings of those words are unchanged.

> Section 1.3.1
> 
> Issue 2:
> "We do not forbid these specifications, but it is
>    RECOMMENDED that they are created only if they have a limited scope
>    of applicability, and all new attributes defined in those
>    specifications are VSAs."
> 
> What is meant by "limited scope of applicability"?  Is it limited scope of applicability within the SDO?  I would think not.  It is already stated in this section that - SDO can design for their own purposes in several places in this section:

  The "limited scope of applicability" is explained in the following
paragraph, which references Sections 3.3.2 and 3.3.3.

>  "By
>    articulating guidelines for RADIUS attribute design, this document
>    enables SDOs out of the IETF to design their own RADIUS attributes
>    within the Vendor-Specific Attribute (VSA) space."
> 
> Is "limited scope of applicability" over and above that?  The basic problem is that we have lots of text that is repeating in this section.

  The limited scope of applicability is explained in detail.  It's
difficult to solve the problem of not explaining in enough detail what
it means, and simultaneously having too much explanatory text in the
document.

> I disagree that:
> 
>  * use only the "basic data types" (see below) for all VSAs;
> 
> Please delete that.  Since the next bullet 
> 
> Actually, the last bullet suffices:
> 
>   * follow the guidelines given in this document.
>
> I suggest getting rid of the bullets and just state:
> 
>  It is RECOMMENDED that SDOs and vendors seek review of RADIUS
>    attribute specifications from the IETF.  However, specifications do
>    not require IETF review when they follow the guidelines given this document.

  The checklist gives a simple and unambiguous definition for when IETF
reviews are needed.  As the rest of the document has been deemed long
and repetitive, a short checklist should be useful.  An SDO wanting to
know if they require an IETF review needs only read a short checklist,
rather than a long and exhausting document.

> Issue: 4:
> 
> Section 2.1
> 
> Change:
> 
>  All other data formats are defined to be "complex data types", and
>    are NOT RECOMMENDED for normal use.  Nested attributes, or attributes
>    grouped via methods other than defined in [RFC2868] do not qualify as
>    "basic data types", and SHOULD NOT be used.
> 
> To
>  All other data formats are defined to be "complex data types", and
>    are NOT RECOMMENDED for normal use including nested attributes, or attributes
>    grouped via methods other than defined in [RFC2868].
>
> I think the document asserts already that complex data types should not be used.

  The following paragraph qualifies the above statement with an
explanation as to why complex types are sometimes necessary.  Removing
the recommendation means that the flow and logic of the document would
be broken.

> Issue 5:
> 
> Section 2.2
> 
> The following text does not make sense:
> 
> " Vendors therefore SHOULD NOT use multiple
>    formats for VSAs that are associated with a particular Vendor Id.  A
>    vendor wishing to use multiple VSA formats SHOULD request one Vendor
>    Id for each VSA format that they will use."
> 
> If a vendor defines two VSAs one of a basic type and another of a non-basic type they should not require a new vendor id.  Please delete this recommendation.

  It is intended to refer to the "TLV encoding scheme", i.e. RFC 2865
Section 5.26 encoding of {8-bit type, 8-bit length, data}, versus (e.g.)
the USR encoding of {32-bit type, data}.

  I suggest changing the text to clarify this, by saying:

--
All VSA encodings that do not follow the [RFC2865] Section 5.26 scheme
are NOT RECOMMENDED.  Although [RFC2865] does not mandate
it, implementations commonly assume that the Vendor Id can be used as
a key to determine the on-the-wire encoding of a VSA.  Vendors
therefore SHOULD NOT use multiple encodings for VSAs that are
associated with a particular Vendor Id.  A vendor wishing to use
multiple VSA encodings SHOULD request one Vendor Id for each VSA
encoding that they will use.
---

  This uses terminology which is in line with RFC 2865.  I will also
review the document, and ensure that discussion about TLVs uses
"encoding", rather than "format", for consistency and clarity.

> Issue 6:
>  Section 3.2
> 
> " These approaches are often incompatible, leading to
>    additional complexity in RADIUS implementations."
> 
> But they dont have to be compatible.

  The above text is in a section titled "Rationale", i.e. motivation for
the document.  Motivation includes explanations of why bad things are bad.

> Get rid of that statement.

  If everyone had done "the right thing" for RADIUS design, there would
have been no need for the guidelines document.  Unfortunately, that is
not the case, and the rationale for the document should be explained.

> Issue 7:
> 
> Section 3.3.3:
> Is repeating text in previous sections: 1.3.1
> 
> The level of repetition in this document is very high. Points are stated and restated and restated.  It is very exhausting to read.

  The repetition is a the result of a gradual exposition of ideas.
First, a short introduction.  Second, a set of recommendations.  Third,
a detailed rationale for the recommendations.

  When the recommendations and rational were placed side by side, the
feedback was that the document was too complex, and the text should be
separated.  We cannot, unfortunately go back to the previous layout as
it has already been judged to be inappropriate.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 03:55:59 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CF013A6983 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 03:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5sJECt5frmv for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 03:55:58 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E346C3A6921 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 03:55:57 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK81s-0001oB-QI for radiusext-data0@psg.com; Thu, 03 Jun 2010 10:52:04 +0000
Received: from [216.82.249.131] (helo=mail28.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OK81q-0001nh-Ek for radiusext@ops.ietf.org; Thu, 03 Jun 2010 10:52:02 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-11.tower-28.messagelabs.com!1275562319!64005925!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 4918 invoked from network); 3 Jun 2010 10:52:00 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-11.tower-28.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2010 10:52:00 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Thu, 3 Jun 2010 06:51:59 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 06:51:58 -0400
Subject: Re: Issue 5 : Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: Issue 5 : Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDCsoJzdWK+l/ISEeC5YmuoGR+QQ==
Message-ID: <C8B8FF50-333F-44BE-9CAE-01062C983F88@bridgewatersystems.com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com>
In-Reply-To: <4C076FAB.2070001@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>> Issue 5:
>>=20
>> Section 2.2
>>=20
>> The following text does not make sense:
>>=20
>> " Vendors therefore SHOULD NOT use multiple
>>   formats for VSAs that are associated with a particular Vendor Id.  A
>>   vendor wishing to use multiple VSA formats SHOULD request one Vendor
>>   Id for each VSA format that they will use."
>>=20
>> If a vendor defines two VSAs one of a basic type and another of a non-ba=
sic type they should not require a new vendor id.  Please delete this recom=
mendation.
>=20
>  It is intended to refer to the "TLV encoding scheme", i.e. RFC 2865
> Section 5.26 encoding of {8-bit type, 8-bit length, data}, versus (e.g.)
> the USR encoding of {32-bit type, data}.
>=20
>  I suggest changing the text to clarify this, by saying:
>=20
> --
> All VSA encodings that do not follow the [RFC2865] Section 5.26 scheme
> are NOT RECOMMENDED.  Although [RFC2865] does not mandate
> it, implementations commonly assume that the Vendor Id can be used as
> a key to determine the on-the-wire encoding of a VSA.  Vendors
> therefore SHOULD NOT use multiple encodings for VSAs that are
> associated with a particular Vendor Id.  A vendor wishing to use
> multiple VSA encodings SHOULD request one Vendor Id for each VSA
> encoding that they will use.
> ---
>=20
>  This uses terminology which is in line with RFC 2865.  I will also
> review the document, and ensure that discussion about TLVs uses
> "encoding", rather than "format", for consistency and clarity.

Okay.  Perhaps giving an example of what is meant by encoding otherwise thi=
s may be confused with formatting.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 04:01:13 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31C753A69B4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 04:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.577
X-Spam-Level: 
X-Spam-Status: No, score=-3.577 tagged_above=-999 required=5 tests=[AWL=0.918, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQsUofGWWHww for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 04:01:09 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1A71D3A69AE for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 04:01:09 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK88k-00033I-2c for radiusext-data0@psg.com; Thu, 03 Jun 2010 10:59:10 +0000
Received: from [216.82.241.99] (helo=mail51.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OK88h-00032s-1l for radiusext@ops.ietf.org; Thu, 03 Jun 2010 10:59:07 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-2.tower-51.messagelabs.com!1275562745!71766704!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 8061 invoked from network); 3 Jun 2010 10:59:05 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-2.tower-51.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2010 10:59:05 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Thu, 3 Jun 2010 06:59:05 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 06:59:05 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDC8hahyMkKCH7TrC10fwRm0qBzA==
Message-ID: <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com>
In-Reply-To: <4C076FAB.2070001@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On 03-06-2010, at 05:02 , Alan DeKok wrote:

>>=20
>> Issue 6:
>> Section 3.2
>>=20
>> " These approaches are often incompatible, leading to
>>   additional complexity in RADIUS implementations."
>>=20
>> But they dont have to be compatible.
>=20
>  The above text is in a section titled "Rationale", i.e. motivation for
> the document.  Motivation includes explanations of why bad things are bad=
.
>=20
>> Get rid of that statement.
>=20
>  If everyone had done "the right thing" for RADIUS design, there would
> have been no need for the guidelines document.  Unfortunately, that is
> not the case, and the rationale for the document should be explained.

The above states that the approach taken by SDOs when working on their attr=
ibutes was incompatible - but as the document asserts SDOs dont have to be =
compatible with other SDOs.

Just say:

These approaches lead to additional complexity in RADIUS implementations.

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 05:54:57 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59EBB3A67FE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 05:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f+uFLuVKVG29 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 05:54:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2F7963A67D7 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 05:54:56 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OK9u2-000LcD-GC for radiusext-data0@psg.com; Thu, 03 Jun 2010 12:52:06 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OK9tz-000Lbk-R1 for radiusext@ops.ietf.org; Thu, 03 Jun 2010 12:52:04 +0000
Message-ID: <4C07A571.6040004@deployingradius.com>
Date: Thu, 03 Jun 2010 14:52:01 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com>
In-Reply-To: <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>>> " These approaches are often incompatible, leading to
>>>   additional complexity in RADIUS implementations."
>
> The above states that the approach taken by SDOs when working on their attributes was incompatible - but as the document asserts SDOs dont have to be compatible with other SDOs.

  No, it does not.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 06:38:28 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2BE53A67D1 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 06:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.664
X-Spam-Level: 
X-Spam-Status: No, score=-100.664 tagged_above=-999 required=5 tests=[AWL=-0.664, BAYES_50=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kS1fcQLDoCAt for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 06:38:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DAE8828C162 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 06:38:24 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKAa8-0003dX-JP for radiusext-data0@psg.com; Thu, 03 Jun 2010 13:35:36 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OKAa6-0003cn-4P for radiusext@ops.ietf.org; Thu, 03 Jun 2010 13:35:34 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.71) (envelope-from <trac@tools.ietf.org>) id 1OKAa3-0006gH-8r; Thu, 03 Jun 2010 06:35:31 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: wdec@cisco.com
X-Trac-Project: radext
Date: Thu, 03 Jun 2010 13:35:31 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #2: comments on draft-ietf-radext-ipv6-access-01
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/2#comment:1
Message-ID: <073.45ee5b4e5cc2640cee95be39b075a65b@tools.ietf.org>
References: <064.0440af090a5dac555f69c650b81696c8@tools.ietf.org>
X-Trac-Ticket-ID: 2
In-Reply-To: <064.0440af090a5dac555f69c650b81696c8@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: wdec@cisco.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#2: comments on draft-ietf-radext-ipv6-access-01
-------------------------------------+--------------------------------------
 Reporter:  msmith@…                 |       Owner:  wdec@…        
     Type:  defect                   |      Status:  assigned      
 Priority:  major                    |   Milestone:  milestone1    
Component:  ipv6-access              |     Version:  1.0           
 Severity:  In WG Last Call          |    Keywords:                
-------------------------------------+--------------------------------------
Changes (by wdec@…):

  * status:  new => assigned


Comment:

 Sorry for not replying earlier, just came across this ticket...

 There are actually a number of issues pointed out, which I'll address one
 by one:

 1. Deployment Scenarios
 Partially accepted: Propose changing RG host to RG or host. In practically
 all deployments, the RG looks/talks like a host on its WAN interface, so
 the distinction is subtle (and one that continues to be discussed over).
 In terms of the diagram and terminology, while it may be BBF specific,
 there really is no other open standard architecture to refer to. So
 instead of coining new phrases, or adding options like AN or eQAM or
 Switch, etc, leaving things as they are would seem best.

 2. The existing use of prefix with IID is, as you also note, not very
 pretty. Furthermore it is specific to PPP (IPCPv6). In cases where say
 DHCPv6 is desired to be used for assigning the address, instead of
 splitting up the address between the two existing attributes, the new one
 can be used with a neater effect.

 3. Domain name
 This is a good point, but one that appears to be more general than IPv6
 attributes. I know of VSAs for the domain name, for precisely the purpose
 you give, and it's likely to be applicable to both v4 and v6. Do you see
 need for split domains?

 4. Adding a dhcp server address.
 This is an interesting proposal, but perhaps a bit too specific in terms
 of the set-up where it could be applicable. One of the drivers for this
 draft has been that some operators intend to use Radius to pass some of
 the key attributes to an embedded dhcpv6 server. In the scenario you
 describe, the NAS would effectively either use DHCPv6 to get some config
 for itself, or be a proxy for the client. One gets the impression that
 both of these mechanisms may need to be explored further with dhcpv6
 folks...

 5. What would be your proposal for encoding this without using a complex
 attribute? In some of the past draft iterations, we had pretty much all
 parameters allowed, but this was deemed to contravene existing radius
 practices, so we simplified to the bare minimum.
 Side note: I think that a route preference could very well be a default
 setting which does not need to be exposed via Radius.

 6. Yes, that's fine. We'll try to add it to the draft, unless someone
 objects.

 Thanks,
 Woj.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/2#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 06:57:37 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73CAA3A67B5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 06:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.13
X-Spam-Level: 
X-Spam-Status: No, score=-100.13 tagged_above=-999 required=5 tests=[AWL=0.364, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwmIr7eR2Ovn for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 06:57:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D707D3A67A3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 06:57:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKAsX-0007FY-CH for radiusext-data0@psg.com; Thu, 03 Jun 2010 13:54:37 +0000
Received: from [119.145.14.66] (helo=szxga03-in.huawei.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <tena@huawei.com>) id 1OKAsT-0007Ex-Fr for radiusext@ops.ietf.org; Thu, 03 Jun 2010 13:54:34 +0000
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00FAUYMV7E@szxga03-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 21:54:31 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00FAVYMVER@szxga03-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 21:54:31 +0800 (CST)
Received: from z00147053k ([10.70.39.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3F00F79YMVTB@szxml04-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 21:54:31 +0800 (CST)
Date: Thu, 03 Jun 2010 21:54:28 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: FEDAUTH BOF request
To: dromasca@avaya.com, dime@ietf.org, radiusext@ops.ietf.org, aaa-doctors@ietf.org, Bernard Aboba <bernard_aboba@hotmail.com>
Message-id: <A142425E33AB431C8F6FBF8C10E4594B@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: multipart/alternative; boundary="Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)"
X-Priority: 3
X-MSMail-priority: Normal
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com> <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W350A9D16B24A7A1F9D76F193D10@phx.gbl>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a multi-part message in MIME format.

--Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi Bernard,
Comments are in line.

B. R.
Tina
http://tinatsou.weebly.com/contact.html
  ----- Original Message ----- 
  From: Bernard Aboba 
  To: tena@huawei.com ; aaa-doctors@ietf.org ; radiusext@ops.ietf.org ; dime@ietf.org ; dromasca@avaya.com 
  Sent: Thursday, June 03, 2010 1:03 PM
  Subject: RE: FEDAUTH BOF request


  Tina said: 

  > Comments are below.
  > 1. This might be of interest to ngHLR (Unified Subscriber Center) kind of 
  > solutions who provide Identity Management services
  > 2. From protocol side, I think it may be more interesting for RADIUS as I  doubt the suitability of Diameter for this.

  Not sure why RADIUS would be more suitable than Diameter for carrying large payloads such as SAML assertions.  The 4096 octet RADIUS PDU limit is not transport-specific -- that is, transporting the RADIUS payload over TCP does not solve the problem. 

  [Tina: You are also right from the aspect you raised.
  Diameter roaming model is well established (in use cases like WLAN-3GPP interworking) without the use of EAP or SAML. I fail to see what would be the benefits of using EAP or SAML with Diameter which the current roaming model does not already have.
  Everything has pros and cons, as you said in another email, let's begin with a problem statement, and then protocols.]


   
  > ----- Original Message ----- 
  > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
  > To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
  > <aaa-doctors@ietf.org>
  > Sent: Wednesday, June 02, 2010 10:56 PM
  > Subject: FEDAUTH BOF request
  > 
  > 
  > Diameter and RADIUS experts should pay attention to the request to hold
  > a Federated Authentication (FEDAUTH) BOF which will be discussed this
  > morning by the IAB and the IESG.
  > 
  > The Draft Charter is available at
  > http://www.project-moonshot.org/bof/charter/, and more information about
  > this BOF or other BOF requests can be examined at
  > http://trac.tools.ietf.org/bof/trac/
  > 
  > Dan
  > 
  > --
  > to unsubscribe send a message to radiusext-request@ops.ietf.org with
  > the word 'unsubscribe' in a single line as the message text body.
  > archive: <http://psg.com/lists/radiusext/>
  > 
  > 
  > 
  > --
  > to unsubscribe send a message to radiusext-request@ops.ietf.org with
  > the word 'unsubscribe' in a single line as the message text body.
  > archive: <http://psg.com/lists/radiusext/>

--Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>.hmmessage P {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
	FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>

<META content="MSHTML 6.00.6000.17023" name=GENERATOR></HEAD>
<BODY class=hmmessage bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff>Hi Bernard,</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff>Comments are in line.</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff>B. R.<BR>Tina</FONT><BR><A 
href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=bernard_aboba@hotmail.com 
  href="mailto:bernard_aboba@hotmail.com">Bernard Aboba</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=tena@huawei.com 
  href="mailto:tena@huawei.com">tena@huawei.com</A> ; <A 
  title=aaa-doctors@ietf.org 
  href="mailto:aaa-doctors@ietf.org">aaa-doctors@ietf.org</A> ; <A 
  title=radiusext@ops.ietf.org 
  href="mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</A> ; <A 
  title=dime@ietf.org href="mailto:dime@ietf.org">dime@ietf.org</A> ; <A 
  title=dromasca@avaya.com 
  href="mailto:dromasca@avaya.com">dromasca@avaya.com</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, June 03, 2010 1:03 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: FEDAUTH BOF request</DIV>
  <DIV><BR></DIV>
  <DIV>Tina said: <BR><BR>&gt; Comments are below.<BR>&gt; 1. This might be of 
  interest to ngHLR (Unified Subscriber Center) kind of <BR>&gt; solutions who 
  provide Identity Management services<BR>&gt; 2. From protocol side, I think it 
  may be more interesting for RADIUS as I&nbsp; doubt the suitability of 
  Diameter for this.<BR><BR>Not sure why RADIUS would be more suitable than 
  Diameter for carrying large payloads such as SAML assertions.&nbsp; The 4096 
  octet RADIUS PDU limit is not transport-specific -- that is, transporting the 
  RADIUS payload over TCP does not solve the problem.&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff>[Tina: You are also right from the aspect 
  you&nbsp;raised.</FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff>Diameter roaming model is well established 
  (in use cases like WLAN-3GPP interworking) without the use of EAP or SAML. I 
  fail to see what would be the benefits of using EAP or SAML with Diameter 
  which the current roaming model does not already have.</FONT></DIV>
  <DIV><FONT face=Arial><FONT color=#0000ff>Everything has pros and cons, as you 
  said in another email, let's begin with a problem statement, and then 
  protocols.]</FONT><BR></FONT><BR><BR>&nbsp;<BR>&gt; ----- Original Message 
  ----- <BR>&gt; From: "Romascanu, Dan (Dan)" &lt;dromasca@avaya.com&gt;<BR>&gt; 
  To: &lt;dime@ietf.org&gt;; "radext mailing list" 
  &lt;radiusext@ops.ietf.org&gt;; <BR>&gt; &lt;aaa-doctors@ietf.org&gt;<BR>&gt; 
  Sent: Wednesday, June 02, 2010 10:56 PM<BR>&gt; Subject: FEDAUTH BOF 
  request<BR>&gt; <BR>&gt; <BR>&gt; Diameter and RADIUS experts should pay 
  attention to the request to hold<BR>&gt; a Federated Authentication (FEDAUTH) 
  BOF which will be discussed this<BR>&gt; morning by the IAB and the 
  IESG.<BR>&gt; <BR>&gt; The Draft Charter is available at<BR>&gt; 
  http://www.project-moonshot.org/bof/charter/, and more information 
  about<BR>&gt; this BOF or other BOF requests can be examined at<BR>&gt; 
  http://trac.tools.ietf.org/bof/trac/<BR>&gt; <BR>&gt; Dan<BR>&gt; <BR>&gt; 
  --<BR>&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org 
  with<BR>&gt; the word 'unsubscribe' in a single line as the message text 
  body.<BR>&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<BR>&gt; 
  <BR>&gt; <BR>&gt; <BR>&gt; --<BR>&gt; to unsubscribe send a message to 
  radiusext-request@ops.ietf.org with<BR>&gt; the word 'unsubscribe' in a single 
  line as the message text body.<BR>&gt; archive: 
  &lt;http://psg.com/lists/radiusext/&gt;<BR></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 07:02:34 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 416D53A67A3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 07:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.252
X-Spam-Level: 
X-Spam-Status: No, score=-100.252 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jR82XVaZZYnU for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 07:02:29 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4508A3A67D1 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 07:02:29 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKAvv-0007yX-7F for radiusext-data0@psg.com; Thu, 03 Jun 2010 13:58:07 +0000
Received: from [119.145.14.67] (helo=szxga05-in.huawei.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <tena@huawei.com>) id 1OKAvr-0007xS-01 for radiusext@ops.ietf.org; Thu, 03 Jun 2010 13:58:03 +0000
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F001IWYSPR1@szxga05-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 21:58:01 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00KO8YSO2V@szxga05-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 21:58:00 +0800 (CST)
Received: from z00147053k ([10.70.39.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3F00FSMYSMTB@szxml04-in.huawei.com> for radiusext@ops.ietf.org; Thu, 03 Jun 2010 21:58:00 +0800 (CST)
Date: Thu, 03 Jun 2010 21:57:56 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: [Dime] FEDAUTH BOF request
To: dromasca@avaya.com, dime@ietf.org, radiusext@ops.ietf.org, aaa-doctors@ietf.org, Wolfgang.Steigerwald@telekom.de, "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Message-id: <87BAC297AD614E1E8E885DA28CA60DD2@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=ISO-8859-1; reply-type=original
Content-transfer-encoding: 8BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com> <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <F30237DE0DEB964C89C4D3A3473B46E506EC37DB@S4DE9JSAAII.ost.t-com.de> <3D3C75174CB95F42AD6BCC56E5555B4502A8093D@FIESEXC015.nsn-intra.net>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi Wolfgang and Hannes,
You are also right from the good nature of Diameter.
I just mentioned one possible interesting point in my previous email 
replying to Bernard et al.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message ----- 
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: <Wolfgang.Steigerwald@telekom.de>; <tena@huawei.com>; 
<aaa-doctors@ietf.org>; <radiusext@ops.ietf.org>; <dime@ietf.org>; 
<dromasca@avaya.com>
Sent: Thursday, June 03, 2010 3:18 PM
Subject: RE: [Dime] FEDAUTH BOF request


Looking forward to hear that answer as well :-)

>-----Original Message-----
>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On
>Behalf Of ext Wolfgang.Steigerwald@telekom.de
>Sent: 03 June, 2010 10:16
>To: tena@huawei.com; aaa-doctors@ietf.org;
>radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
>Subject: Re: [Dime] FEDAUTH BOF request
>
>Hello Tina,
>
>what assumption let you think RADIUS is more suitable then
>DIAMETER? DIAMETER is much more developed, is a peer to peer
>protocol, designed to transport also structured data, not as
>limited on payload and therefore much better suitable for the
>purpose of IdM.
>
>Best Regards
>
> Wolfgang
>
>-----Ursprüngliche Nachricht-----
>Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im
>Auftrag von Tina TSOU
>Gesendet: Donnerstag, 3. Juni 2010 06:03
>An: aaa-doctors@ietf.org; radext mailing list; dime@ietf.org;
>Romascanu, Dan (Dan)
>Betreff: Re: [Dime] FEDAUTH BOF request
>
>Comments are below.
>1. This might be of interest to ngHLR (Unified Subscriber
>Center) kind of solutions who provide Identity Management
>services 2. From protocol side, I think it may be more
>interesting for RADIUS as I doubt the suitability of Diameter for this.
>
>B. R.
>Tina
>http://tinatsou.weebly.com/contact.html
>
>----- Original Message -----
>From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>To: <dime@ietf.org>; "radext mailing list"
><radiusext@ops.ietf.org>; <aaa-doctors@ietf.org>
>Sent: Wednesday, June 02, 2010 10:56 PM
>Subject: FEDAUTH BOF request
>
>
>Diameter and RADIUS experts should pay attention to the
>request to hold a Federated Authentication (FEDAUTH) BOF which
>will be discussed this morning by the IAB and the IESG.
>
>The Draft Charter is available at
>http://www.project-moonshot.org/bof/charter/, and more
>information about this BOF or other BOF requests can be
>examined  at http://trac.tools.ietf.org/bof/trac/
>
>Dan
>
>--
>to unsubscribe send a message to
>radiusext-request@ops.ietf.org with the word 'unsubscribe' in
>a single line as the message text body.
>archive: <http://psg.com/lists/radiusext/>
>
>
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 10:57:57 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C62928C0F7 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 10:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.806
X-Spam-Level: 
X-Spam-Status: No, score=-3.806 tagged_above=-999 required=5 tests=[AWL=0.689, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id huuMbbba9BQA for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 10:57:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D494A3A689F for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 10:57:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKEas-000PG5-T9 for radiusext-data0@psg.com; Thu, 03 Jun 2010 17:52:38 +0000
Received: from [216.82.249.147] (helo=mail29.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OKEap-000PFi-Vh for radiusext@ops.ietf.org; Thu, 03 Jun 2010 17:52:36 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-6.tower-29.messagelabs.com!1275587531!56744318!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 25071 invoked from network); 3 Jun 2010 17:52:12 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-6.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 3 Jun 2010 17:52:12 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Thu, 3 Jun 2010 13:52:11 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 13:52:10 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDRX1uXyb1FZE9TTGWUIOYHSSH5A==
Message-ID: <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <4C07A571.6040004@deployingradius.com>
In-Reply-To: <4C07A571.6040004@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

With which do you disagree when you say "No, it does not."
a) The above states that the approach taken by SDOs when working on their a=
ttributes was incompatible.
b) but as the document asserts SDOs dont have to be compatible with other S=
DOs.
c) Both of these statements

???


On 03-06-2010, at 08:52 , Alan DeKok wrote:

>>>> " These approaches are often incompatible, leading to
>>>>  additional complexity in RADIUS implementations."
>>=20
>> The above states that the approach taken by SDOs when working on their a=
ttributes was incompatible - but as the document asserts SDOs dont have to =
be compatible with other SDOs.
>=20
>  No, it does not.
>=20
>  Alan DeKok.

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 13:03:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 628103A6A37 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 13:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvgYXFmKODOV for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 13:03:24 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6F8383A6A38 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 13:03:19 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKGb1-000LAD-SX for radiusext-data0@psg.com; Thu, 03 Jun 2010 20:00:55 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OKGay-000L9J-QM for radiusext@ops.ietf.org; Thu, 03 Jun 2010 20:00:52 +0000
Message-ID: <4C0809E7.2050103@deployingradius.com>
Date: Thu, 03 Jun 2010 22:00:39 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <4C07A571.6040004@deployingradius.com> <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com>
In-Reply-To: <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> With which do you disagree when you say "No, it does not."

  It's a rather straightforward reading of the message:

You: ... the document asserts SDOs dont have to be compatible
       with other SDOs.

Me:  No, it does not.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 13:59:19 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8883F3A6A35 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 13:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLZG7egswapF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 13:59:18 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6188E3A68CE for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 13:59:18 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKHPs-0003jx-Cs for radiusext-data0@psg.com; Thu, 03 Jun 2010 20:53:28 +0000
Received: from [207.3.149.133] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1OKHPp-0003iL-ES for radiusext@ops.ietf.org; Thu, 03 Jun 2010 20:53:25 +0000
Received: (qmail 10789 invoked from network); 3 Jun 2010 20:53:24 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 3 Jun 2010 20:53:24 -0000
Message-Id: <5D6B078F-C7EC-4646-AEF8-F86D1582075C@elbrysnetworks.com>
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: radext mailing list <radiusext@ops.ietf.org>
In-Reply-To: <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Date: Thu, 3 Jun 2010 16:53:23 -0400
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com>
X-Mailer: Apple Mail (2.936)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

My thinking on the applicability of design guidelines has always been  
pretty simple.  It starts with the premise that any Standards  
Development Organization (SDO) is in the business of defining  
interoperable standards.  If we can't all agree that this is a truism,  
we have deeper problems.  Within that framework, the notion that what  
one SDO does will never impact any other SDO or the Internet Community  
at large is questionable.  It may be true sometimes, but I don't  
believe it's universally true.

Within the scope of RADIUS Attribute design and compatibility, I think  
there are three levels:

(1)  Attributes that are of interest to a single vendor, e.g., for a  
single product line.  No cross-vendor interoperability is needed.

We use Vendor-Specific Attributes for these cases.  The rules are  
pretty lax.  Code-point allocation is managed by the vendor with the  
number space defined by their Private Enterprise Number (PEN).


(2) Attributes that are  of interest to an industry segment and a  
single SDO that serves that industry.  WiMAX is one example.  Multi- 
vendor interoperability within an industry segment is expected.

We use SDO-Specific Attributes (SSA) for these cases, which are VSAs  
in terms of format and code-point allocation, using a PEN assigned to  
the SDO rather than one assigned to an individual vendor.  The rules  
are more stringent.  Compliance with the design guidelines is strongly  
encouraged, but review by outside agencies (the IETF, AAA Doctors,  
etc.) is purely optional.


(3)  Attributes that are of broad interest to the Internet Community.   
Global Internet multi-vendor interoperability is expected.

We use Standard Attributes for these cases, with code-point allocation  
via IANA, subject to the appropriate IETF review and consensus.   
Strict conformance with the design guidelines is expected, unless a  
good case can be made for an exception, and those tasked with  
reviewing the proposals will almost certainly use the design  
guidelines as a review checklist.






--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 20:02:09 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B82443A6862 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 20:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.944
X-Spam-Level: 
X-Spam-Status: No, score=-3.944 tagged_above=-999 required=5 tests=[AWL=0.551, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlZlxha3sI-7 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 20:02:08 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A27DE3A6782 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 20:02:08 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKN59-000FXf-0P for radiusext-data0@psg.com; Fri, 04 Jun 2010 02:56:27 +0000
Received: from [216.82.254.195] (helo=mail200.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OKN53-000FV9-0I for radiusext@ops.ietf.org; Fri, 04 Jun 2010 02:56:21 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-12.tower-200.messagelabs.com!1275620179!55205253!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 12279 invoked from network); 4 Jun 2010 02:56:19 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-12.tower-200.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jun 2010 02:56:19 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Thu, 3 Jun 2010 22:56:18 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 22:56:17 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDkYDaxxjjrOmcRSyigdxKL8mwYA==
Message-ID: <DDD4FA4C-B08E-43AD-9A11-38B0B38C43DB@bridgewatersystems.com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <4C07A571.6040004@deployingradius.com> <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com> <4C0809E7.2050103@deployingradius.com>
In-Reply-To: <4C0809E7.2050103@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Read this:

Section 1.3 ....

 While SDOs and vendors MAY choose to create specifications not
   following these guidelines, this should be done only when those
   specifications are intended for use in scenarios within a limited
   scope of applicability.  Where general usage is possible, adhering to
   these guidelines is RECOMMENDED.

Unless i am missing something  -- the above states that they dont have to b=
e compatible.



On 03-06-2010, at 16:00 , Alan DeKok wrote:

> Avi Lior wrote:
>> With which do you disagree when you say "No, it does not."
>=20
>  It's a rather straightforward reading of the message:
>=20
> You: ... the document asserts SDOs dont have to be compatible
>       with other SDOs.
>=20
> Me:  No, it does not.
>=20
>  Alan DeKok.

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun  3 22:11:29 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D1FF3A6925 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 22:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.712
X-Spam-Level: 
X-Spam-Status: No, score=0.712 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CX20u9JF58mi for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  3 Jun 2010 22:11:24 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 239843A690F for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  3 Jun 2010 22:11:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKP7l-0003Xu-9J for radiusext-data0@psg.com; Fri, 04 Jun 2010 05:07:17 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OKP7i-0003XS-NT for radiusext@ops.ietf.org; Fri, 04 Jun 2010 05:07:14 +0000
Message-ID: <4C0889FD.1010703@deployingradius.com>
Date: Fri, 04 Jun 2010 07:07:09 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <4C07A571.6040004@deployingradius.com> <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com> <4C0809E7.2050103@deployingradius.com> <DDD4FA4C-B08E-43AD-9A11-38B0B38C43DB@bridgewatersystems.com>
In-Reply-To: <DDD4FA4C-B08E-43AD-9A11-38B0B38C43DB@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> Section 1.3 ....
> 
>  While SDOs and vendors MAY choose to create specifications not
>    following these guidelines, this should be done only when those
>    specifications are intended for use in scenarios within a limited
>    scope of applicability.  Where general usage is possible, adhering to
>    these guidelines is RECOMMENDED.
> 
> Unless i am missing something  -- the above states that they dont have to be compatible.

  No, it does not.  The word "compatible" does not appear in that text.
 I have no idea what you mean by "compatible".  That word could mean
almost anything.

  Two SDOs may choose to ignore the guidelines, but may still both be
"compatible", or they may not be "compatible".  The document does not
distinguish between those two scenarios.

>>... the document asserts SDOs dont have to be compatible
>>       with other SDOs.

  The only usage of "compatible" in the document is via the word
"incompatible", as in:

	... different groups taking different approaches.
	These approaches are often incompatible, leading to
	additional complexity

  The document suggests that incompatibility is a problem to be avoided.
 You assert that the document says the exact opposite.

  I repeat my objection: No, it doesn't.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Fri Jun  4 00:21:38 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4837928C127 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 00:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.837
X-Spam-Level: 
X-Spam-Status: No, score=0.837 tagged_above=-999 required=5 tests=[AWL=-0.527, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xEIcVXsl4LG8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 00:21:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 40FD53A6A26 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  4 Jun 2010 00:21:37 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKR7m-000JRd-FJ for radiusext-data0@psg.com; Fri, 04 Jun 2010 07:15:26 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OKR7k-000JQW-1P for radiusext@ops.ietf.org; Fri, 04 Jun 2010 07:15:24 +0000
Message-ID: <4C08A807.3000509@deployingradius.com>
Date: Fri, 04 Jun 2010 09:15:19 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: radext mailing list <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <5D6B078F-C7EC-4646-AEF8-F86D1582075C@elbrysnetworks.com>
In-Reply-To: <5D6B078F-C7EC-4646-AEF8-F86D1582075C@elbrysnetworks.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson wrote:
> My thinking on the applicability of design guidelines has always been
> pretty simple.

  While I agree, discussion shows that isn't a uniformly held opinion.

> Within the scope of RADIUS Attribute design and compatibility, I think
> there are three levels:

  If it's all right, I'll wordsmith that and put it into the introduction.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Fri Jun  4 00:35:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE42E3A657C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 00:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.532
X-Spam-Level: **
X-Spam-Status: No, score=2.532 tagged_above=-999 required=5 tests=[AWL=-1.081, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.449, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTO09IcWqSgl for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 00:35:20 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E209F3A67DB for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  4 Jun 2010 00:35:18 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKRNV-000LoA-0p for radiusext-data0@psg.com; Fri, 04 Jun 2010 07:31:41 +0000
Received: from [74.208.4.195] (helo=mout.perfora.net) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <alper.yegin@yegin.org>) id 1OKRNQ-000LnR-OL for radiusext@ops.ietf.org; Fri, 04 Jun 2010 07:31:36 +0000
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MY7Qm-1OpI2f3O8u-00VID5; Fri, 04 Jun 2010 03:31:26 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Bernard Aboba'" <bernard_aboba@hotmail.com>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>,	<F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
In-Reply-To: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
Subject: RE: [Dime] FEDAUTH BOF request
Date: Fri, 4 Jun 2010 10:30:58 +0300
Message-ID: <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A0_01CB03D1.0B8D02F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsC3Vu3xwQsiPtKT8+vfB1gbF+XiAA2UOhg
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX18y1cDDDbHwzc0rK+re1041lchS1Dg/3U9B3ek zrDOUvkjOhWErTfZBgfmWbJCOxwOu3DJT47CFQbCimRLqJVL6u OOecGjtXfoBXG9HHEBhW97gRdtYxZyP
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a multipart message in MIME format.

------=_NextPart_000_01A0_01CB03D1.0B8D02F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


In particular, the problems of EAP auth (e.g. multiple round-trips, general
fragility in federated uses) become highly toxic when applied to Realtime
applications such as XMPP and SIP.  As we have learned, Digest auth (RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.  For users of real-time
applications, additional latency is a basic, non-negotiable goal.  If the
relatively modest number of exchanges implied by RFC 5090 were intolerable
in realtime applications,  how can we expect EAP exchanges (which can
involve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The
answer unfortunately, is that there is no chance at all.  

So in summary, I believe that some aspects of the problem statement make
sense, but that a solution has been chosen prematurely.  The right way to
move forward in a situation like this is to begin with a problem statement,
which should include carefully validating the uses cases.  



 

 

Alper> I agree. 

 

Alper> Anyone who was around the ICOS BoF in IETF 62 would remember that the
community was convinced(!) that using EAP for anything other than network
access was a no-no. Now before we embark on marching in  180-degree opposite
direction, I'd say the community needs to be "unconvinced" first. I'm not
saying this is not doable, but something we need to go through first.

 

Alper

 

 

  

> ----- Original Message ----- 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
> <aaa-doctors@ietf.org>
> Sent: Wednesday, June 02, 2010 10:56 PM
> Subject: FEDAUTH BOF request
> 
> 
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
> 
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/, and more information about
> this BOF or other BOF requests can be examined at
> http://trac.tools.ietf.org/bof/trac/
> 
> Dan
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> 
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


------=_NextPart_000_01A0_01CB03D1.0B8D02F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
In particular, the problems of EAP auth (e.g. multiple round-trips, =
general
fragility in federated uses) become highly toxic when applied to =
Realtime
applications such as XMPP and SIP.&nbsp; As we have learned, Digest auth =
(RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.&nbsp; For users of real-time
applications, additional latency is a basic, non-negotiable goal.&nbsp; =
If the
relatively modest number of exchanges implied by RFC 5090 were =
intolerable in
realtime applications,&nbsp; how can we expect EAP exchanges (which can =
involve
4-5 times the number of roundtrips of RFC 5090) to be deployed?&nbsp; =
The
answer unfortunately, is that there is no chance at all.&nbsp; <br>
<br>
So in summary, I believe that some aspects of the problem statement make =
sense,
but that a solution has been chosen prematurely.&nbsp; The right way to =
move
forward in a situation like this is to begin with a problem statement, =
which
should include carefully validating the uses cases.&nbsp; <br>
<br>
<span style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; I agree. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; Anyone who was around the ICOS BoF in IETF 62 =
would
remember that the community was convinced(!) that using EAP for anything =
other
than network access was a no-no. Now before we embark on marching in =
&nbsp;180-degree
opposite direction, I&#8217;d say the community needs to be =
&#8220;unconvinced&#8221;
first. I&#8217;m not saying this is not doable, but something we need to =
go
through first.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>&nbsp;
<br>
<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;Romascanu, Dan (Dan)&quot; =
&lt;dromasca@avaya.com&gt;<br>
&gt; To: &lt;dime@ietf.org&gt;; &quot;radext mailing list&quot;
&lt;radiusext@ops.ietf.org&gt;; <br>
&gt; &lt;aaa-doctors@ietf.org&gt;<br>
&gt; Sent: Wednesday, June 02, 2010 10:56 PM<br>
&gt; Subject: FEDAUTH BOF request<br>
&gt; <br>
&gt; <br>
&gt; Diameter and RADIUS experts should pay attention to the request to =
hold<br>
&gt; a Federated Authentication (FEDAUTH) BOF which will be discussed =
this<br>
&gt; morning by the IAB and the IESG.<br>
&gt; <br>
&gt; The Draft Charter is available at<br>
&gt; http://www.project-moonshot.org/bof/charter/, and more information =
about<br>
&gt; this BOF or other BOF requests can be examined at<br>
&gt; http://trac.tools.ietf.org/bof/trac/<br>
&gt; <br>
&gt; Dan<br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: =
&lt;http://psg.com/lists/radiusext/&gt;<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_01A0_01CB03D1.0B8D02F0--



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Fri Jun  4 06:33:40 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23E033A6A37 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 06:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.106
X-Spam-Level: 
X-Spam-Status: No, score=-3.106 tagged_above=-999 required=5 tests=[AWL=-0.470, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dwY9-Q0WrHuc for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 06:33:38 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6046F3A6A66 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  4 Jun 2010 06:33:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKWwV-0002S9-Pa for radiusext-data0@psg.com; Fri, 04 Jun 2010 13:28:11 +0000
Received: from [216.82.249.147] (helo=mail29.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OKWwS-0002RM-RY for radiusext@ops.ietf.org; Fri, 04 Jun 2010 13:28:09 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-14.tower-29.messagelabs.com!1275658086!59693285!2
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 23398 invoked from network); 4 Jun 2010 13:28:07 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-14.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 4 Jun 2010 13:28:07 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Fri, 4 Jun 2010 09:28:06 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Fri, 4 Jun 2010 09:26:54 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsD6cQOQ/rtT0gFQuqV9prjEx5xwg==
Message-ID: <C8AFF4BF-0046-464C-BE14-1C0805E639B0@bridgewatersystems.com>
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <4C07A571.6040004@deployingradius.com> <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com> <4C0809E7.2050103@deployingradius.com> <DDD4FA4C-B08E-43AD-9A11-38B0B38C43DB@bridgewatersystems.com> <4C0889FD.1010703@deployingradius.com>
In-Reply-To: <4C0889FD.1010703@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On 04-06-2010, at 01:07 , Alan DeKok wrote:

> Avi Lior wrote:
>> Section 1.3 ....
>>=20
>> While SDOs and vendors MAY choose to create specifications not
>>   following these guidelines, this should be done only when those
>>   specifications are intended for use in scenarios within a limited
>>   scope of applicability.  Where general usage is possible, adhering to
>>   these guidelines is RECOMMENDED.
>>=20
>> Unless i am missing something  -- the above states that they dont have t=
o be compatible.
>=20
>  No, it does not.  The word "compatible" does not appear in that text.
> I have no idea what you mean by "compatible".  That word could mean
> almost anything.
>=20
>  Two SDOs may choose to ignore the guidelines, but may still both be
> "compatible", or they may not be "compatible".  The document does not
> distinguish between those two scenarios.

In the context of this document and in the context of the specific section =
I was commenting on --  i think it is darn clear what we mean by compatible=
 or incompatible.

In any case....

>  The document suggests that incompatibility is a problem to be avoided.
> You assert that the document says the exact opposite.
>=20
>  I repeat my objection: No, it doesn't.

No i don't assert the opposite.  I am saying the document allows for SDOs t=
o create incompatible specifications.  To repeat what I said with appropria=
te words highlighted:  "the document asserts SDOs DONT HAVE TO BE COMPATIBL=
E."=20

back to the original issue - that is issue 6:

Issue 6: Section 3.2

" These approaches are often incompatible, leading to
  additional complexity in RADIUS implementations."

Just say "These approaches often lead to additional complexity in RADIUS im=
plementations."

I dont see the need to bring incompatibility statement into this paragraph.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Fri Jun  4 06:42:25 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0599428C121 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 06:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.805
X-Spam-Level: 
X-Spam-Status: No, score=0.805 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jmpb6WnLl99U for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 06:42:24 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DB2C428C125 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  4 Jun 2010 06:42:23 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKX6o-0004A8-0r for radiusext-data0@psg.com; Fri, 04 Jun 2010 13:38:50 +0000
Received: from [207.3.149.133] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1OKX6l-00049U-SK for radiusext@ops.ietf.org; Fri, 04 Jun 2010 13:38:48 +0000
Received: (qmail 16381 invoked from network); 4 Jun 2010 13:38:46 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 4 Jun 2010 13:38:46 -0000
Cc: radext mailing list <radiusext@ops.ietf.org>
Message-Id: <B3EB5ED4-2210-4879-A34A-1CC083D69D69@elbrysnetworks.com>
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <4C08A807.3000509@deployingradius.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Date: Fri, 4 Jun 2010 09:38:45 -0400
References: <20100414121503.8200128C281@core3.amsl.com> <4BC5BB10.4080006@deployingradius.com>,<0b1001cadbf4$6631bfc0$32953f40$@com> <BLU137-W3272B8995285C2B99C9DF0930F0@phx.gbl> <4BC875D5.1060802@deployingradius.com> <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com> <4C076FAB.2070001@deployingradius.com> <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com> <5D6B078F-C7EC-4646-AEF8-F86D1582075C@elbrysnetworks.com> <4C08A807.3000509@deployingradius.com>
X-Mailer: Apple Mail (2.936)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Jun 4, 2010, at 3:15 AM, Alan DeKok wrote:

 > If it's all right, I'll wordsmith that and put it into the  
introduction.

Of course.  Anything to help move this document along.




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Fri Jun  4 10:18:15 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8459E3A694C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 10:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.036
X-Spam-Level: 
X-Spam-Status: No, score=-9.036 tagged_above=-999 required=5 tests=[AWL=-0.541, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExMBRwsguz8i for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  4 Jun 2010 10:18:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 14BF43A6934 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  4 Jun 2010 10:18:11 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OKaQb-000FUy-Ky for radiusext-data0@psg.com; Fri, 04 Jun 2010 17:11:29 +0000
Received: from [171.68.10.86] (helo=sj-iport-4.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jsalowey@cisco.com>) id 1OKaQX-000FTv-Pe for radiusext@ops.ietf.org; Fri, 04 Jun 2010 17:11:26 +0000
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEfQCEyrRN+K/2dsb2JhbACeRnGlSJoRgl+COASDSYM5
X-IronPort-AV: E=Sophos;i="4.53,362,1272844800";  d="scan'208";a="139524287"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 04 Jun 2010 17:11:23 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o54HBN6O004272; Fri, 4 Jun 2010 17:11:23 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 4 Jun 2010 10:11:23 -0700
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
Subject: RE: [Dime] FEDAUTH BOF request
Date: Fri, 4 Jun 2010 10:11:22 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE50A9EDD7D@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Dime] FEDAUTH BOF request
Thread-Index: AcsC3V6qlMZy6lk0TKacZwhNYrbcbgBJ7grw
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>,<F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
X-OriginalArrivalTime: 04 Jun 2010 17:11:23.0825 (UTC) FILETIME=[F5ADD210:01CB0408]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

I agree with a lot of what Bernard says below. For better or for worse
EAP is closely associated with AAA.  The fit may be odd in some cases,
but deployments have found success in making it work.  This is why it is
attractive.  I don't think that replacing EAP in AAA with some other
framework, such as GSSAPI, is going to lead to better results.  It is
true that along the way modifications, such as RADSEC, have been
deployed to make things work better.   It is risky to assume that AAA
and EAP can be successfully applied to any arbitrary scenario without a
firm grip on the use cases.  If at the end of the design you end up with
something that is called EAP and AAA, but actually is completely
different you will lose the perceived advantage of building on top of
existing AAA and EAP infrastructure

I'm not as convinced as Bernard that it can't work, but I think there
needs to be a firm understanding of the use cases to determine what is
required to deliver a solution and what changes may be necessary. =20



> -----Original Message-----
> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf
Of
> Bernard Aboba
> Sent: Wednesday, June 02, 2010 10:26 PM
> To: tena@huawei.com; aaa-doctors@ietf.org; radiusext@ops.ietf.org;
> dime@ietf.org; dromasca@avaya.com
> Subject: Re: [Dime] FEDAUTH BOF request
>=20
> Let me provide a bit of  context about what I think the problem is
here.
>=20
> As noted by Sam in a previous conversation, the basic use case is
"cloud
> services", where an education institution or enterprise is making use
of
> hosted services.  In these situations, the institution may not just
want
> the service provider to host an application, but may want to keep
their
> credentials local, rather than hosting this in the cloud as well.
>=20
> In the original Moonshot investigation, Kerberos was considered as a
> potential solution.  However, while Kerberos is well understood from a
> security point of view, and could relatively easily be modified to
support
> EAP-based pre-auth (numerous proposals for this have been advanced and
in
> some cases implemented)  Kerberos federation has not been widely
deployed.
>=20
> One of the basic problems with putting a KDC on the Internet is that
there
> is no easy way to protect it, since both clients and other KDCs may
need
> to send packets to and from the KDC.  For this reason if there are
roaming
> clients there is no easy way to filter traffic to/from the KDC.  In
> addition, the Kerberos protocol is vulnerable to passive attacks in
the
> absence of extensions such as PKINIT or Kerberos Hardening.
>=20
> In contrast, the AAA roaming model has been widely deployed, in part
> because it is much easier to protect a AAA server.  AAA servers only
talk
> to AAA clients, not to users directly.  This means that it is
typically
> possible to filter traffic to the AAA server so that only packets
> originating from legitimate AAA clients can be sent to/from the AAA
> server.
>=20
> In addition to these basic security issues, the AAA delegation model
is
> much simpler than Kerberos.  Obtaining a Kerberos TGT for a local
realm
> involves first obtaining a TGT from a "home" realm and then requesting
a
> TGT for the local realm.  This involves multiple exchanges, and as
noted
> earlier requires both the local KDC and the home KDC to be available
over
> the Internet.  In contrast, a AAA client implicitly delegates
authority to
> the AAA server for the Accept/Reject decision, so that explicit trust
> relationships don't need to be configured.  As long as the AAA client
can
> reach the AAA server via a chain of proxies the trust relationship can
> succeed.
>=20
> Given these basic characteristics of Kerberos and AAA delegation, the
> Moonshot team has decided that a AAA-based approach to delegation is
more
> likely to be widely deployed than a Kerberos-based one.  My take on
this
> is that this assessment is probably realistic.
>=20
> Where I get lost is making the leap between the AAA delegation model
and
> use of EAP.  As we saw with Digest authentication (RFC 5090), it is
> possible to extend AAA to support application-layer authentication
without
> use of EAP.  For example, using AAA to carry GSS-API payloads would
not
> require much more than defining a GSS-Message attribute.  EAP has no
> unique properties that make it more suitable for use with AAA.  In
fact, I
> would argue that the fit between EAP and AAA has always been tenuous
at
> best -- witness the issues encountered in federated EAP authentication
> that RADSEC has been needed to address.
>=20
> In particular, the problems of EAP auth (e.g. multiple round-trips,
> general fragility in federated uses) become highly toxic when applied
to
> Realtime applications such as XMPP and SIP.  As we have learned,
Digest
> auth (RFC 5090) has not been widely deployed, in part because of
concern
> about the additional latency added by a AAA exchange.  For users of
real-
> time applications, additional latency is a basic, non-negotiable goal.
If
> the relatively modest number of exchanges implied by RFC 5090 were
> intolerable in realtime applications,  how can we expect EAP exchanges
> (which can involve 4-5 times the number of roundtrips of RFC 5090) to
be
> deployed?  The answer unfortunately, is that there is no chance at
all.
>=20
[Joe]=20
> So in summary, I believe that some aspects of the problem statement
make
> sense, but that a solution has been chosen prematurely.  The right way
to
> move forward in a situation like this is to begin with a problem
> statement, which should include carefully validating the uses cases.
>=20
>=20
> > ----- Original Message -----
> > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> > To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>;
> > <aaa-doctors@ietf.org>
> > Sent: Wednesday, June 02, 2010 10:56 PM
> > Subject: FEDAUTH BOF request
> >
> >
> > Diameter and RADIUS experts should pay attention to the request to
> > hold a Federated Authentication (FEDAUTH) BOF which will be
discussed
> > this morning by the IAB and the IESG.
> >
> > The Draft Charter is available at
> > http://www.project-moonshot.org/bof/charter/, and more information
> > about this BOF or other BOF requests can be examined at
> > http://trac.tools.ietf.org/bof/trac/
> >
> > Dan
> >
> > --
> > to unsubscribe send a message to radiusext-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://psg.com/lists/radiusext/>
> >
> >
> >
> > --
> > to unsubscribe send a message to radiusext-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://psg.com/lists/radiusext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun  7 08:18:15 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2E573A6359 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 08:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.104
X-Spam-Level: **
X-Spam-Status: No, score=2.104 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXggRntm0SBA for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 08:18:14 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B9D6E3A79E1 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon,  7 Jun 2010 04:34:39 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLaWK-000LhN-Nw for radiusext-data0@psg.com; Mon, 07 Jun 2010 11:29:32 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OLaWI-000Lgn-6F for radiusext@ops.ietf.org; Mon, 07 Jun 2010 11:29:30 +0000
Message-ID: <4C0CD816.6060809@deployingradius.com>
Date: Mon, 07 Jun 2010 13:29:26 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Updated copy of the design guidelines document
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

  I've submitted a new version of the design guidelines document, based
on recent feedback.

  The changes are:

- clarify "TLV encoding" versus "data format" as per Avi's review

  This required a series of minor changes throughout the document.

- add Dave Nelson's overview of the different attributes to
  the "introduction" section.

  This required significant re-writes of that section.

- Added Bernard's suggested text from
  http://ops.ietf.org/lists/radiusext/2010/msg00277.html

  As the introduction section had been re-written, the text
  was no longer appropriate for that section.  Instead, it was
  added to Section 3.3.3.

- added Terminology of "standard space" and "vendor space"

  We may want to add terminology of "TLV encoding" and "data format".

- audited the document for consistency

- changed a few "... needs to..." into SHOULD.  The "needs to" text
  is ambiguous, in that it makes suggestions without using RFC2119 text.

- Added Section A.1.4 allowing data types from Appendix B.  The existing
  text in Section A.2 allowed this, so making it explicit in A.1 is
  a good idea.


  Please review the updated Introduction, as it has changed a lot.

 Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun  7 08:27:32 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94B373A67B3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 08:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tylBn9SrWq-I for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 08:27:31 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B61FA3A71A7 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon,  7 Jun 2010 04:36:06 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLaXJ-000Lrd-CW for radiusext-data0@psg.com; Mon, 07 Jun 2010 11:30:33 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <root@core3.amsl.com>) id 1OLaXG-000Lqz-IL for radiusext@ops.ietf.org; Mon, 07 Jun 2010 11:30:30 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id B64A428C9C7; Mon,  7 Jun 2010 04:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-design-14.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100607113012.B64A428C9C7@core3.amsl.com>
Date: Mon,  7 Jun 2010 04:30:02 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

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 Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-14.txt
	Pages           : 40
	Date            : 2010-06-07

This document provides guidelines for the design of attributes used
by the Remote Authentication Dial In User Service (RADIUS) protocol.
It is expected that these guidelines will prove useful to authors and
reviewers of future RADIUS attribute specifications, both within the
IETF as well as other Standards Development Organizations (SDOs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-radext-design-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2010-06-07042913.I-D@ietf.org>

--NextPart--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun  7 08:44:07 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F8BE28C3C4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 08:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.053
X-Spam-Level: *
X-Spam-Status: No, score=1.053 tagged_above=-999 required=5 tests=[AWL=-1.052, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hR8jALt21JI2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 08:43:59 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 42F7E3A86D3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun,  6 Jun 2010 09:18:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLITW-000IDU-KX for radiusext-data0@psg.com; Sun, 06 Jun 2010 16:13:26 +0000
Received: from [65.55.111.99] (helo=blu0-omc2-s24.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OLITR-000ICq-CV for radiusext@ops.ietf.org; Sun, 06 Jun 2010 16:13:21 +0000
Received: from BLU137-DS5 ([65.55.111.73]) by blu0-omc2-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 6 Jun 2010 09:13:18 -0700
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alper Yegin'" <alper.yegin@yegin.org>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>,	<F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>	<BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl> <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
In-Reply-To: <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
Subject: RE: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
Date: Sun, 6 Jun 2010 09:13:19 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CB0558.818885A0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsC3Vu3xwQsiPtKT8+vfB1gbF+XiAA2UOhgAHbjbHA=
Content-Language: en-us
X-OriginalArrivalTime: 06 Jun 2010 16:13:18.0263 (UTC) FILETIME=[2CF2C470:01CB0593]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_001C_01CB0558.818885A0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Previous tests have shown problems with use of RADIUS/EAP over UDP in
federated scenarios:

http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentication-over-jammed-
network/

 

As noted in the above paper, once packet loss is introduced, completing the
multiple roundtrips of EAP authentication becomes increasingly difficult. 

 

RADIUS over TCP holds up much better until a threshold is reached, and then
authentication success fractions fall dramatically.   

 

Due to the transport issues and RADIUS packet size limitation of 4096 (which
may impact the ability to transport SAML assertions), it seems like Diameter
would be more suitable.  

 

 

 

 

From: aaa-doctors-bounces@ietf.org [mailto:aaa-doctors-bounces@ietf.org] On
Behalf Of Alper Yegin
Sent: Friday, June 04, 2010 12:31 AM
To: 'Bernard Aboba'; tena@huawei.com; aaa-doctors@ietf.org;
radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request

 


In particular, the problems of EAP auth (e.g. multiple round-trips, general
fragility in federated uses) become highly toxic when applied to Realtime
applications such as XMPP and SIP.  As we have learned, Digest auth (RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.  For users of real-time
applications, additional latency is a basic, non-negotiable goal.  If the
relatively modest number of exchanges implied by RFC 5090 were intolerable
in realtime applications,  how can we expect EAP exchanges (which can
involve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The
answer unfortunately, is that there is no chance at all.  

So in summary, I believe that some aspects of the problem statement make
sense, but that a solution has been chosen prematurely.  The right way to
move forward in a situation like this is to begin with a problem statement,
which should include carefully validating the uses cases.  

 

 

Alper> I agree. 

 

Alper> Anyone who was around the ICOS BoF in IETF 62 would remember that the
community was convinced(!) that using EAP for anything other than network
access was a no-no. Now before we embark on marching in  180-degree opposite
direction, I'd say the community needs to be "unconvinced" first. I'm not
saying this is not doable, but something we need to go through first.

 

Alper

 

 

  

> ----- Original Message ----- 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
> <aaa-doctors@ietf.org>
> Sent: Wednesday, June 02, 2010 10:56 PM
> Subject: FEDAUTH BOF request
> 
> 
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
> 
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/, and more information about
> this BOF or other BOF requests can be examined at
> http://trac.tools.ietf.org/bof/trac/
> 
> Dan
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> 
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


------=_NextPart_000_001C_01CB0558.818885A0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Previous tests have shown problems with use of RADIUS/EAP =
over
UDP in federated scenarios:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentic=
ation-over-jammed-network/<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As noted in the above paper, once packet loss is =
introduced, completing
the multiple roundtrips of EAP authentication becomes increasingly =
difficult. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>RADIUS over TCP holds up much better until a threshold is
reached, and then authentication success fractions fall dramatically. =
&nbsp;&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Due to the transport issues and RADIUS packet size =
limitation of
4096 (which may impact the ability to transport SAML assertions), it =
seems like
Diameter would be more suitable. &nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
aaa-doctors-bounces@ietf.org [mailto:aaa-doctors-bounces@ietf.org] <b>On =
Behalf
Of </b>Alper Yegin<br>
<b>Sent:</b> Friday, June 04, 2010 12:31 AM<br>
<b>To:</b> 'Bernard Aboba'; tena@huawei.com; aaa-doctors@ietf.org;
radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com<br>
<b>Subject:</b> Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF =
request<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
In particular, the problems of EAP auth (e.g. multiple round-trips, =
general
fragility in federated uses) become highly toxic when applied to =
Realtime
applications such as XMPP and SIP.&nbsp; As we have learned, Digest auth =
(RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.&nbsp; For users of real-time
applications, additional latency is a basic, non-negotiable goal.&nbsp; =
If the
relatively modest number of exchanges implied by RFC 5090 were =
intolerable in
realtime applications,&nbsp; how can we expect EAP exchanges (which can =
involve
4-5 times the number of roundtrips of RFC 5090) to be deployed?&nbsp; =
The
answer unfortunately, is that there is no chance at all.&nbsp; <br>
<br>
So in summary, I believe that some aspects of the problem statement make =
sense,
but that a solution has been chosen prematurely.&nbsp; The right way to =
move
forward in a situation like this is to begin with a problem statement, =
which
should include carefully validating the uses cases.&nbsp; <span
style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; I agree. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; Anyone who was around the ICOS BoF in IETF 62 =
would
remember that the community was convinced(!) that using EAP for anything =
other
than network access was a no-no. Now before we embark on marching in
&nbsp;180-degree opposite direction, I&#8217;d say the community needs =
to be
&#8220;unconvinced&#8221; first. I&#8217;m not saying this is not =
doable, but
something we need to go through first.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>&nbsp;
<br>
<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;Romascanu, Dan (Dan)&quot; =
&lt;dromasca@avaya.com&gt;<br>
&gt; To: &lt;dime@ietf.org&gt;; &quot;radext mailing list&quot;
&lt;radiusext@ops.ietf.org&gt;; <br>
&gt; &lt;aaa-doctors@ietf.org&gt;<br>
&gt; Sent: Wednesday, June 02, 2010 10:56 PM<br>
&gt; Subject: FEDAUTH BOF request<br>
&gt; <br>
&gt; <br>
&gt; Diameter and RADIUS experts should pay attention to the request to =
hold<br>
&gt; a Federated Authentication (FEDAUTH) BOF which will be discussed =
this<br>
&gt; morning by the IAB and the IESG.<br>
&gt; <br>
&gt; The Draft Charter is available at<br>
&gt; http://www.project-moonshot.org/bof/charter/, and more information =
about<br>
&gt; this BOF or other BOF requests can be examined at<br>
&gt; http://trac.tools.ietf.org/bof/trac/<br>
&gt; <br>
&gt; Dan<br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: =
&lt;http://psg.com/lists/radiusext/&gt;<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_001C_01CB0558.818885A0--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun  7 10:17:50 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32B6E28C445 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 10:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.247
X-Spam-Level: 
X-Spam-Status: No, score=-0.247 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32rVDNVH02dc for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 10:17:49 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 896893A9037 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun,  6 Jun 2010 14:09:07 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLN1T-0002gC-Cs for radiusext-data0@psg.com; Sun, 06 Jun 2010 21:04:47 +0000
Received: from [70.89.142.196] (helo=aspen.internal.iea-software.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <peterd@iea-software.com>) id 1OLN1Q-0002fq-DI for radiusext@ops.ietf.org; Sun, 06 Jun 2010 21:04:44 +0000
Received: from SMURF (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005291726@aspen.internal.iea-software.com>; Sun, 6 Jun 2010 14:04:42 -0700
Date: Sun, 6 Jun 2010 14:04:39 -0700 (Pacific Daylight Time)
From: Peter Deacon <peterd@iea-software.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
cc: 'Alper Yegin' <alper.yegin@yegin.org>, tena@huawei.com,  aaa-doctors@ietf.org, radiusext@ops.ietf.org, dime@ietf.org,  dromasca@avaya.com
Subject: RE: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
In-Reply-To: <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
Message-ID: <alpine.WNT.2.00.1006061319410.1732@SMURF>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl> <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org> <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Sun, 6 Jun 2010, Bernard Aboba wrote:

> Previous tests have shown problems with use of RADIUS/EAP over UDP in
> federated scenarios:

> http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentication-over-jammed-
> network/

> As noted in the above paper, once packet loss is introduced, completing the
> multiple roundtrips of EAP authentication becomes increasingly difficult.

This paper has some crazy figures.. look at the data for packet loss.

40% packet loss (client to server) = 78% success rate for PEAP-MSCHAPv2
40% packet loss (server to client) = 20% success rate for PEAP-MSCHAPv2

There is a footnote on this issue "The more favorable results for 
client-to-server jamming are caused by the aggressive packet re-sending 
strategy of wpa_supplicant compared to the behavior of Radiator."

If the server did not receive client request or client did not receive 
server response the knowledge available and avenue for response by the 
client is the same in either case.  The figures appear to reflect a 
substantial implementation artifact in the servers tx side retransmit.

regards,
Peter

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun  7 10:56:00 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CD6A3A67C0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 10:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WB-d9IK53ug3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon,  7 Jun 2010 10:55:58 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 41F0E3A6933 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon,  7 Jun 2010 10:55:08 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLgSG-0009yV-HT for radiusext-data0@psg.com; Mon, 07 Jun 2010 17:49:44 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <wwwrun@core3.amsl.com>) id 1OLgS9-0009xj-1j for radiusext@ops.ietf.org; Mon, 07 Jun 2010 17:49:37 +0000
Received: by core3.amsl.com (Postfix, from userid 30) id 0066D3A6988; Mon,  7 Jun 2010 10:49:34 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>,  radext mailing list <radiusext@ops.ietf.org>,  radext chair <radext-chairs@tools.ietf.org>
Subject: Document Action: 'Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol' to Informational RFC
Message-Id: <20100607174935.0066D3A6988@core3.amsl.com>
Date: Mon,  7 Jun 2010 10:49:34 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

The IESG has approved the following document:

- 'Use of Status-Server Packets in the Remote Authentication Dial In User 
   Service (RADIUS) Protocol '
   <draft-ietf-radext-status-server-09.txt> as an Informational RFC


This document is the product of the RADIUS EXTensions Working Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-status-server-09.txt

Technical Summary

This document specifies a deployed extenion to RADIUS which enables
clients to query the status of a RADIUS server.  While the
Status-Server Code (12) was defined as experimental in RFC 2865
Section 3, details of the protocol's operation have not been
documented until now.  

Working Group Summary

This document has completed RADEXT WG last call, with the primary
areas of discussion relating to security and ID field usage. 

The RADEXT WG elected to recommend this document for publication
as an Informational RFC rather than as a standards-Track RFC due
to concerns about problems with deployed implementations.  The
fixes recommended within the document are compatible with
existing servers that receive Status-Server packets, but impose new
security requirements on clients that send Status-Server packets.

Document Quality

The document has been reviewed by IETF RADEXT WG members. 
An expert review has been carried out by Ignacio Goyret. 

Status-Server has been implemented by multiple vendors, 
including RADIATOR, FreeRADIUS and Cistron.  It is currently
in use within EDUROAM, an educational roaming consortium
with more than one million users worldwide.  As
a result, the document reflects operational experience.

Personnel

Bernard Aboba is the document shepherd for this document. 
Dan Romascanu is the responsible AD.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun  8 07:25:10 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DBA028C1AC for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 07:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.579
X-Spam-Level: *
X-Spam-Status: No, score=1.579 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uxJSXDEJZ1ui for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 07:25:09 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E83BB28C19C for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  8 Jun 2010 07:25:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLzeN-0007x5-QJ for radiusext-data0@psg.com; Tue, 08 Jun 2010 14:19:31 +0000
Received: from [65.55.116.15] (helo=blu0-omc1-s4.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OLzeK-0007wk-Ug for radiusext@ops.ietf.org; Tue, 08 Jun 2010 14:19:29 +0000
Received: from BLU137-W23 ([65.55.116.7]) by blu0-omc1-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 Jun 2010 07:19:27 -0700
Message-ID: <BLU137-W232034863E4B79D0A9666093D60@phx.gbl>
Content-Type: multipart/alternative; boundary="_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_"
X-Originating-IP: [140.247.243.93]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Last Look at RADIUS Design Guidelines
Date: Tue, 8 Jun 2010 07:19:27 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Jun 2010 14:19:27.0764 (UTC) FILETIME=[9A7AD540:01CB0715]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


This is announcing a "last look" at the RADIUS Design Guidelines document=
=2C prior to its being approval by the IETF for publication as a Best Curre=
nt Practice (BCP).=20

The document is available for inspection here:
http://tools.ietf.org/id/draft-ietf-radext-design

The "last look" will last until June 28=2C 2010.  Comments may be submitted=
 in any of the following ways:

a. Submission via the RADEXT TRAC system: http://trac.tools.ietf.org/wg/rad=
ext/trac/newticket

b. Comments sent to the RADEXT WG mailing list (radiusext@ops.ietf.org).=20
 		 	   		  =

--_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
This is announcing a "last look" at the RADIUS Design Guidelines document=
=2C prior to its being approval by the IETF for publication as a Best Curre=
nt Practice (BCP). <br><br>The document is available for inspection here:<b=
r>http://tools.ietf.org/id/draft-ietf-radext-design<br><br>The "last look" =
will last until June 28=2C 2010.&nbsp=3B Comments may be submitted in any o=
f the following ways:<br><br>a. Submission via the RADEXT TRAC system: http=
://trac.tools.ietf.org/wg/radext/trac/newticket<br><br>b. Comments sent to =
the RADEXT WG mailing list (radiusext@ops.ietf.org). <br> 		 	   		  </body=
>
</html>=

--_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun  8 07:32:41 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ADA728C1F8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 07:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.755
X-Spam-Level: *
X-Spam-Status: No, score=1.755 tagged_above=-999 required=5 tests=[AWL=-0.351, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eC5sxdsArMiQ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 07:32:40 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A62CD28C203 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  8 Jun 2010 07:31:09 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLzm9-00097U-9k for radiusext-data0@psg.com; Tue, 08 Jun 2010 14:27:33 +0000
Received: from [65.55.116.49] (helo=blu0-omc1-s38.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OLzm5-00097A-RY for radiusext@ops.ietf.org; Tue, 08 Jun 2010 14:27:29 +0000
Received: from BLU137-W1 ([65.55.116.9]) by blu0-omc1-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 Jun 2010 07:27:28 -0700
Message-ID: <BLU137-W12C935295D1D5695A60FF93D60@phx.gbl>
Content-Type: multipart/alternative; boundary="_173f1fb3-7506-40f6-a833-e6ee1bc0c714_"
X-Originating-IP: [140.247.243.93]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Repost:  The RADEXT WG Guide to TRAC
Date: Tue, 8 Jun 2010 07:27:28 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Jun 2010 14:27:28.0931 (UTC) FILETIME=[B9471730:01CB0716]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_173f1fb3-7506-40f6-a833-e6ee1bc0c714_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


The RADEXT WG is now using the TRAC database to keep track of issues=20
relating to work in progress=2C including working group work items and=20
individual submissions undergoing review.  This document provides some=20
basic information on how to use TRAC to submit or edit issues. =20
Documentation
 relating to the TRAC Issue Tracking database is available here: http://tra=
c.tools.ietf.org/wg/radext/trac/wiki

Since this documentation is somewhat lengthy (and mostly relevant to=20
Admins)=2C here is a pithy synopsis.=20
=20
1.       To submit an issue=20
in TRAC=2C you first need to login to the RADEXT WG site on the tools=20
server:  http://tools.ietf.org/wg/radext/trac/login
=20


2.       If you don=92t already have a login ID=2C you can obtain one by=20
navigating to this site:   http://trac.tools.ietf.org/newlogin


3.       Once you have obtained an account=2C and have logged in=2C you can=
=20
file an issue by navigating to the  ticket entry form: http://trac.tools.ie=
tf.org/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=2C or =93enhancement=94 for a proposed addition of=20
functionality (such as an additional requirement).=20

b.      The Priority: field is set based on the severity of the Issue. =20
 For example=2C editorial issues are typically =93minor=94 or =93trivial=94=
.=20

c.       The Milestone: field should be set to milestone1 (useless=2C I=20
know).=20

d.      The Component: field should be set to the document you are=20
filing the issue on. =20

e.      The Version: field should be set to =931.0=94.=20

f.        The Severity: field should be set to based on the status of=20
the document (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=20
inspiration seizes you.=20

h.      The Assign To: field is generally filled in with the email=20
address of the editor.=20


5.       Typically it won=92t be necessary to enclose a file with the=20
ticket=2C but if you need to=2C select =93I have files to attach to this=20
ticket=94.=20


6.       If you want to preview your Issue=2C click on the =93Preview=94=20
button.  When you=92re ready to submit the issue=2C click on the =93Create=
=20
Ticket=94 button.=20


7.       If you want to update an issue=2C go to the "View Tickets" page: h=
ttp://trac.tools.ietf.org/wg/radext/trac/report/1=20
 Click on the ticket # you want to update=2C and then modify the ticket=20
fields as required.=20


That=92s it! =20


If you encounter problems with TRAC=2C send email to me and I=92ll try to=20
figure out what=92s going on.=20


Happy TRACing=2C

Bernard 		 	   		  =

--_173f1fb3-7506-40f6-a833-e6ee1bc0c714_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The RADEXT WG is now using the TRAC database to keep track of issues=20
relating to work in progress=2C including working group work items and=20
individual submissions undergoing review.&nbsp=3B This document provides so=
me=20
basic information on how to use TRAC to submit or edit issues.&nbsp=3B <br>=
Documentation
 relating to the TRAC Issue Tracking database is available here: <a rel=3D"=
nofollow" href=3D"http://trac.tools.ietf.org/wg/radext/trac/wiki">http://tr=
ac.tools.ietf.org/wg/radext/trac/wiki</a><br>
Since this documentation is somewhat lengthy (and mostly relevant to=20
Admins)=2C here is a pithy synopsis. <br>&nbsp=3B<br>1.&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B To submit an issue=20
in TRAC=2C you first need to login to the RADEXT WG site on the tools=20
server:&nbsp=3B <a rel=3D"nofollow" href=3D"http://tools.ietf.org/wg/radext=
/trac/login">http://tools.ietf.org/wg/radext/trac/login</a>
 <br><br>
2.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you don=92t already h=
ave a login ID=2C you can obtain one by=20
navigating to this site:&nbsp=3B&nbsp=3B <a rel=3D"nofollow" href=3D"http:/=
/trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/newlogin</a><br><=
br>
3.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Once you have obtained a=
n account=2C and have logged in=2C you can=20
file an issue by navigating to the&nbsp=3B ticket entry form: <a rel=3D"nof=
ollow" href=3D"http://trac.tools.ietf.org/wg/radext/trac/newticket">http://=
trac.tools.ietf.org/wg/radext/trac/newticket</a><br><br>
4.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B When opening an issue:<b=
r><br>
a.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Type: field should b=
e set to =93defect=94 for an issue with the
 current document text=2C or =93enhancement=94 for a proposed addition of=20
functionality (such as an additional requirement). <br>
b.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Priority: field is set based=
 on the severity of the Issue.&nbsp=3B&nbsp=3B
 For example=2C editorial issues are typically =93minor=94 or =93trivial=94=
. <br>
c.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Milestone: field sho=
uld be set to milestone1 (useless=2C I=20
know). <br>
d.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Component: field should be s=
et to the document you are=20
filing the issue on.&nbsp=3B <br>
e.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Version: field should be set=
 to =931.0=94. <br>
f.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Severity: fi=
eld should be set to based on the status of=20
the document (e.g. =93In WG Last Call=94 for a document in WG last call)<br=
>
g.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Keywords: an=
d CC: fields can be left blank unless=20
inspiration seizes you. <br>
h.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Assign To: field is generall=
y filled in with the email=20
address of the editor. <br>
<br>5.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Typically it won=92t=
 be necessary to enclose a file with the=20
ticket=2C but if you need to=2C select =93I have files to attach to this=20
ticket=94. <br>
<br>6.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you want to previ=
ew your Issue=2C click on the =93Preview=94=20
button.&nbsp=3B When you=92re ready to submit the issue=2C click on the =93=
Create=20
Ticket=94 button. <br>
<br>7.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you want to updat=
e an issue=2C go to the "View Tickets" page: <a rel=3D"nofollow" href=3D"ht=
tp://trac.tools.ietf.org/wg/radext/trac/report/1">http://trac.tools.ietf.or=
g/wg/radext/trac/report/1</a>&nbsp=3B
 Click on the ticket # you want to update=2C and then modify the ticket=20
fields as required. <br><br>
That=92s it!&nbsp=3B <br><br>
If you encounter problems with TRAC=2C send email to me and I=92ll try to=20
figure out what=92s going on. <br><br>
Happy TRACing=2C<br>
Bernard 		 	   		  </body>
</html>=

--_173f1fb3-7506-40f6-a833-e6ee1bc0c714_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun  8 07:39:10 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D489128C1BD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 07:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WSxTaPTzaI11 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 07:39:09 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 001523A67F6 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  8 Jun 2010 07:39:08 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OLzro-000AEn-LI for radiusext-data0@psg.com; Tue, 08 Jun 2010 14:33:24 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OLzri-000ADv-Gi for radiusext@ops.ietf.org; Tue, 08 Jun 2010 14:33:18 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.71) (envelope-from <trac@tools.ietf.org>) id 1OLzre-0002Vr-7r; Tue, 08 Jun 2010 07:33:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, iesg@ietf.org
X-Trac-Project: radext
Date: Tue, 08 Jun 2010 14:33:14 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #25: IESG DISCUSS Comments
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/25
Message-ID: <054.920a9e623434ddb929f86da019a86134@tools.ietf.org>
X-Trac-Ticket-ID: 25
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, iesg@ietf.org, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#25: IESG DISCUSS Comments
-----------------------------------+----------------------------------------
 Reporter:  iesg@…                 |       Owner:  aland@…                  
     Type:  defect                 |      Status:  new                      
 Priority:  blocker                |   Milestone:  milestone1               
Component:  tcp-transport          |     Version:  1.0                      
 Severity:  Submitted WG Document  |    Keywords:                           
-----------------------------------+----------------------------------------
 Discusses and other comments

 Summary: Has a DISCUSS. Has enough positions to pass once DISCUSSes are
 resolved.
 Russ Housley

 Comment (2010-05-19)

   Please consider the comments from the Gen-ART Review by Glenn
   Kowack on 18 May 2010.  The review can be found at:

     http://www.softarmor.com/rai/temp-gen-art/
     draft-ietf-radext-tcp-transport-06-kowack.txt

 Lars Eggert

 Comment (2010-05-20)

 Agree with Tim's DISCUSS.

 Section 27, paragraph 13:
 >    It is not intended
 >    to define TCP as a transport protocol for RADIUS in the absence of
 >    TLS.

   The document title is "RADIUS Over TCP". It's surprising to then see
   that abstract say that it is not intended to define RADIUS over TCP...
   Suggestion: Rename document to "Radius over TLS"?


 Section 1., paragraph 1:
 >    While
 >    there are a number of benefits to using UDP as outlined in [RFC2865]
 >    Section 2.4, there are also some limitations:

   Lack of congestion control is surely a limitation?


 Section 1.1., paragraph 2:
 >    In scenarios where RADIUS proxies exchange a large volume of packets
 >    (10+ packets per second), it is likely that there will be sufficient
 >    traffic to enable the congestion window to be widened beyond the
 >    minimum value on a long-term basis, enabling ACK piggy-backing.

   I don't understand what this paragraph means to say. The TCP
   congestion window opens already at much lower rates than 10+ pps.
   Also, how is this at all related to ACK-piggybacking?


 Section 1.1., paragraph 5:
 >    These problems disappear if a 4096 application-layer payload can be
 >    used alongside RADIUS over TLS.  Since most TCP implementations
 >    support MTU discovery, the TCP MSS is automatically adjusted to
 >    account for the MTU, and the larger congestion window supported by
 >    TCP may allow multiple TCP segments to be sent within a single
 >    window.

   Even those few TCP stacks that don't do PMTUD can already support
   arbitrary payloads (just with slightly less efficient packetization).


 Section 2.6.1., paragraph 5:
 >    As noted previously, RADIUS packets SHOULD NOT be re-transmitted to
 >    the same destination IP and numerical port, but over a different
 >    transport layer.

   Where does it say that? The second paragraph of Section 2.6 says that
   they MAY be retransmitted over a new connection (which is different
   from a SHOULD NOT). Also, "transport layer" here is unclear - do you
   mean "transport connection" (= use a different TCP connection) or do
   you mean "transport protocol" (= use UDP)?


 Section 2.6.2., paragraph 2:
 >    Unlike UDP, TLS is subject to issues related to Head of Line (HoL)
 >    blocking.  This occurs when when a TLS segment is lost and a
 >    subsequent TLS segment arrives out of order.  While the RADIUS server
 >    can process RADIUS packets out of order, the semantics of TLS makes
 >    this impossible.  This limitation can lower the maximum packet
 >    processing rate of RADIUS over TLS.

   s/TLS/TCP/ in this paragraph


 Section 2.6.4., paragraph 6:
 >    After applying the above rules, there are still situations where the
 >    previous specifications allow a packet to be "silently discarded".
 >    In these situations, the TCP connections MAY remain open, or MAY be
 >    closed, as an implementation choice.  However, the invalid packet
 >    MUST be silently discarded.

   In order to reduce connection-setup overheads, wouldn't it make sense
   to RECOMMEND the connection stay open?

 Ralph Droms

 Discuss (2010-05-20)

 This Discuss is related to Tim's Discuss.  This text:

    "Bare" TCP transport MAY, however, be used when another method such
    as
 IPSec [RFC4301] is used to provide additional confidentiality and
    security.
 Should experience show that such deployments are useful,
    this specification
 could be moved to standards track.

 is confusing.  Why would experience with
 "bare" TCP or IPSec TCP cause draft-ietf-radext-tcp-transport to progress
 to
 Standards Track?

 Similarly, from the Abstract:

    It [draft-ietf-radext-tcp-transport-06.txt] is not intended
    to define TCP as a transport protocol for RADIUS in the absence of
    TLS.

 while several of the motivations for RADIUS over TCP in section 1.1 are
 not
 specific to RADIUS with TLS.

 Adrian Farrel

 Comment (2010-05-20)

 To follow up on Tim Polk's Discuss point 2
 I appreciate the sentiment of the
 paragraph, but "NOT RECOMMENDED" is not RFC 2119 language (as idnits would
 tell
 you). You have to flip the sense of the sentence and use "RECOMMENDED".
 But Tim
 is also right, please consider "MUST NOT" since the following paragraph...

    "Bare" TCP transport MAY, however, be used when another method such
    as IPSec [RFC4301] is used to provide additional confidentiality and
    security.  Should experience show that such deployments are useful,
    this specification could be moved to standards track.

 ...is really confusing. It implies that the purpose of this document *is*
 to
 define the use of bare TCP transport which is in conflict with the
 Abstract.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/25>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun  8 12:34:03 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C30353A6781 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 12:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.486
X-Spam-Level: *
X-Spam-Status: No, score=1.486 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KEBHtalBi-Gj for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  8 Jun 2010 12:34:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id AADD43A659B for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  8 Jun 2010 12:34:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OM4UI-0007u1-EQ for radiusext-data0@psg.com; Tue, 08 Jun 2010 19:29:26 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OM4UF-0007tb-JC for radiusext@ops.ietf.org; Tue, 08 Jun 2010 19:29:23 +0000
Message-ID: <4C0E9A11.5090504@deployingradius.com>
Date: Tue, 08 Jun 2010 21:29:21 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Glenn Kowack <glenn@riveronce.com>
CC: gen-art@ietf.org, 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Gen-ART LC review of draft-ietf-radext-tcp-transport-06.txt
References: <1E9286E3-285A-46E7-8823-25B00D6AE38A@riveronce.com> <4BFA346C.5090509@deployingradius.com> <9A6D525E-D5A3-447F-9D09-B516B3146667@riveronce.com>
In-Reply-To: <9A6D525E-D5A3-447F-9D09-B516B3146667@riveronce.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glenn Kowack wrote:
...
>>> Does ‘traditional’ here mean as defined by the specification or is UDP
>>> use optional?
>>  It means "as defined by the spec".  Until now, UDP has been mandatory.
> 
> I recommend you say that explicitly: as defined by the specification.  It's not
> clear to me what 'traditional' means to random readers; they may view the
> cited use of UDP as strictly historical.  In any event, they probably won't
> understand that 'traditional' means 'normative'.

  OK.

>> It is not intended to define TCP as a transport protocol for RADIUS in
>> the absence of a secure transport layer.
> 
> Although an improvement, your change does not provide the clarification
> I believe is necessary.  Stating a negative, and also citing 'intent' in "not
> intended to define", is awkward and leaves room for speculation about the
> positive case.  Please see my prior example.

  OK, except that using RADIUS + TCP over IPSec would be allowed.  It's
too restrictive to specify TLS as the only permitted secure transport layer.

> I think I should have been clearer that my question is about generally-
> acceptable levels of failure for a mass-market network service.  This sort
> of data covers a broad area and should be publicly available.

  References would be helpful.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun 10 07:53:59 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03D2728C0DF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 10 Jun 2010 07:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.816
X-Spam-Level: 
X-Spam-Status: No, score=0.816 tagged_above=-999 required=5 tests=[AWL=-1.289, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8YoSY-QZ7PN for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 10 Jun 2010 07:53:57 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BFA893A6978 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 10 Jun 2010 07:53:57 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OMj3G-0005Lc-CS for radiusext-data0@psg.com; Thu, 10 Jun 2010 14:48:14 +0000
Received: from [135.11.29.16] (helo=p-us1-iereast-outbound-tmp.us1.avaya.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <dromasca@avaya.com>) id 1OMj3D-0005Kv-Hl for radiusext@ops.ietf.org; Thu, 10 Jun 2010 14:48:11 +0000
X-IronPort-AV: E=Sophos;i="4.53,398,1272859200";  d="scan'208";a="19984577"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 10 Jun 2010 10:48:01 -0400
X-IronPort-AV: E=Sophos;i="4.53,398,1272859200";  d="scan'208";a="482436172"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Jun 2010 10:48: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
Subject: New WG co-chair
Date: Thu, 10 Jun 2010 16:47:49 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040228312F@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New WG co-chair
Thread-Index: AcsIq+WHvButc422RKCIchV/bl7DQg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "radext mailing list" <radiusext@ops.ietf.org>
Cc: "Ron Bonica" <rbonica@juniper.net>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Please welcome Mauricio Sanchez as the new co-chair of the RADEXT WG,
working together with Bernard Aboba. Congratulations and good luck,
Mauricio.=20

Thanks again to David Nelson who co-chaired for many years the WG
together with Bernard, and we hope that he will continue to be a fine
contributor.=20

Please allow me to thank everybody who considered the nomination, to all
people who made proposals and sent valuable comments about the
candidates. I am encouraged by the good response and the discussions
that took place during the open nomination process. I had to chose among
a number of candidates, all fine professionals and willing to contribute
to the WG progress by assuming the responsibility of co-chairing the WG.
It's been a difficult choice and a good sign about the vitality of the
WG.=20

Regards,

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Thu Jun 10 20:58:01 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 748983A67FB for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 10 Jun 2010 20:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.895
X-Spam-Level: 
X-Spam-Status: No, score=-101.895 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fu2y3nm-AJFQ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 10 Jun 2010 20:58:00 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 312DC3A681F for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 10 Jun 2010 20:58:00 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OMvIp-0006JH-Gq for radiusext-data0@psg.com; Fri, 11 Jun 2010 03:53:07 +0000
Received: from [15.192.0.45] (helo=g5t0008.atlanta.hp.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <mauricio.sanchez@hp.com>) id 1OMvIm-0006Ip-4Q for radiusext@ops.ietf.org; Fri, 11 Jun 2010 03:53:04 +0000
Received: from G5W0603.americas.hpqcorp.net (g5w0603.americas.hpqcorp.net [16.228.9.186]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g5t0008.atlanta.hp.com (Postfix) with ESMTPS id 9C8162426A; Fri, 11 Jun 2010 03:53:02 +0000 (UTC)
Received: from G5W0323.americas.hpqcorp.net (16.228.8.68) by G5W0603.americas.hpqcorp.net (16.228.9.186) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 11 Jun 2010 03:50:59 +0000
Received: from GVW0671EXC.americas.hpqcorp.net ([16.230.34.4]) by G5W0323.americas.hpqcorp.net ([16.228.8.68]) with mapi; Fri, 11 Jun 2010 03:50:59 +0000
From: "Sanchez, Mauricio (ProCurve)" <mauricio.sanchez@hp.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, radext mailing list <radiusext@ops.ietf.org>
CC: Ron Bonica <rbonica@juniper.net>
Date: Fri, 11 Jun 2010 03:50:58 +0000
Subject: RE: New WG co-chair
Thread-Topic: New WG co-chair
Thread-Index: AcsIq+WHvButc422RKCIchV/bl7DQgAKIwIA
Message-ID: <9BC2F7926B33FE4AB10D69891D58FC1C5313DB6B41@GVW0671EXC.americas.hpqcorp.net>
References: <EDC652A26FB23C4EB6384A4584434A040228312F@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040228312F@307622ANEX5.global.avaya.com>
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
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Thank you Dan.  Look forward to rolling up my sleeves together with the RAD=
EXT community and continuing to improve RADIUS. =20

-MS

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On=
 Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, June 10, 2010 7:48 AM
To: radext mailing list
Cc: Ron Bonica
Subject: New WG co-chair

Please welcome Mauricio Sanchez as the new co-chair of the RADEXT WG,
working together with Bernard Aboba. Congratulations and good luck,
Mauricio.=20

Thanks again to David Nelson who co-chaired for many years the WG
together with Bernard, and we hope that he will continue to be a fine
contributor.=20

Please allow me to thank everybody who considered the nomination, to all
people who made proposals and sent valuable comments about the
candidates. I am encouraged by the good response and the discussions
that took place during the open nomination process. I had to chose among
a number of candidates, all fine professionals and willing to contribute
to the WG progress by assuming the responsibility of co-chairing the WG.
It's been a difficult choice and a good sign about the vitality of the
WG.=20

Regards,

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 09:03:05 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8417E3A68F8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 09:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.218
X-Spam-Level: *
X-Spam-Status: No, score=1.218 tagged_above=-999 required=5 tests=[AWL=-0.887, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yq8UZnVs3MZw for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 09:03:00 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id ED4073A68F6 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 09:02:59 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOYXU-000PMJ-TC for radiusext-data0@psg.com; Tue, 15 Jun 2010 15:59:00 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OOYXS-000PLg-Ix for radiusext@ops.ietf.org; Tue, 15 Jun 2010 15:58:58 +0000
Message-ID: <4C17A33D.2090405@deployingradius.com>
Date: Tue, 15 Jun 2010 17:58:53 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Is provisioning services in Accounting-Request packets bad?
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

  When a RADIUS server returns Access-Accept, some systems also request
that it send an Accounting-Request packet to a provisioning system.
This provisioning system requires information such as Framed-IP-Address,
or copies of some VSAs from the Access-Accept.

  Quote "This is not unusual, and several vendors are providing such a
solution".

  RFC 2866 doesn't forbid this, as it expects accounting packets to be
sent by the NAS.  The guidelines document contains minimal text about
accounting.

  Is it worth adding a line in the "guidelines" document saying that
accounting packets are to be used for... accounting?  And that
provisioning services via Accounting-Request is bad?

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 09:17:30 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3556A3A6979 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 09:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nz-abOc81nNb for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 09:17:29 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C9A693A6950 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 09:17:28 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOYlY-0001sI-6l for radiusext-data0@psg.com; Tue, 15 Jun 2010 16:13:32 +0000
Received: from [207.3.149.133] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1OOYlV-0001rp-LH for radiusext@ops.ietf.org; Tue, 15 Jun 2010 16:13:30 +0000
Received: (qmail 12759 invoked from network); 15 Jun 2010 16:13:28 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 15 Jun 2010 16:13:28 -0000
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
In-Reply-To: <4C17A33D.2090405@deployingradius.com>
Date: Tue, 15 Jun 2010 12:13:28 -0400
Cc: 'radext mailing list' <radiusext@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com>
References: <4C17A33D.2090405@deployingradius.com>
To: Alan DeKok <aland@deployingradius.com>
X-Mailer: Apple Mail (2.1078)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Jun 15, 2010, at 11:58 AM, Alan DeKok wrote:

> When a RADIUS server returns Access-Accept, some systems also request
> that it send an Accounting-Request packet to a provisioning system.
> This provisioning system requires information such as =
Framed-IP-Address,
> or copies of some VSAs from the Access-Accept.

What does the provisioning system do with the information and how does =
it relate the result back to the NAS?

What entity sends the Accounting-Request, the NAS or he RADIUS server.  =
You use "it" and I'm unclear what "it" refers to.

> Quote "This is not unusual, and several vendors are providing such a
> solution".
>=20
> RFC 2866 doesn't forbid this, as it expects accounting packets to be
> sent by the NAS.  The guidelines document contains minimal text about
> accounting.
>=20
> Is it worth adding a line in the "guidelines" document saying that
> accounting packets are to be used for... accounting?  And that
> provisioning services via Accounting-Request is bad?

Well, I personally think that provisioning services via an =
Accounting-Request is bad, but I don't yet see how the NAS is actually =
being provisioned by a request message.  What is fairly common practice =
is to build resource management systems around RADIUS Accounting.  Is =
that the sort of thing you're talking about?

Regards,

Dave

David B. Nelson

Elbrys Networks, Inc.
282 Corporate Drive, Unit 1
Portsmouth, NH 03801

+1.603.570.2636
www.elbrysnetworks.com
dnelson@elbrysnetworks.com






--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 11:01:42 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A826E3A68B7 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gl+Y-58vOuK for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:01:40 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 253493A68D9 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 11:01:40 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOaPG-000IW3-P2 for radiusext-data0@psg.com; Tue, 15 Jun 2010 17:58:38 +0000
Received: from [216.82.249.147] (helo=mail29.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OOaPD-000ITd-UU for radiusext@ops.ietf.org; Tue, 15 Jun 2010 17:58:36 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-4.tower-29.messagelabs.com!1276624713!53656987!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 27230 invoked from network); 15 Jun 2010 17:58:34 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-4.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jun 2010 17:58:34 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Tue, 15 Jun 2010 13:58:32 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: Alan DeKok <aland@deployingradius.com>, radext mailing list <radiusext@ops.ietf.org>
Date: Tue, 15 Jun 2010 13:58:32 -0400
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Thread-Topic: Is provisioning services in Accounting-Request packets bad?
Thread-Index: AcsMtF499lfWbg37QL26T/qVskVEKw==
Message-ID: <020DF101-49BC-433F-87F9-A22B4FD5B0DD@bridgewatersystems.com>
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com>
In-Reply-To: <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On one hand we may need more information as David is mentioning.

But there is nothing wrong with a Back office system using information cont=
ained in an accounting message.

A back office system can be used for billing but it can also be used to do =
other things like generate triggers for Intrussion Detection/Prevention sys=
tems, Firewalls etc etc....

And thus some of the information could be used for provisioning of some ser=
vice by a back office system.

We should not be concerned about this.  It has nothing to do with the over =
the wire protocol.  As long as the information is valid to be sent in the A=
ccounting Messages we should be fine.




On 15-06-2010, at 12:13 , David B. Nelson wrote:

> On Jun 15, 2010, at 11:58 AM, Alan DeKok wrote:
>=20
>> When a RADIUS server returns Access-Accept, some systems also request
>> that it send an Accounting-Request packet to a provisioning system.
>> This provisioning system requires information such as Framed-IP-Address,
>> or copies of some VSAs from the Access-Accept.
>=20
> What does the provisioning system do with the information and how does it=
 relate the result back to the NAS?
>=20
> What entity sends the Accounting-Request, the NAS or he RADIUS server.  Y=
ou use "it" and I'm unclear what "it" refers to.
>=20
>> Quote "This is not unusual, and several vendors are providing such a
>> solution".
>>=20
>> RFC 2866 doesn't forbid this, as it expects accounting packets to be
>> sent by the NAS.  The guidelines document contains minimal text about
>> accounting.
>>=20
>> Is it worth adding a line in the "guidelines" document saying that
>> accounting packets are to be used for... accounting?  And that
>> provisioning services via Accounting-Request is bad?
>=20
> Well, I personally think that provisioning services via an Accounting-Req=
uest is bad, but I don't yet see how the NAS is actually being provisioned =
by a request message.  What is fairly common practice is to build resource =
management systems around RADIUS Accounting.  Is that the sort of thing you=
're talking about?
>=20
> Regards,
>=20
> Dave
>=20
> David B. Nelson
>=20
> Elbrys Networks, Inc.
> 282 Corporate Drive, Unit 1
> Portsmouth, NH 03801
>=20
> +1.603.570.2636
> www.elbrysnetworks.com
> dnelson@elbrysnetworks.com
>=20
>=20
>=20
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 11:10:04 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 075293A6950 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.974
X-Spam-Level: 
X-Spam-Status: No, score=0.974 tagged_above=-999 required=5 tests=[AWL=-0.390, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K2VeDzZMYJ8h for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:10:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C3A443A6909 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 11:10:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOaWi-000K9g-RI for radiusext-data0@psg.com; Tue, 15 Jun 2010 18:06:20 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OOaWg-000K8y-C0 for radiusext@ops.ietf.org; Tue, 15 Jun 2010 18:06:18 +0000
Message-ID: <4C17C118.3060009@deployingradius.com>
Date: Tue, 15 Jun 2010 20:06:16 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com>
In-Reply-To: <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson wrote:
> What does the provisioning system do with the information and how does it relate the result back to the NAS?

  It creates FW rules for the user.  It does *not* relay the result back
to the NAS.

> What entity sends the Accounting-Request, the NAS or he RADIUS server.  You use "it" and I'm unclear what "it" refers to.

  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
server originates the Accounting-Request.

  The *intent* appears to be that waiting the extra 1/10s for the NAS to
originate the Accounting-Request would be a catastrophic delay.  The
"network setup" side of the user session needs to be done before the
Access-Accept is received by the NAS.

  The "simplest" way to do this is to overload RADIUS.

> Well, I personally think that provisioning services via an Accounting-Request is bad, but I don't yet see how the NAS is actually being provisioned by a request message.  What is fairly common practice is to build resource management systems around RADIUS Accounting.  Is that the sort of thing you're talking about?

  I can understand making decisions (e.g. Disconnect-Request) on
reception of an Accounting-Request packet.  i.e. "user is over 2G, kick
them off of the net".

  The above discussion isn't that.  It's the RADIUS server *fabricating*
an Accounting-Request packet for a user session, because it's faster to
do it that way than to wait for the NAS.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 11:40:37 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F11B3A69B8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTZu9Okfhj5p for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:40:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5A1BB3A699D for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 11:40:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOb1I-000P2q-KC for radiusext-data0@psg.com; Tue, 15 Jun 2010 18:37:56 +0000
Received: from [207.3.149.133] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1OOb1G-000P2b-Ap for radiusext@ops.ietf.org; Tue, 15 Jun 2010 18:37:54 +0000
Received: (qmail 18091 invoked from network); 15 Jun 2010 18:37:53 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 15 Jun 2010 18:37:53 -0000
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
In-Reply-To: <4C17C118.3060009@deployingradius.com>
Date: Tue, 15 Jun 2010 14:37:53 -0400
Cc: 'radext mailing list' <radiusext@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <53333FD9-4B64-4AEB-8042-8081FBCFF456@elbrysnetworks.com>
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com>
To: Alan DeKok <aland@deployingradius.com>
X-Mailer: Apple Mail (2.1078)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Jun 15, 2010, at 2:06 PM, Alan DeKok wrote:

> It creates FW rules for the user.  It does *not* relay the result back
> to the NAS.

OK, I think I get it.

> The NAS sends an Access-Request to the RADIUS server.
> The RADIUS server originates the Accounting-Request.

To a RADIUS Accounting Server?

Let's see if I've got this....

The NAS (Node A) sends an Access-Request to the RADIUs Server (Node B) =
which then sends an Accounting-Request to the RADIUS Accounting Server =
(Node C), and subsequently the RADIUS Server (Node B) sends an =
Access-Accept to the NAS (Node A)?  The RADIUS Accounting Server (Node =
C) by some means creates access rules for the user and sends them to the =
Firewall (Node D)?

Yikes.

> The *intent* appears to be that waiting the extra 1/10s for the NAS to
> originate the Accounting-Request would be a catastrophic delay.  The
> "network setup" side of the user session needs to be done before the
> Access-Accept is received by the NAS.
>
> The "simplest" way to do this is to overload RADIUS.

Well, RADIUS has a history of being an eminently overload-able protocol. =
 :-)

I think it's unusual, to say the least, for a RADIUS Server to initiate =
a request on behalf of a NAS unless that RADIUS Server is acting in the =
role of RADIUS Proxy Server.  That doesn't seem to be the case here.

Regards,

Dave

David B. Nelson

Elbrys Networks, Inc.
282 Corporate Drive, Unit 1
Portsmouth, NH 03801

+1.603.570.2636
www.elbrysnetworks.com
dnelson@elbrysnetworks.com






--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 11:41:01 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD5113A6879 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.409
X-Spam-Level: *
X-Spam-Status: No, score=1.409 tagged_above=-999 required=5 tests=[AWL=-0.696, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isEBQfYxKWsT for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 11:41:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B731D3A696C for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 11:41:00 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOb2F-000PDq-IJ for radiusext-data0@psg.com; Tue, 15 Jun 2010 18:38:55 +0000
Received: from [65.55.116.14] (helo=blu0-omc1-s3.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OOb2D-000PDG-Eb for radiusext@ops.ietf.org; Tue, 15 Jun 2010 18:38:53 +0000
Received: from BLU137-DS9 ([65.55.116.9]) by blu0-omc1-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 15 Jun 2010 11:38:52 -0700
X-Originating-IP: [75.164.156.18]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>, "'David B. Nelson'" <dnelson@elbrysnetworks.com>
CC: "'radext mailing list'" <radiusext@ops.ietf.org>
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com>
In-Reply-To: <4C17C118.3060009@deployingradius.com>
Subject: RE: Is provisioning services in Accounting-Request packets bad?
Date: Tue, 15 Jun 2010 11:40:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsMtgeGNdw3k5GUQAi7QrdKaWVc3wAA9jig
Content-Language: en-us
X-OriginalArrivalTime: 15 Jun 2010 18:38:52.0899 (UTC) FILETIME=[00EA3330:01CB0CBA]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok said:

"  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
server originates the Accounting-Request."

So this requires the NAS to act as an Accounting Server?  

What if doesn't respond?  Does the RADIUS server keep retransmitting the
Accounting-Request??


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 12:08:57 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 610B73A6983 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 12:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.023
X-Spam-Level: *
X-Spam-Status: No, score=1.023 tagged_above=-999 required=5 tests=[AWL=-0.341, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id enKIjS-s+2yW for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 12:08:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4D99F3A699D for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 12:08:56 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OObRP-0003KF-O1 for radiusext-data0@psg.com; Tue, 15 Jun 2010 19:04:55 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OObRN-0003Jo-3s for radiusext@ops.ietf.org; Tue, 15 Jun 2010 19:04:53 +0000
Message-ID: <4C17CED3.90500@deployingradius.com>
Date: Tue, 15 Jun 2010 21:04:51 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <53333FD9-4B64-4AEB-8042-8081FBCFF456@elbrysnetworks.com>
In-Reply-To: <53333FD9-4B64-4AEB-8042-8081FBCFF456@elbrysnetworks.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson wrote:
>> The NAS sends an Access-Request to the RADIUS server.
>> The RADIUS server originates the Accounting-Request.
> 
> To a RADIUS Accounting Server?

  Nope.  To a provisioning system.  e.g. firewall.  It opens FW rules
for the IP, send an ACK, and otherwise discards the accounting data.

  The normal accounting stream still exists, and uses a completely
different path through the network.

> Let's see if I've got this....
> 
> The NAS (Node A) sends an Access-Request to the RADIUs Server (Node B) which then sends an Accounting-Request to the RADIUS Accounting Server (Node C), and subsequently the RADIUS Server (Node B) sends an Access-Accept to the NAS (Node A)?  The RADIUS Accounting Server (Node C) by some means creates access rules for the user and sends them to the Firewall (Node D)?
> 
> Yikes.

  Something like that.

>> The *intent* appears to be that waiting the extra 1/10s for the NAS to
>> originate the Accounting-Request would be a catastrophic delay.  The
>> "network setup" side of the user session needs to be done before the
>> Access-Accept is received by the NAS.
>>
>> The "simplest" way to do this is to overload RADIUS.
> 
> Well, RADIUS has a history of being an eminently overload-able protocol.  :-)
> 
> I think it's unusual, to say the least, for a RADIUS Server to initiate a request on behalf of a NAS unless that RADIUS Server is acting in the role of RADIUS Proxy Server.  That doesn't seem to be the case here.

  Yup.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 12:32:59 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B39B3A67A2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 12:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.061
X-Spam-Level: *
X-Spam-Status: No, score=1.061 tagged_above=-999 required=5 tests=[AWL=-0.303, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QqbQ2FvjoUdl for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 12:32:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EE2BD3A68BE for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 12:32:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OObqS-0006fK-Tr for radiusext-data0@psg.com; Tue, 15 Jun 2010 19:30:48 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OObqQ-0006eb-5Z for radiusext@ops.ietf.org; Tue, 15 Jun 2010 19:30:46 +0000
Message-ID: <4C17D4E3.10308@deployingradius.com>
Date: Tue, 15 Jun 2010 21:30:43 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: "David B. Nelson" <dnelson@elbrysnetworks.com>,  radext mailing list <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <020DF101-49BC-433F-87F9-A22B4FD5B0DD@bridgewatersystems.com>
In-Reply-To: <020DF101-49BC-433F-87F9-A22B4FD5B0DD@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> On one hand we may need more information as David is mentioning.
> 
> But there is nothing wrong with a Back office system using information contained in an accounting message.

  Absolutely.

> A back office system can be used for billing but it can also be used to do other things like generate triggers for Intrussion Detection/Prevention systems, Firewalls etc etc....
> 
> And thus some of the information could be used for provisioning of some service by a back office system.
> 
> We should not be concerned about this.  It has nothing to do with the over the wire protocol.  As long as the information is valid to be sent in the Accounting Messages we should be fine.

  My main issue is that accounting packets should be generated by the
system managing the user session. i.e. the NAS.  Anything else in the
network (e.g. RADIUS proxy) has no business "inventing" accounting
packets for a session.

  That strikes me as an odd way of creating a vendor-specific
provisioning API.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 12:37:44 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 997983A6974 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 12:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.162
X-Spam-Level: 
X-Spam-Status: No, score=0.162 tagged_above=-999 required=5 tests=[AWL=0.657, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKM7u4TKTTjr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 12:37:43 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0E0ED3A6972 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 12:37:43 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OObut-0007Hk-3a for radiusext-data0@psg.com; Tue, 15 Jun 2010 19:35:23 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OObuq-0007HP-1r for radiusext@ops.ietf.org; Tue, 15 Jun 2010 19:35:20 +0000
Message-ID: <4C17D5F7.3030408@deployingradius.com>
Date: Tue, 15 Jun 2010 21:35:19 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,  'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl>
In-Reply-To: <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> Alan DeKok said:
> 
> "  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
> server originates the Accounting-Request."
> 
> So this requires the NAS to act as an Accounting Server?  

  Nope.  A third machine receives the Accounting-Request.

> What if doesn't respond?  Does the RADIUS server keep retransmitting the
> Accounting-Request??

  Nope.  The time frames are 'too short' for retransmits to be relevant.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 15:42:08 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76B493A6925 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 15:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.195
X-Spam-Level: 
X-Spam-Status: No, score=-3.195 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYcnbPEavLdS for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 15:42:05 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B94043A68DF for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 15:42:03 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOekn-0004aj-5C for radiusext-data0@psg.com; Tue, 15 Jun 2010 22:37:09 +0000
Received: from [216.82.249.147] (helo=mail29.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OOekk-0004aU-QT for radiusext@ops.ietf.org; Tue, 15 Jun 2010 22:37:06 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-14.tower-29.messagelabs.com!1276641423!62786923!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 10710 invoked from network); 15 Jun 2010 22:37:04 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-14.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jun 2010 22:37:04 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Tue, 15 Jun 2010 18:37:03 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Date: Tue, 15 Jun 2010 18:37:01 -0400
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Thread-Topic: Is provisioning services in Accounting-Request packets bad?
Thread-Index: AcsM20X61gHdrf9rT/y6Qdh1huzujA==
Message-ID: <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com>
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl> <4C17D5F7.3030408@deployingradius.com>
In-Reply-To: <4C17D5F7.3030408@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Okay.  I think I understand....

The RADIUS server sends an access-accept to the NAS and at the same time mo=
re or less, it sends an Accounting Request message to the Back Office to pr=
ovisiong something (a firewall).

Weird.  This is instead of the NAS generating an accounting request message=
.

But given that what is wrong with this?

For one, the session may not have started on the NAS so you have provisione=
d something that may have not happened.  In the case of the FW, this could =
be bad - you opened a hole for something that isnt really there etc.

But is this still problematic in general.

The general case is:

1) Does the specification require that an Accounting message be generate by=
 a NAS only.  Or can it be generated by a proxy or server?

2) Does the specification allow a Proxy to add attributes to accounting. =20

The answer to 2 is yes.

I am not sure what the answer to one should be.  I would think no. But ther=
e could be corner cases where the real NAS cant generate accounting and the=
 next hop AAA proxy can.  Certainly in some deployments the NAS is not real=
ly a single entity.  So  making a rule could break these corner cases.

But what is the real problem here? Other than potential problems for partic=
ular use cases.  I think we should remain silent.


On 15-06-2010, at 15:35 , Alan DeKok wrote:

> Bernard Aboba wrote:
>> Alan DeKok said:
>>=20
>> "  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
>> server originates the Accounting-Request."
>>=20
>> So this requires the NAS to act as an Accounting Server? =20
>=20
>  Nope.  A third machine receives the Accounting-Request.
>=20
>> What if doesn't respond?  Does the RADIUS server keep retransmitting the
>> Accounting-Request??
>=20
>  Nope.  The time frames are 'too short' for retransmits to be relevant.
>=20
>  Alan DeKok.
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 15 23:31:52 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A31B83A6851 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 23:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.032
X-Spam-Level: *
X-Spam-Status: No, score=1.032 tagged_above=-999 required=5 tests=[AWL=-0.332, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1miiGFqHdC2N for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 15 Jun 2010 23:31:51 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6D2A23A68E8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 15 Jun 2010 23:31:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOm5w-000NNd-FE for radiusext-data0@psg.com; Wed, 16 Jun 2010 06:27:28 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OOm5t-000NMw-PF for radiusext@ops.ietf.org; Wed, 16 Jun 2010 06:27:26 +0000
Message-ID: <4C186EC8.6070802@deployingradius.com>
Date: Wed, 16 Jun 2010 08:27:20 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl> <4C17D5F7.3030408@deployingradius.com> <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com>
In-Reply-To: <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> Okay.  I think I understand....
> 
> The RADIUS server sends an access-accept to the NAS and at the same time more or less, it sends an Accounting Request message to the Back Office to provisiong something (a firewall).
>
> Weird.  This is instead of the NAS generating an accounting request message.

  Yes. and yes.

> But given that what is wrong with this?
> 
> For one, the session may not have started on the NAS so you have provisioned something that may have not happened.  In the case of the FW, this could be bad - you opened a hole for something that isnt really there etc.

  Sure.  But RADIUS isn't really a generic provisioning API.

> But is this still problematic in general.
> 
> The general case is:
> 
> 1) Does the specification require that an Accounting message be generate by a NAS only.  Or can it be generated by a proxy or server?

  The "naive" expectation is that accounting messages are tied to
sessions, and generated by the same system that originated the
Access-Request.

> I am not sure what the answer to one should be.  I would think no. But there could be corner cases where the real NAS cant generate accounting and the next hop AAA proxy can.  Certainly in some deployments the NAS is not really a single entity.  So  making a rule could break these corner cases.

  Sure.  If the same "administrative system" creates Access-Requests &&
Accounting-Requests, it doesn't matter which box creates what, so long
as they all communicate.  But that's very different from having the
system sending an Access-Accept create an Accounting-Request packet.

> But what is the real problem here? Other than potential problems for particular use cases.  I think we should remain silent.

  It complicates network design.  It potentially allows for unlimited
growth in the number of RADIUS packets based on a login.  If the
Access-Request is proxied multiple times. and each proxy "invents"
another RADIUS packet... bad things can happen.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun 16 05:44:24 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20D0F3A6A30 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 16 Jun 2010 05:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level: 
X-Spam-Status: No, score=-3.1 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqVBRgx8xNvW for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 16 Jun 2010 05:44:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7CD443A68C7 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 16 Jun 2010 05:44:22 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOrrO-000NsZ-72 for radiusext-data0@psg.com; Wed, 16 Jun 2010 12:36:50 +0000
Received: from [216.82.249.147] (helo=mail29.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1OOrrL-000NsD-DY for radiusext@ops.ietf.org; Wed, 16 Jun 2010 12:36:47 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-14.tower-29.messagelabs.com!1276691805!62952539!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 27904 invoked from network); 16 Jun 2010 12:36:46 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-14.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 16 Jun 2010 12:36:46 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Wed, 16 Jun 2010 08:36:44 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Date: Wed, 16 Jun 2010 08:36:42 -0400
Subject: RE: Is provisioning services in Accounting-Request packets bad?
Thread-Topic: Is provisioning services in Accounting-Request packets bad?
Thread-Index: AcsNHPtiF3nn5/T5R3aCuMBzVo3OTQAL4+Yw
Message-ID: <AF6CC6ADFC631348B9C22998A699B9EC593FD7A2@m679t05.fpmis.bridgewatersys.com>
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl> <4C17D5F7.3030408@deployingradius.com> <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com> <4C186EC8.6070802@deployingradius.com>
In-Reply-To: <4C186EC8.6070802@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

See inline..

BTW I am not defending the specific use case  - and I am not critizing it e=
ither.  I don't have enough information.

I am concerned though that we may put in place rules/guidelines that would =
hinder good network design.

So specifically:

>   Sure.  But RADIUS isn't really a generic provisioning API.
[AL>] You are right RADIUS isn't a provisioning API or a provisioning syste=
m.  But the information obtained from RADIUS is being used to provision som=
ething.  Just like RADIUS is not a billing API nor a Billing system but rat=
her the information provided by RADIUS is useful in generating a bill for t=
he subscriber. =20
The information being generated by RADIUS is used for many purposes.

In this particular case I think your issue is with using accounting message=
s to provision a firewall.  I think it is that the accounting message is ge=
nerated along the proxy chain (okay the extreme end of the proxy chain but =
nevertheless the proxy chain). Right?


>   The "naive" expectation is that accounting messages are tied to
> sessions, and generated by the same system that originated the
> Access-Request.
[AL>] The accounting message is still being tied to a session in this case.=
  And it is the same system.  The system appears to be distributed.  The re=
al problem is that it is generated by the "same system that originated the =
Access-Request" Right?

>=20
> > I am not sure what the answer to one should be.  I would think no.
> But there could be corner cases where the real NAS cant generate
> accounting and the next hop AAA proxy can.  Certainly in some
> deployments the NAS is not really a single entity.  So  making a rule
> could break these corner cases.
>=20
>   Sure.  If the same "administrative system" creates Access-Requests &&
> Accounting-Requests, it doesn't matter which box creates what, so long
> as they all communicate.  But that's very different from having the
> system sending an Access-Accept create an Accounting-Request packet.

In the specific use case, the logical entities are all communicating.  I am=
 not sure what you mean by "Administrative System".  Who is to say that the=
 NAS and Server or not in the same adimistrative domain.  I don't know much=
 details about the use case.  I don't know what the Admisitrative Domain ha=
s to do with this?

>=20
> > But what is the real problem here? Other than potential problems for
> particular use cases.  I think we should remain silent.
>=20
>   It complicates network design.  It potentially allows for unlimited
> growth in the number of RADIUS packets based on a login.  If the
> Access-Request is proxied multiple times. and each proxy "invents"
> another RADIUS packet... bad things can happen.

Sure.  But who is to say that following a similar approach wouldn't simplif=
y the network design.  We don't know enough details but perhaps in this cas=
e this was the best most economical approach to the problem.  It seems weir=
d sitting at the IETF level. =20

I am not sure what general guidance you would propose here that would help =
and not hinder.

>=20
>   Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun 16 06:58:28 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AFFE3A6863 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 16 Jun 2010 06:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQ9jJKvRyfLz for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 16 Jun 2010 06:58:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 080013A687D for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 16 Jun 2010 06:58:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOt4f-000BIZ-0I for radiusext-data0@psg.com; Wed, 16 Jun 2010 13:54:37 +0000
Received: from [207.3.149.133] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1OOt4Z-000BET-Ct for radiusext@ops.ietf.org; Wed, 16 Jun 2010 13:54:31 +0000
Received: (qmail 29282 invoked from network); 16 Jun 2010 13:54:29 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 16 Jun 2010 13:54:29 -0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: Is provisioning services in Accounting-Request packets bad?
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
In-Reply-To: <AF6CC6ADFC631348B9C22998A699B9EC593FD7A2@m679t05.fpmis.bridgewatersys.com>
Date: Wed, 16 Jun 2010 09:54:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <12E28CA6-108B-43E1-87FF-7FDC056B0BB9@elbrysnetworks.com>
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl> <4C17D5F7.3030408@deployingradius.com> <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com> <4C186EC8.6070802@deployingradius.com> <AF6CC6ADFC631348B9C22998A699B9EC593FD7A2@m679t05.fpmis.bridgewatersys.com>
To: radext mailing list <radiusext@ops.ietf.org>
X-Mailer: Apple Mail (2.1078)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Jun 16, 2010, at 8:36 AM, Avi Lior wrote:

> I am not sure what general guidance you would propose here that would =
help and not hinder.

I'm not sure where such guidance would be delivered.  This is not a =
matter of RADIUS Attribute design, and it's out scope for the Design =
Guidelines.  It seems to me this is (or is not) a deviation from the =
RADIUS operational model, depending on your interpretation.

It may well be a reasonable solution in a given set or circumstances.  =
It certainly does not follow the "conservative" or "narrow" =
interpretation of the RADIUS operational model (command level data =
flow).  This is fine as a proprietary vendor extension to RADIUS.  My =
only concern would be if this kind of adaptation were to become popular, =
and customers created a demand to replicate this solution in other use / =
deployment cases, where it may not be appropriate.  I would not like to =
see this sort of solution evolve to become a de facto or de jure =
extension to the RADIUS standard.




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun 16 07:58:16 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F41C83A68E9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 16 Jun 2010 07:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.059
X-Spam-Level: *
X-Spam-Status: No, score=1.059 tagged_above=-999 required=5 tests=[AWL=-0.305, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCWc0rf2KF8c for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 16 Jun 2010 07:58:14 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9B7023A691B for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 16 Jun 2010 07:58:14 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OOu0D-000LKN-4S for radiusext-data0@psg.com; Wed, 16 Jun 2010 14:54:05 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OOu0A-000LJp-0l for radiusext@ops.ietf.org; Wed, 16 Jun 2010 14:54:02 +0000
Message-ID: <4C18E587.8050008@deployingradius.com>
Date: Wed, 16 Jun 2010 16:53:59 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
References: <4C17A33D.2090405@deployingradius.com> <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com> <4C17C118.3060009@deployingradius.com> <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl> <4C17D5F7.3030408@deployingradius.com> <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com> <4C186EC8.6070802@deployingradius.com> <AF6CC6ADFC631348B9C22998A699B9EC593FD7A2@m679t05.fpmis.bridgewatersys.com>
In-Reply-To: <AF6CC6ADFC631348B9C22998A699B9EC593FD7A2@m679t05.fpmis.bridgewatersys.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> In this particular case I think your issue is with using accounting messages to provision a firewall.  I think it is that the accounting message is generated along the proxy chain (okay the extreme end of the proxy chain but nevertheless the proxy chain). Right?

  Yes.

> [AL>] The accounting message is still being tied to a session in this case.  And it is the same system.  The system appears to be distributed.  The real problem is that it is generated by the "same system that originated the Access-Request" Right?

  Yes.

> In the specific use case, the logical entities are all communicating.  I am not sure what you mean by "Administrative System".  Who is to say that the NAS and Server or not in the same adimistrative domain.  I don't know much details about the use case.  I don't know what the Admisitrative Domain has to do with this?

  What I mean is that the "NAS" functionality may be split across more
than 1 machine.  If so, they are all managed by the same people.

> Sure.  But who is to say that following a similar approach wouldn't simplify the network design.  We don't know enough details but perhaps in this case this was the best most economical approach to the problem.  It seems weird sitting at the IETF level.  
> 
> I am not sure what general guidance you would propose here that would help and not hinder.

  RADIUS isn't a generic provisioning system?

  I could use accounting packets to provision new users, rather than
using direct DB writes.  If the administration system doesn't have write
access to the database, it could use RADIUS to send the new user
credentials to the RADIUS server, which would write them to the DB.

  It's possible, but weird, and likely not recommended.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 12:23:59 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFD9B3A68A5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 12:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.945
X-Spam-Level: *
X-Spam-Status: No, score=1.945 tagged_above=-999 required=5 tests=[AWL=-1.160, BAYES_60=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBx80eVqWE2O for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 12:23:58 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8F3473A6801 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 12:23:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQQ38-0002lo-NF for radiusext-data0@psg.com; Sun, 20 Jun 2010 19:19:22 +0000
Received: from [65.55.116.35] (helo=blu0-omc1-s24.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OQQ35-0002lD-Qf for radiusext@ops.ietf.org; Sun, 20 Jun 2010 19:19:20 +0000
Received: from BLU137-W2 ([65.55.116.9]) by blu0-omc1-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 20 Jun 2010 12:19:19 -0700
Message-ID: <BLU137-W2472BAA74908C6D1297B693C20@phx.gbl>
Content-Type: multipart/alternative; boundary="_7e63b6a6-9866-4661-97ea-2f5523cc45c2_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Meeting week of July 12
Date: Sun, 20 Jun 2010 12:19:18 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Jun 2010 19:19:19.0355 (UTC) FILETIME=[7B42C0B0:01CB10AD]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_7e63b6a6-9866-4661-97ea-2f5523cc45c2_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


We are looking at potentially scheduling a RADEXT Virtual Interim meeting t=
he week of July 12=2C 2010.=20

Please fill out a Doodle Poll indicating your availability:
http://www.doodle.com/362t54udqbbkupdp
 		 	   		  =

--_7e63b6a6-9866-4661-97ea-2f5523cc45c2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
We are looking at potentially scheduling a RADEXT Virtual Interim meeting t=
he week of July 12=2C 2010. <br><br>Please fill out a Doodle Poll indicatin=
g your availability:<br>http://www.doodle.com/362t54udqbbkupdp<br> 		 	   	=
	  </body>
</html>=

--_7e63b6a6-9866-4661-97ea-2f5523cc45c2_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 13:01:02 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBBC63A68AD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 13:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.359
X-Spam-Level: 
X-Spam-Status: No, score=-102.359 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNRsLQFhpCZk for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 13:01:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8D1D53A67EC for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 13:01:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQQb4-0006sh-EL for radiusext-data0@psg.com; Sun, 20 Jun 2010 19:54:26 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQQb2-0006sB-0K for radiusext@ops.ietf.org; Sun, 20 Jun 2010 19:54:24 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQQaz-0000Nw-3a; Sun, 20 Jun 2010 12:54:21 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Sun, 20 Jun 2010 19:54:21 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #26: Terminology (Section 1.1)
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/26
Message-ID: <066.bb35d2e7170fe573be2872ab6e28e60f@tools.ietf.org>
X-Trac-Ticket-ID: 26
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#26: Terminology (Section 1.1)
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 standard space
      The 256 possible attributes that follow the format defined in
      [RFC2865] Section 5.

 vendor space
      The contents of the "String" field of a Vendor-Specific Attribute
       (VSA) ([RFC2865] Section 5.26).

 [BA] Given the extended attribute work, we may not want to define the
 standard space a bit more flexibly.  Also, the definition of vendor space
 should take the vendor-type field into account, no?
 Recommend this be changed to:

 standard space
      RADIUS attributes which are allocated by IANA and which follow the
 format defined in RFC 2865 [RFC2865] Section 5.

 vendor space
     The contents of the "String" field of a Vendor-Specific Attribute
 (VSA), as defined in [RFC2865] Section 5.26.  These attributes provide a
 unique attribute space for each vendor (identified by the Vendor-Type
 field) which they can self-allocate."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/26>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 16:38:56 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8C2D3A6916 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 16:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.361
X-Spam-Level: 
X-Spam-Status: No, score=-102.361 tagged_above=-999 required=5 tests=[AWL=0.239, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VL-4UhAFDBRw for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 16:38:54 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DDEF73A6915 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 16:38:53 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQU2T-00037r-Mf for radiusext-data0@psg.com; Sun, 20 Jun 2010 23:34:57 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQU2Q-00037X-Vd for radiusext@ops.ietf.org; Sun, 20 Jun 2010 23:34:55 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQU2M-0007cN-Mm; Sun, 20 Jun 2010 16:34:51 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Sun, 20 Jun 2010 23:34:50 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #27: Section 1.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/27
Message-ID: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
X-Trac-Ticket-ID: 27
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#27: Section 1.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Section 1.3 needs to describe the situations in which this document
 applies.  As discussed as part of the resolution of Issue 327, there are
 situations where vendors and SDOs will choose to not satisfy the
 guidelines.  Also, there is other work in progress (e.g. Extended
 Attributes).

 My recommendation is to replace Section 1.3 with the following:

 1.3 Applicability

    The advice in this document applies to attributes used to
    encode service-provisioning, authentication, or accounting data,
    based on the attribute encodings and data formats defined in RFC 2865
    [RFC2865], RFC 2866 [RFC2866] and subsequent RADIUS RFCs.

    Since this document represents a Best Current Practice, it does not
    update or deprecate existing standards.  As a result, the uses of
    the terms "MUST" and "MUST NOT" are limited to requirements already
    present in existing documents.

    It is RECOMMENDED that these guidelines be followed for all new RADIUS
    specifications, whether they originate from a vendor, an SDO, or the
 IETF.
    Doing so will ensure the widest possible applicability and
 interoperability
    of the specifications, while requiring minimal changes to existing
 systems.
    In particular, it is expected that RADIUS specifications requesting
    allocation within the standards space will follow these guidelines,
    and will explain why this is not possible if they cannot.

    However, there are situations in which vendors or SDOs can choose not
    to follow these guidelines without major consequences.  As noted in
    [RFC2865] Section 5.26, Vendor-Specific Attributes (VSAs) are
    "available to allow vendors to support their own extended Attributes
 not
    suitable for general usage."  Where vendors or SDOs develop
    specificatons "not suitable for general usage", limited
 interoperability
    and inability to use existing implementations may be acceptable and
    in these situations, vendors and SDOs MAY NOT choose to conform to
 these
    guidelines.

    Note that the RADEXT WG is currently involved in the development of an
    Extended Attributes specification [EXTEN].  This specification, when
    completed, will provide its own usage guidelines.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/27>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 16:41:31 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 276A23A691A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 16:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level: 
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtYMrT9kcGBP for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 16:41:30 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 031CA3A6919 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 16:41:30 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQU6F-0003SD-GD for radiusext-data0@psg.com; Sun, 20 Jun 2010 23:38:51 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQU6D-0003Rs-6c for radiusext@ops.ietf.org; Sun, 20 Jun 2010 23:38:49 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQU6B-0007jJ-Ip; Sun, 20 Jun 2010 16:38:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Sun, 20 Jun 2010 23:38:47 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #28: Section 1.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/28
Message-ID: <066.21f1182b696155b3e3e204d3d7194146@tools.ietf.org>
X-Trac-Ticket-ID: 28
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

 [BA] Since elements of this paragraph have been incorporated into the
 proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
 Section 6 appears restricts usage of "MUST" and "MUST NOT":

    We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/28>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 16:42:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 282643A691C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 16:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level: 
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9PVtAvGiqul for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 16:42:28 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id ED2EC3A691A for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 16:42:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQU7H-0003YR-S5 for radiusext-data0@psg.com; Sun, 20 Jun 2010 23:39:55 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQU7F-0003Xw-Jn for radiusext@ops.ietf.org; Sun, 20 Jun 2010 23:39:53 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQU7E-0007oo-5R; Sun, 20 Jun 2010 16:39:52 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Sun, 20 Jun 2010 23:39:52 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #28: Section 1.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/28#comment:1
Message-ID: <075.526d29e14060cfe24f83d4961005d0a1@tools.ietf.org>
References: <066.21f1182b696155b3e3e204d3d7194146@tools.ietf.org>
X-Trac-Ticket-ID: 28
In-Reply-To: <066.21f1182b696155b3e3e204d3d7194146@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
Description changed by bernard_aboba@…:

Old description:

> We emphasize that the uses of "MUST" and "MUST NOT" in this document
>    are limited to requirements to follow the IETF process for IETF
>    standards, and quotes from other documents.  As a result, the uses of
>    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
>    behavior within implementations.
>
> [BA] Since elements of this paragraph have been incorporated into the
> proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
> Section 6 appears restricts usage of "MUST" and "MUST NOT":
>
>    We emphasize that the uses of "MUST" and "MUST NOT" in this document
>    are limited to requirements to follow the IETF process for IETF
>    standards, and quotes from other documents.  As a result, the uses of
>    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
>    behavior within implementations.

New description:

 We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

 [BA] Since elements of this paragraph have been incorporated into the
 proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
 Section 6 appears restricts usage of "MUST" and "MUST NOT":

     Imperatives of the type defined in this memo must be used with care
    and sparingly.  In particular, they MUST only be used where it is
    actually required for interoperation or to limit behavior which has
    potential for causing harm (e.g., limiting retransmisssions)  For
    example, they must not be used to try to impose a particular method
    on implementors where the method is not required for
    interoperability.

--

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/28#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 20:39:51 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 101B63A6A02 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 20:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUqUnTNC4VVA for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 20:39:46 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D217D3A67D9 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 20:39:42 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQXn6-000F0t-Kj for radiusext-data0@psg.com; Mon, 21 Jun 2010 03:35:20 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQXn4-000F0g-AZ for radiusext@ops.ietf.org; Mon, 21 Jun 2010 03:35:18 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQXn0-0001bH-1z; Sun, 20 Jun 2010 20:35:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 03:35:13 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #27: Section 1.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/27#comment:1
Message-ID: <075.f9de9721aba99e8222bb62d2689fb0fc@tools.ietf.org>
References: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
X-Trac-Ticket-ID: 27
In-Reply-To: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#27: Section 1.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  critical                   |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…


Comment:

 Please add the following paragraph to the end of Section 1.3:

    RADIUS protocol changes, or specification of attributes (such as
    Service-Type) that can, in effect, provide new RADIUS commands
    require greater expertise and deeper review, as do changes to the
    RADIUS operational model.  As a result, such changes are outside the
    scope of this document and MUST NOT be undertaken outside the IETF.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/27#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 21:11:01 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50E943A6A07 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 21:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.369
X-Spam-Level: 
X-Spam-Status: No, score=-102.369 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3RPCP79SSWRA for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 21:10:54 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E5A5F3A6A10 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 21:10:53 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQYI7-000IJh-VQ for radiusext-data0@psg.com; Mon, 21 Jun 2010 04:07:23 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQYI5-000IJB-3Y for radiusext@ops.ietf.org; Mon, 21 Jun 2010 04:07:21 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQYI2-00058X-JF; Sun, 20 Jun 2010 21:07:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 04:07:18 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #29: Section 2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/29
Message-ID: <066.9278f2fd2da1a1adf9153579ef1ae1c5@tools.ietf.org>
X-Trac-Ticket-ID: 29
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#29: Section 2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:            
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Section 2 currently repeats text from other sections and utilizes MUST n
 MUST NOT normative language outside the bounds suggested in RFC 2119.

 A suggested rewrite is as follows:

 2. Guidelines

    The Remote Authentication Dial In User Service (RADIUS) defined in
    [RFC2865] and [RFC2866] uses elements known as attributes in order to
    represent authentication, authorization and accounting data.

    Unlike SNMP, first defined in [RFC1157] and [RFC1155], RADIUS does
    not define a formal data definition language.  The data type of
    RADIUS attributes is not transported on the wire.  Rather, the data
    type of a RADIUS attribute is fixed when an attribute is defined.
    Based on the RADIUS attribute type code, RADIUS clients and servers
    can determine the data type based on preconfigured entries within a
    data dictionary.

    To explain the implications of this early RADIUS design decision we
    distinguish two types of data types, namely "basic" and "complex".
    Basic data types use one of the existing RADIUS data types as defined
    below, encapsulated in a RADIUS attribute or VSA.  All other data
    formats are "complex types".

    RADIUS attributes can be classified into three broad categories:

       * Attributes that are of interest to a single vendor, e.g., for a
         product or product line.  Minimal cross-vendor interoperability
         is needed.  Vendor-Specific Attributes (VSAs) are appropriate
         for this purpose.  Code-point allocation is managed by each
         vendor, with the number space defined by their Private Enterprise
         Number (PEN).

       * Attributes that are of interest to an industry segment, where an
         SDO defines the attributes for that industry.  Multi-vendor
         interoperability within an industry segment is expected.

         Vendor-Specific Attributes (VSAs) are appropriate for
         use in this situation.  Code-point allocation is managed by
         the SDO with the number space defined by the SDO's PEN,
         rather then the PEN of an individual vendor.

       * Attributes that are of broad interest to the Internet Community.
         Multi-vendor interoperability is expected.

         Attributes within the standards space are appropriate for this
         purpose, and are allocated via IANA as described in [RFC3575].
         Since the standards space represents a finite resource,
         and is the only attribute space available for use by IETF working
 groups,
         vendors and SDOs are encouraged to utilize the VSA space, rather
 than
         requesting allocation of attributes from the standards space.
         Self-allocation of standards attributes is considered anti-social
         behavior and is strongly discouraged.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/29>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 21:54:02 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC95F3A6A21 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 21:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.164
X-Spam-Level: 
X-Spam-Status: No, score=-101.164 tagged_above=-999 required=5 tests=[AWL=-0.978, BAYES_40=-0.185, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ySjpa76qycwF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 21:54:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id CC0383A686B for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 21:53:59 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQYu5-000ML7-Te for radiusext-data0@psg.com; Mon, 21 Jun 2010 04:46:37 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQYu3-000MKf-6O for radiusext@ops.ietf.org; Mon, 21 Jun 2010 04:46:35 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQYu0-0005Xj-Ap; Sun, 20 Jun 2010 21:46:32 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 04:46:32 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #30: Section 1.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/30
Message-ID: <066.662d4351e84edff3e03f1dd33c281067@tools.ietf.org>
X-Trac-Ticket-ID: 30
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#30: Section 1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Material relating to reviews is included in various places within the
 document.  My recommendation is to delete Section 3.3.4 and to
 combine material relating to reviews into Section 1.4:

 1.4 Reviews

    For specifications utilizing attributes within the standards
    space, conformance with the design guidelines in this document
    is expected unless a good case can be made for an exception.
    Reviewers SHOULD use the design guidelines as a review
    checklist.

    While not required, IETF review may also be beneficial for
 specifications
    utilizing the Vendor-Specific space. Experience has shown that
 attributes
    not originally designed for general usage can subsequently garner
    wide-spread deployment.  An example is the vendor-specific attributes
    defined in [RFC2548], which have been widely implemented within
    IEEE 802.11 Access Points.

    In order to assist in the development of specifications
    conforming to these guidelines, authors can request review by
    sending email to the AAA Doctors [DOCTORS] or equivalent mailing list.
    The IETF Operations & Management Area Directors will then arrange for
    the review to be completed and posted to the AAA Doctors mailing list
    [DOCTORS], RADEXT WG mailing list, or other IETF mailing list.
    Since reviews are handled by volunteers, responses are provided on a
    best-effort basis, with no service level guarantees.  Authors are
    encouraged to seek review as early as possible, so as to
    avoid potential delays.

    In order to provide reviewers with access to the specification, vendors
    and SDOs are encouraged to make them publicly available.
    Where the RADIUS specification is embedded within a larger document
    which cannot be made public, the RADIUS attribute and value
    definitions can be made available on a public web site or can be
    published as an Informational RFC, as with [RFC4679].

    The review process requires neither allocation of attributes within
    the IETF standard attribute space nor publication of an IETF RFC.
    Requiring SDOs or vendors to rehost VSAs into the IETF standards
    attribute space solely for the purpose of obtaining review would put
    pressure on the standards space, and may be harmful to
    interoperability, since would create two ways to provision the same
    service.  Rehosting may also require changes to the RADIUS data model
    which will affect implementations that do not intend to support the
    SDO or vendor specifications.

    Similarly, vendors are encouraged to make their specifications
    publicly available, for maximum interoperability.  However, it is not
    necessary for a vendor to request publication of a VSA specification
    as an Informational RFC by the IETF.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/30>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:11:04 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 533883A6A1E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level: 
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QUj77A1whVwa for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:11:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7D21A3A6A21 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:11:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQa9l-00068Y-5R for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:06:53 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQa9h-00067y-Du for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:06:50 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQa9e-0002Ij-L5; Sun, 20 Jun 2010 23:06:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:06:46 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #31: Section 2.1
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/31
Message-ID: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
X-Trac-Ticket-ID: 31
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#31: Section 2.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 All other data formats are defined to be "complex data types", and
    are NOT RECOMMENDED for normal use.  Nested attributes, or attributes
    grouped via methods other than defined in [RFC2868] do not qualify as
    "basic data types", and SHOULD NOT be used.

    There may be situations where complex attributes are acceptable
    because they reduce complexity in non-RADIUS systems, or because
    leveraging the basic data types would be awkward.  Unfortunately,
    there are no "hard and fast" rules for where the complexity would
    best be located.  Each situation has to be decided on a case-by-case
    basis.  The cost-benefit trade-off may result in a "complex data
    type" being defined in RADIUS, as discussed in Appendix B.  When this
    is done, an explanation SHOULD be offered as to why the complex data
    type was used.

 [BA] The first paragraph could be mis-construed as prohibiting grouping
 mechanisms such as the Extended Attributes approach.

 Recommended replacement:

    All other data formats (including nested attributes) are defined
    to be "complex data types", and are NOT RECOMMENDED for normal
    use.  Complex data types MAY be used in situations where they
    reduce complexity in non-RADIUS systems, or where using
    the basic data types would be awkward (such as where grouping
    would be required in order to link related attributes).  Since
    there are no "hard and fast" rules for where complexity is best
    located, each situation has to be decided on a case-by-case
    basis.  Examples of this tradeoff are discussed in Appendix B.
    Where a complex data type is selected, an explanation SHOULD be
    offered as to why this was necessary.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/31>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:26:05 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56E103A6A29 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level: 
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvyxodby8C1s for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:26:04 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EEB853A6807 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:26:03 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQaOM-00085f-PH for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:21:58 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQaOK-00085A-DR for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:21:56 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQaOI-0003NR-I1; Sun, 20 Jun 2010 23:21:54 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:21:54 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #32: Section 2.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/32
Message-ID: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org>
X-Trac-Ticket-ID: 32
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#32: Section 2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 As noted in this Section, VSA data formats are under the sole discretion
 of SDOs and vendors.  This point should be made up front.

 Recommended change is to replace Section 2.2 with the following:

  2.2. Vendor-Specific Attribute Space

    The Vendor-Specific Attribute space is defined to be the contents of
    the "String" field of the Vendor-Specific Attribute ([RFC2865]
    Section 5.26).  As discussed there, it is intended for vendors and
    SDOs to support their own Attributes not suitable for general use.

    While the encoding of attributes within the vendor space is under
    the control of vendors and SDOs, following the guidelines described
    here is advantageous since it enables maximum interoperability with
    minimal changes to existing systems.

    For example, RADIUS server support for new attributes using
    "basic data types" can typically be accomplished by editing
    a RADIUS dictionary, whereas "complex data types" typically
    require RADIUS server code changes, which can add complexity
    and delays in implementation.

    Vendor RADIUS Attribute specifications SHOULD self-allocate
    attributes from the vendor space, rather than requesting an
    allocation (or self-allocating) from within the RADIUS
    standard attribute space.

    VSA encodings that do not follow the [RFC2865] Section 5.26
    scheme are NOT RECOMMENDED.  Although [RFC2865] does not mandate it,
    implementations commonly assume that the Vendor Id can be used as a
    key to determine the on-the-wire encoding of a VSA.  Vendors
    therefore SHOULD NOT use multiple encodings for VSAs that are
    associated with a particular Vendor Id.  A vendor wishing to use
    multiple VSA encodings SHOULD request one Vendor Id for each VSA
    encoding that they will use.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/32>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:27:12 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80FE83A67D4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z81qhDikqMug for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:27:11 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 377453A67AF for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:27:11 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQaRE-0008Uz-EJ for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:24:56 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQaRC-0008UQ-56 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:24:54 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQaRA-0005vt-D5; Sun, 20 Jun 2010 23:24:52 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:24:52 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #33: Section 2.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/33
Message-ID: <066.62faf616ea565dc0b10e87f948868195@tools.ietf.org>
X-Trac-Ticket-ID: 33
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#33: Section 2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 New commands (i.e., the Code field in the packet header) and new
    attributes in the standard space are allocated only through "IETF
    Consensus" as noted in [RFC3575] Section 2.1.

 [BA] The rules described in RFC 3575 are more complex than this.  In fact,
 some parameters require standards track. Recommended change:

    Requirements for allocation of new commands (i.e. the Code field in the
 packet header) and new attributes within the standards space are described
 in [RFC3575] Section 2.1.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/33>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:35:23 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F8093A6824 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.369
X-Spam-Level: 
X-Spam-Status: No, score=-102.369 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IAegnyZlfGv9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:35:18 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 767E93A6452 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:35:17 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQaXP-0009Rs-5j for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:31:19 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQaXM-0009RL-Gh for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:31:16 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQaXK-0001iR-DP; Sun, 20 Jun 2010 23:31:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:31:14 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #34: Section 2.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/34
Message-ID: <066.724427df9acd759c7941d97bac4745fa@tools.ietf.org>
X-Trac-Ticket-ID: 34
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#34: Section 2.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 The first paragraph of Section 2.4 appears to refer to a missing quotation
 from RFC 2865 Section 5.26.

 Recommended text for Section 2.4 is as follows:

 2.4. Translation of Vendor Specifications

   [RFC2865] Section 5.26 defines Vendor-Specific attributes as follows:

       This Attribute is available to allow vendors to support their own
       extended Attributes not suitable for general usage.  It MUST not
       affect the operation of the RADIUS protocol.

       Servers not equipped to interpret the vendor-specific information
       sent by a client MUST ignore it (although it may be reported).
       Clients which do not receive desired vendor-specific information
       SHOULD make an attempt to operate without it, although they may do
       so (and report they are doing so) in a degraded mode.

    The limitation on changes to the RADIUS protocol effectively
    prohibits VSAs from changing fundamental aspects of RADIUS operation,
    such as modifying RADIUS packet sequences, or adding new commands.
    However, the requirement for clients and servers to be able to
    operate in the absence of VSAs has proven to be less of a constraint,
    since it is still possible for a RADIUS client and server to mutually
    indicate support for VSAs, after which behavior expectations can be
    reset.

    Therefore, RFC 2865 provides considerable latitude for development of
    new attributes within the vendor space, while prohibiting development
    of protocol variants.  This flexibility implies that RADIUS
    attributes can often be developed within the vendor space without
    loss (and possibly even with gain) in functionality.

    As a result, translation of RADIUS attributes developed within the
    vendor space into the standard space may provide only modest
    benefits, while accelerating the exhaustion of the standard attribute
    space.  We do not expect that all RADIUS attribute specifications
    requiring interoperability will be developed within the IETF, and
    allocated from the standards space.  A more scalable approach is to
    recognize the flexibility of the vendor space, while working toward
    improvements in the quality and availability of RADIUS attribute
    specifications, regardless of where they are developed.

    It is therefore NOT RECOMMENDED that specifications intended solely
    for use by a vendor or SDO use be translated into the standard space.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/34>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:39:29 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1419C3A6A21 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.371
X-Spam-Level: 
X-Spam-Status: No, score=-102.371 tagged_above=-999 required=5 tests=[AWL=0.229, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwUM3+j15mLt for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:39:28 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 016FB3A6782 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:39:28 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQabl-000A6C-0O for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:35:49 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQabh-000A5Q-QN for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:35:46 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQabf-0001nT-TG; Sun, 20 Jun 2010 23:35:43 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:35:43 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #35: Section 3.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/35
Message-ID: <066.f29fbf3629c77bbf08c484718db6ecb1@tools.ietf.org>
X-Trac-Ticket-ID: 35
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#35: Section 3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:            
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 The RADIUS data types are poorly defined.

 [BA] Since Section 2.1 claims that RADIUS defines some basic data types,
 this sentence appears contradictory.  I recommend that it be deleted.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/35>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:47:48 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C1613A6824 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7icXhsMt33Y9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:47:47 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 16DD63A67AF for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:47:47 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQakQ-000BUE-Ca for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:44:46 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQakO-000BSr-52 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:44:44 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQakM-0001y0-KQ; Sun, 20 Jun 2010 23:44:42 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:44:42 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #36: Section 3.2.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/36
Message-ID: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-Trac-Ticket-ID: 36
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 We therefore RECOMMEND that the introduction of
    new types and complex data types within RADIUS attribute
    specifications be avoided.  A potential exception to this
    recommendation occurs for attributes that inherently require code
    changes on both the client and server.  For example, as described in
    Appendix B, complex attributes have been used in situations involving
    authentication and security attributes that need to be dynamically
    computed and verified.

 [BA] This advice is not completely consistent with that in Section 2.1.
 Recommended change:

    As described in Section 2.1, the introduction of complex data
    types is discouraged where viable alternatives are available.
    A potential exception is attributes that inherently require code
    changes on both the client and server.  For example, as described in
    Appendix B, complex attributes have been used in situations involving
    authentication and security attributes that need to be dynamically
    computed and verified.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:52:39 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A53D3A6A2C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.374
X-Spam-Level: 
X-Spam-Status: No, score=-102.374 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSPuc9dNU5GR for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:52:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 04EF83A680E for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:52:37 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQaoZ-000C8J-9G for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:49:03 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQaoW-000C5H-TY for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:49:01 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQaoV-0004i8-1k; Sun, 20 Jun 2010 23:48:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:48:59 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #36: Section 3.2.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:2
Message-ID: <075.e79bd98b22ef5bac9db989d68d77e4f9@tools.ietf.org>
References: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-Trac-Ticket-ID: 36
In-Reply-To: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Despite the above caveats, there may be situations where complex
    attributes are beneficial because they reduce complexity in the non-
    RADIUS systems.  Unfortunately, there are no "hard and fast" rules
    for where the complexity would best be located.  Each situation has
    to be decided on a case-by-case basis.

 [BA] This paragraph is repeated in Section 2.1.  It should be deleted
 here.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:52:40 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B3EC3A6A2C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.376
X-Spam-Level: 
X-Spam-Status: No, score=-102.376 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l3Kh30E3JnTf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:52:39 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A1BA83A680E for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:52:39 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQanZ-000Bvm-2M for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:48:01 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQanW-000BvU-Qe for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:47:59 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQanU-0004hM-Vi; Sun, 20 Jun 2010 23:47:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:47:56 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #36: Section 3.2.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:1
Message-ID: <075.c01b3caff0d50893028c5e1710274a38@tools.ietf.org>
References: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-Trac-Ticket-ID: 36
In-Reply-To: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Another sentence in Section 3.2.3:

    The only other exception to the recommendation against complex types
    is for types that can be treated as opaque data by the RADIUS server.

 [BA] As noted in Section 2.1, there are other situations in which complex
 types could be used, so this doesn't represent the only exception.
 Recommended change:

 Another exception to the recommendation against complex types is for types
 that can be treated as opaque data by the RADIUS server.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:55:55 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DA833A6807 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGSYjh5ibWV1 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:55:54 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3CF593A66B4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:55:54 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQarz-000Che-1t for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:52:35 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQarw-000ChD-Vj for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:52:33 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQarv-0004k2-Ej; Sun, 20 Jun 2010 23:52:31 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:52:31 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #37: Section 3.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/37
Message-ID: <066.742781818d0501ff26ecf299adf1569e@tools.ietf.org>
X-Trac-Ticket-ID: 37
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#37: Section 3.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Along with these advantages, some limitations of VSA usage are noted
    in [RFC2865] Section 5.26:

       This Attribute is available to allow vendors to support their own
       extended Attributes not suitable for general usage.  It MUST NOT
       affect the operation of the RADIUS protocol.

       Servers not equipped to interpret the vendor-specific information
       sent by a client MUST ignore it (although it may be reported).
       Clients which do not receive desired vendor-specific information
       SHOULD make an attempt to operate without it, although they may do
       so (and report they are doing so) in a degraded mode.

 [BA] This text appears to belong in Section 2.4 as indicated in a
 previously submitted issue.  It can therefore be deleted here.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/37>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sun Jun 20 23:58:05 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EC213A6782 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.379
X-Spam-Level: 
X-Spam-Status: No, score=-102.379 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgtGt+uIvFwU for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 20 Jun 2010 23:58:04 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2A73D3A66B4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 20 Jun 2010 23:58:04 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQavc-000DL5-9b for radiusext-data0@psg.com; Mon, 21 Jun 2010 06:56:20 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQava-000DKj-60 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 06:56:18 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQavY-0004lP-Jt; Sun, 20 Jun 2010 23:56:16 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 06:56:16 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #38: Section 3.3.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/38
Message-ID: <066.1af3d45c417cac96d365427693871f0f@tools.ietf.org>
X-Trac-Ticket-ID: 38
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#38: Section 3.3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Nevertheless, following the guidelines outlined within this document
    has many advantages.  Following these guidelines means that RADIUS
    servers can be updated to support the vendor's equipment by editing a
    RADIUS dictionary.  It is therefore RECOMMENDED that vendors follow
    the guidelines outlined here, which are intended to enable maximum
    interoperability with minimal changes to existing systems.  If these
    guidelines are not followed, then the vendor's equipment can only be
    supported via code changes in RADIUS server implementations.  Such
    code changes add complexity and delay to implementations.

 [BA] This advice is repeated elsewhere so it can be deleted here.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/38>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:07:20 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 863BE28C0DF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.381
X-Spam-Level: 
X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYJO1Z6nhoUx for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:07:19 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 38D163A66B4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:07:19 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQb28-000EUW-75 for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:03:04 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQb25-000ERg-Sl for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:03:02 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQb24-0004sT-0B; Mon, 21 Jun 2010 00:03:00 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:02:59 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #39: Section 4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/39
Message-ID: <066.df1daf14667d81e8afd9f29fbf508222@tools.ietf.org>
X-Trac-Ticket-ID: 39
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#39: Section 4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 4. IANA Considerations

    This document does not require that the IANA update any existing
    registry or create any new registry, but includes information that
    affects the IANA, which:

       * includes specific guidelines for Expert Reviewers appointed
         under the IANA considerations of [RFC3575]

       * includes guidelines that recommend against self allocation from
         the RADIUS standard attribute space in other SDO RADIUS
         Attribute specifications.

       * recommends that SDOs request a Private Enterprise Code (PEC)
         from the IANA, for use as a Vendor-Id within a Vendor-Specific
         attribute.

 [BA] BCPs cannot update standards track documents such as RFC 2865 or
 3575. This should be made more clear.  Recommended change:

 4. IANA Considerations

    This document has no action items for IANA.  However, it does provide
 guidelines for Expert Reviewers appointed as described in [RFC3575].

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/39>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:09:16 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58E123A6A2D for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMkolY4oXm0q for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:09:15 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 715E13A6824 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:09:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQb5n-000F6p-Dm for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:06:51 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQb5l-000F6S-Ac for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:06:49 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQb5j-0004uA-5q; Mon, 21 Jun 2010 00:06:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:06:47 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #40: A.1.1
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/40
Message-ID: <066.c348298679e6ac8be6dda5f15d68c762@tools.ietf.org>
X-Trac-Ticket-ID: 40
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#40: A.1.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Does the data fit within the basic data types described in Section
    2.1.1, as outlined below?

 [BA] The basic data types are described in Section 2.1, not 2.1.1.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/40>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:14:53 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40FEC3A6782 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.384
X-Spam-Level: 
X-Spam-Status: No, score=-102.384 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVFhOf-+yRMF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:14:51 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 26CC33A66B4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:14:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbAm-000FlE-Dt for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:12:00 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbAk-000Fkt-AR for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:11:58 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbAi-0007PS-Or; Mon, 21 Jun 2010 00:11:56 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:11:56 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #41: A1.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/41
Message-ID: <066.35ef0fd4b0f0bfa68c437991b72c5c9d@tools.ietf.org>
X-Trac-Ticket-ID: 41
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space via "IETF consensus", and SHOULD
    NOT be allocated from the vendor space.

 [BA] A BCP should not be setting IANA allocation policy.  Recommended
 change:

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/41>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:15:27 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 195363A6807 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.385
X-Spam-Level: 
X-Spam-Status: No, score=-102.385 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYE+swhUkvZw for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:15:14 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0A20D3A67C0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:15:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQb83-000FON-Pa for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:09:11 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQb81-000FNw-P6 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:09:09 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQb7z-00051l-PG; Mon, 21 Jun 2010 00:09:07 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:09:07 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #40: A.1.1
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/40#comment:1
Message-ID: <075.cabb75e8cd1eb2f0b7594d8170ea8486@tools.ietf.org>
References: <066.c348298679e6ac8be6dda5f15d68c762@tools.ietf.org>
X-Trac-Ticket-ID: 40
In-Reply-To: <066.c348298679e6ac8be6dda5f15d68c762@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#40: A.1.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Another bad reference:

       * Attributes grouped into a logical container, using the
         [RFC2868] tagging mechanism.  This approach is NOT
         RECOMMENDED (see Section 2.1.2), but is permissible where

 [BA] There is no section 2.1.2.  Perhaps this refers to section 3.2.2?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/40#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:23:18 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 420AC3A6813 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.387
X-Spam-Level: 
X-Spam-Status: No, score=-102.387 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14pkOfcsr8gh for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:23:17 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EDA173A6A36 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:23:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbHJ-000GoJ-5S for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:18:45 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbHG-000Gns-AN for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:18:42 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbHE-0000Cb-0G; Mon, 21 Jun 2010 00:18:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:18:39 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #41: A1.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/41#comment:1
Message-ID: <075.e8d2ffb915eb6426a0ff306c0bbfc808@tools.ietf.org>
References: <066.35ef0fd4b0f0bfa68c437991b72c5c9d@tools.ietf.org>
X-Trac-Ticket-ID: 41
In-Reply-To: <066.35ef0fd4b0f0bfa68c437991b72c5c9d@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
Description changed by bernard_aboba@…:

Old description:

> Does the data provide authentication and/or security capabilities for
>    the RADIUS protocol, as outlined below?  If so, it SHOULD be
>    allocated from the standard space via "IETF consensus", and SHOULD
>    NOT be allocated from the vendor space.
>
> [BA] A BCP should not be setting IANA allocation policy.  Recommended
> change:
>
>    Does the data provide authentication and/or security capabilities for
>    the RADIUS protocol, as outlined below?  If so, it SHOULD be
>    allocated from the standard space.

New description:

 A.1.2. Transport of Authentication and Security Data

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space via "IETF consensus", and SHOULD
    NOT be allocated from the vendor space.

       * Complex data types that carry authentication methods which
         RADIUS servers are expected to parse and verify as part of
         an authentication process.

       * Complex data types that carry security information intended
         to increase the security of the RADIUS protocol itself.

    Any data type carrying authentication and/or security data that is
    not meant to be parsed by a RADIUS server is an "opaque data type",
    as defined below.

 [BA] This section appears disjointed, as though it was missing some text.
 Recommended change:

 A.1.2. Transport of Authentication and Security Data

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, use of a complex data
 type is acceptable, under the following circumstances:

       * Complex data types that carry authentication methods which
         RADIUS servers are expected to parse and verify as part of
         an authentication process.

       * Complex data types that carry security information intended
         to increase the security of the RADIUS protocol itself.

    Any data type carrying authentication and/or security data that is
    not meant to be parsed by a RADIUS server is an "opaque data type",
    as defined below.

--

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/41#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:23:32 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43CF43A6782 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level: 
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFrA8p9OYxrg for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:23:31 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 678113A6A2F for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:23:31 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbKA-000HEX-68 for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:21:42 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbK7-000HDu-VU for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:21:40 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbK6-0003bf-DF; Mon, 21 Jun 2010 00:21:38 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:21:38 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #42: A1.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/42
Message-ID: <066.c718f23db5a05bfadaeed54ed9eac870@tools.ietf.org>
X-Trac-Ticket-ID: 42
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#42: A1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 A.1.4. Pre-existing data types


    There is a trade-off in design between re-using existing formats for
    historical compatibility, or choosing new formats for a "better"
    design.  This trade-off does not always require the "better" design
    to be used.  As a result. pre-existing complex data types described
    in Appendix B MAY be used, though this practice is NOT RECOMMENDED.

 [BA] Mailing list discussion indicates that there is not consensus to
 deprecate existing RADIUS types.  Suggested change:


    There is a trade-off in design between re-using existing formats for
    historical compatibility, or choosing new formats for a "better"
    design.  This trade-off does not always require the "better" design
    to be used.  As a result. pre-existing complex data types described
    in Appendix B MAY be used.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/42>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:26:27 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52B343A6A2F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.39
X-Spam-Level: 
X-Spam-Status: No, score=-102.39 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfFCUnRW4j9X for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:26:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3232C3A6782 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:26:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbN5-000Hh6-Cw for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:24:43 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbN3-000Hga-9q for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:24:41 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbN1-00068r-Kf; Mon, 21 Jun 2010 00:24:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:24:39 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #44: A2.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/44
Message-ID: <066.879cec9bcf87b115799be41de863bd79@tools.ietf.org>
X-Trac-Ticket-ID: 44
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#44: A2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 See also Section 2.1.3 for a
    discussion of why complex types are problematic.

 [BA] This advice is now in Section 2.1.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/44>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:26:41 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C17E3A6A2F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.392
X-Spam-Level: 
X-Spam-Status: No, score=-102.392 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CICa2srRYLgz for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:26:40 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 74E7B3A6782 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:26:40 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbLg-000HSe-GC for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:23:16 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbLe-000HSA-A2 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:23:14 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbLc-0002Gy-4g; Mon, 21 Jun 2010 00:23:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:23:12 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #43: A.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/43
Message-ID: <066.243f80f72f83195911ccef0c7dfaccea@tools.ietf.org>
X-Trac-Ticket-ID: 43
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#43: A.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 A.2. Improper Data Types

    All data types other than the ones described above in Appendix A.1
    and Appendix B SHOULD NOT be used.  This section describes in detail
    a number of data types that are NOT RECOMMENDED in new RADIUS
    specifications.  Where possible, replacement data types are
    suggested.

 [BA] WG discussion has indicated that there is not WG consensus for this
 text.  It should be deleted.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/43>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:31:07 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A6E228C0E5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.393
X-Spam-Level: 
X-Spam-Status: No, score=-102.393 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCXs2az+IrHL for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:31:06 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0B9FB28C0E4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:31:06 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbPi-000IDE-Ra for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:27:26 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbPg-000ICy-JG for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:27:24 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbPf-0006kc-1c; Mon, 21 Jun 2010 00:27:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:27:23 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #45: A.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/45
Message-ID: <066.e8d3570384e5f639d2d58a68cd44d9f3@tools.ietf.org>
X-Trac-Ticket-ID: 45
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#45: A.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Transport of opaque data
         relating to AAA is also permitted, as discussed above in
         Section 2.1.3. However, if the specification does not relate
         to AAA, then RADIUS SHOULD NOT be used.

 [BA] This is discussed in Section 3.2.3, not 2.1.3.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/45>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 00:44:15 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A840C3A67F2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.394
X-Spam-Level: 
X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3W8RbUYVvN1 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 00:44:11 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0166E3A66B4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 00:44:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQbdl-000KXW-KF for radiusext-data0@psg.com; Mon, 21 Jun 2010 07:41:57 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQbdj-000KX3-Fv for radiusext@ops.ietf.org; Mon, 21 Jun 2010 07:41:55 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQbdf-0004PJ-Gu; Mon, 21 Jun 2010 00:41:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 07:41:51 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #46: B.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/46
Message-ID: <066.83cff34b2792d6b61197dd7e270cc6f9@tools.ietf.org>
X-Trac-Ticket-ID: 46
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#46: B.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Since this is a security attribute and is encrypted, code changes are
    required on the RADIUS client and server to support it, regardless of
    the attribute format.  Therefore, this complex data type is
    acceptable in this situation.

 [BA] The design of the Tunnel-Password attribute goes against the
 recommendations in the Security Considerations section, so suggesting that
 this attribute is acceptable doesn't make sense.

 Recommended change:

    Since this is a security attribute, code changes are
    required on the RADIUS client and server to support it, regardless of
    the attribute format.  However, while use of a complex data type is
    acceptable in this situation, the design of the Tunnel-Password
 attribute is problematic from a security perspective, since it uses MD5 as
 a cipher, and provides a password to a NAS, potentially without proper
 authorization.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/46>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 04:29:36 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E756B3A6957 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 04:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.163
X-Spam-Level: **
X-Spam-Status: No, score=2.163 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVOVHXH7zEFd for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 04:29:36 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id AB2163A6A61 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 04:29:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQf5e-00040p-J4 for radiusext-data0@psg.com; Mon, 21 Jun 2010 11:22:58 +0000
Received: from [76.96.59.228] (helo=qmta15.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1OQf5c-00040N-38 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 11:22:56 +0000
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta15.westchester.pa.mail.comcast.net with comcast id YbBx1e0021vXlb85FbNvMM; Mon, 21 Jun 2010 11:22:55 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta17.westchester.pa.mail.comcast.net with comcast id YbNu1e00B0yip6Y3dbNu0E; Mon, 21 Jun 2010 11:22:55 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <066.bb35d2e7170fe573be2872ab6e28e60f@tools.ietf.org>
Subject: RE: [radext] #26: Terminology (Section 1.1)
Date: Mon, 21 Jun 2010 07:22:53 -0400
Message-ID: <E1E3A7F7F01B4CEC96AEF762E89D0FAB@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsQszjm3loAJqFbTe+872jGVmzMtwAf95og
In-Reply-To: <066.bb35d2e7170fe573be2872ab6e28e60f@tools.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Wow.   Such a long series of emails.  I appreciate having the issues
separated, but dealing with so many suggested changes out of context is
challenging.

>  [BA] Given the extended attribute work, we may not want to 
>  define the standard space a bit more flexibly.

Did you intend the "not" in this sentence?

>  standard space
>       RADIUS attributes which are allocated by IANA and which
>       follow the format defined in RFC 2865 [RFC2865] Section 5.

If the suggestion is to be more flexible in defining "standard space", your
suggested text seems to fall short of the mark, in that it talks about the
"format defined in RFC 2865 [RFC2865] Section 5".  Clearly that excludes the
Extended Attributes, no?



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 04:42:17 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9DE13A6806 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 04:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.163
X-Spam-Level: **
X-Spam-Status: No, score=2.163 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBgWvCdSNcM6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 04:42:15 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 07A223A676A for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 04:42:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQfKx-00077v-Q1 for radiusext-data0@psg.com; Mon, 21 Jun 2010 11:38:47 +0000
Received: from [76.96.62.48] (helo=qmta05.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1OQfKv-00077N-Bu for radiusext@ops.ietf.org; Mon, 21 Jun 2010 11:38:45 +0000
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta05.westchester.pa.mail.comcast.net with comcast id Yadx1e0021uE5Es55belTX; Mon, 21 Jun 2010 11:38:45 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta16.westchester.pa.mail.comcast.net with comcast id Ybel1e0090yip6Y3cbel6n; Mon, 21 Jun 2010 11:38:45 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
Subject: RE: [radext] #27: Section 1.3
Date: Mon, 21 Jun 2010 07:38:44 -0400
Message-ID: <D4579D30828E41299D053CA90D0A6682@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsQ0akDkKHU/0jYTQ2eSyCeVvgfDAAYpvcg
In-Reply-To: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>     However, there are situations in which vendors or SDOs can choose
>     not to follow these guidelines without major consequences.  As
>     noted in [RFC2865] Section 5.26, Vendor-Specific Attributes (VSAs)
>     are "available to allow vendors to support their own extended 
>     Attributes not suitable for general usage."  Where vendors or 
>     SDOs develop specifications "not suitable for general usage",
>     limited interoperability and inability to use existing 
>     implementations may be acceptable and in these situations, 
>     vendors and SDOs MAY NOT choose to conform to these
>     guidelines.

I have always felt that the notion of placing other SDOs on the same plane
as vendors is a silly one.  I believe I know what motivates this treatment.
It seems to me to be a compromise to assuage those RADIUS practitioners who
are active in other SDOs and who have continually been critical of this WG's
attempts to define a reasonably rigorous set of attribute design criteria.
The point of *any* SDO is to define interoperable standards for multiple
vendors to use, to promote multi-vendor interoperability in implementations
and deployments.  To suggest that SDOs, other than the IETF, do not require
multi-vendor interoperability in their standards seems to devalue their
work.

I think that there should be a three tier scheme for recommended compliance
with these guidelines, not two tier.  I believe that non-IETF SDOs should be
held to a higher level of expectations than single vendors, but lower that
the IETF itself.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 04:55:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A33C3A6806 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 04:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.163
X-Spam-Level: **
X-Spam-Status: No, score=2.163 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obN8o5MYHCqg for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 04:55:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7CE8B3A6A6B for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 04:55:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQfXy-000ANl-9M for radiusext-data0@psg.com; Mon, 21 Jun 2010 11:52:14 +0000
Received: from [76.96.62.96] (helo=qmta09.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1OQfXw-000AMM-3A for radiusext@ops.ietf.org; Mon, 21 Jun 2010 11:52:12 +0000
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta09.westchester.pa.mail.comcast.net with comcast id YbT11e00217dt5G59bsCnK; Mon, 21 Jun 2010 11:52:12 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta13.westchester.pa.mail.comcast.net with comcast id YbsC1e0020yip6Y3ZbsCqt; Mon, 21 Jun 2010 11:52:12 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
Subject: RE: [radext] #31: Section 2.1
Date: Mon, 21 Jun 2010 07:52:11 -0400
Message-ID: <7B98BEC1F8794DAD9B079F1CE7299D98@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsRCGmkluKuAdSmQL6eeVCTbSxIWAALsjCw
In-Reply-To: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>  Recommended replacement:
> 
>     All other data formats (including nested attributes) are defined
>     to be "complex data types", and are NOT RECOMMENDED for normal
>     use.  Complex data types MAY be used in situations where they
>     reduce complexity in non-RADIUS systems, or where using
>     the basic data types would be awkward (such as where grouping
>     would be required in order to link related attributes).  Since
>     there are no "hard and fast" rules for where complexity is best
>     located, each situation has to be decided on a case-by-case
>     basis.  Examples of this tradeoff are discussed in Appendix B.
>     Where a complex data type is selected, an explanation SHOULD be
>     offered as to why this was necessary.

At this point in time, I would support adding "such as where grouping would
be required in order to link related attributes" as an example of a case
that would justify the use of complex data types.  It is a great
disappointment to me that the WG failed to come to consensus on a more
regularized and formal mechanism to accommodate attribute grouping.  I think
that the ad hoc mechanism of grouping in complex data values is a distant
second best to a more formal and structured grouping mechanism.  However, at
this point, it is what it is.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 05:09:10 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D83733A6963 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.163
X-Spam-Level: **
X-Spam-Status: No, score=2.163 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2l--CEghilO for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:09:09 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BE3C63A695A for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 05:09:09 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQfla-000DOW-Nt for radiusext-data0@psg.com; Mon, 21 Jun 2010 12:06:18 +0000
Received: from [76.96.62.80] (helo=qmta08.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1OQflW-000DNo-Mk for radiusext@ops.ietf.org; Mon, 21 Jun 2010 12:06:14 +0000
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta08.westchester.pa.mail.comcast.net with comcast id Ya9j1e0010mv7h058c6FbU; Mon, 21 Jun 2010 12:06:15 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta11.westchester.pa.mail.comcast.net with comcast id Yc6C1e00N0yip6Y3Xc6DiK; Mon, 21 Jun 2010 12:06:15 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org>
Subject: RE: [radext] #32: Section 2.2
Date: Mon, 21 Jun 2010 08:06:11 -0400
Message-ID: <F59C310D417C4E1C8E854A435E12BA94@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsRCo8yDQJiDLykTEK0eb6SSAZLAwALa2uA
In-Reply-To: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>  Recommended change is to replace Section 2.2 with the following:
> 
>   2.2. Vendor-Specific Attribute Space
> 
>     The Vendor-Specific Attribute space is defined to be the contents of
>     the "String" field of the Vendor-Specific Attribute ([RFC2865]
>     Section 5.26).  As discussed there, it is intended for vendors and
>     SDOs to support their own Attributes not suitable for general use.

Once again, I don't support the conflation of vendors and SDOs.  We do want
non-IETF SDOs to use the VSA mechanism, primarily to conserve the scarce
pool of IANA-assigned code points.  However, I'm convinced that sending the
message that what another standards organization does is of no more
importance or consequence than the activity of a single vendor is a mistake.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 05:09:39 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00A603A6963 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.163
X-Spam-Level: **
X-Spam-Status: No, score=2.163 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5sCm6UyggU0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:09:38 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1ACEE3A695A for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 05:09:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQflW-000DNv-Kw for radiusext-data0@psg.com; Mon, 21 Jun 2010 12:06:14 +0000
Received: from [76.96.62.40] (helo=qmta04.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1OQflU-000DNV-Ls for radiusext@ops.ietf.org; Mon, 21 Jun 2010 12:06:12 +0000
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta04.westchester.pa.mail.comcast.net with comcast id Yaw01e0070mv7h054c6Dn1; Mon, 21 Jun 2010 12:06:13 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta11.westchester.pa.mail.comcast.net with comcast id Yc6C1e00N0yip6Y3Xc6Chp; Mon, 21 Jun 2010 12:06:13 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org> <075.c01b3caff0d50893028c5e1710274a38@tools.ietf.org>
Subject: RE: [radext] #36: Section 3.2.3
Date: Mon, 21 Jun 2010 08:06:11 -0400
Message-ID: <F83DFFBAACC848C9B691EF49A098B0E2@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsRDkEfwo2X0rjkRRSz/sP6Yn7CmgAKud3g
In-Reply-To: <075.c01b3caff0d50893028c5e1710274a38@tools.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>  Recommended change:
> 
>  Another exception to the recommendation against complex types is for
>  types that can be treated as opaque data by the RADIUS server.

This is a single sentence out of context, so my concern may be addressed
elsewhere, but I've always felt that one important test of "opaqueness" is
whether or not the payload of the attribute is laid out in details in the
RADIUS document, in the traditional fashion of other RADIUS attributes.  If
it's truly opaque, then the format MUST be defined in some other, non-RADIUS
document.  Otherwise, this opens up the possibility of defining new services
in the context of a RADIUS document.  In other words, an attribute can't at
the same time be "opaque" to the RADIUS server but spelled out in detail to
the RADIUS developer in the RADIUS document.  It's either "defined
elsewhere" or it isn't.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 05:16:14 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9CAA3A6964 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.163
X-Spam-Level: **
X-Spam-Status: No, score=2.163 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoCfZid0Jmkq for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:16:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2768E3A6962 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 05:16:13 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQftQ-000Er5-HX for radiusext-data0@psg.com; Mon, 21 Jun 2010 12:14:24 +0000
Received: from [76.96.59.227] (helo=qmta12.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1OQftO-000Eqi-LX for radiusext@ops.ietf.org; Mon, 21 Jun 2010 12:14:22 +0000
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta12.westchester.pa.mail.comcast.net with comcast id YaX91e00117dt5G5CcEP0u; Mon, 21 Jun 2010 12:14:23 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta13.westchester.pa.mail.comcast.net with comcast id YcEN1e00B0yip6Y3ZcENdj; Mon, 21 Jun 2010 12:14:23 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <066.c718f23db5a05bfadaeed54ed9eac870@tools.ietf.org>
Subject: RE: [radext] #42: A1.4
Date: Mon, 21 Jun 2010 08:14:21 -0400
Message-ID: <BE301B02D1BD42B192CD1C44C276CE4A@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcsREpZdBmOj9ct5RDWUj4+cPPtFRwAKGEgg
In-Reply-To: <066.c718f23db5a05bfadaeed54ed9eac870@tools.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>  [BA] Mailing list discussion indicates that there is not consensus to
>  deprecate existing RADIUS types.  Suggested change:
> 
>     There is a trade-off in design between re-using existing formats for
>     historical compatibility, or choosing new formats for a "better"
>     design.  This trade-off does not always require the "better" design
>     to be used.  As a result. pre-existing complex data types described
>     in Appendix B MAY be used.

As much as it disappoints me personally, I don't dispute the fact.  We did
not obtain consensus.  



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 05:28:28 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AEDA3A6988 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.167
X-Spam-Level: 
X-Spam-Status: No, score=-0.167 tagged_above=-999 required=5 tests=[AWL=0.328, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3N3ZptHq7qtd for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:28:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 23A773A67AC for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 05:28:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQg5A-000GvZ-8Y for radiusext-data0@psg.com; Mon, 21 Jun 2010 12:26:32 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OQg58-000Gv6-8E for radiusext@ops.ietf.org; Mon, 21 Jun 2010 12:26:30 +0000
Message-ID: <4C1F5A74.1010807@deployingradius.com>
Date: Mon, 21 Jun 2010 14:26:28 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Dave Nelson <d.b.nelson@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: [radext] #36: Section 3.2.3
References: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org> <075.c01b3caff0d50893028c5e1710274a38@tools.ietf.org> <F83DFFBAACC848C9B691EF49A098B0E2@NEWTON603>
In-Reply-To: <F83DFFBAACC848C9B691EF49A098B0E2@NEWTON603>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Dave Nelson wrote:
> This is a single sentence out of context, so my concern may be addressed
> elsewhere, but I've always felt that one important test of "opaqueness" is
> whether or not the payload of the attribute is laid out in details in the
> RADIUS document, in the traditional fashion of other RADIUS attributes.  If
> it's truly opaque, then the format MUST be defined in some other, non-RADIUS
> document.

  Yes.  See Section 2.1, which says this explicitly.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 05:31:38 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5643C3A6806 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.118
X-Spam-Level: *
X-Spam-Status: No, score=1.118 tagged_above=-999 required=5 tests=[AWL=-0.987, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agUosk1cfH2v for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 05:31:33 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id F22A93A6988 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 05:31:31 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQg8b-000Hat-E8 for radiusext-data0@psg.com; Mon, 21 Jun 2010 12:30:05 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OQg8Z-000HaF-BQ for radiusext@ops.ietf.org; Mon, 21 Jun 2010 12:30:03 +0000
Message-ID: <4C1F5B4A.9010203@deployingradius.com>
Date: Mon, 21 Jun 2010 14:30:02 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Dave Nelson <d.b.nelson@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: [radext] #32: Section 2.2
References: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org> <F59C310D417C4E1C8E854A435E12BA94@NEWTON603>
In-Reply-To: <F59C310D417C4E1C8E854A435E12BA94@NEWTON603>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Dave Nelson wrote:
> Once again, I don't support the conflation of vendors and SDOs.  We do want
> non-IETF SDOs to use the VSA mechanism, primarily to conserve the scarce
> pool of IANA-assigned code points.  However, I'm convinced that sending the
> message that what another standards organization does is of no more
> importance or consequence than the activity of a single vendor is a mistake.

  A single vendor still expects their equipment to be used in a wide
variety of circumstances.  Experience shows that vendors who have
significant sales can have their non-standard formats adopted by all
major RADIUS servers.

  The same applies to SDOs.

  I think that the discussion about "not suitable for general use" is
really "not suitable for standardization through the IETF".  As such,
vendors and SDOs fall into the same non-IETF category.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 06:19:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FB143A69BC for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 06:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.139
X-Spam-Level: 
X-Spam-Status: No, score=-0.139 tagged_above=-999 required=5 tests=[AWL=0.356, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTbRo5IYXZvM for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 06:19:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A0C333A6809 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 06:19:24 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQgrc-0000Mj-CP for radiusext-data0@psg.com; Mon, 21 Jun 2010 13:16:36 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1OQgrX-0000Lz-7F for radiusext@ops.ietf.org; Mon, 21 Jun 2010 13:16:31 +0000
Message-ID: <4C1F662E.8060009@deployingradius.com>
Date: Mon, 21 Jun 2010 15:16:30 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Recent Issues
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

  I've updated the document to address recent issues as raised on the
tracker.

  Some minor word-smithing was done, but nothing more.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 06:37:47 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADD153A6856 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 06:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.312
X-Spam-Level: 
X-Spam-Status: No, score=-102.312 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xHlN8ZhwGoSb for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 06:37:46 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B81413A683C for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 06:37:46 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQh56-0002k4-Ui for radiusext-data0@psg.com; Mon, 21 Jun 2010 13:30:32 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <root@core3.amsl.com>) id 1OQh54-0002jN-HJ for radiusext@ops.ietf.org; Mon, 21 Jun 2010 13:30:30 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 01BB83A69CD; Mon, 21 Jun 2010 06:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-design-15.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100621133016.01BB83A69CD@core3.amsl.com>
Date: Mon, 21 Jun 2010 06:30:03 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

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 Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-15.txt
	Pages           : 39
	Date            : 2010-06-21

This document provides guidelines for the design of attributes used
by the Remote Authentication Dial In User Service (RADIUS) protocol.
It is expected that these guidelines will prove useful to authors and
reviewers of future RADIUS attribute specifications, both within the
IETF as well as other Standards Development Organizations (SDOs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-15.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-radext-design-15.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2010-06-21061612.I-D@ietf.org>

--NextPart--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:03:37 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81D2928C0F0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.397
X-Spam-Level: 
X-Spam-Status: No, score=-102.397 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52rvPP9YFNFG for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:03:36 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 116C53A6868 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:03:36 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiTR-000JgC-Oe for radiusext-data0@psg.com; Mon, 21 Jun 2010 14:59:45 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiTP-000JfT-D2 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 14:59:43 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiTM-00056q-6k; Mon, 21 Jun 2010 07:59:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 14:59:40 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #27: Section 1.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/27#comment:2
Message-ID: <075.ef2fe80b78fff208b04d3aefd55afbc4@tools.ietf.org>
References: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
X-Trac-Ticket-ID: 27
In-Reply-To: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#27: Section 1.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  aland@…                  
     Type:  defect                     |       Status:  closed                   
 Priority:  critical                   |    Milestone:  milestone1               
Component:  design                     |      Version:  1.0                      
 Severity:  Submitted WG Document      |   Resolution:  fixed                    
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/27#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:04:37 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39DC33A681E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kLx3OJxWeYkq for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:04:36 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4FA443A6826 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:04:36 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiVR-000KBX-Ao for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:01:49 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiVP-000KAx-7W for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:01:47 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiVN-0005Gh-Lm; Mon, 21 Jun 2010 08:01:45 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:01:45 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #29: Section 2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/29#comment:1
Message-ID: <075.61c6858b00c5e7090b1298b27e9a0590@tools.ietf.org>
References: <066.9278f2fd2da1a1adf9153579ef1ae1c5@tools.ietf.org>
X-Trac-Ticket-ID: 29
In-Reply-To: <066.9278f2fd2da1a1adf9153579ef1ae1c5@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#29: Section 2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  critical                   |    Milestone:  milestone1
Component:  design                     |      Version:            
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/29#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:04:40 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57BFE3A6826 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.4
X-Spam-Level: 
X-Spam-Status: No, score=-102.4 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kceQin3BEfvP for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:04:39 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 771193A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:04:39 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiUA-000Joy-VH for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:00:30 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiU8-000JoJ-PR for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:00:28 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiU7-0005EH-BS; Mon, 21 Jun 2010 08:00:27 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:00:27 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #28: Section 1.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/28#comment:2
Message-ID: <075.a7b0590f41de4a67dbd05293aff83f7a@tools.ietf.org>
References: <066.21f1182b696155b3e3e204d3d7194146@tools.ietf.org>
X-Trac-Ticket-ID: 28
In-Reply-To: <066.21f1182b696155b3e3e204d3d7194146@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  critical                   |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/28#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:05:17 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24A093A6826 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lAthYOnp8fwe for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:05:16 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 550283A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:05:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiWT-000KKj-5o for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:02:53 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiWQ-000KJr-QI for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:02:51 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiWP-0005HV-DT; Mon, 21 Jun 2010 08:02:49 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:02:49 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #30: Section 1.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/30#comment:1
Message-ID: <075.0782462d55f1c0ef28f4e9f96d6de584@tools.ietf.org>
References: <066.662d4351e84edff3e03f1dd33c281067@tools.ietf.org>
X-Trac-Ticket-ID: 30
In-Reply-To: <066.662d4351e84edff3e03f1dd33c281067@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#30: Section 1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/30#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:07:57 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E54843A6868 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.403
X-Spam-Level: 
X-Spam-Status: No, score=-102.403 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id POjqcgnbTOP8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:07:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B07163A63CA for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:07:56 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiZK-000Kva-Tt for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:05:50 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiZI-000KvG-R1 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:05:49 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiZH-0005UC-EA; Mon, 21 Jun 2010 08:05:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:05:47 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #31: Section 2.1
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/31#comment:1
Message-ID: <075.2dba1fddd9d3ade885fed6fbc3651c04@tools.ietf.org>
References: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
X-Trac-Ticket-ID: 31
In-Reply-To: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#31: Section 2.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Sorry for the inexact editing instructions.  Once the first paragraph is
 replaced, the second paragraph is unnecessary.  Please delete the
 following:

 There may be situations where complex attributes are acceptable
 because they reduce complexity in non-RADIUS systems, or because
 leveraging the basic data types would be awkward. Unfortunately,
 there are no "hard and fast" rules for where the complexity would
 best be located. Each situation has to be decided on a case-by-case
 basis. The cost-benefit trade-off may result in a "complex data
 type" being defined in RADIUS, as discussed in Appendix B. When this
 is done, an explanation SHOULD be offered as to why the complex data
 type was used.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/31#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:10:07 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E92B03A6880 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vr0f6aOg13Zy for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:10:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 607593A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:10:03 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQib9-000LEa-Av for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:07:43 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQib7-000LE5-9F for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:07:41 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQib5-0005wb-Rf; Mon, 21 Jun 2010 08:07:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:07:39 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #32: Section 2.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/32#comment:1
Message-ID: <075.26ea701164777c295892f3e67ca82ca0@tools.ietf.org>
References: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org>
X-Trac-Ticket-ID: 32
In-Reply-To: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#32: Section 2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/32#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:11:06 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E21C83A6887 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.405
X-Spam-Level: 
X-Spam-Status: No, score=-102.405 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qaBDo7h5XD2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:11:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 95EE73A6868 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:11:03 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQibk-000LKx-UI for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:08:20 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQibi-000LKL-OJ for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:08:18 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQibh-0005xC-99; Mon, 21 Jun 2010 08:08:17 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:08:17 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #33: Section 2.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/33#comment:1
Message-ID: <075.b077939161ff91c48d353777a96e3df7@tools.ietf.org>
References: <066.62faf616ea565dc0b10e87f948868195@tools.ietf.org>
X-Trac-Ticket-ID: 33
In-Reply-To: <066.62faf616ea565dc0b10e87f948868195@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#33: Section 2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  blocker                    |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/33#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:11:12 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB71C3A6868 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2vbJ2T2asbf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:11:11 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id ED8153A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:11:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQicv-000LVI-Gc for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:09:33 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQict-000LUu-8N for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:09:31 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQicr-0005yF-QT; Mon, 21 Jun 2010 08:09:29 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:09:29 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #34: Section 2.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/34#comment:1
Message-ID: <075.ea2bb663d18199e7a8c9ad663dbbe275@tools.ietf.org>
References: <066.724427df9acd759c7941d97bac4745fa@tools.ietf.org>
X-Trac-Ticket-ID: 34
In-Reply-To: <066.724427df9acd759c7941d97bac4745fa@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#34: Section 2.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/34#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:15:44 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29C423A6880 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.408
X-Spam-Level: 
X-Spam-Status: No, score=-102.408 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nv9zqxBPuc3U for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:15:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4301D3A6938 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:15:18 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQigH-000MBz-Ap for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:13:01 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQigF-000M4F-1o for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:12:59 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQigD-0004Wh-Cv; Mon, 21 Jun 2010 08:12:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:12:57 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #37: Section 3.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/37#comment:1
Message-ID: <075.c9b4373a18876b084eba473753c43606@tools.ietf.org>
References: <066.742781818d0501ff26ecf299adf1569e@tools.ietf.org>
X-Trac-Ticket-ID: 37
In-Reply-To: <066.742781818d0501ff26ecf299adf1569e@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#37: Section 3.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/37#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:16:22 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAF5F3A6874 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level: 
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.191, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJP1PlZXZGAc for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:16:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D04623A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:16:21 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQihc-000MVa-6S for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:14:24 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQihZ-000MV9-II for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:14:21 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQihV-0005Rm-Lt; Mon, 21 Jun 2010 08:14:19 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:14:17 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #36: Section 3.2.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:3
Message-ID: <075.6b41c9701e7d1a525ab82d139c4e6419@tools.ietf.org>
References: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-Trac-Ticket-ID: 36
In-Reply-To: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:3>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:16:37 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31B063A6887 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level: 
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QkOLBl+EDSZw for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:16:36 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2E8F33A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:16:36 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQie7-000Lif-Jw for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:10:47 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQie5-000Lhv-2K for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:10:45 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQie2-0006hd-UC; Mon, 21 Jun 2010 08:10:42 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:10:42 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #35: Section 3.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/35#comment:1
Message-ID: <075.1743acd45506ad6c2df2af443f964b26@tools.ietf.org>
References: <066.f29fbf3629c77bbf08c484718db6ecb1@tools.ietf.org>
X-Trac-Ticket-ID: 35
In-Reply-To: <066.f29fbf3629c77bbf08c484718db6ecb1@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#35: Section 3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:            
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/35#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:17:48 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93F403A681E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level: 
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHKaHr89VbKi for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:17:47 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id F12293A67AB for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:17:45 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQijA-000MmO-Qs for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:16:00 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQij5-000MkA-GY for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:15:55 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQij3-00081Z-N2; Mon, 21 Jun 2010 08:15:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:15:53 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #38: Section 3.3.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/38#comment:1
Message-ID: <075.bc9222bd2adde92d1ddf77b33c66a25a@tools.ietf.org>
References: <066.1af3d45c417cac96d365427693871f0f@tools.ietf.org>
X-Trac-Ticket-ID: 38
In-Reply-To: <066.1af3d45c417cac96d365427693871f0f@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#38: Section 3.3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/38#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:20:19 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A136C3A67F3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:20:19 -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.187, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1P6iMSTdEsf7 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:20:14 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8E47F3A6896 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:20:13 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQill-000NKM-15 for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:18:41 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQilg-000NJq-UZ for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:18:37 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQilf-0003I6-AQ; Mon, 21 Jun 2010 08:18:35 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:18:35 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #40: A.1.1
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/40#comment:2
Message-ID: <075.bb774ac9f448ef654bd73cb845f98ef8@tools.ietf.org>
References: <066.c348298679e6ac8be6dda5f15d68c762@tools.ietf.org>
X-Trac-Ticket-ID: 40
In-Reply-To: <066.c348298679e6ac8be6dda5f15d68c762@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#40: A.1.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/40#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:20:23 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4DEF3A681E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level: 
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78jyy+qhIrnp for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:20:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E00AB3A67F3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:20:21 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQik3-000N0H-CI for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:16:55 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQik1-000MzJ-4B for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:16:53 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQijz-0000iN-HQ; Mon, 21 Jun 2010 08:16:51 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:16:51 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #39: Section 4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/39#comment:1
Message-ID: <075.c15054fb388bf576551c6eaf4b8c5bdd@tools.ietf.org>
References: <066.df1daf14667d81e8afd9f29fbf508222@tools.ietf.org>
X-Trac-Ticket-ID: 39
In-Reply-To: <066.df1daf14667d81e8afd9f29fbf508222@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#39: Section 4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/39#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:24:03 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC0673A68BD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.415
X-Spam-Level: 
X-Spam-Status: No, score=-102.415 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 927p2snbnzL9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:24:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E58173A6893 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:24:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQip5-000NxN-Ht for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:22:07 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQip3-000Nwb-BO for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:22:05 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQip1-0002xC-GN; Mon, 21 Jun 2010 08:22:03 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:22:03 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #41: A1.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/41#comment:2
Message-ID: <075.8d70c9086b439cb01aa300e33c9daaa3@tools.ietf.org>
References: <066.35ef0fd4b0f0bfa68c437991b72c5c9d@tools.ietf.org>
X-Trac-Ticket-ID: 41
In-Reply-To: <066.35ef0fd4b0f0bfa68c437991b72c5c9d@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/41#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:24:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA8233A68C0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.416
X-Spam-Level: 
X-Spam-Status: No, score=-102.416 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aF2lML9urTuB for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:24:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C6C6C3A68B3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:24:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQipw-000O72-6j for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:23:00 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQipt-000O4l-Gn for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:22:58 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQipr-00046l-Uw; Mon, 21 Jun 2010 08:22:55 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:22:55 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #26: Terminology (Section 1.1)
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/26#comment:1
Message-ID: <075.00f3b0fc9972e6f3478c2dce4b95904b@tools.ietf.org>
References: <066.bb35d2e7170fe573be2872ab6e28e60f@tools.ietf.org>
X-Trac-Ticket-ID: 26
In-Reply-To: <066.bb35d2e7170fe573be2872ab6e28e60f@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#26: Terminology (Section 1.1)
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/26#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:26:06 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 488ED3A68C0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.417
X-Spam-Level: 
X-Spam-Status: No, score=-102.417 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5fDbWmSSLhFG for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:26:05 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E21493A6897 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:26:04 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQir2-000OTs-Ix for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:24:08 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQir0-000OTD-5I for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:24:06 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiqy-0005dv-Hv; Mon, 21 Jun 2010 08:24:04 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:24:04 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #42: A1.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/42#comment:1
Message-ID: <075.572ac7eec58bafa24d7a10e68b0d9e05@tools.ietf.org>
References: <066.c718f23db5a05bfadaeed54ed9eac870@tools.ietf.org>
X-Trac-Ticket-ID: 42
In-Reply-To: <066.c718f23db5a05bfadaeed54ed9eac870@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#42: A1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  blocker                    |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/42#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:26:56 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 440783A6938 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.418
X-Spam-Level: 
X-Spam-Status: No, score=-102.418 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id We77vZSFOoV9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:26:55 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 625FB3A68C0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:26:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiri-000Ob6-UV for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:24:50 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQirg-000OZy-RK for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:24:49 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQirf-0006eR-A6; Mon, 21 Jun 2010 08:24:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:24:47 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #44: A2.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/44#comment:1
Message-ID: <075.02e8c63961e16c3aeb372a305828477c@tools.ietf.org>
References: <066.879cec9bcf87b115799be41de863bd79@tools.ietf.org>
X-Trac-Ticket-ID: 44
In-Reply-To: <066.879cec9bcf87b115799be41de863bd79@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#44: A2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/44#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:28:36 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 788EE3A68B2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juJSMt-fui1E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:28:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7FC2C3A6938 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:28:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQitG-000Ozr-V1 for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:26:27 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQitE-000OzM-Gg for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:26:24 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQitC-0000So-Uc; Mon, 21 Jun 2010 08:26:22 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:26:22 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #43: A.2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/43#comment:1
Message-ID: <075.5198e38ba5dbc4251195dc42e61045ae@tools.ietf.org>
References: <066.243f80f72f83195911ccef0c7dfaccea@tools.ietf.org>
X-Trac-Ticket-ID: 43
In-Reply-To: <066.243f80f72f83195911ccef0c7dfaccea@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#43: A.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  blocker                    |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/43#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:30:18 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A9C43A6897 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.421
X-Spam-Level: 
X-Spam-Status: No, score=-102.421 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJRFwgHJ-2+F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:30:05 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 99AC93A6826 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:30:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQivA-000PJf-MI for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:28:24 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiv8-000PJG-6a for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:28:22 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQiv6-0003GJ-Jd; Mon, 21 Jun 2010 08:28:20 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:28:20 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #45: A.4
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/45#comment:1
Message-ID: <075.f5fafff81744b4bfa8de9ea7a466a58d@tools.ietf.org>
References: <066.e8d3570384e5f639d2d58a68cd44d9f3@tools.ietf.org>
X-Trac-Ticket-ID: 45
In-Reply-To: <066.e8d3570384e5f639d2d58a68cd44d9f3@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#45: A.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/45#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:32:10 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DA963A6910 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.422
X-Spam-Level: 
X-Spam-Status: No, score=-102.422 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCFagBWSOVRt for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:32:05 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 397293A6800 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:31:43 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQiw3-000PVm-5Y for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:29:19 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQiw0-000PVC-EO for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:29:17 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQivy-0004Kc-NY; Mon, 21 Jun 2010 08:29:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:29:14 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #46: B.3
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/46#comment:1
Message-ID: <075.1ca9058c5dbb95d8f8a06bca69ef428c@tools.ietf.org>
References: <066.83cff34b2792d6b61197dd7e270cc6f9@tools.ietf.org>
X-Trac-Ticket-ID: 46
In-Reply-To: <066.83cff34b2792d6b61197dd7e270cc6f9@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#46: B.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/46#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:38:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 300F03A681E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.423
X-Spam-Level: 
X-Spam-Status: No, score=-102.423 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l806bMdrk-wb for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:38:32 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0261A3A6818 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:38:32 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQj1l-0000cA-KV for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:35:13 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQj1j-0000bm-F9 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:35:11 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQj1g-0007vK-U4; Mon, 21 Jun 2010 08:35:08 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:35:08 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #47: A.4 Reference
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/47
Message-ID: <066.b9144fa71986f1480fec361be35d5a4d@tools.ietf.org>
X-Trac-Ticket-ID: 47
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#47: A.4 Reference
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  minor                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
 For further details, see Section 3.3.

 [BA] Section 3.3 is about the Vendor Space, and doesn't appear to relate
 to the recommendations in A.4.  Is this the right reference or perhaps
 Section 3.1 was intended instead?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/47>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:42:59 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1673B3A6800 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.012
X-Spam-Level: **
X-Spam-Status: No, score=2.012 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pfch0+0jHb9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:42:58 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 216B93A681E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:42:57 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQj6z-0001le-NL for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:40:37 +0000
Received: from [207.3.149.133] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.72 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1OQj6w-0001lI-R8 for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:40:35 +0000
Received: (qmail 1141 invoked from network); 21 Jun 2010 15:40:33 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 21 Jun 2010 15:40:33 -0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: [radext] #32: Section 2.2
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
In-Reply-To: <4C1F5B4A.9010203@deployingradius.com>
Date: Mon, 21 Jun 2010 11:40:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEDC7BF5-FBD3-41FE-869C-781CD4BD605B@elbrysnetworks.com>
References: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org> <F59C310D417C4E1C8E854A435E12BA94@NEWTON603> <4C1F5B4A.9010203@deployingradius.com>
To: radext mailing list <radiusext@ops.ietf.org>
X-Mailer: Apple Mail (2.1081)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Jun 21, 2010, at 8:30 AM, Alan DeKok wrote:

>  A single vendor still expects their equipment to be used in a wide
> variety of circumstances.  Experience shows that vendors who have
> significant sales can have their non-standard formats adopted by all
> major RADIUS servers.

Yes, but isn't that rather a corner case, in terms of the way the =
process is supposed to work?  I was addressing baseline expectations.

>  I think that the discussion about "not suitable for general use" is
> really "not suitable for standardization through the IETF".  As such,
> vendors and SDOs fall into the same non-IETF category.

If you were to change the text to say that, I'd agree.  But that's not =
what it says, and the definition of VSA in RFC 2865 is couched in terms =
of "not suitable for general use".

If what we want to say is that these guidelines really only apply for =
work done in the IETF, I think the document does convey that message.  =
My questions is whether that's really the message we want to convey.







--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 08:51:35 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 071BB3A695B for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.424
X-Spam-Level: 
X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZiWlbdG3ZoO0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 08:51:33 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7FD5B3A694D for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 08:51:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQjEl-0003fv-8b for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:48:39 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQjEi-0003eN-UM for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:48:37 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQjEh-0005xd-7C; Mon, 21 Jun 2010 08:48:35 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:48:35 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #48: B.6
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/48
Message-ID: <066.d6ad801904e0d402bede96ab040ae3fd@tools.ietf.org>
X-Trac-Ticket-ID: 48
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#48: B.6
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 This attribute contains no encrypted component, and is it not
    directly involved in authentication.  The individual sub-fields could
    therefore have been encapsulated in separate attributes.

    Since the form of the text string is well defined, there is no
    benefit in using a text string.  Instead, an integer attribute should
    have been assigned for each of the transmit speed and the receive
    speed.  A separate enumerated integer should have been assigned for
    the additional information, as was done with the NAS-Port-Type
    attribute.

 [BA] The text in RFC 2869 Section 5.11 refers to ITU-T efforts relating to
 connect strings.  This indicates that the authors thought of the Connect-
 Info attribute as an "opaque data" defined by ITU-T.  Given this, the
 attribute could qualify for an exception.  Recommended change:

    This attribute contains no encrypted component, and is it not
    directly involved in authentication.  The individual sub-fields could
    therefore have been encapsulated in separate attributes.

    However, since the definition refers to potential standardization
 activity within ITU, the Connect-Info attribute can also be thought of
 opaque data whose definition is provided elsewhere.  The Connect-Info
 attribute could therefore qualify for an exception as described in Section
 3.2.3.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/48>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 09:01:07 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF7DD28C0F6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 09:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.495
X-Spam-Level: 
X-Spam-Status: No, score=-101.495 tagged_above=-999 required=5 tests=[AWL=-0.754, BAYES_20=-0.74, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wMweBC9KML7A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 09:01:06 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9826E28C0FE for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 09:01:06 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQjML-0005SD-VN for radiusext-data0@psg.com; Mon, 21 Jun 2010 15:56:29 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQjMJ-0005RT-EO for radiusext@ops.ietf.org; Mon, 21 Jun 2010 15:56:27 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQjMH-0006MQ-IS; Mon, 21 Jun 2010 08:56:25 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 15:56:25 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #49: B.10
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/49
Message-ID: <066.86883efddb9747b3070442cd0525945d@tools.ietf.org>
X-Trac-Ticket-ID: 49
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#49: B.10
------------------------------------------+---------------------------------
 Reporter:  bernard_aboba@…               |       Owner:            
     Type:  defect                        |      Status:  new       
 Priority:  critical                      |   Milestone:  milestone1
Component:  design                        |     Version:  1.0       
 Severity:  Waiting for Shepherd Writeup  |    Keywords:            
------------------------------------------+---------------------------------
 B.9. Digest-*

    [RFC5090] attempts to standardize the functionality provided by an
    expired internet-draft [AAA-SIP] which improperly used two attributes
    from the standard space without being assigned them by IANA.  This
    self-allocation is forbidden, as described above in Section 1.3 and
    in Section 2.  In addition, the draft uses nested attributes, which
    are discouraged in Section 2.1.  The updated document uses basic data
    types, and allocates nearly 20 attributes in the process.

    However, the draft has seen wide-spread implementation, where
    [RFC5090] has not.  While there are a number of factors involved, one
    factor may be that implementors disagreed with the trade-offs made in
    the updated specification.  It may have been better to simply
    document the existing format, and request IANA allocation of two
    attributes.  The resulting design would have used nested attributes,
    but may have gained more wide-spread implementation.

    It is difficult to know which choice is optimal.  Given the
    complexity of the protocols and implementations, it is impossible to
    define "hard and fast" rules for RADIUS design guidelines.

 [BA] There is already a section B.9.  This section should therefore be
 renumbered as "B.10".  The recommended text is as follows:

 B.10. Digest-*

    [RFC5090] attempts to standardize the functionality provided by an
    expired internet-draft [AAA-SIP] which improperly used two attributes
    from the standard space without being assigned them by IANA.  This
    self-allocation is forbidden, as described above in Section 2.
    In addition, the draft uses nested attributes, which
    are discouraged in Section 2.1.  The updated document uses basic data
    types, and allocates nearly 20 attributes in the process.

    However, the draft has seen wide-spread implementation, where
    [RFC5090] has not.  One explanation may be that implementors
    disagreed with the trade-offs made in the updated specification.
    It may have been better to simply document the existing format, and
    request IANA allocation of two attributes.  The resulting design
    would have used nested attributes, but may have gained more
    wide-spread implementation.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/49>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 12:15:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6D693A6AEE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 12:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.408
X-Spam-Level: *
X-Spam-Status: No, score=1.408 tagged_above=-999 required=5 tests=[AWL=-0.512, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xc4m5oeAcr4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 12:15:24 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B6FFD3A6AF1 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 12:15:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQmPp-000Dh3-HI for radiusext-data0@psg.com; Mon, 21 Jun 2010 19:12:17 +0000
Received: from [65.55.116.28] (helo=blu0-omc1-s17.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OQmPm-000Dgk-Uk for radiusext@ops.ietf.org; Mon, 21 Jun 2010 19:12:15 +0000
Received: from BLU137-DS3 ([65.55.116.8]) by blu0-omc1-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 21 Jun 2010 12:12:13 -0700
X-Originating-IP: [131.107.0.117]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS3D3993A6B458AD2CF387E93C30@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Reminder: Last Look at RADIUS Design Guidelines
Date: Mon, 21 Jun 2010 12:12:11 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01CB113A.FA9F4B70"
X-Mailer: Microsoft Outlook 14.0
Thread-index: AcsRdaUIvQgmEsXQT5GVbOyxBHff/A==
Content-Language: en-us
X-OriginalArrivalTime: 21 Jun 2010 19:12:13.0832 (UTC) FILETIME=[A80AD880:01CB1175]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0005_01CB113A.FA9F4B70
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a reminder of an ongoing "last look" at the RADIUS Design Guidelines
document, prior to its being approval by the IETF for publication as a Best
Current Practice (BCP). 

The document is available for inspection here:
http://tools.ietf.org/id/draft-ietf-radext-design

The "last look" will last until June 28, 2010.  Comments may be submitted in
any of the following ways:

a. Submission via the RADEXT TRAC system:
http://trac.tools.ietf.org/wg/radext/trac/newticket

b. Comments sent to the RADEXT WG mailing list (radiusext@ops.ietf.org).


------=_NextPart_000_0005_01CB113A.FA9F4B70
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>This is a =
reminder of an ongoing &quot;last look&quot; at the RADIUS Design =
Guidelines document, prior to its being approval by the IETF for =
publication as a Best Current Practice (BCP). <br><br>The document is =
available for inspection =
here:<br>http://tools.ietf.org/id/draft-ietf-radext-design<br><br>The =
&quot;last look&quot; will last until June 28, 2010.&nbsp; Comments may =
be submitted in any of the following ways:<br><br>a. Submission via the =
RADEXT TRAC system: =
http://trac.tools.ietf.org/wg/radext/trac/newticket<br><br>b. Comments =
sent to the RADEXT WG mailing list =
(radiusext@ops.ietf.org).<o:p></o:p></p></div></body></html>
------=_NextPart_000_0005_01CB113A.FA9F4B70--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 13:16:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78C4A3A68D5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 13:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIZKnosH6CyT for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 13:16:24 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6BB693A68B8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 13:16:24 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQnLo-000Mjg-2A for radiusext-data0@psg.com; Mon, 21 Jun 2010 20:12:12 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQnLk-000MjD-9n for radiusext@ops.ietf.org; Mon, 21 Jun 2010 20:12:08 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQnLg-0002qX-90; Mon, 21 Jun 2010 13:12:04 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 20:12:04 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: [radext] #50: Section 2
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/50
Message-ID: <066.141c2ea2d0d450221123bf29bcda84f2@tools.ietf.org>
X-Trac-Ticket-ID: 50
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#50: Section 2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  minor                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
 Basic data types use one of the existing RADIUS data types as defined
    below, encapsulated in a [RFC2865] RADIUS attribute, or in a
    [RFC2865] RADIUS VSA.

 [BA] The basic types are defined in Section 2.1. Recommended change:

    Basic data types use one of the existing RADIUS data types defined in
 Section 2.1, encapsulated in a [RFC2865] RADIUS attribute, or in a
    [RFC2865] RADIUS VSA.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/50>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 14:08:32 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 495663A68AD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 14:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.421
X-Spam-Level: 
X-Spam-Status: No, score=-102.421 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XwjOwWgyHcb for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 14:08:29 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 722483A684E for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 14:08:29 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQoCB-0004q6-G8 for radiusext-data0@psg.com; Mon, 21 Jun 2010 21:06:19 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQoC9-0004pf-3j for radiusext@ops.ietf.org; Mon, 21 Jun 2010 21:06:17 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQoC6-00064j-UR; Mon, 21 Jun 2010 14:06:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 21:06:14 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #49: B.10
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/49#comment:1
Message-ID: <075.2d70bde77f962ddbfb6ead707fff5e00@tools.ietf.org>
References: <066.86883efddb9747b3070442cd0525945d@tools.ietf.org>
X-Trac-Ticket-ID: 49
In-Reply-To: <066.86883efddb9747b3070442cd0525945d@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#49: B.10
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  critical                   |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…
  * severity:  Waiting for Shepherd Writeup => Submitted WG Document


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/49#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 14:10:03 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29E113A6881 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 14:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.422
X-Spam-Level: 
X-Spam-Status: No, score=-102.422 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B0e1EyUBtP4R for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 14:10:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id CBDCC3A6863 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 14:10:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQoBM-0004gf-Ly for radiusext-data0@psg.com; Mon, 21 Jun 2010 21:05:28 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQoBJ-0004gD-KN for radiusext@ops.ietf.org; Mon, 21 Jun 2010 21:05:26 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQoBG-00062Z-GU; Mon, 21 Jun 2010 14:05:22 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 21:05:22 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #31: Section 2.1
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/31#comment:2
Message-ID: <075.86960762b07cfa7ae68eb1b594565c74@tools.ietf.org>
References: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
X-Trac-Ticket-ID: 31
In-Reply-To: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#31: Section 2.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  minor                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/31#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 21 14:10:08 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3674D3A6881 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 14:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.424
X-Spam-Level: 
X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wXd2l9e73zc for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 21 Jun 2010 14:10:06 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 416AA3A687C for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 21 Jun 2010 14:10:06 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OQoCu-0004vM-7G for radiusext-data0@psg.com; Mon, 21 Jun 2010 21:07:04 +0000
Received: from [2001:1890:1112:1::2a] (helo=zinfandel.tools.ietf.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <trac@tools.ietf.org>) id 1OQoCr-0004v5-JH for radiusext@ops.ietf.org; Mon, 21 Jun 2010 21:07:01 +0000
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQoCp-00064y-VE; Mon, 21 Jun 2010 14:06:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: aland@deployingradius.com, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Mon, 21 Jun 2010 21:06:59 -0000
Reply-To: radiusext@ops.ietf.org
X-URL: http://tools.ietf.org/radext/
Subject: Re: [radext] #48: B.6
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/48#comment:1
Message-ID: <075.115578fef3e62c7f031eb07091287d8c@tools.ietf.org>
References: <066.d6ad801904e0d402bede96ab040ae3fd@tools.ietf.org>
X-Trac-Ticket-ID: 48
In-Reply-To: <066.d6ad801904e0d402bede96ab040ae3fd@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: aland@deployingradius.com, bernard_aboba@hotmail.com, radiusext@ops.ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

#48: B.6
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  major                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/48#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 22 13:59:23 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B202D3A69E2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 22 Jun 2010 13:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.405
X-Spam-Level: *
X-Spam-Status: No, score=1.405 tagged_above=-999 required=5 tests=[AWL=-0.701, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrC0IBG5kHvE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 22 Jun 2010 13:59:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8BB4C3A68C5 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 22 Jun 2010 13:59:22 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1ORATD-000Ibb-Fo for radiusext-data0@psg.com; Tue, 22 Jun 2010 20:53:23 +0000
Received: from [65.55.116.15] (helo=blu0-omc1-s4.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1ORAT9-000IZL-Mf for radiusext@ops.ietf.org; Tue, 22 Jun 2010 20:53:19 +0000
Received: from BLU137-DS14 ([65.55.116.9]) by blu0-omc1-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Jun 2010 13:53:18 -0700
X-Originating-IP: [72.11.66.126]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS14C8498664F74977DE667493C40@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Agenda for Virtual Interim Meeting - Take One
Date: Tue, 22 Jun 2010 13:53:16 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D1_01CB1212.44478440"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsSScG0jYMs0oAmTIGttiITiTawswAAyTpw
Content-Language: en-us
X-OriginalArrivalTime: 22 Jun 2010 20:53:18.0362 (UTC) FILETIME=[F1326FA0:01CB124C]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_00D1_01CB1212.44478440
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Here is a first stab at an agenda for the RADEXT Virtual Interim meeting.
The overall goal is to focus on re-invigorating long-stuck work items.  If
you have additional agenda items, please send them to Mauricio or myself. 

 

RADEXT WG Virtual Interim Agenda

 

Presentations:  TBD

Jabber room:  radext at jabber.ietf.org

WebEx:  TBD

 

Chairs

        Bernard Aboba <bernard_aboba at hotmail.com> 

        Mauricio Sanchez <mauricio.sanchez at hp.com>

 

Agenda

 

Preliminaries (10 minutes)

 

     Attendance

     Note takers

     Agenda bash

     Document Status

 

Documents Completing IETF Last Call (40 minutes)

 

RADIUS over TCP, Alan DeKok (10 minutes)

http://tools.ietf.org/html/draft-ietf-radext-tcp

 

Design Guidelines, Alan DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

 

RADEXT WG Work Items (30 minutes)

 

Extended RADIUS Attributes, Alan DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-extended-attributes


------=_NextPart_000_00D1_01CB1212.44478440
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal>Here is a first stab at an agenda for the RADEXT =
Virtual
Interim meeting.&nbsp; The overall goal is to focus on re-invigorating
long-stuck work items.&nbsp; If you have additional agenda items, please =
send
them to Mauricio or myself. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>RADEXT WG Virtual Interim Agenda<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Presentations:&nbsp; TBD<o:p></o:p></p>

<p class=3DMsoNormal>Jabber room:&nbsp; radext at =
jabber.ietf.org<o:p></o:p></p>

<p class=3DMsoNormal>WebEx:&nbsp; TBD<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Chairs<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bernard =
Aboba
&lt;bernard_aboba at hotmail.com&gt; <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mauricio =
Sanchez
&lt;mauricio.sanchez at hp.com&gt;<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Agenda<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>Preliminaries (10 minutes)<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Attendance<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Note takers<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Document =
Status<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Documents Completing IETF Last Call (40 =
minutes)<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>RADIUS over TCP, Alan DeKok (10 =
minutes)<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-tcp<o:p></=
o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>Design Guidelines, Alan DeKok (30 =
minutes)<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-design-gui=
delines<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>RADEXT WG Work Items (30 minutes)<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Extended RADIUS Attributes, Alan DeKok (30 =
minutes)<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-extended-a=
ttributes<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_00D1_01CB1212.44478440--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun 23 01:19:12 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29F303A6A56 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 23 Jun 2010 01:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.535
X-Spam-Level: 
X-Spam-Status: No, score=0.535 tagged_above=-999 required=5 tests=[AWL=-0.459, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lN1ij6O9mEhA for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 23 Jun 2010 01:19:10 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9432B3A6970 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 23 Jun 2010 01:19:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1ORL6P-00035e-9B for radiusext-data0@psg.com; Wed, 23 Jun 2010 08:14:33 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1ORL6N-00035A-BK for radiusext@ops.ietf.org; Wed, 23 Jun 2010 08:14:31 +0000
Message-ID: <4C21C263.6060001@deployingradius.com>
Date: Wed, 23 Jun 2010 10:14:27 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Agenda for Virtual Interim Meeting - Take One
References: <BLU137-DS14C8498664F74977DE667493C40@phx.gbl>
In-Reply-To: <BLU137-DS14C8498664F74977DE667493C40@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> Here is a first stab at an agenda for the RADEXT Virtual Interim
..
> RADIUS over TCP, Alan DeKok (10 minutes)

  Goal: WG consensus && document finalization.

> Design Guidelines, Alan DeKok (30 minutes)

  Goal: WG consensus && publication.

> Extended RADIUS Attributes, Alan DeKok (30 minutes)

  Goal: what next?

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sat Jun 26 18:28:30 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FD503A6976 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 26 Jun 2010 18:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.893
X-Spam-Level: **
X-Spam-Status: No, score=2.893 tagged_above=-999 required=5 tests=[AWL=-2.212, BAYES_95=3, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFeJorgyVs6s for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 26 Jun 2010 18:28:29 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1F8593A696B for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 26 Jun 2010 18:28:29 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OSgbL-0007vg-Jg for radiusext-data0@psg.com; Sun, 27 Jun 2010 01:24:03 +0000
Received: from [65.55.116.41] (helo=blu0-omc1-s30.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OSgbI-0007vR-Ux for radiusext@ops.ietf.org; Sun, 27 Jun 2010 01:24:01 +0000
Received: from BLU137-DS17 ([65.55.116.9]) by blu0-omc1-s30.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 26 Jun 2010 18:24:00 -0700
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS17BD61277AE413BBA78D4193C90@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Doodle Poll for RADEXT Virtual Interim
Date: Sat, 26 Jun 2010 18:24:31 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01CB155C.D27D4270"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsQrXpzOc8l2GT/T8udWzYyz3YypgE6a9BQ
Content-Language: en-us
X-OriginalArrivalTime: 27 Jun 2010 01:24:00.0087 (UTC) FILETIME=[6BABFE70:01CB1597]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0088_01CB155C.D27D4270
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The RADEXT WG is considering scheduling a Virtual Interim meeting during the
week of July 12, 2010. 

Please fill out a Doodle Poll indicating your availability:
http://www.doodle.com/362t54udqbbkupdp

 

 


------=_NextPart_000_0088_01CB155C.D27D4270
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>The RADEXT WG is considering </span><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>scheduling a Virtual =
Interim
meeting </span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>during </span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>the week of July 12, 2010. <br>
<br>
Please fill out a Doodle Poll indicating your availability:<br>
http://www.doodle.com/362t54udqbbkupdp</span><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_0088_01CB155C.D27D4270--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Sat Jun 26 18:28:35 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B496C3A6976 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 26 Jun 2010 18:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.454
X-Spam-Level: *
X-Spam-Status: No, score=1.454 tagged_above=-999 required=5 tests=[AWL=-0.652, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id byNAjHlfh7dd for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 26 Jun 2010 18:28:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BC91F3A696B for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 26 Jun 2010 18:28:34 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OSgap-0007uM-7S for radiusext-data0@psg.com; Sun, 27 Jun 2010 01:23:31 +0000
Received: from [65.55.116.41] (helo=blu0-omc1-s30.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OSgam-0007u1-Bg for radiusext@ops.ietf.org; Sun, 27 Jun 2010 01:23:28 +0000
Received: from BLU137-DS17 ([65.55.116.8]) by blu0-omc1-s30.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 26 Jun 2010 18:23:26 -0700
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS17B50567EB4D713B67946F93C90@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: FINAL REMINDER: Last Look at RADIUS Design Guidelines
Date: Sat, 26 Jun 2010 18:21:20 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01CB155C.BE8C2060"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsRdaUIvQgmEsXQT5GVbOyxBHff/AEIUzDg
Content-Language: en-us
X-OriginalArrivalTime: 27 Jun 2010 01:23:26.0634 (UTC) FILETIME=[57BB78A0:01CB1597]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0083_01CB155C.BE8C2060
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a reminder of an ongoing "last look" at the RADIUS Design Guidelines
document, prior to its approval by the IETF for publication as a Best
Current Practice (BCP). 

The document is available for inspection here:
http://tools.ietf.org/id/draft-ietf-radext-design

The "last look" will last until Monday, June 28, 2010.  Comments may be
submitted in any of the following ways:

a. Submission via the RADEXT TRAC system:
http://trac.tools.ietf.org/wg/radext/trac/newticket

b. Comments sent to the RADEXT WG mailing list (radiusext@ops.ietf.org).


------=_NextPart_000_0083_01CB155C.BE8C2060
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal>This is a reminder of an ongoing &quot;last =
look&quot; at
the RADIUS Design Guidelines document, prior to its approval by the IETF =
for
publication as a Best Current Practice (BCP). <br>
<br>
The document is available for inspection here:<br>
http://tools.ietf.org/id/draft-ietf-radext-design<br>
<br>
The &quot;last look&quot; will last until <span =
style=3D'color:#1F497D'>Monday, </span>June
28, 2010.&nbsp; Comments may be submitted in any of the following =
ways:<br>
<br>
a. Submission via the RADEXT TRAC system:
http://trac.tools.ietf.org/wg/radext/trac/newticket<br>
<br>
b. Comments sent to the RADEXT WG mailing list =
(radiusext@ops.ietf.org).<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0083_01CB155C.BE8C2060--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 28 12:34:04 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3562B3A691D for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 28 Jun 2010 12:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.434
X-Spam-Level: *
X-Spam-Status: No, score=1.434 tagged_above=-999 required=5 tests=[AWL=-0.672, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOYkVnXgSkS8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 28 Jun 2010 12:34:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C446A3A696D for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 28 Jun 2010 12:33:59 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OTK0n-0006a2-W8 for radiusext-data0@psg.com; Mon, 28 Jun 2010 19:28:58 +0000
Received: from [65.55.116.28] (helo=blu0-omc1-s17.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OTK0l-0006ZM-5j for radiusext@ops.ietf.org; Mon, 28 Jun 2010 19:28:55 +0000
Received: from BLU137-W14 ([65.55.116.9]) by blu0-omc1-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Jun 2010 12:27:34 -0700
Message-ID: <BLU137-W14F678A9C2C685D698CEA393CA0@phx.gbl>
Content-Type: multipart/alternative; boundary="_9de5580f-3329-4b98-bc38-0b41ce11d790_"
X-Originating-IP: [131.107.0.81]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim:  July 12, 2010
Date: Mon, 28 Jun 2010 12:27:34 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Jun 2010 19:27:34.0535 (UTC) FILETIME=[F5B73970:01CB16F7]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_9de5580f-3329-4b98-bc38-0b41ce11d790_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The RADEXT WG will be holding a Virtual Interm Meeting on Monday=2C July 12=
=2C 2010 from 11 AM - 1:30 PM Pacific Time.   A strawman agenda is enclosed=
 below=3B details of the conference call parameters will be posted to the l=
ist.  If you have additional agenda items=2C please send them to Mauricio o=
r myself.=20



RADEXT WG Virtual Interim Agenda

Monday=2C July 12=2C 2010

11 AM - 1:30 PM Pacific Time

=20

Presentations:  http://www.drizzle.com/~aboba/RADEXT/July-Interim/

Jabber room:  radext
at jabber.ietf.org

Conference parameters:=20
TBD

=20

=20

Chairs

        Bernard Aboba
<bernard_aboba at hotmail.com>=20

        Mauricio
Sanchez <mauricio.sanchez at hp.com>

=20

Agenda

=20

11:00- 11:10 AM PT  Preliminaries (10 minutes)

=20

     Attendance

     Note takers

     Agenda bash

     Document Status

=20

Documents Completing IETF Last Call (40 minutes)

=20

11:10 AM - 11:20 AM PT  RADIUS over TCP=2C Alan DeKok (10 minutes)

http://tools.ietf.org/html/draft-ietf-radext-tcp

=20

11:20 AM- 11:50 AM PT  Design Guidelines=2C Alan DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

=20

RADEXT WG Work Items (30 minutes)

=20

11:50 AM - 12:20 PM PT  Extended RADIUS Attributes=2C Alan DeKok (30 minute=
s)

http://tools.ietf.org/html/draft-ietf-radext-extended-attributes

=20

=20

=20


 		 	   		  =

--_9de5580f-3329-4b98-bc38-0b41ce11d790_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The RADEXT WG will be holding a Virtual Interm Meeting on Monday=2C July 12=
=2C 2010 from 11 AM - 1:30 PM Pacific Time.&nbsp=3B&nbsp=3B A strawman agen=
da is enclosed below=3B details of the conference call parameters will be p=
osted to the list.&nbsp=3B If you have additional agenda items=2C please se=
nd them to Mauricio or myself. <br><br><meta http-equiv=3D"Content-Type" co=
ntent=3D"text/html=3B charset=3Dutf-8"><meta name=3D"ProgId" content=3D"Wor=
d.Document"><meta name=3D"Generator" content=3D"Microsoft Word 14"><meta na=
me=3D"Originator" content=3D"Microsoft Word 14"><link rel=3D"File-List" hre=
f=3D"file:///C:%5CUsers%5Cbernarda%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%=
5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file:///C:%5CUsers%5Cbern=
arda%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><l=
ink rel=3D"colorSchemeMapping" href=3D"file:///C:%5CUsers%5Cbernarda%5CAppD=
ata%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[=
if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45=3B-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"267">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri=3B
	panose-1:2 15 5 2 2 2 4 3 2 4=3B
	mso-font-alt:"Electra LH Regular"=3B
	mso-font-charset:0=3B
	mso-generic-font-family:swiss=3B
	mso-font-pitch:variable=3B
	mso-font-signature:-520092929 1073786111 9 0 415 0=3B}
 /* Style Definitions */
 p.MsoNormal=2C li.MsoNormal=2C div.MsoNormal
	{mso-style-unhide:no=3B
	mso-style-qformat:yes=3B
	mso-style-parent:""=3B
	margin:0in=3B
	margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-fareast-font-family:"Times New Roman"=3B
	mso-bidi-font-family:"Times New Roman"=3B}
a:link=2C span.MsoHyperlink
	{mso-style-priority:99=3B
	font-family:"Times New Roman"=2C"serif"=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:blue=3B
	text-decoration:underline=3B
	text-underline:single=3B}
a:visited=2C span.MsoHyperlinkFollowed
	{mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	color:purple=3B
	mso-themecolor:followedhyperlink=3B
	text-decoration:underline=3B
	text-underline:single=3B}
span.EmailStyle16
	{mso-style-type:personal=3B
	mso-style-noshow:yes=3B
	mso-style-unhide:no=3B
	mso-ansi-font-size:11.0pt=3B
	mso-bidi-font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:windowtext=3B}
.MsoChpDefault
	{mso-style-type:export-only=3B
	mso-default-props:yes=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:Calibri=3B}
.MsoPapDefault
	{mso-style-type:export-only=3B}
@page WordSection1
	{size:8.5in 11.0in=3B
	margin:1.0in 1.0in 1.0in 1.0in=3B
	mso-header-margin:.5in=3B
	mso-footer-margin:.5in=3B
	mso-paper-source:0=3B}
div.WordSection1
	{page:WordSection1=3B}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal"=3B
	mso-tstyle-rowband-size:0=3B
	mso-tstyle-colband-size:0=3B
	mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	mso-style-parent:""=3B
	mso-padding-alt:0in 5.4pt 0in 5.4pt=3B
	mso-para-margin:0in=3B
	mso-para-margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B}
</style>
<![endif]-->

<p class=3D"MsoNormal">RADEXT WG Virtual Interim Agenda<o:p></o:p></p>

<p class=3D"MsoNormal">Monday=2C July 12=2C 2010<o:p></o:p></p>

<p class=3D"MsoNormal">11 AM - 1:30 PM Pacific Time<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">Presentations:<span style=3D"">&nbsp=3B </span><a hr=
ef=3D"http://www.drizzle.com/%7Eaboba/RADEXT/July-Interim/">http://www.driz=
zle.com/~aboba/RADEXT/July-Interim/</a><o:p></o:p></p>

<p class=3D"MsoNormal">Jabber room:<span style=3D"">&nbsp=3B </span>radext
at jabber.ietf.org<o:p></o:p></p>

<p class=3D"MsoNormal">Conference parameters:<span style=3D"">&nbsp=3B
</span>TBD<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Chairs<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Bernard Aboba
&lt=3Bbernard_aboba at hotmail.com&gt=3B <o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Mauricio
Sanchez &lt=3Bmauricio.sanchez at hp.com&gt=3B<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Agenda<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:00- 11:10 AM PT&nbsp=3B Preliminaries (10 minutes=
)<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Attendance<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Note takers<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Agenda bash<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Document Status<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Documents Completing IETF Last Call (40 minutes)<o:p=
></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:10 AM - 11:20 AM PT&nbsp=3B RADIUS over TCP=2C Al=
an DeKok (10 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-tcp">http://tools.ietf.org/html/draft-ietf-radext-tcp</a><o:p></o:p></p=
>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:20 AM- 11:50 AM PT&nbsp=3B Design Guidelines=2C A=
lan DeKok (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-design-guidelines">http://tools.ietf.org/html/draft-ietf-radext-design-=
guidelines</a><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">RADEXT WG Work Items (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:50 AM - 12:20 PM PT&nbsp=3B Extended RADIUS Attri=
butes=2C Alan DeKok (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-extended-attributes">http://tools.ietf.org/html/draft-ietf-radext-exten=
ded-attributes</a><o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<br> 		 	   		  </body>
</html>=

--_9de5580f-3329-4b98-bc38-0b41ce11d790_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 28 15:34:01 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0578D3A6A09 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 28 Jun 2010 15:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.741
X-Spam-Level: 
X-Spam-Status: No, score=-100.741 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 649Wem19mMHJ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 28 Jun 2010 15:33:59 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EA73C28C134 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 28 Jun 2010 15:33:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OTMqR-0004Co-KT for radiusext-data0@psg.com; Mon, 28 Jun 2010 22:30:27 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <root@core3.amsl.com>) id 1OTMqP-0004CV-0s for radiusext@ops.ietf.org; Mon, 28 Jun 2010 22:30:25 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 6814C3A6A09; Mon, 28 Jun 2010 15:30:01 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: RADEXT WG Virtual Interim Meeting, July 12, 2010 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100628223013.6814C3A6A09@core3.amsl.com>
Date: Mon, 28 Jun 2010 15:30:02 -0700 (PDT)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

The RADEXT WG will be holding a virtual interim meeting on Monday, July 
12, 2010, from 11 AM - 1:30 PM Pacific Time.

A strawman agenda has been posted to the list:
http://ops.ietf.org/lists/radiusext/2010/msg00483.html

Conference call parameters will be posted to the mailing list once they 
are available:
http://ops.ietf.org/lists/radiusext/2010/threads.html

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Mon Jun 28 15:50:44 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0A673A69F7 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 28 Jun 2010 15:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.44
X-Spam-Level: *
X-Spam-Status: No, score=1.44 tagged_above=-999 required=5 tests=[AWL=-0.665, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TI90ALmez00W for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 28 Jun 2010 15:50:44 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5EA6C3A69E3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 28 Jun 2010 15:50:43 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OTN6t-0005zk-Fh for radiusext-data0@psg.com; Mon, 28 Jun 2010 22:47:27 +0000
Received: from [65.55.116.41] (helo=blu0-omc1-s30.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OTN6r-0005zS-JQ for radiusext@ops.ietf.org; Mon, 28 Jun 2010 22:47:25 +0000
Received: from BLU137-DS2 ([65.55.116.8]) by blu0-omc1-s30.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Jun 2010 15:47:24 -0700
X-Originating-IP: [131.107.0.75]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS2E177C3B7D37DDBA627E893CA0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Meeting
Date: Mon, 28 Jun 2010 15:47:23 -0700
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcsXE8hkC/pKrz4cQcW9WjE4ShNKAgAABcPw
Content-Language: en-us
X-OriginalArrivalTime: 28 Jun 2010 22:47:24.0243 (UTC) FILETIME=[E0237A30:01CB1713]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 14.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16011104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN=radiusext@ops.ietf.org;RSVP=TRUE:mailto:radiusext@ops.ietf.org
CLASS:PUBLIC
CREATED:20100628T224723Z
DESCRIPTION:RADEXT WG Virtual Interim Agenda\nMonday\, July 12\, 2010\n11 A
	M - 1:30 PM Pacific Time\n\nPresentations:  http://www.drizzle.com/~aboba/
	RADEXT/July-Interim/\nJabber room:  radext at jabber.ietf.org\nConference 
	parameters:  TBD\n\n \nChairs\n        Bernard Aboba <bernard_aboba at hot
	mail.com> \n        Mauricio Sanchez <mauricio.sanchez at hp.com>\n \nAgen
	da\n \nPreliminaries (10 minutes)\n \n     Attendance\n     Note takers\n 
	    Agenda bash\n     Document Status\n \nDocuments Completing IETF Last C
	all (40 minutes)\n \nRADIUS over TCP\, Alan DeKok (10 minutes)\nhttp://too
	ls.ietf.org/html/draft-ietf-radext-tcp\n \nDesign Guidelines\, Alan DeKok 
	(30 minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-design-guidelin
	es\n \nRADEXT WG Work Items (30 minutes)\n \nExtended RADIUS Attributes\, 
	Alan DeKok (30 minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-exte
	nded-attributes\n\n\n\n\n
DTEND;TZID="Pacific Standard Time":20100712T133000
DTSTAMP:20100628T224723Z
DTSTART;TZID="Pacific Standard Time":20100712T110000
LAST-MODIFIED:20100628T224723Z
LOCATION:Teleconference
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim Meeting
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E00800000000804B061CD916CB01000000000000000
	010000000183AD543CB686B41B739B4F5CD5A595D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.01.0240.003">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">RADEXT WG Virtual Interim Agenda</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN
	 LANG="en-us"><FONT FACE="Calibri">Monday\, July 12\, 2010</FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">11 AM - 1:30 PM P
	acific Time</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE=
	"Calibri">Presentations:&nbsp\;</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A
	 HREF="http://www.drizzle.com/~aboba/RADEXT/July-Interim/"><SPAN LANG="en-
	us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://www.drizzle.com/~aboba/
	RADEXT/July-Interim/</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN 
	LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Cali
	bri">Jabber room:&nbsp\; radext at jabber.ietf.org</FONT></SPAN></P>\n\n<P
	 DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Conference parameters:&nb
	sp\; TBD</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Ca
	libri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FA
	CE="Calibri">Chairs</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FO
	NT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\;&nbsp\;&nbsp\;&nbsp\; Bernar
	d Aboba &lt\;bernard_aboba at hotmail.com&gt\; </FONT></SPAN></P>\n\n<P DI
	R=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\;
	&nbsp\;&nbsp\;&nbsp\; Mauricio Sanchez &lt\;mauricio.sanchez at hp.com&gt\
	;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">
	&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Cal
	ibri">Agenda</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE
	="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FON
	T FACE="Calibri">Preliminaries (10 minutes)</FONT></SPAN></P>\n\n<P DIR=LT
	R><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P 
	DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp
	\; Attendance</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FAC
	E="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\; Note takers</FONT></SPAN></P>\n\n
	<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&n
	bsp\; Agenda bash</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT
	 FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\; Document Status</FONT></SPAN>
	</P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</FONT><
	/SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Documents
	 Completing IETF Last Call (40 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><S
	PAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=
	LTR><SPAN LANG="en-us"><FONT FACE="Calibri">RADIUS over TCP\, Alan DeKok (
	10 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><A H
	REF="http://tools.ietf.org/html/draft-ietf-radext-tcp"><SPAN LANG="en-us">
	<U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf.org/html/draft-i
	etf-radext-tcp</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="
	en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&
	nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Cali
	bri">Design Guidelines\, Alan DeKok (30 minutes)</FONT></SPAN></P>\n\n<P D
	IR=LTR><SPAN LANG="en-us"></SPAN><A HREF="http://tools.ietf.org/html/draft
	-ietf-radext-design-guidelines"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF
	" FACE="Calibri">http://tools.ietf.org/html/draft-ietf-radext-design-guide
	lines</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></
	SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</F
	ONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">RADE
	XT WG Work Items (30 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="
	en-us"><FONT FACE="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN 
	LANG="en-us"><FONT FACE="Calibri">Extended RADIUS Attributes\, Alan DeKok 
	(30 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><A 
	HREF="http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf
	.org/html/draft-ietf-radext-extended-attributes</FONT></U></SPAN><SPAN LAN
	G="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN></P>\n<BR>\n<BR>\n<BR>\n\n<
	/BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Tue Jun 29 03:45:52 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01FB03A680E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 29 Jun 2010 03:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.721
X-Spam-Level: 
X-Spam-Status: No, score=-8.721 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWGQ27IBgOtW for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 29 Jun 2010 03:45:50 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7E9693A68DA for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 29 Jun 2010 03:45:50 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OTYCc-0008H1-8J for radiusext-data0@psg.com; Tue, 29 Jun 2010 10:38:06 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72 (FreeBSD)) (envelope-from <wdec@cisco.com>) id 1OTYCZ-0008GI-Hu for radiusext@ops.ietf.org; Tue, 29 Jun 2010 10:38:04 +0000
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGlqKUyrRN+J/2dsb2JhbACSVYxmcaQPmk+FJAQ
X-IronPort-AV: E=Sophos;i="4.53,503,1272844800";  d="scan'208";a="339469475"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-1.cisco.com with ESMTP; 29 Jun 2010 10:37:49 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o5TAbVYC004143; Tue, 29 Jun 2010 10:37:48 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 29 Jun 2010 12:37:48 +0200
Received: from 10.55.215.35 ([10.55.215.35]) by XMB-AMS-111.cisco.com ([144.254.74.86]) with Microsoft Exchange Server HTTP-DAV ; Tue, 29 Jun 2010 10:37:47 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Tue, 29 Jun 2010 12:38:02 +0200
Subject: Re: RADEXT Virtual Interim Meeting
From: Wojciech Dec <wdec@cisco.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: <radiusext@ops.ietf.org>
Message-ID: <C84F99AA.52E8%wdec@cisco.com>
Thread-Topic: RADEXT Virtual Interim Meeting
Thread-Index: AcsXE8hkC/pKrz4cQcW9WjE4ShNKAgAABcPwABjRsmw=
In-Reply-To: <BLU137-DS2E177C3B7D37DDBA627E893CA0@phx.gbl>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Jun 2010 10:37:48.0246 (UTC) FILETIME=[1E062F60:01CB1777]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hello Bernard,

Could you please also allow 10mins for draft-ietf-radext-ipv6-access?

Also, given the time of the call, would you mind hosting this slot up
towards the beginning?

Thanks,
Woj.



On 29/06/2010 00:47, "Bernard Aboba" <bernard_aboba@hotmail.com> wrote:

> 


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

From owner-radiusext@ops.ietf.org  Wed Jun 30 12:52:25 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8B463A68F3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 30 Jun 2010 12:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.381
X-Spam-Level: *
X-Spam-Status: No, score=1.381 tagged_above=-999 required=5 tests=[AWL=-0.725, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GtIG7PYmN8ae for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 30 Jun 2010 12:52:24 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BD61F3A689D for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 30 Jun 2010 12:52:23 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1OU3Fr-00090R-3t for radiusext-data0@psg.com; Wed, 30 Jun 2010 19:47:31 +0000
Received: from [65.55.116.13] (helo=blu0-omc1-s2.blu0.hotmail.com) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1OU3Fo-000903-90 for radiusext@ops.ietf.org; Wed, 30 Jun 2010 19:47:28 +0000
Received: from BLU137-W22 ([65.55.116.7]) by blu0-omc1-s2.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 30 Jun 2010 12:47:27 -0700
Message-ID: <BLU137-W2228A03C45D8DE302DFD8893CC0@phx.gbl>
Content-Type: multipart/alternative; boundary="_1a4ef98c-2c98-4fa1-82c4-d54a03144040_"
X-Originating-IP: [131.107.0.111]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda - Take Two
Date: Wed, 30 Jun 2010 12:47:27 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 30 Jun 2010 19:47:27.0124 (UTC) FILETIME=[11615D40:01CB188D]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_1a4ef98c-2c98-4fa1-82c4-d54a03144040_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable




RADEXT WG Virtual Interim Agenda

Monday=2C July 12=2C 2010

11 AM - 1:30 PM Pacific Time

=20

Presentations:  http://www.drizzle.com/~aboba/RADEXT/July-Interim/

Jabber room:  radext
at jabber.ietf.org

Conference parameters:=20
TBD

=20



Chairs

        Bernard Aboba
<bernard_aboba at hotmail.com>=20

        Mauricio
Sanchez <mauricio.sanchez at hp.com>

=20

Agenda

=20

11:00 AM =96 11:10 AM PT Preliminaries (10 minutes)

=20

     Attendance

     Note takers

     Agenda bash

     Document Status

=20

Documents Completing IETF Last Call (40 minutes)

=20

11:20 AM =96 11:30 AM PT RADIUS over TCP=2C Alan DeKok (10
minutes)

http://tools.ietf.org/html/draft-ietf-radext-tcp

=20

11:30 =96 12:00 PM PT Design Guidelines=2C Alan DeKok (30
minutes)

http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

=20

Documents Completing RADEXT WG Last Call

=20

12:00 PM =96 12:15 PM PT IPv6 Access=2C W. Dec (15 minutes)

http://tools.ietf.org/html/draft-ietf-radext-ipv6-access

=20

RADEXT WG Work Items (30 minutes)

=20

12:15 PM PT =96 12:45 PM PT Extended RADIUS Attributes=2C Alan
DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-extended-attributes

 		 	   		  =

--_1a4ef98c-2c98-4fa1-82c4-d54a03144040_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
<meta http-equiv=3D"Content-Type" content=3D"text/html=3B charset=3Dutf-8">=
<meta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" co=
ntent=3D"Microsoft Word 14"><meta name=3D"Originator" content=3D"Microsoft =
Word 14"><link rel=3D"File-List" href=3D"file:///C:%5CUsers%5Cbernarda%5CAp=
pData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><!--[if gte m=
so 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file:///C:%5CUsers%5Cbern=
arda%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><l=
ink rel=3D"colorSchemeMapping" href=3D"file:///C:%5CUsers%5Cbernarda%5CAppD=
ata%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[=
if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45=3B-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"267">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri=3B
	panose-1:2 15 5 2 2 2 4 3 2 4=3B
	mso-font-alt:"Electra LH Regular"=3B
	mso-font-charset:0=3B
	mso-generic-font-family:swiss=3B
	mso-font-pitch:variable=3B
	mso-font-signature:-520092929 1073786111 9 0 415 0=3B}
 /* Style Definitions */
 p.MsoNormal=2C li.MsoNormal=2C div.MsoNormal
	{mso-style-unhide:no=3B
	mso-style-qformat:yes=3B
	mso-style-parent:""=3B
	margin:0in=3B
	margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-fareast-font-family:"Times New Roman"=3B
	mso-bidi-font-family:"Times New Roman"=3B}
a:link=2C span.MsoHyperlink
	{mso-style-priority:99=3B
	font-family:"Times New Roman"=2C"serif"=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:blue=3B
	text-decoration:underline=3B
	text-underline:single=3B}
a:visited=2C span.MsoHyperlinkFollowed
	{mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	color:purple=3B
	mso-themecolor:followedhyperlink=3B
	text-decoration:underline=3B
	text-underline:single=3B}
span.EmailStyle16
	{mso-style-type:personal=3B
	mso-style-noshow:yes=3B
	mso-style-unhide:no=3B
	mso-ansi-font-size:11.0pt=3B
	mso-bidi-font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:windowtext=3B}
.MsoChpDefault
	{mso-style-type:export-only=3B
	mso-default-props:yes=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:Calibri=3B}
.MsoPapDefault
	{mso-style-type:export-only=3B}
@page WordSection1
	{size:8.5in 11.0in=3B
	margin:1.0in 1.0in 1.0in 1.0in=3B
	mso-header-margin:.5in=3B
	mso-footer-margin:.5in=3B
	mso-paper-source:0=3B}
div.WordSection1
	{page:WordSection1=3B}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal"=3B
	mso-tstyle-rowband-size:0=3B
	mso-tstyle-colband-size:0=3B
	mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	mso-style-parent:""=3B
	mso-padding-alt:0in 5.4pt 0in 5.4pt=3B
	mso-para-margin:0in=3B
	mso-para-margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B}
</style>
<![endif]-->

<p class=3D"MsoNormal">RADEXT WG Virtual Interim Agenda<o:p></o:p></p>

<p class=3D"MsoNormal">Monday=2C July 12=2C 2010<o:p></o:p></p>

<p class=3D"MsoNormal">11 AM - 1:30 PM Pacific Time<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">Presentations:<span style=3D"">&nbsp=3B </span><a hr=
ef=3D"http://www.drizzle.com/%7Eaboba/RADEXT/July-Interim/">http://www.driz=
zle.com/~aboba/RADEXT/July-Interim/</a><o:p></o:p></p>

<p class=3D"MsoNormal">Jabber room:<span style=3D"">&nbsp=3B </span>radext
at jabber.ietf.org<o:p></o:p></p>

<p class=3D"MsoNormal">Conference parameters:<span style=3D"">&nbsp=3B
</span>TBD<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>



<p class=3D"MsoNormal">Chairs<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Bernard Aboba
&lt=3Bbernard_aboba at hotmail.com&gt=3B <o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Mauricio
Sanchez &lt=3Bmauricio.sanchez at hp.com&gt=3B<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Agenda<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:00 AM =96 11:10 AM PT Preliminaries (10 minutes)<=
o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Attendance<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Note takers<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Agenda bash<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Document Status<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Documents Completing IETF Last Call (40 minutes)<o:p=
></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:20 AM =96 11:30 AM PT RADIUS over TCP=2C Alan DeK=
ok (10
minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-tcp">http://tools.ietf.org/html/draft-ietf-radext-tcp</a><o:p></o:p></p=
>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:30 =96 12:00 PM PT Design Guidelines=2C Alan DeKo=
k (30
minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-design-guidelines">http://tools.ietf.org/html/draft-ietf-radext-design-=
guidelines</a><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Documents Completing RADEXT WG Last Call<o:p></o:p><=
/p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">12:00 PM =96 12:15 PM PT IPv6 Access=2C W. Dec (15 m=
inutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-ipv6-access">http://tools.ietf.org/html/draft-ietf-radext-ipv6-access</=
a><o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">RADEXT WG Work Items (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">12:15 PM PT =96 12:45 PM PT Extended RADIUS Attribut=
es=2C Alan
DeKok (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-extended-attributes">http://tools.ietf.org/html/draft-ietf-radext-exten=
ded-attributes</a><o:p></o:p></p>

 		 	   		  </body>
</html>=

--_1a4ef98c-2c98-4fa1-82c4-d54a03144040_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 30 Jun 2010 19:48:23 +0000
Message-ID: <BLU137-W2228A03C45D8DE302DFD8893CC0@phx.gbl>
Content-Type: multipart/alternative; boundary="_1a4ef98c-2c98-4fa1-82c4-d54a03144040_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda - Take Two
Date: Wed, 30 Jun 2010 12:47:27 -0700
MIME-Version: 1.0

--_1a4ef98c-2c98-4fa1-82c4-d54a03144040_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable




RADEXT WG Virtual Interim Agenda

Monday=2C July 12=2C 2010

11 AM - 1:30 PM Pacific Time

=20

Presentations:  http://www.drizzle.com/~aboba/RADEXT/July-Interim/

Jabber room:  radext
at jabber.ietf.org

Conference parameters:=20
TBD

=20



Chairs

        Bernard Aboba
<bernard_aboba at hotmail.com>=20

        Mauricio
Sanchez <mauricio.sanchez at hp.com>

=20

Agenda

=20

11:00 AM =96 11:10 AM PT Preliminaries (10 minutes)

=20

     Attendance

     Note takers

     Agenda bash

     Document Status

=20

Documents Completing IETF Last Call (40 minutes)

=20

11:20 AM =96 11:30 AM PT RADIUS over TCP=2C Alan DeKok (10
minutes)

http://tools.ietf.org/html/draft-ietf-radext-tcp

=20

11:30 =96 12:00 PM PT Design Guidelines=2C Alan DeKok (30
minutes)

http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

=20

Documents Completing RADEXT WG Last Call

=20

12:00 PM =96 12:15 PM PT IPv6 Access=2C W. Dec (15 minutes)

http://tools.ietf.org/html/draft-ietf-radext-ipv6-access

=20

RADEXT WG Work Items (30 minutes)

=20

12:15 PM PT =96 12:45 PM PT Extended RADIUS Attributes=2C Alan
DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-extended-attributes

 		 	   		  =

--_1a4ef98c-2c98-4fa1-82c4-d54a03144040_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
<meta http-equiv=3D"Content-Type" content=3D"text/html=3B charset=3Dutf-8">=
<meta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" co=
ntent=3D"Microsoft Word 14"><meta name=3D"Originator" content=3D"Microsoft =
Word 14"><link rel=3D"File-List" href=3D"file:///C:%5CUsers%5Cbernarda%5CAp=
pData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><!--[if gte m=
so 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file:///C:%5CUsers%5Cbern=
arda%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><l=
ink rel=3D"colorSchemeMapping" href=3D"file:///C:%5CUsers%5Cbernarda%5CAppD=
ata%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[=
if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45=3B-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"267">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri=3B
	panose-1:2 15 5 2 2 2 4 3 2 4=3B
	mso-font-alt:"Electra LH Regular"=3B
	mso-font-charset:0=3B
	mso-generic-font-family:swiss=3B
	mso-font-pitch:variable=3B
	mso-font-signature:-520092929 1073786111 9 0 415 0=3B}
 /* Style Definitions */
 p.MsoNormal=2C li.MsoNormal=2C div.MsoNormal
	{mso-style-unhide:no=3B
	mso-style-qformat:yes=3B
	mso-style-parent:""=3B
	margin:0in=3B
	margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-fareast-font-family:"Times New Roman"=3B
	mso-bidi-font-family:"Times New Roman"=3B}
a:link=2C span.MsoHyperlink
	{mso-style-priority:99=3B
	font-family:"Times New Roman"=2C"serif"=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:blue=3B
	text-decoration:underline=3B
	text-underline:single=3B}
a:visited=2C span.MsoHyperlinkFollowed
	{mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	color:purple=3B
	mso-themecolor:followedhyperlink=3B
	text-decoration:underline=3B
	text-underline:single=3B}
span.EmailStyle16
	{mso-style-type:personal=3B
	mso-style-noshow:yes=3B
	mso-style-unhide:no=3B
	mso-ansi-font-size:11.0pt=3B
	mso-bidi-font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:windowtext=3B}
.MsoChpDefault
	{mso-style-type:export-only=3B
	mso-default-props:yes=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:Calibri=3B}
.MsoPapDefault
	{mso-style-type:export-only=3B}
@page WordSection1
	{size:8.5in 11.0in=3B
	margin:1.0in 1.0in 1.0in 1.0in=3B
	mso-header-margin:.5in=3B
	mso-footer-margin:.5in=3B
	mso-paper-source:0=3B}
div.WordSection1
	{page:WordSection1=3B}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal"=3B
	mso-tstyle-rowband-size:0=3B
	mso-tstyle-colband-size:0=3B
	mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	mso-style-parent:""=3B
	mso-padding-alt:0in 5.4pt 0in 5.4pt=3B
	mso-para-margin:0in=3B
	mso-para-margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B}
</style>
<![endif]-->

<p class=3D"MsoNormal">RADEXT WG Virtual Interim Agenda<o:p></o:p></p>

<p class=3D"MsoNormal">Monday=2C July 12=2C 2010<o:p></o:p></p>

<p class=3D"MsoNormal">11 AM - 1:30 PM Pacific Time<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">Presentations:<span style=3D"">&nbsp=3B </span><a hr=
ef=3D"http://www.drizzle.com/%7Eaboba/RADEXT/July-Interim/">http://www.driz=
zle.com/~aboba/RADEXT/July-Interim/</a><o:p></o:p></p>

<p class=3D"MsoNormal">Jabber room:<span style=3D"">&nbsp=3B </span>radext
at jabber.ietf.org<o:p></o:p></p>

<p class=3D"MsoNormal">Conference parameters:<span style=3D"">&nbsp=3B
</span>TBD<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>



<p class=3D"MsoNormal">Chairs<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Bernard Aboba
&lt=3Bbernard_aboba at hotmail.com&gt=3B <o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Mauricio
Sanchez &lt=3Bmauricio.sanchez at hp.com&gt=3B<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Agenda<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:00 AM =96 11:10 AM PT Preliminaries (10 minutes)<=
o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Attendance<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Note takers<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Agenda bash<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Document Status<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Documents Completing IETF Last Call (40 minutes)<o:p=
></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:20 AM =96 11:30 AM PT RADIUS over TCP=2C Alan DeK=
ok (10
minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-tcp">http://tools.ietf.org/html/draft-ietf-radext-tcp</a><o:p></o:p></p=
>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:30 =96 12:00 PM PT Design Guidelines=2C Alan DeKo=
k (30
minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-design-guidelines">http://tools.ietf.org/html/draft-ietf-radext-design-=
guidelines</a><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Documents Completing RADEXT WG Last Call<o:p></o:p><=
/p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">12:00 PM =96 12:15 PM PT IPv6 Access=2C W. Dec (15 m=
inutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-ipv6-access">http://tools.ietf.org/html/draft-ietf-radext-ipv6-access</=
a><o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">RADEXT WG Work Items (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">12:15 PM PT =96 12:45 PM PT Extended RADIUS Attribut=
es=2C Alan
DeKok (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-extended-attributes">http://tools.ietf.org/html/draft-ietf-radext-exten=
ded-attributes</a><o:p></o:p></p>

 		 	   		  </body>
</html>=

--_1a4ef98c-2c98-4fa1-82c4-d54a03144040_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 29 Jun 2010 10:38:57 +0000
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Tue, 29 Jun 2010 12:38:02 +0200
Subject: Re: RADEXT Virtual Interim Meeting
From: Wojciech Dec <wdec@cisco.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: <radiusext@ops.ietf.org>
Message-ID: <C84F99AA.52E8%wdec@cisco.com>
Thread-Topic: RADEXT Virtual Interim Meeting
Thread-Index: AcsXE8hkC/pKrz4cQcW9WjE4ShNKAgAABcPwABjRsmw=
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit

Hello Bernard,

Could you please also allow 10mins for draft-ietf-radext-ipv6-access?

Also, given the time of the call, would you mind hosting this slot up
towards the beginning?

Thanks,
Woj.



On 29/06/2010 00:47, "Bernard Aboba" <bernard_aboba@hotmail.com> wrote:

> 


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 28 Jun 2010 22:47:48 +0000
Message-ID: <BLU137-DS2E177C3B7D37DDBA627E893CA0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Meeting
Date: Mon, 28 Jun 2010 15:47:23 -0700
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsXE8hkC/pKrz4cQcW9WjE4ShNKAgAABcPw
Content-Language: en-us

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 14.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16011104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN=radiusext@ops.ietf.org;RSVP=TRUE:mailto:radiusext@ops.ietf.org
CLASS:PUBLIC
CREATED:20100628T224723Z
DESCRIPTION:RADEXT WG Virtual Interim Agenda\nMonday\, July 12\, 2010\n11 A
	M - 1:30 PM Pacific Time\n\nPresentations:  http://www.drizzle.com/~aboba/
	RADEXT/July-Interim/\nJabber room:  radext at jabber.ietf.org\nConference 
	parameters:  TBD\n\n \nChairs\n        Bernard Aboba <bernard_aboba at hot
	mail.com> \n        Mauricio Sanchez <mauricio.sanchez at hp.com>\n \nAgen
	da\n \nPreliminaries (10 minutes)\n \n     Attendance\n     Note takers\n 
	    Agenda bash\n     Document Status\n \nDocuments Completing IETF Last C
	all (40 minutes)\n \nRADIUS over TCP\, Alan DeKok (10 minutes)\nhttp://too
	ls.ietf.org/html/draft-ietf-radext-tcp\n \nDesign Guidelines\, Alan DeKok 
	(30 minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-design-guidelin
	es\n \nRADEXT WG Work Items (30 minutes)\n \nExtended RADIUS Attributes\, 
	Alan DeKok (30 minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-exte
	nded-attributes\n\n\n\n\n
DTEND;TZID="Pacific Standard Time":20100712T133000
DTSTAMP:20100628T224723Z
DTSTART;TZID="Pacific Standard Time":20100712T110000
LAST-MODIFIED:20100628T224723Z
LOCATION:Teleconference
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim Meeting
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E00800000000804B061CD916CB01000000000000000
	010000000183AD543CB686B41B739B4F5CD5A595D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.01.0240.003">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">RADEXT WG Virtual Interim Agenda</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN
	 LANG="en-us"><FONT FACE="Calibri">Monday\, July 12\, 2010</FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">11 AM - 1:30 PM P
	acific Time</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE=
	"Calibri">Presentations:&nbsp\;</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A
	 HREF="http://www.drizzle.com/~aboba/RADEXT/July-Interim/"><SPAN LANG="en-
	us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://www.drizzle.com/~aboba/
	RADEXT/July-Interim/</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN 
	LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Cali
	bri">Jabber room:&nbsp\; radext at jabber.ietf.org</FONT></SPAN></P>\n\n<P
	 DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Conference parameters:&nb
	sp\; TBD</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Ca
	libri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FA
	CE="Calibri">Chairs</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FO
	NT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\;&nbsp\;&nbsp\;&nbsp\; Bernar
	d Aboba &lt\;bernard_aboba at hotmail.com&gt\; </FONT></SPAN></P>\n\n<P DI
	R=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\;
	&nbsp\;&nbsp\;&nbsp\; Mauricio Sanchez &lt\;mauricio.sanchez at hp.com&gt\
	;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">
	&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Cal
	ibri">Agenda</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE
	="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FON
	T FACE="Calibri">Preliminaries (10 minutes)</FONT></SPAN></P>\n\n<P DIR=LT
	R><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P 
	DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp
	\; Attendance</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FAC
	E="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\; Note takers</FONT></SPAN></P>\n\n
	<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&n
	bsp\; Agenda bash</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT
	 FACE="Calibri">&nbsp\;&nbsp\;&nbsp\;&nbsp\; Document Status</FONT></SPAN>
	</P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</FONT><
	/SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Documents
	 Completing IETF Last Call (40 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><S
	PAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=
	LTR><SPAN LANG="en-us"><FONT FACE="Calibri">RADIUS over TCP\, Alan DeKok (
	10 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><A H
	REF="http://tools.ietf.org/html/draft-ietf-radext-tcp"><SPAN LANG="en-us">
	<U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf.org/html/draft-i
	etf-radext-tcp</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="
	en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&
	nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Cali
	bri">Design Guidelines\, Alan DeKok (30 minutes)</FONT></SPAN></P>\n\n<P D
	IR=LTR><SPAN LANG="en-us"></SPAN><A HREF="http://tools.ietf.org/html/draft
	-ietf-radext-design-guidelines"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF
	" FACE="Calibri">http://tools.ietf.org/html/draft-ietf-radext-design-guide
	lines</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></
	SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;</F
	ONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">RADE
	XT WG Work Items (30 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="
	en-us"><FONT FACE="Calibri">&nbsp\;</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN 
	LANG="en-us"><FONT FACE="Calibri">Extended RADIUS Attributes\, Alan DeKok 
	(30 minutes)</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><A 
	HREF="http://tools.ietf.org/html/draft-ietf-radext-extended-attributes"><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf
	.org/html/draft-ietf-radext-extended-attributes</FONT></U></SPAN><SPAN LAN
	G="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN></P>\n<BR>\n<BR>\n<BR>\n\n<
	/BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 28 Jun 2010 22:31:07 +0000
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: RADEXT WG Virtual Interim Meeting, July 12, 2010 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100628223013.6814C3A6A09@core3.amsl.com>
Date: Mon, 28 Jun 2010 15:30:02 -0700 (PDT)

The RADEXT WG will be holding a virtual interim meeting on Monday, July 
12, 2010, from 11 AM - 1:30 PM Pacific Time.

A strawman agenda has been posted to the list:
http://ops.ietf.org/lists/radiusext/2010/msg00483.html

Conference call parameters will be posted to the mailing list once they 
are available:
http://ops.ietf.org/lists/radiusext/2010/threads.html

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 28 Jun 2010 19:29:38 +0000
Message-ID: <BLU137-W14F678A9C2C685D698CEA393CA0@phx.gbl>
Content-Type: multipart/alternative; boundary="_9de5580f-3329-4b98-bc38-0b41ce11d790_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim:  July 12, 2010
Date: Mon, 28 Jun 2010 12:27:34 -0700
MIME-Version: 1.0

--_9de5580f-3329-4b98-bc38-0b41ce11d790_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The RADEXT WG will be holding a Virtual Interm Meeting on Monday=2C July 12=
=2C 2010 from 11 AM - 1:30 PM Pacific Time.   A strawman agenda is enclosed=
 below=3B details of the conference call parameters will be posted to the l=
ist.  If you have additional agenda items=2C please send them to Mauricio o=
r myself.=20



RADEXT WG Virtual Interim Agenda

Monday=2C July 12=2C 2010

11 AM - 1:30 PM Pacific Time

=20

Presentations:  http://www.drizzle.com/~aboba/RADEXT/July-Interim/

Jabber room:  radext
at jabber.ietf.org

Conference parameters:=20
TBD

=20

=20

Chairs

        Bernard Aboba
<bernard_aboba at hotmail.com>=20

        Mauricio
Sanchez <mauricio.sanchez at hp.com>

=20

Agenda

=20

11:00- 11:10 AM PT  Preliminaries (10 minutes)

=20

     Attendance

     Note takers

     Agenda bash

     Document Status

=20

Documents Completing IETF Last Call (40 minutes)

=20

11:10 AM - 11:20 AM PT  RADIUS over TCP=2C Alan DeKok (10 minutes)

http://tools.ietf.org/html/draft-ietf-radext-tcp

=20

11:20 AM- 11:50 AM PT  Design Guidelines=2C Alan DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

=20

RADEXT WG Work Items (30 minutes)

=20

11:50 AM - 12:20 PM PT  Extended RADIUS Attributes=2C Alan DeKok (30 minute=
s)

http://tools.ietf.org/html/draft-ietf-radext-extended-attributes

=20

=20

=20


 		 	   		  =

--_9de5580f-3329-4b98-bc38-0b41ce11d790_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The RADEXT WG will be holding a Virtual Interm Meeting on Monday=2C July 12=
=2C 2010 from 11 AM - 1:30 PM Pacific Time.&nbsp=3B&nbsp=3B A strawman agen=
da is enclosed below=3B details of the conference call parameters will be p=
osted to the list.&nbsp=3B If you have additional agenda items=2C please se=
nd them to Mauricio or myself. <br><br><meta http-equiv=3D"Content-Type" co=
ntent=3D"text/html=3B charset=3Dutf-8"><meta name=3D"ProgId" content=3D"Wor=
d.Document"><meta name=3D"Generator" content=3D"Microsoft Word 14"><meta na=
me=3D"Originator" content=3D"Microsoft Word 14"><link rel=3D"File-List" hre=
f=3D"file:///C:%5CUsers%5Cbernarda%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%=
5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file:///C:%5CUsers%5Cbern=
arda%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><l=
ink rel=3D"colorSchemeMapping" href=3D"file:///C:%5CUsers%5Cbernarda%5CAppD=
ata%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[=
if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45=3B-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"267">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri=3B
	panose-1:2 15 5 2 2 2 4 3 2 4=3B
	mso-font-alt:"Electra LH Regular"=3B
	mso-font-charset:0=3B
	mso-generic-font-family:swiss=3B
	mso-font-pitch:variable=3B
	mso-font-signature:-520092929 1073786111 9 0 415 0=3B}
 /* Style Definitions */
 p.MsoNormal=2C li.MsoNormal=2C div.MsoNormal
	{mso-style-unhide:no=3B
	mso-style-qformat:yes=3B
	mso-style-parent:""=3B
	margin:0in=3B
	margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-fareast-font-family:"Times New Roman"=3B
	mso-bidi-font-family:"Times New Roman"=3B}
a:link=2C span.MsoHyperlink
	{mso-style-priority:99=3B
	font-family:"Times New Roman"=2C"serif"=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:blue=3B
	text-decoration:underline=3B
	text-underline:single=3B}
a:visited=2C span.MsoHyperlinkFollowed
	{mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	color:purple=3B
	mso-themecolor:followedhyperlink=3B
	text-decoration:underline=3B
	text-underline:single=3B}
span.EmailStyle16
	{mso-style-type:personal=3B
	mso-style-noshow:yes=3B
	mso-style-unhide:no=3B
	mso-ansi-font-size:11.0pt=3B
	mso-bidi-font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:"Times New Roman"=3B
	color:windowtext=3B}
.MsoChpDefault
	{mso-style-type:export-only=3B
	mso-default-props:yes=3B
	font-family:"Calibri"=2C"sans-serif"=3B
	mso-ascii-font-family:Calibri=3B
	mso-hansi-font-family:Calibri=3B
	mso-bidi-font-family:Calibri=3B}
.MsoPapDefault
	{mso-style-type:export-only=3B}
@page WordSection1
	{size:8.5in 11.0in=3B
	margin:1.0in 1.0in 1.0in 1.0in=3B
	mso-header-margin:.5in=3B
	mso-footer-margin:.5in=3B
	mso-paper-source:0=3B}
div.WordSection1
	{page:WordSection1=3B}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal"=3B
	mso-tstyle-rowband-size:0=3B
	mso-tstyle-colband-size:0=3B
	mso-style-noshow:yes=3B
	mso-style-priority:99=3B
	mso-style-parent:""=3B
	mso-padding-alt:0in 5.4pt 0in 5.4pt=3B
	mso-para-margin:0in=3B
	mso-para-margin-bottom:.0001pt=3B
	mso-pagination:widow-orphan=3B
	font-size:11.0pt=3B
	font-family:"Calibri"=2C"sans-serif"=3B}
</style>
<![endif]-->

<p class=3D"MsoNormal">RADEXT WG Virtual Interim Agenda<o:p></o:p></p>

<p class=3D"MsoNormal">Monday=2C July 12=2C 2010<o:p></o:p></p>

<p class=3D"MsoNormal">11 AM - 1:30 PM Pacific Time<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal">Presentations:<span style=3D"">&nbsp=3B </span><a hr=
ef=3D"http://www.drizzle.com/%7Eaboba/RADEXT/July-Interim/">http://www.driz=
zle.com/~aboba/RADEXT/July-Interim/</a><o:p></o:p></p>

<p class=3D"MsoNormal">Jabber room:<span style=3D"">&nbsp=3B </span>radext
at jabber.ietf.org<o:p></o:p></p>

<p class=3D"MsoNormal">Conference parameters:<span style=3D"">&nbsp=3B
</span>TBD<o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Chairs<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Bernard Aboba
&lt=3Bbernard_aboba at hotmail.com&gt=3B <o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B </span>Mauricio
Sanchez &lt=3Bmauricio.sanchez at hp.com&gt=3B<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Agenda<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:00- 11:10 AM PT&nbsp=3B Preliminaries (10 minutes=
)<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Attendance<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Note takers<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Agenda bash<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B </=
span>Document Status<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">Documents Completing IETF Last Call (40 minutes)<o:p=
></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:10 AM - 11:20 AM PT&nbsp=3B RADIUS over TCP=2C Al=
an DeKok (10 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-tcp">http://tools.ietf.org/html/draft-ietf-radext-tcp</a><o:p></o:p></p=
>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:20 AM- 11:50 AM PT&nbsp=3B Design Guidelines=2C A=
lan DeKok (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-design-guidelines">http://tools.ietf.org/html/draft-ietf-radext-design-=
guidelines</a><o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">RADEXT WG Work Items (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><span style=3D"">&nbsp=3B</span><o:p></o:p></p>

<p class=3D"MsoNormal">11:50 AM - 12:20 PM PT&nbsp=3B Extended RADIUS Attri=
butes=2C Alan DeKok (30 minutes)<o:p></o:p></p>

<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-ietf-rad=
ext-extended-attributes">http://tools.ietf.org/html/draft-ietf-radext-exten=
ded-attributes</a><o:p></o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<p class=3D"MsoNormal"><o:p>&nbsp=3B</o:p></p>

<br> 		 	   		  </body>
</html>=

--_9de5580f-3329-4b98-bc38-0b41ce11d790_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 27 Jun 2010 01:24:55 +0000
Message-ID: <BLU137-DS17B50567EB4D713B67946F93C90@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: FINAL REMINDER: Last Look at RADIUS Design Guidelines
Date: Sat, 26 Jun 2010 18:21:20 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01CB155C.BE8C2060"
Thread-Index: AcsRdaUIvQgmEsXQT5GVbOyxBHff/AEIUzDg
Content-Language: en-us

------=_NextPart_000_0083_01CB155C.BE8C2060
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a reminder of an ongoing "last look" at the RADIUS Design Guidelines
document, prior to its approval by the IETF for publication as a Best
Current Practice (BCP). 

The document is available for inspection here:
http://tools.ietf.org/id/draft-ietf-radext-design

The "last look" will last until Monday, June 28, 2010.  Comments may be
submitted in any of the following ways:

a. Submission via the RADEXT TRAC system:
http://trac.tools.ietf.org/wg/radext/trac/newticket

b. Comments sent to the RADEXT WG mailing list (radiusext@ops.ietf.org).


------=_NextPart_000_0083_01CB155C.BE8C2060
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal>This is a reminder of an ongoing &quot;last =
look&quot; at
the RADIUS Design Guidelines document, prior to its approval by the IETF =
for
publication as a Best Current Practice (BCP). <br>
<br>
The document is available for inspection here:<br>
http://tools.ietf.org/id/draft-ietf-radext-design<br>
<br>
The &quot;last look&quot; will last until <span =
style=3D'color:#1F497D'>Monday, </span>June
28, 2010.&nbsp; Comments may be submitted in any of the following =
ways:<br>
<br>
a. Submission via the RADEXT TRAC system:
http://trac.tools.ietf.org/wg/radext/trac/newticket<br>
<br>
b. Comments sent to the RADEXT WG mailing list =
(radiusext@ops.ietf.org).<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0083_01CB155C.BE8C2060--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 27 Jun 2010 01:24:47 +0000
Message-ID: <BLU137-DS17BD61277AE413BBA78D4193C90@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Doodle Poll for RADEXT Virtual Interim
Date: Sat, 26 Jun 2010 18:24:31 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01CB155C.D27D4270"
Thread-Index: AcsQrXpzOc8l2GT/T8udWzYyz3YypgE6a9BQ
Content-Language: en-us

------=_NextPart_000_0088_01CB155C.D27D4270
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The RADEXT WG is considering scheduling a Virtual Interim meeting during the
week of July 12, 2010. 

Please fill out a Doodle Poll indicating your availability:
http://www.doodle.com/362t54udqbbkupdp

 

 


------=_NextPart_000_0088_01CB155C.D27D4270
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>The RADEXT WG is considering </span><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>scheduling a Virtual =
Interim
meeting </span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>during </span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>the week of July 12, 2010. <br>
<br>
Please fill out a Doodle Poll indicating your availability:<br>
http://www.doodle.com/362t54udqbbkupdp</span><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_0088_01CB155C.D27D4270--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 23 Jun 2010 08:15:28 +0000
Message-ID: <4C21C263.6060001@deployingradius.com>
Date: Wed, 23 Jun 2010 10:14:27 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Agenda for Virtual Interim Meeting - Take One
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Here is a first stab at an agenda for the RADEXT Virtual Interim
..
> RADIUS over TCP, Alan DeKok (10 minutes)

  Goal: WG consensus && document finalization.

> Design Guidelines, Alan DeKok (30 minutes)

  Goal: WG consensus && publication.

> Extended RADIUS Attributes, Alan DeKok (30 minutes)

  Goal: what next?

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 22 Jun 2010 20:54:17 +0000
Message-ID: <BLU137-DS14C8498664F74977DE667493C40@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Agenda for Virtual Interim Meeting - Take One
Date: Tue, 22 Jun 2010 13:53:16 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D1_01CB1212.44478440"
Thread-Index: AcsSScG0jYMs0oAmTIGttiITiTawswAAyTpw
Content-Language: en-us

------=_NextPart_000_00D1_01CB1212.44478440
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Here is a first stab at an agenda for the RADEXT Virtual Interim meeting.
The overall goal is to focus on re-invigorating long-stuck work items.  If
you have additional agenda items, please send them to Mauricio or myself. 

 

RADEXT WG Virtual Interim Agenda

 

Presentations:  TBD

Jabber room:  radext at jabber.ietf.org

WebEx:  TBD

 

Chairs

        Bernard Aboba <bernard_aboba at hotmail.com> 

        Mauricio Sanchez <mauricio.sanchez at hp.com>

 

Agenda

 

Preliminaries (10 minutes)

 

     Attendance

     Note takers

     Agenda bash

     Document Status

 

Documents Completing IETF Last Call (40 minutes)

 

RADIUS over TCP, Alan DeKok (10 minutes)

http://tools.ietf.org/html/draft-ietf-radext-tcp

 

Design Guidelines, Alan DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

 

RADEXT WG Work Items (30 minutes)

 

Extended RADIUS Attributes, Alan DeKok (30 minutes)

http://tools.ietf.org/html/draft-ietf-radext-extended-attributes


------=_NextPart_000_00D1_01CB1212.44478440
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal>Here is a first stab at an agenda for the RADEXT =
Virtual
Interim meeting.&nbsp; The overall goal is to focus on re-invigorating
long-stuck work items.&nbsp; If you have additional agenda items, please =
send
them to Mauricio or myself. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>RADEXT WG Virtual Interim Agenda<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Presentations:&nbsp; TBD<o:p></o:p></p>

<p class=3DMsoNormal>Jabber room:&nbsp; radext at =
jabber.ietf.org<o:p></o:p></p>

<p class=3DMsoNormal>WebEx:&nbsp; TBD<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Chairs<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bernard =
Aboba
&lt;bernard_aboba at hotmail.com&gt; <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mauricio =
Sanchez
&lt;mauricio.sanchez at hp.com&gt;<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Agenda<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>Preliminaries (10 minutes)<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Attendance<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Note takers<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Document =
Status<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Documents Completing IETF Last Call (40 =
minutes)<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>RADIUS over TCP, Alan DeKok (10 =
minutes)<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-tcp<o:p></=
o:p></p>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>Design Guidelines, Alan DeKok (30 =
minutes)<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-design-gui=
delines<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>RADEXT WG Work Items (30 minutes)<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Extended RADIUS Attributes, Alan DeKok (30 =
minutes)<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-extended-a=
ttributes<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_00D1_01CB1212.44478440--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 21:07:10 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 21:06:59 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #48: B.6
Message-ID: <075.115578fef3e62c7f031eb07091287d8c@tools.ietf.org>

#48: B.6
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  major                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/48#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 21:06:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 21:06:14 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #49: B.10
Message-ID: <075.2d70bde77f962ddbfb6ead707fff5e00@tools.ietf.org>

#49: B.10
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  critical                   |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…
  * severity:  Waiting for Shepherd Writeup => Submitted WG Document


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/49#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 21:05:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 21:05:22 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #31: Section 2.1
Message-ID: <075.86960762b07cfa7ae68eb1b594565c74@tools.ietf.org>

#31: Section 2.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  minor                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/31#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 20:12:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 20:12:04 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #50: Section 2
Message-ID: <066.141c2ea2d0d450221123bf29bcda84f2@tools.ietf.org>

#50: Section 2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  minor                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
 Basic data types use one of the existing RADIUS data types as defined
    below, encapsulated in a [RFC2865] RADIUS attribute, or in a
    [RFC2865] RADIUS VSA.

 [BA] The basic types are defined in Section 2.1. Recommended change:

    Basic data types use one of the existing RADIUS data types defined in
 Section 2.1, encapsulated in a [RFC2865] RADIUS attribute, or in a
    [RFC2865] RADIUS VSA.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/50>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 19:13:02 +0000
Message-ID: <BLU137-DS3D3993A6B458AD2CF387E93C30@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Reminder: Last Look at RADIUS Design Guidelines
Date: Mon, 21 Jun 2010 12:12:11 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01CB113A.FA9F4B70"
Thread-index: AcsRdaUIvQgmEsXQT5GVbOyxBHff/A==
Content-Language: en-us

------=_NextPart_000_0005_01CB113A.FA9F4B70
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a reminder of an ongoing "last look" at the RADIUS Design Guidelines
document, prior to its being approval by the IETF for publication as a Best
Current Practice (BCP). 

The document is available for inspection here:
http://tools.ietf.org/id/draft-ietf-radext-design

The "last look" will last until June 28, 2010.  Comments may be submitted in
any of the following ways:

a. Submission via the RADEXT TRAC system:
http://trac.tools.ietf.org/wg/radext/trac/newticket

b. Comments sent to the RADEXT WG mailing list (radiusext@ops.ietf.org).


------=_NextPart_000_0005_01CB113A.FA9F4B70
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>This is a =
reminder of an ongoing &quot;last look&quot; at the RADIUS Design =
Guidelines document, prior to its being approval by the IETF for =
publication as a Best Current Practice (BCP). <br><br>The document is =
available for inspection =
here:<br>http://tools.ietf.org/id/draft-ietf-radext-design<br><br>The =
&quot;last look&quot; will last until June 28, 2010.&nbsp; Comments may =
be submitted in any of the following ways:<br><br>a. Submission via the =
RADEXT TRAC system: =
http://trac.tools.ietf.org/wg/radext/trac/newticket<br><br>b. Comments =
sent to the RADEXT WG mailing list =
(radiusext@ops.ietf.org).<o:p></o:p></p></div></body></html>
------=_NextPart_000_0005_01CB113A.FA9F4B70--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:56:46 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:56:25 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #49: B.10
Message-ID: <066.86883efddb9747b3070442cd0525945d@tools.ietf.org>

#49: B.10
------------------------------------------+---------------------------------
 Reporter:  bernard_aboba@…               |       Owner:            
     Type:  defect                        |      Status:  new       
 Priority:  critical                      |   Milestone:  milestone1
Component:  design                        |     Version:  1.0       
 Severity:  Waiting for Shepherd Writeup  |    Keywords:            
------------------------------------------+---------------------------------
 B.9. Digest-*

    [RFC5090] attempts to standardize the functionality provided by an
    expired internet-draft [AAA-SIP] which improperly used two attributes
    from the standard space without being assigned them by IANA.  This
    self-allocation is forbidden, as described above in Section 1.3 and
    in Section 2.  In addition, the draft uses nested attributes, which
    are discouraged in Section 2.1.  The updated document uses basic data
    types, and allocates nearly 20 attributes in the process.

    However, the draft has seen wide-spread implementation, where
    [RFC5090] has not.  While there are a number of factors involved, one
    factor may be that implementors disagreed with the trade-offs made in
    the updated specification.  It may have been better to simply
    document the existing format, and request IANA allocation of two
    attributes.  The resulting design would have used nested attributes,
    but may have gained more wide-spread implementation.

    It is difficult to know which choice is optimal.  Given the
    complexity of the protocols and implementations, it is impossible to
    define "hard and fast" rules for RADIUS design guidelines.

 [BA] There is already a section B.9.  This section should therefore be
 renumbered as "B.10".  The recommended text is as follows:

 B.10. Digest-*

    [RFC5090] attempts to standardize the functionality provided by an
    expired internet-draft [AAA-SIP] which improperly used two attributes
    from the standard space without being assigned them by IANA.  This
    self-allocation is forbidden, as described above in Section 2.
    In addition, the draft uses nested attributes, which
    are discouraged in Section 2.1.  The updated document uses basic data
    types, and allocates nearly 20 attributes in the process.

    However, the draft has seen wide-spread implementation, where
    [RFC5090] has not.  One explanation may be that implementors
    disagreed with the trade-offs made in the updated specification.
    It may have been better to simply document the existing format, and
    request IANA allocation of two attributes.  The resulting design
    would have used nested attributes, but may have gained more
    wide-spread implementation.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/49>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:48:49 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:48:35 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #48: B.6
Message-ID: <066.d6ad801904e0d402bede96ab040ae3fd@tools.ietf.org>

#48: B.6
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 This attribute contains no encrypted component, and is it not
    directly involved in authentication.  The individual sub-fields could
    therefore have been encapsulated in separate attributes.

    Since the form of the text string is well defined, there is no
    benefit in using a text string.  Instead, an integer attribute should
    have been assigned for each of the transmit speed and the receive
    speed.  A separate enumerated integer should have been assigned for
    the additional information, as was done with the NAS-Port-Type
    attribute.

 [BA] The text in RFC 2869 Section 5.11 refers to ITU-T efforts relating to
 connect strings.  This indicates that the authors thought of the Connect-
 Info attribute as an "opaque data" defined by ITU-T.  Given this, the
 attribute could qualify for an exception.  Recommended change:

    This attribute contains no encrypted component, and is it not
    directly involved in authentication.  The individual sub-fields could
    therefore have been encapsulated in separate attributes.

    However, since the definition refers to potential standardization
 activity within ITU, the Connect-Info attribute can also be thought of
 opaque data whose definition is provided elsewhere.  The Connect-Info
 attribute could therefore qualify for an exception as described in Section
 3.2.3.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/48>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:40:51 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: [radext] #32: Section 2.2
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Mon, 21 Jun 2010 11:40:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEDC7BF5-FBD3-41FE-869C-781CD4BD605B@elbrysnetworks.com>
To: radext mailing list <radiusext@ops.ietf.org>

On Jun 21, 2010, at 8:30 AM, Alan DeKok wrote:

>  A single vendor still expects their equipment to be used in a wide
> variety of circumstances.  Experience shows that vendors who have
> significant sales can have their non-standard formats adopted by all
> major RADIUS servers.

Yes, but isn't that rather a corner case, in terms of the way the =
process is supposed to work?  I was addressing baseline expectations.

>  I think that the discussion about "not suitable for general use" is
> really "not suitable for standardization through the IETF".  As such,
> vendors and SDOs fall into the same non-IETF category.

If you were to change the text to say that, I'd agree.  But that's not =
what it says, and the definition of VSA in RFC 2865 is couched in terms =
of "not suitable for general use".

If what we want to say is that these guidelines really only apply for =
work done in the IETF, I think the document does convey that message.  =
My questions is whether that's really the message we want to convey.







--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:35:36 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:35:08 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #47: A.4 Reference
Message-ID: <066.b9144fa71986f1480fec361be35d5a4d@tools.ietf.org>

#47: A.4 Reference
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  minor                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
 For further details, see Section 3.3.

 [BA] Section 3.3 is about the Vendor Space, and doesn't appear to relate
 to the recommendations in A.4.  Is this the right reference or perhaps
 Section 3.1 was intended instead?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/47>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:29:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:29:14 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #46: B.3
Message-ID: <075.1ca9058c5dbb95d8f8a06bca69ef428c@tools.ietf.org>

#46: B.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/46#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:28:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:28:20 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #45: A.4
Message-ID: <075.f5fafff81744b4bfa8de9ea7a466a58d@tools.ietf.org>

#45: A.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/45#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:26:33 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:26:22 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #43: A.2
Message-ID: <075.5198e38ba5dbc4251195dc42e61045ae@tools.ietf.org>

#43: A.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  blocker                    |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/43#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:24:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:24:47 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #44: A2.2
Message-ID: <075.02e8c63961e16c3aeb372a305828477c@tools.ietf.org>

#44: A2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/44#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:24:16 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:24:04 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #42: A1.4
Message-ID: <075.572ac7eec58bafa24d7a10e68b0d9e05@tools.ietf.org>

#42: A1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  blocker                    |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/42#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:23:05 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:22:55 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #26: Terminology (Section 1.1)
Message-ID: <075.00f3b0fc9972e6f3478c2dce4b95904b@tools.ietf.org>

#26: Terminology (Section 1.1)
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/26#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:22:18 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:22:03 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #41: A1.2
Message-ID: <075.8d70c9086b439cb01aa300e33c9daaa3@tools.ietf.org>

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/41#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:18:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:18:35 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #40: A.1.1
Message-ID: <075.bb774ac9f448ef654bd73cb845f98ef8@tools.ietf.org>

#40: A.1.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/40#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:17:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:16:51 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #39: Section 4
Message-ID: <075.c15054fb388bf576551c6eaf4b8c5bdd@tools.ietf.org>

#39: Section 4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/39#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:16:10 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:15:53 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #38: Section 3.3.2
Message-ID: <075.bc9222bd2adde92d1ddf77b33c66a25a@tools.ietf.org>

#38: Section 3.3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/38#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:14:34 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:14:17 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #36: Section 3.2.3
Message-ID: <075.6b41c9701e7d1a525ab82d139c4e6419@tools.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:3>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:13:10 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:12:57 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #37: Section 3.3
Message-ID: <075.c9b4373a18876b084eba473753c43606@tools.ietf.org>

#37: Section 3.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/37#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:11:08 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:10:42 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #35: Section 3.2
Message-ID: <075.1743acd45506ad6c2df2af443f964b26@tools.ietf.org>

#35: Section 3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:            
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/35#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:09:38 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:09:29 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #34: Section 2.4
Message-ID: <075.ea2bb663d18199e7a8c9ad663dbbe275@tools.ietf.org>

#34: Section 2.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  major                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/34#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:08:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:08:17 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #33: Section 2.3
Message-ID: <075.b077939161ff91c48d353777a96e3df7@tools.ietf.org>

#33: Section 2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  blocker                    |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/33#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:07:52 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:07:39 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #32: Section 2.2
Message-ID: <075.26ea701164777c295892f3e67ca82ca0@tools.ietf.org>

#32: Section 2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/32#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:05:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:05:47 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #31: Section 2.1
Message-ID: <075.2dba1fddd9d3ade885fed6fbc3651c04@tools.ietf.org>

#31: Section 2.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Sorry for the inexact editing instructions.  Once the first paragraph is
 replaced, the second paragraph is unnecessary.  Please delete the
 following:

 There may be situations where complex attributes are acceptable
 because they reduce complexity in non-RADIUS systems, or because
 leveraging the basic data types would be awkward. Unfortunately,
 there are no "hard and fast" rules for where the complexity would
 best be located. Each situation has to be decided on a case-by-case
 basis. The cost-benefit trade-off may result in a "complex data
 type" being defined in RADIUS, as discussed in Appendix B. When this
 is done, an explanation SHOULD be offered as to why the complex data
 type was used.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/31#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:03:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:02:49 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #30: Section 1.4
Message-ID: <075.0782462d55f1c0ef28f4e9f96d6de584@tools.ietf.org>

#30: Section 1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  minor                      |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/30#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:01:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:01:45 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #29: Section 2
Message-ID: <075.61c6858b00c5e7090b1298b27e9a0590@tools.ietf.org>

#29: Section 2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  critical                   |    Milestone:  milestone1
Component:  design                     |      Version:            
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/29#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:00:35 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 15:00:27 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #28: Section 1.2
Message-ID: <075.a7b0590f41de4a67dbd05293aff83f7a@tools.ietf.org>

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:            
     Type:  defect                     |       Status:  closed    
 Priority:  critical                   |    Milestone:  milestone1
Component:  design                     |      Version:  1.0       
 Severity:  Submitted WG Document      |   Resolution:  fixed     
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/28#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 15:00:22 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 14:59:40 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #27: Section 1.3
Message-ID: <075.ef2fe80b78fff208b04d3aefd55afbc4@tools.ietf.org>

#27: Section 1.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |        Owner:  aland@…                  
     Type:  defect                     |       Status:  closed                   
 Priority:  critical                   |    Milestone:  milestone1               
Component:  design                     |      Version:  1.0                      
 Severity:  Submitted WG Document      |   Resolution:  fixed                    
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/27#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 13:31:03 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-design-15.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100621133016.01BB83A69CD@core3.amsl.com>
Date: Mon, 21 Jun 2010 06:30:03 -0700 (PDT)

--NextPart

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 Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-15.txt
	Pages           : 39
	Date            : 2010-06-21

This document provides guidelines for the design of attributes used
by the Remote Authentication Dial In User Service (RADIUS) protocol.
It is expected that these guidelines will prove useful to authors and
reviewers of future RADIUS attribute specifications, both within the
IETF as well as other Standards Development Organizations (SDOs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-15.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-radext-design-15.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2010-06-21061612.I-D@ietf.org>

--NextPart--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 13:17:04 +0000
Message-ID: <4C1F662E.8060009@deployingradius.com>
Date: Mon, 21 Jun 2010 15:16:30 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Recent Issues
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

  I've updated the document to address recent issues as raised on the
tracker.

  Some minor word-smithing was done, but nothing more.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 12:30:12 +0000
Message-ID: <4C1F5B4A.9010203@deployingradius.com>
Date: Mon, 21 Jun 2010 14:30:02 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Dave Nelson <d.b.nelson@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: [radext] #32: Section 2.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dave Nelson wrote:
> Once again, I don't support the conflation of vendors and SDOs.  We do want
> non-IETF SDOs to use the VSA mechanism, primarily to conserve the scarce
> pool of IANA-assigned code points.  However, I'm convinced that sending the
> message that what another standards organization does is of no more
> importance or consequence than the activity of a single vendor is a mistake.

  A single vendor still expects their equipment to be used in a wide
variety of circumstances.  Experience shows that vendors who have
significant sales can have their non-standard formats adopted by all
major RADIUS servers.

  The same applies to SDOs.

  I think that the discussion about "not suitable for general use" is
really "not suitable for standardization through the IETF".  As such,
vendors and SDOs fall into the same non-IETF category.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 12:26:56 +0000
Message-ID: <4C1F5A74.1010807@deployingradius.com>
Date: Mon, 21 Jun 2010 14:26:28 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Dave Nelson <d.b.nelson@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: [radext] #36: Section 3.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dave Nelson wrote:
> This is a single sentence out of context, so my concern may be addressed
> elsewhere, but I've always felt that one important test of "opaqueness" is
> whether or not the payload of the attribute is laid out in details in the
> RADIUS document, in the traditional fashion of other RADIUS attributes.  If
> it's truly opaque, then the format MUST be defined in some other, non-RADIUS
> document.

  Yes.  See Section 2.1, which says this explicitly.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 12:14:34 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: [radext] #42: A1.4
Date: Mon, 21 Jun 2010 08:14:21 -0400
Message-ID: <BE301B02D1BD42B192CD1C44C276CE4A@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsREpZdBmOj9ct5RDWUj4+cPPtFRwAKGEgg

>  [BA] Mailing list discussion indicates that there is not consensus to
>  deprecate existing RADIUS types.  Suggested change:
> 
>     There is a trade-off in design between re-using existing formats for
>     historical compatibility, or choosing new formats for a "better"
>     design.  This trade-off does not always require the "better" design
>     to be used.  As a result. pre-existing complex data types described
>     in Appendix B MAY be used.

As much as it disappoints me personally, I don't dispute the fact.  We did
not obtain consensus.  



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 12:06:41 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: [radext] #36: Section 3.2.3
Date: Mon, 21 Jun 2010 08:06:11 -0400
Message-ID: <F83DFFBAACC848C9B691EF49A098B0E2@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsRDkEfwo2X0rjkRRSz/sP6Yn7CmgAKud3g

>  Recommended change:
> 
>  Another exception to the recommendation against complex types is for
>  types that can be treated as opaque data by the RADIUS server.

This is a single sentence out of context, so my concern may be addressed
elsewhere, but I've always felt that one important test of "opaqueness" is
whether or not the payload of the attribute is laid out in details in the
RADIUS document, in the traditional fashion of other RADIUS attributes.  If
it's truly opaque, then the format MUST be defined in some other, non-RADIUS
document.  Otherwise, this opens up the possibility of defining new services
in the context of a RADIUS document.  In other words, an attribute can't at
the same time be "opaque" to the RADIUS server but spelled out in detail to
the RADIUS developer in the RADIUS document.  It's either "defined
elsewhere" or it isn't.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 12:06:33 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: [radext] #32: Section 2.2
Date: Mon, 21 Jun 2010 08:06:11 -0400
Message-ID: <F59C310D417C4E1C8E854A435E12BA94@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsRCo8yDQJiDLykTEK0eb6SSAZLAwALa2uA

>  Recommended change is to replace Section 2.2 with the following:
> 
>   2.2. Vendor-Specific Attribute Space
> 
>     The Vendor-Specific Attribute space is defined to be the contents of
>     the "String" field of the Vendor-Specific Attribute ([RFC2865]
>     Section 5.26).  As discussed there, it is intended for vendors and
>     SDOs to support their own Attributes not suitable for general use.

Once again, I don't support the conflation of vendors and SDOs.  We do want
non-IETF SDOs to use the VSA mechanism, primarily to conserve the scarce
pool of IANA-assigned code points.  However, I'm convinced that sending the
message that what another standards organization does is of no more
importance or consequence than the activity of a single vendor is a mistake.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 11:52:30 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: [radext] #31: Section 2.1
Date: Mon, 21 Jun 2010 07:52:11 -0400
Message-ID: <7B98BEC1F8794DAD9B079F1CE7299D98@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsRCGmkluKuAdSmQL6eeVCTbSxIWAALsjCw

>  Recommended replacement:
> 
>     All other data formats (including nested attributes) are defined
>     to be "complex data types", and are NOT RECOMMENDED for normal
>     use.  Complex data types MAY be used in situations where they
>     reduce complexity in non-RADIUS systems, or where using
>     the basic data types would be awkward (such as where grouping
>     would be required in order to link related attributes).  Since
>     there are no "hard and fast" rules for where complexity is best
>     located, each situation has to be decided on a case-by-case
>     basis.  Examples of this tradeoff are discussed in Appendix B.
>     Where a complex data type is selected, an explanation SHOULD be
>     offered as to why this was necessary.

At this point in time, I would support adding "such as where grouping would
be required in order to link related attributes" as an example of a case
that would justify the use of complex data types.  It is a great
disappointment to me that the WG failed to come to consensus on a more
regularized and formal mechanism to accommodate attribute grouping.  I think
that the ad hoc mechanism of grouping in complex data values is a distant
second best to a more formal and structured grouping mechanism.  However, at
this point, it is what it is.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 11:39:04 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: [radext] #27: Section 1.3
Date: Mon, 21 Jun 2010 07:38:44 -0400
Message-ID: <D4579D30828E41299D053CA90D0A6682@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsQ0akDkKHU/0jYTQ2eSyCeVvgfDAAYpvcg

>     However, there are situations in which vendors or SDOs can choose
>     not to follow these guidelines without major consequences.  As
>     noted in [RFC2865] Section 5.26, Vendor-Specific Attributes (VSAs)
>     are "available to allow vendors to support their own extended 
>     Attributes not suitable for general usage."  Where vendors or 
>     SDOs develop specifications "not suitable for general usage",
>     limited interoperability and inability to use existing 
>     implementations may be acceptable and in these situations, 
>     vendors and SDOs MAY NOT choose to conform to these
>     guidelines.

I have always felt that the notion of placing other SDOs on the same plane
as vendors is a silly one.  I believe I know what motivates this treatment.
It seems to me to be a compromise to assuage those RADIUS practitioners who
are active in other SDOs and who have continually been critical of this WG's
attempts to define a reasonably rigorous set of attribute design criteria.
The point of *any* SDO is to define interoperable standards for multiple
vendors to use, to promote multi-vendor interoperability in implementations
and deployments.  To suggest that SDOs, other than the IETF, do not require
multi-vendor interoperability in their standards seems to devalue their
work.

I think that there should be a three tier scheme for recommended compliance
with these guidelines, not two tier.  I believe that non-IETF SDOs should be
held to a higher level of expectations than single vendors, but lower that
the IETF itself.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 11:23:43 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: [radext] #26: Terminology (Section 1.1)
Date: Mon, 21 Jun 2010 07:22:53 -0400
Message-ID: <E1E3A7F7F01B4CEC96AEF762E89D0FAB@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsQszjm3loAJqFbTe+872jGVmzMtwAf95og

Wow.   Such a long series of emails.  I appreciate having the issues
separated, but dealing with so many suggested changes out of context is
challenging.

>  [BA] Given the extended attribute work, we may not want to 
>  define the standard space a bit more flexibly.

Did you intend the "not" in this sentence?

>  standard space
>       RADIUS attributes which are allocated by IANA and which
>       follow the format defined in RFC 2865 [RFC2865] Section 5.

If the suggestion is to be more flexible in defining "standard space", your
suggested text seems to fall short of the mark, in that it talks about the
"format defined in RFC 2865 [RFC2865] Section 5".  Clearly that excludes the
Extended Attributes, no?



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:42:13 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:41:51 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #46: B.3
Message-ID: <066.83cff34b2792d6b61197dd7e270cc6f9@tools.ietf.org>

#46: B.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Since this is a security attribute and is encrypted, code changes are
    required on the RADIUS client and server to support it, regardless of
    the attribute format.  Therefore, this complex data type is
    acceptable in this situation.

 [BA] The design of the Tunnel-Password attribute goes against the
 recommendations in the Security Considerations section, so suggesting that
 this attribute is acceptable doesn't make sense.

 Recommended change:

    Since this is a security attribute, code changes are
    required on the RADIUS client and server to support it, regardless of
    the attribute format.  However, while use of a complex data type is
    acceptable in this situation, the design of the Tunnel-Password
 attribute is problematic from a security perspective, since it uses MD5 as
 a cipher, and provides a password to a NAS, potentially without proper
 authorization.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/46>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:27:49 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:27:23 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #45: A.4
Message-ID: <066.e8d3570384e5f639d2d58a68cd44d9f3@tools.ietf.org>

#45: A.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Transport of opaque data
         relating to AAA is also permitted, as discussed above in
         Section 2.1.3. However, if the specification does not relate
         to AAA, then RADIUS SHOULD NOT be used.

 [BA] This is discussed in Section 3.2.3, not 2.1.3.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/45>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:24:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:24:39 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #44: A2.2
Message-ID: <066.879cec9bcf87b115799be41de863bd79@tools.ietf.org>

#44: A2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 See also Section 2.1.3 for a
    discussion of why complex types are problematic.

 [BA] This advice is now in Section 2.1.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/44>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:23:26 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:23:12 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #43: A.2
Message-ID: <066.243f80f72f83195911ccef0c7dfaccea@tools.ietf.org>

#43: A.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 A.2. Improper Data Types

    All data types other than the ones described above in Appendix A.1
    and Appendix B SHOULD NOT be used.  This section describes in detail
    a number of data types that are NOT RECOMMENDED in new RADIUS
    specifications.  Where possible, replacement data types are
    suggested.

 [BA] WG discussion has indicated that there is not WG consensus for this
 text.  It should be deleted.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/43>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:21:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:21:38 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #42: A1.4
Message-ID: <066.c718f23db5a05bfadaeed54ed9eac870@tools.ietf.org>

#42: A1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 A.1.4. Pre-existing data types


    There is a trade-off in design between re-using existing formats for
    historical compatibility, or choosing new formats for a "better"
    design.  This trade-off does not always require the "better" design
    to be used.  As a result. pre-existing complex data types described
    in Appendix B MAY be used, though this practice is NOT RECOMMENDED.

 [BA] Mailing list discussion indicates that there is not consensus to
 deprecate existing RADIUS types.  Suggested change:


    There is a trade-off in design between re-using existing formats for
    historical compatibility, or choosing new formats for a "better"
    design.  This trade-off does not always require the "better" design
    to be used.  As a result. pre-existing complex data types described
    in Appendix B MAY be used.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/42>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:19:08 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:18:39 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #41: A1.2
Message-ID: <075.e8d2ffb915eb6426a0ff306c0bbfc808@tools.ietf.org>

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
Description changed by bernard_aboba@…:

Old description:

> Does the data provide authentication and/or security capabilities for
>    the RADIUS protocol, as outlined below?  If so, it SHOULD be
>    allocated from the standard space via "IETF consensus", and SHOULD
>    NOT be allocated from the vendor space.
>
> [BA] A BCP should not be setting IANA allocation policy.  Recommended
> change:
>
>    Does the data provide authentication and/or security capabilities for
>    the RADIUS protocol, as outlined below?  If so, it SHOULD be
>    allocated from the standard space.

New description:

 A.1.2. Transport of Authentication and Security Data

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space via "IETF consensus", and SHOULD
    NOT be allocated from the vendor space.

       * Complex data types that carry authentication methods which
         RADIUS servers are expected to parse and verify as part of
         an authentication process.

       * Complex data types that carry security information intended
         to increase the security of the RADIUS protocol itself.

    Any data type carrying authentication and/or security data that is
    not meant to be parsed by a RADIUS server is an "opaque data type",
    as defined below.

 [BA] This section appears disjointed, as though it was missing some text.
 Recommended change:

 A.1.2. Transport of Authentication and Security Data

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, use of a complex data
 type is acceptable, under the following circumstances:

       * Complex data types that carry authentication methods which
         RADIUS servers are expected to parse and verify as part of
         an authentication process.

       * Complex data types that carry security information intended
         to increase the security of the RADIUS protocol itself.

    Any data type carrying authentication and/or security data that is
    not meant to be parsed by a RADIUS server is an "opaque data type",
    as defined below.

--

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/41#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:12:11 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:11:56 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #41: A1.2
Message-ID: <066.35ef0fd4b0f0bfa68c437991b72c5c9d@tools.ietf.org>

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space via "IETF consensus", and SHOULD
    NOT be allocated from the vendor space.

 [BA] A BCP should not be setting IANA allocation policy.  Recommended
 change:

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/41>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:09:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:09:07 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #40: A.1.1
Message-ID: <075.cabb75e8cd1eb2f0b7594d8170ea8486@tools.ietf.org>

#40: A.1.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Another bad reference:

       * Attributes grouped into a logical container, using the
         [RFC2868] tagging mechanism.  This approach is NOT
         RECOMMENDED (see Section 2.1.2), but is permissible where

 [BA] There is no section 2.1.2.  Perhaps this refers to section 3.2.2?

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/40#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:07:02 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:06:47 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #40: A.1.1
Message-ID: <066.c348298679e6ac8be6dda5f15d68c762@tools.ietf.org>

#40: A.1.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Does the data fit within the basic data types described in Section
    2.1.1, as outlined below?

 [BA] The basic data types are described in Section 2.1, not 2.1.1.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/40>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 07:03:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 07:02:59 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #39: Section 4
Message-ID: <066.df1daf14667d81e8afd9f29fbf508222@tools.ietf.org>

#39: Section 4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 4. IANA Considerations

    This document does not require that the IANA update any existing
    registry or create any new registry, but includes information that
    affects the IANA, which:

       * includes specific guidelines for Expert Reviewers appointed
         under the IANA considerations of [RFC3575]

       * includes guidelines that recommend against self allocation from
         the RADIUS standard attribute space in other SDO RADIUS
         Attribute specifications.

       * recommends that SDOs request a Private Enterprise Code (PEC)
         from the IANA, for use as a Vendor-Id within a Vendor-Specific
         attribute.

 [BA] BCPs cannot update standards track documents such as RFC 2865 or
 3575. This should be made more clear.  Recommended change:

 4. IANA Considerations

    This document has no action items for IANA.  However, it does provide
 guidelines for Expert Reviewers appointed as described in [RFC3575].

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/39>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:56:30 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:56:16 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #38: Section 3.3.2
Message-ID: <066.1af3d45c417cac96d365427693871f0f@tools.ietf.org>

#38: Section 3.3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Nevertheless, following the guidelines outlined within this document
    has many advantages.  Following these guidelines means that RADIUS
    servers can be updated to support the vendor's equipment by editing a
    RADIUS dictionary.  It is therefore RECOMMENDED that vendors follow
    the guidelines outlined here, which are intended to enable maximum
    interoperability with minimal changes to existing systems.  If these
    guidelines are not followed, then the vendor's equipment can only be
    supported via code changes in RADIUS server implementations.  Such
    code changes add complexity and delay to implementations.

 [BA] This advice is repeated elsewhere so it can be deleted here.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/38>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:52:49 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:52:31 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #37: Section 3.3
Message-ID: <066.742781818d0501ff26ecf299adf1569e@tools.ietf.org>

#37: Section 3.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Along with these advantages, some limitations of VSA usage are noted
    in [RFC2865] Section 5.26:

       This Attribute is available to allow vendors to support their own
       extended Attributes not suitable for general usage.  It MUST NOT
       affect the operation of the RADIUS protocol.

       Servers not equipped to interpret the vendor-specific information
       sent by a client MUST ignore it (although it may be reported).
       Clients which do not receive desired vendor-specific information
       SHOULD make an attempt to operate without it, although they may do
       so (and report they are doing so) in a degraded mode.

 [BA] This text appears to belong in Section 2.4 as indicated in a
 previously submitted issue.  It can therefore be deleted here.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/37>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:49:13 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:48:59 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #36: Section 3.2.3
Message-ID: <075.e79bd98b22ef5bac9db989d68d77e4f9@tools.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Despite the above caveats, there may be situations where complex
    attributes are beneficial because they reduce complexity in the non-
    RADIUS systems.  Unfortunately, there are no "hard and fast" rules
    for where the complexity would best be located.  Each situation has
    to be decided on a case-by-case basis.

 [BA] This paragraph is repeated in Section 2.1.  It should be deleted
 here.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:48:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:47:56 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #36: Section 3.2.3
Message-ID: <075.c01b3caff0d50893028c5e1710274a38@tools.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Comment(by bernard_aboba@…):

 Another sentence in Section 3.2.3:

    The only other exception to the recommendation against complex types
    is for types that can be treated as opaque data by the RADIUS server.

 [BA] As noted in Section 2.1, there are other situations in which complex
 types could be used, so this doesn't represent the only exception.
 Recommended change:

 Another exception to the recommendation against complex types is for types
 that can be treated as opaque data by the RADIUS server.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:45:03 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:44:42 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #36: Section 3.2.3
Message-ID: <066.754f7ea163a89c14248438330bcd1d17@tools.ietf.org>

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 We therefore RECOMMEND that the introduction of
    new types and complex data types within RADIUS attribute
    specifications be avoided.  A potential exception to this
    recommendation occurs for attributes that inherently require code
    changes on both the client and server.  For example, as described in
    Appendix B, complex attributes have been used in situations involving
    authentication and security attributes that need to be dynamically
    computed and verified.

 [BA] This advice is not completely consistent with that in Section 2.1.
 Recommended change:

    As described in Section 2.1, the introduction of complex data
    types is discouraged where viable alternatives are available.
    A potential exception is attributes that inherently require code
    changes on both the client and server.  For example, as described in
    Appendix B, complex attributes have been used in situations involving
    authentication and security attributes that need to be dynamically
    computed and verified.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:36:09 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:35:43 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #35: Section 3.2
Message-ID: <066.f29fbf3629c77bbf08c484718db6ecb1@tools.ietf.org>

#35: Section 3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:            
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 The RADIUS data types are poorly defined.

 [BA] Since Section 2.1 claims that RADIUS defines some basic data types,
 this sentence appears contradictory.  I recommend that it be deleted.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/35>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:31:46 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:31:14 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #34: Section 2.4
Message-ID: <066.724427df9acd759c7941d97bac4745fa@tools.ietf.org>

#34: Section 2.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 The first paragraph of Section 2.4 appears to refer to a missing quotation
 from RFC 2865 Section 5.26.

 Recommended text for Section 2.4 is as follows:

 2.4. Translation of Vendor Specifications

   [RFC2865] Section 5.26 defines Vendor-Specific attributes as follows:

       This Attribute is available to allow vendors to support their own
       extended Attributes not suitable for general usage.  It MUST not
       affect the operation of the RADIUS protocol.

       Servers not equipped to interpret the vendor-specific information
       sent by a client MUST ignore it (although it may be reported).
       Clients which do not receive desired vendor-specific information
       SHOULD make an attempt to operate without it, although they may do
       so (and report they are doing so) in a degraded mode.

    The limitation on changes to the RADIUS protocol effectively
    prohibits VSAs from changing fundamental aspects of RADIUS operation,
    such as modifying RADIUS packet sequences, or adding new commands.
    However, the requirement for clients and servers to be able to
    operate in the absence of VSAs has proven to be less of a constraint,
    since it is still possible for a RADIUS client and server to mutually
    indicate support for VSAs, after which behavior expectations can be
    reset.

    Therefore, RFC 2865 provides considerable latitude for development of
    new attributes within the vendor space, while prohibiting development
    of protocol variants.  This flexibility implies that RADIUS
    attributes can often be developed within the vendor space without
    loss (and possibly even with gain) in functionality.

    As a result, translation of RADIUS attributes developed within the
    vendor space into the standard space may provide only modest
    benefits, while accelerating the exhaustion of the standard attribute
    space.  We do not expect that all RADIUS attribute specifications
    requiring interoperability will be developed within the IETF, and
    allocated from the standards space.  A more scalable approach is to
    recognize the flexibility of the vendor space, while working toward
    improvements in the quality and availability of RADIUS attribute
    specifications, regardless of where they are developed.

    It is therefore NOT RECOMMENDED that specifications intended solely
    for use by a vendor or SDO use be translated into the standard space.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/34>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:25:10 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:24:52 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #33: Section 2.3
Message-ID: <066.62faf616ea565dc0b10e87f948868195@tools.ietf.org>

#33: Section 2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 New commands (i.e., the Code field in the packet header) and new
    attributes in the standard space are allocated only through "IETF
    Consensus" as noted in [RFC3575] Section 2.1.

 [BA] The rules described in RFC 3575 are more complex than this.  In fact,
 some parameters require standards track. Recommended change:

    Requirements for allocation of new commands (i.e. the Code field in the
 packet header) and new attributes within the standards space are described
 in [RFC3575] Section 2.1.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/33>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:22:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:21:54 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #32: Section 2.2
Message-ID: <066.33129145ce0a65cb59d1ab4569d4187f@tools.ietf.org>

#32: Section 2.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 As noted in this Section, VSA data formats are under the sole discretion
 of SDOs and vendors.  This point should be made up front.

 Recommended change is to replace Section 2.2 with the following:

  2.2. Vendor-Specific Attribute Space

    The Vendor-Specific Attribute space is defined to be the contents of
    the "String" field of the Vendor-Specific Attribute ([RFC2865]
    Section 5.26).  As discussed there, it is intended for vendors and
    SDOs to support their own Attributes not suitable for general use.

    While the encoding of attributes within the vendor space is under
    the control of vendors and SDOs, following the guidelines described
    here is advantageous since it enables maximum interoperability with
    minimal changes to existing systems.

    For example, RADIUS server support for new attributes using
    "basic data types" can typically be accomplished by editing
    a RADIUS dictionary, whereas "complex data types" typically
    require RADIUS server code changes, which can add complexity
    and delays in implementation.

    Vendor RADIUS Attribute specifications SHOULD self-allocate
    attributes from the vendor space, rather than requesting an
    allocation (or self-allocating) from within the RADIUS
    standard attribute space.

    VSA encodings that do not follow the [RFC2865] Section 5.26
    scheme are NOT RECOMMENDED.  Although [RFC2865] does not mandate it,
    implementations commonly assume that the Vendor Id can be used as a
    key to determine the on-the-wire encoding of a VSA.  Vendors
    therefore SHOULD NOT use multiple encodings for VSAs that are
    associated with a particular Vendor Id.  A vendor wishing to use
    multiple VSA encodings SHOULD request one Vendor Id for each VSA
    encoding that they will use.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/32>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 06:07:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 06:06:46 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #31: Section 2.1
Message-ID: <066.580754da2ef39b90d28026c0d6eba488@tools.ietf.org>

#31: Section 2.1
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 All other data formats are defined to be "complex data types", and
    are NOT RECOMMENDED for normal use.  Nested attributes, or attributes
    grouped via methods other than defined in [RFC2868] do not qualify as
    "basic data types", and SHOULD NOT be used.

    There may be situations where complex attributes are acceptable
    because they reduce complexity in non-RADIUS systems, or because
    leveraging the basic data types would be awkward.  Unfortunately,
    there are no "hard and fast" rules for where the complexity would
    best be located.  Each situation has to be decided on a case-by-case
    basis.  The cost-benefit trade-off may result in a "complex data
    type" being defined in RADIUS, as discussed in Appendix B.  When this
    is done, an explanation SHOULD be offered as to why the complex data
    type was used.

 [BA] The first paragraph could be mis-construed as prohibiting grouping
 mechanisms such as the Extended Attributes approach.

 Recommended replacement:

    All other data formats (including nested attributes) are defined
    to be "complex data types", and are NOT RECOMMENDED for normal
    use.  Complex data types MAY be used in situations where they
    reduce complexity in non-RADIUS systems, or where using
    the basic data types would be awkward (such as where grouping
    would be required in order to link related attributes).  Since
    there are no "hard and fast" rules for where complexity is best
    located, each situation has to be decided on a case-by-case
    basis.  Examples of this tradeoff are discussed in Appendix B.
    Where a complex data type is selected, an explanation SHOULD be
    offered as to why this was necessary.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/31>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 04:47:13 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 04:46:32 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #30: Section 1.4
Message-ID: <066.662d4351e84edff3e03f1dd33c281067@tools.ietf.org>

#30: Section 1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Material relating to reviews is included in various places within the
 document.  My recommendation is to delete Section 3.3.4 and to
 combine material relating to reviews into Section 1.4:

 1.4 Reviews

    For specifications utilizing attributes within the standards
    space, conformance with the design guidelines in this document
    is expected unless a good case can be made for an exception.
    Reviewers SHOULD use the design guidelines as a review
    checklist.

    While not required, IETF review may also be beneficial for
 specifications
    utilizing the Vendor-Specific space. Experience has shown that
 attributes
    not originally designed for general usage can subsequently garner
    wide-spread deployment.  An example is the vendor-specific attributes
    defined in [RFC2548], which have been widely implemented within
    IEEE 802.11 Access Points.

    In order to assist in the development of specifications
    conforming to these guidelines, authors can request review by
    sending email to the AAA Doctors [DOCTORS] or equivalent mailing list.
    The IETF Operations & Management Area Directors will then arrange for
    the review to be completed and posted to the AAA Doctors mailing list
    [DOCTORS], RADEXT WG mailing list, or other IETF mailing list.
    Since reviews are handled by volunteers, responses are provided on a
    best-effort basis, with no service level guarantees.  Authors are
    encouraged to seek review as early as possible, so as to
    avoid potential delays.

    In order to provide reviewers with access to the specification, vendors
    and SDOs are encouraged to make them publicly available.
    Where the RADIUS specification is embedded within a larger document
    which cannot be made public, the RADIUS attribute and value
    definitions can be made available on a public web site or can be
    published as an Informational RFC, as with [RFC4679].

    The review process requires neither allocation of attributes within
    the IETF standard attribute space nor publication of an IETF RFC.
    Requiring SDOs or vendors to rehost VSAs into the IETF standards
    attribute space solely for the purpose of obtaining review would put
    pressure on the standards space, and may be harmful to
    interoperability, since would create two ways to provision the same
    service.  Rehosting may also require changes to the RADIUS data model
    which will affect implementations that do not intend to support the
    SDO or vendor specifications.

    Similarly, vendors are encouraged to make their specifications
    publicly available, for maximum interoperability.  However, it is not
    necessary for a vendor to request publication of a VSA specification
    as an Informational RFC by the IETF.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/30>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 04:07:47 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 04:07:18 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #29: Section 2
Message-ID: <066.9278f2fd2da1a1adf9153579ef1ae1c5@tools.ietf.org>

#29: Section 2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:            
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Section 2 currently repeats text from other sections and utilizes MUST n
 MUST NOT normative language outside the bounds suggested in RFC 2119.

 A suggested rewrite is as follows:

 2. Guidelines

    The Remote Authentication Dial In User Service (RADIUS) defined in
    [RFC2865] and [RFC2866] uses elements known as attributes in order to
    represent authentication, authorization and accounting data.

    Unlike SNMP, first defined in [RFC1157] and [RFC1155], RADIUS does
    not define a formal data definition language.  The data type of
    RADIUS attributes is not transported on the wire.  Rather, the data
    type of a RADIUS attribute is fixed when an attribute is defined.
    Based on the RADIUS attribute type code, RADIUS clients and servers
    can determine the data type based on preconfigured entries within a
    data dictionary.

    To explain the implications of this early RADIUS design decision we
    distinguish two types of data types, namely "basic" and "complex".
    Basic data types use one of the existing RADIUS data types as defined
    below, encapsulated in a RADIUS attribute or VSA.  All other data
    formats are "complex types".

    RADIUS attributes can be classified into three broad categories:

       * Attributes that are of interest to a single vendor, e.g., for a
         product or product line.  Minimal cross-vendor interoperability
         is needed.  Vendor-Specific Attributes (VSAs) are appropriate
         for this purpose.  Code-point allocation is managed by each
         vendor, with the number space defined by their Private Enterprise
         Number (PEN).

       * Attributes that are of interest to an industry segment, where an
         SDO defines the attributes for that industry.  Multi-vendor
         interoperability within an industry segment is expected.

         Vendor-Specific Attributes (VSAs) are appropriate for
         use in this situation.  Code-point allocation is managed by
         the SDO with the number space defined by the SDO's PEN,
         rather then the PEN of an individual vendor.

       * Attributes that are of broad interest to the Internet Community.
         Multi-vendor interoperability is expected.

         Attributes within the standards space are appropriate for this
         purpose, and are allocated via IANA as described in [RFC3575].
         Since the standards space represents a finite resource,
         and is the only attribute space available for use by IETF working
 groups,
         vendors and SDOs are encouraged to utilize the VSA space, rather
 than
         requesting allocation of attributes from the standards space.
         Self-allocation of standards attributes is considered anti-social
         behavior and is strongly discouraged.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/29>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 21 Jun 2010 03:36:24 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, bernard_aboba@hotmail.com
Date: Mon, 21 Jun 2010 03:35:13 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #27: Section 1.3
Message-ID: <075.f9de9721aba99e8222bb62d2689fb0fc@tools.ietf.org>

#27: Section 1.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:  aland@…                  
     Type:  defect                     |      Status:  new                      
 Priority:  critical                   |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------
Changes (by bernard_aboba@…):

  * owner:  => aland@…


Comment:

 Please add the following paragraph to the end of Section 1.3:

    RADIUS protocol changes, or specification of attributes (such as
    Service-Type) that can, in effect, provide new RADIUS commands
    require greater expertise and deeper review, as do changes to the
    RADIUS operational model.  As a result, such changes are outside the
    scope of this document and MUST NOT be undertaken outside the IETF.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/27#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 20 Jun 2010 23:40:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Sun, 20 Jun 2010 23:39:52 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #28: Section 1.2
Message-ID: <075.526d29e14060cfe24f83d4961005d0a1@tools.ietf.org>

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
Description changed by bernard_aboba@…:

Old description:

> We emphasize that the uses of "MUST" and "MUST NOT" in this document
>    are limited to requirements to follow the IETF process for IETF
>    standards, and quotes from other documents.  As a result, the uses of
>    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
>    behavior within implementations.
>
> [BA] Since elements of this paragraph have been incorporated into the
> proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
> Section 6 appears restricts usage of "MUST" and "MUST NOT":
>
>    We emphasize that the uses of "MUST" and "MUST NOT" in this document
>    are limited to requirements to follow the IETF process for IETF
>    standards, and quotes from other documents.  As a result, the uses of
>    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
>    behavior within implementations.

New description:

 We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

 [BA] Since elements of this paragraph have been incorporated into the
 proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
 Section 6 appears restricts usage of "MUST" and "MUST NOT":

     Imperatives of the type defined in this memo must be used with care
    and sparingly.  In particular, they MUST only be used where it is
    actually required for interoperation or to limit behavior which has
    potential for causing harm (e.g., limiting retransmisssions)  For
    example, they must not be used to try to impose a particular method
    on implementors where the method is not required for
    interoperability.

--

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/28#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 20 Jun 2010 23:38:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Sun, 20 Jun 2010 23:38:47 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #28: Section 1.2
Message-ID: <066.21f1182b696155b3e3e204d3d7194146@tools.ietf.org>

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

 [BA] Since elements of this paragraph have been incorporated into the
 proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
 Section 6 appears restricts usage of "MUST" and "MUST NOT":

    We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/28>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 20 Jun 2010 23:35:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Sun, 20 Jun 2010 23:34:50 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #27: Section 1.3
Message-ID: <066.5b3c6a550fc959f2f8315453df9b692a@tools.ietf.org>

#27: Section 1.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Section 1.3 needs to describe the situations in which this document
 applies.  As discussed as part of the resolution of Issue 327, there are
 situations where vendors and SDOs will choose to not satisfy the
 guidelines.  Also, there is other work in progress (e.g. Extended
 Attributes).

 My recommendation is to replace Section 1.3 with the following:

 1.3 Applicability

    The advice in this document applies to attributes used to
    encode service-provisioning, authentication, or accounting data,
    based on the attribute encodings and data formats defined in RFC 2865
    [RFC2865], RFC 2866 [RFC2866] and subsequent RADIUS RFCs.

    Since this document represents a Best Current Practice, it does not
    update or deprecate existing standards.  As a result, the uses of
    the terms "MUST" and "MUST NOT" are limited to requirements already
    present in existing documents.

    It is RECOMMENDED that these guidelines be followed for all new RADIUS
    specifications, whether they originate from a vendor, an SDO, or the
 IETF.
    Doing so will ensure the widest possible applicability and
 interoperability
    of the specifications, while requiring minimal changes to existing
 systems.
    In particular, it is expected that RADIUS specifications requesting
    allocation within the standards space will follow these guidelines,
    and will explain why this is not possible if they cannot.

    However, there are situations in which vendors or SDOs can choose not
    to follow these guidelines without major consequences.  As noted in
    [RFC2865] Section 5.26, Vendor-Specific Attributes (VSAs) are
    "available to allow vendors to support their own extended Attributes
 not
    suitable for general usage."  Where vendors or SDOs develop
    specificatons "not suitable for general usage", limited
 interoperability
    and inability to use existing implementations may be acceptable and
    in these situations, vendors and SDOs MAY NOT choose to conform to
 these
    guidelines.

    Note that the RADEXT WG is currently involved in the development of an
    Extended Attributes specification [EXTEN].  This specification, when
    completed, will provide its own usage guidelines.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/27>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 20 Jun 2010 19:54:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: bernard_aboba@hotmail.com
Date: Sun, 20 Jun 2010 19:54:21 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #26: Terminology (Section 1.1)
Message-ID: <066.bb35d2e7170fe573be2872ab6e28e60f@tools.ietf.org>

#26: Terminology (Section 1.1)
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 standard space
      The 256 possible attributes that follow the format defined in
      [RFC2865] Section 5.

 vendor space
      The contents of the "String" field of a Vendor-Specific Attribute
       (VSA) ([RFC2865] Section 5.26).

 [BA] Given the extended attribute work, we may not want to define the
 standard space a bit more flexibly.  Also, the definition of vendor space
 should take the vendor-type field into account, no?
 Recommend this be changed to:

 standard space
      RADIUS attributes which are allocated by IANA and which follow the
 format defined in RFC 2865 [RFC2865] Section 5.

 vendor space
     The contents of the "String" field of a Vendor-Specific Attribute
 (VSA), as defined in [RFC2865] Section 5.26.  These attributes provide a
 unique attribute space for each vendor (identified by the Vendor-Type
 field) which they can self-allocate."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/26>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 20 Jun 2010 19:20:32 +0000
Message-ID: <BLU137-W2472BAA74908C6D1297B693C20@phx.gbl>
Content-Type: multipart/alternative; boundary="_7e63b6a6-9866-4661-97ea-2f5523cc45c2_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Meeting week of July 12
Date: Sun, 20 Jun 2010 12:19:18 -0700
MIME-Version: 1.0

--_7e63b6a6-9866-4661-97ea-2f5523cc45c2_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


We are looking at potentially scheduling a RADEXT Virtual Interim meeting t=
he week of July 12=2C 2010.=20

Please fill out a Doodle Poll indicating your availability:
http://www.doodle.com/362t54udqbbkupdp
 		 	   		  =

--_7e63b6a6-9866-4661-97ea-2f5523cc45c2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
We are looking at potentially scheduling a RADEXT Virtual Interim meeting t=
he week of July 12=2C 2010. <br><br>Please fill out a Doodle Poll indicatin=
g your availability:<br>http://www.doodle.com/362t54udqbbkupdp<br> 		 	   	=
	  </body>
</html>=

--_7e63b6a6-9866-4661-97ea-2f5523cc45c2_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 16 Jun 2010 14:54:42 +0000
Message-ID: <4C18E587.8050008@deployingradius.com>
Date: Wed, 16 Jun 2010 16:53:59 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> In this particular case I think your issue is with using accounting messages to provision a firewall.  I think it is that the accounting message is generated along the proxy chain (okay the extreme end of the proxy chain but nevertheless the proxy chain). Right?

  Yes.

> [AL>] The accounting message is still being tied to a session in this case.  And it is the same system.  The system appears to be distributed.  The real problem is that it is generated by the "same system that originated the Access-Request" Right?

  Yes.

> In the specific use case, the logical entities are all communicating.  I am not sure what you mean by "Administrative System".  Who is to say that the NAS and Server or not in the same adimistrative domain.  I don't know much details about the use case.  I don't know what the Admisitrative Domain has to do with this?

  What I mean is that the "NAS" functionality may be split across more
than 1 machine.  If so, they are all managed by the same people.

> Sure.  But who is to say that following a similar approach wouldn't simplify the network design.  We don't know enough details but perhaps in this case this was the best most economical approach to the problem.  It seems weird sitting at the IETF level.  
> 
> I am not sure what general guidance you would propose here that would help and not hinder.

  RADIUS isn't a generic provisioning system?

  I could use accounting packets to provision new users, rather than
using direct DB writes.  If the administration system doesn't have write
access to the database, it could use RADIUS to send the new user
credentials to the RADIUS server, which would write them to the DB.

  It's possible, but weird, and likely not recommended.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 16 Jun 2010 13:55:35 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: Is provisioning services in Accounting-Request packets bad?
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Wed, 16 Jun 2010 09:54:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <12E28CA6-108B-43E1-87FF-7FDC056B0BB9@elbrysnetworks.com>
To: radext mailing list <radiusext@ops.ietf.org>

On Jun 16, 2010, at 8:36 AM, Avi Lior wrote:

> I am not sure what general guidance you would propose here that would =
help and not hinder.

I'm not sure where such guidance would be delivered.  This is not a =
matter of RADIUS Attribute design, and it's out scope for the Design =
Guidelines.  It seems to me this is (or is not) a deviation from the =
RADIUS operational model, depending on your interpretation.

It may well be a reasonable solution in a given set or circumstances.  =
It certainly does not follow the "conservative" or "narrow" =
interpretation of the RADIUS operational model (command level data =
flow).  This is fine as a proprietary vendor extension to RADIUS.  My =
only concern would be if this kind of adaptation were to become popular, =
and customers created a demand to replicate this solution in other use / =
deployment cases, where it may not be appropriate.  I would not like to =
see this sort of solution evolve to become a de facto or de jure =
extension to the RADIUS standard.




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 16 Jun 2010 12:37:33 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Date: Wed, 16 Jun 2010 08:36:42 -0400
Subject: RE: Is provisioning services in Accounting-Request packets bad?
Thread-Topic: Is provisioning services in Accounting-Request packets bad?
Thread-Index: AcsNHPtiF3nn5/T5R3aCuMBzVo3OTQAL4+Yw
Message-ID: <AF6CC6ADFC631348B9C22998A699B9EC593FD7A2@m679t05.fpmis.bridgewatersys.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

See inline..

BTW I am not defending the specific use case  - and I am not critizing it e=
ither.  I don't have enough information.

I am concerned though that we may put in place rules/guidelines that would =
hinder good network design.

So specifically:

>   Sure.  But RADIUS isn't really a generic provisioning API.
[AL>] You are right RADIUS isn't a provisioning API or a provisioning syste=
m.  But the information obtained from RADIUS is being used to provision som=
ething.  Just like RADIUS is not a billing API nor a Billing system but rat=
her the information provided by RADIUS is useful in generating a bill for t=
he subscriber. =20
The information being generated by RADIUS is used for many purposes.

In this particular case I think your issue is with using accounting message=
s to provision a firewall.  I think it is that the accounting message is ge=
nerated along the proxy chain (okay the extreme end of the proxy chain but =
nevertheless the proxy chain). Right?


>   The "naive" expectation is that accounting messages are tied to
> sessions, and generated by the same system that originated the
> Access-Request.
[AL>] The accounting message is still being tied to a session in this case.=
  And it is the same system.  The system appears to be distributed.  The re=
al problem is that it is generated by the "same system that originated the =
Access-Request" Right?

>=20
> > I am not sure what the answer to one should be.  I would think no.
> But there could be corner cases where the real NAS cant generate
> accounting and the next hop AAA proxy can.  Certainly in some
> deployments the NAS is not really a single entity.  So  making a rule
> could break these corner cases.
>=20
>   Sure.  If the same "administrative system" creates Access-Requests &&
> Accounting-Requests, it doesn't matter which box creates what, so long
> as they all communicate.  But that's very different from having the
> system sending an Access-Accept create an Accounting-Request packet.

In the specific use case, the logical entities are all communicating.  I am=
 not sure what you mean by "Administrative System".  Who is to say that the=
 NAS and Server or not in the same adimistrative domain.  I don't know much=
 details about the use case.  I don't know what the Admisitrative Domain ha=
s to do with this?

>=20
> > But what is the real problem here? Other than potential problems for
> particular use cases.  I think we should remain silent.
>=20
>   It complicates network design.  It potentially allows for unlimited
> growth in the number of RADIUS packets based on a login.  If the
> Access-Request is proxied multiple times. and each proxy "invents"
> another RADIUS packet... bad things can happen.

Sure.  But who is to say that following a similar approach wouldn't simplif=
y the network design.  We don't know enough details but perhaps in this cas=
e this was the best most economical approach to the problem.  It seems weir=
d sitting at the IETF level. =20

I am not sure what general guidance you would propose here that would help =
and not hinder.

>=20
>   Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 16 Jun 2010 06:28:15 +0000
Message-ID: <4C186EC8.6070802@deployingradius.com>
Date: Wed, 16 Jun 2010 08:27:20 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> Okay.  I think I understand....
> 
> The RADIUS server sends an access-accept to the NAS and at the same time more or less, it sends an Accounting Request message to the Back Office to provisiong something (a firewall).
>
> Weird.  This is instead of the NAS generating an accounting request message.

  Yes. and yes.

> But given that what is wrong with this?
> 
> For one, the session may not have started on the NAS so you have provisioned something that may have not happened.  In the case of the FW, this could be bad - you opened a hole for something that isnt really there etc.

  Sure.  But RADIUS isn't really a generic provisioning API.

> But is this still problematic in general.
> 
> The general case is:
> 
> 1) Does the specification require that an Accounting message be generate by a NAS only.  Or can it be generated by a proxy or server?

  The "naive" expectation is that accounting messages are tied to
sessions, and generated by the same system that originated the
Access-Request.

> I am not sure what the answer to one should be.  I would think no. But there could be corner cases where the real NAS cant generate accounting and the next hop AAA proxy can.  Certainly in some deployments the NAS is not really a single entity.  So  making a rule could break these corner cases.

  Sure.  If the same "administrative system" creates Access-Requests &&
Accounting-Requests, it doesn't matter which box creates what, so long
as they all communicate.  But that's very different from having the
system sending an Access-Accept create an Accounting-Request packet.

> But what is the real problem here? Other than potential problems for particular use cases.  I think we should remain silent.

  It complicates network design.  It potentially allows for unlimited
growth in the number of RADIUS packets based on a login.  If the
Access-Request is proxied multiple times. and each proxy "invents"
another RADIUS packet... bad things can happen.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 22:37:54 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "David B. Nelson" <dnelson@elbrysnetworks.com>, radext mailing list <radiusext@ops.ietf.org>
Date: Tue, 15 Jun 2010 18:37:01 -0400
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Thread-Topic: Is provisioning services in Accounting-Request packets bad?
Thread-Index: AcsM20X61gHdrf9rT/y6Qdh1huzujA==
Message-ID: <932FF5E1-D50B-42B3-9889-CAB44ECE1D6A@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Okay.  I think I understand....

The RADIUS server sends an access-accept to the NAS and at the same time mo=
re or less, it sends an Accounting Request message to the Back Office to pr=
ovisiong something (a firewall).

Weird.  This is instead of the NAS generating an accounting request message=
.

But given that what is wrong with this?

For one, the session may not have started on the NAS so you have provisione=
d something that may have not happened.  In the case of the FW, this could =
be bad - you opened a hole for something that isnt really there etc.

But is this still problematic in general.

The general case is:

1) Does the specification require that an Accounting message be generate by=
 a NAS only.  Or can it be generated by a proxy or server?

2) Does the specification allow a Proxy to add attributes to accounting. =20

The answer to 2 is yes.

I am not sure what the answer to one should be.  I would think no. But ther=
e could be corner cases where the real NAS cant generate accounting and the=
 next hop AAA proxy can.  Certainly in some deployments the NAS is not real=
ly a single entity.  So  making a rule could break these corner cases.

But what is the real problem here? Other than potential problems for partic=
ular use cases.  I think we should remain silent.


On 15-06-2010, at 15:35 , Alan DeKok wrote:

> Bernard Aboba wrote:
>> Alan DeKok said:
>>=20
>> "  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
>> server originates the Accounting-Request."
>>=20
>> So this requires the NAS to act as an Accounting Server? =20
>=20
>  Nope.  A third machine receives the Accounting-Request.
>=20
>> What if doesn't respond?  Does the RADIUS server keep retransmitting the
>> Accounting-Request??
>=20
>  Nope.  The time frames are 'too short' for retransmits to be relevant.
>=20
>  Alan DeKok.
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 19:35:31 +0000
Message-ID: <4C17D5F7.3030408@deployingradius.com>
Date: Tue, 15 Jun 2010 21:35:19 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,  'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Alan DeKok said:
> 
> "  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
> server originates the Accounting-Request."
> 
> So this requires the NAS to act as an Accounting Server?  

  Nope.  A third machine receives the Accounting-Request.

> What if doesn't respond?  Does the RADIUS server keep retransmitting the
> Accounting-Request??

  Nope.  The time frames are 'too short' for retransmits to be relevant.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 19:31:09 +0000
Message-ID: <4C17D4E3.10308@deployingradius.com>
Date: Tue, 15 Jun 2010 21:30:43 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: "David B. Nelson" <dnelson@elbrysnetworks.com>,  radext mailing list <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> On one hand we may need more information as David is mentioning.
> 
> But there is nothing wrong with a Back office system using information contained in an accounting message.

  Absolutely.

> A back office system can be used for billing but it can also be used to do other things like generate triggers for Intrussion Detection/Prevention systems, Firewalls etc etc....
> 
> And thus some of the information could be used for provisioning of some service by a back office system.
> 
> We should not be concerned about this.  It has nothing to do with the over the wire protocol.  As long as the information is valid to be sent in the Accounting Messages we should be fine.

  My main issue is that accounting packets should be generated by the
system managing the user session. i.e. the NAS.  Anything else in the
network (e.g. RADIUS proxy) has no business "inventing" accounting
packets for a session.

  That strikes me as an odd way of creating a vendor-specific
provisioning API.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 19:05:41 +0000
Message-ID: <4C17CED3.90500@deployingradius.com>
Date: Tue, 15 Jun 2010 21:04:51 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David B. Nelson wrote:
>> The NAS sends an Access-Request to the RADIUS server.
>> The RADIUS server originates the Accounting-Request.
> 
> To a RADIUS Accounting Server?

  Nope.  To a provisioning system.  e.g. firewall.  It opens FW rules
for the IP, send an ACK, and otherwise discards the accounting data.

  The normal accounting stream still exists, and uses a completely
different path through the network.

> Let's see if I've got this....
> 
> The NAS (Node A) sends an Access-Request to the RADIUs Server (Node B) which then sends an Accounting-Request to the RADIUS Accounting Server (Node C), and subsequently the RADIUS Server (Node B) sends an Access-Accept to the NAS (Node A)?  The RADIUS Accounting Server (Node C) by some means creates access rules for the user and sends them to the Firewall (Node D)?
> 
> Yikes.

  Something like that.

>> The *intent* appears to be that waiting the extra 1/10s for the NAS to
>> originate the Accounting-Request would be a catastrophic delay.  The
>> "network setup" side of the user session needs to be done before the
>> Access-Accept is received by the NAS.
>>
>> The "simplest" way to do this is to overload RADIUS.
> 
> Well, RADIUS has a history of being an eminently overload-able protocol.  :-)
> 
> I think it's unusual, to say the least, for a RADIUS Server to initiate a request on behalf of a NAS unless that RADIUS Server is acting in the role of RADIUS Proxy Server.  That doesn't seem to be the case here.

  Yup.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 18:39:01 +0000
Message-ID: <BLU137-DS9B25E90E08BE9CA9BFD1393DD0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>, "'David B. Nelson'" <dnelson@elbrysnetworks.com>
CC: "'radext mailing list'" <radiusext@ops.ietf.org>
Subject: RE: Is provisioning services in Accounting-Request packets bad?
Date: Tue, 15 Jun 2010 11:40:18 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcsMtgeGNdw3k5GUQAi7QrdKaWVc3wAA9jig
Content-Language: en-us

Alan DeKok said:

"  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
server originates the Accounting-Request."

So this requires the NAS to act as an Accounting Server?  

What if doesn't respond?  Does the RADIUS server keep retransmitting the
Accounting-Request??


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 18:38:18 +0000
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Tue, 15 Jun 2010 14:37:53 -0400
Cc: 'radext mailing list' <radiusext@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <53333FD9-4B64-4AEB-8042-8081FBCFF456@elbrysnetworks.com>
To: Alan DeKok <aland@deployingradius.com>

On Jun 15, 2010, at 2:06 PM, Alan DeKok wrote:

> It creates FW rules for the user.  It does *not* relay the result back
> to the NAS.

OK, I think I get it.

> The NAS sends an Access-Request to the RADIUS server.
> The RADIUS server originates the Accounting-Request.

To a RADIUS Accounting Server?

Let's see if I've got this....

The NAS (Node A) sends an Access-Request to the RADIUs Server (Node B) =
which then sends an Accounting-Request to the RADIUS Accounting Server =
(Node C), and subsequently the RADIUS Server (Node B) sends an =
Access-Accept to the NAS (Node A)?  The RADIUS Accounting Server (Node =
C) by some means creates access rules for the user and sends them to the =
Firewall (Node D)?

Yikes.

> The *intent* appears to be that waiting the extra 1/10s for the NAS to
> originate the Accounting-Request would be a catastrophic delay.  The
> "network setup" side of the user session needs to be done before the
> Access-Accept is received by the NAS.
>
> The "simplest" way to do this is to overload RADIUS.

Well, RADIUS has a history of being an eminently overload-able protocol. =
 :-)

I think it's unusual, to say the least, for a RADIUS Server to initiate =
a request on behalf of a NAS unless that RADIUS Server is acting in the =
role of RADIUS Proxy Server.  That doesn't seem to be the case here.

Regards,

Dave

David B. Nelson

Elbrys Networks, Inc.
282 Corporate Drive, Unit 1
Portsmouth, NH 03801

+1.603.570.2636
www.elbrysnetworks.com
dnelson@elbrysnetworks.com






--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 18:06:35 +0000
Message-ID: <4C17C118.3060009@deployingradius.com>
Date: Tue, 15 Jun 2010 20:06:16 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David B. Nelson wrote:
> What does the provisioning system do with the information and how does it relate the result back to the NAS?

  It creates FW rules for the user.  It does *not* relay the result back
to the NAS.

> What entity sends the Accounting-Request, the NAS or he RADIUS server.  You use "it" and I'm unclear what "it" refers to.

  The NAS sends an Access-Request to the RADIUS server.  The RADIUS
server originates the Accounting-Request.

  The *intent* appears to be that waiting the extra 1/10s for the NAS to
originate the Accounting-Request would be a catastrophic delay.  The
"network setup" side of the user session needs to be done before the
Access-Accept is received by the NAS.

  The "simplest" way to do this is to overload RADIUS.

> Well, I personally think that provisioning services via an Accounting-Request is bad, but I don't yet see how the NAS is actually being provisioned by a request message.  What is fairly common practice is to build resource management systems around RADIUS Accounting.  Is that the sort of thing you're talking about?

  I can understand making decisions (e.g. Disconnect-Request) on
reception of an Accounting-Request packet.  i.e. "user is over 2G, kick
them off of the net".

  The above discussion isn't that.  It's the RADIUS server *fabricating*
an Accounting-Request packet for a user session, because it's faster to
do it that way than to wait for the NAS.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 17:59:14 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: Alan DeKok <aland@deployingradius.com>, radext mailing list <radiusext@ops.ietf.org>
Date: Tue, 15 Jun 2010 13:58:32 -0400
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Thread-Topic: Is provisioning services in Accounting-Request packets bad?
Thread-Index: AcsMtF499lfWbg37QL26T/qVskVEKw==
Message-ID: <020DF101-49BC-433F-87F9-A22B4FD5B0DD@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On one hand we may need more information as David is mentioning.

But there is nothing wrong with a Back office system using information cont=
ained in an accounting message.

A back office system can be used for billing but it can also be used to do =
other things like generate triggers for Intrussion Detection/Prevention sys=
tems, Firewalls etc etc....

And thus some of the information could be used for provisioning of some ser=
vice by a back office system.

We should not be concerned about this.  It has nothing to do with the over =
the wire protocol.  As long as the information is valid to be sent in the A=
ccounting Messages we should be fine.




On 15-06-2010, at 12:13 , David B. Nelson wrote:

> On Jun 15, 2010, at 11:58 AM, Alan DeKok wrote:
>=20
>> When a RADIUS server returns Access-Accept, some systems also request
>> that it send an Accounting-Request packet to a provisioning system.
>> This provisioning system requires information such as Framed-IP-Address,
>> or copies of some VSAs from the Access-Accept.
>=20
> What does the provisioning system do with the information and how does it=
 relate the result back to the NAS?
>=20
> What entity sends the Accounting-Request, the NAS or he RADIUS server.  Y=
ou use "it" and I'm unclear what "it" refers to.
>=20
>> Quote "This is not unusual, and several vendors are providing such a
>> solution".
>>=20
>> RFC 2866 doesn't forbid this, as it expects accounting packets to be
>> sent by the NAS.  The guidelines document contains minimal text about
>> accounting.
>>=20
>> Is it worth adding a line in the "guidelines" document saying that
>> accounting packets are to be used for... accounting?  And that
>> provisioning services via Accounting-Request is bad?
>=20
> Well, I personally think that provisioning services via an Accounting-Req=
uest is bad, but I don't yet see how the NAS is actually being provisioned =
by a request message.  What is fairly common practice is to build resource =
management systems around RADIUS Accounting.  Is that the sort of thing you=
're talking about?
>=20
> Regards,
>=20
> Dave
>=20
> David B. Nelson
>=20
> Elbrys Networks, Inc.
> 282 Corporate Drive, Unit 1
> Portsmouth, NH 03801
>=20
> +1.603.570.2636
> www.elbrysnetworks.com
> dnelson@elbrysnetworks.com
>=20
>=20
>=20
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 16:13:48 +0000
Subject: Re: Is provisioning services in Accounting-Request packets bad?
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Tue, 15 Jun 2010 12:13:28 -0400
Cc: 'radext mailing list' <radiusext@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8BFDB7F-2B4B-44F8-9638-8AF70796DF82@elbrysnetworks.com>
To: Alan DeKok <aland@deployingradius.com>

On Jun 15, 2010, at 11:58 AM, Alan DeKok wrote:

> When a RADIUS server returns Access-Accept, some systems also request
> that it send an Accounting-Request packet to a provisioning system.
> This provisioning system requires information such as =
Framed-IP-Address,
> or copies of some VSAs from the Access-Accept.

What does the provisioning system do with the information and how does =
it relate the result back to the NAS?

What entity sends the Accounting-Request, the NAS or he RADIUS server.  =
You use "it" and I'm unclear what "it" refers to.

> Quote "This is not unusual, and several vendors are providing such a
> solution".
>=20
> RFC 2866 doesn't forbid this, as it expects accounting packets to be
> sent by the NAS.  The guidelines document contains minimal text about
> accounting.
>=20
> Is it worth adding a line in the "guidelines" document saying that
> accounting packets are to be used for... accounting?  And that
> provisioning services via Accounting-Request is bad?

Well, I personally think that provisioning services via an =
Accounting-Request is bad, but I don't yet see how the NAS is actually =
being provisioned by a request message.  What is fairly common practice =
is to build resource management systems around RADIUS Accounting.  Is =
that the sort of thing you're talking about?

Regards,

Dave

David B. Nelson

Elbrys Networks, Inc.
282 Corporate Drive, Unit 1
Portsmouth, NH 03801

+1.603.570.2636
www.elbrysnetworks.com
dnelson@elbrysnetworks.com






--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 15 Jun 2010 16:00:01 +0000
Message-ID: <4C17A33D.2090405@deployingradius.com>
Date: Tue, 15 Jun 2010 17:58:53 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Is provisioning services in Accounting-Request packets bad?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

  When a RADIUS server returns Access-Accept, some systems also request
that it send an Accounting-Request packet to a provisioning system.
This provisioning system requires information such as Framed-IP-Address,
or copies of some VSAs from the Access-Accept.

  Quote "This is not unusual, and several vendors are providing such a
solution".

  RFC 2866 doesn't forbid this, as it expects accounting packets to be
sent by the NAS.  The guidelines document contains minimal text about
accounting.

  Is it worth adding a line in the "guidelines" document saying that
accounting packets are to be used for... accounting?  And that
provisioning services via Accounting-Request is bad?

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 11 Jun 2010 03:54:08 +0000
From: "Sanchez, Mauricio (ProCurve)" <mauricio.sanchez@hp.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, radext mailing list <radiusext@ops.ietf.org>
CC: Ron Bonica <rbonica@juniper.net>
Date: Fri, 11 Jun 2010 03:50:58 +0000
Subject: RE: New WG co-chair
Thread-Topic: New WG co-chair
Thread-Index: AcsIq+WHvButc422RKCIchV/bl7DQgAKIwIA
Message-ID: <9BC2F7926B33FE4AB10D69891D58FC1C5313DB6B41@GVW0671EXC.americas.hpqcorp.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thank you Dan.  Look forward to rolling up my sleeves together with the RAD=
EXT community and continuing to improve RADIUS. =20

-MS

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On=
 Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, June 10, 2010 7:48 AM
To: radext mailing list
Cc: Ron Bonica
Subject: New WG co-chair

Please welcome Mauricio Sanchez as the new co-chair of the RADEXT WG,
working together with Bernard Aboba. Congratulations and good luck,
Mauricio.=20

Thanks again to David Nelson who co-chaired for many years the WG
together with Bernard, and we hope that he will continue to be a fine
contributor.=20

Please allow me to thank everybody who considered the nomination, to all
people who made proposals and sent valuable comments about the
candidates. I am encouraged by the good response and the discussions
that took place during the open nomination process. I had to chose among
a number of candidates, all fine professionals and willing to contribute
to the WG progress by assuming the responsibility of co-chairing the WG.
It's been a difficult choice and a good sign about the vitality of the
WG.=20

Regards,

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 10 Jun 2010 14:48:50 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: New WG co-chair
Date: Thu, 10 Jun 2010 16:47:49 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040228312F@307622ANEX5.global.avaya.com>
Thread-Topic: New WG co-chair
Thread-Index: AcsIq+WHvButc422RKCIchV/bl7DQg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "radext mailing list" <radiusext@ops.ietf.org>
Cc: "Ron Bonica" <rbonica@juniper.net>

Please welcome Mauricio Sanchez as the new co-chair of the RADEXT WG,
working together with Bernard Aboba. Congratulations and good luck,
Mauricio.=20

Thanks again to David Nelson who co-chaired for many years the WG
together with Bernard, and we hope that he will continue to be a fine
contributor.=20

Please allow me to thank everybody who considered the nomination, to all
people who made proposals and sent valuable comments about the
candidates. I am encouraged by the good response and the discussions
that took place during the open nomination process. I had to chose among
a number of candidates, all fine professionals and willing to contribute
to the WG progress by assuming the responsibility of co-chairing the WG.
It's been a difficult choice and a good sign about the vitality of the
WG.=20

Regards,

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 08 Jun 2010 19:30:17 +0000
Message-ID: <4C0E9A11.5090504@deployingradius.com>
Date: Tue, 08 Jun 2010 21:29:21 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Glenn Kowack <glenn@riveronce.com>
CC: gen-art@ietf.org, 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: Gen-ART LC review of draft-ietf-radext-tcp-transport-06.txt
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

Glenn Kowack wrote:
...
>>> Does ‘traditional’ here mean as defined by the specification or is UDP
>>> use optional?
>>  It means "as defined by the spec".  Until now, UDP has been mandatory.
> 
> I recommend you say that explicitly: as defined by the specification.  It's not
> clear to me what 'traditional' means to random readers; they may view the
> cited use of UDP as strictly historical.  In any event, they probably won't
> understand that 'traditional' means 'normative'.

  OK.

>> It is not intended to define TCP as a transport protocol for RADIUS in
>> the absence of a secure transport layer.
> 
> Although an improvement, your change does not provide the clarification
> I believe is necessary.  Stating a negative, and also citing 'intent' in "not
> intended to define", is awkward and leaves room for speculation about the
> positive case.  Please see my prior example.

  OK, except that using RADIUS + TCP over IPSec would be allowed.  It's
too restrictive to specify TLS as the only permitted secure transport layer.

> I think I should have been clearer that my question is about generally-
> acceptable levels of failure for a mass-market network service.  This sort
> of data covers a broad area and should be publicly available.

  References would be helpful.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 08 Jun 2010 14:33:34 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: aland@deployingradius.com, iesg@ietf.org
Date: Tue, 08 Jun 2010 14:33:14 -0000
Reply-To: radiusext@ops.ietf.org
Subject: [radext] #25: IESG DISCUSS Comments
Message-ID: <054.920a9e623434ddb929f86da019a86134@tools.ietf.org>

#25: IESG DISCUSS Comments
-----------------------------------+----------------------------------------
 Reporter:  iesg@…                 |       Owner:  aland@…                  
     Type:  defect                 |      Status:  new                      
 Priority:  blocker                |   Milestone:  milestone1               
Component:  tcp-transport          |     Version:  1.0                      
 Severity:  Submitted WG Document  |    Keywords:                           
-----------------------------------+----------------------------------------
 Discusses and other comments

 Summary: Has a DISCUSS. Has enough positions to pass once DISCUSSes are
 resolved.
 Russ Housley

 Comment (2010-05-19)

   Please consider the comments from the Gen-ART Review by Glenn
   Kowack on 18 May 2010.  The review can be found at:

     http://www.softarmor.com/rai/temp-gen-art/
     draft-ietf-radext-tcp-transport-06-kowack.txt

 Lars Eggert

 Comment (2010-05-20)

 Agree with Tim's DISCUSS.

 Section 27, paragraph 13:
 >    It is not intended
 >    to define TCP as a transport protocol for RADIUS in the absence of
 >    TLS.

   The document title is "RADIUS Over TCP". It's surprising to then see
   that abstract say that it is not intended to define RADIUS over TCP...
   Suggestion: Rename document to "Radius over TLS"?


 Section 1., paragraph 1:
 >    While
 >    there are a number of benefits to using UDP as outlined in [RFC2865]
 >    Section 2.4, there are also some limitations:

   Lack of congestion control is surely a limitation?


 Section 1.1., paragraph 2:
 >    In scenarios where RADIUS proxies exchange a large volume of packets
 >    (10+ packets per second), it is likely that there will be sufficient
 >    traffic to enable the congestion window to be widened beyond the
 >    minimum value on a long-term basis, enabling ACK piggy-backing.

   I don't understand what this paragraph means to say. The TCP
   congestion window opens already at much lower rates than 10+ pps.
   Also, how is this at all related to ACK-piggybacking?


 Section 1.1., paragraph 5:
 >    These problems disappear if a 4096 application-layer payload can be
 >    used alongside RADIUS over TLS.  Since most TCP implementations
 >    support MTU discovery, the TCP MSS is automatically adjusted to
 >    account for the MTU, and the larger congestion window supported by
 >    TCP may allow multiple TCP segments to be sent within a single
 >    window.

   Even those few TCP stacks that don't do PMTUD can already support
   arbitrary payloads (just with slightly less efficient packetization).


 Section 2.6.1., paragraph 5:
 >    As noted previously, RADIUS packets SHOULD NOT be re-transmitted to
 >    the same destination IP and numerical port, but over a different
 >    transport layer.

   Where does it say that? The second paragraph of Section 2.6 says that
   they MAY be retransmitted over a new connection (which is different
   from a SHOULD NOT). Also, "transport layer" here is unclear - do you
   mean "transport connection" (= use a different TCP connection) or do
   you mean "transport protocol" (= use UDP)?


 Section 2.6.2., paragraph 2:
 >    Unlike UDP, TLS is subject to issues related to Head of Line (HoL)
 >    blocking.  This occurs when when a TLS segment is lost and a
 >    subsequent TLS segment arrives out of order.  While the RADIUS server
 >    can process RADIUS packets out of order, the semantics of TLS makes
 >    this impossible.  This limitation can lower the maximum packet
 >    processing rate of RADIUS over TLS.

   s/TLS/TCP/ in this paragraph


 Section 2.6.4., paragraph 6:
 >    After applying the above rules, there are still situations where the
 >    previous specifications allow a packet to be "silently discarded".
 >    In these situations, the TCP connections MAY remain open, or MAY be
 >    closed, as an implementation choice.  However, the invalid packet
 >    MUST be silently discarded.

   In order to reduce connection-setup overheads, wouldn't it make sense
   to RECOMMEND the connection stay open?

 Ralph Droms

 Discuss (2010-05-20)

 This Discuss is related to Tim's Discuss.  This text:

    "Bare" TCP transport MAY, however, be used when another method such
    as
 IPSec [RFC4301] is used to provide additional confidentiality and
    security.
 Should experience show that such deployments are useful,
    this specification
 could be moved to standards track.

 is confusing.  Why would experience with
 "bare" TCP or IPSec TCP cause draft-ietf-radext-tcp-transport to progress
 to
 Standards Track?

 Similarly, from the Abstract:

    It [draft-ietf-radext-tcp-transport-06.txt] is not intended
    to define TCP as a transport protocol for RADIUS in the absence of
    TLS.

 while several of the motivations for RADIUS over TCP in section 1.1 are
 not
 specific to RADIUS with TLS.

 Adrian Farrel

 Comment (2010-05-20)

 To follow up on Tim Polk's Discuss point 2
 I appreciate the sentiment of the
 paragraph, but "NOT RECOMMENDED" is not RFC 2119 language (as idnits would
 tell
 you). You have to flip the sense of the sentence and use "RECOMMENDED".
 But Tim
 is also right, please consider "MUST NOT" since the following paragraph...

    "Bare" TCP transport MAY, however, be used when another method such
    as IPSec [RFC4301] is used to provide additional confidentiality and
    security.  Should experience show that such deployments are useful,
    this specification could be moved to standards track.

 ...is really confusing. It implies that the purpose of this document *is*
 to
 define the use of bare TCP transport which is in conflict with the
 Abstract.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/25>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 08 Jun 2010 14:27:48 +0000
Message-ID: <BLU137-W12C935295D1D5695A60FF93D60@phx.gbl>
Content-Type: multipart/alternative; boundary="_173f1fb3-7506-40f6-a833-e6ee1bc0c714_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Repost:  The RADEXT WG Guide to TRAC
Date: Tue, 8 Jun 2010 07:27:28 -0700
MIME-Version: 1.0

--_173f1fb3-7506-40f6-a833-e6ee1bc0c714_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


The RADEXT WG is now using the TRAC database to keep track of issues=20
relating to work in progress=2C including working group work items and=20
individual submissions undergoing review.  This document provides some=20
basic information on how to use TRAC to submit or edit issues. =20
Documentation
 relating to the TRAC Issue Tracking database is available here: http://tra=
c.tools.ietf.org/wg/radext/trac/wiki

Since this documentation is somewhat lengthy (and mostly relevant to=20
Admins)=2C here is a pithy synopsis.=20
=20
1.       To submit an issue=20
in TRAC=2C you first need to login to the RADEXT WG site on the tools=20
server:  http://tools.ietf.org/wg/radext/trac/login
=20


2.       If you don=92t already have a login ID=2C you can obtain one by=20
navigating to this site:   http://trac.tools.ietf.org/newlogin


3.       Once you have obtained an account=2C and have logged in=2C you can=
=20
file an issue by navigating to the  ticket entry form: http://trac.tools.ie=
tf.org/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=2C or =93enhancement=94 for a proposed addition of=20
functionality (such as an additional requirement).=20

b.      The Priority: field is set based on the severity of the Issue. =20
 For example=2C editorial issues are typically =93minor=94 or =93trivial=94=
.=20

c.       The Milestone: field should be set to milestone1 (useless=2C I=20
know).=20

d.      The Component: field should be set to the document you are=20
filing the issue on. =20

e.      The Version: field should be set to =931.0=94.=20

f.        The Severity: field should be set to based on the status of=20
the document (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=20
inspiration seizes you.=20

h.      The Assign To: field is generally filled in with the email=20
address of the editor.=20


5.       Typically it won=92t be necessary to enclose a file with the=20
ticket=2C but if you need to=2C select =93I have files to attach to this=20
ticket=94.=20


6.       If you want to preview your Issue=2C click on the =93Preview=94=20
button.  When you=92re ready to submit the issue=2C click on the =93Create=
=20
Ticket=94 button.=20


7.       If you want to update an issue=2C go to the "View Tickets" page: h=
ttp://trac.tools.ietf.org/wg/radext/trac/report/1=20
 Click on the ticket # you want to update=2C and then modify the ticket=20
fields as required.=20


That=92s it! =20


If you encounter problems with TRAC=2C send email to me and I=92ll try to=20
figure out what=92s going on.=20


Happy TRACing=2C

Bernard 		 	   		  =

--_173f1fb3-7506-40f6-a833-e6ee1bc0c714_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The RADEXT WG is now using the TRAC database to keep track of issues=20
relating to work in progress=2C including working group work items and=20
individual submissions undergoing review.&nbsp=3B This document provides so=
me=20
basic information on how to use TRAC to submit or edit issues.&nbsp=3B <br>=
Documentation
 relating to the TRAC Issue Tracking database is available here: <a rel=3D"=
nofollow" href=3D"http://trac.tools.ietf.org/wg/radext/trac/wiki">http://tr=
ac.tools.ietf.org/wg/radext/trac/wiki</a><br>
Since this documentation is somewhat lengthy (and mostly relevant to=20
Admins)=2C here is a pithy synopsis. <br>&nbsp=3B<br>1.&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B To submit an issue=20
in TRAC=2C you first need to login to the RADEXT WG site on the tools=20
server:&nbsp=3B <a rel=3D"nofollow" href=3D"http://tools.ietf.org/wg/radext=
/trac/login">http://tools.ietf.org/wg/radext/trac/login</a>
 <br><br>
2.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you don=92t already h=
ave a login ID=2C you can obtain one by=20
navigating to this site:&nbsp=3B&nbsp=3B <a rel=3D"nofollow" href=3D"http:/=
/trac.tools.ietf.org/newlogin">http://trac.tools.ietf.org/newlogin</a><br><=
br>
3.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Once you have obtained a=
n account=2C and have logged in=2C you can=20
file an issue by navigating to the&nbsp=3B ticket entry form: <a rel=3D"nof=
ollow" href=3D"http://trac.tools.ietf.org/wg/radext/trac/newticket">http://=
trac.tools.ietf.org/wg/radext/trac/newticket</a><br><br>
4.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B When opening an issue:<b=
r><br>
a.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Type: field should b=
e set to =93defect=94 for an issue with the
 current document text=2C or =93enhancement=94 for a proposed addition of=20
functionality (such as an additional requirement). <br>
b.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Priority: field is set based=
 on the severity of the Issue.&nbsp=3B&nbsp=3B
 For example=2C editorial issues are typically =93minor=94 or =93trivial=94=
. <br>
c.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Milestone: field sho=
uld be set to milestone1 (useless=2C I=20
know). <br>
d.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Component: field should be s=
et to the document you are=20
filing the issue on.&nbsp=3B <br>
e.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Version: field should be set=
 to =931.0=94. <br>
f.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Severity: fi=
eld should be set to based on the status of=20
the document (e.g. =93In WG Last Call=94 for a document in WG last call)<br=
>
g.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Keywords: an=
d CC: fields can be left blank unless=20
inspiration seizes you. <br>
h.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B The Assign To: field is generall=
y filled in with the email=20
address of the editor. <br>
<br>5.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Typically it won=92t=
 be necessary to enclose a file with the=20
ticket=2C but if you need to=2C select =93I have files to attach to this=20
ticket=94. <br>
<br>6.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you want to previ=
ew your Issue=2C click on the =93Preview=94=20
button.&nbsp=3B When you=92re ready to submit the issue=2C click on the =93=
Create=20
Ticket=94 button. <br>
<br>7.&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you want to updat=
e an issue=2C go to the "View Tickets" page: <a rel=3D"nofollow" href=3D"ht=
tp://trac.tools.ietf.org/wg/radext/trac/report/1">http://trac.tools.ietf.or=
g/wg/radext/trac/report/1</a>&nbsp=3B
 Click on the ticket # you want to update=2C and then modify the ticket=20
fields as required. <br><br>
That=92s it!&nbsp=3B <br><br>
If you encounter problems with TRAC=2C send email to me and I=92ll try to=20
figure out what=92s going on. <br><br>
Happy TRACing=2C<br>
Bernard 		 	   		  </body>
</html>=

--_173f1fb3-7506-40f6-a833-e6ee1bc0c714_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 08 Jun 2010 14:20:19 +0000
Message-ID: <BLU137-W232034863E4B79D0A9666093D60@phx.gbl>
Content-Type: multipart/alternative; boundary="_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Last Look at RADIUS Design Guidelines
Date: Tue, 8 Jun 2010 07:19:27 -0700
MIME-Version: 1.0

--_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


This is announcing a "last look" at the RADIUS Design Guidelines document=
=2C prior to its being approval by the IETF for publication as a Best Curre=
nt Practice (BCP).=20

The document is available for inspection here:
http://tools.ietf.org/id/draft-ietf-radext-design

The "last look" will last until June 28=2C 2010.  Comments may be submitted=
 in any of the following ways:

a. Submission via the RADEXT TRAC system: http://trac.tools.ietf.org/wg/rad=
ext/trac/newticket

b. Comments sent to the RADEXT WG mailing list (radiusext@ops.ietf.org).=20
 		 	   		  =

--_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
This is announcing a "last look" at the RADIUS Design Guidelines document=
=2C prior to its being approval by the IETF for publication as a Best Curre=
nt Practice (BCP). <br><br>The document is available for inspection here:<b=
r>http://tools.ietf.org/id/draft-ietf-radext-design<br><br>The "last look" =
will last until June 28=2C 2010.&nbsp=3B Comments may be submitted in any o=
f the following ways:<br><br>a. Submission via the RADEXT TRAC system: http=
://trac.tools.ietf.org/wg/radext/trac/newticket<br><br>b. Comments sent to =
the RADEXT WG mailing list (radiusext@ops.ietf.org). <br> 		 	   		  </body=
>
</html>=

--_47e2b510-23cb-44ed-b6e6-08958d0b9ccd_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 07 Jun 2010 17:50:39 +0000
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>,  radext mailing list <radiusext@ops.ietf.org>,  radext chair <radext-chairs@tools.ietf.org>
Subject: Document Action: 'Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol' to Informational RFC
Message-Id: <20100607174935.0066D3A6988@core3.amsl.com>
Date: Mon,  7 Jun 2010 10:49:34 -0700 (PDT)

The IESG has approved the following document:

- 'Use of Status-Server Packets in the Remote Authentication Dial In User 
   Service (RADIUS) Protocol '
   <draft-ietf-radext-status-server-09.txt> as an Informational RFC


This document is the product of the RADIUS EXTensions Working Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-status-server-09.txt

Technical Summary

This document specifies a deployed extenion to RADIUS which enables
clients to query the status of a RADIUS server.  While the
Status-Server Code (12) was defined as experimental in RFC 2865
Section 3, details of the protocol's operation have not been
documented until now.  

Working Group Summary

This document has completed RADEXT WG last call, with the primary
areas of discussion relating to security and ID field usage. 

The RADEXT WG elected to recommend this document for publication
as an Informational RFC rather than as a standards-Track RFC due
to concerns about problems with deployed implementations.  The
fixes recommended within the document are compatible with
existing servers that receive Status-Server packets, but impose new
security requirements on clients that send Status-Server packets.

Document Quality

The document has been reviewed by IETF RADEXT WG members. 
An expert review has been carried out by Ignacio Goyret. 

Status-Server has been implemented by multiple vendors, 
including RADIATOR, FreeRADIUS and Cistron.  It is currently
in use within EDUROAM, an educational roaming consortium
with more than one million users worldwide.  As
a result, the document reflects operational experience.

Personnel

Bernard Aboba is the document shepherd for this document. 
Dan Romascanu is the responsible AD.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 07 Jun 2010 11:30:42 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-design-14.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100607113012.B64A428C9C7@core3.amsl.com>
Date: Mon,  7 Jun 2010 04:30:02 -0700 (PDT)

--NextPart

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 Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-14.txt
	Pages           : 40
	Date            : 2010-06-07

This document provides guidelines for the design of attributes used
by the Remote Authentication Dial In User Service (RADIUS) protocol.
It is expected that these guidelines will prove useful to authors and
reviewers of future RADIUS attribute specifications, both within the
IETF as well as other Standards Development Organizations (SDOs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-radext-design-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2010-06-07042913.I-D@ietf.org>

--NextPart--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 07 Jun 2010 11:30:27 +0000
Message-ID: <4C0CD816.6060809@deployingradius.com>
Date: Mon, 07 Jun 2010 13:29:26 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Updated copy of the design guidelines document
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

  I've submitted a new version of the design guidelines document, based
on recent feedback.

  The changes are:

- clarify "TLV encoding" versus "data format" as per Avi's review

  This required a series of minor changes throughout the document.

- add Dave Nelson's overview of the different attributes to
  the "introduction" section.

  This required significant re-writes of that section.

- Added Bernard's suggested text from
  http://ops.ietf.org/lists/radiusext/2010/msg00277.html

  As the introduction section had been re-written, the text
  was no longer appropriate for that section.  Instead, it was
  added to Section 3.3.3.

- added Terminology of "standard space" and "vendor space"

  We may want to add terminology of "TLV encoding" and "data format".

- audited the document for consistency

- changed a few "... needs to..." into SHOULD.  The "needs to" text
  is ambiguous, in that it makes suggestions without using RFC2119 text.

- Added Section A.1.4 allowing data types from Appendix B.  The existing
  text in Section A.2 allowed this, so making it explicit in A.1 is
  a good idea.


  Please review the updated Introduction, as it has changed a lot.

 Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 06 Jun 2010 21:05:44 +0000
Date: Sun, 6 Jun 2010 14:04:39 -0700 (Pacific Daylight Time)
From: Peter Deacon <peterd@iea-software.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
cc: 'Alper Yegin' <alper.yegin@yegin.org>, tena@huawei.com,  aaa-doctors@ietf.org, radiusext@ops.ietf.org, dime@ietf.org,  dromasca@avaya.com
Subject: RE: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
Message-ID: <alpine.WNT.2.00.1006061319410.1732@SMURF>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Sun, 6 Jun 2010, Bernard Aboba wrote:

> Previous tests have shown problems with use of RADIUS/EAP over UDP in
> federated scenarios:

> http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentication-over-jammed-
> network/

> As noted in the above paper, once packet loss is introduced, completing the
> multiple roundtrips of EAP authentication becomes increasingly difficult.

This paper has some crazy figures.. look at the data for packet loss.

40% packet loss (client to server) = 78% success rate for PEAP-MSCHAPv2
40% packet loss (server to client) = 20% success rate for PEAP-MSCHAPv2

There is a footnote on this issue "The more favorable results for 
client-to-server jamming are caused by the aggressive packet re-sending 
strategy of wpa_supplicant compared to the behavior of Radiator."

If the server did not receive client request or client did not receive 
server response the knowledge available and avenue for response by the 
client is the same in either case.  The figures appear to reflect a 
substantial implementation artifact in the servers tx side retransmit.

regards,
Peter

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 06 Jun 2010 16:14:31 +0000
Message-ID: <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alper Yegin'" <alper.yegin@yegin.org>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
Subject: RE: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
Date: Sun, 6 Jun 2010 09:13:19 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CB0558.818885A0"
Thread-Index: AcsC3Vu3xwQsiPtKT8+vfB1gbF+XiAA2UOhgAHbjbHA=
Content-Language: en-us

------=_NextPart_000_001C_01CB0558.818885A0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Previous tests have shown problems with use of RADIUS/EAP over UDP in
federated scenarios:

http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentication-over-jammed-
network/

 

As noted in the above paper, once packet loss is introduced, completing the
multiple roundtrips of EAP authentication becomes increasingly difficult. 

 

RADIUS over TCP holds up much better until a threshold is reached, and then
authentication success fractions fall dramatically.   

 

Due to the transport issues and RADIUS packet size limitation of 4096 (which
may impact the ability to transport SAML assertions), it seems like Diameter
would be more suitable.  

 

 

 

 

From: aaa-doctors-bounces@ietf.org [mailto:aaa-doctors-bounces@ietf.org] On
Behalf Of Alper Yegin
Sent: Friday, June 04, 2010 12:31 AM
To: 'Bernard Aboba'; tena@huawei.com; aaa-doctors@ietf.org;
radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request

 


In particular, the problems of EAP auth (e.g. multiple round-trips, general
fragility in federated uses) become highly toxic when applied to Realtime
applications such as XMPP and SIP.  As we have learned, Digest auth (RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.  For users of real-time
applications, additional latency is a basic, non-negotiable goal.  If the
relatively modest number of exchanges implied by RFC 5090 were intolerable
in realtime applications,  how can we expect EAP exchanges (which can
involve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The
answer unfortunately, is that there is no chance at all.  

So in summary, I believe that some aspects of the problem statement make
sense, but that a solution has been chosen prematurely.  The right way to
move forward in a situation like this is to begin with a problem statement,
which should include carefully validating the uses cases.  

 

 

Alper> I agree. 

 

Alper> Anyone who was around the ICOS BoF in IETF 62 would remember that the
community was convinced(!) that using EAP for anything other than network
access was a no-no. Now before we embark on marching in  180-degree opposite
direction, I'd say the community needs to be "unconvinced" first. I'm not
saying this is not doable, but something we need to go through first.

 

Alper

 

 

  

> ----- Original Message ----- 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
> <aaa-doctors@ietf.org>
> Sent: Wednesday, June 02, 2010 10:56 PM
> Subject: FEDAUTH BOF request
> 
> 
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
> 
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/, and more information about
> this BOF or other BOF requests can be examined at
> http://trac.tools.ietf.org/bof/trac/
> 
> Dan
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> 
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


------=_NextPart_000_001C_01CB0558.818885A0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Previous tests have shown problems with use of RADIUS/EAP =
over
UDP in federated scenarios:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentic=
ation-over-jammed-network/<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As noted in the above paper, once packet loss is =
introduced, completing
the multiple roundtrips of EAP authentication becomes increasingly =
difficult. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>RADIUS over TCP holds up much better until a threshold is
reached, and then authentication success fractions fall dramatically. =
&nbsp;&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Due to the transport issues and RADIUS packet size =
limitation of
4096 (which may impact the ability to transport SAML assertions), it =
seems like
Diameter would be more suitable. &nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
aaa-doctors-bounces@ietf.org [mailto:aaa-doctors-bounces@ietf.org] <b>On =
Behalf
Of </b>Alper Yegin<br>
<b>Sent:</b> Friday, June 04, 2010 12:31 AM<br>
<b>To:</b> 'Bernard Aboba'; tena@huawei.com; aaa-doctors@ietf.org;
radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com<br>
<b>Subject:</b> Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF =
request<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
In particular, the problems of EAP auth (e.g. multiple round-trips, =
general
fragility in federated uses) become highly toxic when applied to =
Realtime
applications such as XMPP and SIP.&nbsp; As we have learned, Digest auth =
(RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.&nbsp; For users of real-time
applications, additional latency is a basic, non-negotiable goal.&nbsp; =
If the
relatively modest number of exchanges implied by RFC 5090 were =
intolerable in
realtime applications,&nbsp; how can we expect EAP exchanges (which can =
involve
4-5 times the number of roundtrips of RFC 5090) to be deployed?&nbsp; =
The
answer unfortunately, is that there is no chance at all.&nbsp; <br>
<br>
So in summary, I believe that some aspects of the problem statement make =
sense,
but that a solution has been chosen prematurely.&nbsp; The right way to =
move
forward in a situation like this is to begin with a problem statement, =
which
should include carefully validating the uses cases.&nbsp; <span
style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; I agree. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; Anyone who was around the ICOS BoF in IETF 62 =
would
remember that the community was convinced(!) that using EAP for anything =
other
than network access was a no-no. Now before we embark on marching in
&nbsp;180-degree opposite direction, I&#8217;d say the community needs =
to be
&#8220;unconvinced&#8221; first. I&#8217;m not saying this is not =
doable, but
something we need to go through first.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>&nbsp;
<br>
<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;Romascanu, Dan (Dan)&quot; =
&lt;dromasca@avaya.com&gt;<br>
&gt; To: &lt;dime@ietf.org&gt;; &quot;radext mailing list&quot;
&lt;radiusext@ops.ietf.org&gt;; <br>
&gt; &lt;aaa-doctors@ietf.org&gt;<br>
&gt; Sent: Wednesday, June 02, 2010 10:56 PM<br>
&gt; Subject: FEDAUTH BOF request<br>
&gt; <br>
&gt; <br>
&gt; Diameter and RADIUS experts should pay attention to the request to =
hold<br>
&gt; a Federated Authentication (FEDAUTH) BOF which will be discussed =
this<br>
&gt; morning by the IAB and the IESG.<br>
&gt; <br>
&gt; The Draft Charter is available at<br>
&gt; http://www.project-moonshot.org/bof/charter/, and more information =
about<br>
&gt; this BOF or other BOF requests can be examined at<br>
&gt; http://trac.tools.ietf.org/bof/trac/<br>
&gt; <br>
&gt; Dan<br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: =
&lt;http://psg.com/lists/radiusext/&gt;<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_001C_01CB0558.818885A0--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 05 Jun 2010 06:11:01 +0000
Message-ID: <4C09EA57.6000509@deployingradius.com>
Date: Sat, 05 Jun 2010 08:10:31 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> In the context of this document and in the context of the specific section I was commenting on --  i think it is darn clear what we mean by compatible or incompatible.

  Given the level of miscommunication, I don't want to make assumptions
about anything.

> No i don't assert the opposite.  I am saying the document allows for SDOs to create incompatible specifications.

  I see no ethical or procedural way for the document to forbid that
practice.

>  To repeat what I said with appropriate words highlighted:  "the document asserts SDOs DONT HAVE TO BE COMPATIBLE." 

  Again, no.  I really can't agree with that statement.

> back to the original issue - that is issue 6:
> 
> Issue 6: Section 3.2
> 
> " These approaches are often incompatible, leading to
>   additional complexity in RADIUS implementations."
> 
> Just say "These approaches often lead to additional complexity in RADIUS implementations."
> 
> I dont see the need to bring incompatibility statement into this paragraph.

  Because it directly contradicts your assertion that the document
states "SDOs don't have to be compatible".

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 05 Jun 2010 05:25:59 +0000
Message-ID: <4C09DFA6.7080505@deployingradius.com>
Date: Sat, 05 Jun 2010 07:24:54 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, tena@huawei.com,  aaa-doctors@ietf.org, radiusext@ops.ietf.org, dime@ietf.org,  dromasca@avaya.com
Subject: Re: [Dime] FEDAUTH BOF request
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Joseph Salowey (jsalowey) wrote:
> I agree with a lot of what Bernard says below. For better or for worse
> EAP is closely associated with AAA.  The fit may be odd in some cases,
> but deployments have found success in making it work.  This is why it is
> attractive.  I don't think that replacing EAP in AAA with some other
> framework, such as GSSAPI, is going to lead to better results.

  I think the proposal is to use GSS "locally", and AAA "globally".
i.e. the SSH client/server would use EAP over GSS.  But the SSH server
would hand that in turn to a GSS to AAA gateway.  That would strip EAP
out of GSS, and put it into RADIUS for global roaming.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 17:12:23 +0000
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Dime] FEDAUTH BOF request
Date: Fri, 4 Jun 2010 10:11:22 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE50A9EDD7D@xmb-sjc-225.amer.cisco.com>
Thread-Topic: [Dime] FEDAUTH BOF request
Thread-Index: AcsC3V6qlMZy6lk0TKacZwhNYrbcbgBJ7grw
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>

I agree with a lot of what Bernard says below. For better or for worse
EAP is closely associated with AAA.  The fit may be odd in some cases,
but deployments have found success in making it work.  This is why it is
attractive.  I don't think that replacing EAP in AAA with some other
framework, such as GSSAPI, is going to lead to better results.  It is
true that along the way modifications, such as RADSEC, have been
deployed to make things work better.   It is risky to assume that AAA
and EAP can be successfully applied to any arbitrary scenario without a
firm grip on the use cases.  If at the end of the design you end up with
something that is called EAP and AAA, but actually is completely
different you will lose the perceived advantage of building on top of
existing AAA and EAP infrastructure

I'm not as convinced as Bernard that it can't work, but I think there
needs to be a firm understanding of the use cases to determine what is
required to deliver a solution and what changes may be necessary. =20



> -----Original Message-----
> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf
Of
> Bernard Aboba
> Sent: Wednesday, June 02, 2010 10:26 PM
> To: tena@huawei.com; aaa-doctors@ietf.org; radiusext@ops.ietf.org;
> dime@ietf.org; dromasca@avaya.com
> Subject: Re: [Dime] FEDAUTH BOF request
>=20
> Let me provide a bit of  context about what I think the problem is
here.
>=20
> As noted by Sam in a previous conversation, the basic use case is
"cloud
> services", where an education institution or enterprise is making use
of
> hosted services.  In these situations, the institution may not just
want
> the service provider to host an application, but may want to keep
their
> credentials local, rather than hosting this in the cloud as well.
>=20
> In the original Moonshot investigation, Kerberos was considered as a
> potential solution.  However, while Kerberos is well understood from a
> security point of view, and could relatively easily be modified to
support
> EAP-based pre-auth (numerous proposals for this have been advanced and
in
> some cases implemented)  Kerberos federation has not been widely
deployed.
>=20
> One of the basic problems with putting a KDC on the Internet is that
there
> is no easy way to protect it, since both clients and other KDCs may
need
> to send packets to and from the KDC.  For this reason if there are
roaming
> clients there is no easy way to filter traffic to/from the KDC.  In
> addition, the Kerberos protocol is vulnerable to passive attacks in
the
> absence of extensions such as PKINIT or Kerberos Hardening.
>=20
> In contrast, the AAA roaming model has been widely deployed, in part
> because it is much easier to protect a AAA server.  AAA servers only
talk
> to AAA clients, not to users directly.  This means that it is
typically
> possible to filter traffic to the AAA server so that only packets
> originating from legitimate AAA clients can be sent to/from the AAA
> server.
>=20
> In addition to these basic security issues, the AAA delegation model
is
> much simpler than Kerberos.  Obtaining a Kerberos TGT for a local
realm
> involves first obtaining a TGT from a "home" realm and then requesting
a
> TGT for the local realm.  This involves multiple exchanges, and as
noted
> earlier requires both the local KDC and the home KDC to be available
over
> the Internet.  In contrast, a AAA client implicitly delegates
authority to
> the AAA server for the Accept/Reject decision, so that explicit trust
> relationships don't need to be configured.  As long as the AAA client
can
> reach the AAA server via a chain of proxies the trust relationship can
> succeed.
>=20
> Given these basic characteristics of Kerberos and AAA delegation, the
> Moonshot team has decided that a AAA-based approach to delegation is
more
> likely to be widely deployed than a Kerberos-based one.  My take on
this
> is that this assessment is probably realistic.
>=20
> Where I get lost is making the leap between the AAA delegation model
and
> use of EAP.  As we saw with Digest authentication (RFC 5090), it is
> possible to extend AAA to support application-layer authentication
without
> use of EAP.  For example, using AAA to carry GSS-API payloads would
not
> require much more than defining a GSS-Message attribute.  EAP has no
> unique properties that make it more suitable for use with AAA.  In
fact, I
> would argue that the fit between EAP and AAA has always been tenuous
at
> best -- witness the issues encountered in federated EAP authentication
> that RADSEC has been needed to address.
>=20
> In particular, the problems of EAP auth (e.g. multiple round-trips,
> general fragility in federated uses) become highly toxic when applied
to
> Realtime applications such as XMPP and SIP.  As we have learned,
Digest
> auth (RFC 5090) has not been widely deployed, in part because of
concern
> about the additional latency added by a AAA exchange.  For users of
real-
> time applications, additional latency is a basic, non-negotiable goal.
If
> the relatively modest number of exchanges implied by RFC 5090 were
> intolerable in realtime applications,  how can we expect EAP exchanges
> (which can involve 4-5 times the number of roundtrips of RFC 5090) to
be
> deployed?  The answer unfortunately, is that there is no chance at
all.
>=20
[Joe]=20
> So in summary, I believe that some aspects of the problem statement
make
> sense, but that a solution has been chosen prematurely.  The right way
to
> move forward in a situation like this is to begin with a problem
> statement, which should include carefully validating the uses cases.
>=20
>=20
> > ----- Original Message -----
> > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> > To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>;
> > <aaa-doctors@ietf.org>
> > Sent: Wednesday, June 02, 2010 10:56 PM
> > Subject: FEDAUTH BOF request
> >
> >
> > Diameter and RADIUS experts should pay attention to the request to
> > hold a Federated Authentication (FEDAUTH) BOF which will be
discussed
> > this morning by the IAB and the IESG.
> >
> > The Draft Charter is available at
> > http://www.project-moonshot.org/bof/charter/, and more information
> > about this BOF or other BOF requests can be examined at
> > http://trac.tools.ietf.org/bof/trac/
> >
> > Dan
> >
> > --
> > to unsubscribe send a message to radiusext-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://psg.com/lists/radiusext/>
> >
> >
> >
> > --
> > to unsubscribe send a message to radiusext-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://psg.com/lists/radiusext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 13:39:06 +0000
Cc: radext mailing list <radiusext@ops.ietf.org>
Message-Id: <B3EB5ED4-2210-4879-A34A-1CC083D69D69@elbrysnetworks.com>
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: Alan DeKok <aland@deployingradius.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Date: Fri, 4 Jun 2010 09:38:45 -0400

On Jun 4, 2010, at 3:15 AM, Alan DeKok wrote:

 > If it's all right, I'll wordsmith that and put it into the  
introduction.

Of course.  Anything to help move this document along.




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 13:29:09 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Fri, 4 Jun 2010 09:26:54 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsD6cQOQ/rtT0gFQuqV9prjEx5xwg==
Message-ID: <C8AFF4BF-0046-464C-BE14-1C0805E639B0@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 04-06-2010, at 01:07 , Alan DeKok wrote:

> Avi Lior wrote:
>> Section 1.3 ....
>>=20
>> While SDOs and vendors MAY choose to create specifications not
>>   following these guidelines, this should be done only when those
>>   specifications are intended for use in scenarios within a limited
>>   scope of applicability.  Where general usage is possible, adhering to
>>   these guidelines is RECOMMENDED.
>>=20
>> Unless i am missing something  -- the above states that they dont have t=
o be compatible.
>=20
>  No, it does not.  The word "compatible" does not appear in that text.
> I have no idea what you mean by "compatible".  That word could mean
> almost anything.
>=20
>  Two SDOs may choose to ignore the guidelines, but may still both be
> "compatible", or they may not be "compatible".  The document does not
> distinguish between those two scenarios.

In the context of this document and in the context of the specific section =
I was commenting on --  i think it is darn clear what we mean by compatible=
 or incompatible.

In any case....

>  The document suggests that incompatibility is a problem to be avoided.
> You assert that the document says the exact opposite.
>=20
>  I repeat my objection: No, it doesn't.

No i don't assert the opposite.  I am saying the document allows for SDOs t=
o create incompatible specifications.  To repeat what I said with appropria=
te words highlighted:  "the document asserts SDOs DONT HAVE TO BE COMPATIBL=
E."=20

back to the original issue - that is issue 6:

Issue 6: Section 3.2

" These approaches are often incompatible, leading to
  additional complexity in RADIUS implementations."

Just say "These approaches often lead to additional complexity in RADIUS im=
plementations."

I dont see the need to bring incompatibility statement into this paragraph.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 07:32:13 +0000
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Bernard Aboba'" <bernard_aboba@hotmail.com>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
Subject: RE: [Dime] FEDAUTH BOF request
Date: Fri, 4 Jun 2010 10:30:58 +0300
Message-ID: <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A0_01CB03D1.0B8D02F0"
Thread-Index: AcsC3Vu3xwQsiPtKT8+vfB1gbF+XiAA2UOhg
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_01A0_01CB03D1.0B8D02F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


In particular, the problems of EAP auth (e.g. multiple round-trips, general
fragility in federated uses) become highly toxic when applied to Realtime
applications such as XMPP and SIP.  As we have learned, Digest auth (RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.  For users of real-time
applications, additional latency is a basic, non-negotiable goal.  If the
relatively modest number of exchanges implied by RFC 5090 were intolerable
in realtime applications,  how can we expect EAP exchanges (which can
involve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The
answer unfortunately, is that there is no chance at all.  

So in summary, I believe that some aspects of the problem statement make
sense, but that a solution has been chosen prematurely.  The right way to
move forward in a situation like this is to begin with a problem statement,
which should include carefully validating the uses cases.  



 

 

Alper> I agree. 

 

Alper> Anyone who was around the ICOS BoF in IETF 62 would remember that the
community was convinced(!) that using EAP for anything other than network
access was a no-no. Now before we embark on marching in  180-degree opposite
direction, I'd say the community needs to be "unconvinced" first. I'm not
saying this is not doable, but something we need to go through first.

 

Alper

 

 

  

> ----- Original Message ----- 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
> <aaa-doctors@ietf.org>
> Sent: Wednesday, June 02, 2010 10:56 PM
> Subject: FEDAUTH BOF request
> 
> 
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
> 
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/, and more information about
> this BOF or other BOF requests can be examined at
> http://trac.tools.ietf.org/bof/trac/
> 
> Dan
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> 
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


------=_NextPart_000_01A0_01CB03D1.0B8D02F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
In particular, the problems of EAP auth (e.g. multiple round-trips, =
general
fragility in federated uses) become highly toxic when applied to =
Realtime
applications such as XMPP and SIP.&nbsp; As we have learned, Digest auth =
(RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.&nbsp; For users of real-time
applications, additional latency is a basic, non-negotiable goal.&nbsp; =
If the
relatively modest number of exchanges implied by RFC 5090 were =
intolerable in
realtime applications,&nbsp; how can we expect EAP exchanges (which can =
involve
4-5 times the number of roundtrips of RFC 5090) to be deployed?&nbsp; =
The
answer unfortunately, is that there is no chance at all.&nbsp; <br>
<br>
So in summary, I believe that some aspects of the problem statement make =
sense,
but that a solution has been chosen prematurely.&nbsp; The right way to =
move
forward in a situation like this is to begin with a problem statement, =
which
should include carefully validating the uses cases.&nbsp; <br>
<br>
<span style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; I agree. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; Anyone who was around the ICOS BoF in IETF 62 =
would
remember that the community was convinced(!) that using EAP for anything =
other
than network access was a no-no. Now before we embark on marching in =
&nbsp;180-degree
opposite direction, I&#8217;d say the community needs to be =
&#8220;unconvinced&#8221;
first. I&#8217;m not saying this is not doable, but something we need to =
go
through first.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>&nbsp;
<br>
<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;Romascanu, Dan (Dan)&quot; =
&lt;dromasca@avaya.com&gt;<br>
&gt; To: &lt;dime@ietf.org&gt;; &quot;radext mailing list&quot;
&lt;radiusext@ops.ietf.org&gt;; <br>
&gt; &lt;aaa-doctors@ietf.org&gt;<br>
&gt; Sent: Wednesday, June 02, 2010 10:56 PM<br>
&gt; Subject: FEDAUTH BOF request<br>
&gt; <br>
&gt; <br>
&gt; Diameter and RADIUS experts should pay attention to the request to =
hold<br>
&gt; a Federated Authentication (FEDAUTH) BOF which will be discussed =
this<br>
&gt; morning by the IAB and the IESG.<br>
&gt; <br>
&gt; The Draft Charter is available at<br>
&gt; http://www.project-moonshot.org/bof/charter/, and more information =
about<br>
&gt; this BOF or other BOF requests can be examined at<br>
&gt; http://trac.tools.ietf.org/bof/trac/<br>
&gt; <br>
&gt; Dan<br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: =
&lt;http://psg.com/lists/radiusext/&gt;<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_01A0_01CB03D1.0B8D02F0--



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 07:16:23 +0000
Message-ID: <4C08A807.3000509@deployingradius.com>
Date: Fri, 04 Jun 2010 09:15:19 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: radext mailing list <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David B. Nelson wrote:
> My thinking on the applicability of design guidelines has always been
> pretty simple.

  While I agree, discussion shows that isn't a uniformly held opinion.

> Within the scope of RADIUS Attribute design and compatibility, I think
> there are three levels:

  If it's all right, I'll wordsmith that and put it into the introduction.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 05:08:08 +0000
Message-ID: <4C0889FD.1010703@deployingradius.com>
Date: Fri, 04 Jun 2010 07:07:09 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> Section 1.3 ....
> 
>  While SDOs and vendors MAY choose to create specifications not
>    following these guidelines, this should be done only when those
>    specifications are intended for use in scenarios within a limited
>    scope of applicability.  Where general usage is possible, adhering to
>    these guidelines is RECOMMENDED.
> 
> Unless i am missing something  -- the above states that they dont have to be compatible.

  No, it does not.  The word "compatible" does not appear in that text.
 I have no idea what you mean by "compatible".  That word could mean
almost anything.

  Two SDOs may choose to ignore the guidelines, but may still both be
"compatible", or they may not be "compatible".  The document does not
distinguish between those two scenarios.

>>... the document asserts SDOs dont have to be compatible
>>       with other SDOs.

  The only usage of "compatible" in the document is via the word
"incompatible", as in:

	... different groups taking different approaches.
	These approaches are often incompatible, leading to
	additional complexity

  The document suggests that incompatibility is a problem to be avoided.
 You assert that the document says the exact opposite.

  I repeat my objection: No, it doesn't.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 04 Jun 2010 02:57:20 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 22:56:17 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDkYDaxxjjrOmcRSyigdxKL8mwYA==
Message-ID: <DDD4FA4C-B08E-43AD-9A11-38B0B38C43DB@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Read this:

Section 1.3 ....

 While SDOs and vendors MAY choose to create specifications not
   following these guidelines, this should be done only when those
   specifications are intended for use in scenarios within a limited
   scope of applicability.  Where general usage is possible, adhering to
   these guidelines is RECOMMENDED.

Unless i am missing something  -- the above states that they dont have to b=
e compatible.



On 03-06-2010, at 16:00 , Alan DeKok wrote:

> Avi Lior wrote:
>> With which do you disagree when you say "No, it does not."
>=20
>  It's a rather straightforward reading of the message:
>=20
> You: ... the document asserts SDOs dont have to be compatible
>       with other SDOs.
>=20
> Me:  No, it does not.
>=20
>  Alan DeKok.

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 20:53:48 +0000
Message-Id: <5D6B078F-C7EC-4646-AEF8-F86D1582075C@elbrysnetworks.com>
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: radext mailing list <radiusext@ops.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Date: Thu, 3 Jun 2010 16:53:23 -0400

My thinking on the applicability of design guidelines has always been  
pretty simple.  It starts with the premise that any Standards  
Development Organization (SDO) is in the business of defining  
interoperable standards.  If we can't all agree that this is a truism,  
we have deeper problems.  Within that framework, the notion that what  
one SDO does will never impact any other SDO or the Internet Community  
at large is questionable.  It may be true sometimes, but I don't  
believe it's universally true.

Within the scope of RADIUS Attribute design and compatibility, I think  
there are three levels:

(1)  Attributes that are of interest to a single vendor, e.g., for a  
single product line.  No cross-vendor interoperability is needed.

We use Vendor-Specific Attributes for these cases.  The rules are  
pretty lax.  Code-point allocation is managed by the vendor with the  
number space defined by their Private Enterprise Number (PEN).


(2) Attributes that are  of interest to an industry segment and a  
single SDO that serves that industry.  WiMAX is one example.  Multi- 
vendor interoperability within an industry segment is expected.

We use SDO-Specific Attributes (SSA) for these cases, which are VSAs  
in terms of format and code-point allocation, using a PEN assigned to  
the SDO rather than one assigned to an individual vendor.  The rules  
are more stringent.  Compliance with the design guidelines is strongly  
encouraged, but review by outside agencies (the IETF, AAA Doctors,  
etc.) is purely optional.


(3)  Attributes that are of broad interest to the Internet Community.   
Global Internet multi-vendor interoperability is expected.

We use Standard Attributes for these cases, with code-point allocation  
via IANA, subject to the appropriate IETF review and consensus.   
Strict conformance with the design guidelines is expected, unless a  
good case can be made for an exception, and those tasked with  
reviewing the proposals will almost certainly use the design  
guidelines as a review checklist.






--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 20:01:29 +0000
Message-ID: <4C0809E7.2050103@deployingradius.com>
Date: Thu, 03 Jun 2010 22:00:39 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> With which do you disagree when you say "No, it does not."

  It's a rather straightforward reading of the message:

You: ... the document asserts SDOs dont have to be compatible
       with other SDOs.

Me:  No, it does not.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 17:54:52 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 13:52:10 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDRX1uXyb1FZE9TTGWUIOYHSSH5A==
Message-ID: <0089109D-5260-482B-B65B-DD7EF94A4076@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

With which do you disagree when you say "No, it does not."
a) The above states that the approach taken by SDOs when working on their a=
ttributes was incompatible.
b) but as the document asserts SDOs dont have to be compatible with other S=
DOs.
c) Both of these statements

???


On 03-06-2010, at 08:52 , Alan DeKok wrote:

>>>> " These approaches are often incompatible, leading to
>>>>  additional complexity in RADIUS implementations."
>>=20
>> The above states that the approach taken by SDOs when working on their a=
ttributes was incompatible - but as the document asserts SDOs dont have to =
be compatible with other SDOs.
>=20
>  No, it does not.
>=20
>  Alan DeKok.

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 13:58:18 +0000
Date: Thu, 03 Jun 2010 21:57:56 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: [Dime] FEDAUTH BOF request
To: dromasca@avaya.com, dime@ietf.org, radiusext@ops.ietf.org, aaa-doctors@ietf.org, Wolfgang.Steigerwald@telekom.de, "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Message-id: <87BAC297AD614E1E8E885DA28CA60DD2@china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1; reply-type=original
Content-transfer-encoding: 8BIT

Hi Wolfgang and Hannes,
You are also right from the good nature of Diameter.
I just mentioned one possible interesting point in my previous email 
replying to Bernard et al.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message ----- 
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: <Wolfgang.Steigerwald@telekom.de>; <tena@huawei.com>; 
<aaa-doctors@ietf.org>; <radiusext@ops.ietf.org>; <dime@ietf.org>; 
<dromasca@avaya.com>
Sent: Thursday, June 03, 2010 3:18 PM
Subject: RE: [Dime] FEDAUTH BOF request


Looking forward to hear that answer as well :-)

>-----Original Message-----
>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On
>Behalf Of ext Wolfgang.Steigerwald@telekom.de
>Sent: 03 June, 2010 10:16
>To: tena@huawei.com; aaa-doctors@ietf.org;
>radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
>Subject: Re: [Dime] FEDAUTH BOF request
>
>Hello Tina,
>
>what assumption let you think RADIUS is more suitable then
>DIAMETER? DIAMETER is much more developed, is a peer to peer
>protocol, designed to transport also structured data, not as
>limited on payload and therefore much better suitable for the
>purpose of IdM.
>
>Best Regards
>
> Wolfgang
>
>-----Ursprüngliche Nachricht-----
>Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im
>Auftrag von Tina TSOU
>Gesendet: Donnerstag, 3. Juni 2010 06:03
>An: aaa-doctors@ietf.org; radext mailing list; dime@ietf.org;
>Romascanu, Dan (Dan)
>Betreff: Re: [Dime] FEDAUTH BOF request
>
>Comments are below.
>1. This might be of interest to ngHLR (Unified Subscriber
>Center) kind of solutions who provide Identity Management
>services 2. From protocol side, I think it may be more
>interesting for RADIUS as I doubt the suitability of Diameter for this.
>
>B. R.
>Tina
>http://tinatsou.weebly.com/contact.html
>
>----- Original Message -----
>From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>To: <dime@ietf.org>; "radext mailing list"
><radiusext@ops.ietf.org>; <aaa-doctors@ietf.org>
>Sent: Wednesday, June 02, 2010 10:56 PM
>Subject: FEDAUTH BOF request
>
>
>Diameter and RADIUS experts should pay attention to the
>request to hold a Federated Authentication (FEDAUTH) BOF which
>will be discussed this morning by the IAB and the IESG.
>
>The Draft Charter is available at
>http://www.project-moonshot.org/bof/charter/, and more
>information about this BOF or other BOF requests can be
>examined  at http://trac.tools.ietf.org/bof/trac/
>
>Dan
>
>--
>to unsubscribe send a message to
>radiusext-request@ops.ietf.org with the word 'unsubscribe' in
>a single line as the message text body.
>archive: <http://psg.com/lists/radiusext/>
>
>
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 13:55:13 +0000
Date: Thu, 03 Jun 2010 21:54:28 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: FEDAUTH BOF request
To: dromasca@avaya.com, dime@ietf.org, radiusext@ops.ietf.org, aaa-doctors@ietf.org, Bernard Aboba <bernard_aboba@hotmail.com>
Message-id: <A142425E33AB431C8F6FBF8C10E4594B@china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)"

This is a multi-part message in MIME format.

--Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi Bernard,
Comments are in line.

B. R.
Tina
http://tinatsou.weebly.com/contact.html
  ----- Original Message ----- 
  From: Bernard Aboba 
  To: tena@huawei.com ; aaa-doctors@ietf.org ; radiusext@ops.ietf.org ; dime@ietf.org ; dromasca@avaya.com 
  Sent: Thursday, June 03, 2010 1:03 PM
  Subject: RE: FEDAUTH BOF request


  Tina said: 

  > Comments are below.
  > 1. This might be of interest to ngHLR (Unified Subscriber Center) kind of 
  > solutions who provide Identity Management services
  > 2. From protocol side, I think it may be more interesting for RADIUS as I  doubt the suitability of Diameter for this.

  Not sure why RADIUS would be more suitable than Diameter for carrying large payloads such as SAML assertions.  The 4096 octet RADIUS PDU limit is not transport-specific -- that is, transporting the RADIUS payload over TCP does not solve the problem. 

  [Tina: You are also right from the aspect you raised.
  Diameter roaming model is well established (in use cases like WLAN-3GPP interworking) without the use of EAP or SAML. I fail to see what would be the benefits of using EAP or SAML with Diameter which the current roaming model does not already have.
  Everything has pros and cons, as you said in another email, let's begin with a problem statement, and then protocols.]


   
  > ----- Original Message ----- 
  > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
  > To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
  > <aaa-doctors@ietf.org>
  > Sent: Wednesday, June 02, 2010 10:56 PM
  > Subject: FEDAUTH BOF request
  > 
  > 
  > Diameter and RADIUS experts should pay attention to the request to hold
  > a Federated Authentication (FEDAUTH) BOF which will be discussed this
  > morning by the IAB and the IESG.
  > 
  > The Draft Charter is available at
  > http://www.project-moonshot.org/bof/charter/, and more information about
  > this BOF or other BOF requests can be examined at
  > http://trac.tools.ietf.org/bof/trac/
  > 
  > Dan
  > 
  > --
  > to unsubscribe send a message to radiusext-request@ops.ietf.org with
  > the word 'unsubscribe' in a single line as the message text body.
  > archive: <http://psg.com/lists/radiusext/>
  > 
  > 
  > 
  > --
  > to unsubscribe send a message to radiusext-request@ops.ietf.org with
  > the word 'unsubscribe' in a single line as the message text body.
  > archive: <http://psg.com/lists/radiusext/>

--Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>.hmmessage P {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
	FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>

<META content="MSHTML 6.00.6000.17023" name=GENERATOR></HEAD>
<BODY class=hmmessage bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff>Hi Bernard,</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff>Comments are in line.</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff>B. R.<BR>Tina</FONT><BR><A 
href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=bernard_aboba@hotmail.com 
  href="mailto:bernard_aboba@hotmail.com">Bernard Aboba</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=tena@huawei.com 
  href="mailto:tena@huawei.com">tena@huawei.com</A> ; <A 
  title=aaa-doctors@ietf.org 
  href="mailto:aaa-doctors@ietf.org">aaa-doctors@ietf.org</A> ; <A 
  title=radiusext@ops.ietf.org 
  href="mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</A> ; <A 
  title=dime@ietf.org href="mailto:dime@ietf.org">dime@ietf.org</A> ; <A 
  title=dromasca@avaya.com 
  href="mailto:dromasca@avaya.com">dromasca@avaya.com</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, June 03, 2010 1:03 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: FEDAUTH BOF request</DIV>
  <DIV><BR></DIV>
  <DIV>Tina said: <BR><BR>&gt; Comments are below.<BR>&gt; 1. This might be of 
  interest to ngHLR (Unified Subscriber Center) kind of <BR>&gt; solutions who 
  provide Identity Management services<BR>&gt; 2. From protocol side, I think it 
  may be more interesting for RADIUS as I&nbsp; doubt the suitability of 
  Diameter for this.<BR><BR>Not sure why RADIUS would be more suitable than 
  Diameter for carrying large payloads such as SAML assertions.&nbsp; The 4096 
  octet RADIUS PDU limit is not transport-specific -- that is, transporting the 
  RADIUS payload over TCP does not solve the problem.&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff>[Tina: You are also right from the aspect 
  you&nbsp;raised.</FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff>Diameter roaming model is well established 
  (in use cases like WLAN-3GPP interworking) without the use of EAP or SAML. I 
  fail to see what would be the benefits of using EAP or SAML with Diameter 
  which the current roaming model does not already have.</FONT></DIV>
  <DIV><FONT face=Arial><FONT color=#0000ff>Everything has pros and cons, as you 
  said in another email, let's begin with a problem statement, and then 
  protocols.]</FONT><BR></FONT><BR><BR>&nbsp;<BR>&gt; ----- Original Message 
  ----- <BR>&gt; From: "Romascanu, Dan (Dan)" &lt;dromasca@avaya.com&gt;<BR>&gt; 
  To: &lt;dime@ietf.org&gt;; "radext mailing list" 
  &lt;radiusext@ops.ietf.org&gt;; <BR>&gt; &lt;aaa-doctors@ietf.org&gt;<BR>&gt; 
  Sent: Wednesday, June 02, 2010 10:56 PM<BR>&gt; Subject: FEDAUTH BOF 
  request<BR>&gt; <BR>&gt; <BR>&gt; Diameter and RADIUS experts should pay 
  attention to the request to hold<BR>&gt; a Federated Authentication (FEDAUTH) 
  BOF which will be discussed this<BR>&gt; morning by the IAB and the 
  IESG.<BR>&gt; <BR>&gt; The Draft Charter is available at<BR>&gt; 
  http://www.project-moonshot.org/bof/charter/, and more information 
  about<BR>&gt; this BOF or other BOF requests can be examined at<BR>&gt; 
  http://trac.tools.ietf.org/bof/trac/<BR>&gt; <BR>&gt; Dan<BR>&gt; <BR>&gt; 
  --<BR>&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org 
  with<BR>&gt; the word 'unsubscribe' in a single line as the message text 
  body.<BR>&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<BR>&gt; 
  <BR>&gt; <BR>&gt; <BR>&gt; --<BR>&gt; to unsubscribe send a message to 
  radiusext-request@ops.ietf.org with<BR>&gt; the word 'unsubscribe' in a single 
  line as the message text body.<BR>&gt; archive: 
  &lt;http://psg.com/lists/radiusext/&gt;<BR></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_7B4nn4f3xYb02dix0iwk0A)--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 13:35:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "radext issue tracker" <trac@tools.ietf.org>
Cc: radiusext@ops.ietf.org
Auto-Submitted: auto-generated
To: wdec@cisco.com
Date: Thu, 03 Jun 2010 13:35:31 -0000
Reply-To: radiusext@ops.ietf.org
Subject: Re: [radext] #2: comments on draft-ietf-radext-ipv6-access-01
Message-ID: <073.45ee5b4e5cc2640cee95be39b075a65b@tools.ietf.org>

#2: comments on draft-ietf-radext-ipv6-access-01
-------------------------------------+--------------------------------------
 Reporter:  msmith@…                 |       Owner:  wdec@…        
     Type:  defect                   |      Status:  assigned      
 Priority:  major                    |   Milestone:  milestone1    
Component:  ipv6-access              |     Version:  1.0           
 Severity:  In WG Last Call          |    Keywords:                
-------------------------------------+--------------------------------------
Changes (by wdec@…):

  * status:  new => assigned


Comment:

 Sorry for not replying earlier, just came across this ticket...

 There are actually a number of issues pointed out, which I'll address one
 by one:

 1. Deployment Scenarios
 Partially accepted: Propose changing RG host to RG or host. In practically
 all deployments, the RG looks/talks like a host on its WAN interface, so
 the distinction is subtle (and one that continues to be discussed over).
 In terms of the diagram and terminology, while it may be BBF specific,
 there really is no other open standard architecture to refer to. So
 instead of coining new phrases, or adding options like AN or eQAM or
 Switch, etc, leaving things as they are would seem best.

 2. The existing use of prefix with IID is, as you also note, not very
 pretty. Furthermore it is specific to PPP (IPCPv6). In cases where say
 DHCPv6 is desired to be used for assigning the address, instead of
 splitting up the address between the two existing attributes, the new one
 can be used with a neater effect.

 3. Domain name
 This is a good point, but one that appears to be more general than IPv6
 attributes. I know of VSAs for the domain name, for precisely the purpose
 you give, and it's likely to be applicable to both v4 and v6. Do you see
 need for split domains?

 4. Adding a dhcp server address.
 This is an interesting proposal, but perhaps a bit too specific in terms
 of the set-up where it could be applicable. One of the drivers for this
 draft has been that some operators intend to use Radius to pass some of
 the key attributes to an embedded dhcpv6 server. In the scenario you
 describe, the NAS would effectively either use DHCPv6 to get some config
 for itself, or be a proxy for the client. One gets the impression that
 both of these mechanisms may need to be explored further with dhcpv6
 folks...

 5. What would be your proposal for encoding this without using a complex
 attribute? In some of the past draft iterations, we had pretty much all
 parameters allowed, but this was deemed to contravene existing radius
 practices, so we simplified to the bare minimum.
 Side note: I think that a route preference could very well be a default
 setting which does not need to be exposed via Radius.

 6. Yes, that's fine. We'll try to add it to the draft, unless someone
 objects.

 Thanks,
 Woj.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/2#comment:1>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 12:52:53 +0000
Message-ID: <4C07A571.6040004@deployingradius.com>
Date: Thu, 03 Jun 2010 14:52:01 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

>>> " These approaches are often incompatible, leading to
>>>   additional complexity in RADIUS implementations."
>
> The above states that the approach taken by SDOs when working on their attributes was incompatible - but as the document asserts SDOs dont have to be compatible with other SDOs.

  No, it does not.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 10:59:27 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 06:59:05 -0400
Subject: Re: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: On issue 6: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDC8hahyMkKCH7TrC10fwRm0qBzA==
Message-ID: <1957F063-9C44-43D4-9619-FAEA1681F828@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 03-06-2010, at 05:02 , Alan DeKok wrote:

>>=20
>> Issue 6:
>> Section 3.2
>>=20
>> " These approaches are often incompatible, leading to
>>   additional complexity in RADIUS implementations."
>>=20
>> But they dont have to be compatible.
>=20
>  The above text is in a section titled "Rationale", i.e. motivation for
> the document.  Motivation includes explanations of why bad things are bad=
.
>=20
>> Get rid of that statement.
>=20
>  If everyone had done "the right thing" for RADIUS design, there would
> have been no need for the guidelines document.  Unfortunately, that is
> not the case, and the rationale for the document should be explained.

The above states that the approach taken by SDOs when working on their attr=
ibutes was incompatible - but as the document asserts SDOs dont have to be =
compatible with other SDOs.

Just say:

These approaches lead to additional complexity in RADIUS implementations.

Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 10:52:49 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Thu, 3 Jun 2010 06:51:58 -0400
Subject: Re: Issue 5 : Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: Issue 5 : Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsDCsoJzdWK+l/ISEeC5YmuoGR+QQ==
Message-ID: <C8B8FF50-333F-44BE-9CAE-01062C983F88@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

>> Issue 5:
>>=20
>> Section 2.2
>>=20
>> The following text does not make sense:
>>=20
>> " Vendors therefore SHOULD NOT use multiple
>>   formats for VSAs that are associated with a particular Vendor Id.  A
>>   vendor wishing to use multiple VSA formats SHOULD request one Vendor
>>   Id for each VSA format that they will use."
>>=20
>> If a vendor defines two VSAs one of a basic type and another of a non-ba=
sic type they should not require a new vendor id.  Please delete this recom=
mendation.
>=20
>  It is intended to refer to the "TLV encoding scheme", i.e. RFC 2865
> Section 5.26 encoding of {8-bit type, 8-bit length, data}, versus (e.g.)
> the USR encoding of {32-bit type, data}.
>=20
>  I suggest changing the text to clarify this, by saying:
>=20
> --
> All VSA encodings that do not follow the [RFC2865] Section 5.26 scheme
> are NOT RECOMMENDED.  Although [RFC2865] does not mandate
> it, implementations commonly assume that the Vendor Id can be used as
> a key to determine the on-the-wire encoding of a VSA.  Vendors
> therefore SHOULD NOT use multiple encodings for VSAs that are
> associated with a particular Vendor Id.  A vendor wishing to use
> multiple VSA encodings SHOULD request one Vendor Id for each VSA
> encoding that they will use.
> ---
>=20
>  This uses terminology which is in line with RFC 2865.  I will also
> review the document, and ensure that discussion about TLVs uses
> "encoding", rather than "format", for consistency and clarity.

Okay.  Perhaps giving an example of what is meant by encoding otherwise thi=
s may be confused with formatting.


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 09:03:33 +0000
Message-ID: <4C076FAB.2070001@deployingradius.com>
Date: Thu, 03 Jun 2010 11:02:35 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> Section 1.2
> 
> Issue 1:
> Special language is provided for "MUST" "MUST-NOT"  do we need to state the same for "SHALL" and "SHALL-NOT"?  I am not sure because I haven't checked.  

  It is not necessary.  The special language for "MUST" and "MUST NOT"
is there because there were concerns that the document didn't state
clearly enough that it had no new normative requirements on RADIUS.

  i.e. that text is explanatory, and has no meaning other than to
clarify the role of the document for the reader.  The normal RFC 2119
meanings of those words are unchanged.

> Section 1.3.1
> 
> Issue 2:
> "We do not forbid these specifications, but it is
>    RECOMMENDED that they are created only if they have a limited scope
>    of applicability, and all new attributes defined in those
>    specifications are VSAs."
> 
> What is meant by "limited scope of applicability"?  Is it limited scope of applicability within the SDO?  I would think not.  It is already stated in this section that - SDO can design for their own purposes in several places in this section:

  The "limited scope of applicability" is explained in the following
paragraph, which references Sections 3.3.2 and 3.3.3.

>  "By
>    articulating guidelines for RADIUS attribute design, this document
>    enables SDOs out of the IETF to design their own RADIUS attributes
>    within the Vendor-Specific Attribute (VSA) space."
> 
> Is "limited scope of applicability" over and above that?  The basic problem is that we have lots of text that is repeating in this section.

  The limited scope of applicability is explained in detail.  It's
difficult to solve the problem of not explaining in enough detail what
it means, and simultaneously having too much explanatory text in the
document.

> I disagree that:
> 
>  * use only the "basic data types" (see below) for all VSAs;
> 
> Please delete that.  Since the next bullet 
> 
> Actually, the last bullet suffices:
> 
>   * follow the guidelines given in this document.
>
> I suggest getting rid of the bullets and just state:
> 
>  It is RECOMMENDED that SDOs and vendors seek review of RADIUS
>    attribute specifications from the IETF.  However, specifications do
>    not require IETF review when they follow the guidelines given this document.

  The checklist gives a simple and unambiguous definition for when IETF
reviews are needed.  As the rest of the document has been deemed long
and repetitive, a short checklist should be useful.  An SDO wanting to
know if they require an IETF review needs only read a short checklist,
rather than a long and exhausting document.

> Issue: 4:
> 
> Section 2.1
> 
> Change:
> 
>  All other data formats are defined to be "complex data types", and
>    are NOT RECOMMENDED for normal use.  Nested attributes, or attributes
>    grouped via methods other than defined in [RFC2868] do not qualify as
>    "basic data types", and SHOULD NOT be used.
> 
> To
>  All other data formats are defined to be "complex data types", and
>    are NOT RECOMMENDED for normal use including nested attributes, or attributes
>    grouped via methods other than defined in [RFC2868].
>
> I think the document asserts already that complex data types should not be used.

  The following paragraph qualifies the above statement with an
explanation as to why complex types are sometimes necessary.  Removing
the recommendation means that the flow and logic of the document would
be broken.

> Issue 5:
> 
> Section 2.2
> 
> The following text does not make sense:
> 
> " Vendors therefore SHOULD NOT use multiple
>    formats for VSAs that are associated with a particular Vendor Id.  A
>    vendor wishing to use multiple VSA formats SHOULD request one Vendor
>    Id for each VSA format that they will use."
> 
> If a vendor defines two VSAs one of a basic type and another of a non-basic type they should not require a new vendor id.  Please delete this recommendation.

  It is intended to refer to the "TLV encoding scheme", i.e. RFC 2865
Section 5.26 encoding of {8-bit type, 8-bit length, data}, versus (e.g.)
the USR encoding of {32-bit type, data}.

  I suggest changing the text to clarify this, by saying:

--
All VSA encodings that do not follow the [RFC2865] Section 5.26 scheme
are NOT RECOMMENDED.  Although [RFC2865] does not mandate
it, implementations commonly assume that the Vendor Id can be used as
a key to determine the on-the-wire encoding of a VSA.  Vendors
therefore SHOULD NOT use multiple encodings for VSAs that are
associated with a particular Vendor Id.  A vendor wishing to use
multiple VSA encodings SHOULD request one Vendor Id for each VSA
encoding that they will use.
---

  This uses terminology which is in line with RFC 2865.  I will also
review the document, and ensure that discussion about TLVs uses
"encoding", rather than "format", for consistency and clarity.

> Issue 6:
>  Section 3.2
> 
> " These approaches are often incompatible, leading to
>    additional complexity in RADIUS implementations."
> 
> But they dont have to be compatible.

  The above text is in a section titled "Rationale", i.e. motivation for
the document.  Motivation includes explanations of why bad things are bad.

> Get rid of that statement.

  If everyone had done "the right thing" for RADIUS design, there would
have been no need for the guidelines document.  Unfortunately, that is
not the case, and the rationale for the document should be explained.

> Issue 7:
> 
> Section 3.3.3:
> Is repeating text in previous sections: 1.3.1
> 
> The level of repetition in this document is very high. Points are stated and restated and restated.  It is very exhausting to read.

  The repetition is a the result of a gradual exposition of ideas.
First, a short introduction.  Second, a set of recommendations.  Third,
a detailed rationale for the recommendations.

  When the recommendations and rational were placed side by side, the
feedback was that the document was too complex, and the text should be
separated.  We cannot, unfortunately go back to the previous layout as
it has already been judged to be inappropriate.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 05:27:03 +0000
Message-ID: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
Content-Type: multipart/alternative; boundary="_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, <dime@ietf.org>, "dromasca@avaya.com" <dromasca@avaya.com>
Subject: RE: FEDAUTH BOF request
Date: Wed, 2 Jun 2010 22:26:26 -0700
MIME-Version: 1.0

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Let me provide a bit of  context about what I think the problem is here.=20

As noted by Sam in a previous conversation=2C the basic use case is "cloud =
services"=2C where an education institution or enterprise is making use of =
hosted services.  In these situations=2C the institution may not just want =
the service provider to host an application=2C but may want to keep their c=
redentials local=2C rather than hosting this in the cloud as well.=20

In the original Moonshot investigation=2C Kerberos was considered as a pote=
ntial solution.  However=2C while Kerberos is well understood from a securi=
ty point of view=2C and could relatively easily be modified to support EAP-=
based pre-auth (numerous proposals for this have been advanced and in some =
cases implemented)  Kerberos federation has not been widely deployed.=20

One of the basic problems with putting a KDC on the Internet is that there =
is no easy way to protect it=2C since both clients and other KDCs may need =
to send packets to and from the KDC.  For this reason if there are roaming =
clients there is no easy way to filter traffic to/from the KDC.  In additio=
n=2C the Kerberos protocol is vulnerable to passive attacks in the absence =
of extensions such as PKINIT or Kerberos Hardening.=20

In contrast=2C the AAA roaming model has been widely deployed=2C in part be=
cause it is much easier to protect a AAA server.  AAA servers only talk to =
AAA clients=2C not to users directly.  This means that it is typically poss=
ible to filter traffic to the AAA server so that only packets originating f=
rom legitimate AAA clients can be sent to/from the AAA server.  =20

In addition to these basic security issues=2C the AAA delegation model is m=
uch simpler than Kerberos.  Obtaining a Kerberos TGT for a local realm invo=
lves first obtaining a TGT from a "home" realm and then requesting a TGT fo=
r the local realm.  This involves multiple exchanges=2C and as noted earlie=
r requires both the local KDC and the home KDC to be available over the Int=
ernet.  In contrast=2C a AAA client implicitly delegates authority to the A=
AA server for the Accept/Reject decision=2C so that explicit trust relation=
ships don't need to be configured.  As long as the AAA client can reach the=
 AAA server via a chain of proxies the trust relationship can succeed.=20

Given these basic characteristics of Kerberos and AAA delegation=2C the Moo=
nshot team has decided that a AAA-based approach to delegation is more like=
ly to be widely deployed than a Kerberos-based one.  My take on this is tha=
t this assessment is probably realistic.=20

Where I get lost is making the leap between the AAA delegation model and us=
e of EAP.  As we saw with Digest authentication (RFC 5090)=2C it is possibl=
e to extend AAA to support application-layer authentication without use of =
EAP.  For example=2C using AAA to carry GSS-API payloads would not require =
much more than defining a GSS-Message attribute.  EAP has no unique propert=
ies that make it more suitable for use with AAA.  In fact=2C I would argue =
that the fit between EAP and AAA has always been tenuous at best -- witness=
 the issues encountered in federated EAP authentication that RADSEC has bee=
n needed to address. =20

In particular=2C the problems of EAP auth (e.g. multiple round-trips=2C gen=
eral fragility in federated uses) become highly toxic when applied to Realt=
ime applications such as XMPP and SIP.  As we have learned=2C Digest auth (=
RFC 5090) has not been widely deployed=2C in part because of concern about =
the additional latency added by a AAA exchange.  For users of real-time app=
lications=2C additional latency is a basic=2C non-negotiable goal.  If the =
relatively modest number of exchanges implied by RFC 5090 were intolerable =
in realtime applications=2C  how can we expect EAP exchanges (which can inv=
olve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The a=
nswer unfortunately=2C is that there is no chance at all. =20

So in summary=2C I believe that some aspects of the problem statement make =
sense=2C but that a solution has been chosen prematurely.  The right way to=
 move forward in a situation like this is to begin with a problem statement=
=2C which should include carefully validating the uses cases. =20
 =20

> ----- Original Message -----=20
> From: "Romascanu=2C Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>=3B "radext mailing list" <radiusext@ops.ietf.org>=3B=
=20
> <aaa-doctors@ietf.org>
> Sent: Wednesday=2C June 02=2C 2010 10:56 PM
> Subject: FEDAUTH BOF request
>=20
>=20
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
>=20
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/=2C and more information abou=
t
> this BOF or other BOF requests can be examined  at
> http://trac.tools.ietf.org/bof/trac/
>=20
> Dan
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Let me provide a bit of&nbsp=3B context about what I think the problem is h=
ere. <br><br>As noted by Sam in a previous conversation=2C the basic use ca=
se is "cloud services"=2C where an education institution or enterprise is m=
aking use of hosted services.&nbsp=3B In these situations=2C the institutio=
n may not just want the service provider to host an application=2C but may =
want to keep their credentials local=2C rather than hosting this in the clo=
ud as well. <br><br>In the original Moonshot investigation=2C Kerberos was =
considered as a potential solution.&nbsp=3B However=2C while Kerberos is we=
ll understood from a security point of view=2C and could relatively easily =
be modified to support EAP-based pre-auth (numerous proposals for this have=
 been advanced and in some cases implemented)&nbsp=3B Kerberos federation h=
as not been widely deployed. <br><br>One of the basic problems with putting=
 a KDC on the Internet is that there is no easy way to protect it=2C since =
both clients and other KDCs may need to send packets to and from the KDC.&n=
bsp=3B For this reason if there are roaming clients there is no easy way to=
 filter traffic to/from the KDC.&nbsp=3B In addition=2C the Kerberos protoc=
ol is vulnerable to passive attacks in the absence of extensions such as PK=
INIT or Kerberos Hardening. <br><br>In contrast=2C the AAA roaming model ha=
s been widely deployed=2C in part because it is much easier to protect a AA=
A server.&nbsp=3B AAA servers only talk to AAA clients=2C not to users dire=
ctly.&nbsp=3B This means that it is typically possible to filter traffic to=
 the AAA server so that only packets originating from legitimate AAA client=
s can be sent to/from the AAA server.&nbsp=3B&nbsp=3B <br><br>In addition t=
o these basic security issues=2C the AAA delegation model is much simpler t=
han Kerberos.&nbsp=3B Obtaining a Kerberos TGT for a local realm involves f=
irst obtaining a TGT from a "home" realm and then requesting a TGT for the =
local realm.&nbsp=3B This involves multiple exchanges=2C and as noted earli=
er requires both the local KDC and the home KDC to be available over the In=
ternet.&nbsp=3B In contrast=2C a AAA client implicitly delegates authority =
to the AAA server for the Accept/Reject decision=2C so that explicit trust =
relationships don't need to be configured.&nbsp=3B As long as the AAA clien=
t can reach the AAA server via a chain of proxies the trust relationship ca=
n succeed. <br><br>Given these basic characteristics of Kerberos and AAA de=
legation=2C the Moonshot team has decided that a AAA-based approach to dele=
gation is more likely to be widely deployed than a Kerberos-based one.&nbsp=
=3B My take on this is that this assessment is probably realistic. <br><br>=
Where I get lost is making the leap between the AAA delegation model and us=
e of EAP.&nbsp=3B As we saw with Digest authentication (RFC 5090)=2C it is =
possible to extend AAA to support application-layer authentication without =
use of EAP.&nbsp=3B For example=2C using AAA to carry GSS-API payloads woul=
d not require much more than defining a GSS-Message attribute.&nbsp=3B EAP =
has no unique properties that make it more suitable for use with AAA.&nbsp=
=3B In fact=2C I would argue that the fit between EAP and AAA has always be=
en tenuous at best -- witness the issues encountered in federated EAP authe=
ntication that RADSEC has been needed to address.&nbsp=3B <br><br>In partic=
ular=2C the problems of EAP auth (e.g. multiple round-trips=2C general frag=
ility in federated uses) become highly toxic when applied to Realtime appli=
cations such as XMPP and SIP.&nbsp=3B As we have learned=2C Digest auth (RF=
C 5090) has not been widely deployed=2C in part because of concern about th=
e additional latency added by a AAA exchange.&nbsp=3B For users of real-tim=
e applications=2C additional latency is a basic=2C non-negotiable goal.&nbs=
p=3B If the relatively modest number of exchanges implied by RFC 5090 were =
intolerable in realtime applications=2C&nbsp=3B how can we expect EAP excha=
nges (which can involve 4-5 times the number of roundtrips of RFC 5090) to =
be deployed?&nbsp=3B The answer unfortunately=2C is that there is no chance=
 at all.&nbsp=3B <br><br>So in summary=2C I believe that some aspects of th=
e problem statement make sense=2C but that a solution has been chosen prema=
turely.&nbsp=3B The right way to move forward in a situation like this is t=
o begin with a problem statement=2C which should include carefully validati=
ng the uses cases.&nbsp=3B <br>&nbsp=3B <br><br>&gt=3B ----- Original Messa=
ge ----- <br>&gt=3B From: "Romascanu=2C Dan (Dan)" &lt=3Bdromasca@avaya.com=
&gt=3B<br>&gt=3B To: &lt=3Bdime@ietf.org&gt=3B=3B "radext mailing list" &lt=
=3Bradiusext@ops.ietf.org&gt=3B=3B <br>&gt=3B &lt=3Baaa-doctors@ietf.org&gt=
=3B<br>&gt=3B Sent: Wednesday=2C June 02=2C 2010 10:56 PM<br>&gt=3B Subject=
: FEDAUTH BOF request<br>&gt=3B <br>&gt=3B <br>&gt=3B Diameter and RADIUS e=
xperts should pay attention to the request to hold<br>&gt=3B a Federated Au=
thentication (FEDAUTH) BOF which will be discussed this<br>&gt=3B morning b=
y the IAB and the IESG.<br>&gt=3B <br>&gt=3B The Draft Charter is available=
 at<br>&gt=3B http://www.project-moonshot.org/bof/charter/=2C and more info=
rmation about<br>&gt=3B this BOF or other BOF requests can be examined  at<=
br>&gt=3B http://trac.tools.ietf.org/bof/trac/<br>&gt=3B <br>&gt=3B Dan<br>=
&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscribe send a message to radiusext-r=
equest@ops.ietf.org with<br>&gt=3B the word 'unsubscribe' in a single line =
as the message text body.<br>&gt=3B archive: &lt=3Bhttp://psg.com/lists/rad=
iusext/&gt=3B<br>&gt=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&gt=3B to un=
subscribe send a message to radiusext-request@ops.ietf.org with<br>&gt=3B t=
he word 'unsubscribe' in a single line as the message text body.<br>&gt=3B =
archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 05:04:03 +0000
Message-ID: <BLU137-W350A9D16B24A7A1F9D76F193D10@phx.gbl>
Content-Type: multipart/alternative; boundary="_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, <dime@ietf.org>, "dromasca@avaya.com" <dromasca@avaya.com>
Subject: RE: FEDAUTH BOF request
Date: Wed, 2 Jun 2010 22:03:16 -0700
MIME-Version: 1.0

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Tina said:=20

> Comments are below.
> 1. This might be of interest to ngHLR (Unified Subscriber Center) kind of=
=20
> solutions who provide Identity Management services
> 2. From protocol side=2C I think it may be more interesting for RADIUS as=
 I  doubt the suitability of Diameter for this.

Not sure why RADIUS would be more suitable than Diameter for carrying large=
 payloads such as SAML assertions.  The 4096 octet RADIUS PDU limit is not =
transport-specific -- that is=2C transporting the RADIUS payload over TCP d=
oes not solve the problem.=20

=20
> ----- Original Message -----=20
> From: "Romascanu=2C Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>=3B "radext mailing list" <radiusext@ops.ietf.org>=3B=
=20
> <aaa-doctors@ietf.org>
> Sent: Wednesday=2C June 02=2C 2010 10:56 PM
> Subject: FEDAUTH BOF request
>=20
>=20
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
>=20
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/=2C and more information abou=
t
> this BOF or other BOF requests can be examined  at
> http://trac.tools.ietf.org/bof/trac/
>=20
> Dan
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Tina said: <br><br>&gt=3B Comments are below.<br>&gt=3B 1. This might be of=
 interest to ngHLR (Unified Subscriber Center) kind of <br>&gt=3B solutions=
 who provide Identity Management services<br>&gt=3B 2. From protocol side=
=2C I think it may be more interesting for RADIUS as I&nbsp=3B doubt the su=
itability of Diameter for this.<br><br>Not sure why RADIUS would be more su=
itable than Diameter for carrying large payloads such as SAML assertions.&n=
bsp=3B The 4096 octet RADIUS PDU limit is not transport-specific -- that is=
=2C transporting the RADIUS payload over TCP does not solve the problem. <b=
r><br>&nbsp=3B<br>&gt=3B ----- Original Message ----- <br>&gt=3B From: "Rom=
ascanu=2C Dan (Dan)" &lt=3Bdromasca@avaya.com&gt=3B<br>&gt=3B To: &lt=3Bdim=
e@ietf.org&gt=3B=3B "radext mailing list" &lt=3Bradiusext@ops.ietf.org&gt=
=3B=3B <br>&gt=3B &lt=3Baaa-doctors@ietf.org&gt=3B<br>&gt=3B Sent: Wednesda=
y=2C June 02=2C 2010 10:56 PM<br>&gt=3B Subject: FEDAUTH BOF request<br>&gt=
=3B <br>&gt=3B <br>&gt=3B Diameter and RADIUS experts should pay attention =
to the request to hold<br>&gt=3B a Federated Authentication (FEDAUTH) BOF w=
hich will be discussed this<br>&gt=3B morning by the IAB and the IESG.<br>&=
gt=3B <br>&gt=3B The Draft Charter is available at<br>&gt=3B http://www.pro=
ject-moonshot.org/bof/charter/=2C and more information about<br>&gt=3B this=
 BOF or other BOF requests can be examined  at<br>&gt=3B http://trac.tools.=
ietf.org/bof/trac/<br>&gt=3B <br>&gt=3B Dan<br>&gt=3B <br>&gt=3B --<br>&gt=
=3B to unsubscribe send a message to radiusext-request@ops.ietf.org with<br=
>&gt=3B the word 'unsubscribe' in a single line as the message text body.<b=
r>&gt=3B archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br>&gt=3B <br=
>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscribe send a message to=
 radiusext-request@ops.ietf.org with<br>&gt=3B the word 'unsubscribe' in a =
single line as the message text body.<br>&gt=3B archive: &lt=3Bhttp://psg.c=
om/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_--

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 03 Jun 2010 04:03:45 +0000
Date: Thu, 03 Jun 2010 12:02:46 +0800
From: Tina TSOU <tena@huawei.com>
Subject: Re: FEDAUTH BOF request
To: aaa-doctors@ietf.org, radext mailing list <radiusext@ops.ietf.org>, dime@ietf.org, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-id: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT

Comments are below.
1. This might be of interest to ngHLR (Unified Subscriber Center) kind of 
solutions who provide Identity Management services
2. From protocol side, I think it may be more interesting for RADIUS as I 
doubt the suitability of Diameter for this.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
<aaa-doctors@ietf.org>
Sent: Wednesday, June 02, 2010 10:56 PM
Subject: FEDAUTH BOF request


Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 02 Jun 2010 15:15:38 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Wed, 2 Jun 2010 11:14:51 -0400
Subject: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Topic: Avi review of I-D Action:draft-ietf-radext-design-13.txt
Thread-Index: AcsCZljknF/AXCfARZua6Gos5EBBoA==
Message-ID: <7FDC2F64-EAC6-4E2E-A541-9AEF4BB22347@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Section 1.2

Issue 1:
Special language is provided for "MUST" "MUST-NOT"  do we need to state the=
 same for "SHALL" and "SHALL-NOT"?  I am not sure because I haven't checked=
. =20

Section 1.3.1

Issue 2:
"We do not forbid these specifications, but it is
   RECOMMENDED that they are created only if they have a limited scope
   of applicability, and all new attributes defined in those
   specifications are VSAs."

What is meant by "limited scope of applicability"?  Is it limited scope of =
applicability within the SDO?  I would think not.  It is already stated in =
this section that - SDO can design for their own purposes in several places=
 in this section:

 "By
   articulating guidelines for RADIUS attribute design, this document
   enables SDOs out of the IETF to design their own RADIUS attributes
   within the Vendor-Specific Attribute (VSA) space."

Is "limited scope of applicability" over and above that?  The basic problem=
 is that we have lots of text that is repeating in this section.

Issue 3:

I disagree that:

 * use only the "basic data types" (see below) for all VSAs;

Please delete that.  Since the next bullet=20

Actually, the last bullet suffices:

  * follow the guidelines given in this document.

I suggest getting rid of the bullets and just state:

 It is RECOMMENDED that SDOs and vendors seek review of RADIUS
   attribute specifications from the IETF.  However, specifications do
   not require IETF review when they follow the guidelines given this docum=
ent.

Issue: 4:

Section 2.1

Change:

 All other data formats are defined to be "complex data types", and
   are NOT RECOMMENDED for normal use.  Nested attributes, or attributes
   grouped via methods other than defined in [RFC2868] do not qualify as
   "basic data types", and SHOULD NOT be used.

To
 All other data formats are defined to be "complex data types", and
   are NOT RECOMMENDED for normal use including nested attributes, or attri=
butes
   grouped via methods other than defined in [RFC2868].

I think the document asserts already that complex data types should not be =
used.

Issue 5:

Section 2.2

The following text does not make sense:

" Vendors therefore SHOULD NOT use multiple
   formats for VSAs that are associated with a particular Vendor Id.  A
   vendor wishing to use multiple VSA formats SHOULD request one Vendor
   Id for each VSA format that they will use."

If a vendor defines two VSAs one of a basic type and another of a non-basic=
 type they should not require a new vendor id.  Please delete this recommen=
dation.

Issue 6:
 Section 3.2

" These approaches are often incompatible, leading to
   additional complexity in RADIUS implementations."

But they dont have to be compatible.

Get rid of that statement.

Issue 7:

Section 3.3.3:
Is repeating text in previous sections: 1.3.1

The level of repetition in this document is very high. Points are stated an=
d restated and restated.  It is very exhausting to read.


Avi Lior
avi@bridgewatersystems.com
office: +1 613-591-9104x6417
    cell: +1 613-796-4183



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 02 Jun 2010 14:57:48 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: FEDAUTH BOF request
Date: Wed, 2 Jun 2010 16:56:17 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>
Thread-Topic: FEDAUTH BOF request
Thread-Index: AcsCY8D3YG4qrCIAT927dkDMQ1m8hw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>, "radext mailing list" <radiusext@ops.ietf.org>, <aaa-doctors@ietf.org>

Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.=20

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

