From owner-radiusext@ops.ietf.org  Fri Aug  1 04:26:33 2008
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 4C7143A6849
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  1 Aug 2008 04:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.588
X-Spam-Level: 
X-Spam-Status: No, score=-0.588 tagged_above=-999 required=5
	tests=[AWL=-1.640, BAYES_05=-1.11, 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 rZcLE89gOciy
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri,  1 Aug 2008 04:26:32 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6EFC93A6CE3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  1 Aug 2008 04:26:32 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KOshh-0007qU-G4
	for radiusext-data@psg.com; Fri, 01 Aug 2008 11:21:49 +0000
Received: from [76.96.62.32] (helo=QMTA03.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KOshd-0007ol-H4
	for radiusext@ops.ietf.org; Fri, 01 Aug 2008 11:21:47 +0000
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59])
	by QMTA03.westchester.pa.mail.comcast.net with comcast
	id wxzu1Z0011GhbT853zMkrx; Fri, 01 Aug 2008 11:21:44 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA07.westchester.pa.mail.comcast.net with comcast
	id wzMk1Z00124Kx1C3TzMk8q; Fri, 01 Aug 2008 11:21:44 +0000
X-Authority-Analysis: v=1.0 c=1 a=7DkhCYs15ycH1WLI64QA:9
 a=M9RmaRqGYdJ5y7HjUHpF9jB0TkcA:4 a=zoKOyUDlhksA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Fri, 1 Aug 2008 07:21:47 -0400
Message-ID: <05b401c8f3c8$c9638350$6401a8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acjzr2Kn0c/WA3wOSYyrkViaWZSahgAGUDwQ
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba writes...

> Are there any objections to granting the allocation as requested below?

None from me.



--
to unsubscribe send a message to 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 Aug  1 05:50:04 2008
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 1A3AC3A6970
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  1 Aug 2008 05:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5
	tests=[AWL=-1.052, 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 YUw4wjXUiCsj
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri,  1 Aug 2008 05:50:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E50C428C513
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  1 Aug 2008 05:45:19 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KOtvA-000GuW-Jl
	for radiusext-data@psg.com; Fri, 01 Aug 2008 12:39:48 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <blourdel@cisco.com>)
	id 1KOtv3-000Gru-TV
	for radiusext@ops.ietf.org; Fri, 01 Aug 2008 12:39:46 +0000
X-IronPort-AV: E=Sophos;i="4.31,293,1215388800"; 
   d="scan'208";a="16006071"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
  by ams-iport-1.cisco.com with ESMTP; 01 Aug 2008 12:39:32 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m71CdVxR021917;
	Fri, 1 Aug 2008 14:39:31 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m71CdV6S024270;
	Fri, 1 Aug 2008 12:39:31 GMT
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 1 Aug 2008 14:39:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] draft-lourdelet-radext-ipv6-dhcp-00 published
Date: Fri, 1 Aug 2008 14:40:03 +0200
Message-ID: <A05118C6DF9320488C77F3D5459B17B707E50CE4@xmb-ams-333.emea.cisco.com>
In-Reply-To: <3A460794-0078-4FAB-A401-7DB0507E717A@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] draft-lourdelet-radext-ipv6-dhcp-00 published
Thread-Index: AcjyUC6ylRNCKry7R6KCPBISPaTeWwBgyt2w
From: "Benoit Lourdelet (blourdel)" <blourdel@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, <dhcwg@ietf.org>,
        <radiusext@ops.ietf.org>
Cc: <gwz@netcube.com>
X-OriginalArrivalTime: 01 Aug 2008 12:39:31.0784 (UTC) FILETIME=[A559E480:01C8F3D3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1474; t=1217594371; x=1218458371;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=blourdel@cisco.com;
	z=From:=20=22Benoit=20Lourdelet=20(blourdel)=22=20<blourdel@
	cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20draft-lourdelet-radext-ipv6-d
	hcp-00=20published
	|Sender:=20;
	bh=Ogs/0GMvXFuh8jZ2LUAvQimJUqaDtdsfowHioisT+58=;
	b=I6eQ5/K7RqqKgIlr9VF0mBra0nqjRMlHptut2k92+NNw4DKHRE97HwujgF
	nW5aTtj+sFZ7j4+IG2+7ALxzNbcDoVeTtgrirs6DqAbUXtXVYWkxx8ECaRCI
	8i+zDJg2sA;
Authentication-Results: ams-dkim-2; header.From=blourdel@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

FYI,

This individual work will be included in a revision of RFC3162 that Glen
Zorn and I are going to work on.


Regards

Benoit

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms (rdroms)
Sent: Wednesday, July 30, 2008 4:23 PM
To: dhcwg@ietf.org; radiusext@ops.ietf.org
Subject: Re: [dhcwg] draft-lourdelet-radext-ipv6-dhcp-00 published

Correction.  On a link with no router advertisements you need to
configure any addresses and prefixes manually and separately.

There is no expectation that the prefix from an assigned address is
necessarily on the link.  On-link prefixes are independent from assigned
addresses.

- Ralph

On Jul 30, 2008, at 8:01 AM, Hemant Singh (shemant) wrote:
>> What about the scenario where there is no router in the network or=20
>> not
> announcing router advertisement with prefix options? What length of=20
> prefix the >DHCPv6 client should use for address assignment?
>
>> Best Regards,
>> 	Janos
>
>
>
> There is no provision in DHCPv6 to include prefix length in a message=20
> to the client - I have said so several times to the DHCPv6 mailer. =20
> Check the email archives.  In a router-less network, you are hosed. =20
> You have to configure an address and prefix length manually.
>
> Hemant

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

--
to unsubscribe send a message to 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 Aug  3 08:32:44 2008
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 79EAD3A68FA
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun,  3 Aug 2008 08:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.105
X-Spam-Level: 
X-Spam-Status: No, score=0.105 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	J_CHICKENPOX_65=0.6, 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 Bm0Vu3fgVq3H
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun,  3 Aug 2008 08:32:42 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 8C56C3A68D9
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun,  3 Aug 2008 08:32:42 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KPfUO-000AgE-6K
	for radiusext-data@psg.com; Sun, 03 Aug 2008 15:27:20 +0000
Received: from [66.46.199.134] (helo=webmail.bridgewatersystems.com)
	by psg.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <avi@bridgewatersystems.com>)
	id 1KPfUH-000AfR-9b
	for radiusext@ops.ietf.org; Sun, 03 Aug 2008 15:27:17 +0000
Received: from exchange02.bridgewatersys.com ([192.168.150.32]) by
 exchange02.bridgewatersys.com ([192.168.150.32]) with mapi; Sun, 3 Aug 2008
 11:27:11 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Bernard Aboba <aboba@internaut.com>, "radiusext@ops.ietf.org"
	<radiusext@ops.ietf.org>
Date: Sun, 3 Aug 2008 11:27:02 -0400
Subject: RE: Request for NAS-Port-Type Allocation
Thread-Topic: Request for NAS-Port-Type Allocation
Thread-Index: Acjzrww/JniR9YHcSBKqpH+cS5HpwwBzlTcy
Message-ID: <8A8CFE8F89C38B41A749C19328C76D6308A058A024@exchange02.bridgewatersys.com>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808010108130.3452@internaut.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>

Looks fine to me as well.

________________________________________
From: owner-radiusext@ops.ietf.org [owner-radiusext@ops.ietf.org] On Behalf=
 Of Bernard Aboba [aboba@internaut.com]
Sent: Friday, August 01, 2008 4:14 AM
To: radiusext@ops.ietf.org
Subject: Request for NAS-Port-Type Allocation

The IANA has received a request for a new NAS-Port-Type allocation.  As
stated in RFC 3575, Section 2.1:

   Certain attributes (for example, NAS-Port-Type) in RADIUS define a
   list of values to correspond with various meanings.  There can be 4
   billion (2^32) values for each attribute.  Additional values can be
   allocated by the Designated Expert.  The exception to this policy is
   the Service-Type attribute (6), whose values define new modes of
   operation for RADIUS.  Values 1-16 of the Service-Type attribute have
   been allocated.  Allocation of new Service-Type values are by IETF
   Consensus.  The intention is that any allocation will be accompanied
   by a published RFC.

Are there any objections to granting the allocation as requested below?

Contact Name :
Tomohiro Ichida

Contact Email :
t_ichida@willcom-inc.com

Type of Assignment :
I request the allocation of new NAS-Port-TYPE.

http://www.iana.org/assignments/radius-types
Values for RADIUS Attribute 61, NAS-Port-Type [RFC2865]:

Registry :
The value is "Wireless - XGP"

Description :
There is a standardization organization as PHS-MOU.
We'd like to prescribe the new number in NAS-PORT-TYPE.
And We'd like to use its number by the next generation PHS system.
it is same as "Wireless - CDMA2000","Wireless - IEEE 802.16"

PHS-MOU is explained as follows this URL
 http://www.phsmou.org/

Additional Info :
 The "Next Generation PHS" specification is is being made.
 A document is not open to the public,sorry.

--
to unsubscribe send a message to 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  Thu Aug  7 22:21:42 2008
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 BC6113A65A6
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu,  7 Aug 2008 22:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.218
X-Spam-Level: 
X-Spam-Status: No, score=-0.218 tagged_above=-999 required=5 tests=[AWL=0.219,
	BAYES_00=-2.599, 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 z00lIK1YMyFu
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu,  7 Aug 2008 22:21:41 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id A108D3A68C0
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu,  7 Aug 2008 22:21:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KRKLm-0008bj-F8
	for radiusext-data@psg.com; Fri, 08 Aug 2008 05:17:18 +0000
Received: from [76.96.30.80] (helo=QMTA08.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KRKLj-0008bN-20
	for radiusext@ops.ietf.org; Fri, 08 Aug 2008 05:17:16 +0000
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id zh1X1Z0030EPchoA8hHExW; Fri, 08 Aug 2008 05:17:14 +0000
Received: from gwzPC ([124.120.225.183])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id zhGk1Z00K3y2SNs8MhH3K2; Fri, 08 Aug 2008 05:17:12 +0000
X-Authority-Analysis: v=1.0 c=1 a=l-Z553lCpb66PHMjOhUA:9
 a=7mIvM9QIgfWHCaW_3Jjv4DpmKS8A:4 a=hodff89a88cA:10 a=zoKOyUDlhksA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Fri, 8 Aug 2008 12:16:33 +0700
Message-ID: <006601c8f915$f4055a00$dc100e00$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba <mailto://aboba@internaut.com> writes:

> The IANA has received a request for a new NAS-Port-Type allocation.  As
> stated in RFC 3575, Section 2.1:
> 
>    Certain attributes (for example, NAS-Port-Type) in RADIUS define a
>    list of values to correspond with various meanings.  There can be 4
>    billion (2^32) values for each attribute.  Additional values can be
>    allocated by the Designated Expert.  The exception to this policy is
>    the Service-Type attribute (6), whose values define new modes of
>    operation for RADIUS.  Values 1-16 of the Service-Type attribute
> have
>    been allocated.  Allocation of new Service-Type values are by IETF
>    Consensus.  The intention is that any allocation will be accompanied
>    by a published RFC.
> 
> Are there any objections to granting the allocation as requested below?

My only objection is to being bothered with it ;-).  I forgot: what is the
rationale behind such careful rationing of the 4 billion (!) NAS-Port-Type
values again?

...



--
to unsubscribe send a message to 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 Aug  8 07:22:50 2008
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 7488C3A681D
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  8 Aug 2008 07:22:50 -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 Kq7zPoiaDjhE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri,  8 Aug 2008 07:22:49 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 819093A6B75
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  8 Aug 2008 07:22:49 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KRSlS-000NQd-V4
	for radiusext-data@psg.com; Fri, 08 Aug 2008 14:16:22 +0000
Received: from [64.233.182.186] (helo=nf-out-0910.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <clapidus@gmail.com>)
	id 1KRSlP-000NQ9-0c
	for radiusext@ops.ietf.org; Fri, 08 Aug 2008 14:16:20 +0000
Received: by nf-out-0910.google.com with SMTP id g13so893524nfb.11
        for <radiusext@ops.ietf.org>; Fri, 08 Aug 2008 07:16:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=an/9L45pKEc3ADml82AS774Nh9xhQRsOesQopASZ0Lc=;
        b=oLZWg79cDqvHN9CXX2nbkVWjkaI7k9Esy439PXPKXDHFpfxJKcDt2Lq2MoWHxVRtbE
         vTGA5csAYC0aq5X/Mn/idZUh6QAmnFwWc/M14rO93Zm69m2vSjX7YqFFpMlNgRESo7R2
         zwSl4d8DUlum4rldY2FcU750RPsuCb9wIeQLU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=mSpTdKuYrY1bm/it88EFTOdO1GY4KvrLql3gYoEasYw/B8Ve9/VTWyQujnc9/Il3Ln
         7i28WfCKNCc90du5pu1ktWLT9CILmsLAFL9RRDCO+E1m7VsH1Qmrgw/3xKVtoO5WxWXb
         +0rQDdqNPbLlB6PH+wss44GdhXF4kGxMAPNDY=
Received: by 10.103.218.9 with SMTP id v9mr3159319muq.91.1218204976616;
        Fri, 08 Aug 2008 07:16:16 -0700 (PDT)
Received: by 10.103.179.8 with HTTP; Fri, 8 Aug 2008 07:16:16 -0700 (PDT)
Message-ID: <c3a174020808080716u3e7635d7x2068d0afeadfb468@mail.gmail.com>
Date: Fri, 8 Aug 2008 11:16:16 -0300
From: "Claudio Lapidus" <clapidus@gmail.com>
To: "Glen Zorn" <glenzorn@comcast.net>, "Bernard Aboba" <aboba@internaut.com>, 
	radiusext@ops.ietf.org
Subject: Re: Request for NAS-Port-Type Allocation
In-Reply-To: <006601c8f915$f4055a00$dc100e00$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
	 <006601c8f915$f4055a00$dc100e00$@net>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Fri, Aug 8, 2008 at 2:16 AM, Glen Zorn <glenzorn@comcast.net> wrote:
> what is the
> rationale behind such careful rationing of the 4 billion (!) NAS-Port-Type
> values again?

Hmm, perhaps is it that every new value will need to be properly
understood by all existing implementations, which in turn will need to
be retrofitted to handle it?

regards,
cl.

--
to unsubscribe send a message to 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 Aug  8 12:15:27 2008
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 29BF23A635F
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri,  8 Aug 2008 12:15:27 -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 WGLXQPW9GomA
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri,  8 Aug 2008 12:15:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 3F5173A68B3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri,  8 Aug 2008 12:15:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KRXM3-0005SZ-Tn
	for radiusext-data@psg.com; Fri, 08 Aug 2008 19:10:27 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <dnelson@elbrysnetworks.com>)
	id 1KRXLw-0005QV-Oy
	for radiusext@ops.ietf.org; Fri, 08 Aug 2008 19:10:26 +0000
Received: (qmail 19854 invoked from network); 8 Aug 2008 15:10:10 -0400
Received: from unknown (HELO xpsuperdvd2) (172.22.18.93)
  by gumby.elbrysnetworks.com with SMTP; 8 Aug 2008 15:10:10 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com> <006601c8f915$f4055a00$dc100e00$@net>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Fri, 8 Aug 2008 15:09:57 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
In-Reply-To: <006601c8f915$f4055a00$dc100e00$@net>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> I forgot: what is the rationale behind such careful rationing
> of the 4 billion (!) NAS-Port-Type values again?

I don't think the value is in rationing.  As you point out, it's not an
overly scarce resource.  I think the value is in maintaining a decent
signal-to-noise ratio in the IANA registry.  Given that there are 4 billion
possible values, it's preferable to avoid duplicates or nearly-duplicates
with ambiguously subtle distinctions.



--
to unsubscribe send a message to 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 Aug  9 03:10:23 2008
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 E953E3A6ACE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  9 Aug 2008 03:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.973
X-Spam-Level: 
X-Spam-Status: No, score=0.973 tagged_above=-999 required=5 tests=[AWL=-1.190,
	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 RJQycWvcC8gK
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat,  9 Aug 2008 03:10:23 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id BCE223A68D2
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  9 Aug 2008 03:10:22 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KRlJh-000Oui-Ox
	for radiusext-data@psg.com; Sat, 09 Aug 2008 10:04:57 +0000
Received: from [76.96.30.64] (helo=QMTA07.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KRlJc-000Ou3-O6
	for radiusext@ops.ietf.org; Sat, 09 Aug 2008 10:04:55 +0000
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id 0A401a0030mlR8UA7A4rX3; Sat, 09 Aug 2008 10:04:51 +0000
Received: from gwzPC ([124.120.216.34])
	by OMTA11.emeryville.ca.mail.comcast.net with comcast
	id 0A3w1a0060l6YCk8XA4SCS; Sat, 09 Aug 2008 10:04:46 +0000
X-Authority-Analysis: v=1.0 c=1 a=Ob27Ffc350yWJpUCRpcA:9
 a=OsmdL2bWAhwTE_4mftzpMjFK2e0A:4 a=-utQw5L2n1AA:10 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com> <006601c8f915$f4055a00$dc100e00$@net> <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2>
In-Reply-To: <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sat, 9 Aug 2008 17:03:40 +0700
Message-ID: <002b01c8fa07$4236ecb0$c6a4c610$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycA==
Content-language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson <mailto://dnelson@elbrysnetworks.com> writes:

> Glen Zorn writes...
> 
> > I forgot: what is the rationale behind such careful rationing
> > of the 4 billion (!) NAS-Port-Type values again?
> 
> I don't think the value is in rationing.  As you point out, it's not an
> overly scarce resource.  I think the value is in maintaining a decent
> signal-to-noise ratio in the IANA registry.  Given that there are 4
> billion
> possible values, 

Micro-managing the namespace is a waste of time.

> it's preferable to avoid duplicates or nearly-
> duplicates
> with ambiguously subtle distinctions.

The level of distinction that is considered to be subtle tends to vary both
with the state of the art & the expertise of the observer: the difference
between uranium-238 and u-235 certainly seems subtle to me (what's a couple
of neutrons between friends? ;-) but is certainly not subtle to a modern
physicist & even less so to a maker of atomic bombs.  My point is that,
because NAS-Port-Type values generally represent L2 protocols, it is
somewhat likely that IETF "experts" will lack the expertise to make these
kinds of decisions in the exotic cases anyway.  The current request is a
case in point: I will admit that I had no idea what PHS was (let alone
PHS-MoU) until I went off to the Web site to check.  I wonder how many other
people on this list did?  In fact, I'm still not sure what, exactly, makes
it unique enough to require a separate number but (given that there are
3,999,999,965 of them left) I really don't care.

...



--
to unsubscribe send a message to 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 Aug  9 11:29:34 2008
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 CA9643A6DD2
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  9 Aug 2008 11:29:34 -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 3-ptR2cy+e34
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat,  9 Aug 2008 11:29:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B1F163A6DCB
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  9 Aug 2008 11:29:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KRt67-0000um-Bo
	for radiusext-data@psg.com; Sat, 09 Aug 2008 18:23:27 +0000
Received: from [76.96.30.24] (helo=QMTA02.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KRt63-0000uD-T3
	for radiusext@ops.ietf.org; Sat, 09 Aug 2008 18:23:25 +0000
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA02.emeryville.ca.mail.comcast.net with comcast
	id 0GqV1a00D17UAYkA2JPPKg; Sat, 09 Aug 2008 18:23:23 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA13.emeryville.ca.mail.comcast.net with comcast
	id 0JPK1a00124Kx1C8ZJPLtp; Sat, 09 Aug 2008 18:23:22 +0000
X-Authority-Analysis: v=1.0 c=1 a=rfS014n20X2wI5cVcEIA:9
 a=AkLyrAYA0DUvyE1EkO4Qyq1Pr6UA:4 a=tqucuuI3bnEA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com> <006601c8f915$f4055a00$dc100e00$@net> <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2> <002b01c8fa07$4236ecb0$c6a4c610$@net>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sat, 9 Aug 2008 14:23:33 -0400
Message-ID: <000c01c8fa4d$0a0d2ac0$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <002b01c8fa07$4236ecb0$c6a4c610$@net>
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycAASi42w
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> ...the difference between uranium-238 and u-235 certainly seems
> subtle to me (what's a couple of neutrons between friends? ;-)
> but is certainly not subtle to a modern physicist...

Sure.  However, if you need U-238, and get mislabeled U-235 by mistake, you
may not be satisfied.

> I wonder how many other people on this list did?

I did.

> In fact, I'm still not sure what, exactly, makes it unique enough
> to require a separate number but (given that there are 3,999,999,965
> of them left) I really don't care.

Would you care if, say a million of so of them were all assigned for "IEEE
Wireless"?  I'd find that horribly confusing.  All I'm looking for is enough
review to make sure that the naming is sufficiently clear such that "caveat
emptor" can reasonably apply.  Truth/accuracy in labeling.  If folks want to
get assignments for their "secret sauce" specialized flavors of ports, I
agree, there is no scarcity issue.  I think there is an accuracy of
nomenclature issue.  I don't think it's fair to require IANA to make that
judgment.



--
to unsubscribe send a message to 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 Aug 10 04:20:22 2008
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 E6F5D3A6A18
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 10 Aug 2008 04:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.369
X-Spam-Level: *
X-Spam-Status: No, score=1.369 tagged_above=-999 required=5 tests=[AWL=-0.794,
	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 CqNyUuZn56X0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 10 Aug 2008 04:20:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 676943A6A27
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 10 Aug 2008 04:20:20 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KS8rw-0000h0-RC
	for radiusext-data@psg.com; Sun, 10 Aug 2008 11:13:52 +0000
Received: from [76.96.30.16] (helo=QMTA01.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KS8rs-0000gW-VO
	for radiusext@ops.ietf.org; Sun, 10 Aug 2008 11:13:50 +0000
Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id 0bAQ1a0070cQ2SLA1bEDrm; Sun, 10 Aug 2008 11:14:13 +0000
Received: from gwzPC ([124.120.224.130])
	by OMTA10.emeryville.ca.mail.comcast.net with comcast
	id 0bCV1a00B2pRWGU8WbCwRU; Sun, 10 Aug 2008 11:13:15 +0000
X-Authority-Analysis: v=1.0 c=1 a=5gFTm4fYYh3RdGZSGlcA:9
 a=liT3Dkk5X_br3XeUxPFdXBAGB-MA:4 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com> <006601c8f915$f4055a00$dc100e00$@net> <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2> <002b01c8fa07$4236ecb0$c6a4c610$@net> <000c01c8fa4d$0a0d2ac0$fefea8c0@NEWTON603>
In-Reply-To: <000c01c8fa4d$0a0d2ac0$fefea8c0@NEWTON603>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sun, 10 Aug 2008 18:12:55 +0700
Message-ID: <000a01c8fada$19355800$4ba00800$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycAASi42wACM1RVA=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson writes:

> Glen Zorn writes...
> 
> > ...the difference between uranium-238 and u-235 certainly seems
> > subtle to me (what's a couple of neutrons between friends? ;-)
> > but is certainly not subtle to a modern physicist...
> 
> Sure.  However, if you need U-238, and get mislabeled U-235 by mistake,
> you
> may not be satisfied.
> 
> > I wonder how many other people on this list did?
> 
> I did.
> 
> > In fact, I'm still not sure what, exactly, makes it unique enough
> > to require a separate number but (given that there are 3,999,999,965
> > of them left) I really don't care.
> 
> Would you care if, say a million of so of them were all assigned for
> "IEEE
> Wireless"?  I'd find that horribly confusing.  All I'm looking for is
> enough
> review to make sure that the naming is sufficiently clear such that
> "caveat
> emptor" can reasonably apply.  

Since we're tripping the light fantastic here, the expert review process
falls apart with more than a few entries anyway (if there were only a
million port types it would take more than a month to _scan_ them @ 1/sec.,
8 hrs./day).  In fact, it may fall apart at 35, since a NAS-Port-Type was
assigned for PHS (AKA PIAFS) in RFC 2865...

...



--
to unsubscribe send a message to 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 Aug 10 05:33:50 2008
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 C66F43A6D31
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 10 Aug 2008 05:33:50 -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 2l+ltpwQw7HJ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 10 Aug 2008 05:33:49 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id BC3A03A6D43
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 10 Aug 2008 05:33:49 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KSA2p-000HeD-LZ
	for radiusext-data@psg.com; Sun, 10 Aug 2008 12:29:11 +0000
Received: from [76.96.30.16] (helo=QMTA01.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KSA2l-000HdN-SW
	for radiusext@ops.ietf.org; Sun, 10 Aug 2008 12:29:09 +0000
Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id 0bXx1a00A0cQ2SLA1cV7tm; Sun, 10 Aug 2008 12:29:07 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA10.emeryville.ca.mail.comcast.net with comcast
	id 0cUD1a00524Kx1C8WcUEGR; Sun, 10 Aug 2008 12:28:14 +0000
X-Authority-Analysis: v=1.0 c=1 a=QadW0hNMHbKtGOQq0zQA:9
 a=yN1-qJll83n0SiT28XRznZfVT1oA:4 a=tqucuuI3bnEA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808010108130.3452@internaut.com> <006601c8f915$f4055a00$dc100e00$@net> <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2> <002b01c8fa07$4236ecb0$c6a4c610$@net> <000c01c8fa4d$0a0d2ac0$fefea8c0@NEWTON603> <000a01c8fada$19355800$4ba00800$@net>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sun, 10 Aug 2008 08:29:20 -0400
Message-ID: <005201c8fae4$b7d05370$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <000a01c8fada$19355800$4ba00800$@net>
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycAASi42wACM1RVAAAsiLQA==
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> In fact, it may fall apart at 35, since a NAS-Port-Type was
> assigned for PHS (AKA PIAFS) in RFC 2865...

And your point is that Next Generation PHS is not sufficiently
differentiated from PHS?  I think I might agree, on the general principle
that "next generation" is always relative, and what do you call the sequel?

So you've made a concrete and useful contribution to expert review.
Congratulations!

We should probably request that IANA list this entry as "PHS-MOU" and not
"Next Generation PHS".

As long as the nomenclature is unambiguous and there is some reference to a
specification, standards forum, corporation or individual that can be
contacted by anyone who really wants to know "What is this port type,
exactly?", I think it's fine.



--
to unsubscribe send a message to 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 Aug 12 04:50:19 2008
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 F36D33A685D
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 12 Aug 2008 04:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.268
X-Spam-Level: 
X-Spam-Status: No, score=0.268 tagged_above=-999 required=5 tests=[AWL=0.705,
	BAYES_00=-2.599, 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 yf-C04G2tg5V
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 12 Aug 2008 04:50:18 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C9B293A67AB
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 12 Aug 2008 04:50:17 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KSsI4-000EGg-Kx
	for radiusext-data@psg.com; Tue, 12 Aug 2008 11:43:52 +0000
Received: from [76.96.30.64] (helo=QMTA07.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KSsI0-000EGF-SP
	for radiusext@ops.ietf.org; Tue, 12 Aug 2008 11:43:50 +0000
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id 1PS41a00417UAYkA7PjoPj; Tue, 12 Aug 2008 11:43:48 +0000
Received: from gwzPC ([124.120.229.221])
	by OMTA13.emeryville.ca.mail.comcast.net with comcast
	id 1Pj71a00P4nFC248ZPjWpK; Tue, 12 Aug 2008 11:43:42 +0000
X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=qVUFDw_wW08cc_UsBd4A:9
 a=A80jrtvHaJoNYvUcOeOzBAQvJg0A:4 a=9XSpoOj3B7kA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: no overall type in Extended Attributes
Date: Tue, 12 Aug 2008 18:42:28 +0700
Message-ID: <003b01c8fc70$8b64b9b0$a22e2d10$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj8cH7yvNkKOzRlSyubqA/JJgcYlQ==
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

As I mentioned a couple of times at the Dublin session, the current
definition of the Extended Attributes 
(http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-0
4.txt) doesn't in general allow the definition of an overall type for the
Attribute in question:  an Extended Attribute is basically just an unordered
set of TLVs.  This fact doesn't bother me much, if at all, but the second
time I mentioned it there was some grumbling from the crowd, so I thought
I'd bring it up one more time on the list...



--
to unsubscribe send a message to 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 Aug 12 05:44:56 2008
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 786783A6A80
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 12 Aug 2008 05:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.863
X-Spam-Level: 
X-Spam-Status: No, score=0.863 tagged_above=-999 required=5 tests=[AWL=1.300,
	BAYES_00=-2.599, 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 rA-KnNKtBgtJ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 12 Aug 2008 05:44:55 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 957183A6A65
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 12 Aug 2008 05:44:54 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KStAl-000K42-79
	for radiusext-data@psg.com; Tue, 12 Aug 2008 12:40:23 +0000
Received: from [76.96.30.40] (helo=QMTA04.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KStAh-000K3F-87
	for radiusext@ops.ietf.org; Tue, 12 Aug 2008 12:40:21 +0000
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
	by QMTA04.emeryville.ca.mail.comcast.net with comcast
	id 1Qf01a0060mlR8UA4QgJMQ; Tue, 12 Aug 2008 12:40:18 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA11.emeryville.ca.mail.comcast.net with comcast
	id 1QgH1a00S24Kx1C8XQgJTg; Tue, 12 Aug 2008 12:40:18 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=-FcEtz19Q9Xyk4uhV3IA:9
 a=_BZpySH8oPfx5alwRl-14eWRRQoA:4 a=tqucuuI3bnEA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <003b01c8fc70$8b64b9b0$a22e2d10$@net>
Subject: RE: no overall type in Extended Attributes
Date: Tue, 12 Aug 2008 08:40:18 -0400
Message-ID: <016201c8fc78$94551c60$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <003b01c8fc70$8b64b9b0$a22e2d10$@net>
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Acj8cH7yvNkKOzRlSyubqA/JJgcYlQABvSrg
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> ...the current definition of the Extended Attributes
> doesn't in general allow the definition of an overall type for the
> Attribute in question: an Extended Attribute is basically just an
> unordered set of TLVs.

In other words, the Extended Attribute is a "super attribute" or "wrapper
attribute" that contains other "attributes", which you refer to as "TLVs",
to distinguish them from standalone attributes.

The issue is that one cannot "name" any particular group of aggregated TLVs.
One solution is to simply add a Group-Name TLV to the Extended Attribute.
I'm not sure that addresses the intended use, however.  I suspect that the
use is to "call up" a pre-defined grouping by name.

I think I'd like to see some "real-world" examples of use cases discussed
here before I would want to attempt to make a decision on whether this is a
serious issue or not.



--
to unsubscribe send a message to 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 Aug 12 07:02:34 2008
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 B2DFD3A6B14
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 12 Aug 2008 07:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.118
X-Spam-Level: 
X-Spam-Status: No, score=-0.118 tagged_above=-999 required=5 tests=[AWL=0.319,
	BAYES_00=-2.599, 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 oeE4Fz5DXYtO
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 12 Aug 2008 07:02:29 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0CB923A6AEC
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 12 Aug 2008 07:02:29 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KSuNe-00029G-OV
	for radiusext-data@psg.com; Tue, 12 Aug 2008 13:57:46 +0000
Received: from [76.96.30.80] (helo=QMTA08.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KSuNX-00028G-K6
	for radiusext@ops.ietf.org; Tue, 12 Aug 2008 13:57:44 +0000
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id 1Qy11a0040FhH24A8RxfJo; Tue, 12 Aug 2008 13:57:39 +0000
Received: from gwzPC ([124.120.229.221])
	by OMTA08.emeryville.ca.mail.comcast.net with comcast
	id 1RwW1a0064nFC248URxHzk; Tue, 12 Aug 2008 13:57:34 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=No5EcEP4AAAA:8
 a=2Wvqr4D9JdvOMpXITsIA:9 a=7Nw6Me9CVtgLAoZS7fgA:7
 a=227_-mK-kDTrdXIYZl3wPm4YajcA:4 a=si9q_4b84H0A:10 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>
References: <003b01c8fc70$8b64b9b0$a22e2d10$@net> <016201c8fc78$94551c60$fefea8c0@NEWTON603>
In-Reply-To: <016201c8fc78$94551c60$fefea8c0@NEWTON603>
Subject: RE: no overall type in Extended Attributes
Date: Tue, 12 Aug 2008 20:55:50 +0700
Message-ID: <004201c8fc83$3b46a520$b1d3ef60$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj8cH7yvNkKOzRlSyubqA/JJgcYlQABvSrgAAKxtHA=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson <mailto://d.b.nelson@comcast.net>  writes:

> Glen Zorn writes...
> 
> > ...the current definition of the Extended Attributes
> > doesn't in general allow the definition of an overall type for the
> > Attribute in question: an Extended Attribute is basically just an
> > unordered set of TLVs.
> 
> In other words, the Extended Attribute is a "super attribute" or
> "wrapper
> attribute" that contains other "attributes", 

In other words, the Extended Attributes have the same qualities as RFC 2865
VSAs.

> which you refer to as
> "TLVs",
> to distinguish them from standalone attributes.
> 
> The issue is that one cannot "name" any particular group of aggregated
> TLVs.

I wouldn't call it an "issue" -- whether it's an issue is what is to be
determined.  It is a characteristic.

> One solution is to simply add a Group-Name TLV to the Extended
> Attribute.
> I'm not sure that addresses the intended use, however.  I suspect that
> the
> use is to "call up" a pre-defined grouping by name.

I don't know what use it would actually be, outside of making discussions of
the protocol a little easier.  It certainly doesn't modify the operation of
the protocol.

> 
> I think I'd like to see some "real-world" examples of use cases
> discussed
> here before I would want to attempt to make a decision on whether this
> is a
> serious issue or not.
> 
> 
> 
> --
> to unsubscribe send a message to 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 Aug 13 19:10:39 2008
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 0B91128C1EF
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 13 Aug 2008 19:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.185
X-Spam-Level: 
X-Spam-Status: No, score=-104.185 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4, 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 x66pT0UQB6Ez
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 13 Aug 2008 19:10:38 -0700 (PDT)
Received: from psg.com (psg.com [147.28.0.62])
	by core3.amsl.com (Postfix) with ESMTP id 19DFF28C1E9
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 13 Aug 2008 19:10:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTSEQ-000Ic2-5d
	for radiusext-data@psg.com; Thu, 14 Aug 2008 02:06:30 +0000
Received: from [63.208.196.178] (helo=mho-01-bos.mailhop.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <aboba@internaut.com>)
	id 1KTSEM-000Ibk-59
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:06:28 +0000
Received: from c-24-16-124-122.hsd1.mn.comcast.net ([24.16.124.122] helo=internaut.com)
	by mho-01-bos.mailhop.org with esmtpa (Exim 4.68)
	(envelope-from <aboba@internaut.com>)
	id 1KTSEL-0009pb-6U
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:06:25 +0000
Received: by internaut.com (Postfix, from userid 1001)
	id 5B20070CDB; Wed, 13 Aug 2008 19:06:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id 45C3470B42
	for <radiusext@ops.ietf.org>; Wed, 13 Aug 2008 19:06:24 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.124.122
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+maafDDifUpF86MQNH5XCC
Date: Wed, 13 Aug 2008 19:06:24 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Message-ID: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a reminder of the RADEXT WG Last Call on "Extended 
RADIUS Attributes", prior to requesting that the IESG publish it as a Proposed Standard. 
 
The document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-04.txt
 
WG Last Call was originally to have completed on August 10, 2008.   
However, due to lack of response to the RADEXT WG last call, 
we will be extending the WG last call to August 31, 2008.  Please 
review the document and post your comments to the RADEXT WG mailing list 
(radiusext@ops.ietf.org) in the format described on the RADEXT WG Issues 
list (http://www.drizzle.com/~aboba/RADEXT/).   
 
If you have read the document and approve of its publication, but have no
comments, please also post this to the list. 

--
to unsubscribe send a message to 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 Aug 13 19:10:39 2008
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 B36A728C1E5
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 13 Aug 2008 19:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5
	tests=[AWL=-1.874, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=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 sW+QCqSjc3g5
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 13 Aug 2008 19:10:39 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E10A628C1EE
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 13 Aug 2008 19:10:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTSEp-000IeE-T2
	for radiusext-data@psg.com; Thu, 14 Aug 2008 02:06:55 +0000
Received: from [63.208.196.179] (helo=mho-02-bos.mailhop.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <aboba@internaut.com>)
	id 1KTSEl-000IdY-B0
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:06:53 +0000
Received: from c-24-16-124-122.hsd1.mn.comcast.net ([24.16.124.122] helo=internaut.com)
	by mho-02-bos.mailhop.org with esmtpa (Exim 4.68)
	(envelope-from <aboba@internaut.com>)
	id 1KTSEk-000Anc-BS
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:06:50 +0000
Received: by internaut.com (Postfix, from userid 1001)
	id AA09670CDB; Wed, 13 Aug 2008 19:06:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id 9CACD70B42
	for <radiusext@ops.ietf.org>; Wed, 13 Aug 2008 19:06:49 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.124.122
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/3A6m29h7Naj9fwTst32tr
Date: Wed, 13 Aug 2008 19:06:49 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: REMINDER: Request for Minutes, Slides
Message-ID: <Pine.LNX.4.64.0808131906300.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

If you took minutes at the RADEXT WG meeting at IETF 72, please send them 
to me (Bernard_Aboba@hotmail.com) and/or Dave Nelson. 

Also, if you presented and did not send slides, please do so. 

--
to unsubscribe send a message to 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 Aug 13 19:10:48 2008
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 2215F28C1E7
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 13 Aug 2008 19:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5
	tests=[AWL=-0.937, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=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 qRCLLux31f9k
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 13 Aug 2008 19:10:47 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 370A328C1E9
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 13 Aug 2008 19:10:47 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTSDu-000IZn-Sh
	for radiusext-data@psg.com; Thu, 14 Aug 2008 02:05:58 +0000
Received: from [63.208.196.179] (helo=mho-02-bos.mailhop.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <aboba@internaut.com>)
	id 1KTSDn-000IZ5-3h
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:05:56 +0000
Received: from c-24-16-124-122.hsd1.wa.comcast.net ([24.16.124.122] helo=internaut.com)
	by mho-02-bos.mailhop.org with esmtpa (Exim 4.68)
	(envelope-from <aboba@internaut.com>)
	id 1KTSDl-000AKY-B6
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:05:49 +0000
Received: by internaut.com (Postfix, from userid 1001)
	id 5C59770CDB; Wed, 13 Aug 2008 19:05:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id 4C16570B42
	for <radiusext@ops.ietf.org>; Wed, 13 Aug 2008 19:05:48 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.124.122
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18xd0ut9+BOaY/6pYwRTSl3
Date: Wed, 13 Aug 2008 19:05:48 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for
 RADIUS"
Message-ID: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a reminder of the ongoing RADEXT WG Last Call on "Crypto-Agility 
Requirements for RADIUS" prior to requesting that the IESG publish it as 
an Informational RFC. 
 
The document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-crypto-agility-requirements-00.txt
 
WG Last Call was to have lasted until August 10, 2008.   Since there 
have been no comments posted yet, we will extend the last call for 
another two weeks (until August 31, 2008).  Please 
review the document and post your comments to the RADEXT WG mailing list 
(radiusext@ops.ietf.org) in the format described on the RADEXT WG Issues 
list (http://www.drizzle.com/~aboba/RADEXT/).   
 
If you have read the document and approve of its publication, but have no
comments, please also post this to the list. 

--
to unsubscribe send a message to 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 Aug 13 19:12:05 2008
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 22CE828C1E8
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 13 Aug 2008 19:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.143
X-Spam-Level: 
X-Spam-Status: No, score=-104.143 tagged_above=-999 required=5
	tests=[AWL=2.456, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	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 9swNd-leDay4
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 13 Aug 2008 19:12:04 -0700 (PDT)
Received: from psg.com (psg.com [147.28.0.62])
	by core3.amsl.com (Postfix) with ESMTP id 4F37828C1EA
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 13 Aug 2008 19:11:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTSGs-000IrY-Ri
	for radiusext-data@psg.com; Thu, 14 Aug 2008 02:09:02 +0000
Received: from [63.208.196.179] (helo=mho-02-bos.mailhop.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <aboba@internaut.com>)
	id 1KTSGp-000Ir2-D4
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:09:01 +0000
Received: from c-24-16-124-122.hsd1.wa.comcast.net ([24.16.124.122] helo=internaut.com)
	by mho-02-bos.mailhop.org with esmtpa (Exim 4.68)
	(envelope-from <aboba@internaut.com>)
	id 1KTSGn-000BZb-TS
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:08:58 +0000
Received: by internaut.com (Postfix, from userid 1001)
	id 3E72270CDB; Wed, 13 Aug 2008 19:08:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id 30F2C70B42
	for <radiusext@ops.ietf.org>; Wed, 13 Aug 2008 19:08:57 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.124.122
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/1DcWRJ0oihcfr02s7G/Cz
Date: Wed, 13 Aug 2008 19:08:57 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Message-ID: <Pine.LNX.4.64.0808131907000.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.

	Title           : New Tunnel-Type Values
	Author(s)       : A. Tiwari
	Filename        : draft-tiwari-radext-tunnel-type-01.txt
	Pages           : 6
	Date            : 2008-08-10

This document defines a set of values for the Tunnel-Type RADIUS
Attribute.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-type-01.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.

<ftp://ftp.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-type-01.txt>

--
to unsubscribe send a message to 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 Aug 13 19:22:53 2008
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 69A2928C102
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 13 Aug 2008 19:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.808
X-Spam-Level: 
X-Spam-Status: No, score=0.808 tagged_above=-999 required=5 tests=[AWL=-3.723,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	MANGLED_GIRL=2.3, MANGLED_PILL=2.3, RDNS_NONE=0.1, URI_HEX=0.368]
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 Uo6WR34JqHJR
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 13 Aug 2008 19:22:52 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1A14D3A6990
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 13 Aug 2008 19:22:52 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTSQj-000Jax-QJ
	for radiusext-data@psg.com; Thu, 14 Aug 2008 02:19:13 +0000
Received: from [63.208.196.179] (helo=mho-02-bos.mailhop.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <aboba@internaut.com>)
	id 1KTSQf-000Jab-Uo
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:19:11 +0000
Received: from c-24-16-124-122.hsd1.mn.comcast.net ([24.16.124.122] helo=internaut.com)
	by mho-02-bos.mailhop.org with esmtpa (Exim 4.68)
	(envelope-from <aboba@internaut.com>)
	id 1KTSQe-000FXw-K4
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 02:19:09 +0000
Received: by internaut.com (Postfix, from userid 1001)
	id 537EE70CDB; Wed, 13 Aug 2008 19:19:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id 45E2370C53
	for <radiusext@ops.ietf.org>; Wed, 13 Aug 2008 19:19:07 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.124.122
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+9RTmFxYfK+l/8lta0k9xW
Date: Wed, 13 Aug 2008 19:19:07 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
Message-ID: <Pine.LNX.4.64.0808131912120.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn said:

"As I mentioned a couple of times at the Dublin session, the current
definition of the Extended Attributes 
(http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-0
4.txt) doesn't in general allow the definition of an overall type for the
Attribute in question:  an Extended Attribute is basically just an 
unordered set of TLVs.  This fact doesn't bother me much, if at all, but 
the second time I mentioned it there was some grumbling from the crowd, so 
I thought I'd bring it up one more time on the list..."

One question is how the grouping semantic differs from that of Diameter 
(RFC 3588), and what the impact is.  Looking at RFC 3588, it does seem 
that the agbility to name and define a Grouped AVP has some advantages. 

For example, it enables a formal definition of the grouped AVP, including 
a grammar.  Without this, it is possible that the loose semantics would affect 
interoperability (e.g. arbitrary attribute groupings might not be 
supported understood).  

>From RFC 3588 Section 4.4:

4.4.  Grouped AVP Values

   The Diameter protocol allows AVP values of type 'Grouped.'  This
   implies that the Data field is actually a sequence of AVPs.  It is
   possible to include an AVP with a Grouped type within a Grouped type,
   that is, to nest them.  AVPs within an AVP of type Grouped have the
   same padding requirements as non-Grouped AVPs, as defined in Section
   4.

   The AVP Code numbering space of all AVPs included in a Grouped AVP is
   the same as for non-grouped AVPs.  Further, if any of the AVPs
   encapsulated within a Grouped AVP has the 'M' (mandatory) bit set,
   the Grouped AVP itself MUST also include the 'M' bit set.

   Every Grouped AVP defined MUST include a corresponding grammar, using
   ABNF [ABNF] (with modifications), as defined below.

      grouped-avp-def  = name "::=" avp

      name-fmt         = ALPHA *(ALPHA / DIGIT / "-")

      name             = name-fmt
                         ; The name has to be the name of an AVP,
                         ; defined in the base or extended Diameter
                         ; specifications.

      avp              = header  [ *fixed] [ *required] [ *optional]
                         [ *fixed]

      header           = "<" "AVP-Header:" avpcode [vendor] ">"

      avpcode          = 1*DIGIT
                         ; The AVP Code assigned to the Grouped AVP

      vendor           = 1*DIGIT
                         ; The Vendor-ID assigned to the Grouped AVP.
                         ; If absent, the default value of zero is
                         ; used.

4.4.1.  Example AVP with a Grouped Data type

   The Example-AVP (AVP Code 999999) is of type Grouped and is used to
   clarify how Grouped AVP values work.  The Grouped Data field has the
   following ABNF grammar:

      Example-AVP  ::= < AVP Header: 999999 >
                       { Origin-Host }
                     1*{ Session-Id }
                      *[ AVP ]

   An Example-AVP with Grouped Data follows.

   The Origin-Host AVP is required (Section 6.3).  In this case:

      Origin-Host = "example.com".

   One or more Session-Ids must follow.  Here there are two:

      Session-Id =
        "grump.example.com:33041;23432;893;0AF3B81"

      Session-Id =
        "grump.example.com:33054;23561;2358;0AF3B82"

   optional AVPs included are

      Recovery-Policy = <binary>
         2163bc1d0ad82371f6bc09484133c3f09ad74a0dd5346d54195a7cf0b35
         2cabc881839a4fdcfbc1769e2677a4c1fb499284c5f70b48f58503a45c5
         c2d6943f82d5930f2b7c1da640f476f0e9c9572a50db8ea6e51e1c2c7bd
         f8bb43dc995144b8dbe297ac739493946803e1cee3e15d9b765008a1b2a
         cf4ac777c80041d72c01e691cf751dbf86e85f509f3988e5875dc905119
         26841f00f0e29a6d1ddc1a842289d440268681e052b30fb638045f7779c
         1d873c784f054f688f5001559ecff64865ef975f3e60d2fd7966b8c7f92

      Futuristic-Acct-Record = <binary>
         fe19da5802acd98b07a5b86cb4d5d03f0314ab9ef1ad0b67111ff3b90a0
         57fe29620bf3585fd2dd9fcc38ce62f6cc208c6163c008f4258d1bc88b8
         17694a74ccad3ec69269461b14b2e7a4c111fb239e33714da207983f58c
         41d018d56fe938f3cbf089aac12a912a2f0d1923a9390e5f789cb2e5067
         d3427475e49968f841

   The data for the optional AVPs is represented in hex since the format
   of these AVPs is neither known at the time of definition of the
   Example-AVP group, nor (likely) at the time when the example instance
   of this AVP is interpreted - except by Diameter implementations which
   support the same set of AVPs.  The encoding example illustrates how
   padding is used and how length fields are calculated.  Also note that
   AVPs may be present in the Grouped AVP value which the receiver
   cannot interpret (here, the Recover-Policy and Futuristic-Acct-Record
   AVPs).

   This AVP would be encoded as follows:

           0       1       2       3       4       5       6       7
       +-------+-------+-------+-------+-------+-------+-------+-------+
     0 |     Example AVP Header (AVP Code = 999999), Length = 468      |
       +-------+-------+-------+-------+-------+-------+-------+-------+
     8 |     Origin-Host AVP Header (AVP Code = 264), Length = 19      |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    16 |  'e'  |  'x'  |  'a'  |  'm'  |  'p'  |  'l'  |  'e'  |  '.'  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    24 |  'c'  |  'o'  |  'm'  |Padding|     Session-Id AVP Header     |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    32 | (AVP Code = 263), Length = 50 |  'g'  |  'r'  |  'u'  |  'm'  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
    64 |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '1'  |Padding|Padding|
       +-------+-------+-------+-------+-------+-------+-------+-------+
    72 |     Session-Id AVP Header (AVP Code = 263), Length = 51       |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    80 |  'g'  |  'r'  |  'u'  |  'm'  |  'p'  |  '.'  |  'e'  |  'x'  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
   104 |  '0'  |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '2'  |Padding|
       +-------+-------+-------+-------+-------+-------+-------+-------+
   112 |   Recovery-Policy Header (AVP Code = 8341), Length = 223      |
       +-------+-------+-------+-------+-------+-------+-------+-------+
   120 |  0x21 | 0x63  | 0xbc  | 0x1d  | 0x0a  | 0xd8  | 0x23  | 0x71  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
   320 |  0x2f | 0xd7  | 0x96  | 0x6b  | 0x8c  | 0x7f  | 0x92  |Padding|
       +-------+-------+-------+-------+-------+-------+-------+-------+
   328 | Futuristic-Acct-Record Header (AVP Code = 15930), Length = 137|
       +-------+-------+-------+-------+-------+-------+-------+-------+
   336 |  0xfe | 0x19  | 0xda  | 0x58  | 0x02  | 0xac  | 0xd9  | 0x8b  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
   464 |  0x41 |Padding|Padding|Padding|
       +-------+-------+-------+-------+





--
to unsubscribe send a message to 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 Aug 14 02:34:54 2008
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 5387F3A6952
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 02:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.105
X-Spam-Level: 
X-Spam-Status: No, score=0.105 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	J_CHICKENPOX_31=0.6, 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 BunZWrSE9-EP
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 02:34:53 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id CAF263A686B
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 02:34:52 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTZ8Y-0000Ln-RP
	for radiusext-data@psg.com; Thu, 14 Aug 2008 09:28:54 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KTZ8U-0000LJ-PB
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 09:28:52 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 56C9A123423B
	for <radiusext@ops.ietf.org>; Thu, 14 Aug 2008 11:28:47 +0200 (CEST)
Message-ID: <48A3FAA1.1020109@deployingradius.com>
Date: Thu, 14 Aug 2008 11:28:01 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
X-Enigmail-Version: 0.95.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:
> This is a reminder of the RADEXT WG Last Call on "Extended 
> RADIUS Attributes", prior to requesting that the IESG publish it as a Proposed Standard. 

Submitter name: Alan DeKok
Submitter email address: aland@deployingradius.com
Date first submitted: Aug 14 2008
Reference:
Document: [EXTEN]
Comment type: T
Priority: 2

Section 4:
...
   o  The final octet of the header contains the More flag and Tag
      field.  If the one bit More flag is set (1) this indicates that
      the encapsulated TLV is continued in the following Extended
      Attribute; if the More flag is clear (0) then all of the
      encapsulated TLVs fit into the current Extended Attribute.  The
      More flag MUST NOT be set if the Extended Attribute contains more
      than one TLV.

  To be clear: this means that the Extended-Attribute can encapsulate
multiple TLV's if they're short, or only one TLV if it's long.


Section 5:

   M (More)

      The More Flag is one (1) bit in length and MUST be present.  When
      a value to be transmitted exceeds 246 octets in length it is
      fragmented over two or more Extended Attributes.  If the More Flag
      is set (1), this indicates that the Value field of the Extended
      Attribute contains a fragment of a larger value, which is
      continued in the next Extended Attribute of the same Ext-Type.

  Can we add a MUST?  i.e. If the More Flag is set, the next attribute
MUST be an Extended-Attribute of the same Extended-Type.

  Inserting *other* attributes in between a fragemented attribute is
annoying and pointless.  It's better to forbid this, and to declare that
packets failing this test are malformed, and SHOULD be silently discarded.

   Ext-Type

      Two (2) octets.  Up-to-date values of the Ext-Type field are
      specified in the most recent "Assigned Numbers" [IANA].  Values
      XXXX-YYYY are reserved.

  I would suggest reserving the top 1K: 64512-65535

6.  Examples

   Consider an attribute called Foo of type String.  Foo has been
   allocated an Extended-Type 0f 257 by IANA.  The following figure
   shows the encoding of Foo(0,4) = "Hello":

  What does "Foo(0,4)" mean?  This is the first reference in that
document to that attribute naming scheme.  (I presume it's an attribute
naming scheme).  Why not just refer to it as "Foo"?

  The diagram also has Ext-Type (16 bits) of 257 split between two bytes
(8 bits) of 0 and 257.  I welcome the novel ability to count to 257 in
an 8-bit field, but perhaps this could be corrected. :)

  The examples should use numbers from the reserved space (i.e. 64512),
and not from the IANA allocated space (257).  The examples also use the
attribute name "Foo" multiple times.  It should instead use unique names.

   Figure 2 below
   illustrates the encoding of the first 7 octets of the first Extended
   Attribute (Foo(0,6) = "Hello W"), while Figure 3 shows how the second
   attribute (Foo(246,250) = "e end.") is encoded.

  Hmm... So Foo(N,M) is a reference to the fragments?  I don't see why
this is necessary.  We don't do it for EAP-Message.  I would suggest
just referring to it as "Foo", and "the first fragment (octets 0 through
245)", and "the second fragment (octets 246 through 250).

...
   Consider the following structure:

     struct
       Integer a;
       String  b;
       Integer c;
     endStruct

  What syntax is this?  I think I understand it, but I'm not sure
everyone will come to a shared understanding.  Maybe instead the example
can be given by reference to existing RADIUS data types.  e.g. A
structure of RADIUS data types (integer, text, integer) would previously
have to be encoded as three separate and independent attributes.  Here,
it can be encoded as 3 attributes sharing a common tag.

  Reading the rest of the example, I find the b(4,5) syntax very
awkward.  I suggest discarding it, and just referring to the diagrams.

  The examples could also given broken-out hex encoding of the
attributes, which may be clearer than the ASCII art diagrams.  e.g.

  1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f

7.  Security Considerations

   I suggest adding a note that a new attribute encoding is an
opportunity for buffer overflows, inadequate checks, etc.  Implementors
SHOULD take care to validate the lengths, etc. before decoding the
contents of the attributes.

8.  IANA Considerations
...
   It also requires that IANA set up a new registry for the RADIUS
   Extended Attribute Types.

  I suggest leaving the first 0..255 attributes as unallocated, in order
to avoid confusion with legacy RADIUS attributes.


9.  Open Issues

   What is the numbering scheme for attributes that will be used by RFC
   writers going forward?  For example today we write user-name(1).

  Uh... We do?  I've never seen that in an RFC.  I suggest deleting this
section entirely.

  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 Aug 14 03:00:27 2008
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 DBE4E3A6B40
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 03:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.08
X-Spam-Level: 
X-Spam-Status: No, score=-1.08 tagged_above=-999 required=5 tests=[AWL=-0.032,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, 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 ak70RSBZvxCe
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 03:00:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D59B33A6B2E
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 03:00:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTZZU-0002wM-Ni
	for radiusext-data@psg.com; Thu, 14 Aug 2008 09:56:44 +0000
Received: from [158.64.1.34] (helo=legolas.restena.lu)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <stefan.winter@restena.lu>)
	id 1KTZZQ-0002vg-GO
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 09:56:42 +0000
Received: from legolas.restena.lu (localhost [127.0.0.1])
	by legolas.restena.lu (Postfix) with ESMTP id 6C33EB8B2B;
	Thu, 14 Aug 2008 11:56:39 +0200 (CEST)
Received: from [158.64.1.155] (aragorn.restena.lu [158.64.1.155])
	by legolas.restena.lu (Postfix) with ESMTPA id 5CC58B8A25;
	Thu, 14 Aug 2008 11:56:39 +0200 (CEST)
Message-ID: <48A40157.2050706@restena.lu>
Date: Thu, 14 Aug 2008 11:56:39 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hello,

a few comments:

TLV encoding and M flag: All examples stuff the maximum payload into the first fragment, set the M bit and put the remainder into the next fragment. This is fine and sensible, but not enforced in the description.
One might also do any other split of the data, like if there is a 300 byte data to be transmitted, 150 in the first fragment, 150 in the second.
There also is no clarification whether fragmenting should only occur when it is needed. Without requiring this, a compliant implementation could as well split the 5-byte data "Hello" into five fragments. I suggest to add a bit of wording to strongly discourage that.

TLV encoding rules: Ext-Length field misses its unit ... (in octets)...

Example in Figure 3: VSA Length. 7 + 9 = 16, not 15.

Figure 4: 

- is it worth mentioning that this encoding is not the only one possible, since the order of the struct members doesn't need to be preserved during marshalling? 

- There is a one-off in the encoding of String b. b is 251 octets, i.e. comprised of b[0] thru b[250].
The first fragment can (correct in the figure) hold up to 245 characters, i.e b[0] thru b[244]. Six(!) characters remain, b[245] thru b[250]. The encoding of the second fragment needs to be changed for a TLV data length of 6, which also changes Ext-Length to 3 + 6 = 9 and VSA-Length to 7 + 9 + 7 = 23. The byte-order of the last integer is odd, it looks like the last two bytes are swapped. This is neither big- not little-endian, and I suspect it's an error.
A corrected figure is below:

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type (26)   |    Length     |          Vendor-Id
   |               |  (7+9+7=23)   |             (0)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           Vendor-Id (cont)        |M|    Tag      |    Ext-Type
                 (0)               |0|    (42)     |      (0)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    Ext-Type (cont)|   Ext-Length  |     Value     |               |
         (259)     |   (3 + 6 = 9) |      (e)      |      ( )      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |               |               |    
   |      (e)      |      (n)      |      (d)      |      (.)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    Ext-Type (cont) Ext-type (cont)|   Ext-Length  |               |
         (0)             (271)     |   (3 + 4 = 7) |    (0x12)     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |               |               |
   |    (0x34)     |     (0x56)    |     (0x78)    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Some nitbits: 

- Intro: "101 or so have been". Or so sound a bit colloquial.
- first example: "Extended-Type *of* 257 by IANA." ( not 0f)

Finally, Security Considerations: This section is rather short, I suggest to expand the "TBD" :-)

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to 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 Aug 14 03:10:35 2008
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 546D73A6D78
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 03:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.076
X-Spam-Level: 
X-Spam-Status: No, score=-1.076 tagged_above=-999 required=5
	tests=[AWL=-0.028, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	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 ZhrFkzD2LYI1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 03:10:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 76F293A6C28
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 03:10:34 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTZk5-00043j-0q
	for radiusext-data@psg.com; Thu, 14 Aug 2008 10:07:41 +0000
Received: from [158.64.1.34] (helo=legolas.restena.lu)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <stefan.winter@restena.lu>)
	id 1KTZk0-000437-2z
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 10:07:38 +0000
Received: from legolas.restena.lu (localhost [127.0.0.1])
	by legolas.restena.lu (Postfix) with ESMTP id 3B2DFB8B2F
	for <radiusext@ops.ietf.org>; Thu, 14 Aug 2008 12:07:35 +0200 (CEST)
Received: from [158.64.1.155] (aragorn.restena.lu [158.64.1.155])
	by legolas.restena.lu (Postfix) with ESMTPA id 2E04BB06FC
	for <radiusext@ops.ietf.org>; Thu, 14 Aug 2008 12:07:35 +0200 (CEST)
Message-ID: <48A403E7.1030000@restena.lu>
Date: Thu, 14 Aug 2008 12:07:35 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu>
In-Reply-To: <48A40157.2050706@restena.lu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

 > A corrected figure is below:

Oh well. Add a line-break at the obvious place.

Stefan


-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to 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 Aug 14 03:44:03 2008
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 849993A6B40
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 03:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.195
X-Spam-Level: 
X-Spam-Status: No, score=-0.195 tagged_above=-999 required=5 tests=[AWL=0.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 Z52XhblixWzv
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 03:44:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 77C1B3A68BE
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 03:44:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTaFf-0006yk-KP
	for radiusext-data@psg.com; Thu, 14 Aug 2008 10:40:19 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KTaFb-0006y9-OX
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 10:40:17 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 8499C123423B
	for <radiusext@ops.ietf.org>; Thu, 14 Aug 2008 12:40:14 +0200 (CEST)
Message-ID: <48A40B60.6010303@deployingradius.com>
Date: Thu, 14 Aug 2008 12:39:28 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu>
In-Reply-To: <48A40157.2050706@restena.lu>
X-Enigmail-Version: 0.95.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>

Stefan Winter wrote:
> One might also do any other split of the data, like if there is a 300
> byte data to be transmitted, 150 in the first fragment, 150 in the second.
> There also is no clarification whether fragmenting should only occur
> when it is needed. Without requiring this, a compliant implementation
> could as well split the 5-byte data "Hello" into five fragments. I
> suggest to add a bit of wording to strongly discourage that.

  I would say:

  The More Flag MUST NOT be set if the Length is less than 255.

> - is it worth mentioning that this encoding is not the only one
> possible, since the order of the struct members doesn't need to be
> preserved during marshalling?

  Yes.  Attributes don't have order in RADIUS.

  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 Aug 14 04:14:56 2008
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 17A883A6DB0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 04:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=0.274,
	BAYES_00=-2.599, 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 5FSfOqYu-pWW
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 04:14:55 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2CA4D3A6DA3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 04:14:55 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTajQ-000BCx-AK
	for radiusext-data@psg.com; Thu, 14 Aug 2008 11:11:04 +0000
Received: from [76.96.30.17] (helo=QMTA10.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTajM-000BCL-SG
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 11:11:02 +0000
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id 2ACS1a0050FhH24AABB02N; Thu, 14 Aug 2008 11:11:00 +0000
Received: from gwzPC ([124.120.216.202])
	by OMTA08.emeryville.ca.mail.comcast.net with comcast
	id 2BAZ1a00K4NbUxY8UBApbm; Thu, 14 Aug 2008 11:10:58 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=mBW5SjzQz0sIHFtvxzkA:9 a=i1AjARogfm7lHuS5l0oZr17v9_kA:4 a=ufO146cb3fEA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Stefan Winter'" <stefan.winter@restena.lu>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu>
In-Reply-To: <48A40157.2050706@restena.lu>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 18:10:19 +0700
Message-ID: <000701c8fdfe$5e220ef0$1a662cd0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj99HP/tjdafrPARXuHUs1IJ4c0YgACReoA
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Stefan Winter <mailto://stefan.winter@restena.lu> writes:

> Hello,
> 
> a few comments:
> 
> TLV encoding and M flag: All examples stuff the maximum payload into
> the first fragment, set the M bit and put the remainder into the next
> fragment. This is fine and sensible, but not enforced in the
> description.
> One might also do any other split of the data, like if there is a 300
> byte data to be transmitted, 150 in the first fragment, 150 in the
> second.
> There also is no clarification whether fragmenting should only occur
> when it is needed. Without requiring this, a compliant implementation
> could as well split the 5-byte data "Hello" into five fragments. I
> suggest to add a bit of wording to strongly discourage that.

Maybe just put a note like "If you are a total moron, stop reading now." in
the Abstract?

...

> Finally, Security Considerations: This section is rather short, I
> suggest to expand the "TBD" :-)

Text is welcome.

...



--
to unsubscribe send a message to 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 Aug 14 04:32:17 2008
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 BC8123A6DAE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 04:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.287
X-Spam-Level: **
X-Spam-Status: No, score=2.287 tagged_above=-999 required=5 tests=[AWL=-2.244,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	MANGLED_GIRL=2.3, MANGLED_PILL=2.3, RDNS_NONE=0.1, URI_HEX=0.368]
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 6A9mmnyEQMV1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 04:32:16 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6DF863A6D83
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 04:32:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTazq-000Che-2d
	for radiusext-data@psg.com; Thu, 14 Aug 2008 11:28:02 +0000
Received: from [76.96.62.56] (helo=QMTA06.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTazl-000ChE-53
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 11:27:59 +0000
Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28])
	by QMTA06.westchester.pa.mail.comcast.net with comcast
	id 2A7T1a00A0cZkys56BTwxu; Thu, 14 Aug 2008 11:27:56 +0000
Received: from gwzPC ([124.120.216.202])
	by OMTA10.westchester.pa.mail.comcast.net with comcast
	id 2BT71a0064NbUxY3WBTa7s; Thu, 14 Aug 2008 11:27:51 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=48vgC7mUAAAA:8
 a=No5EcEP4AAAA:8 a=6ne5XP7cBmWQdK5BIDAA:9 a=I0khd97O76JwJaLYVfUA:7
 a=ZT4ZnDRJQ-EKPIAEOuynH7a76OsA:4 a=hodff89a88cA:10 a=Y6qChIQXU1wA:10
 a=zoKOyUDlhksA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808131912120.24114@internaut.com>
Subject: RE: no overall type in Extended Attributes
Date: Thu, 14 Aug 2008 18:26:49 +0700
Message-ID: <000801c8fe00$b50248a0$1f06d9e0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9tI9KOI7i58ewR6q8qn9+WmSnywASr9SQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba <mailto://aboba@internaut.com> writes:

> Glen Zorn said:
> 
> "As I mentioned a couple of times at the Dublin session, the current
> definition of the Extended Attributes
> (http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> attributes-0
> 4.txt) doesn't in general allow the definition of an overall type for
> the
> Attribute in question:  an Extended Attribute is basically just an
> unordered set of TLVs.  This fact doesn't bother me much, if at all,
> but
> the second time I mentioned it there was some grumbling from the crowd,
> so
> I thought I'd bring it up one more time on the list..."
> 
> One question is how the grouping semantic differs from that of Diameter
> (RFC 3588), and what the impact is.  Looking at RFC 3588, it does seem
> that the agbility to name and define a Grouped AVP has some advantages.

Perhaps, but it also has disadvantages (such as the awkwardness of defining
new AVPs for simple, ad-hoc situations.

> 
> For example, it enables a formal definition of the grouped AVP,
> including
> a grammar.  

It's not clear that this is actually an advantage: a large majority of the
confusion I've seen reported by Diameter developers has been caused by ABNF.


> Without this, it is possible that the loose semantics would
> affect
> interoperability (e.g. arbitrary attribute groupings might not be
> supported understood).

I don't see how this could happen except for essentially the same reasons as
in Diameter (despite the over-specification of the protocol).  From your
quotation of RFC 3588 below:

'The data for the optional AVPs is represented in hex since the format of
these AVPs is neither known at the time of definition of the Example-AVP
group, nor (likely) at the time when the example instance of this AVP is
interpreted - except by Diameter implementations which support the same set
of AVPs...note that AVPs may be present in the Grouped AVP value which the
receiver cannot interpret...'

> 
> From RFC 3588 Section 4.4:
> 
> 4.4.  Grouped AVP Values
> 
>    The Diameter protocol allows AVP values of type 'Grouped.'  This
>    implies that the Data field is actually a sequence of AVPs.  It is
>    possible to include an AVP with a Grouped type within a Grouped
> type,
>    that is, to nest them.  AVPs within an AVP of type Grouped have the
>    same padding requirements as non-Grouped AVPs, as defined in Section
>    4.
> 
>    The AVP Code numbering space of all AVPs included in a Grouped AVP
> is
>    the same as for non-grouped AVPs.  Further, if any of the AVPs
>    encapsulated within a Grouped AVP has the 'M' (mandatory) bit set,
>    the Grouped AVP itself MUST also include the 'M' bit set.
> 
>    Every Grouped AVP defined MUST include a corresponding grammar,
> using
>    ABNF [ABNF] (with modifications), as defined below.
> 
>       grouped-avp-def  = name "::=" avp
> 
>       name-fmt         = ALPHA *(ALPHA / DIGIT / "-")
> 
>       name             = name-fmt
>                          ; The name has to be the name of an AVP,
>                          ; defined in the base or extended Diameter
>                          ; specifications.
> 
>       avp              = header  [ *fixed] [ *required] [ *optional]
>                          [ *fixed]
> 
>       header           = "<" "AVP-Header:" avpcode [vendor] ">"
> 
>       avpcode          = 1*DIGIT
>                          ; The AVP Code assigned to the Grouped AVP
> 
>       vendor           = 1*DIGIT
>                          ; The Vendor-ID assigned to the Grouped AVP.
>                          ; If absent, the default value of zero is
>                          ; used.
> 
> 4.4.1.  Example AVP with a Grouped Data type
> 
>    The Example-AVP (AVP Code 999999) is of type Grouped and is used to
>    clarify how Grouped AVP values work.  The Grouped Data field has the
>    following ABNF grammar:
> 
>       Example-AVP  ::= < AVP Header: 999999 >
>                        { Origin-Host }
>                      1*{ Session-Id }
>                       *[ AVP ]
> 
>    An Example-AVP with Grouped Data follows.
> 
>    The Origin-Host AVP is required (Section 6.3).  In this case:
> 
>       Origin-Host = "example.com".
> 
>    One or more Session-Ids must follow.  Here there are two:
> 
>       Session-Id =
>         "grump.example.com:33041;23432;893;0AF3B81"
> 
>       Session-Id =
>         "grump.example.com:33054;23561;2358;0AF3B82"
> 
>    optional AVPs included are
> 
>       Recovery-Policy = <binary>
>          2163bc1d0ad82371f6bc09484133c3f09ad74a0dd5346d54195a7cf0b35
>          2cabc881839a4fdcfbc1769e2677a4c1fb499284c5f70b48f58503a45c5
>          c2d6943f82d5930f2b7c1da640f476f0e9c9572a50db8ea6e51e1c2c7bd
>          f8bb43dc995144b8dbe297ac739493946803e1cee3e15d9b765008a1b2a
>          cf4ac777c80041d72c01e691cf751dbf86e85f509f3988e5875dc905119
>          26841f00f0e29a6d1ddc1a842289d440268681e052b30fb638045f7779c
>          1d873c784f054f688f5001559ecff64865ef975f3e60d2fd7966b8c7f92
> 
>       Futuristic-Acct-Record = <binary>
>          fe19da5802acd98b07a5b86cb4d5d03f0314ab9ef1ad0b67111ff3b90a0
>          57fe29620bf3585fd2dd9fcc38ce62f6cc208c6163c008f4258d1bc88b8
>          17694a74ccad3ec69269461b14b2e7a4c111fb239e33714da207983f58c
>          41d018d56fe938f3cbf089aac12a912a2f0d1923a9390e5f789cb2e5067
>          d3427475e49968f841
> 
>    The data for the optional AVPs is represented in hex since the
> format
>    of these AVPs is neither known at the time of definition of the
>    Example-AVP group, nor (likely) at the time when the example
> instance
>    of this AVP is interpreted - except by Diameter implementations
> which
>    support the same set of AVPs.  The encoding example illustrates how
>    padding is used and how length fields are calculated.  Also note
> that
>    AVPs may be present in the Grouped AVP value which the receiver
>    cannot interpret (here, the Recover-Policy and Futuristic-Acct-
> Record
>    AVPs).
> 
>    This AVP would be encoded as follows:
> 
>            0       1       2       3       4       5       6       7
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>      0 |     Example AVP Header (AVP Code = 999999), Length = 468
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>      8 |     Origin-Host AVP Header (AVP Code = 264), Length = 19
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     16 |  'e'  |  'x'  |  'a'  |  'm'  |  'p'  |  'l'  |  'e'  |  '.'
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     24 |  'c'  |  'o'  |  'm'  |Padding|     Session-Id AVP Header
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     32 | (AVP Code = 263), Length = 50 |  'g'  |  'r'  |  'u'  |  'm'
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     64 |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '1'
> |Padding|Padding|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     72 |     Session-Id AVP Header (AVP Code = 263), Length = 51
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     80 |  'g'  |  'r'  |  'u'  |  'm'  |  'p'  |  '.'  |  'e'  |  'x'
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    104 |  '0'  |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '2'
> |Padding|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    112 |   Recovery-Policy Header (AVP Code = 8341), Length = 223
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    120 |  0x21 | 0x63  | 0xbc  | 0x1d  | 0x0a  | 0xd8  | 0x23  | 0x71
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    320 |  0x2f | 0xd7  | 0x96  | 0x6b  | 0x8c  | 0x7f  | 0x92
> |Padding|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    328 | Futuristic-Acct-Record Header (AVP Code = 15930), Length =
> 137|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    336 |  0xfe | 0x19  | 0xda  | 0x58  | 0x02  | 0xac  | 0xd9  | 0x8b
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    464 |  0x41 |Padding|Padding|Padding|
>        +-------+-------+-------+-------+
> 
> 
> 
> 
> 
> --
> to unsubscribe send a message to 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  Thu Aug 14 04:36:22 2008
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 CF5613A6841
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 04:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5
	tests=[AWL=-0.879, 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 gpF+Nu+yz4p4
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 04:36:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D58373A6D2F
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 04:36:21 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTb4w-000D86-QH
	for radiusext-data@psg.com; Thu, 14 Aug 2008 11:33:18 +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.69 (FreeBSD))
	(envelope-from <dromasca@avaya.com>)
	id 1KTb4m-000D6v-Gh
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 11:33:14 +0000
X-IronPort-AV: E=Sophos;i="4.32,209,1217822400"; 
   d="scan'208";a="118263157"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
  by de307622-de-outbound.net.avaya.com with ESMTP; 14 Aug 2008 07:33:04 -0400
X-IronPort-AV: E=Sophos;i="4.32,209,1217822400"; 
   d="scan'208";a="258332704"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15])
  by co300216-co-erhwest-out.avaya.com with ESMTP; 14 Aug 2008 07:33:03 -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: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 13:32:59 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com>
In-Reply-To: <000701c8fdfe$5e220ef0$1a662cd0$@net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Thread-Index: Acj99HP/tjdafrPARXuHUs1IJ4c0YgACReoAAAD28RA=
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu> <000701c8fdfe$5e220ef0$1a662cd0$@net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Glen Zorn" <glenzorn@comcast.net>,
	"Stefan Winter" <stefan.winter@restena.lu>
Cc: <radiusext@ops.ietf.org>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

=20

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Glen Zorn
> Sent: Thursday, August 14, 2008 2:10 PM
> To: 'Stefan Winter'
> Cc: radiusext@ops.ietf.org
> Subject: RE: REMINDER: RADEXT WG Last call on "Extended=20
> RADIUS Attributes"
>=20
> Stefan Winter <mailto://stefan.winter@restena.lu> writes:
>=20

...

> > There also is no clarification whether fragmenting should=20
> only occur=20
> > when it is needed. Without requiring this, a compliant=20
> implementation=20
> > could as well split the 5-byte data "Hello" into five fragments. I=20
> > suggest to add a bit of wording to strongly discourage that.
>=20
> Maybe just put a note like "If you are a total moron, stop=20
> reading now." in the Abstract?
>=20
> ...

There certainly should be some other ways to say it.=20

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 Aug 14 04:46:57 2008
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 3DA773A6D93
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 04:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.072
X-Spam-Level: 
X-Spam-Status: No, score=-1.072 tagged_above=-999 required=5
	tests=[AWL=-0.024, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	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 d5gFRI+jeaMD
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 04:46:56 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 671393A695A
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 04:46:56 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTbCP-000DrN-SP
	for radiusext-data@psg.com; Thu, 14 Aug 2008 11:41:01 +0000
Received: from [158.64.1.34] (helo=legolas.restena.lu)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <stefan.winter@restena.lu>)
	id 1KTbCM-000Dqq-79
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 11:41:00 +0000
Received: from legolas.restena.lu (localhost [127.0.0.1])
	by legolas.restena.lu (Postfix) with ESMTP id CB672B8A25;
	Thu, 14 Aug 2008 13:40:56 +0200 (CEST)
Received: from [158.64.1.155] (aragorn.restena.lu [158.64.1.155])
	by legolas.restena.lu (Postfix) with ESMTPA id BC5D0AF03D;
	Thu, 14 Aug 2008 13:40:56 +0200 (CEST)
Message-ID: <48A419C8.2030308@restena.lu>
Date: Thu, 14 Aug 2008 13:40:56 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
CC: Glen Zorn <glenzorn@comcast.net>, radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu> <000701c8fdfe$5e220ef0$1a662cd0$@net> <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi,

>> Maybe just put a note like "If you are a total moron, stop 
>> reading now." in the Abstract?
>>     
>
> There certainly should be some other ways to say it. 
>   

Alan's wording "The More Flag MUST NOT be set if the Length is less than 
255." sounds good to me.

Stefan


-- 

Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to 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 Aug 14 10:32:48 2008
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 4D2363A6358
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 10:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[AWL=0.555,
	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 Y-HLMu32I8R2
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 10:32:47 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2BD8C3A6D5B
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 10:32:47 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTgc0-000NMP-Ni
	for radiusext-data@psg.com; Thu, 14 Aug 2008 17:27:48 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <dnelson@elbrysnetworks.com>)
	id 1KTgbt-000NLL-0l
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 17:27:43 +0000
Received: (qmail 13448 invoked from network); 14 Aug 2008 13:27:35 -0400
Received: from unknown (HELO xpsuperdvd2) (172.22.18.93)
  by gumby.elbrysnetworks.com with SMTP; 14 Aug 2008 13:27:35 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
Cc: "'Alan DeKok'" <aland@deployingradius.com>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 13:27:42 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj98OXV6Mdn/4x7RkyVEJ2+H8F8JAAKa5MA
In-Reply-To: <48A3FAA1.1020109@deployingradius.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok writes...

>   Inserting *other* attributes in between a fragemented attribute
> is annoying and pointless.  It's better to forbid this, and to 
> declare that packets failing this test are malformed, and SHOULD
> be silently discarded.

I think this would introduce a new, non-backwards-compatible requirement.
Today, RADIUS requires that attributes of the same type not be re-ordered in
the PDU, e.g. by proxies. There is no such requirement for attributes of
differing types.

>   What does "Foo(0,4)" mean?

I suppose it means the TLV with Type Code 4, assigned within the IETF
allocation, i.e. Attribute 26, Vendor-ID 0.

Why not just refer to it as "Foo"?

There is a long-standing typographical tradition of listing attributes as
Attribute-Name (##).

>    Consider the following structure:
> 
>      struct
>        Integer a;
>        String  b;
>        Integer c;
>      endStruct
> 
>   What syntax is this?

Pseudo-code?  Maybe actually using ANSI C would be more universal.  I think
the RADIUS data types are not a good way to express this concept, as
witnessed by confusion in various drafts over the years. 

>   Reading the rest of the example, I find the b(4,5) syntax very
> awkward.

I think that's part of Glen's [potential] issue.

> 7.  Security Considerations
> 
>    I suggest adding a note that a new attribute encoding is an
> opportunity for buffer overflows, inadequate checks, etc. 
> Implementors SHOULD take care to validate the lengths, etc. 
> before decoding the contents of the attributes.

How is that different from good coding guidelines for *any* implementation
of *any* protocol?  What about the on-the-wire protocol involved raises
these risks?

> 9.  Open Issues
> 
>    What is the numbering scheme for attributes that will be used by RFC
>    writers going forward?  For example today we write user-name(1).
> 
>   Uh... We do?

Yes, we do.  I can cite numerous examples.



--
to unsubscribe send a message to 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 Aug 14 10:39:41 2008
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 A39AE3A6902
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 10:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.052
X-Spam-Level: 
X-Spam-Status: No, score=0.052 tagged_above=-999 required=5 tests=[AWL=0.489,
	BAYES_00=-2.599, 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 sKOV4cfATb5V
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 10:39:40 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B5A1F3A68A2
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 10:39:40 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTgiu-000O8Q-Ch
	for radiusext-data@psg.com; Thu, 14 Aug 2008 17:34:56 +0000
Received: from [76.96.30.24] (helo=QMTA02.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTgiQ-000O5H-Dx
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 17:34:51 +0000
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
	by QMTA02.emeryville.ca.mail.comcast.net with comcast
	id 2FW61a0030S2fkCA2HaSrc; Thu, 14 Aug 2008 17:34:26 +0000
Received: from gwzPC ([124.120.216.202])
	by OMTA09.emeryville.ca.mail.comcast.net with comcast
	id 2HZw1a00L4NbUxY8VHaDtb; Thu, 14 Aug 2008 17:34:23 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=W7nZUePsgs13qpcMI8AA:9 a=BSnzFr9rgOitSedIKkDda0JwVj4A:4 a=ufO146cb3fEA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Stefan Winter'" <stefan.winter@restena.lu>
Cc: <radiusext@ops.ietf.org>,
	"'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu> <000701c8fdfe$5e220ef0$1a662cd0$@net> <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com> <48A419C8.2030308@restena.lu>
In-Reply-To: <48A419C8.2030308@restena.lu>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 00:33:40 +0700
Message-ID: <004f01c8fe33$ed1b84d0$c7528e70$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj+Ap5X2rEQpcmqQfK3am5RpDNpsQAMAXdA
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Stefan Winter [mailto:stefan.winter@restena.lu] writes:

> Hi,
>=20
> >> Maybe just put a note like "If you are a total moron, stop
> >> reading now." in the Abstract?
> >>
> >
> > There certainly should be some other ways to say it.
> >
>=20
> Alan's wording "The More Flag MUST NOT be set if the Length is less
> than
> 255." sounds good to me.

My point was that making these kinds of rules is pointless: if someone =
wants
to split "Hello" into 5 separate attributes they either have a very good
reason to do so that none of us can foresee or they will soon be finding
gainful employment in a different field.  In any case, it's not possible =
to
protect people from their own stupidity (besides, they could still do it
with tags).

>=20
> Stefan
>=20
>=20
> --
>=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education =
Nationale et
> de la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473




--
to unsubscribe send a message to 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 Aug 14 10:40:45 2008
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 8058B3A68A0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 10:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.682
X-Spam-Level: 
X-Spam-Status: No, score=-0.682 tagged_above=-999 required=5
	tests=[AWL=-0.245, BAYES_00=-2.599, 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 QwopbxpHcBpJ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 10:40:44 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6200A3A6868
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 10:40:44 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTgkw-000ONS-Pr
	for radiusext-data@psg.com; Thu, 14 Aug 2008 17:37:02 +0000
Received: from [213.165.64.20] (helo=mail.gmx.net)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <Hannes.Tschofenig@gmx.net>)
	id 1KTgko-000OML-55
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 17:37:00 +0000
Received: (qmail invoked by alias); 14 Aug 2008 17:36:52 -0000
Received: from a91-154-105-144.elisa-laajakaista.fi (EHLO [192.168.255.3]) [91.154.105.144]
  by mail.gmx.net (mp056) with SMTP; 14 Aug 2008 19:36:52 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/bmQ8Yo43bFSId3YSu5onP8ptXT5d7P0i0cBNrgT
	epm1+7IUUz8Qug
Message-ID: <48A46D3A.9000406@gmx.net>
Date: Thu, 14 Aug 2008 20:36:58 +0300
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.64
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard,

why is there is a working group last call on this document given that it 
still has an open issue section giving me the impression that the 
document is far from being ready?

Ciao
Hannes

Bernard Aboba wrote:
> This is a reminder of the RADEXT WG Last Call on "Extended 
> RADIUS Attributes", prior to requesting that the IESG publish it as a Proposed Standard. 
>  
> The document is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-04.txt
>  
> WG Last Call was originally to have completed on August 10, 2008.   
> However, due to lack of response to the RADEXT WG last call, 
> we will be extending the WG last call to August 31, 2008.  Please 
> review the document and post your comments to the RADEXT WG mailing list 
> (radiusext@ops.ietf.org) in the format described on the RADEXT WG Issues 
> list (http://www.drizzle.com/~aboba/RADEXT/).   
>  
> If you have read the document and approve of its publication, but have no
> comments, please also post this to the list. 
>
> --
> to unsubscribe send a message to 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  Thu Aug 14 12:29:01 2008
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 763BB3A6878
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 12:29:01 -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 XAvRacIf5mGN
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 12:29:00 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 405593A6822
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 12:29:00 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTiQq-0009qH-2G
	for radiusext-data@psg.com; Thu, 14 Aug 2008 19:24:24 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KTiQl-0009pd-Nl
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 19:24:22 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 7726F123423B;
	Thu, 14 Aug 2008 21:24:18 +0200 (CEST)
Message-ID: <48A48634.9030002@deployingradius.com>
Date: Thu, 14 Aug 2008 21:23:32 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2>
In-Reply-To: <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2>
X-Enigmail-Version: 0.95.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:
> I think this would introduce a new, non-backwards-compatible requirement.
> Today, RADIUS requires that attributes of the same type not be re-ordered in
> the PDU, e.g. by proxies. There is no such requirement for attributes of
> differing types.

  That's not *quite* what I meant.

  What I meant was interspersing attributes of disparate types.  I'm not
aware of any implementation that does this (e.g. for EAP-Message).  But
I've learned to be paranoid about RADIUS specifications.

>>   What does "Foo(0,4)" mean?
> 
> I suppose it means the TLV with Type Code 4, assigned within the IETF
> allocation, i.e. Attribute 26, Vendor-ID 0.

  Nope.  Read the rest of the doc.  It means "octets 0 through 4 of
attribute Foo".

> There is a long-standing typographical tradition of listing attributes as
> Attribute-Name (##).

  References?

[ struct ]
>>   What syntax is this?
> 
> Pseudo-code?  Maybe actually using ANSI C would be more universal.  I think
> the RADIUS data types are not a good way to express this concept, as
> witnessed by confusion in various drafts over the years. 

  I'm just asking for a definition of the terminology and concepts
referred to in the draft.  What's an "Integer", or a "String"?  Do these
relate to C definitions?  RADIUS?

> How is that different from good coding guidelines for *any* implementation
> of *any* protocol?  What about the on-the-wire protocol involved raises
> these risks?

  Er... nothing.

>> 9.  Open Issues
>>
>>    What is the numbering scheme for attributes that will be used by RFC
>>    writers going forward?  For example today we write user-name(1).
>>
>>   Uh... We do?
> 
> Yes, we do.  I can cite numerous examples.

  Where?

  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 Aug 14 12:31:18 2008
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 C64BF3A68C2
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 12:31:18 -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 6yIuHDiJOAHY
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 12:31:18 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id ED8563A6886
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 12:31:17 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTiU5-000AFW-6d
	for radiusext-data@psg.com; Thu, 14 Aug 2008 19:27:45 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KTiU1-000AEh-6h
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 19:27:43 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 34312123423B;
	Thu, 14 Aug 2008 21:27:40 +0200 (CEST)
Message-ID: <48A486FC.40007@deployingradius.com>
Date: Thu, 14 Aug 2008 21:26:52 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'Stefan Winter' <stefan.winter@restena.lu>, radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu> <000701c8fdfe$5e220ef0$1a662cd0$@net> <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com> <48A419C8.2030308@restena.lu> <004f01c8fe33$ed1b84d0$c7528e70$@net>
In-Reply-To: <004f01c8fe33$ed1b84d0$c7528e70$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
>> Alan's wording "The More Flag MUST NOT be set if the Length is less
>> than
>> 255." sounds good to me.
> 
> My point was that making these kinds of rules is pointless: if someone wants
> to split "Hello" into 5 separate attributes they either have a very good
> reason to do so that none of us can foresee or they will soon be finding
> gainful employment in a different field.  In any case, it's not possible to
> protect people from their own stupidity (besides, they could still do it
> with tags).

  It's only one sentence.  And it will stop the stupid people from
afflicting everyone else.

  RFC 2865 has comments saying:

      The secret MUST NOT be empty (length 0) since this would allow
      packets to be trivially forged.

  Which were inserted because of real-world exposure to implementations
having *no* configuration for shared secrets. (i.e. they were always NUL).

  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 Aug 14 12:51:26 2008
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 9B63F3A693C
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 12:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.734
X-Spam-Level: *
X-Spam-Status: No, score=1.734 tagged_above=-999 required=5 tests=[AWL=-0.185,
	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 gIa8BtH0O1vp
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 12:51:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 23B183A67BD
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 12:51:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTin6-000Ca8-Ke
	for radiusext-data@psg.com; Thu, 14 Aug 2008 19:47:24 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <dnelson@elbrysnetworks.com>)
	id 1KTin1-000CZ5-O3
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 19:47:22 +0000
Received: (qmail 16554 invoked from network); 14 Aug 2008 15:47:15 -0400
Received: from unknown (HELO xpsuperdvd2) (172.22.18.93)
  by gumby.elbrysnetworks.com with SMTP; 14 Aug 2008 15:47:15 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <48A48634.9030002@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 15:47:23 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <90797A5700C14358A7838274F4364A9D@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj+Q1yb5FtV6joZRmm9F5LXJQ3oRQAAIOJA
In-Reply-To: <48A48634.9030002@deployingradius.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

> > Yes, we do.  I can cite numerous examples.
> 
>   Where?

Section 7.1 of RFC 2865.  Section 2.1 of RFC 3580.  Section 2.2 of RFC 5176.
Section 2.1.1 of RFC 5080.  Section 6 of RFC 5090.

This is not an exhaustive list, but rather a sampling.



--
to unsubscribe send a message to 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 Aug 14 13:08:14 2008
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 39CE03A68A0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 13:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5
	tests=[AWL=-1.052, 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 B7nA6qmBw+V8
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 13:08:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0A7F83A6851
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 13:08:13 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTj3s-000Eae-KP
	for radiusext-data@psg.com; Thu, 14 Aug 2008 20:04:44 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jsalowey@cisco.com>)
	id 1KTj3n-000EZe-8l
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 20:04:41 +0000
X-IronPort-AV: E=Sophos;i="4.32,211,1217808000"; 
   d="scan'208";a="95186123"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
  by sj-iport-3.cisco.com with ESMTP; 14 Aug 2008 20:04:38 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m7EK4c6i010513;
	Thu, 14 Aug 2008 13:04:38 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m7EK4cOB007843;
	Thu, 14 Aug 2008 20:04:38 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 14 Aug 2008 13:04:38 -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: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Thu, 14 Aug 2008 13:04:34 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5065592E5@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
thread-index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDA
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <aboba@internaut.com>, <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 14 Aug 2008 20:04:38.0402 (UTC) FILETIME=[FB1B2620:01C8FE48]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2084; t=1218744278; x=1219608278;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jsalowey@cisco.com;
	z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci
	sco.com>
	|Subject:=20RE=3A=20REMINDER=3A=20RADEXT=20WG=20Last=20Call
	=20on=20=22Crypto-Agility=20Requirements=20for=20RADIUS=22
	|Sender:=20;
	bh=eNLHBQ1Zdc2VxhjKIGHW/FNxqdVhdgg23O5nMZLGWp4=;
	b=Z51LD1H14aBvYg6ah+3fVJz6D+1FwDXHbdqYbP3dkFVw9eK1zH+6QM7wjz
	SZH/Ne/C6N7VcjWxjzWTP5+G4bsXl8L+Zg/UtFNzx32NC4/ZdpGpK5WKOegR
	pAidxI0IanlUZLc5oKO8ufrPez+CV2wsWG86GAN1dfj26g0uDW0kg=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

I have read the draft and for the most part it looks good.

I have a few comments:

1. Section 4.2:

In cases where the client needs to protect all or part of the radius
request the "hint and select" negotiation the client would provide more
than a hint when it chooses the algorithms for protection.  Perhaps hint
and select is not quite the right term, may be specify and select?  The
client specifies what it uses and can specify a list it supports that
the server can use.=20

2. Section 4.6:

Section 4.6 makes reference to security considerations text about key
management.  Shouldn't this text be in this document?

Thanks,

Joe




> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
> Sent: Wednesday, August 13, 2008 7:06 PM
> To: radiusext@ops.ietf.org
> Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility=20
> Requirements for RADIUS"
>=20
> This is a reminder of the ongoing RADEXT WG Last Call on=20
> "Crypto-Agility Requirements for RADIUS" prior to requesting=20
> that the IESG publish it as an Informational RFC.=20
> =20
> The document is available here:
>
http://www.ietf.org/internet-drafts/draft-ietf-radext-crypto-agility-req
uirements-00.txt
> =20
> WG Last Call was to have lasted until August 10, 2008.   Since there=20
> have been no comments posted yet, we will extend the last=20
> call for another two weeks (until August 31, 2008).  Please=20
> review the document and post your comments to the RADEXT WG=20
> mailing list
> (radiusext@ops.ietf.org) in the format described on the=20
> RADEXT WG Issues=20
> list (http://www.drizzle.com/~aboba/RADEXT/).  =20
> =20
> If you have read the document and approve of its publication,=20
> but have no comments, please also post this to the list.=20
>=20
> --
> to unsubscribe send a message to=20
> radiusext-request@ops.ietf.org with the word 'unsubscribe' in=20
> a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=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/>


From owner-radiusext@ops.ietf.org  Thu Aug 14 13:10:27 2008
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 019F63A69C0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 13:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5
	tests=[AWL=-1.052, 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 qVKySc-zyxnC
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 13:10:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B00753A6926
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 13:10:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTj3u-000Eaw-OS
	for radiusext-data@psg.com; Thu, 14 Aug 2008 20:04:46 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jsalowey@cisco.com>)
	id 1KTj3p-000EZe-MR
	for radiusext@ops.ietf.org; Thu, 14 Aug 2008 20:04:44 +0000
X-IronPort-AV: E=Sophos;i="4.32,211,1217808000"; 
   d="scan'208";a="95186126"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
  by sj-iport-3.cisco.com with ESMTP; 14 Aug 2008 20:04:39 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m7EK4cbq024122;
	Thu, 14 Aug 2008 13:04:38 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m7EK4cqL006463;
	Thu, 14 Aug 2008 20:04:38 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 14 Aug 2008 13:04:38 -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: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Thu, 14 Aug 2008 13:04:34 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5065592E6@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
thread-index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDA
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <aboba@internaut.com>, <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 14 Aug 2008 20:04:38.0839 (UTC) FILETIME=[FB5DD470:01C8FE48]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2084; t=1218744278; x=1219608278;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jsalowey@cisco.com;
	z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci
	sco.com>
	|Subject:=20RE=3A=20REMINDER=3A=20RADEXT=20WG=20Last=20Call
	=20on=20=22Crypto-Agility=20Requirements=20for=20RADIUS=22
	|Sender:=20;
	bh=eNLHBQ1Zdc2VxhjKIGHW/FNxqdVhdgg23O5nMZLGWp4=;
	b=K1zVbDZl7hSbOaH907cYxXBZnYvd8SGpLLZqhIx5TFwPSrWEW0aDppYZB0
	GpScm40idfnQjgHR3LKSFP5QOxkFdHeM1ckGqXmflU508dhOAnPd+0xBXq+Z
	jA0TYyww+L;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

I have read the draft and for the most part it looks good.

I have a few comments:

1. Section 4.2:

In cases where the client needs to protect all or part of the radius
request the "hint and select" negotiation the client would provide more
than a hint when it chooses the algorithms for protection.  Perhaps hint
and select is not quite the right term, may be specify and select?  The
client specifies what it uses and can specify a list it supports that
the server can use.=20

2. Section 4.6:

Section 4.6 makes reference to security considerations text about key
management.  Shouldn't this text be in this document?

Thanks,

Joe




> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
> Sent: Wednesday, August 13, 2008 7:06 PM
> To: radiusext@ops.ietf.org
> Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility=20
> Requirements for RADIUS"
>=20
> This is a reminder of the ongoing RADEXT WG Last Call on=20
> "Crypto-Agility Requirements for RADIUS" prior to requesting=20
> that the IESG publish it as an Informational RFC.=20
> =20
> The document is available here:
>
http://www.ietf.org/internet-drafts/draft-ietf-radext-crypto-agility-req
uirements-00.txt
> =20
> WG Last Call was to have lasted until August 10, 2008.   Since there=20
> have been no comments posted yet, we will extend the last=20
> call for another two weeks (until August 31, 2008).  Please=20
> review the document and post your comments to the RADEXT WG=20
> mailing list
> (radiusext@ops.ietf.org) in the format described on the=20
> RADEXT WG Issues=20
> list (http://www.drizzle.com/~aboba/RADEXT/).  =20
> =20
> If you have read the document and approve of its publication,=20
> but have no comments, please also post this to the list.=20
>=20
> --
> to unsubscribe send a message to=20
> radiusext-request@ops.ietf.org with the word 'unsubscribe' in=20
> a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=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/>


From owner-radiusext@ops.ietf.org  Thu Aug 14 23:54:47 2008
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 948523A6819
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 14 Aug 2008 23:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level: 
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[AWL=0.440,
	BAYES_00=-2.599, 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 DQUs-vs+tVCE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 14 Aug 2008 23:54:46 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 845243A6452
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 14 Aug 2008 23:54:46 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTt8t-000Brk-Ss
	for radiusext-data@psg.com; Fri, 15 Aug 2008 06:50:35 +0000
Received: from [76.96.62.17] (helo=QMTA10.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTt8p-000BrQ-JU
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 06:50:33 +0000
Received: from OMTA08.westchester.pa.mail.comcast.net ([76.96.62.12])
	by QMTA10.westchester.pa.mail.comcast.net with comcast
	id 2VkK1a0040Fqzac5AWqXDL; Fri, 15 Aug 2008 06:50:31 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA08.westchester.pa.mail.comcast.net with comcast
	id 2WpX1a0035TN7tY3UWq3uf; Fri, 15 Aug 2008 06:50:26 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=dHilbzAkS7l0_5lsIREA:9 a=QRydyI7jXtbn4kADpDAuDZ7bEYcA:4 a=-utQw5L2n1AA:10
 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>
Cc: "'Alan DeKok'" <aland@deployingradius.com>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2>
In-Reply-To: <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 13:49:14 +0700
Message-ID: <002001c8fea3$19c89800$4d59c800$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj98OXV6Mdn/4x7RkyVEJ2+H8F8JAAKa5MAACH4/lA=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson <mailto:// dnelson@elbrysnetworks.com> writes:

> Alan DeKok writes...
> 
> >   Inserting *other* attributes in between a fragemented attribute
> > is annoying and pointless.  It's better to forbid this, and to
> > declare that packets failing this test are malformed, and SHOULD
> > be silently discarded.
> 
> I think this would introduce a new, non-backwards-compatible
> requirement.
> Today, RADIUS requires that attributes of the same type not be re-
> ordered in
> the PDU, e.g. by proxies. There is no such requirement for attributes
> of
> differing types.

I believe that he meant that all fragments of a given attribute must be
contiguous in the original packet...

> 
> >   What does "Foo(0,4)" mean?
> 
> I suppose it means the TLV with Type Code 4, assigned within the IETF
> allocation, i.e. Attribute 26, Vendor-ID 0.

This would be a perfectly reasonable interpretation, but it actually means
"octets 0-4 of attribute Foo".

...



--
to unsubscribe send a message to 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 Aug 15 01:59:18 2008
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 575613A6856
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 01:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.037
X-Spam-Level: 
X-Spam-Status: No, score=-0.037 tagged_above=-999 required=5 tests=[AWL=0.400,
	BAYES_00=-2.599, 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 1yoFC0dPIODj
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 01:59:17 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 3C5F93A67DF
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 01:59:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTv5U-000L8z-R7
	for radiusext-data@psg.com; Fri, 15 Aug 2008 08:55:12 +0000
Received: from [76.96.62.80] (helo=QMTA08.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTv5Q-000L8W-Vj
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 08:55:10 +0000
Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20])
	by QMTA08.westchester.pa.mail.comcast.net with comcast
	id 2YuB1a0040SCNGk58Yv8qZ; Fri, 15 Aug 2008 08:55:08 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA09.westchester.pa.mail.comcast.net with comcast
	id 2YuC1a0085TN7tY3VYumnc; Fri, 15 Aug 2008 08:55:03 +0000
X-Authority-Analysis: v=1.0 c=1 a=a7u_cT3PH9QA:10 a=8HcvQD4DwR0A:10
 a=q2xzoZfwZc8g-uX_mxIA:9 a=Egx_kVpOyjDzSpImTgAA:7
 a=RvL_7mfaOCoAoXIlB_Tm0_ObwMMA:4 a=nbrB6oW77rQA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
Subject: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 15 Aug 2008 15:53:55 +0700
Message-ID: <002201c8feb4$81ee5df0$85cb19d0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48Q
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Questions:

The WG Charter states that all of the existing crypto-agility proposals are
to be published as Experimental RFCs.  In that case, how can the requirement
that " at least one mandatory to implement algorithm will be defined"
(section 1.2) be fulfilled?


Editorial comments:

Front page header:
Since the source of the document is stated in section 1.1 to be the radext
WG, David's role should probably be "Editor".

Section 1.2:
s/propose one of more Internet Drafts/propose one or more Internet-Drafts/

Section 2:
s/Crypto-Agility is the ability for/Crypto-agility is the ability of/

Section 4.5, paragraph 5 states:

   Editorial Note: With the expected acceptance of the proposed RADEXT
   WG Charter revision, some of the issues raised in the preceding
   paragraphs become moot, and this section ought to be revised to
   reflect the revised charter.

Haven't those charter revisions already taken place?


Technical comments:

Section 2, paragraph 2 states:

   In the specific context of the RADIUS protocol and RADIUS
   implementations, crypto-agility may be better defined as the ability
   of RADIUS implementations to negotiate cryptographic algorithms for
   use in RADIUS exchanges, including the cryptographic algorithms used
   to protect RADIUS packets and to hide RADIUS Attributes.  This
   capability covers all RADIUS message types: Access-Request/Response,
   Accounting-Request/Response, and CoA/Disconnect-Request/Response.

Since RADIUS has no negotiation method of I'm aware (hint & accept/ignore is
hardly a negotiation mechanism) I find these statements very curious,
especially in light of the earlier statement (section 2, paragraph 3) that
the password-hiding function will be negotiable.  Basically, what is being
called for is impossible in the context of the RADIUS protocol, implying
that the negotiations would take place outside of RADIUS (e.g., in TLS).  I
think that it is at least inappropriate in a requirements document, in that
it assumes a solution.

Section 4.1: 
Once again, assuming a solution.  State the requirements that a solution
must meet, not your personal assumptions about the form which the solution
will take.  I say "personal" because a fair subset of the active WG (of
which this document is purportedly a product) _does not_ share the
expectation that " proposals will utilize other techniques".

Section 4.2, paragraph 2 states:

   Included in negotiation techniques are "hint and consent" mechanisms
   where the NAS provides a list of algorithms and the server selects
   one.

If the server is required to select from the list it can hardly be called a
hint.  Once again, I can't see at all how this mechanism could be made to
work in the case of the Access-Request message.

Section 4.3, paragraph 1 states:

   Solutions to the problem MUST demonstrate backward compatibility with
   existing RADIUS implementations.  

I would _really_ like to see some rationale for this requirement (aside from
"backward compatibility is sacred and must never be questioned" ;-).  Given
that this is new and presumably desirable functionality, why is a simple
upgrade path not sufficient?

Section 4.5, paragraph 3 states:

   Crypto-agility solutions SHOULD NOT require fundamental changes to
   the RADIUS operational model, such as the introduction of new
   commands or maintenance of state on the RADIUS server.  

OK, I'll bite: how, exactly, does the introduction of a new command
fundamentally change the RADIUS operational model?



--
to unsubscribe send a message to 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 Aug 15 03:16:23 2008
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 34AE93A6D24
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 03:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.07
X-Spam-Level: 
X-Spam-Status: No, score=-0.07 tagged_above=-999 required=5 tests=[AWL=0.367,
	BAYES_00=-2.599, 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 EK47t8ihXlhZ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 03:16:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1C5C73A6D23
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 03:16:22 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTwHB-0001Z6-5p
	for radiusext-data@psg.com; Fri, 15 Aug 2008 10:11:21 +0000
Received: from [76.96.30.32] (helo=QMTA03.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTwH6-0001YX-3Z
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 10:11:19 +0000
Received: from OMTA04.emeryville.ca.mail.comcast.net ([76.96.30.35])
	by QMTA03.emeryville.ca.mail.comcast.net with comcast
	id 2a9w1a0010lTkoCA3aBFq5; Fri, 15 Aug 2008 10:11:15 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA04.emeryville.ca.mail.comcast.net with comcast
	id 2aAr1a0025TN7tY8QaB5CW; Fri, 15 Aug 2008 10:11:13 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=48vgC7mUAAAA:8 a=Cv6e0pkHAAAA:8 a=No5EcEP4AAAA:8 a=mNaPCpVUwBOiJ1SxxnQA:9
 a=4YZuVEBOBGVB3u6a-ZMA:7 a=vogK8CxwqXhmLC6GqT1xV6aZiFAA:4 a=BFDKbZatV3MA:10
 a=2uiCRmbCp6AA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A46D3A.9000406@gmx.net>
In-Reply-To: <48A46D3A.9000406@gmx.net>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 17:10:33 +0700
Message-ID: <002c01c8febf$2f4e04f0$8dea0ed0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj+NL1voI03o1KBT8O1QRUZ/eKMYAAiHH0Q
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hannes Tschofenig <mailto:// Hannes.Tschofenig@gmx.net> writes:

> Bernard,
> 
> why is there is a working group last call on this document given that
> it
> still has an open issue section giving me the impression that the
> document is far from being ready?

1) As you know, the issues list is not an official WG document, but a tool
for the use of the Chairs & as such its state has no bearing on the status
of a document.
2) All 3 of the issues assigned to the extended attributes document appear
to actually refer to RFC 5080.

> 
> Ciao
> Hannes
> 
> Bernard Aboba wrote:
> > This is a reminder of the RADEXT WG Last Call on "Extended
> > RADIUS Attributes", prior to requesting that the IESG publish it as a
> Proposed Standard.
> >
> > The document is available here:
> > http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> attributes-04.txt
> >
> > WG Last Call was originally to have completed on August 10, 2008.
> > However, due to lack of response to the RADEXT WG last call,
> > we will be extending the WG last call to August 31, 2008.  Please
> > review the document and post your comments to the RADEXT WG mailing
> list
> > (radiusext@ops.ietf.org) in the format described on the RADEXT WG
> Issues
> > list (http://www.drizzle.com/~aboba/RADEXT/).
> >
> > If you have read the document and approve of its publication, but
> have no
> > comments, please also post this to the list.
> >
> > --
> > to unsubscribe send a message to 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  Fri Aug 15 05:30:11 2008
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 DDDE83A6D84
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 05:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[AWL=0.338,
	BAYES_00=-2.599, 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 4RGTeInPQw+C
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 05:30:11 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C5C333A6D79
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 05:30:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTyNB-000Ce8-Pb
	for radiusext-data@psg.com; Fri, 15 Aug 2008 12:25:41 +0000
Received: from [76.96.62.96] (helo=QMTA09.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KTyN4-000CdE-Sr
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 12:25:39 +0000
Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44])
	by QMTA09.westchester.pa.mail.comcast.net with comcast
	id 2bDz1a0040xGWP859cRZDH; Fri, 15 Aug 2008 12:25:33 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA12.westchester.pa.mail.comcast.net with comcast
	id 2cQg1a00J5TN7tY3YcRAid; Fri, 15 Aug 2008 12:25:28 +0000
X-Authority-Analysis: v=1.0 c=1 a=KaEX0pHM2ccA:10 a=_RDAsohIr2QA:10
 a=6bkegg1Ead2TMV-UuHEA:9 a=kpSNZzdn1fQ5g7l26tWpQhhSGMkA:4 a=tqucuuI3bnEA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: <abhisht@microsoft.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131907000.24114@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808131907000.24114@internaut.com>
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Date: Fri, 15 Aug 2008 19:24:23 +0700
Message-ID: <003301c8fed1$e9571f00$bc055d00$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9swl5Q5+W+luPTBm1XAuPqNYzHABHQ7rQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glancing over this:

Since there's only one author, it would be good to move the apostrophe in
"Authors'" left.  

In the table in Section 3, move the abbreviation (ESP) next to "Payload".

Since new values of the Tunnel-Type Attribute are allocated by IETF
Consensus, it might be a better idea to separate this into 2 docs, one for
the ESP value & the other for the proprietary one.  In fact, because the
spec for the Microsoft Secure Socket Tunneling Protocol is public & appears
fairly stable, I would prefer that the allocation be part of an
Informational RFC describing the protocol.  At the very least, though, the
name needs to be changed to "Microsoft's Secure Socket Tunneling Protocol"
(or something similar) that identifies its proprietary nature.




--
to unsubscribe send a message to 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 Aug 15 06:49:43 2008
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 9D27D28C1F5
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 06:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5
	tests=[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 14ERwYP6jDK4
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 06:49:42 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0B1FC3A6ACC
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 06:49:42 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KTzbu-000Jau-3C
	for radiusext-data@psg.com; Fri, 15 Aug 2008 13:44:58 +0000
Received: from [209.85.146.181] (helo=wa-out-1112.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <gdweber@gmail.com>)
	id 1KTzbo-000Ja0-3q
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 13:44:54 +0000
Received: by wa-out-1112.google.com with SMTP id j37so522661waf.23
        for <radiusext@ops.ietf.org>; Fri, 15 Aug 2008 06:44:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:cc:in-reply-to:mime-version:content-type:references;
        bh=S2AHwBBWOHoZ8zoJw8jzfReV8z6EYrX6ThToeAByDwc=;
        b=DaX1jXlf1afLtniFeKnXgDqg09q4krS/tDZhnt77ja1BH0KG0FqdsFYIK2Rfyz3hZc
         pDr4a/iuQj0M6GdvsJQ9pSN1XYwRHwqHewF/gVkqQPaY3aP6Vt/c4ep0w0X/6iDnNK0/
         XtYHQdQ5eW2ZPl7bnpu7azasq+Tmv7wUk8UDE=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:references;
        b=nWD8qCuglGBH9ovPfQQKxVaR1RFmLwwKjj5EjT5mdrTUZ4fp5Qd8F8iBVQE7fgNPyC
         ZRmQ6vLjD9cr2Q/gzYYPZtGDZQfI+yNDi9gTTS30CI5amFQ/iyUlw5mjPaP7w6qLt22e
         bcP1WgaLJ4M1FTcK5s+hhn+Pr9NwboSmmsnik=
Received: by 10.115.91.11 with SMTP id t11mr2483125wal.41.1218807891748;
        Fri, 15 Aug 2008 06:44:51 -0700 (PDT)
Received: by 10.114.79.8 with HTTP; Fri, 15 Aug 2008 06:44:51 -0700 (PDT)
Message-ID: <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>
Date: Fri, 15 Aug 2008 09:44:51 -0400
From: "Greg Weber" <gdweber@gmail.com>
To: "Glen Zorn" <glenzorn@comcast.net>
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Cc: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, radiusext@ops.ietf.org
In-Reply-To: <002c01c8febf$2f4e04f0$8dea0ed0$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_88201_1355597.1218807891739"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
	 <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_Part_88201_1355597.1218807891739
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn <glenzorn@comcast.net> wrote:

> Hannes Tschofenig <mailto:// Hannes.Tschofenig@gmx.net> writes:
>
> > Bernard,
> >
> > why is there is a working group last call on this document given that
> > it
> > still has an open issue section giving me the impression that the
> > document is far from being ready?
>
> 1) As you know, the issues list is not an official WG document, but a tool
> for the use of the Chairs & as such its state has no bearing on the status
> of a document.
> 2) All 3 of the issues assigned to the extended attributes document appear
> to actually refer to RFC 5080.


I suspect Hannes was referring to the open issues section in the draft's
text,
not the list maintained by the chairs.  Regarding the latter, the issue that
I
filed (#250) was intended for your -00 draft, not RFC 5080.  I haven't read
your current draft version yet to see if these comments were addressed;
there was no response on the list -that I recall.

Greg


>
>
> >
> > Ciao
> > Hannes
> >
> > Bernard Aboba wrote:
> > > This is a reminder of the RADEXT WG Last Call on "Extended
> > > RADIUS Attributes", prior to requesting that the IESG publish it as a
> > Proposed Standard.
> > >
> > > The document is available here:
> > > http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> > attributes-04.txt
> > >
> > > WG Last Call was originally to have completed on August 10, 2008.
> > > However, due to lack of response to the RADEXT WG last call,
> > > we will be extending the WG last call to August 31, 2008.  Please
> > > review the document and post your comments to the RADEXT WG mailing
> > list
> > > (radiusext@ops.ietf.org) in the format described on the RADEXT WG
> > Issues
> > > list (http://www.drizzle.com/~aboba/RADEXT/).
> > >
> > > If you have read the document and approve of its publication, but
> > have no
> > > comments, please also post this to the list.
> > >
> > > --
> > > to unsubscribe send a message to 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/>
>

------=_Part_88201_1355597.1218807891739
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn <span dir="ltr">&lt;<a href="mailto:glenzorn@comcast.net">glenzorn@comcast.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">Hannes Tschofenig &lt;mailto:// <a href="mailto:Hannes.Tschofenig@gmx.net">Hannes.Tschofenig@gmx.net</a>&gt; writes:<br>
<br>
&gt; Bernard,<br>
&gt;<br>
&gt; why is there is a working group last call on this document given that<br>
&gt; it<br>
&gt; still has an open issue section giving me the impression that the<br>
&gt; document is far from being ready?<br>
<br>
</div>1) As you know, the issues list is not an official WG document, but a tool<br>
for the use of the Chairs &amp; as such its state has no bearing on the status<br>
of a document.<br>
2) All 3 of the issues assigned to the extended attributes document appear<br>
to actually refer to RFC 5080.</blockquote><div><br></div><div>I suspect Hannes was referring to the open issues section in the draft&#39;s text,</div><div>not the list maintained by the chairs. &nbsp;Regarding the latter, the issue that I</div>
<div>filed (#250) was intended for your -00 draft, not RFC 5080. &nbsp;I haven&#39;t read&nbsp;</div><div>your current draft version yet to see if these comments were addressed;</div><div>there was no response on the list -that I recall. &nbsp;</div>
<div><br></div><div>Greg</div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<div><div></div><div class="Wj3C7c"><br>
&gt;<br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt;<br>
&gt; Bernard Aboba wrote:<br>
&gt; &gt; This is a reminder of the RADEXT WG Last Call on &quot;Extended<br>
&gt; &gt; RADIUS Attributes&quot;, prior to requesting that the IESG publish it as a<br>
&gt; Proposed Standard.<br>
&gt; &gt;<br>
&gt; &gt; The document is available here:<br>
&gt; &gt; <a href="http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-" target="_blank">http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-</a><br>
&gt; attributes-04.txt<br>
&gt; &gt;<br>
&gt; &gt; WG Last Call was originally to have completed on August 10, 2008.<br>
&gt; &gt; However, due to lack of response to the RADEXT WG last call,<br>
&gt; &gt; we will be extending the WG last call to August 31, 2008. &nbsp;Please<br>
&gt; &gt; review the document and post your comments to the RADEXT WG mailing<br>
&gt; list<br>
&gt; &gt; (<a href="mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</a>) in the format described on the RADEXT WG<br>
&gt; Issues<br>
&gt; &gt; list (<a href="http://www.drizzle.com/~aboba/RADEXT/" target="_blank">http://www.drizzle.com/~aboba/RADEXT/</a>).<br>
&gt; &gt;<br>
&gt; &gt; If you have read the document and approve of its publication, but<br>
&gt; have no<br>
&gt; &gt; comments, please also post this to the list.<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; to unsubscribe send a message to <a href="mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf.org</a> with<br>
&gt; &gt; the word &#39;unsubscribe&#39; in a single line as the message text body.<br>
&gt; &gt; archive: &lt;<a href="http://psg.com/lists/radiusext/" target="_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; to unsubscribe send a message to <a href="mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf.org</a> with<br>
&gt; the word &#39;unsubscribe&#39; in a single line as the message text body.<br>
&gt; archive: &lt;<a href="http://psg.com/lists/radiusext/" target="_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
<br>
<br>
<br>
--<br>
to unsubscribe send a message to <a href="mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf.org</a> with<br>
the word &#39;unsubscribe&#39; in a single line as the message text body.<br>
archive: &lt;<a href="http://psg.com/lists/radiusext/" target="_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
</div></div></blockquote></div><br></div>

------=_Part_88201_1355597.1218807891739--

--
to unsubscribe send a message to 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 Aug 15 08:08:32 2008
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 E87FF3A6B99
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 08:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.122
X-Spam-Level: 
X-Spam-Status: No, score=-0.122 tagged_above=-999 required=5 tests=[AWL=0.314,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	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 Za8Q+iT6MhpQ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 08:08:31 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 582543A6911
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 08:08:31 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU0pX-000Bd6-ST
	for radiusext-data@psg.com; Fri, 15 Aug 2008 15:03:07 +0000
Received: from [76.96.62.64] (helo=QMTA07.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KU0pN-000BcE-TT
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 15:03:05 +0000
Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44])
	by QMTA07.westchester.pa.mail.comcast.net with comcast
	id 2aP81a0090xGWP857f2xZR; Fri, 15 Aug 2008 15:02:57 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA12.westchester.pa.mail.comcast.net with comcast
	id 2f1w1a00J5TN7tY3Yf2VQ2; Fri, 15 Aug 2008 15:02:52 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=48vgC7mUAAAA:8 a=Cv6e0pkHAAAA:8 a=No5EcEP4AAAA:8 a=ocyef1Fx8lWH9WZ7xnMA:9
 a=-VxYxOsZoErW4pkpkloA:7 a=2PyrvVxlzShZ1Zg9VHgOEz9OLgkA:4 a=MSl-tDqOz04A:10
 a=si9q_4b84H0A:10 a=BFDKbZatV3MA:10 a=SKpDKCWXRSQA:10 a=yMhMjlubAAAA:8
 a=SSmOFEACAAAA:8 a=eG2L4FfVyZdknPpZTF4A:7 a=-Jhs7iYPk7MJSakSivKDkwksg-MA:4
 a=37WNUvjkh6kA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Greg Weber'" <gdweber@gmail.com>
Cc: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>	 <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net> <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>
In-Reply-To: <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 22:01:38 +0700
Message-ID: <005301c8fee7$e2d305c0$a8791140$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0054_01C8FF22.8F31DDC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj+3Rj1HVv1sjaWSxmopbH4DOoxmwAChFmA
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a multipart message in MIME format.

------=_NextPart_000_0054_01C8FF22.8F31DDC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greg Weber [mailto:gdweber@gmail.com]  writes:


On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn <glenzorn@comcast.net> wrote:

Hannes Tschofenig <mailto:// Hannes.Tschofenig@gmx.net> writes:

> Bernard,
>
> why is there is a working group last call on this document given that
> it
> still has an open issue section giving me the impression that the
> document is far from being ready?

1) As you know, the issues list is not an official WG document, but a tool
for the use of the Chairs & as such its state has no bearing on the status
of a document.
2) All 3 of the issues assigned to the extended attributes document appear
to actually refer to RFC 5080.

 

I suspect Hannes was referring to the open issues section in the draft's
text,

not the list maintained by the chairs.  Regarding the latter, the issue that
I

filed (#250) was intended for your -00 draft, not RFC 5080.  

 

Be that as it may, the link points to an issue raised by Bernard re: the
Fixes draft.

 

I haven't read 

your current draft version yet to see if these comments were addressed;

there was no response on the list -that I recall.  

 

Probably not, since it was an individual submission & last time I checked
the authors of such have no obligation to respond to the WG, which in turn
has no control over the work.  

 

Greg

 

 


>
> Ciao
> Hannes
>
> Bernard Aboba wrote:
> > This is a reminder of the RADEXT WG Last Call on "Extended
> > RADIUS Attributes", prior to requesting that the IESG publish it as a
> Proposed Standard.
> >
> > The document is available here:
> > http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> attributes-04.txt
> >
> > WG Last Call was originally to have completed on August 10, 2008.
> > However, due to lack of response to the RADEXT WG last call,
> > we will be extending the WG last call to August 31, 2008.  Please
> > review the document and post your comments to the RADEXT WG mailing
> list
> > (radiusext@ops.ietf.org) in the format described on the RADEXT WG
> Issues
> > list (http://www.drizzle.com/~aboba/RADEXT/).
> >
> > If you have read the document and approve of its publication, but
> have no
> > comments, please also post this to the list.
> >
> > --
> > to unsubscribe send a message to 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/>

 


------=_NextPart_000_0054_01C8FF22.8F31DDC0
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=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:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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'>

<div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Greg
Weber [mailto:gdweber@gmail.com] &nbsp;writes:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
</span>On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn &lt;<a
href=3D"mailto:glenzorn@comcast.net">glenzorn@comcast.net</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hannes Tschofenig =
&lt;mailto://
<a =
href=3D"mailto:Hannes.Tschofenig@gmx.net">Hannes.Tschofenig@gmx.net</a>&g=
t;
writes:<br>
<br>
&gt; Bernard,<br>
&gt;<br>
&gt; why is there is a working group last call on this document given =
that<br>
&gt; it<br>
&gt; still has an open issue section giving me the impression that =
the<br>
&gt; document is far from being ready?<o:p></o:p></p>

</div>

<p class=3DMsoNormal>1) As you know, the issues list is not an official =
WG
document, but a tool<br>
for the use of the Chairs &amp; as such its state has no bearing on the =
status<br>
of a document.<br>
2) All 3 of the issues assigned to the extended attributes document =
appear<br>
to actually refer to RFC 5080.<o:p></o:p></p>

<div>

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

</div>

<div>

<p class=3DMsoNormal>I suspect Hannes was referring to the open issues =
section in
the draft's text,<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>not the list maintained by the chairs. =
&nbsp;Regarding the
latter, the issue that I<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>filed (#250) was intended for your -00 draft, not =
RFC 5080.
&nbsp;<span style=3D'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:"Arial =
Black","sans-serif";
color:#7030A0'>Be that as it may, the link points to an issue raised by =
Bernard
re: the Fixes draft.<o:p></o:p></span></p>

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

<p class=3DMsoNormal>I haven't read&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>your current draft version yet to see if these =
comments were
addressed;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>there was no response on the list -that I recall. =
&nbsp;<o:p></o:p></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:"Arial =
Black","sans-serif";
color:#7030A0'>Probably not, since it was an individual submission &amp; =
last
time I checked the authors of such have no obligation to respond to the =
WG,
which in turn has no control over the work.&nbsp; <o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>Greg<o:p></o:p></p>

</div>

<div>

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

</div>

<blockquote style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>

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

<div>

<div>

<p class=3DMsoNormal><br>
&gt;<br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt;<br>
&gt; Bernard Aboba wrote:<br>
&gt; &gt; This is a reminder of the RADEXT WG Last Call on =
&quot;Extended<br>
&gt; &gt; RADIUS Attributes&quot;, prior to requesting that the IESG =
publish it
as a<br>
&gt; Proposed Standard.<br>
&gt; &gt;<br>
&gt; &gt; The document is available here:<br>
&gt; &gt; <a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-"
target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-radext-e=
xtended-</a><br>
&gt; attributes-04.txt<br>
&gt; &gt;<br>
&gt; &gt; WG Last Call was originally to have completed on August 10, =
2008.<br>
&gt; &gt; However, due to lack of response to the RADEXT WG last =
call,<br>
&gt; &gt; we will be extending the WG last call to August 31, 2008.
&nbsp;Please<br>
&gt; &gt; review the document and post your comments to the RADEXT WG =
mailing<br>
&gt; list<br>
&gt; &gt; (<a =
href=3D"mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</a>)
in the format described on the RADEXT WG<br>
&gt; Issues<br>
&gt; &gt; list (<a href=3D"http://www.drizzle.com/~aboba/RADEXT/" =
target=3D"_blank">http://www.drizzle.com/~aboba/RADEXT/</a>).<br>
&gt; &gt;<br>
&gt; &gt; If you have read the document and approve of its publication, =
but<br>
&gt; have no<br>
&gt; &gt; comments, please also post this to the list.<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; to unsubscribe send a message to <a
href=3D"mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf=
.org</a>
with<br>
&gt; &gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; &gt; archive: &lt;<a href=3D"http://psg.com/lists/radiusext/" =
target=3D"_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; to unsubscribe send a message to <a
href=3D"mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf=
.org</a>
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;<a href=3D"http://psg.com/lists/radiusext/" =
target=3D"_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
<br>
<br>
<br>
--<br>
to unsubscribe send a message to <a =
href=3D"mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf=
.org</a>
with<br>
the word 'unsubscribe' in a single line as the message text body.<br>
archive: &lt;<a href=3D"http://psg.com/lists/radiusext/" =
target=3D"_blank">http://psg.com/lists/radiusext/</a>&gt;<o:p></o:p></p>

</div>

</div>

</blockquote>

</div>

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

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0054_01C8FF22.8F31DDC0--



--
to unsubscribe send a message to 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 Aug 15 08:56:56 2008
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 DF8693A67A8
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 08:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.064
X-Spam-Level: *
X-Spam-Status: No, score=1.064 tagged_above=-999 required=5 tests=[AWL=-0.914,
	BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	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 UrNs7iEAjXvz
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 08:56:54 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 247683A6810
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 08:56:54 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU1az-000GD8-7j
	for radiusext-data@psg.com; Fri, 15 Aug 2008 15:52:09 +0000
Received: from [76.96.62.96] (helo=QMTA09.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KU1au-000GCg-NI
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 15:52:07 +0000
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36])
	by QMTA09.westchester.pa.mail.comcast.net with comcast
	id 2bKv1a00E0mv7h059fs4Be; Fri, 15 Aug 2008 15:52:04 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA11.westchester.pa.mail.comcast.net with comcast
	id 2fqq1a00D5TN7tY3XfrUgH; Fri, 15 Aug 2008 15:51:56 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=Fs30csCArJFmjaezrVMA:9 a=_SNubCq4-JWsw8Fj8Ew94HqfTZEA:4 a=y4M8Ahb7xz0A:10
 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=onrPpW1F1sZDmv-9QGQA:9
 a=yPL_8lgDq6lpLIN3JPAA:7 a=aFvjbRDTB4H8VP2jI0kyyPWrMQ0A:4 a=37WNUvjkh6kA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Glen Zorn'" <glenzorn@comcast.net>,
	"'Greg Weber'" <gdweber@gmail.com>
Cc: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>	 <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net> <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com> <005301c8fee7$e2d305c0$a8791140$@net>
In-Reply-To: <005301c8fee7$e2d305c0$a8791140$@net>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 22:50:31 +0700
Message-ID: <005b01c8feee$ba955700$2fc00500$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005C_01C8FF29.66F45610"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj+3Rj1HVv1sjaWSxmopbH4DOoxmwAChFmAAAG+UmA=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a multipart message in MIME format.

------=_NextPart_000_005C_01C8FF29.66F45610
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

.

 

I haven't read 

your current draft version yet to see if these comments were addressed;

there was no response on the list -that I recall.  

 

Probably not, since it was an individual submission & last time I checked
the authors of such have no obligation to respond to the WG, which in turn
has no control over the work.  

 

Of course, since the draft is now a WG item I'd love to address your
comments (if I could only see them ;-).

 

.


------=_NextPart_000_005C_01C8FF29.66F45610
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=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:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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'>

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

<div>

<div>

<div>

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

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

<p class=3DMsoNormal>I haven't read&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>your current draft version yet to see if these =
comments were
addressed;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>there was no response on the list -that I recall. =
&nbsp;<o:p></o:p></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:"Arial =
Black","sans-serif";
color:#7030A0'>Probably not, since it was an individual submission &amp; =
last
time I checked the authors of such have no obligation to respond to the =
WG, which
in turn has no control over the work.&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:"Arial =
Black","sans-serif";
color:#1F497D'>Of course, since the draft is now a WG item I'd love to =
address your
comments (if I could only see them ;-).<o:p></o:p></span></p>

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

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

</div>

</div>

</div>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_005C_01C8FF29.66F45610--



--
to unsubscribe send a message to 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 Aug 15 09:05:34 2008
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 ADB8D3A6ABD
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 09:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5
	tests=[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 FOFkHaLOps0S
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 09:05:33 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 9EADD3A67A8
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 09:05:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU1jd-000H73-K9
	for radiusext-data@psg.com; Fri, 15 Aug 2008 16:01:05 +0000
Received: from [74.125.44.29] (helo=yx-out-2324.google.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <gdweber@gmail.com>)
	id 1KU1jZ-000H6g-Aw
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 16:01:03 +0000
Received: by yx-out-2324.google.com with SMTP id 8so791471yxb.71
        for <radiusext@ops.ietf.org>; Fri, 15 Aug 2008 09:01:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:cc:in-reply-to:mime-version:content-type:references;
        bh=eVRIXPD28BfH/7IB8rzb9cM4IcG9IiDznQkiAq39g50=;
        b=oRVtT09O4G06/ArRFJcrL9kFUl1sPDrNB7g1ThmkUIJaBxrpG/ZVsp8CMzc1mdPQLN
         CnqzX/RZgg6GCWM9h8PvypPD0Qi2oyAsAQ79usGe4nVJnY0Cq9XEkIxPyHngqCzUJq7i
         YlbBB7UIlLpfXDpn+Tw2WXQqSRPPOFN9icQzY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:references;
        b=GrjSa1UFHBgZbLQ0hbJnwkevv1g/ljJqxeOubpKPa6Zvyu4S3423RhGOwtgYF0oqYM
         J4K1hFffMvqHqunpQIqSMFvmxTh/xYPu/N/KXH/OIjJb+WPzrRa1U/L6vgP+hZZzYim9
         XpJ0b4wxHLplGY0pUGCBmfPzjoKzQCuqnVrwQ=
Received: by 10.115.89.1 with SMTP id r1mr2730144wal.12.1218816059690;
        Fri, 15 Aug 2008 09:00:59 -0700 (PDT)
Received: by 10.114.79.8 with HTTP; Fri, 15 Aug 2008 09:00:59 -0700 (PDT)
Message-ID: <d11ef1350808150900o496b3c3as31ca2d073bfebc63@mail.gmail.com>
Date: Fri, 15 Aug 2008 12:00:59 -0400
From: "Greg Weber" <gdweber@gmail.com>
To: "Glen Zorn" <glenzorn@comcast.net>
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Cc: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, radiusext@ops.ietf.org
In-Reply-To: <005b01c8feee$ba955700$2fc00500$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_90886_12638339.1218816059680"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
	 <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net>
	 <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>
	 <005301c8fee7$e2d305c0$a8791140$@net>
	 <005b01c8feee$ba955700$2fc00500$@net>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_Part_90886_12638339.1218816059680
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Fri, Aug 15, 2008 at 11:50 AM, Glen Zorn <glenzorn@comcast.net> wrote:

>     =85
>
>
>
> I haven't read
>
> your current draft version yet to see if these comments were addressed;
>
> there was no response on the list -that I recall.
>
>
>
> Probably not, since it was an individual submission & last time I checked
> the authors of such have no obligation to respond to the WG, which in tur=
n
> has no control over the work.
>
>
>
> Of course, since the draft is now a WG item I'd love to address your
> comments (if I could only see them ;-).
>

These were my comments on the -00 WG draft:
  http://ops.ietf.org/lists/radiusext/2008/msg00095.html
Not sure if these have been addressed or obviated by now- or if they
were originally valid...

Greg

>
>
> =85
>

------=_Part_90886_12638339.1218816059680
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote">On Fri, Aug 15, 2008 at=
 11:50 AM, Glen Zorn <span dir=3D"ltr">&lt;<a href=3D"mailto:glenzorn@comca=
st.net">glenzorn@comcast.net</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex;">









<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div>

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

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

<div>

<div><div class=3D"Ih2E3d">

<div>

<p><span style=3D"font-size:11.0pt;color:#1F497D">=85</span></p>

<p><span style=3D"font-size:11.0pt;color:#7030A0">&nbsp;</span></p>

<p>I haven&#39;t read&nbsp;</p>

</div>

<div>

<p>your current draft version yet to see if these comments were
addressed;</p>

</div>

</div><div><div class=3D"Ih2E3d">

<p>there was no response on the list -that I recall. &nbsp;</p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></p>

<p><span style=3D"font-size:11.0pt;color:#7030A0">Probably not, since it wa=
s an individual submission &amp; last
time I checked the authors of such have no obligation to respond to the WG,=
 which
in turn has no control over the work.&nbsp; </span></p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></p>

</div><p><span style=3D"font-size:11.0pt;color:#1F497D">Of course, since th=
e draft is now a WG item I&#39;d love to address your
comments (if I could only see them ;-).</span></p></div></div></div></div><=
/div></div></div></blockquote><div><br></div><div>These were my comments on=
 the -00 WG draft:</div><div>&nbsp;&nbsp;<a href=3D"http://ops.ietf.org/lis=
ts/radiusext/2008/msg00095.html">http://ops.ietf.org/lists/radiusext/2008/m=
sg00095.html</a></div>
<div>Not sure if these have been addressed or obviated by now- or if they</=
div><div>were originally valid...</div><div><br></div><div>Greg&nbsp;</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><div style=3D"borde=
r:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div style=
=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><di=
v><div><div>
<p><span style=3D"font-size:11.0pt;color:#1F497D"></span></p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">=85</span></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>


</blockquote></div><br></div>

------=_Part_90886_12638339.1218816059680--

--
to unsubscribe send a message to 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 Aug 15 09:12:14 2008
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 A38B93A6B64
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 09:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.087
X-Spam-Level: 
X-Spam-Status: No, score=-0.087 tagged_above=-999 required=5 tests=[AWL=0.351,
	BAYES_00=-2.599, 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 dAM0Nc3OZYCY
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 09:12:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 5FBB63A6A47
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 09:12:13 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU1qw-000Hmr-MQ
	for radiusext-data@psg.com; Fri, 15 Aug 2008 16:08:38 +0000
Received: from [76.96.30.16] (helo=QMTA01.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KU1qs-000HmO-Uq
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 16:08:36 +0000
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id 2blR1a00817UAYkA1g8ayB; Fri, 15 Aug 2008 16:08:34 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA13.emeryville.ca.mail.comcast.net with comcast
	id 2g881a0125TN7tY8Zg8Qy0; Fri, 15 Aug 2008 16:08:32 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=vdEc4T8do3wNX8INcEUA:9 a=J5PmvoUieidFoswxIZU6QjezDXkA:4 a=r5QHxzKXScQA:10
 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com>
In-Reply-To: <48A3FAA1.1020109@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 23:07:50 +0700
Message-ID: <006f01c8fef1$17fdc6a0$47f953e0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj98OGpJZ+vwklsSX6zK6+G8ry4pQA/omMg
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok <mailto://aland@deployingradius.com> writes:

...

> Section 4:
> ...
>    o  The final octet of the header contains the More flag and Tag
>       field.  If the one bit More flag is set (1) this indicates that
>       the encapsulated TLV is continued in the following Extended
>       Attribute; if the More flag is clear (0) then all of the
>       encapsulated TLVs fit into the current Extended Attribute.  The
>       More flag MUST NOT be set if the Extended Attribute contains more
>       than one TLV.
> 
>   To be clear: this means that the Extended-Attribute can encapsulate
> multiple TLV's if they're short, or only one TLV if it's long.

OK, are you saying that the existing text isn't clear?  It seems pretty
precise to me, should it be more vague (e.g., "long" & "short")?

> 
> 
> Section 5:
> 
>    M (More)
> 
>       The More Flag is one (1) bit in length and MUST be present.  When
>       a value to be transmitted exceeds 246 octets in length it is
>       fragmented over two or more Extended Attributes.  If the More
> Flag
>       is set (1), this indicates that the Value field of the Extended
>       Attribute contains a fragment of a larger value, which is
>       continued in the next Extended Attribute of the same Ext-Type.
> 
>   Can we add a MUST?  i.e. If the More Flag is set, the next attribute
> MUST be an Extended-Attribute of the same Extended-Type.

Fine

...

>    Ext-Type
> 
>       Two (2) octets.  Up-to-date values of the Ext-Type field are
>       specified in the most recent "Assigned Numbers" [IANA].  Values
>       XXXX-YYYY are reserved.
> 
>   I would suggest reserving the top 1K: 64512-65535

Rationale?

...

>    Consider the following structure:
> 
>      struct
>        Integer a;
>        String  b;
>        Integer c;
>      endStruct
> 
>   What syntax is this?  I think I understand it, but I'm not sure
> everyone will come to a shared understanding.  Maybe instead the
> example
> can be given by reference to existing RADIUS data types.  e.g. A
> structure of RADIUS data types (integer, text, integer) would
> previously
> have to be encoded as three separate and independent attributes.  

Previously, such a structure was impossible to encode in RADIUS.

> Here,
> it can be encoded as 3 attributes sharing a common tag.

Or as 3 TLVs in a single attribute (depending upon the length of the string.

> 
>   Reading the rest of the example, I find the b(4,5) syntax very
> awkward.  I suggest discarding it, and just referring to the diagrams.

Actually, I'd just as soon discard the examples: this draft has way too much
flavor of a tutorial for my taste...

> 
>   The examples could also given broken-out hex encoding of the
> attributes, which may be clearer than the ASCII art diagrams.  e.g.
> 
>   1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f

You're joking, right?

> 
> 7.  Security Considerations
> 
>    I suggest adding a note that a new attribute encoding is an
> opportunity for buffer overflows, inadequate checks, etc.  Implementors
> SHOULD take care to validate the lengths, etc. before decoding the
> contents of the attributes.
> 
> 8.  IANA Considerations
> ...
>    It also requires that IANA set up a new registry for the RADIUS
>    Extended Attribute Types.
> 
>   I suggest leaving the first 0..255 attributes as unallocated, in
> order
> to avoid confusion with legacy RADIUS attributes.

Presumably the people who would get confused are those who have to be told
to protect against buffer overflows (& send "hello" as five separate
attributes), right?

...



--
to unsubscribe send a message to 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 Aug 15 09:47:17 2008
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 5132828C261
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 09:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.107
X-Spam-Level: 
X-Spam-Status: No, score=-0.107 tagged_above=-999 required=5 tests=[AWL=0.330,
	BAYES_00=-2.599, 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 hBdSXALEcN6d
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 09:47:16 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 77E1D28C258
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 09:47:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU2Ox-000LPJ-4M
	for radiusext-data@psg.com; Fri, 15 Aug 2008 16:43:47 +0000
Received: from [76.96.62.96] (helo=QMTA09.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KU2Ot-000LOc-JZ
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 16:43:45 +0000
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19])
	by QMTA09.westchester.pa.mail.comcast.net with comcast
	id 2eJd1a0060QuhwU59gjjxR; Fri, 15 Aug 2008 16:43:43 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA02.westchester.pa.mail.comcast.net with comcast
	id 2gig1a00Y5TN7tY3NgjD65; Fri, 15 Aug 2008 16:43:38 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=7jpLcmv7bF64EOSk06gA:9 a=Ul1run1PSDSiEToXFXfepm4nBO0A:4 a=ufO146cb3fEA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Stefan Winter'" <stefan.winter@restena.lu>,
	"'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu>
In-Reply-To: <48A40157.2050706@restena.lu>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 23:42:20 +0700
Message-ID: <009a01c8fef5$f5273850$df75a8f0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj99HP/tjdafrPARXuHUs1IJ4c0YgA/a3wA
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Stefan Weber <maito://stefan.winter@restena.lu> writes:

...

> TLV encoding rules: Ext-Length field misses its unit ... (in octets)...

OK

> 
> Example in Figure 3: VSA Length. 7 + 9 = 16, not 15.

OK

...

> Some nitbits:
> 
> - Intro: "101 or so have been". Or so sound a bit colloquial.
> - first example: "Extended-Type *of* 257 by IANA." ( not 0f)

OK

...



--
to unsubscribe send a message to 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 Aug 15 10:04:54 2008
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 D17943A6768
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 10:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.125
X-Spam-Level: 
X-Spam-Status: No, score=-0.125 tagged_above=-999 required=5 tests=[AWL=0.312,
	BAYES_00=-2.599, 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 ixrg6U1fh2fY
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 10:04:53 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id B6AE33A68F9
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 10:04:53 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU2fD-000N7Z-B9
	for radiusext-data@psg.com; Fri, 15 Aug 2008 17:00:35 +0000
Received: from [76.96.30.56] (helo=QMTA06.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KU2f5-000N6q-SG
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 17:00:33 +0000
Received: from OMTA04.emeryville.ca.mail.comcast.net ([76.96.30.35])
	by QMTA06.emeryville.ca.mail.comcast.net with comcast
	id 2fuD1a00a0lTkoCA6h0T6Z; Fri, 15 Aug 2008 17:00:27 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA04.emeryville.ca.mail.comcast.net with comcast
	id 2gzx1a00A5TN7tY8Qh0FcQ; Fri, 15 Aug 2008 17:00:25 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=lgGLWeF3AAAA:8 a=Yphh8Qa9hEWOx3zOr9wA:9 a=2F8fy9YlLsjZLGkN8kQA:7
 a=qp43znl5uoQYK1PjxRjHoKIq_dYA:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'Stefan Winter'" <stefan.winter@restena.lu>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A40157.2050706@restena.lu> <000701c8fdfe$5e220ef0$1a662cd0$@net> <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com> <48A419C8.2030308@restena.lu> <004f01c8fe33$ed1b84d0$c7528e70$@net> <48A486FC.40007@deployingradius.com>
In-Reply-To: <48A486FC.40007@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 23:59:37 +0700
Message-ID: <009b01c8fef8$55f76400$01e62c00$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj+Q9IHh1Eq44ROQd2GY3z+cDCn5gAsjWSQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> >> Alan's wording "The More Flag MUST NOT be set if the Length is less
> >> than
> >> 255." sounds good to me.
> >
> > My point was that making these kinds of rules is pointless: if
> someone wants
> > to split "Hello" into 5 separate attributes they either have a very
> good
> > reason to do so that none of us can foresee or they will soon be
> finding
> > gainful employment in a different field.  In any case, it's not
> possible to
> > protect people from their own stupidity (besides, they could still do
> it
> > with tags).
> 
>   It's only one sentence.  

A sentence here, a sentence there & pretty soon you're outlawing driving
while blindfolded (http://www.whatcar.com/news-article.aspx?NA=229117)...

> And it will stop the stupid people from
> afflicting everyone else.

No, they can still do it (even more stupidly) with tags...

> 
>   RFC 2865 has comments saying:
> 
>       The secret MUST NOT be empty (length 0) since this would allow
>       packets to be trivially forged.
> 
>   Which were inserted because of real-world exposure to implementations
> having *no* configuration for shared secrets. (i.e. they were always
> NUL).

That may be stupid, or not, depending upon the level of other security in
the network...

> 
>   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 Aug 15 10:06:26 2008
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 ECE563A6882
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 10:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.066
X-Spam-Level: *
X-Spam-Status: No, score=1.066 tagged_above=-999 required=5 tests=[AWL=-0.912,
	BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	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 GxGH4T-QsSt3
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 10:06:23 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 343AF3A6768
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 10:06:23 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU2h6-000NKX-Kp
	for radiusext-data@psg.com; Fri, 15 Aug 2008 17:02:32 +0000
Received: from [76.96.30.17] (helo=QMTA10.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KU2h1-000NJe-8W
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 17:02:29 +0000
Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id 2by71a0040b6N64AAh2SR3; Fri, 15 Aug 2008 17:02:27 +0000
Received: from gwzPC ([124.120.226.252])
	by OMTA03.emeryville.ca.mail.comcast.net with comcast
	id 2h1t1a00V5TN7tY8Ph2DY8; Fri, 15 Aug 2008 17:02:23 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=48vgC7mUAAAA:8 a=Fs30csCArJFmjaezrVMA:9 a=HMuhD6t0gMbYhYMshPClId-M_4kA:4
 a=MSl-tDqOz04A:10 a=si9q_4b84H0A:10 a=SKpDKCWXRSQA:10 a=yMhMjlubAAAA:8
 a=SSmOFEACAAAA:8 a=jU9UbnIbS8pyuuQtwoMA:9 a=zpknMiYYS8VR480iIfQA:7
 a=ZnnLtF9URlXnQ6vWuP9cE3acPSEA:4 a=37WNUvjkh6kA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Greg Weber'" <gdweber@gmail.com>
Cc: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>	 <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net>	 <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>	 <005301c8fee7$e2d305c0$a8791140$@net>	 <005b01c8feee$ba955700$2fc00500$@net> <d11ef1350808150900o496b3c3as31ca2d073bfebc63@mail.gmail.com>
In-Reply-To: <d11ef1350808150900o496b3c3as31ca2d073bfebc63@mail.gmail.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 00:01:35 +0700
Message-ID: <009c01c8fef8$9c532ba0$d4f982e0$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_009D_01C8FF33.48B203A0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj+8B12LwlU9bUHS12+ZopF6L3EHgACEXFQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a multipart message in MIME format.

------=_NextPart_000_009D_01C8FF33.48B203A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greg Weber [mailto:gdweber@gmail.com]  writes:

 

On Fri, Aug 15, 2008 at 11:50 AM, Glen Zorn <glenzorn@comcast.net> wrote:

.

 

I haven't read 

your current draft version yet to see if these comments were addressed;

there was no response on the list -that I recall.  

 

Probably not, since it was an individual submission & last time I checked
the authors of such have no obligation to respond to the WG, which in turn
has no control over the work.  

 

Of course, since the draft is now a WG item I'd love to address your
comments (if I could only see them ;-).

 

These were my comments on the -00 WG draft:

  http://ops.ietf.org/lists/radiusext/2008/msg00095.html

 

Thanks!

Not sure if these have been addressed or obviated by now- or if they

were originally valid...

 

Greg 

 

.

 


------=_NextPart_000_009D_01C8FF33.48B203A0
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=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;}
 /* 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;}
@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'>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:#00B050'>Greg Weber
[mailto:gdweber@gmail.com] &nbsp;writes:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal>On Fri, Aug 15, 2008 at 11:50 AM, Glen Zorn &lt;<a
href=3D"mailto:glenzorn@comcast.net">glenzorn@comcast.net</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<div>

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

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

<div>

<div>

<div>

<div>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&#8230;</span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#7030A0'>&nbsp;</span><o:p></o:p></p>

<p>I haven't read&nbsp;<o:p></o:p></p>

</div>

<div>

<p>your current draft version yet to see if these comments were =
addressed;<o:p></o:p></p>

</div>

</div>

<div>

<div>

<p>there was no response on the list -that I recall. =
&nbsp;<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p><span style=3D'font-size:11.0pt;color:#7030A0'>Probably not, since it =
was an
individual submission &amp; last time I checked the authors of such have =
no
obligation to respond to the WG, which in turn has no control over the
work.&nbsp; </span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

</div>

<p><span style=3D'font-size:11.0pt;color:#1F497D'>Of course, since the =
draft is
now a WG item I'd love to address your comments (if I could only see =
them ;-).</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>These were my comments on the -00 WG =
draft:<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;<a
href=3D"http://ops.ietf.org/lists/radiusext/2008/msg00095.html">http://op=
s.ietf.org/lists/radiusext/2008/msg00095.html</a><o:p></o:p></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'color:#00B050'>Thanks!<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal>Not sure if these have been addressed or obviated =
by now- or
if they<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>were originally valid...<o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<blockquote style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>

<div>

<div>

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

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

<div>

<div>

<div>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&#8230;</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</blockquote>

</div>

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

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_009D_01C8FF33.48B203A0--



--
to unsubscribe send a message to 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 Aug 15 10:21:01 2008
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 3969028C263
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 10:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.589
X-Spam-Level: 
X-Spam-Status: No, score=0.589 tagged_above=-999 required=5 tests=[AWL=1.084,
	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 F9tX9nlDdFsM
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 10:21:00 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 65D7A3A6BAE
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 10:21:00 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU2vO-000OqN-5y
	for radiusext-data@psg.com; Fri, 15 Aug 2008 17:17:18 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <dnelson@elbrysnetworks.com>)
	id 1KU2vJ-000Opf-D0
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 17:17:15 +0000
Received: (qmail 7555 invoked from network); 15 Aug 2008 13:17:09 -0400
Received: from unknown (HELO xpsuperdvd2) (172.22.18.93)
  by gumby.elbrysnetworks.com with SMTP; 15 Aug 2008 13:17:09 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <AC1CFD94F59A264488DC2BEC3E890DE5065592E5@xmb-sjc-225.amer.cisco.com>
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 15 Aug 2008 13:17:12 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <D4371E585AF84CD5BDF3EC1F35DABB59@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5065592E5@xmb-sjc-225.amer.cisco.com>
Thread-Index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDAAEn0hlA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Joseph Salowey writes...

> 1. Section 4.2:
> 
> In cases where the client needs to protect all or part of the radius
> request the "hint and select" negotiation the client would provide 
> more than a hint when it chooses the algorithms for protection. 
> Perhaps hint and select is not quite the right term, may be specify
> and select?

While adding a more robust form of capabilities negotiation to RADIUS might
be a useful thing, it's not a charted work item.  I think we are stuck with
the current "hint and select" paradigm that is common usage in RADIUS today.

Perhaps I've misunderstood your comment.  Could you give an example?

> 2. Section 4.6:
> 
> Section 4.6 makes reference to security considerations text about key
> management.  Shouldn't this text be in this document?

Yes, I think so.  Would anyone like to propose some text and a citation into
RFC 4017?



--
to unsubscribe send a message to 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 Aug 15 10:39:00 2008
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 E52693A6B12
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 10:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.318
X-Spam-Level: 
X-Spam-Status: No, score=0.318 tagged_above=-999 required=5 tests=[AWL=0.813,
	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 aoJZUnFg7+ZH
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 10:38:59 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 657C03A69C2
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 10:38:58 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU3DR-0000dh-EU
	for radiusext-data@psg.com; Fri, 15 Aug 2008 17:35:57 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <dnelson@elbrysnetworks.com>)
	id 1KU3Cn-0000aD-O9
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 17:35:55 +0000
Received: (qmail 7964 invoked from network); 15 Aug 2008 13:35:16 -0400
Received: from unknown (HELO xpsuperdvd2) (172.22.18.93)
  by gumby.elbrysnetworks.com with SMTP; 15 Aug 2008 13:35:16 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <002201c8feb4$81ee5df0$85cb19d0$@net>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 15 Aug 2008 13:35:20 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <5E154780AF9E4987A71861EDFD3750C9@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <002201c8feb4$81ee5df0$85cb19d0$@net>
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> The WG Charter states that all of the existing crypto-agility
> proposals are to be published as Experimental RFCs.  In that case,
> how can the requirement that " at least one mandatory to implement 
> algorithm will be defined" (section 1.2) be fulfilled?

Why not?  The algorithms are defined in existing documents.

> Front page header:
> Since the source of the document is stated in section 1.1 to be
> the radext WG, David's role should probably be "Editor".

Yes.

> Section 1.2:
> s/propose one of more Internet Drafts/propose one or more Internet-Drafts/
> 
> Section 2:
> s/Crypto-Agility is the ability for/Crypto-agility is the ability of/

OK.

> Section 4.5, paragraph 5 states:
> 
>    Editorial Note: With the expected acceptance of the proposed RADEXT
>    WG Charter revision, some of the issues raised in the preceding
>    paragraphs become moot, and this section ought to be revised to
>    reflect the revised charter.
> 
> Haven't those charter revisions already taken place?

As of submission of the -00 draft, the IESG was still deliberating the
re-charter request.  Will be fixed in -01.

> Technical comments:
> 
> Section 2, paragraph 2 states:
> 
>    In the specific context of the RADIUS protocol and RADIUS
>    implementations, crypto-agility may be better defined as the ability
>    of RADIUS implementations to negotiate cryptographic algorithms for
>    use in RADIUS exchanges, including the cryptographic algorithms used
>    to protect RADIUS packets and to hide RADIUS Attributes.  This
>    capability covers all RADIUS message types: Access-Request/Response,
>    Accounting-Request/Response, and CoA/Disconnect-Request/Response.
> 
> Since RADIUS has no negotiation method of I'm aware (hint & 
> accept/ignore is hardly a negotiation mechanism)...

Yeah, but it's what we've got.

>... I find these statements very curious, especially in light of the
> earlier statement (section 2, paragraph 3) that the password-hiding
> function will be negotiable.  Basically, what is being called for is
> impossible in the context of the RADIUS protocol, implying that the
> negotiations would take place outside of RADIUS (e.g., in TLS).

That wasn't what I understood when I transcribed that text.  It's true that
"hint and consent" is a bit crude, but I'd like to see a more in-depth
technical exploration of why you think it makes crypto-agility impossible
within RADIUS

> Section 4.1:
> Once again, assuming a solution.  State the requirements that a solution
> must meet, not your personal assumptions about the form which the solution
> will take.  I say "personal" because a fair subset of the active WG (of
> which this document is purportedly a product) _does not_ share the
> expectation that " proposals will utilize other techniques".

I take that text to means that RADIUS over IPSec has already been defined,
and therefore proposing RADIUS over IPSec is not what we're looking for to
address RADIUS crypto-agility.  After all, if an existing solution needs
everyone's needs, why waste time on a requirements document, never mind a
solution document?  Therefore, it's reasonable to say that "Just use IPSec."
is out of scope for RADIUS crypto-agility.

> Section 4.2, paragraph 2 states:
> 
>    Included in negotiation techniques are "hint and consent" mechanisms
>    where the NAS provides a list of algorithms and the server selects
>    one.
> 
> If the server is required to select from the list it can hardly be 
> called a hint.  Once again, I can't see at all how this mechanism 
> could be made to work in the case of the Access-Request message.

Please explain.

> Section 4.3, paragraph 1 states:
> 
>    Solutions to the problem MUST demonstrate backward compatibility
>    with existing RADIUS implementations.
> 
> I would _really_ like to see some rationale for this requirement 
> (aside from "backward compatibility is sacred and must never be 
> questioned" ;-).

Given that the RADIUS protocol doesn't have a protocol version field,
maintaining backward compatibility seems pretty basic.

> Given that this is new and presumably desirable functionality,
> why is a simple upgrade path not sufficient?

A "fork-lift" upgrade?  :-)



--
to unsubscribe send a message to 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 Aug 15 15:49:08 2008
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 8FBCA3A63C9
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 15:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.494
X-Spam-Level: 
X-Spam-Status: No, score=-4.494 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	HTML_MESSAGE=0.001, 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 MMXpivOTRTLF
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 15:49:07 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0330D3A68E3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 15:49:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KU81y-0002Ag-3m
	for radiusext-data@psg.com; Fri, 15 Aug 2008 22:44:26 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <mchiba@cisco.com>)
	id 1KU81s-00029r-5z
	for radiusext@ops.ietf.org; Fri, 15 Aug 2008 22:44:23 +0000
X-IronPort-AV: E=Sophos;i="4.32,218,1217808000"; 
   d="scan'208,217";a="66316985"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
  by sj-iport-1.cisco.com with ESMTP; 15 Aug 2008 22:44:19 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m7FMiJeN018610;
	Fri, 15 Aug 2008 15:44:19 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m7FMiJ1Z008315;
	Fri, 15 Aug 2008 22:44:19 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 15 Aug 2008 15:44:19 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8FF28.741696EA"
Subject: RE: Help me about RFC3576
Date: Fri, 15 Aug 2008 15:43:59 -0700
Message-ID: <D492339CC466C84EA5E0AF1CECB20081062E44F1@xmb-sjc-21b.amer.cisco.com>
In-Reply-To: <771596.32561.qm@web35102.mail.mud.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Help me about RFC3576
Thread-Index: Acj/Ew2NPy5SzbNqRqGrplLecXBW0wAFRlPQ
References: <771596.32561.qm@web35102.mail.mud.yahoo.com>
From: "Murtaza Chiba (mchiba)" <mchiba@cisco.com>
To: <bhcuong2005@yahoo.com>, <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 15 Aug 2008 22:44:19.0463 (UTC) FILETIME=[7446C970:01C8FF28]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3108; t=1218840259; x=1219704259;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mchiba@cisco.com;
	z=From:=20=22Murtaza=20Chiba=20(mchiba)=22=20<mchiba@cisco.c
	om>
	|Subject:=20RE=3A=20Help=20me=20about=20RFC3576
	|Sender:=20;
	bh=NpHE7bgONOHnP5Z69N/gDyIdVA3mvEYiNSSIwT+S9/o=;
	b=sw1AweM29chMfgo715QSX5n3BuY45Fp4kLGkp0GQuU5iMeNFIzrprP9wbU
	C5z/677kuppR7Rz3hUuXdeqVrTnS4YY+pRjzLZvaHotCdXDv+PELOC+xNB22
	oz7CnSvG09;
Authentication-Results: sj-dkim-3; header.From=mchiba@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8FF28.741696EA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
Included radius extensions WG.   Not sure what was decided in the bis
portion.
=20
Thanks,
-Murtaza


________________________________

	From: Cuong Hoang Bui [mailto:bhcuong2005@yahoo.com]=20
	Sent: Friday, August 15, 2008 1:11 PM
	To: Murtaza Chiba (mchiba)
	Subject: Help me about RFC3576
=09
=09
Dear Mr. Chiba,

I have a question related to CoA messages.
If both supported attribute(s) and unsupported attribute(s) are included
in CoA-Request message, then what happens? NAS doesn't process packets
and return CoA-NAK back to Radius server or it processes only supported
attributes, but should it send CoA-NAK or CoA-ACK back to RADIUS server?

Thank you

Regards
Cuong
=09



------_=_NextPart_001_01C8FF28.741696EA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16674" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578094222-15082008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Included radius extensions WG.&nbsp;&nbsp; Not =
sure what=20
was decided in the bis portion.</FONT></SPAN></DIV>
<DIV><SPAN class=3D578094222-15082008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D578094222-15082008><FONT face=3DArial color=3D#0000ff =

size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D578094222-15082008><FONT face=3DArial color=3D#0000ff =

size=3D2>-Murtaza</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><BR></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Cuong Hoang Bui=20
  [mailto:bhcuong2005@yahoo.com] <BR><B>Sent:</B> Friday, August 15, =
2008 1:11=20
  PM<BR><B>To:</B> Murtaza Chiba (mchiba)<BR><B>Subject:</B> Help me =
about=20
  RFC3576<BR></FONT><BR></DIV>
  <DIV></DIV>
  <TABLE cellSpacing=3D0 cellPadding=3D0 border=3D0>
    <TBODY>
    <TR>
      <TD vAlign=3Dtop>Dear Mr. Chiba,<BR><BR>I have a question related =
to CoA=20
        messages.<BR>If both supported attribute(s) and unsupported =
attribute(s)=20
        are included in CoA-Request message, then what happens? NAS =
doesn't=20
        process packets and return CoA-NAK back to Radius server or it =
processes=20
        only supported attributes, but should it send CoA-NAK or CoA-ACK =
back to=20
        RADIUS server?<BR><BR>Thank=20
  =
you<BR><BR>Regards<BR>Cuong<BR></TD></TR></TBODY></TABLE><BR></BLOCKQUOTE=
></BODY></HTML>

------_=_NextPart_001_01C8FF28.741696EA--

--
to unsubscribe send a message to 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 Aug 15 23:15:47 2008
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 4B6D128C0D0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 15 Aug 2008 23:15:47 -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 o++Jvtd0inSb
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 15 Aug 2008 23:15:46 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 38A0928C0D9
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 15 Aug 2008 23:15:46 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUF0W-0007Zv-6j
	for radiusext-data@psg.com; Sat, 16 Aug 2008 06:11:24 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KUF0S-0007ZS-N1
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 06:11:22 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id B732B123423B;
	Sat, 16 Aug 2008 08:11:15 +0200 (CEST)
Message-ID: <48A66F52.3060302@deployingradius.com>
Date: Sat, 16 Aug 2008 08:10:26 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: "'David B. Nelson'" <dnelson@elbrysnetworks.com>, 
 radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net>
In-Reply-To: <002001c8fea3$19c89800$4d59c800$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> I believe that he meant that all fragments of a given attribute must be
> contiguous in the original packet...

  RFC 3579, Section 3.1:

      If multiple
      EAP-Message attributes are contained within an Access-Request or
      Access-Challenge packet, they MUST be in order and they MUST be
      consecutive attributes in the Access-Request or Access-Challenge
      packet.

  Requiring this for Extended-Attribute is a good idea.

  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 Aug 16 01:23:10 2008
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 7B9A83A6A18
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 01:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.096
X-Spam-Level: 
X-Spam-Status: No, score=-0.096 tagged_above=-999 required=5 tests=[AWL=0.341,
	BAYES_00=-2.599, 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 wTMVzje1KWEZ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 01:23:09 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id EF6B23A69DB
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 01:23:08 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUGzG-000GnE-8K
	for radiusext-data@psg.com; Sat, 16 Aug 2008 08:18:14 +0000
Received: from [76.96.30.17] (helo=QMTA10.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUGzC-000Gmt-5J
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 08:18:12 +0000
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id 2wGV1a00J17UAYkAAwJ97E; Sat, 16 Aug 2008 08:18:09 +0000
Received: from gwzPC ([124.120.221.249])
	by OMTA13.emeryville.ca.mail.comcast.net with comcast
	id 2wHa1a0035PTbrQ8ZwHz6G; Sat, 16 Aug 2008 08:18:07 +0000
X-Authority-Analysis: v=1.0 c=1 a=_KgF-38uPHMA:10 a=P4Kb_900TAMA:10
 a=No5EcEP4AAAA:8 a=YgKt5_3j6gIfAaYDXB4A:9 a=SH3CnoJVg1R1b5it260A:7
 a=OlCkJg9b7b8JxwRWnFEK-WWBnmUA:4 a=-utQw5L2n1AA:10 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <002201c8feb4$81ee5df0$85cb19d0$@net> <5E154780AF9E4987A71861EDFD3750C9@xpsuperdvd2>
In-Reply-To: <5E154780AF9E4987A71861EDFD3750C9@xpsuperdvd2>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Sat, 16 Aug 2008 15:17:03 +0700
Message-ID: <000101c8ff78$854b6b90$8fe242b0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcAAAWPE8A==
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson <mailto://dnelson@elbrysnetworks.com> writes:

> Glen Zorn writes...
> 
> > The WG Charter states that all of the existing crypto-agility
> > proposals are to be published as Experimental RFCs.  In that case,
> > how can the requirement that " at least one mandatory to implement
> > algorithm will be defined" (section 1.2) be fulfilled?
> 
> Why not?  The algorithms are defined in existing documents.

What documents?  Since an Experimental RFC holds no standing as a standard,
how can it specify _anything_ as mandatory?

...

> > Technical comments:
> >
> > Section 2, paragraph 2 states:
> >
> >    In the specific context of the RADIUS protocol and RADIUS
> >    implementations, crypto-agility may be better defined as the
> ability
> >    of RADIUS implementations to negotiate cryptographic algorithms
> for
> >    use in RADIUS exchanges, including the cryptographic algorithms
> used
> >    to protect RADIUS packets and to hide RADIUS Attributes.  This
> >    capability covers all RADIUS message types: Access-
> Request/Response,
> >    Accounting-Request/Response, and CoA/Disconnect-Request/Response.
> >
> > Since RADIUS has no negotiation method of I'm aware (hint &
> > accept/ignore is hardly a negotiation mechanism)...
> 
> Yeah, but it's what we've got.
> 
> >... I find these statements very curious, especially in light of the
> > earlier statement (section 2, paragraph 3) that the password-hiding
> > function will be negotiable.  Basically, what is being called for is
> > impossible in the context of the RADIUS protocol, implying that the
> > negotiations would take place outside of RADIUS (e.g., in TLS).
> 
> That wasn't what I understood when I transcribed that text.  It's true
> that
> "hint and consent" is a bit crude, but I'd like to see a more in-depth
> technical exploration of why you think it makes crypto-agility
> impossible
> within RADIUS

The last time I checked (please correct me if I'm wrong), the "hint" was
from a NAS to a server regarding what the NAS wanted returned.  In many
cases, these "hints" would not be anything of the sort; instead, they will
be a simple statement of the algorithm used by the NAS.  Examples are the
User-Password Attribute & request authentication/integrity protection.  The
only way that I can think of for the server to refuse the "hint" would be if
we were to hi-jack the Access-Challenge message, which in itself constitutes
a novel negotiation method for RADIUS.

> 
> > Section 4.1:
> > Once again, assuming a solution.  State the requirements that a
> solution
> > must meet, not your personal assumptions about the form which the
> solution
> > will take.  I say "personal" because a fair subset of the active WG
> (of
> > which this document is purportedly a product) _does not_ share the
> > expectation that " proposals will utilize other techniques".
> 
> I take that text to means that RADIUS over IPSec has already been
> defined,
> and therefore proposing RADIUS over IPSec is not what we're looking for
> to
> address RADIUS crypto-agility.  After all, if an existing solution
> needs
> everyone's needs, why waste time on a requirements document, never mind
> a
> solution document?  Therefore, it's reasonable to say that "Just use
> IPSec."
> is out of scope for RADIUS crypto-agility.

The text to which I was referring is "Therefore, it is expected that
proposals will utilize other techniques".

> 
> > Section 4.2, paragraph 2 states:
> >
> >    Included in negotiation techniques are "hint and consent"
> mechanisms
> >    where the NAS provides a list of algorithms and the server selects
> >    one.
> >
> > If the server is required to select from the list it can hardly be
> > called a hint.  Once again, I can't see at all how this mechanism
> > could be made to work in the case of the Access-Request message.
> 
> Please explain.

See above.

> 
> > Section 4.3, paragraph 1 states:
> >
> >    Solutions to the problem MUST demonstrate backward compatibility
> >    with existing RADIUS implementations.
> >
> > I would _really_ like to see some rationale for this requirement
> > (aside from "backward compatibility is sacred and must never be
> > questioned" ;-).
> 
> Given that the RADIUS protocol doesn't have a protocol version field,
> maintaining backward compatibility seems pretty basic.

OK, so that sounds an awful lot like " backward compatibility is sacred and
must never be questioned" to me.  

> 
> > Given that this is new and presumably desirable functionality,
> > why is a simple upgrade path not sufficient?
> 
> A "fork-lift" upgrade?  :-)

Hardly. New messages and or capabilities can fairly easily be introduced in
a piece-meal fashion, as long as it is done with care.
 
> 
> 
> 
> --
> to unsubscribe send a message to 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  Sat Aug 16 03:18:39 2008
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 04ACD3A69CC
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 03:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.112
X-Spam-Level: 
X-Spam-Status: No, score=-0.112 tagged_above=-999 required=5 tests=[AWL=0.325,
	BAYES_00=-2.599, 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 kaR00XkDw1HQ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 03:18:38 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 268F43A6A11
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 03:18:38 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUInt-0000BB-V6
	for radiusext-data@psg.com; Sat, 16 Aug 2008 10:14:37 +0000
Received: from [76.96.30.64] (helo=QMTA07.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUInq-0000AS-EL
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 10:14:36 +0000
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id 2yDH1a00117UAYkA7yEalY; Sat, 16 Aug 2008 10:14:34 +0000
Received: from gwzPC ([124.120.221.249])
	by OMTA13.emeryville.ca.mail.comcast.net with comcast
	id 2yE41a0065PTbrQ8ZyEMCG; Sat, 16 Aug 2008 10:14:32 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=No5EcEP4AAAA:8 a=fU9LJKApuY5FF5UbHC0A:9 a=pNaE7UpnEz2NZpL1yy0A:7
 a=WpsCCziqbXgzTtADQKv3HSoIacsA:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com>
In-Reply-To: <48A66F52.3060302@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 17:13:42 +0700
Message-ID: <002301c8ff88$cb8734d0$62959e70$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj/Z2dOQPRiYtQdTHiffyMYG1DQ9wAHyjLw
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok <mailto://aland@deployingradius.com> writes:

> Glen Zorn wrote:
> > I believe that he meant that all fragments of a given attribute must
> be
> > contiguous in the original packet...
> 
>   RFC 3579, Section 3.1:
> 
>       If multiple
>       EAP-Message attributes are contained within an Access-Request or
>       Access-Challenge packet, they MUST be in order and they MUST be
>       consecutive attributes in the Access-Request or Access-Challenge
>       packet.
> 
>   Requiring this for Extended-Attribute is a good idea.

Alright, how about this?

   M (More)

      The More Flag is one (1) bit in length and MUST be present.  When
      a value to be transmitted exceeds 246 octets in length it is
      fragmented over two or more Extended Attributes.  If the More Flag
      is set (1), this indicates that the Value field of the Extended
      Attribute contains a fragment of a larger value, which is
      continued in the next Extended Attribute of the same Ext-Type.
      When the More Flag is clear (0), the final (or only) fragment of
      the value is contained in the Extended Attribute.  Any Extended 
	Attributes containing multiple fragments of the same value MUST be 
	in order and MUST be consecutive attributes in the packet.

> 
>   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/>



--
to unsubscribe send a message to 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 Aug 16 03:30:28 2008
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 2C3AC3A688E
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 03:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Level: 
X-Spam-Status: No, score=0.802 tagged_above=-999 required=5 tests=[AWL=-0.620,
	BAYES_20=-0.74, 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 vEBNARA7FhsX
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 03:30:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 224CD3A6820
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 03:30:27 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUIyt-000192-JB
	for radiusext-data@psg.com; Sat, 16 Aug 2008 10:25:59 +0000
Received: from [76.96.30.40] (helo=QMTA04.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUIyn-000187-HD
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 10:25:56 +0000
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA04.emeryville.ca.mail.comcast.net with comcast
	id 2y5r1a0050QkzPwA4yRt16; Sat, 16 Aug 2008 10:25:53 +0000
Received: from gwzPC ([124.120.221.249])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id 2yRT1a00E5PTbrQ8NyRjsG; Sat, 16 Aug 2008 10:25:51 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=kGzLYcl_Fbmi9M8kV30A:9 a=srvYgiTBuwizAhSESfYA:7
 a=a2FuFvZUlRuAEwsemB6jqdec-3kA:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <006f01c8fef1$17fdc6a0$47f953e0$@net> <48A67144.5070709@deployingradius.com>
In-Reply-To: <48A67144.5070709@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 17:25:06 +0700
Message-ID: <002401c8ff8a$61b7bbe0$252733a0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj/aA2acCMyYpedS4GdGJl/49uH/wAIMVsQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok <mailto://aland@deployingradius.com> writes:

> 
> Glen Zorn wrote:
> > OK, are you saying that the existing text isn't clear?  It seems
> pretty
> > precise to me, should it be more vague (e.g., "long" & "short")?
> 
>   I just wanted to be sure I understood it.

OK.

> 
> >>       Two (2) octets.  Up-to-date values of the Ext-Type field are
> >>       specified in the most recent "Assigned Numbers" [IANA].
> Values
> >>       XXXX-YYYY are reserved.
> >>
> >>   I would suggest reserving the top 1K: 64512-65535
> >
> > Rationale?
> 
>   Numbers are better than XXXX-YYYY. :)  As for using the top 1K rather
> than 256, or 32, or 4.... it's small enough that we likely won't need
> the attribute numbers later, and large enough it gives a lot of room to
> work with.
> 
>   I'd say 32 may be too small, and anything over 1K is likely too
> large.

OK.  Any other opinions?

> 
> > Actually, I'd just as soon discard the examples: this draft has way
> too much
> > flavor of a tutorial for my taste...
> 
>   Sure.

Great!  Anybody married to section 6?  If not, it's gone...


> 
> >>   The examples could also given broken-out hex encoding of the
> >> attributes, which may be clearer than the ASCII art diagrams.  e.g.
> >>
> >>   1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f
> >
> > You're joking, right?
> 
>   Other RFC's have hex examples...

Sure, but I thought that we were writing not with any expectation of a
reasonable level of shared knowledge but for the LCD...

> 
> >>   I suggest leaving the first 0..255 attributes as unallocated, in
> >> order
> >> to avoid confusion with legacy RADIUS attributes.
> >
> > Presumably the people who would get confused are those who have to be
> told
> > to protect against buffer overflows (& send "hello" as five separate
> > attributes), right?
> 
>   Yes.
> 
>   I should put up a web page listing all of the "creative"
> interpretation of the RFC's.  Some people have put a lot of effort into
> doing the most inventive things.

"There is no end to the folly of men..."

> 
>   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 Aug 16 06:54:33 2008
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 64E953A6820
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 06:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.73
X-Spam-Level: *
X-Spam-Status: No, score=1.73 tagged_above=-999 required=5 tests=[AWL=-0.433,
	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 bZni6XGKLhHt
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 06:54:32 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 46B973A697C
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 06:54:32 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUMB2-000IPf-NF
	for radiusext-data@psg.com; Sat, 16 Aug 2008 13:50:44 +0000
Received: from [76.96.30.48] (helo=QMTA05.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KUMAz-000IPM-8M
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 13:50:42 +0000
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
	by QMTA05.emeryville.ca.mail.comcast.net with comcast
	id 30Cq1a00J0S2fkCA51qgJL; Sat, 16 Aug 2008 13:50:40 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA09.emeryville.ca.mail.comcast.net with comcast
	id 31qd1a00N24Kx1C8V1qe34; Sat, 16 Aug 2008 13:50:40 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=NutahLe0otnoMdzWAQwA:9 a=8JmZyy9rGIWL3XOIYYI3AvE6UYcA:4 a=tqucuuI3bnEA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <006f01c8fef1$17fdc6a0$47f953e0$@net> <48A67144.5070709@deployingradius.com> <002401c8ff8a$61b7bbe0$252733a0$@net>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 09:50:42 -0400
Message-ID: <000001c8ffa7$14466c40$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj/aA2acCMyYpedS4GdGJl/49uH/wAIMVsQAAdgn5A=
In-Reply-To: <002401c8ff8a$61b7bbe0$252733a0$@net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> > > Actually, I'd just as soon discard the examples: this draft has
> > > way too much flavor of a tutorial for my taste...
> >
> >   Sure.
> 
> Great!  Anybody married to section 6?  If not, it's gone...

I think examples sections (in this or any other document) are
extraordinarily helpful.  They help the reader to understand the details,
and the help the author by bringing to light incongruities in the normative
text.  I wouldn't be so quick to dispense with that section.  That fact that
it is raising issues tells me it has value.



--
to unsubscribe send a message to 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 Aug 16 07:02:49 2008
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 602703A68A8
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 07:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.745
X-Spam-Level: *
X-Spam-Status: No, score=1.745 tagged_above=-999 required=5 tests=[AWL=-0.232,
	BAYES_40=-0.185, 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 tU0LwK72At9R
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 07:02:48 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 76C863A6876
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 07:02:48 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUMJ6-000J8p-VW
	for radiusext-data@psg.com; Sat, 16 Aug 2008 13:59:04 +0000
Received: from [76.96.30.96] (helo=QMTA09.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KUMJ3-000J8N-Fy
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 13:59:03 +0000
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id 312G1a00F0QkzPwA91z1vk; Sat, 16 Aug 2008 13:59:01 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id 31yz1a00G24Kx1C8N1z0KT; Sat, 16 Aug 2008 13:59:01 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=Ez5NLzwIScexvbKFZNgA:9 a=349DxtYYX0ANllxsK7CqyklTVTMA:4 a=tqucuuI3bnEA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 09:59:03 -0400
Message-ID: <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj/Z2dOQPRiYtQdTHiffyMYG1DQ9wAHyjLwAAgjzUA=
In-Reply-To: <002301c8ff88$cb8734d0$62959e70$@net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

>    M (More)
> 
>       The More Flag is one (1) bit in length and MUST be present.  When
>       a value to be transmitted exceeds 246 octets in length it is
>       fragmented over two or more Extended Attributes.  If the More Flag
>       is set (1), this indicates that the Value field of the Extended
>       Attribute contains a fragment of a larger value, which is
>       continued in the next Extended Attribute of the same Ext-Type.
>       When the More Flag is clear (0), the final (or only) fragment of
>       the value is contained in the Extended Attribute.  Any Extended
> 	 Attributes containing multiple fragments of the same value MUST be
> 	 in order and MUST be consecutive attributes in the packet.

It's the last sentence that I claim adds new requirements to RADIUS.  This
is not required for EAP-Message Attributes, nor any others that I'm aware
of.  I'm stopping short of claiming that this new requirement isn't backward
compatible.  I can easily envision implementations where this would not be
any sort of burden to enforce.  I'm just wondering if there are any
implementations where it would be a burden?  I also see the advantage in
terms of ease of implementation of parsing and reconstruction.



--
to unsubscribe send a message to 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 Aug 16 07:17:05 2008
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 103CC3A6B80
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 07:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.514
X-Spam-Level: *
X-Spam-Status: No, score=1.514 tagged_above=-999 required=5 tests=[AWL=0.092,
	BAYES_20=-0.74, 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 KKHsONZVxwKB
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 07:17:04 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2795B3A6809
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 07:16:41 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUMX2-000KRx-W2
	for radiusext-data@psg.com; Sat, 16 Aug 2008 14:13:28 +0000
Received: from [76.96.30.40] (helo=QMTA04.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KUMWy-000KR3-IS
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 14:13:26 +0000
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA04.emeryville.ca.mail.comcast.net with comcast
	id 2zga1a00C0QkzPwA42DQeZ; Sat, 16 Aug 2008 14:13:24 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id 32DN1a00Q24Kx1C8N2DPzr; Sat, 16 Aug 2008 14:13:24 +0000
X-Authority-Analysis: v=1.0 c=1 a=_KgF-38uPHMA:10 a=P4Kb_900TAMA:10
 a=7Q47rwxljtCr7IOwWrgA:9 a=JMqhKbeZxQPUzR9OB_cA:7
 a=GDXxMY-SzrJjARgm8DM8aJl-xJMA:4 a=tqucuuI3bnEA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <002201c8feb4$81ee5df0$85cb19d0$@net> <5E154780AF9E4987A71861EDFD3750C9@xpsuperdvd2> <000101c8ff78$854b6b90$8fe242b0$@net>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Sat, 16 Aug 2008 10:13:26 -0400
Message-ID: <000201c8ffaa$414abf40$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcAAAWPE8AAp9nlQ
In-Reply-To: <000101c8ff78$854b6b90$8fe242b0$@net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Glen Zorn writes...

> What documents?

Those defining the cipher suites to be used.  Surely we're not going to
attempt to define them within a RADIUS document?

> Since an Experimental RFC holds no standing as a standard, how can it
> specify _anything_ as mandatory?

Sorry to be repetitive, buy why not?

> The last time I checked (please correct me if I'm wrong), the "hint" was
> from a NAS to a server regarding what the NAS wanted returned.  In many
> cases, these "hints" would not be anything of the sort; instead, they will
> be a simple statement of the algorithm used by the NAS.

How is that not a hint?  Sorry, but I simply don't see where you're going
with this.

> Examples are the User-Password Attribute & request
> authentication/integrity protection.

Eh?

> The only way that I can think of for the server to refuse the
> "hint" would be if we were to hi-jack the Access-Challenge message,
> which in itself constitutes a novel negotiation method for RADIUS.

Well, yes.  We discussed that briefly during an ill-fated attempt to add
generic capabilities negotiation to RADIUS.  So, yes there is no "NAK" and
counter-proposal capability, simply offer and accept or offer and reject.  I
fail to see why that would not allow a rudimentary form of crypto-agility.
The way a server refuses the hint by means of an Access-Reject message.

> > Therefore, it's reasonable to say that "Just use IPSec."
> > is out of scope for RADIUS crypto-agility.
> 
> The text to which I was referring is "Therefore, it is expected that
> proposals will utilize other techniques".

Well, if "Just use IPSec" is out of scope, doesn't it follow that "proposals
will use other methods" [besides IPSec)?  Again, I simply don't see where
you're going with this.

> > > I would _really_ like to see some rationale for this requirement
> > > (aside from "backward compatibility is sacred and must never be
> > > questioned" ;-).
> >
> > Given that the RADIUS protocol doesn't have a protocol version field,
> > maintaining backward compatibility seems pretty basic.
> 
> OK, so that sounds an awful lot like " backward compatibility is sacred
> and must never be questioned" to me.

If you say so...

> > > Given that this is new and presumably desirable functionality,
> > > why is a simple upgrade path not sufficient?
> >
> > A "fork-lift" upgrade?  :-)
> 
> Hardly. New messages and or capabilities can fairly easily be introduced
> in a piece-meal fashion, as long as it is done with care.

Well _that_ sounds a bit like "and a miracle occurs here".  That which is a
simple upgrade path to some is a deployment nightmare to others.  We need to
be a bit more specific, I think.



--
to unsubscribe send a message to 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 Aug 16 07:19:34 2008
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 E6D723A69BE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 07:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.776
X-Spam-Level: *
X-Spam-Status: No, score=1.776 tagged_above=-999 required=5 tests=[AWL=-0.201,
	BAYES_40=-0.185, 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 PlJTh+htbkmx
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 07:19:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1C1FB3A6809
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 07:19:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUMZF-000KnT-VP
	for radiusext-data@psg.com; Sat, 16 Aug 2008 14:15:45 +0000
Received: from [76.96.30.16] (helo=QMTA01.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KUMZC-000Kmu-OB
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 14:15:44 +0000
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id 31d21a0090EPchoA12FiSq; Sat, 16 Aug 2008 14:15:42 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id 32Fg1a00R24Kx1C8M2FhGn; Sat, 16 Aug 2008 14:15:42 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=gCkb8YzjIzgU_pSpqBcA:9 a=mIiUykJ3wxw-QgEZKVpoMAaN_gcA:4 a=955elKCOoL8A:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net> <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 10:15:45 -0400
Message-ID: <000301c8ffaa$93ad23e0$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj/Z2dOQPRiYtQdTHiffyMYG1DQ9wAHyjLwAAgjzUAAANQ0sA==
In-Reply-To: <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Clarifying...

> > 	 Attributes containing multiple fragments of the same value MUST be
> > 	 in order and MUST be consecutive attributes in the packet.
> 
> It's the last sentence that I claim adds new requirements to RADIUS

I'm talking about the second MUST in that sentence.


--
to unsubscribe send a message to 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 Aug 16 07:30:29 2008
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 378D83A6982
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 07:30:29 -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=[AWL=-0.000, 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 AksFKjo7jtbu
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 07:30:28 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 456F13A6809
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 07:30:28 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUMke-000M5E-Bn
	for radiusext-data@psg.com; Sat, 16 Aug 2008 14:27:32 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KUMkZ-000M4X-Vw
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 14:27:29 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id D7382123423B;
	Sat, 16 Aug 2008 16:27:26 +0200 (CEST)
Message-ID: <48A6E39C.5090604@deployingradius.com>
Date: Sat, 16 Aug 2008 16:26:36 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "David B. Nelson" <d.b.nelson@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net> <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603>
In-Reply-To: <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603>
X-Enigmail-Version: 0.95.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:
> Glen Zorn writes...
>> ...   Any Extended
>> 	 Attributes containing multiple fragments of the same value MUST be
>> 	 in order and MUST be consecutive attributes in the packet.
> 
> It's the last sentence that I claim adds new requirements to RADIUS.  This
> is not required for EAP-Message Attributes,

  Nope.  See RFC 3579 Section 3.1:

       If multiple
      EAP-Message attributes are contained within an Access-Request or
      Access-Challenge packet, they MUST be in order and they MUST be
      consecutive attributes in the Access-Request or Access-Challenge
      packet.

  MUST be consecutive attributes would seem pretty clear.

> nor any others that I'm aware
> of.  I'm stopping short of claiming that this new requirement isn't backward
> compatible.  I can easily envision implementations where this would not be
> any sort of burden to enforce.  I'm just wondering if there are any
> implementations where it would be a burden?  I also see the advantage in
> terms of ease of implementation of parsing and reconstruction.

  It's a PITA to root through the packet, looking for the next attribute
which *might* be the same... and which isn't consecutive.  I've done
this for the previous version of the Extended-Attributes.  It's awkward.
 It's much easier just to check: Next attribute is the same?  Nope?
Dump the packet as malformed.

  It makes for less code, and fewer chances for programming errors.

  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 Aug 16 10:14:22 2008
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 5F4ED3A6AA2
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 10:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.931
X-Spam-Level: 
X-Spam-Status: No, score=-0.931 tagged_above=-999 required=5
	tests=[AWL=-0.494, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=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 rzf5Y54KbCq1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 10:14:21 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id C16193A6A1F
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 10:14:20 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUPIb-00096T-GE
	for radiusext-data@psg.com; Sat, 16 Aug 2008 17:10:45 +0000
Received: from [63.208.196.179] (helo=mho-02-bos.mailhop.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD))
	(envelope-from <aboba@internaut.com>)
	id 1KUPIY-000963-1J
	for radiusext@ops.ietf.org; Sat, 16 Aug 2008 17:10:43 +0000
Received: from c-24-16-124-122.hsd1.wa.comcast.net ([24.16.124.122] helo=internaut.com)
	by mho-02-bos.mailhop.org with esmtpa (Exim 4.68)
	(envelope-from <aboba@internaut.com>)
	id 1KUPIV-000F16-Rc; Sat, 16 Aug 2008 17:10:40 +0000
Received: by internaut.com (Postfix, from userid 1001)
	id DE0D470CDD; Sat, 16 Aug 2008 10:10:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id D47D970BE9;
	Sat, 16 Aug 2008 10:10:37 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.124.122
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+3NBxGJHm2deVCiOa5j6aa
Date: Sat, 16 Aug 2008 10:10:37 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: Glen Zorn <glenzorn@comcast.net>
cc: 'Greg Weber' <gdweber@gmail.com>, 
    'Hannes Tschofenig' <Hannes.Tschofenig@gmx.net>, radiusext@ops.ietf.org
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
In-Reply-To: <005301c8fee7$e2d305c0$a8791140$@net>
Message-ID: <Pine.LNX.4.64.0808161003250.26442@internaut.com>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> 
 <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net>
 <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>
 <005301c8fee7$e2d305c0$a8791140$@net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

> 1) As you know, the issues list is not an official WG document, but a tool
> for the use of the Chairs & as such its state has no bearing on the status
> of a document.
> 2) All 3 of the issues assigned to the extended attributes document appear
> to actually refer to RFC 5080.

Issues 225, 250 and 251 all refer to the Extended Attributes document. 

> I suspect Hannes was referring to the open issues section in the draft's
> text, not the list maintained by the chairs.  Regarding the latter, the 
> issue that I filed (#250) was intended for your -00 draft, not RFC 5080.  
> 
> Be that as it may, the link points to an issue raised by Bernard re: the
> Fixes draft.

On Mozilla, the link does point to Issue 250.  What browser were you 
using? 

> I haven't read your current draft version yet to see if these comments were addressed;
> there was no response on the list -that I recall.  

--
to unsubscribe send a message to 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 Aug 16 21:47:08 2008
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 AA3D83A6903
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 16 Aug 2008 21:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.898
X-Spam-Level: *
X-Spam-Status: No, score=1.898 tagged_above=-999 required=5 tests=[AWL=-0.265,
	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 IqOpecfnlpVE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 16 Aug 2008 21:47:07 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 7E7DC3A695F
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 16 Aug 2008 21:47:07 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUa5s-0009bI-Td
	for radiusext-data@psg.com; Sun, 17 Aug 2008 04:42:20 +0000
Received: from [76.96.30.80] (helo=QMTA08.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <d.b.nelson@comcast.net>)
	id 1KUa5Z-0009a0-H6
	for radiusext@ops.ietf.org; Sun, 17 Aug 2008 04:42:03 +0000
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id 3FoT1a0050EPchoA8Gi19A; Sun, 17 Aug 2008 04:42:01 +0000
Received: from NEWTON603 ([24.61.11.96])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id 3Ghz1a00124Kx1C8MGhz15; Sun, 17 Aug 2008 04:42:01 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=Bvi-HSMcUnMUNU2lUaMA:9 a=RmSxo26jTxoDgZ88zAag6BXxbDcA:4 a=MxZ3bB5I4kYA:10
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net> <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603> <48A6E39C.5090604@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sun, 17 Aug 2008 00:42:04 -0400
Message-ID: <001c01c90023$9a223c00$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj/rDWssMK/BbPQTCeqzMwkBEb8TQAdznfA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <48A6E39C.5090604@deployingradius.com>
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

>   See RFC 3579 Section 3.1:
> 
>       If multiple
>       EAP-Message attributes are contained within an Access-Request or
>       Access-Challenge packet, they MUST be in order and they MUST be
>       consecutive attributes in the Access-Request or Access-Challenge
>       packet.

Damn.  When did that sneak in there?  :-)



--
to unsubscribe send a message to 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 Aug 17 00:32:16 2008
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 6C1E93A6B66
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 17 Aug 2008 00:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.644
X-Spam-Level: 
X-Spam-Status: No, score=0.644 tagged_above=-999 required=5 tests=[AWL=-0.408,
	BAYES_05=-1.11, 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 OtXMErKDGhJ1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 17 Aug 2008 00:32:15 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 5ED8D3A6B16
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 17 Aug 2008 00:32:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUcgs-000Kcs-Cw
	for radiusext-data@psg.com; Sun, 17 Aug 2008 07:28:42 +0000
Received: from [76.96.30.48] (helo=QMTA05.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUcgo-000KcL-VQ
	for radiusext@ops.ietf.org; Sun, 17 Aug 2008 07:28:40 +0000
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA05.emeryville.ca.mail.comcast.net with comcast
	id 3KTo1a00C0x6nqcA5KUeXG; Sun, 17 Aug 2008 07:28:38 +0000
Received: from gwzPC ([124.120.223.251])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id 3KTh1a0085S3YwU8YKUMkc; Sun, 17 Aug 2008 07:28:36 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=fNAG5FIyhIRLZW4MTw8A:9 a=Tt8Hz2L4uubvKLgCkXb9a6Z3OaAA:4 a=hodff89a88cA:10
 a=zoKOyUDlhksA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: "'Greg Weber'" <gdweber@gmail.com>,
	"'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com>  <48A46D3A.9000406@gmx.net> <002c01c8febf$2f4e04f0$8dea0ed0$@net> <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com> <005301c8fee7$e2d305c0$a8791140$@net> <Pine.LNX.4.64.0808161003250.26442@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0808161003250.26442@internaut.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sun, 17 Aug 2008 14:27:13 +0700
Message-ID: <004c01c9003a$b71268f0$25373ad0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj/wwLBeFHtTgSyRLa72dQjisishAAc5EcQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba [mailto:aboba@internaut.com] writes:

...

> > Be that as it may, the link points to an issue raised by Bernard re:
> the
> > Fixes draft.
> 
> On Mozilla, the link does point to Issue 250.  
> What browser were you
> using?

IE 7.0.6.  Investigating further w/Opera & Safari, it appears that IE is not
handling references to internal points in the HTML file correctly: it just
opens radissues2.html & quits, leaving the pointer at the beginning (issue
#200).  Opera & Safari position the pointer correctly (after a (long) while
;-). 

...



--
to unsubscribe send a message to 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 Aug 17 00:39:26 2008
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 297503A6B79
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 17 Aug 2008 00:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.083
X-Spam-Level: 
X-Spam-Status: No, score=-0.083 tagged_above=-999 required=5 tests=[AWL=0.354,
	BAYES_00=-2.599, 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 Q4JY6xVsSq85
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 17 Aug 2008 00:39:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 55EAA3A6B16
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 17 Aug 2008 00:39:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUcne-000LDM-M1
	for radiusext-data@psg.com; Sun, 17 Aug 2008 07:35:42 +0000
Received: from [76.96.30.56] (helo=QMTA06.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUcnZ-000LCh-C3
	for radiusext@ops.ietf.org; Sun, 17 Aug 2008 07:35:40 +0000
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA06.emeryville.ca.mail.comcast.net with comcast
	id 3Ka21a0060x6nqcA6KbdcA; Sun, 17 Aug 2008 07:35:37 +0000
Received: from gwzPC ([124.120.223.251])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id 3Kb71a0035S3YwU8YKbQFc; Sun, 17 Aug 2008 07:35:35 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=No5EcEP4AAAA:8 a=uOgh1dInKMU5b2U7p5kA:9 a=VnpElICRnafLwg5f9FsA:7
 a=ircG5rvkGaYx6mwexeNzTFpeD_QA:4 a=si9q_4b84H0A:10 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>,
	"'Alan DeKok'" <aland@deployingradius.com>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net> <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603> <48A6E39C.5090604@deployingradius.com> <001c01c90023$9a223c00$fefea8c0@NEWTON603>
In-Reply-To: <001c01c90023$9a223c00$fefea8c0@NEWTON603>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sun, 17 Aug 2008 14:34:40 +0700
Message-ID: <004d01c9003b$bddbaa10$3992fe30$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj/rDWssMK/BbPQTCeqzMwkBEb8TQAdznfAAAXpGWA=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson <mailto://d.b.nelson@comcast.net> writes:

> >   See RFC 3579 Section 3.1:
> >
> >       If multiple
> >       EAP-Message attributes are contained within an Access-Request
> or
> >       Access-Challenge packet, they MUST be in order and they MUST be
> >       consecutive attributes in the Access-Request or Access-
> Challenge
> >       packet.
> 
> Damn.  When did that sneak in there?  :-)

Well, let's see, it was in 2869, so about 10 years ago :-)

> 
> 
> 
> --
> to unsubscribe send a message to 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  Sun Aug 17 02:52:09 2008
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 3A1463A6997
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 17 Aug 2008 02:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.647
X-Spam-Level: 
X-Spam-Status: No, score=0.647 tagged_above=-999 required=5 tests=[AWL=-0.405,
	BAYES_05=-1.11, 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 x4d3gFannvCU
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 17 Aug 2008 02:52:08 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E73BF3A6952
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 17 Aug 2008 02:52:07 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUeqr-0004bt-BL
	for radiusext-data@psg.com; Sun, 17 Aug 2008 09:47:09 +0000
Received: from [76.96.30.56] (helo=QMTA06.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUeqn-0004bV-Sd
	for radiusext@ops.ietf.org; Sun, 17 Aug 2008 09:47:07 +0000
Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28])
	by QMTA06.emeryville.ca.mail.comcast.net with comcast
	id 3Mlu1a0060cQ2SLA6Mn5uE; Sun, 17 Aug 2008 09:47:05 +0000
Received: from gwzPC ([124.120.223.251])
	by OMTA10.emeryville.ca.mail.comcast.net with comcast
	id 3MVm1a0015S3YwU8WMlj3U; Sun, 17 Aug 2008 09:45:56 +0000
X-Authority-Analysis: v=1.0 c=1 a=_PEPdYUJN3EszErq27oA:9
 a=HBJ9c6q5mlzlEZciZtkA:7 a=n_ul-uTIPQQt2Z4A9r0fA98BpdcA:4 a=wHsKxTt6_eQA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: <gdweber@gmail.com>
Cc: <radiusext@ops.ietf.org>
Subject: Issue 250
Date: Sun, 17 Aug 2008 16:30:25 +0700
Message-ID: <005001c9004b$e82b2a60$b8817f20$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckAS9S6yurFrCN3Q5qq1JZcS1a6XA==
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

"In section 5, the Ext-Length field is defined as the length of the Extended
Attribute.  I think you mean it's the length of the TLV (multiple TLVs can
be
in the Extended Attribute).  I think that would make the value ">=3", not
">=4"."

That being the case, maybe it would be more descriptive to make the names of
the fields to "TLV-type" & "TLV-Length"?


"It's probably worth calling out any artifacts of overloading attribute 26
which wouldn't apply to standard attributes in the original number space
(or apply to overloading a new attribute instead of 26)."  

Of course, since it's only the format that needs to be inherited from VSAs,
the overall Type can be changed...


"For example, attribute 26 is already specifically excluded from some RADIUS
message
types, e.g. CoA-NAK,"

Just out of curiosity, does anyone know why that is so?  


"so new Extended Attributes couldn't be included in
those messages, but new standard attribute could be."  

Extended Attributes could be legalized for those messages in the exactly the
same way as for new "standard" attributes: through an updating RFC.


"Also, are malformed VSAs always treated just like malformed non-VSAs?"

Don't the rules defined in RFC 2865 apply to all attributes?


"I think it would be useful to explicitly mention if recursive grouping is
allowed and that Extended Attributes cannot be grouped with non-Extended
Attributes."

I have no idea how recursive grouping could be done with this scheme, but if
it could I don't know why you would want to outlaw it; one of the benefits
of the (apparently confusing) sanctioning of Ext-Types 0-256 is that it
makes it impossible to encapsulate legacy attributes in Extended Attributes
(although the legacy attribute space _could_ be duplicated in the first 257
slots, possibly a decent idea...


"It's probably useful to mention what happens when an Extended Attribute's
tag is non-zero and it contains multiple TLVs (this does not seem to be
excluded -as multiple TLVs are when the M-bit is on)."

I thought that that was obvious...what is unclear?






--
to unsubscribe send a message to 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 Aug 17 03:17:28 2008
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 0FBFF3A686B
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 17 Aug 2008 03:17:28 -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.945,
	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 9Ox4vGS5wG-8
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 17 Aug 2008 03:17:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id DDEFF3A6997
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 17 Aug 2008 03:17:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KUfG7-0006YO-K7
	for radiusext-data@psg.com; Sun, 17 Aug 2008 10:13:15 +0000
Received: from [76.96.30.96] (helo=QMTA09.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KUfG3-0006Y4-I7
	for radiusext@ops.ietf.org; Sun, 17 Aug 2008 10:13:13 +0000
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id 3NCE1a0030QkzPwA9NDBBi; Sun, 17 Aug 2008 10:13:11 +0000
Received: from gwzPC ([124.120.223.251])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id 3NC41a0095S3YwU8NNCyQc; Sun, 17 Aug 2008 10:13:07 +0000
X-Authority-Analysis: v=1.0 c=1 a=_KgF-38uPHMA:10 a=P4Kb_900TAMA:10
 a=rQVDROaagm3McDuhQd0A:9 a=VMe2xH0mEef-aVIOETcA:7
 a=C4jK9ZEfR5toWoIsDTTKNzKfp4cA:4 a=si9q_4b84H0A:10 a=oltf0pfCdT4A:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <002201c8feb4$81ee5df0$85cb19d0$@net> <5E154780AF9E4987A71861EDFD3750C9@xpsuperdvd2> <000101c8ff78$854b6b90$8fe242b0$@net> <000201c8ffaa$414abf40$fefea8c0@NEWTON603>
In-Reply-To: <000201c8ffaa$414abf40$fefea8c0@NEWTON603>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Sun, 17 Aug 2008 17:11:37 +0700
Message-ID: <005101c90051$a940b170$fbc21450$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcAAAWPE8AAp9nlQACan50A=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

David B. Nelson <mailto://d.b.nelson@comcast.net> writes: 

> 
> Glen Zorn writes...
> 
> > What documents?
> 
> Those defining the cipher suites to be used.  Surely we're not going to
> attempt to define them within a RADIUS document?

Define what?  Whether the algorithm is mandatory to implement for use in
RADIUS?  I sincerely hope so!

> 
> > Since an Experimental RFC holds no standing as a standard, how can it
> > specify _anything_ as mandatory?
> 
> Sorry to be repetitive, buy why not?
> 
> > The last time I checked (please correct me if I'm wrong), the "hint"
> was
> > from a NAS to a server regarding what the NAS wanted returned.  In
> many
> > cases, these "hints" would not be anything of the sort; instead, they
> will
> > be a simple statement of the algorithm used by the NAS.
> 
> How is that not a hint?  

Some definitions of "hint":

an indirect suggestion
a slight indication
a clue

What about any of those suggests a declarative statement?

...

> > The only way that I can think of for the server to refuse the
> > "hint" would be if we were to hi-jack the Access-Challenge message,
> > which in itself constitutes a novel negotiation method for RADIUS.
> 
> Well, yes.  We discussed that briefly during an ill-fated attempt to
> add
> generic capabilities negotiation to RADIUS.  So, yes there is no "NAK"
> and
> counter-proposal capability, simply offer and accept or offer and
> reject.  I
> fail to see why that would not allow a rudimentary form of crypto-
> agility.
> The way a server refuses the hint by means of an Access-Reject message.

And the client knows that this is a refusal of this particular hint (instead
of the multiple other conditions that might elicit an Access-Reject how,
exactly?  Parsing the Reply-Message Attribute that may or may not be
present?

...

> 
> > > > Given that this is new and presumably desirable functionality,
> > > > why is a simple upgrade path not sufficient?
> > >
> > > A "fork-lift" upgrade?  :-)
> >
> > Hardly. New messages and or capabilities can fairly easily be
> introduced
> > in a piece-meal fashion, as long as it is done with care.
> 
> Well _that_ sounds a bit like "and a miracle occurs here".  

I guess miracles really do happen every day then ;-): support for EAP,
dynamic authorization, 802.11...

...



--
to unsubscribe send a message to 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 Aug 18 14:10:59 2008
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 3CC7028C0CE
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 18 Aug 2008 14:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.43
X-Spam-Level: 
X-Spam-Status: No, score=-5.43 tagged_above=-999 required=5 tests=[AWL=-0.935,
	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 8NBqky366Mie
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Mon, 18 Aug 2008 14:10:58 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id F10743A6852
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 18 Aug 2008 14:10:57 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KVBv0-000BeZ-KS
	for radiusext-data@psg.com; Mon, 18 Aug 2008 21:05:38 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com)
	by psg.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <jsalowey@cisco.com>)
	id 1KVBuq-000Bdj-Om
	for radiusext@ops.ietf.org; Mon, 18 Aug 2008 21:05:36 +0000
X-IronPort-AV: E=Sophos;i="4.32,230,1217808000"; 
   d="scan'208";a="66938585"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
  by sj-iport-1.cisco.com with ESMTP; 18 Aug 2008 21:05:28 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m7IL5SQM007622;
	Mon, 18 Aug 2008 14:05:28 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m7IL5SF8004648;
	Mon, 18 Aug 2008 21:05:28 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 18 Aug 2008 14:05:27 -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: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Mon, 18 Aug 2008 14:05:48 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5065CB35C@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <D4371E585AF84CD5BDF3EC1F35DABB59@xpsuperdvd2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
thread-index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDAAEn0hlAAntbhEA==
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <AC1CFD94F59A264488DC2BEC3E890DE5065592E5@xmb-sjc-225.amer.cisco.com> <D4371E585AF84CD5BDF3EC1F35DABB59@xpsuperdvd2>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "David B. Nelson" <dnelson@elbrysnetworks.com>, <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 18 Aug 2008 21:05:27.0937 (UTC) FILETIME=[240CFF10:01C90176]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1918; t=1219093528; x=1219957528;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jsalowey@cisco.com;
	z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci
	sco.com>
	|Subject:=20RE=3A=20REMINDER=3A=20RADEXT=20WG=20Last=20Call
	=20on=20=22Crypto-Agility=20Requirements=20for=20RADIUS=22
	|Sender:=20;
	bh=7Nw0/IbThR7Gi8opomxnHmv/p845j+NJswyX6KpHO00=;
	b=hNVTKzTF996+UrRHG1HB2fsA5kXgzb1OrBcQy7+b2blGeph3uMhLU0r8G+
	CPAWhJeYPfnhQ1NdCD7cqXHjv4Fl4F5BOtKmGq/72FkbuzYwdNNYOoSloj83
	z/xoziHyBc;
Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

=20

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of David B. Nelson
> Sent: Friday, August 15, 2008 10:17 AM
> To: radiusext@ops.ietf.org
> Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility=20
> Requirements for RADIUS"
>=20
> Joseph Salowey writes...
>=20
> > 1. Section 4.2:
> >=20
> > In cases where the client needs to protect all or part of=20
> the radius=20
> > request the "hint and select" negotiation the client would provide=20
> > more than a hint when it chooses the algorithms for protection.
> > Perhaps hint and select is not quite the right term, may be specify=20
> > and select?
>=20
> While adding a more robust form of capabilities negotiation=20
> to RADIUS might be a useful thing, it's not a charted work=20
> item.  I think we are stuck with the current "hint and=20
> select" paradigm that is common usage in RADIUS today.
>=20
> Perhaps I've misunderstood your comment.  Could you give an example?
>=20
[Joe] There is some confusion.  I don't want to change the behavior, I
just think the term "hint and select" is a bit misleading since the
client will have to select some algorithm to protect its messages.  This
is a bit more than a "hint".  The client can "hint to the server what it
supports. =20

> > 2. Section 4.6:
> >=20
> > Section 4.6 makes reference to security considerations text=20
> about key=20
> > management.  Shouldn't this text be in this document?
>=20
> Yes, I think so.  Would anyone like to propose some text and=20
> a citation into RFC 4017?
>=20
[Joe] I'll try to provide some text by the end of the week. =20

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


From owner-radiusext@ops.ietf.org  Mon Aug 18 14:27:04 2008
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 35CF93A67E1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 18 Aug 2008 14:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.362
X-Spam-Level: *
X-Spam-Status: No, score=1.362 tagged_above=-999 required=5 tests=[AWL=-0.557,
	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 j6ekymlEtkuz
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Mon, 18 Aug 2008 14:27:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 167F63A6D27
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 18 Aug 2008 14:26:56 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KVCAM-000DDS-Hk
	for radiusext-data@psg.com; Mon, 18 Aug 2008 21:21:30 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <dnelson@elbrysnetworks.com>)
	id 1KVCAI-000DCz-V4
	for radiusext@ops.ietf.org; Mon, 18 Aug 2008 21:21:28 +0000
Received: (qmail 16086 invoked from network); 18 Aug 2008 17:21:23 -0400
Received: from unknown (HELO xpsuperdvd2) (172.22.18.93)
  by gumby.elbrysnetworks.com with SMTP; 18 Aug 2008 17:21:23 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131904270.24114@internaut.com> <AC1CFD94F59A264488DC2BEC3E890DE5065592E5@xmb-sjc-225.amer.cisco.com> <D4371E585AF84CD5BDF3EC1F35DABB59@xpsuperdvd2> <AC1CFD94F59A264488DC2BEC3E890DE5065CB35C@xmb-sjc-225.amer.cisco.com>
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Mon, 18 Aug 2008 17:21:21 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <7215774374A94535A323C71758E60AA7@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE5065CB35C@xmb-sjc-225.amer.cisco.com>
Thread-Index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDAAEn0hlAAntbhEAAAuMDQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Joseph Salowey writes...

> [Joe] There is some confusion.

I think an example packet exchange, showing how the client and server
"negotiate" the algorithm they will mutually use would be helpful.

> [Joe] I'll try to provide some text by the end of the week.

Thanks.



--
to unsubscribe send a message to 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 Aug 22 07:37:56 2008
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 4508A3A67E1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 22 Aug 2008 07:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.302
X-Spam-Level: 
X-Spam-Status: No, score=-102.302 tagged_above=-999 required=5
	tests=[AWL=0.298, 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 q46RZ+FdpvD0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 22 Aug 2008 07:37:55 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 97E513A6967
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 22 Aug 2008 07:37:41 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KWXeg-000KZI-Sg
	for radiusext-data@psg.com; Fri, 22 Aug 2008 14:30:22 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <root@core3.amsl.com>)
	id 1KWXeW-000KYP-T0
	for radiusext@ops.ietf.org; Fri, 22 Aug 2008 14:30:17 +0000
Received: by core3.amsl.com (Postfix, from userid 0)
	id BA4C63A697D; Fri, 22 Aug 2008 07:30:01 -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-radsec-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080822143001.BA4C63A697D@core3.amsl.com>
Date: Fri, 22 Aug 2008 07:30:01 -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           : TLS encryption for RADIUS over TCP (RadSec)
	Author(s)       : S. Winter, et al.
	Filename        : draft-ietf-radext-radsec-01.txt
	Pages           : 17
	Date            : 2008-08-22

This document specifies security on the transport layer (TLS) for the
RADIUS protocol [RFC2865] when transmitted over TCP
[I-D.dekok-radext-tcp-transport].  This enables dynamic trust
relationships between RADIUS servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-01.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-radsec-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2008-08-22071555.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  Fri Aug 22 08:51:22 2008
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 6350128C27F
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 22 Aug 2008 08:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.086
X-Spam-Level: 
X-Spam-Status: No, score=-1.086 tagged_above=-999 required=5
	tests=[AWL=-0.038, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	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 FG19pd-6W+3A
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 22 Aug 2008 08:48:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 462353A6960
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 22 Aug 2008 08:48:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KWYnv-0009c3-TY
	for radiusext-data@psg.com; Fri, 22 Aug 2008 15:43:59 +0000
Received: from [158.64.1.34] (helo=legolas.restena.lu)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <stefan.winter@restena.lu>)
	id 1KWYnb-0009Nz-Ia
	for radiusext@ops.ietf.org; Fri, 22 Aug 2008 15:43:41 +0000
Received: from legolas.restena.lu (localhost [127.0.0.1])
	by legolas.restena.lu (Postfix) with ESMTP id A4566AF03F
	for <radiusext@ops.ietf.org>; Fri, 22 Aug 2008 17:43:09 +0200 (CEST)
Received: from [158.64.15.136] (unknown [158.64.15.136])
	by legolas.restena.lu (Postfix) with ESMTPA id 3F2B9AF03A
	for <radiusext@ops.ietf.org>; Fri, 22 Aug 2008 17:43:09 +0200 (CEST)
Message-ID: <48AEDEC9.3060806@restena.lu>
Date: Fri, 22 Aug 2008 17:44:09 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: I-D Action:draft-ietf-radext-radsec-01.txt
References: <20080822143001.BA4C63A697D@core3.amsl.com>
In-Reply-To: <20080822143001.BA4C63A697D@core3.amsl.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi,

this version reflects the discussions from IETF-72.

* normative section in the beginning, informative afterwards with 
explanations
* forbid integrity-only ciphers
* fixed shared "secret" ["radsec" for now, as I don't quite remember 
what we settled for, if anything]

Most of it is text re-shuffling, two notable changes:

* previous versions left CoA and Disconnect unspecified. The current 
draft includes it, the basic rationale being that to implement RadSec, 
new code is necessary anyways and the burden of at least answering to a 
Req with a NAK can be demanded IMO.
* one of the SHOULD ciphers which is based on MD5 is gone. It felt a bit 
awkward to complain about RADIUS' MD5 usage and then recommend a MD5 
based cipher.

If you have comments, I'll be happy to ignore them for the next two 
weeks, since I'll be at a completely-offline vacation. I'll get back to 
IETF business after that.

Greetings,

Stefan Winter

Internet-Drafts@ietf.org schrieb:
> 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           : TLS encryption for RADIUS over TCP (RadSec)
> 	Author(s)       : S. Winter, et al.
> 	Filename        : draft-ietf-radext-radsec-01.txt
> 	Pages           : 17
> 	Date            : 2008-08-22
>
> This document specifies security on the transport layer (TLS) for the
> RADIUS protocol [RFC2865] when transmitted over TCP
> [I-D.dekok-radext-tcp-transport].  This enables dynamic trust
> relationships between RADIUS servers.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-01.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.
>   


--
to unsubscribe send a message to 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 Aug 25 14:21:08 2008
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 CB82C3A6862
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 25 Aug 2008 14:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5
	tests=[AWL=0.251, 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 g6bIlUECnQjS
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Mon, 25 Aug 2008 14:21:08 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D88FF28C44B
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 25 Aug 2008 14:20:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KXjP3-000Gkr-7g
	for radiusext-data@psg.com; Mon, 25 Aug 2008 21:15:09 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <root@core3.amsl.com>)
	id 1KXjOy-000Gjx-Bj
	for radiusext@ops.ietf.org; Mon, 25 Aug 2008 21:15:07 +0000
Received: by core3.amsl.com (Postfix, from userid 0)
	id CDF2428C111; Mon, 25 Aug 2008 14:15:01 -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-status-server-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080825211501.CDF2428C111@core3.amsl.com>
Date: Mon, 25 Aug 2008 14:15:01 -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		: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
	Author(s)	: A. DeKok
	Filename	: draft-ietf-radext-status-server-01.txt
	Pages		: 28
	Date		: 2008-8-25
	
RFC 2865 defines a Status-Server code for use in RADIUS, but labels
   it as "Experimental" without further discussion.  This document
   describes a practical use for the Status-Server packet code, which is
   to let clients query the status of a RADIUS server.  These queries,
   and responses (if any) enable the client to make more informed
   decisions.  The result is a more stable, and more robust RADIUS
   architecture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-status-server-01.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-status-server-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2008-8-25140857.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 Aug 25 15:03:01 2008
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 000DC3A69E3
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 25 Aug 2008 15:03:00 -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 Xsiqx3gJ+Br0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Mon, 25 Aug 2008 15:03:00 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2747A3A69B1
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 25 Aug 2008 15:03:00 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KXk4f-000O08-Qg
	for radiusext-data@psg.com; Mon, 25 Aug 2008 21:58:09 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KXk4Y-000Nz6-N5
	for radiusext@ops.ietf.org; Mon, 25 Aug 2008 21:58:08 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id A60241234225
	for <radiusext@ops.ietf.org>; Mon, 25 Aug 2008 23:58:01 +0200 (CEST)
Message-ID: <48B32AB4.9050409@deployingradius.com>
Date: Mon, 25 Aug 2008 23:57:08 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-radext-status-server-01.txt
References: <20080825211501.CDF2428C111@core3.amsl.com>
In-Reply-To: <20080825211501.CDF2428C111@core3.amsl.com>
X-Enigmail-Version: 0.95.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>

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the RADIUS EXTensions Working Group of the IETF.
> 
> 	Title		: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol

  The changes from -00 reflect the discussion at the WG meeting in
Dublin.  Text on using the CoA port has been added.

  I don't think there's much else to do with the document at this point.

  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 Aug 26 08:25:36 2008
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 080AB3A698F
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 08:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.617
X-Spam-Level: 
X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5
	tests=[AWL=-0.122, 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 3GoYJ+1Y2I0r
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 08:25:35 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 3548A3A6A15
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 08:25:35 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KY0MA-0008v8-0J
	for radiusext-data@psg.com; Tue, 26 Aug 2008 15:21:18 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KY0M5-0008uP-TM
	for radiusext@ops.ietf.org; Tue, 26 Aug 2008 15:21:15 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 3B4CC1234225;
	Tue, 26 Aug 2008 17:21:10 +0200 (CEST)
Message-ID: <48B41F2D.40909@deployingradius.com>
Date: Tue, 26 Aug 2008 17:20:13 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: Comment on draft-ietf-radext-design-04.txt, Appendix A
References: <Pine.LNX.4.64.0807131128470.27225@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0807131128470.27225@internaut.com>
X-Enigmail-Version: 0.95.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:
> There are a few cases where the text in Appendix A is not backed by 
> discussion in the rest of the document, and vice versa.  
...

  I've updated the document as suggested, with some minor word smithing.
 It should show up soon as an announcement.

  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 Aug 26 08:33:33 2008
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 B33A628C1A4
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 08:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level: 
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5
	tests=[AWL=0.483, 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 ISTu8PA2VbsJ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 08:33:33 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 02CC528C1C7
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 08:33:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KY0Ur-000A6P-Cj
	for radiusext-data@psg.com; Tue, 26 Aug 2008 15:30:17 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <root@core3.amsl.com>)
	id 1KY0Ue-000A4l-Cb
	for radiusext@ops.ietf.org; Tue, 26 Aug 2008 15:30:15 +0000
Received: by core3.amsl.com (Postfix, from userid 0)
	id 7F8A83A6B7F; Tue, 26 Aug 2008 08:30:01 -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-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080826153001.7F8A83A6B7F@core3.amsl.com>
Date: Tue, 26 Aug 2008 08:30:01 -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, et al.
	Filename        : draft-ietf-radext-design-05.txt
	Pages           : 36
	Date            : 2008-08-26

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-05.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-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2008-08-26082119.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  Tue Aug 26 20:11:47 2008
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 4AA6A3A6883
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 20:11:47 -0700 (PDT)
X-Quarantine-ID: <WejOWHTAKpRG>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 1.919
X-Spam-Level: *
X-Spam-Status: No, score=1.919 tagged_above=-999 required=5
	tests=[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 WejOWHTAKpRG
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 20:11:46 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E6B943A67A3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 20:11:45 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYBMu-00046Z-0D
	for radiusext-data@psg.com; Wed, 27 Aug 2008 03:06:48 +0000
Received: from [65.54.246.90] (helo=bay0-omc1-s18.bay0.hotmail.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <bernard_aboba@hotmail.com>)
	id 1KYBMg-00042m-9V
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 03:06:36 +0000
Received: from hotmail.com ([10.4.31.11]) by bay0-omc1-s18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 26 Aug 2008 20:06:30 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 26 Aug 2008 20:06:30 -0700
Message-ID: <BLU137-DAV16129148B46F358F280B793610@phx.gbl>
Received: from 131.107.0.102 by BLU137-DAV1.phx.gbl with DAV;
	Wed, 27 Aug 2008 03:06:29 +0000
X-Originating-IP: [131.107.0.102]
X-Originating-Email: [bernard_aboba@hotmail.com]
X-Sender: bernard_aboba@hotmail.com
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: PROTO: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:06:26 -0700
Message-ID: <002101c907f1$e4ba09c0$ae2e1d40$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQ
Content-Language: en-us
X-OriginalArrivalTime: 27 Aug 2008 03:06:30.0302 (UTC) FILETIME=[E72193E0:01C907F1]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Title:  RADIUS Design Guidelines
I-D:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-06.txt
 
Status: Best Current Practice
 
Response to template:
 
1) Have the chairs personally reviewed this version of the ID and do
   they believe this ID is sufficiently baked to forward to the IESG
   for publication?
 
Yes.
 
2) Has the document had adequate review from both key WG members and
   key non-WG members? Do you have any concerns about the depth or
   breadth of the reviews that have been performed?
 
Yes. The ID has had 2 working group last calls.
 
3) Do you have concerns that the document needs more review from a
   particular (broader) perspective (e.g., security, operational
   complexity, someone familiar with AAA, etc.)?
 
No concerns.  
 
4) Do you have any specific concerns/issues with this document that
   you believe the ADs and/or IESG should be aware of? For example,
   perhaps you are uncomfortable with certain parts of the document,
   or whether there really is a need for it, etc., but at the same
   time these issues have been discussed in the WG and the WG has
   indicated it wishes to advance the document anyway.
 
No.
 
5) How solid is the WG consensus behind this document?  Does it
   represent the strong concurrence of a few individuals, with others
   being silent, or does the WG as a whole understand and agree with
   it?
 
There is solid consensus behind this document.  The overall approach
to the document has been extensively discussed, both in IETF meetings
and on the mailing list.  Over a dozen people have commented on various
aspects of the document during its development.  The issues raised in
WG last call, available for inspection at 
http://www.drizzle.com/~aboba/RADEXT/, were resolved in the -06
version of the document.
 
6) Has anyone threatened an appeal or otherwise indicated extreme
   discontent?  If so, please summarize what are they upset about.
 
No.
 
7) Have the chairs verified that the document adheres to _all_ of the
   ID nits?  (see http://www.ietf.org/ID-nits.html).
 
Yes. An output of the run on this revision of the ID by the online nits
checker:
 
idnits 2.08.10 

tmp/draft-ietf-radext-design-05.txt:

  Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ID-Checklist.html:
 
----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking references for intended status: Best Current Practice
 
----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  -- Looks like a reference, but probably isn't: '8' on line 1431
     'The Text field consists of UTF-8 encoded 10646 [8] characters....'


     Summary: 0 errors (**), 0 warnings (==), 1 comment (--).


8) Does the document a) split references into normative/informative,
   and b) are there normative references to IDs, where the IDs are not
   also ready for advancement or are otherwise in an unclear state?
   (Note: the RFC editor will not publish an RFC with normative
   references to IDs, it will delay publication until all such IDs are
   also ready for publication as RFCs.)
 
The document does split references into normative and informative ones.
There are no normative references to IDs.
 
9) For Standards Track and BCP documents, the IESG approval
   announcement includes a writeup section with the following
   sections:
 
   - Technical Summary
 
   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). 
 
   - Working Group Summary
 
    There have been 2 WGLCs on the document.  Much of the discussion on
    the document has centered around the design guidelines 
    surrounding complex attributes, as well as the relationship of the
    RADIUS Vendor-Specific Attribute (VSA) and the Standard attribute
    space.  There was also considerable discussion relating to the
    process for review of RADIUS attributes specified by SDOs.  
    Ultimately, a consensus developed behind a model similar to that
    described in [RFC4663]. 


--
to unsubscribe send a message to 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 Aug 26 20:30:38 2008
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 6C2043A6800
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 20:30:38 -0700 (PDT)
X-Quarantine-ID: <f3QYUascxOY1>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
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_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 f3QYUascxOY1
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 20:30:37 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 57F373A67A3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 20:30:37 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYBgN-0006A0-MK
	for radiusext-data@psg.com; Wed, 27 Aug 2008 03:26:55 +0000
Received: from [65.54.246.113] (helo=bay0-omc1-s41.bay0.hotmail.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <bernard_aboba@hotmail.com>)
	id 1KYBgJ-00069b-MN
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 03:26:53 +0000
Received: from hotmail.com ([10.4.31.17]) by bay0-omc1-s41.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 26 Aug 2008 20:26:51 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 26 Aug 2008 20:26:51 -0700
Message-ID: <BLU137-DAV746AB4419DBEEE3422F6193610@phx.gbl>
Received: from 131.107.0.102 by BLU137-DAV7.phx.gbl with DAV;
	Wed, 27 Aug 2008 03:26:46 +0000
X-Originating-IP: [131.107.0.102]
X-Originating-Email: [bernard_aboba@hotmail.com]
X-Sender: bernard_aboba@hotmail.com
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Last look: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:26:44 -0700
Message-ID: <002201c907f4$bad33bb0$3079b310$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQAACM4PA=
Content-Language: en-us
X-OriginalArrivalTime: 27 Aug 2008 03:26:51.0180 (UTC) FILETIME=[BED4C6C0:01C907F4]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

The RADIUS Design Guidelines has recently been revised to reflect
the issues filed in RADEXT WG last call, and a draft PROTO writeup
has been submitted for WG inspection.  

The new document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-06.txt

The PROTO writeup is available here:
http://ops.ietf.org/lists/radiusext/2008/msg00520.html

If you filed an issue in RADEXT WG last call, please examine the
latest revision in order to determine whether the issue was resolved
to your satisfaction. 

Also, if you have not yet read the document, please do so. 

If you have comments on either the document or the PROTO writeup (see
previous message), please post them to the RADEXT WG mailing list
(radiusext@ops.ietf.org).  Document issues should be encapsulated 
in the format described in the RADEXT Issues List 
(http://www.drizzle.com/~aboba/RADEXT)

This "last look" will complete on September 7, 2008. 


--
to unsubscribe send a message to 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 Aug 26 20:33:11 2008
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 AC0BE3A67D6
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 20:33:11 -0700 (PDT)
X-Quarantine-ID: <LNA5rlnJp37j>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 2.058
X-Spam-Level: **
X-Spam-Status: No, score=2.058 tagged_above=-999 required=5 tests=[AWL=-0.046,
	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 LNA5rlnJp37j
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 20:33:10 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id BFDFD3A67A3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 20:33:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYBkV-0006k7-Rd
	for radiusext-data@psg.com; Wed, 27 Aug 2008 03:31:11 +0000
Received: from [65.54.246.106] (helo=bay0-omc1-s34.bay0.hotmail.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <bernard_aboba@hotmail.com>)
	id 1KYBkQ-0006jQ-Rk
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 03:31:09 +0000
Received: from hotmail.com ([10.4.31.11]) by bay0-omc1-s34.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 26 Aug 2008 20:31:06 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 26 Aug 2008 20:31:06 -0700
Message-ID: <BLU137-DAV102684279E36078ECA28393610@phx.gbl>
Received: from 131.107.0.102 by BLU137-DAV1.phx.gbl with DAV;
	Wed, 27 Aug 2008 03:31:03 +0000
X-Originating-IP: [131.107.0.102]
X-Originating-Email: [bernard_aboba@hotmail.com]
X-Sender: bernard_aboba@hotmail.com
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Revised Last look: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:31:02 -0700
Message-ID: <002401c907f5$546cacc0$fd460640$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQAACM4PAAAF3v0A==
Content-Language: en-us
X-OriginalArrivalTime: 27 Aug 2008 03:31:06.0334 (UTC) FILETIME=[56EA2FE0:01C907F5]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

The RADIUS Design Guidelines has recently been revised to reflect
the issues filed in RADEXT WG last call, and a draft PROTO writeup
has been submitted for WG inspection.  

The new document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-05.txt

The PROTO writeup is available here:
http://ops.ietf.org/lists/radiusext/2008/msg00522.html

If you filed an issue in RADEXT WG last call, please examine the
latest revision in order to determine whether the issue was resolved
to your satisfaction. 

Also, if you have not yet read the document, please do so. 

If you have comments on either the document or the PROTO writeup (see
previous message), please post them to the RADEXT WG mailing list
(radiusext@ops.ietf.org).  Document issues should be encapsulated 
in the format described in the RADEXT Issues List 
(http://www.drizzle.com/~aboba/RADEXT)

This "last look" will complete on September 7, 2008. 


--
to unsubscribe send a message to 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 Aug 26 20:33:27 2008
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 15C0B3A67D6
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 20:33:27 -0700 (PDT)
X-Quarantine-ID: <1Wjk7XG+5+bf>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 1.981
X-Spam-Level: *
X-Spam-Status: No, score=1.981 tagged_above=-999 required=5 tests=[AWL=0.062,
	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 1Wjk7XG+5+bf
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 20:33:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id E9C153A67A3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 20:33:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYBji-0006c6-7k
	for radiusext-data@psg.com; Wed, 27 Aug 2008 03:30:22 +0000
Received: from [65.54.246.98] (helo=bay0-omc1-s26.bay0.hotmail.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <bernard_aboba@hotmail.com>)
	id 1KYBje-0006bj-EF
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 03:30:20 +0000
Received: from hotmail.com ([10.4.31.20]) by bay0-omc1-s26.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 26 Aug 2008 20:30:18 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 26 Aug 2008 20:30:17 -0700
Message-ID: <BLU137-DAV10E073B7D97BF62514814593610@phx.gbl>
Received: from 131.107.0.102 by BLU137-DAV10.phx.gbl with DAV;
	Wed, 27 Aug 2008 03:30:13 +0000
X-Originating-IP: [131.107.0.102]
X-Originating-Email: [bernard_aboba@hotmail.com]
X-Sender: bernard_aboba@hotmail.com
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Revised PROTO: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:30:12 -0700
Message-ID: <002301c907f5$36f46ca0$a4dd45e0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQAADknLA=
Content-Language: en-us
X-OriginalArrivalTime: 27 Aug 2008 03:30:17.0459 (UTC) FILETIME=[39C87430:01C907F5]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Title:  RADIUS Design Guidelines
I-D:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-05.txt
 
Status: Best Current Practice
 
Response to template:
 
1) Have the chairs personally reviewed this version of the ID and do
   they believe this ID is sufficiently baked to forward to the IESG
   for publication?
 
Yes.
 
2) Has the document had adequate review from both key WG members and
   key non-WG members? Do you have any concerns about the depth or
   breadth of the reviews that have been performed?
 
Yes. The ID has had 2 working group last calls.
 
3) Do you have concerns that the document needs more review from a
   particular (broader) perspective (e.g., security, operational
   complexity, someone familiar with AAA, etc.)?
 
No concerns.  
 
4) Do you have any specific concerns/issues with this document that
   you believe the ADs and/or IESG should be aware of? For example,
   perhaps you are uncomfortable with certain parts of the document,
   or whether there really is a need for it, etc., but at the same
   time these issues have been discussed in the WG and the WG has
   indicated it wishes to advance the document anyway.
 
No.
 
5) How solid is the WG consensus behind this document?  Does it
   represent the strong concurrence of a few individuals, with others
   being silent, or does the WG as a whole understand and agree with
   it?
 
There is solid consensus behind this document.  The overall approach
to the document has been extensively discussed, both in IETF meetings
and on the mailing list.  Over a dozen people have commented on various
aspects of the document during its development.  The issues raised in
WG last call, available for inspection at 
http://www.drizzle.com/~aboba/RADEXT/, were resolved in the -05
version of the document.
 
6) Has anyone threatened an appeal or otherwise indicated extreme
   discontent?  If so, please summarize what are they upset about.
 
No.
 
7) Have the chairs verified that the document adheres to _all_ of the
   ID nits?  (see http://www.ietf.org/ID-nits.html).
 
Yes. An output of the run on this revision of the ID by the online nits
checker:
 
idnits 2.08.10 

tmp/draft-ietf-radext-design-05.txt:

  Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ID-Checklist.html:
 
----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking references for intended status: Best Current Practice
 
----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  -- Looks like a reference, but probably isn't: '8' on line 1431
     'The Text field consists of UTF-8 encoded 10646 [8] characters....'


     Summary: 0 errors (**), 0 warnings (==), 1 comment (--).


8) Does the document a) split references into normative/informative,
   and b) are there normative references to IDs, where the IDs are not
   also ready for advancement or are otherwise in an unclear state?
   (Note: the RFC editor will not publish an RFC with normative
   references to IDs, it will delay publication until all such IDs are
   also ready for publication as RFCs.)
 
The document does split references into normative and informative ones.
There are no normative references to IDs.
 
9) For Standards Track and BCP documents, the IESG approval
   announcement includes a writeup section with the following
   sections:
 
   - Technical Summary
 
   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). 
 
   - Working Group Summary
 
    There have been 2 WGLCs on the document.  Much of the discussion on
    the document has centered around the design guidelines 
    surrounding complex attributes, as well as the relationship of the
    RADIUS Vendor-Specific Attribute (VSA) and the Standard attribute
    space.  There was also considerable discussion relating to the
    process for review of RADIUS attributes specified by SDOs.  
    Ultimately, a consensus developed behind a model similar to that
    described in [RFC4663]. 


--
to unsubscribe send a message to 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 Aug 26 21:27:18 2008
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 57B383A6918
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 21:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.052
X-Spam-Level: *
X-Spam-Status: No, score=1.052 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, 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 lyt-URFGvReJ
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 21:27:17 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 6E8633A68D1
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 21:27:17 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYCZA-000Ckh-FX
	for radiusext-data@psg.com; Wed, 27 Aug 2008 04:23:32 +0000
Received: from [76.96.62.40] (helo=QMTA04.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYCZ6-000Ck6-C5
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 04:23:30 +0000
Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52])
	by QMTA04.westchester.pa.mail.comcast.net with comcast
	id 7CVQ1a00F17dt5G54GPTAy; Wed, 27 Aug 2008 04:23:27 +0000
Received: from gwzPC ([124.120.225.106])
	by OMTA13.westchester.pa.mail.comcast.net with comcast
	id 7GNe1a0072JMgNL3ZGP5L3; Wed, 27 Aug 2008 04:23:22 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=o25k7g4T7n0cxXW8OHsA:9
 a=NxTUXgh7YFMG0KHSRsTWlWftZRcA:4 a=hodff89a88cA:10 a=zoKOyUDlhksA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net>
In-Reply-To: <000801c8fe00$b50248a0$1f06d9e0$@net>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 11:21:51 +0700
Message-ID: <003a01c907fc$7c437b00$74ca7100$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9tI9KOI7i58ewR6q8qn9+WmSnywASr9SQAiWv2KA=
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba <mailto://aboba@internaut.com> writes:

...

> Looking at RFC 3588, it does seem
> that the agbility to name and define a Grouped AVP has some
> advantages.

OK, so I've run into a situation when working on a set of attributes for
WiMAX that just begs for a named, multi-TLV attribute.  I guess it does seem
that the extended attributes should be able to handle this situation, fixing
one of the inadequacies (IMHO) of legacy RADIUS attributes, but right now
they can't.  Any suggestions for fixing this problem (as painlessly as
possible :-)? 

...



--
to unsubscribe send a message to 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 Aug 26 23:32:28 2008
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 661993A68BD
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 26 Aug 2008 23:32:28 -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 HraK60S9SEnv
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Tue, 26 Aug 2008 23:32:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2226F3A683E
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 26 Aug 2008 23:32:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYEVz-0002Dg-42
	for radiusext-data@psg.com; Wed, 27 Aug 2008 06:28:23 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYEVu-0002D8-VJ
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 06:28:21 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 39ECE1234225;
	Wed, 27 Aug 2008 08:28:17 +0200 (CEST)
Message-ID: <48B4F3CA.7020901@deployingradius.com>
Date: Wed, 27 Aug 2008 08:27:22 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'Bernard Aboba' <aboba@internaut.com>, radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net>
In-Reply-To: <003a01c907fc$7c437b00$74ca7100$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> OK, so I've run into a situation when working on a set of attributes for
> WiMAX that just begs for a named, multi-TLV attribute.

  Could you be more specific?

>  I guess it does seem
> that the extended attributes should be able to handle this situation, fixing
> one of the inadequacies (IMHO) of legacy RADIUS attributes, but right now
> they can't.  Any suggestions for fixing this problem (as painlessly as
> possible :-)? 

  Painlessly killing RADIUS has been off of the table for a while.
We're stuck with painful solutions.

  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 Aug 27 01:44:27 2008
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 3FC5128C195
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 01:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.608
X-Spam-Level: *
X-Spam-Status: No, score=1.608 tagged_above=-999 required=5 tests=[AWL=-0.555,
	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 qZHZPw042U2Z
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 01:44:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0306F28C1A1
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 01:44:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYGZr-000JYV-Ti
	for radiusext-data@psg.com; Wed, 27 Aug 2008 08:40:31 +0000
Received: from [76.96.62.48] (helo=QMTA05.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYGZk-000JXa-Uk
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 08:40:26 +0000
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51])
	by QMTA05.westchester.pa.mail.comcast.net with comcast
	id 7Lfx1a00216LCl055LgPSZ; Wed, 27 Aug 2008 08:40:23 +0000
Received: from gwzPC ([124.120.225.106])
	by OMTA06.westchester.pa.mail.comcast.net with comcast
	id 7LfP1a0022JMgNL3SLfwxK; Wed, 27 Aug 2008 08:40:18 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=wmtHAxluQ6mEyUQs_MoA:9
 a=wWHmO-fgAgcx1uZDrX646EwxK4wA:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'Bernard Aboba'" <aboba@internaut.com>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com>
In-Reply-To: <48B4F3CA.7020901@deployingradius.com>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 15:38:35 +0700
Message-ID: <004701c90820$5ce75550$16b5fff0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckIDhh6WfRmsmu0RoeEv0Qgug3zOAAEeP8A
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > OK, so I've run into a situation when working on a set of attributes
> for
> > WiMAX that just begs for a named, multi-TLV attribute.
> 
>   Could you be more specific?

About what?

> 
> >  I guess it does seem
> > that the extended attributes should be able to handle this situation,
> fixing
> > one of the inadequacies (IMHO) of legacy RADIUS attributes, but right
> now
> > they can't.  Any suggestions for fixing this problem (as painlessly
> as
> > possible :-)?
> 
>   Painlessly killing RADIUS has been off of the table for a while.

Who's talking about "killing RADIUS"?  Do we have differing definitions of a
"dead" protocol?

> We're stuck with painful solutions.
> 
>   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 Aug 27 01:49:19 2008
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 2B0AE3A693D
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 01:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.556
X-Spam-Level: 
X-Spam-Status: No, score=-0.556 tagged_above=-999 required=5
	tests=[AWL=-0.061, 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 RTRNUr64Ryv3
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 01:49:18 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 0D6DB3A68BD
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 01:49:18 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYGcv-000Jxb-1D
	for radiusext-data@psg.com; Wed, 27 Aug 2008 08:43:41 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYGcm-000Jwd-Fx
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 08:43:34 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 954DD1234225;
	Wed, 27 Aug 2008 10:43:27 +0200 (CEST)
Message-ID: <48B51378.2040100@deployingradius.com>
Date: Wed, 27 Aug 2008 10:42:32 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net>
In-Reply-To: <004701c90820$5ce75550$16b5fff0$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> Alan DeKok [mailto:aland@deployingradius.com] writes:
> 
>> Glen Zorn wrote:
>>> OK, so I've run into a situation when working on a set of attributes
>> for
>>> WiMAX that just begs for a named, multi-TLV attribute.
>>   Could you be more specific?
> 
> About what?

  A named, multi-TLV attribute.

  Most attributes have names.  Most attributes are TLV's.  The
Extended-Attribute encapsulates multiple TLV's.

  So... what's a "named, multi-TLV attribute"?  An attribute inside of
the Extended-Attribute that can carry other TLV's?  Like what's done in
WiMAX?

  It's a good idea.  And if most vendors have to add WiMAX support
anyways, much of the code will already exist.

  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 Aug 27 01:58:58 2008
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 7A0DD28C1AF
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 01:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.33
X-Spam-Level: *
X-Spam-Status: No, score=1.33 tagged_above=-999 required=5 tests=[AWL=0.278,
	BAYES_05=-1.11, 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 rH7a8UUZiksO
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 01:58:57 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 853B33A6BD6
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 01:58:57 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYGox-000Ltu-KM
	for radiusext-data@psg.com; Wed, 27 Aug 2008 08:56:07 +0000
Received: from [76.96.62.32] (helo=QMTA03.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYGor-000Lsy-N5
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 08:56:03 +0000
Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20])
	by QMTA03.westchester.pa.mail.comcast.net with comcast
	id 7Ljk1a0060SCNGk53Lw1Zm; Wed, 27 Aug 2008 08:56:01 +0000
Received: from gwzPC ([124.120.225.106])
	by OMTA09.westchester.pa.mail.comcast.net with comcast
	id 7LvC1a00B2JMgNL3VLvfMs; Wed, 27 Aug 2008 08:55:56 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=Y7yyQfWQ_2jG_busszUA:9
 a=5i-JdcI5Wf54a4NPxP-gO5Dw_g4A:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com>
In-Reply-To: <48B51378.2040100@deployingradius.com>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 15:54:24 +0700
Message-ID: <004c01c90822$8f7612c0$ae623840$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckIIPpq+TrwNZ4XQVK5o8XZY05cpAAAQT1w
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Alan DeKok [mailto:aland@deployingradius.com] writes:
> >
> >> Glen Zorn wrote:
> >>> OK, so I've run into a situation when working on a set of
> attributes
> >> for
> >>> WiMAX that just begs for a named, multi-TLV attribute.
> >>   Could you be more specific?
> >
> > About what?
> 
>   A named, multi-TLV attribute.

Maybe I didn't say it correctly.  I want to name a group of TLVs, I guess.
to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only using
the TLV construct,

> 
>   Most attributes have names.  Most attributes are TLV's.  The
> Extended-Attribute encapsulates multiple TLV's.
> 
>   So... what's a "named, multi-TLV attribute"?  An attribute inside of
> the Extended-Attribute that can carry other TLV's?  Like what's done in
> WiMAX?

Maybe, I'm open; that's why I asked :-).

> 
>   It's a good idea.  And if most vendors have to add WiMAX support
> anyways, much of the code will already exist.
> 
>   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 Aug 27 02:10:10 2008
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 1A9423A6BFB
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 02:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.209
X-Spam-Level: 
X-Spam-Status: No, score=0.209 tagged_above=-999 required=5 tests=[AWL=-0.785,
	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 7Ld1UXRnbAF2
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 02:10:06 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 26E263A6BD6
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 02:10:06 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYGyk-000NHD-HR
	for radiusext-data@psg.com; Wed, 27 Aug 2008 09:06:14 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYGya-000NG3-Fu
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 09:06:09 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id AB3491234225;
	Wed, 27 Aug 2008 11:06:02 +0200 (CEST)
Message-ID: <48B518C2.6020609@deployingradius.com>
Date: Wed, 27 Aug 2008 11:05:06 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net>
In-Reply-To: <004c01c90822$8f7612c0$ae623840$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> Maybe I didn't say it correctly.  I want to name a group of TLVs, I guess.
> to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only using
> the TLV construct,

  Isn't that what the tags are for?

  Foo:1 = 1
  Bar:1 = "hello"
  BaZ:1 = "foo"

  It's not a nice name, but it's a name.

>>   So... what's a "named, multi-TLV attribute"?  An attribute inside of
>> the Extended-Attribute that can carry other TLV's?  Like what's done in
>> WiMAX?
> 
> Maybe, I'm open; that's why I asked :-).

  The main difficulty with that is it's hard to distinguish between
different sets of nested TLV's.  Requiring them to be grouped would help.

  e.g.  An "encapsulating tlv" has sub-tlv's A, B, and C.  What do you
do if you want to send *two* copies of "encapsulating tlv", each with
different values for A, B, and C?

  My guess would to use tags.  The sub-tlv's can be referred to as
"A:1", which would mean "A, encapsulated in it's TLV, which is
encapsulated in Extended-Attribute, which is encapsulated in
Vendor-Specific."

  Ugh.  But it works:

   A:1 = foo
   B:1 = 1
   C:1 = 1.2.3.4
   A:2 = bar
   B:2 = 42
   C:2 = 192.168.0.1

  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 Aug 27 02:29:08 2008
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 D18163A691F
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 02:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.7
X-Spam-Level: *
X-Spam-Status: No, score=1.7 tagged_above=-999 required=5 tests=[AWL=-0.277,
	BAYES_40=-0.185, 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 JqHhmMauWKLC
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 02:29:08 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id CD70E3A6868
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 02:29:07 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYHGZ-000PpW-4K
	for radiusext-data@psg.com; Wed, 27 Aug 2008 09:24:39 +0000
Received: from [76.96.62.32] (helo=QMTA03.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYHGV-000Pot-71
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 09:24:37 +0000
Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43])
	by QMTA03.westchester.pa.mail.comcast.net with comcast
	id 7MGG1a0060vyq2s53MQanH; Wed, 27 Aug 2008 09:24:34 +0000
Received: from gwzPC ([124.120.225.106])
	by OMTA05.westchester.pa.mail.comcast.net with comcast
	id 7MPl1a0022JMgNL3RMQCJw; Wed, 27 Aug 2008 09:24:29 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=o6P6C2fl4Jvpxcyi0NoA:9
 a=xCPB7gAG262JKgn-9rYA:7 a=afnBjQG-SttpDaYejojXPJKpyqEA:4 a=r5QHxzKXScQA:10
 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com>
In-Reply-To: <48B518C2.6020609@deployingradius.com>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 16:22:57 +0700
Message-ID: <005001c90826$8bfd69f0$a3f83dd0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckIJCIOn0USNvKPQtCc8CJ1fTFvCwAASuAg
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Maybe I didn't say it correctly.  I want to name a group of TLVs, I
> guess.
> > to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only
> using
> > the TLV construct,
> 
>   Isn't that what the tags are for?

Not historically.  In RFC 2869, for example, the Tag field is used to group
sets of attributes in an ad-hoc fashion: there's no requirement placed on
the actual membership  of the groups & different groups can contain
different sets of attributes in the same message.

> 
>   Foo:1 = 1
>   Bar:1 = "hello"
>   BaZ:1 = "foo"
> 
>   It's not a nice name, but it's a name.

It's a very inefficient encapsulation, too, since all of the TLVs could be
carried in a single extended attribute.

> 
> >>   So... what's a "named, multi-TLV attribute"?  An attribute inside
> of
> >> the Extended-Attribute that can carry other TLV's?  Like what's done
> in
> >> WiMAX?
> >
> > Maybe, I'm open; that's why I asked :-).
> 
>   The main difficulty with that is it's hard to distinguish between
> different sets of nested TLV's.  Requiring them to be grouped would
> help.
> 
>   e.g.  An "encapsulating tlv" has sub-tlv's A, B, and C.  What do you
> do if you want to send *two* copies of "encapsulating tlv", each with
> different values for A, B, and C?
> 
>   My guess would to use tags.  The sub-tlv's can be referred to as
> "A:1", which would mean "A, encapsulated in it's TLV, which is
> encapsulated in Extended-Attribute, which is encapsulated in
> Vendor-Specific."
> 
>   Ugh.  But it works:
> 
>    A:1 = foo
>    B:1 = 1
>    C:1 = 1.2.3.4
>    A:2 = bar
>    B:2 = 42
>    C:2 = 192.168.0.1
> 
>   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 Aug 27 04:44:03 2008
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 5026C3A69E5
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 04:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.34
X-Spam-Level: 
X-Spam-Status: No, score=-0.34 tagged_above=-999 required=5 tests=[AWL=0.155,
	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 ZMnR7K-QGQih
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 04:44:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 273773A687E
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 04:44:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYJNU-000HkO-7f
	for radiusext-data@psg.com; Wed, 27 Aug 2008 11:39:56 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYJNO-000Hja-JX
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 11:39:54 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 251601234225;
	Wed, 27 Aug 2008 13:39:49 +0200 (CEST)
Message-ID: <48B53CCC.8050505@deployingradius.com>
Date: Wed, 27 Aug 2008 13:38:52 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net>
In-Reply-To: <005001c90826$8bfd69f0$a3f83dd0$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> Not historically.  In RFC 2869, for example, the Tag field is used to group
> sets of attributes in an ad-hoc fashion: there's no requirement placed on
> the actual membership  of the groups & different groups can contain
> different sets of attributes in the same message.

  Then I'm not clear on why the extended attribute format has tags.  I
thought it was about grouping TLV's?

> It's a very inefficient encapsulation, too, since all of the TLVs could be
> carried in a single extended attribute.

  But they can be... the draft says that multiple attributes can go into
one Extended-Attribute, so long as it's not fragmented.  Since the
extended attibute *header* contains the tag, all of the attributes it
encapsulates inherit that tag.

  Or am I missing something completely?

  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 Aug 27 05:31:09 2008
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 966893A6B3C
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 05:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.374
X-Spam-Level: 
X-Spam-Status: No, score=0.374 tagged_above=-999 required=5 tests=[AWL=-0.620,
	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 CndRxGgbD-6n
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 05:31:08 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 8221F3A67A3
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 05:31:08 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYK6t-000N1S-Fr
	for radiusext-data@psg.com; Wed, 27 Aug 2008 12:26:51 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYK6o-000N0d-MQ
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 12:26:49 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id B69991234225;
	Wed, 27 Aug 2008 14:26:45 +0200 (CEST)
Message-ID: <48B547CE.6090500@deployingradius.com>
Date: Wed, 27 Aug 2008 14:25:50 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: "'David B. Nelson'" <dnelson@elbrysnetworks.com>, 
 radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net>
In-Reply-To: <002301c8ff88$cb8734d0$62959e70$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> Alright, how about this?
> 
>    M (More)
> 
>       The More Flag is one (1) bit in length and MUST be present.  When
>       a value to be transmitted exceeds 246 octets in length it is
>       fragmented over two or more Extended Attributes.  If the More Flag
>       is set (1), this indicates that the Value field of the Extended
>       Attribute contains a fragment of a larger value, which is
>       continued in the next Extended Attribute of the same Ext-Type.
>       When the More Flag is clear (0), the final (or only) fragment of
>       the value is contained in the Extended Attribute.  Any Extended 
> 	Attributes containing multiple fragments of the same value MUST be 
> 	in order and MUST be consecutive attributes in the packet.

  Looks good to me.

  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 Aug 27 06:17:33 2008
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 B12183A6B2F
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 06:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.492
X-Spam-Level: *
X-Spam-Status: No, score=1.492 tagged_above=-999 required=5 tests=[AWL=0.070,
	BAYES_20=-0.74, 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 1e5wVRff7l5k
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 06:17:28 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D96023A68EF
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 06:17:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYKpr-00031g-OV
	for radiusext-data@psg.com; Wed, 27 Aug 2008 13:13:19 +0000
Received: from [76.96.62.56] (helo=QMTA06.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYKpj-00030X-6W
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 13:13:17 +0000
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35])
	by QMTA06.westchester.pa.mail.comcast.net with comcast
	id 7Nlv1a0050ldTLk56RDAFW; Wed, 27 Aug 2008 13:13:10 +0000
Received: from gwzPC ([124.120.225.106])
	by OMTA04.westchester.pa.mail.comcast.net with comcast
	id 7RCJ1a0052JMgNL3QRCnQ8; Wed, 27 Aug 2008 13:13:05 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=jg6ihxbZVrdc3QLix-MA:9
 a=ep45UHXkHBiKyE_USXMA:7 a=x1U_b6fhYJydtzmyN2KEahn4CZ4A:4 a=r5QHxzKXScQA:10
 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net> <48B53CCC.8050505@deployingradius.com>
In-Reply-To: <48B53CCC.8050505@deployingradius.com>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 20:12:16 +0700
Message-ID: <007101c90846$965add40$c31097c0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckIOZ3Hwu01OjcjQf+wINqFWxJo5wAC4U5Q
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Not historically.  In RFC 2869, for example, the Tag field is used to
> group
> > sets of attributes in an ad-hoc fashion: there's no requirement
> placed on
> > the actual membership  of the groups & different groups can contain
> > different sets of attributes in the same message.
> 
>   Then I'm not clear on why the extended attribute format has tags.  I
> thought it was about grouping TLV's?

Hmm.  I seem to be having some serious problems communicating today,
or...anyway, I used the word "group" or its plural 3 times in one sentence.
How do you get the idea that tags aren't used for grouping?

> 
> > It's a very inefficient encapsulation, too, since all of the TLVs
> could be
> > carried in a single extended attribute.
> 
>   But they can be... the draft says that multiple attributes can go
> into
> one Extended-Attribute, so long as it's not fragmented.  Since the
> extended attibute *header* contains the tag, all of the attributes it
> encapsulates inherit that tag.

OK, how would you specify this behavior in a document so that humans could
actually understand it?

> 
>   Or am I missing something completely?

Or maybe I am...

> 
>   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 Aug 27 06:19:57 2008
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 C3BF33A68E8
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 06:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.848
X-Spam-Level: *
X-Spam-Status: No, score=1.848 tagged_above=-999 required=5 tests=[AWL=-0.315,
	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 BMnnHoLl9fLd
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 06:19:57 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id DFAC33A67EF
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 06:19:56 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYKtj-0003YF-Fu
	for radiusext-data@psg.com; Wed, 27 Aug 2008 13:17:19 +0000
Received: from [76.96.62.16] (helo=QMTA01.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYKte-0003XO-Fl
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 13:17:17 +0000
Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28])
	by QMTA01.westchester.pa.mail.comcast.net with comcast
	id 7QXN1a0020cZkys51RHD6i; Wed, 27 Aug 2008 13:17:13 +0000
Received: from gwzPC ([124.120.225.106])
	by OMTA10.westchester.pa.mail.comcast.net with comcast
	id 7RGB1a00C2JMgNL3WRGl8R; Wed, 27 Aug 2008 13:17:08 +0000
X-Authority-Analysis: v=1.0 c=1 a=x18D0uCEXKwA:10 a=5QD0VHjLkv0A:10
 a=Y7yyQfWQ_2jG_busszUA:9 a=kadSDizfxR7MozgmMNAt34kz7BgA:4 a=r5QHxzKXScQA:10
 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,
	<radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <002001c8fea3$19c89800$4d59c800$@net> <48A66F52.3060302@deployingradius.com> <002301c8ff88$cb8734d0$62959e70$@net> <48B547CE.6090500@deployingradius.com>
In-Reply-To: <48B547CE.6090500@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Wed, 27 Aug 2008 20:16:09 +0700
Message-ID: <007501c90847$24dd4170$6e97c450$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckIQCw+IZUrnGu2T5uvqzxQz8+FsAABpIIg
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Alright, how about this?
> >
> >    M (More)
> >
> >       The More Flag is one (1) bit in length and MUST be present.
> When
> >       a value to be transmitted exceeds 246 octets in length it is
> >       fragmented over two or more Extended Attributes.  If the More
> Flag
> >       is set (1), this indicates that the Value field of the Extended
> >       Attribute contains a fragment of a larger value, which is
> >       continued in the next Extended Attribute of the same Ext-Type.
> >       When the More Flag is clear (0), the final (or only) fragment
> of
> >       the value is contained in the Extended Attribute.  Any Extended
> > 	Attributes containing multiple fragments of the same value MUST
> be
> > 	in order and MUST be consecutive attributes in the packet.
> 
>   Looks good to me.

OK, cool.  I'll just change the last sentence to say "Any Extended
Attributes containing fragments of the same value MUST be in order and MUST
be consecutive attributes in the packet." because an Extended Attribute
can't contain multiple fragments (my 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  Wed Aug 27 07:32:17 2008
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 BCC8D3A6B21
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 27 Aug 2008 07:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.267
X-Spam-Level: 
X-Spam-Status: No, score=-0.267 tagged_above=-999 required=5 tests=[AWL=0.228,
	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 WCHZlx2ZgX9U
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Wed, 27 Aug 2008 07:32:13 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 9CE513A6BD1
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 27 Aug 2008 07:32:13 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYM0r-000DN7-Ou
	for radiusext-data@psg.com; Wed, 27 Aug 2008 14:28:45 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYM0j-000DJj-Ku
	for radiusext@ops.ietf.org; Wed, 27 Aug 2008 14:28:43 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 4403F1234225;
	Wed, 27 Aug 2008 16:28:36 +0200 (CEST)
Message-ID: <48B5645D.7050202@deployingradius.com>
Date: Wed, 27 Aug 2008 16:27:41 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net> <48B53CCC.8050505@deployingradius.com> <007101c90846$965add40$c31097c0$@net>
In-Reply-To: <007101c90846$965add40$c31097c0$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> Hmm.  I seem to be having some serious problems communicating today,
> or...anyway, I used the word "group" or its plural 3 times in one sentence.
> How do you get the idea that tags aren't used for grouping?

  I think they *are* used for grouping.  You said you wanted to name a
group of TLV's.  I think you can't name the *group*, but you can say
"all of the attributes with tag 1".  That both defines, and names, the
group.

  The RFC 2868 naming for tagged attributes is commonly
Attribute-Name:Tag, or "Attribute-Name = Tag:value".  That method could
be used for tagged extended attributes.

> OK, how would you specify this behavior in a document so that humans could
> actually understand it?

  Multiple attributes can be packed into one Extended-Attribute, so long
as the M bit is zero.  Attributes having different tags MUST be packet
into different Extended-Attributes.

  i.e. if we use a short-cut terminology E(T,foo) meaning "Extended
Attribute with tag T, and contents foo, we have:

  E(1, Foo = 1 | Bar = hello)
  E(1, Foo = 1), E(1, Bar = hello)

  Both meaning "attribute Foo with value 1, tag 1 ALONG WITH attribute
Bar with value hello, tag 1).

  In practice, these attributes would be referred to as:

	Foo:1 = 1
	Bar:1 = hello

  or

	Foo = 1:1
	Bar = 1:hello

  Existing RADIUS attribute parsers handle both formats above.  The only
change is an extra piece of information for the attributes saying "pack
these as extended attributes".  But that's an issue for the dictionaries
and the packet encoding/decoding functions.  It's *shouldn't* affect the
parsing of the textual form of the attributes in server policies.

  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 Aug 28 06:50:09 2008
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 B380428C2C0
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 28 Aug 2008 06:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.636
X-Spam-Level: 
X-Spam-Status: No, score=-0.636 tagged_above=-999 required=5
	tests=[AWL=-0.198, BAYES_00=-2.599, 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 UhAgRGmlYRcA
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 28 Aug 2008 06:50:04 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 2F74B28C276
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 28 Aug 2008 06:50:04 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYhmP-000Mr9-45
	for radiusext-data@psg.com; Thu, 28 Aug 2008 13:43:17 +0000
Received: from [76.96.30.17] (helo=QMTA10.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KYhmA-000Mp2-H7
	for radiusext@ops.ietf.org; Thu, 28 Aug 2008 13:43:08 +0000
Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id 7p3X1a01L0b6N64AApj15U; Thu, 28 Aug 2008 13:43:01 +0000
Received: from gwzPC ([124.121.211.79])
	by OMTA03.emeryville.ca.mail.comcast.net with comcast
	id 7pib1a0171jLGTg8PpirJe; Thu, 28 Aug 2008 13:42:59 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=N74A9zTxEnW9UJRK9uMA:9
 a=CIFC01APV_07c_MZPqnOE6F0f-MA:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net> <48B53CCC.8050505@deployingradius.com> <007101c90846$965add40$c31097c0$@net> <48B5645D.7050202@deployingradius.com>
In-Reply-To: <48B5645D.7050202@deployingradius.com>
Subject: RE: no overall type in Extended Attributes
Date: Thu, 28 Aug 2008 20:42:30 +0700
Message-ID: <00a601c90913$f27767b0$d7663710$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckIUTKJeMje7uFjR42RjcueNkTOLwAwKK3Q
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Hmm.  I seem to be having some serious problems communicating today,
> > or...anyway, I used the word "group" or its plural 3 times in one
> sentence.
> > How do you get the idea that tags aren't used for grouping?
> 
>   I think they *are* used for grouping.  You said you wanted to name a
> group of TLV's.  

No, I said that I want to name an attribute that consists of a group of
TLVs, not the same thing.  For example: a cryptosuite consists of a an
encryption algorithm identifier and an integrity-protection algorithm
identifier.  Multiple cryptosuite attributes can be in the same message.
Both the integrity-protection and encryption algorithms MUST be present or
the cryptosystem attribute is malformed.  I know how to do this easily & in
a way that comprehensible in Diameter or w/a legacy RADIUS attribute.
Apparently it is not possible to specify such a thing in an easily
comprehensible fashion using Extended Attributes.  I consider this to be a
problem (now -- I didn't before because I hadn't run into this,
short-sighted, I know); I'm not sure why (given your sympathetic concern for
programmers who would separate the word "hello" into 5 different attributes
;-) do not.

...



--
to unsubscribe send a message to 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 Aug 28 07:08:52 2008
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 12B043A6C66
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 28 Aug 2008 07:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.3
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 tagged_above=-999 required=5 tests=[AWL=0.195,
	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 4-TsRQWbOwvP
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Thu, 28 Aug 2008 07:08:51 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 16D283A6AE2
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 28 Aug 2008 07:08:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KYi4E-000PFH-3t
	for radiusext-data@psg.com; Thu, 28 Aug 2008 14:01:42 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KYi3z-000PDU-4G
	for radiusext@ops.ietf.org; Thu, 28 Aug 2008 14:01:36 +0000
Received: from [10.0.1.49] (alexander.quiconnect.net [213.30.156.62])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id F1B291234091;
	Thu, 28 Aug 2008 16:01:25 +0200 (CEST)
Message-ID: <48B6AF7C.9000004@deployingradius.com>
Date: Thu, 28 Aug 2008 16:00:28 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net> <48B53CCC.8050505@deployingradius.com> <007101c90846$965add40$c31097c0$@net> <48B5645D.7050202@deployingradius.com> <00a601c90913$f27767b0$d7663710$@net>
In-Reply-To: <00a601c90913$f27767b0$d7663710$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> No, I said that I want to name an attribute that consists of a group of
> TLVs, not the same thing.

  Hmm... the number space for the Extended-Types is flat.  So one
attribute cannot "consist of" a group of TLV's.

>  For example: a cryptosuite consists of a an
> encryption algorithm identifier and an integrity-protection algorithm
> identifier.  Multiple cryptosuite attributes can be in the same message.
> Both the integrity-protection and encryption algorithms MUST be present or
> the cryptosystem attribute is malformed.  I know how to do this easily & in
> a way that comprehensible in Diameter or w/a legacy RADIUS attribute.

  Diameter has a "group" attribute, which is easy.  I don't know how to
do this with a legacy attribute, other than via a complex type.

> Apparently it is not possible to specify such a thing in an easily
> comprehensible fashion using Extended Attributes.  I consider this to be a
> problem (now -- I didn't before because I hadn't run into this,
> short-sighted, I know); I'm not sure why (given your sympathetic concern for
> programmers who would separate the word "hello" into 5 different attributes
> ;-) do not.

  I don't see a problem with sub-TLV's, like is done for WiMAX.  The
various vendors will be implementing WiMAX anyways, so adding sub-TLV's
here wouldn't be a problem.

  This would involve extending the RADIUS data model to include a "tlv"
type.  If the format is the normal 8-bit type, 8-bit data, it would be
compatible with the WiMAX definition, the 3GPP definitions, and perhaps
some other vendor-specific definitions.

  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 Aug 29 09:55:50 2008
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 58F4228C113
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 29 Aug 2008 09:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.509
X-Spam-Level: 
X-Spam-Status: No, score=0.509 tagged_above=-999 required=5 tests=[AWL=0.946,
	BAYES_00=-2.599, 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 6t2StKVKpClD
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 29 Aug 2008 09:55:44 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id A06DF28C10A
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 29 Aug 2008 09:55:41 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KZ7Bw-0007uc-DO
	for radiusext-data@psg.com; Fri, 29 Aug 2008 16:51:20 +0000
Received: from [76.96.62.32] (helo=QMTA03.westchester.pa.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KZ7Bo-0007tY-NU
	for radiusext@ops.ietf.org; Fri, 29 Aug 2008 16:51:18 +0000
Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20])
	by QMTA03.westchester.pa.mail.comcast.net with comcast
	id 8E801a0020SCNGk53GrB8o; Fri, 29 Aug 2008 16:51:11 +0000
Received: from gwzPC ([124.120.226.31])
	by OMTA09.westchester.pa.mail.comcast.net with comcast
	id 8GqM1a00D0hGZEc3VGqp0A; Fri, 29 Aug 2008 16:51:06 +0000
X-Authority-Analysis: v=1.0 c=1 a=67bMvK2nUSEA:10 a=4UEKp4xQsFBPAP4Wwd4A:9
 a=HY3pLAx3jvwqmeme0dNNsXsA4VkA:4 a=r5QHxzKXScQA:10 a=v47ZLdibA2YA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net> <48B53CCC.8050505@deployingradius.com> <007101c90846$965add40$c31097c0$@net> <48B5645D.7050202@deployingradius.com> <00a601c90913$f27767b0$d7663710$@net> <48B6AF7C.9000004@deployingradius.com>
In-Reply-To: <48B6AF7C.9000004@deployingradius.com>
Subject: RE: no overall type in Extended Attributes
Date: Fri, 29 Aug 2008 23:50:08 +0700
Message-ID: <002101c909f7$5a964760$0fc2d620$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckJFpAzVTW/ExAmSWGImlTZEDEfjwA3w2xQ
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > No, I said that I want to name an attribute that consists of a group
> of
> > TLVs, not the same thing.
> 
>   Hmm... the number space for the Extended-Types is flat.  So one
> attribute cannot "consist of" a group of TLV's.
> 
> >  For example: a cryptosuite consists of a an
> > encryption algorithm identifier and an integrity-protection algorithm
> > identifier.  Multiple cryptosuite attributes can be in the same
> message.
> > Both the integrity-protection and encryption algorithms MUST be
> present or
> > the cryptosystem attribute is malformed.  I know how to do this
> easily & in
> > a way that comprehensible in Diameter or w/a legacy RADIUS attribute.
> 
>   Diameter has a "group" attribute, which is easy.  I don't know how to
> do this with a legacy attribute, other than via a complex type.

Right.  The example is related to security...anyway, here's an idea: how
about breaking the Ext-Type field into 2 8-bit fields one of which stays in
the Extended Attribute header (giving naming capability for the attribute
itself) & the other staying in the TLV header?  

> 
> > Apparently it is not possible to specify such a thing in an easily
> > comprehensible fashion using Extended Attributes.  I consider this to
> be a
> > problem (now -- I didn't before because I hadn't run into this,
> > short-sighted, I know); I'm not sure why (given your sympathetic
> concern for
> > programmers who would separate the word "hello" into 5 different
> attributes
> > ;-) do not.
> 
>   I don't see a problem with sub-TLV's, like is done for WiMAX.  The
> various vendors will be implementing WiMAX anyways, so adding sub-TLV's
> here wouldn't be a problem.
> 
>   This would involve extending the RADIUS data model to include a "tlv"
> type.  If the format is the normal 8-bit type, 8-bit data, it would be
> compatible with the WiMAX definition, the 3GPP definitions, and perhaps
> some other vendor-specific definitions.
> 
>   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 Aug 29 22:17:11 2008
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 619A23A6765
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 29 Aug 2008 22:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.495
X-Spam-Level: 
X-Spam-Status: No, score=-8.495 tagged_above=-999 required=5
	tests=[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 QBWM1qLkn6V6
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 29 Aug 2008 22:17:10 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 3A0BD3A6819
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 29 Aug 2008 22:17:10 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KZIjn-0005po-FL
	for radiusext-data@psg.com; Sat, 30 Aug 2008 05:11:03 +0000
Received: from [207.46.52.71] (helo=smtp-sin.microsoft.com)
	by psg.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.69 (FreeBSD))
	(envelope-from <abhisht@microsoft.com>)
	id 1KZIjj-0005pD-OC
	for radiusext@ops.ietf.org; Sat, 30 Aug 2008 05:11:01 +0000
Received: from sin-exhub-c401.southpacific.corp.microsoft.com (157.60.222.31)
 by SIN-EXGWY-E801.partners.extranet.microsoft.com (10.251.168.100) with
 Microsoft SMTP Server (TLS) id 8.1.291.1; Sat, 30 Aug 2008 13:10:49 +0800
Received: from AA-EXMSG-C424.southpacific.corp.microsoft.com ([157.60.226.29])
 by sin-exhub-c401.southpacific.corp.microsoft.com ([157.60.222.31]) with
 mapi; Sat, 30 Aug 2008 13:10:48 +0800
From: Abhishek Tiwari <abhisht@microsoft.com>
To: Glen Zorn <glenzorn@comcast.net>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Sat, 30 Aug 2008 13:10:46 +0800
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Thread-Topic: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt
 (fwd)
Thread-Index: Acj9swl5Q5+W+luPTBm1XAuPqNYzHABHQ7rQAuOK83A=
Message-ID: <701A6382E4B1B0458FC27DE8F6A4770819533737F4@AA-EXMSG-C424.southpacific.corp.microsoft.com>
References: <Pine.LNX.4.64.0808131907000.24114@internaut.com>
 <003301c8fed1$e9571f00$bc055d00$@net>
In-Reply-To: <003301c8fed1$e9571f00$bc055d00$@net>
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>

I have submitted the new draft addressing the most of the feedbacks receive=
d from Glen - except splitting the draft into two (individual tunnel id req=
uest for each tunnel).

Abhishek

-----Original Message-----
From: Glen Zorn [mailto:glenzorn@comcast.net]
Sent: Friday, August 15, 2008 5:54 PM
To: Abhishek Tiwari
Cc: radiusext@ops.ietf.org
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fw=
d)

Glancing over this:

Since there's only one author, it would be good to move the apostrophe in
"Authors'" left.

In the table in Section 3, move the abbreviation (ESP) next to "Payload".

Since new values of the Tunnel-Type Attribute are allocated by IETF
Consensus, it might be a better idea to separate this into 2 docs, one for
the ESP value & the other for the proprietary one.  In fact, because the
spec for the Microsoft Secure Socket Tunneling Protocol is public & appears
fairly stable, I would prefer that the allocation be part of an
Informational RFC describing the protocol.  At the very least, though, the
name needs to be changed to "Microsoft's Secure Socket Tunneling Protocol"
(or something similar) that identifies its proprietary nature.





--
to unsubscribe send a message to 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 Aug 29 22:33:04 2008
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 30F7D3A68EA
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 29 Aug 2008 22:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.212
X-Spam-Level: *
X-Spam-Status: No, score=1.212 tagged_above=-999 required=5 tests=[AWL=0.006,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	RCVD_IN_NJABL_PROXY=1.643, 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 VaWJZfIVTzPl
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Fri, 29 Aug 2008 22:33:03 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 1FD763A6818
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 29 Aug 2008 22:33:03 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KZJ06-0007S0-25
	for radiusext-data@psg.com; Sat, 30 Aug 2008 05:27:54 +0000
Received: from [76.96.30.17] (helo=QMTA10.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KZJ02-0007Ra-Jw
	for radiusext@ops.ietf.org; Sat, 30 Aug 2008 05:27:52 +0000
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id 8VMV1a0040mlR8UAAVTpxw; Sat, 30 Aug 2008 05:27:50 +0000
Received: from gwzPC ([124.120.226.12])
	by OMTA11.emeryville.ca.mail.comcast.net with comcast
	id 8VTQ1a0030GgmpY8XVTg9r; Sat, 30 Aug 2008 05:27:47 +0000
X-Authority-Analysis: v=1.0 c=1 a=KaEX0pHM2ccA:10 a=_RDAsohIr2QA:10
 a=E8a-ox4PRwIwT20QkqsA:9 a=90omom3Rcq0QCdWj-KWLknVOSW4A:4 a=-AOE9ft50oIA:10
 a=IQdfU-mQRuwA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Abhishek Tiwari'" <abhisht@microsoft.com>
Cc: <radiusext@ops.ietf.org>
References: <Pine.LNX.4.64.0808131907000.24114@internaut.com> <003301c8fed1$e9571f00$bc055d00$@net> <701A6382E4B1B0458FC27DE8F6A4770819533737F4@AA-EXMSG-C424.southpacific.corp.microsoft.com>
In-Reply-To: <701A6382E4B1B0458FC27DE8F6A4770819533737F4@AA-EXMSG-C424.southpacific.corp.microsoft.com>
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Date: Sat, 30 Aug 2008 12:27:07 +0700
Message-ID: <002b01c90a61$136177b0$3a246710$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acj9swl5Q5+W+luPTBm1XAuPqNYzHABHQ7rQAuOK83AAAH7Y0A==
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Abhishek Tiwari [mailto:abhisht@microsoft.com] writes:

> I have submitted the new draft addressing the most of the feedbacks
> received from Glen - except splitting the draft into two (individual
> tunnel id request for each tunnel).

Actually, that suggestion was more in the realm of "help you get it
published" than "something wrong w/the draft" anyway.  I suspect that it may
be difficult to round up IETF consensus around a proprietary tunnel type w/o
providing considerably more detail but I've been wrong before.  Good luck!

...




--
to unsubscribe send a message to 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 Aug 30 03:14:52 2008
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 B57903A6977
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 30 Aug 2008 03:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.037
X-Spam-Level: 
X-Spam-Status: No, score=-101.037 tagged_above=-999 required=5
	tests=[AWL=-2.685, BAYES_00=-2.599, FH_HAS_XAIMC=2.696,
	FH_RELAY_NODNS=1.451, 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 dCGFE1TzjEJ6
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 30 Aug 2008 03:14:52 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D3AC33A69F4
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 30 Aug 2008 03:14:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KZNNA-0009XP-JE
	for radiusext-data@psg.com; Sat, 30 Aug 2008 10:08:00 +0000
Received: from [202.99.23.227] (helo=people.com.cn)
	by psg.com with smtp (Exim 4.69 (FreeBSD))
	(envelope-from <Internet-Drafts@ietf.org>)
	id 1KZNN6-0009Wq-5p
	for radiusext@ops.ietf.org; Sat, 30 Aug 2008 10:07:58 +0000
Received: from people.com.cn([192.168.12.36]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm448b92658; Sat, 30 Aug 2008 18:23:32 +0800
Received: from mail.ietf.org([64.170.98.32]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm5248b49291; Wed, 27 Aug 2008 00:22:41 +0800
Received: from mail.ietf.org([64.170.98.32]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id AISP action; Wed, 27 Aug 2008 00:22:41 +0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C94E928C1C4;
	Tue, 26 Aug 2008 08:30:03 -0700 (PDT)
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 7F8A83A6B7F; Tue, 26 Aug 2008 08:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-radext-design-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080826153001.7F8A83A6B7F@core3.amsl.com>
Date: Tue, 26 Aug 2008 08:30:01 -0700 (PDT)
Cc: radiusext@ops.ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
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, et al.
	Filename        : draft-ietf-radext-design-05.txt
	Pages           : 36
	Date            : 2008-08-26

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-05.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-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-08-26082119.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--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  Sat Aug 30 04:29:17 2008
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 BDC533A6ADB
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 30 Aug 2008 04:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[AWL=0.336,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	RCVD_IN_NJABL_PROXY=1.643, 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 Ld8ysH2j7xGz
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sat, 30 Aug 2008 04:29:17 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id D2EA93A6ADA
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 30 Aug 2008 04:29:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KZOYt-000HQb-TQ
	for radiusext-data@psg.com; Sat, 30 Aug 2008 11:24:11 +0000
Received: from [76.96.30.16] (helo=QMTA01.emeryville.ca.mail.comcast.net)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <glenzorn@comcast.net>)
	id 1KZOYl-000HPS-JQ
	for radiusext@ops.ietf.org; Sat, 30 Aug 2008 11:24:09 +0000
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id 8b911a00D0x6nqcA1bQ2yj; Sat, 30 Aug 2008 11:24:02 +0000
Received: from gwzPC ([124.120.226.12])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id 8bPj1a0090GgmpY8YbPvo2; Sat, 30 Aug 2008 11:24:00 +0000
X-Authority-Analysis: v=1.0 c=1 a=uws2Yy0q-LIA:10 a=DV0zoeMap5sA:10
 a=48vgC7mUAAAA:8 a=BF-bCPiDz6j3ovcoNggA:9 a=Z_0iNXRy70GllMmnYLzHuJa6UE4A:4
 a=oltX7JrCFroA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: New version of encrypted attributes draft
Date: Sat, 30 Aug 2008 18:23:25 +0700
Message-ID: <004801c90a92$d6fce250$84f6a6f0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckKktFMjDa6ze7lQgiPrsa9m3CIgQ==
Content-Language: en-us
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Transmitting Confidential Data in RADIUS
	Author(s)       : G. Zorn, et al.
	Filename        : draft-zorn-radius-encattr-12.txt
	Pages           : 24
	Date            : 2008-08-08

This document defines a set of Type-Length-Value (TLV) tuples which,
when encapsulated in RADIUS Extended Attributes, are designed to
allow the secure transmission of sensitive or confidential data
(including encryption keys) between RADIUS clients and servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zorn-radius-encattr-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/draft-zorn-radius-encattr-12.txt



--
to unsubscribe send a message to 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 Aug 31 09:06:20 2008
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 96B0B28C15E
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 31 Aug 2008 09:06:20 -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_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 oqnzrjxQkRb6
	for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>;
	Sun, 31 Aug 2008 09:06:19 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62])
	by core3.amsl.com (Postfix) with ESMTP id 91AB33A6B6A
	for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 31 Aug 2008 09:06:19 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD))
	(envelope-from <owner-radiusext@ops.ietf.org>)
	id 1KZpLf-000KS3-Lv
	for radiusext-data@psg.com; Sun, 31 Aug 2008 16:00:19 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com)
	by psg.com with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <aland@deployingradius.com>)
	id 1KZpLb-000KQn-KV
	for radiusext@ops.ietf.org; Sun, 31 Aug 2008 16:00:17 +0000
Received: from [192.168.0.14] (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238])
	by liberty.deployingradius.com (Postfix) with ESMTPSA id 339F4123430C;
	Sun, 31 Aug 2008 18:00:11 +0200 (CEST)
Message-ID: <48BABFCE.40101@deployingradius.com>
Date: Sun, 31 Aug 2008 17:59:10 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
References: <Pine.LNX.4.64.0808131912120.24114@internaut.com> <000801c8fe00$b50248a0$1f06d9e0$@net> <003a01c907fc$7c437b00$74ca7100$@net> <48B4F3CA.7020901@deployingradius.com> <004701c90820$5ce75550$16b5fff0$@net> <48B51378.2040100@deployingradius.com> <004c01c90822$8f7612c0$ae623840$@net> <48B518C2.6020609@deployingradius.com> <005001c90826$8bfd69f0$a3f83dd0$@net> <48B53CCC.8050505@deployingradius.com> <007101c90846$965add40$c31097c0$@net> <48B5645D.7050202@deployingradius.com> <00a601c90913$f27767b0$d7663710$@net> <48B6AF7C.9000004@deployingradius.com> <002101c909f7$5a964760$0fc2d620$@net>
In-Reply-To: <002101c909f7$5a964760$0fc2d620$@net>
X-Enigmail-Version: 0.95.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>

Glen Zorn wrote:
> Right.  The example is related to security...anyway, here's an idea: how
> about breaking the Ext-Type field into 2 8-bit fields one of which stays in
> the Extended Attribute header (giving naming capability for the attribute
> itself) & the other staying in the TLV header?  

  Are we back to 8-bit types for the Extended-Attribute?

  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-data@psg.com
Delivery-date: Sun, 31 Aug 2008 16:01:47 +0000
Message-ID: <48BABFCE.40101@deployingradius.com>
Date: Sun, 31 Aug 2008 17:59:10 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> Right.  The example is related to security...anyway, here's an idea: how
> about breaking the Ext-Type field into 2 8-bit fields one of which stays in
> the Extended Attribute header (giving naming capability for the attribute
> itself) & the other staying in the TLV header?  

  Are we back to 8-bit types for the Extended-Attribute?

  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-data@psg.com
Delivery-date: Sat, 30 Aug 2008 11:26:16 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: New version of encrypted attributes draft
Date: Sat, 30 Aug 2008 18:23:25 +0700
Message-ID: <004801c90a92$d6fce250$84f6a6f0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: AckKktFMjDa6ze7lQgiPrsa9m3CIgQ==
Content-Language: en-us

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Transmitting Confidential Data in RADIUS
	Author(s)       : G. Zorn, et al.
	Filename        : draft-zorn-radius-encattr-12.txt
	Pages           : 24
	Date            : 2008-08-08

This document defines a set of Type-Length-Value (TLV) tuples which,
when encapsulated in RADIUS Extended Attributes, are designed to
allow the secure transmission of sensitive or confidential data
(including encryption keys) between RADIUS clients and servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zorn-radius-encattr-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/draft-zorn-radius-encattr-12.txt



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 30 Aug 2008 10:10:07 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-radext-design-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080826153001.7F8A83A6B7F@core3.amsl.com>
Date: Tue, 26 Aug 2008 08:30:01 -0700 (PDT)
Cc: radiusext@ops.ietf.org
Reply-To: internet-drafts@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, et al.
	Filename        : draft-ietf-radext-design-05.txt
	Pages           : 36
	Date            : 2008-08-26

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-05.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-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-08-26082119.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--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-data@psg.com
Delivery-date: Sat, 30 Aug 2008 05:30:00 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Abhishek Tiwari'" <abhisht@microsoft.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Date: Sat, 30 Aug 2008 12:27:07 +0700
Message-ID: <002b01c90a61$136177b0$3a246710$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9swl5Q5+W+luPTBm1XAuPqNYzHABHQ7rQAuOK83AAAH7Y0A==
Content-Language: en-us

Abhishek Tiwari [mailto:abhisht@microsoft.com] writes:

> I have submitted the new draft addressing the most of the feedbacks
> received from Glen - except splitting the draft into two (individual
> tunnel id request for each tunnel).

Actually, that suggestion was more in the realm of "help you get it
published" than "something wrong w/the draft" anyway.  I suspect that it may
be difficult to round up IETF consensus around a proprietary tunnel type w/o
providing considerably more detail but I've been wrong before.  Good luck!

...




--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 30 Aug 2008 05:13:06 +0000
From: Abhishek Tiwari <abhisht@microsoft.com>
To: Glen Zorn <glenzorn@comcast.net>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Sat, 30 Aug 2008 13:10:46 +0800
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Thread-Topic: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Thread-Index: Acj9swl5Q5+W+luPTBm1XAuPqNYzHABHQ7rQAuOK83A=
Message-ID: <701A6382E4B1B0458FC27DE8F6A4770819533737F4@AA-EXMSG-C424.southpacific.corp.microsoft.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

I have submitted the new draft addressing the most of the feedbacks receive=
d from Glen - except splitting the draft into two (individual tunnel id req=
uest for each tunnel).

Abhishek

-----Original Message-----
From: Glen Zorn [mailto:glenzorn@comcast.net]
Sent: Friday, August 15, 2008 5:54 PM
To: Abhishek Tiwari
Cc: radiusext@ops.ietf.org
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fw=
d)

Glancing over this:

Since there's only one author, it would be good to move the apostrophe in
"Authors'" left.

In the table in Section 3, move the abbreviation (ESP) next to "Payload".

Since new values of the Tunnel-Type Attribute are allocated by IETF
Consensus, it might be a better idea to separate this into 2 docs, one for
the ESP value & the other for the proprietary one.  In fact, because the
spec for the Microsoft Secure Socket Tunneling Protocol is public & appears
fairly stable, I would prefer that the allocation be part of an
Informational RFC describing the protocol.  At the very least, though, the
name needs to be changed to "Microsoft's Secure Socket Tunneling Protocol"
(or something similar) that identifies its proprietary nature.





--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 29 Aug 2008 16:52:53 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Fri, 29 Aug 2008 23:50:08 +0700
Message-ID: <002101c909f7$5a964760$0fc2d620$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckJFpAzVTW/ExAmSWGImlTZEDEfjwA3w2xQ
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > No, I said that I want to name an attribute that consists of a group
> of
> > TLVs, not the same thing.
> 
>   Hmm... the number space for the Extended-Types is flat.  So one
> attribute cannot "consist of" a group of TLV's.
> 
> >  For example: a cryptosuite consists of a an
> > encryption algorithm identifier and an integrity-protection algorithm
> > identifier.  Multiple cryptosuite attributes can be in the same
> message.
> > Both the integrity-protection and encryption algorithms MUST be
> present or
> > the cryptosystem attribute is malformed.  I know how to do this
> easily & in
> > a way that comprehensible in Diameter or w/a legacy RADIUS attribute.
> 
>   Diameter has a "group" attribute, which is easy.  I don't know how to
> do this with a legacy attribute, other than via a complex type.

Right.  The example is related to security...anyway, here's an idea: how
about breaking the Ext-Type field into 2 8-bit fields one of which stays in
the Extended Attribute header (giving naming capability for the attribute
itself) & the other staying in the TLV header?  

> 
> > Apparently it is not possible to specify such a thing in an easily
> > comprehensible fashion using Extended Attributes.  I consider this to
> be a
> > problem (now -- I didn't before because I hadn't run into this,
> > short-sighted, I know); I'm not sure why (given your sympathetic
> concern for
> > programmers who would separate the word "hello" into 5 different
> attributes
> > ;-) do not.
> 
>   I don't see a problem with sub-TLV's, like is done for WiMAX.  The
> various vendors will be implementing WiMAX anyways, so adding sub-TLV's
> here wouldn't be a problem.
> 
>   This would involve extending the RADIUS data model to include a "tlv"
> type.  If the format is the normal 8-bit type, 8-bit data, it would be
> compatible with the WiMAX definition, the 3GPP definitions, and perhaps
> some other vendor-specific definitions.
> 
>   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-data@psg.com
Delivery-date: Thu, 28 Aug 2008 14:03:18 +0000
Message-ID: <48B6AF7C.9000004@deployingradius.com>
Date: Thu, 28 Aug 2008 16:00:28 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> No, I said that I want to name an attribute that consists of a group of
> TLVs, not the same thing.

  Hmm... the number space for the Extended-Types is flat.  So one
attribute cannot "consist of" a group of TLV's.

>  For example: a cryptosuite consists of a an
> encryption algorithm identifier and an integrity-protection algorithm
> identifier.  Multiple cryptosuite attributes can be in the same message.
> Both the integrity-protection and encryption algorithms MUST be present or
> the cryptosystem attribute is malformed.  I know how to do this easily & in
> a way that comprehensible in Diameter or w/a legacy RADIUS attribute.

  Diameter has a "group" attribute, which is easy.  I don't know how to
do this with a legacy attribute, other than via a complex type.

> Apparently it is not possible to specify such a thing in an easily
> comprehensible fashion using Extended Attributes.  I consider this to be a
> problem (now -- I didn't before because I hadn't run into this,
> short-sighted, I know); I'm not sure why (given your sympathetic concern for
> programmers who would separate the word "hello" into 5 different attributes
> ;-) do not.

  I don't see a problem with sub-TLV's, like is done for WiMAX.  The
various vendors will be implementing WiMAX anyways, so adding sub-TLV's
here wouldn't be a problem.

  This would involve extending the RADIUS data model to include a "tlv"
type.  If the format is the normal 8-bit type, 8-bit data, it would be
compatible with the WiMAX definition, the 3GPP definitions, and perhaps
some other vendor-specific definitions.

  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-data@psg.com
Delivery-date: Thu, 28 Aug 2008 13:45:09 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Thu, 28 Aug 2008 20:42:30 +0700
Message-ID: <00a601c90913$f27767b0$d7663710$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckIUTKJeMje7uFjR42RjcueNkTOLwAwKK3Q
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Hmm.  I seem to be having some serious problems communicating today,
> > or...anyway, I used the word "group" or its plural 3 times in one
> sentence.
> > How do you get the idea that tags aren't used for grouping?
> 
>   I think they *are* used for grouping.  You said you wanted to name a
> group of TLV's.  

No, I said that I want to name an attribute that consists of a group of
TLVs, not the same thing.  For example: a cryptosuite consists of a an
encryption algorithm identifier and an integrity-protection algorithm
identifier.  Multiple cryptosuite attributes can be in the same message.
Both the integrity-protection and encryption algorithms MUST be present or
the cryptosystem attribute is malformed.  I know how to do this easily & in
a way that comprehensible in Diameter or w/a legacy RADIUS attribute.
Apparently it is not possible to specify such a thing in an easily
comprehensible fashion using Extended Attributes.  I consider this to be a
problem (now -- I didn't before because I hadn't run into this,
short-sighted, I know); I'm not sure why (given your sympathetic concern for
programmers who would separate the word "hello" into 5 different attributes
;-) do not.

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 14:29:16 +0000
Message-ID: <48B5645D.7050202@deployingradius.com>
Date: Wed, 27 Aug 2008 16:27:41 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> Hmm.  I seem to be having some serious problems communicating today,
> or...anyway, I used the word "group" or its plural 3 times in one sentence.
> How do you get the idea that tags aren't used for grouping?

  I think they *are* used for grouping.  You said you wanted to name a
group of TLV's.  I think you can't name the *group*, but you can say
"all of the attributes with tag 1".  That both defines, and names, the
group.

  The RFC 2868 naming for tagged attributes is commonly
Attribute-Name:Tag, or "Attribute-Name = Tag:value".  That method could
be used for tagged extended attributes.

> OK, how would you specify this behavior in a document so that humans could
> actually understand it?

  Multiple attributes can be packed into one Extended-Attribute, so long
as the M bit is zero.  Attributes having different tags MUST be packet
into different Extended-Attributes.

  i.e. if we use a short-cut terminology E(T,foo) meaning "Extended
Attribute with tag T, and contents foo, we have:

  E(1, Foo = 1 | Bar = hello)
  E(1, Foo = 1), E(1, Bar = hello)

  Both meaning "attribute Foo with value 1, tag 1 ALONG WITH attribute
Bar with value hello, tag 1).

  In practice, these attributes would be referred to as:

	Foo:1 = 1
	Bar:1 = hello

  or

	Foo = 1:1
	Bar = 1:hello

  Existing RADIUS attribute parsers handle both formats above.  The only
change is an extra piece of information for the attributes saying "pack
these as extended attributes".  But that's an issue for the dictionaries
and the packet encoding/decoding functions.  It's *shouldn't* affect the
parsing of the textual form of the attributes in server policies.

  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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 13:17:27 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'David B. Nelson'" <dnelson@elbrysnetworks.com>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Wed, 27 Aug 2008 20:16:09 +0700
Message-ID: <007501c90847$24dd4170$6e97c450$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckIQCw+IZUrnGu2T5uvqzxQz8+FsAABpIIg
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Alright, how about this?
> >
> >    M (More)
> >
> >       The More Flag is one (1) bit in length and MUST be present.
> When
> >       a value to be transmitted exceeds 246 octets in length it is
> >       fragmented over two or more Extended Attributes.  If the More
> Flag
> >       is set (1), this indicates that the Value field of the Extended
> >       Attribute contains a fragment of a larger value, which is
> >       continued in the next Extended Attribute of the same Ext-Type.
> >       When the More Flag is clear (0), the final (or only) fragment
> of
> >       the value is contained in the Extended Attribute.  Any Extended
> > 	Attributes containing multiple fragments of the same value MUST
> be
> > 	in order and MUST be consecutive attributes in the packet.
> 
>   Looks good to me.

OK, cool.  I'll just change the last sentence to say "Any Extended
Attributes containing fragments of the same value MUST be in order and MUST
be consecutive attributes in the packet." because an Extended Attribute
can't contain multiple fragments (my 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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 13:13:58 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 20:12:16 +0700
Message-ID: <007101c90846$965add40$c31097c0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckIOZ3Hwu01OjcjQf+wINqFWxJo5wAC4U5Q
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Not historically.  In RFC 2869, for example, the Tag field is used to
> group
> > sets of attributes in an ad-hoc fashion: there's no requirement
> placed on
> > the actual membership  of the groups & different groups can contain
> > different sets of attributes in the same message.
> 
>   Then I'm not clear on why the extended attribute format has tags.  I
> thought it was about grouping TLV's?

Hmm.  I seem to be having some serious problems communicating today,
or...anyway, I used the word "group" or its plural 3 times in one sentence.
How do you get the idea that tags aren't used for grouping?

> 
> > It's a very inefficient encapsulation, too, since all of the TLVs
> could be
> > carried in a single extended attribute.
> 
>   But they can be... the draft says that multiple attributes can go
> into
> one Extended-Attribute, so long as it's not fragmented.  Since the
> extended attibute *header* contains the tag, all of the attributes it
> encapsulates inherit that tag.

OK, how would you specify this behavior in a document so that humans could
actually understand it?

> 
>   Or am I missing something completely?

Or maybe I am...

> 
>   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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 12:27:11 +0000
Message-ID: <48B547CE.6090500@deployingradius.com>
Date: Wed, 27 Aug 2008 14:25:50 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,  radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> Alright, how about this?
> 
>    M (More)
> 
>       The More Flag is one (1) bit in length and MUST be present.  When
>       a value to be transmitted exceeds 246 octets in length it is
>       fragmented over two or more Extended Attributes.  If the More Flag
>       is set (1), this indicates that the Value field of the Extended
>       Attribute contains a fragment of a larger value, which is
>       continued in the next Extended Attribute of the same Ext-Type.
>       When the More Flag is clear (0), the final (or only) fragment of
>       the value is contained in the Extended Attribute.  Any Extended 
> 	Attributes containing multiple fragments of the same value MUST be 
> 	in order and MUST be consecutive attributes in the packet.

  Looks good to me.

  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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 11:40:38 +0000
Message-ID: <48B53CCC.8050505@deployingradius.com>
Date: Wed, 27 Aug 2008 13:38:52 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> Not historically.  In RFC 2869, for example, the Tag field is used to group
> sets of attributes in an ad-hoc fashion: there's no requirement placed on
> the actual membership  of the groups & different groups can contain
> different sets of attributes in the same message.

  Then I'm not clear on why the extended attribute format has tags.  I
thought it was about grouping TLV's?

> It's a very inefficient encapsulation, too, since all of the TLVs could be
> carried in a single extended attribute.

  But they can be... the draft says that multiple attributes can go into
one Extended-Attribute, so long as it's not fragmented.  Since the
extended attibute *header* contains the tag, all of the attributes it
encapsulates inherit that tag.

  Or am I missing something completely?

  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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 09:24:56 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 16:22:57 +0700
Message-ID: <005001c90826$8bfd69f0$a3f83dd0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckIJCIOn0USNvKPQtCc8CJ1fTFvCwAASuAg
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Maybe I didn't say it correctly.  I want to name a group of TLVs, I
> guess.
> > to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only
> using
> > the TLV construct,
> 
>   Isn't that what the tags are for?

Not historically.  In RFC 2869, for example, the Tag field is used to group
sets of attributes in an ad-hoc fashion: there's no requirement placed on
the actual membership  of the groups & different groups can contain
different sets of attributes in the same message.

> 
>   Foo:1 = 1
>   Bar:1 = "hello"
>   BaZ:1 = "foo"
> 
>   It's not a nice name, but it's a name.

It's a very inefficient encapsulation, too, since all of the TLVs could be
carried in a single extended attribute.

> 
> >>   So... what's a "named, multi-TLV attribute"?  An attribute inside
> of
> >> the Extended-Attribute that can carry other TLV's?  Like what's done
> in
> >> WiMAX?
> >
> > Maybe, I'm open; that's why I asked :-).
> 
>   The main difficulty with that is it's hard to distinguish between
> different sets of nested TLV's.  Requiring them to be grouped would
> help.
> 
>   e.g.  An "encapsulating tlv" has sub-tlv's A, B, and C.  What do you
> do if you want to send *two* copies of "encapsulating tlv", each with
> different values for A, B, and C?
> 
>   My guess would to use tags.  The sub-tlv's can be referred to as
> "A:1", which would mean "A, encapsulated in it's TLV, which is
> encapsulated in Extended-Attribute, which is encapsulated in
> Vendor-Specific."
> 
>   Ugh.  But it works:
> 
>    A:1 = foo
>    B:1 = 1
>    C:1 = 1.2.3.4
>    A:2 = bar
>    B:2 = 42
>    C:2 = 192.168.0.1
> 
>   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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 09:06:34 +0000
Message-ID: <48B518C2.6020609@deployingradius.com>
Date: Wed, 27 Aug 2008 11:05:06 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> Maybe I didn't say it correctly.  I want to name a group of TLVs, I guess.
> to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only using
> the TLV construct,

  Isn't that what the tags are for?

  Foo:1 = 1
  Bar:1 = "hello"
  BaZ:1 = "foo"

  It's not a nice name, but it's a name.

>>   So... what's a "named, multi-TLV attribute"?  An attribute inside of
>> the Extended-Attribute that can carry other TLV's?  Like what's done in
>> WiMAX?
> 
> Maybe, I'm open; that's why I asked :-).

  The main difficulty with that is it's hard to distinguish between
different sets of nested TLV's.  Requiring them to be grouped would help.

  e.g.  An "encapsulating tlv" has sub-tlv's A, B, and C.  What do you
do if you want to send *two* copies of "encapsulating tlv", each with
different values for A, B, and C?

  My guess would to use tags.  The sub-tlv's can be referred to as
"A:1", which would mean "A, encapsulated in it's TLV, which is
encapsulated in Extended-Attribute, which is encapsulated in
Vendor-Specific."

  Ugh.  But it works:

   A:1 = foo
   B:1 = 1
   C:1 = 1.2.3.4
   A:2 = bar
   B:2 = 42
   C:2 = 192.168.0.1

  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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 08:56:29 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 15:54:24 +0700
Message-ID: <004c01c90822$8f7612c0$ae623840$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckIIPpq+TrwNZ4XQVK5o8XZY05cpAAAQT1w
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Alan DeKok [mailto:aland@deployingradius.com] writes:
> >
> >> Glen Zorn wrote:
> >>> OK, so I've run into a situation when working on a set of
> attributes
> >> for
> >>> WiMAX that just begs for a named, multi-TLV attribute.
> >>   Could you be more specific?
> >
> > About what?
> 
>   A named, multi-TLV attribute.

Maybe I didn't say it correctly.  I want to name a group of TLVs, I guess.
to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only using
the TLV construct,

> 
>   Most attributes have names.  Most attributes are TLV's.  The
> Extended-Attribute encapsulates multiple TLV's.
> 
>   So... what's a "named, multi-TLV attribute"?  An attribute inside of
> the Extended-Attribute that can carry other TLV's?  Like what's done in
> WiMAX?

Maybe, I'm open; that's why I asked :-).

> 
>   It's a good idea.  And if most vendors have to add WiMAX support
> anyways, much of the code will already exist.
> 
>   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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 08:43:48 +0000
Message-ID: <48B51378.2040100@deployingradius.com>
Date: Wed, 27 Aug 2008 10:42:32 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> Alan DeKok [mailto:aland@deployingradius.com] writes:
> 
>> Glen Zorn wrote:
>>> OK, so I've run into a situation when working on a set of attributes
>> for
>>> WiMAX that just begs for a named, multi-TLV attribute.
>>   Could you be more specific?
> 
> About what?

  A named, multi-TLV attribute.

  Most attributes have names.  Most attributes are TLV's.  The
Extended-Attribute encapsulates multiple TLV's.

  So... what's a "named, multi-TLV attribute"?  An attribute inside of
the Extended-Attribute that can carry other TLV's?  Like what's done in
WiMAX?

  It's a good idea.  And if most vendors have to add WiMAX support
anyways, much of the code will already exist.

  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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 08:41:03 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'Bernard Aboba'" <aboba@internaut.com>, <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 15:38:35 +0700
Message-ID: <004701c90820$5ce75550$16b5fff0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckIDhh6WfRmsmu0RoeEv0Qgug3zOAAEeP8A
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > OK, so I've run into a situation when working on a set of attributes
> for
> > WiMAX that just begs for a named, multi-TLV attribute.
> 
>   Could you be more specific?

About what?

> 
> >  I guess it does seem
> > that the extended attributes should be able to handle this situation,
> fixing
> > one of the inadequacies (IMHO) of legacy RADIUS attributes, but right
> now
> > they can't.  Any suggestions for fixing this problem (as painlessly
> as
> > possible :-)?
> 
>   Painlessly killing RADIUS has been off of the table for a while.

Who's talking about "killing RADIUS"?  Do we have differing definitions of a
"dead" protocol?

> We're stuck with painful solutions.
> 
>   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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 06:29:05 +0000
Message-ID: <48B4F3CA.7020901@deployingradius.com>
Date: Wed, 27 Aug 2008 08:27:22 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'Bernard Aboba' <aboba@internaut.com>, radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> OK, so I've run into a situation when working on a set of attributes for
> WiMAX that just begs for a named, multi-TLV attribute.

  Could you be more specific?

>  I guess it does seem
> that the extended attributes should be able to handle this situation, fixing
> one of the inadequacies (IMHO) of legacy RADIUS attributes, but right now
> they can't.  Any suggestions for fixing this problem (as painlessly as
> possible :-)? 

  Painlessly killing RADIUS has been off of the table for a while.
We're stuck with painful solutions.

  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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 04:23:59 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Wed, 27 Aug 2008 11:21:51 +0700
Message-ID: <003a01c907fc$7c437b00$74ca7100$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9tI9KOI7i58ewR6q8qn9+WmSnywASr9SQAiWv2KA=
Content-Language: en-us

Bernard Aboba <mailto://aboba@internaut.com> writes:

...

> Looking at RFC 3588, it does seem
> that the agbility to name and define a Grouped AVP has some
> advantages.

OK, so I've run into a situation when working on a set of attributes for
WiMAX that just begs for a named, multi-TLV attribute.  I guess it does seem
that the extended attributes should be able to handle this situation, fixing
one of the inadequacies (IMHO) of legacy RADIUS attributes, but right now
they can't.  Any suggestions for fixing this problem (as painlessly as
possible :-)? 

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 03:31:14 +0000
Message-ID: <BLU137-DAV102684279E36078ECA28393610@phx.gbl>
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Revised Last look: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:31:02 -0700
Message-ID: <002401c907f5$546cacc0$fd460640$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQAACM4PAAAF3v0A==
Content-Language: en-us

The RADIUS Design Guidelines has recently been revised to reflect
the issues filed in RADEXT WG last call, and a draft PROTO writeup
has been submitted for WG inspection.  

The new document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-05.txt

The PROTO writeup is available here:
http://ops.ietf.org/lists/radiusext/2008/msg00522.html

If you filed an issue in RADEXT WG last call, please examine the
latest revision in order to determine whether the issue was resolved
to your satisfaction. 

Also, if you have not yet read the document, please do so. 

If you have comments on either the document or the PROTO writeup (see
previous message), please post them to the RADEXT WG mailing list
(radiusext@ops.ietf.org).  Document issues should be encapsulated 
in the format described in the RADEXT Issues List 
(http://www.drizzle.com/~aboba/RADEXT)

This "last look" will complete on September 7, 2008. 


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 03:30:27 +0000
Message-ID: <BLU137-DAV10E073B7D97BF62514814593610@phx.gbl>
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Revised PROTO: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:30:12 -0700
Message-ID: <002301c907f5$36f46ca0$a4dd45e0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQAADknLA=
Content-Language: en-us

Title:  RADIUS Design Guidelines
I-D:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-05.txt
 
Status: Best Current Practice
 
Response to template:
 
1) Have the chairs personally reviewed this version of the ID and do
   they believe this ID is sufficiently baked to forward to the IESG
   for publication?
 
Yes.
 
2) Has the document had adequate review from both key WG members and
   key non-WG members? Do you have any concerns about the depth or
   breadth of the reviews that have been performed?
 
Yes. The ID has had 2 working group last calls.
 
3) Do you have concerns that the document needs more review from a
   particular (broader) perspective (e.g., security, operational
   complexity, someone familiar with AAA, etc.)?
 
No concerns.  
 
4) Do you have any specific concerns/issues with this document that
   you believe the ADs and/or IESG should be aware of? For example,
   perhaps you are uncomfortable with certain parts of the document,
   or whether there really is a need for it, etc., but at the same
   time these issues have been discussed in the WG and the WG has
   indicated it wishes to advance the document anyway.
 
No.
 
5) How solid is the WG consensus behind this document?  Does it
   represent the strong concurrence of a few individuals, with others
   being silent, or does the WG as a whole understand and agree with
   it?
 
There is solid consensus behind this document.  The overall approach
to the document has been extensively discussed, both in IETF meetings
and on the mailing list.  Over a dozen people have commented on various
aspects of the document during its development.  The issues raised in
WG last call, available for inspection at 
http://www.drizzle.com/~aboba/RADEXT/, were resolved in the -05
version of the document.
 
6) Has anyone threatened an appeal or otherwise indicated extreme
   discontent?  If so, please summarize what are they upset about.
 
No.
 
7) Have the chairs verified that the document adheres to _all_ of the
   ID nits?  (see http://www.ietf.org/ID-nits.html).
 
Yes. An output of the run on this revision of the ID by the online nits
checker:
 
idnits 2.08.10 

tmp/draft-ietf-radext-design-05.txt:

  Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ID-Checklist.html:
 
----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking references for intended status: Best Current Practice
 
----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  -- Looks like a reference, but probably isn't: '8' on line 1431
     'The Text field consists of UTF-8 encoded 10646 [8] characters....'


     Summary: 0 errors (**), 0 warnings (==), 1 comment (--).


8) Does the document a) split references into normative/informative,
   and b) are there normative references to IDs, where the IDs are not
   also ready for advancement or are otherwise in an unclear state?
   (Note: the RFC editor will not publish an RFC with normative
   references to IDs, it will delay publication until all such IDs are
   also ready for publication as RFCs.)
 
The document does split references into normative and informative ones.
There are no normative references to IDs.
 
9) For Standards Track and BCP documents, the IESG approval
   announcement includes a writeup section with the following
   sections:
 
   - Technical Summary
 
   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). 
 
   - Working Group Summary
 
    There have been 2 WGLCs on the document.  Much of the discussion on
    the document has centered around the design guidelines 
    surrounding complex attributes, as well as the relationship of the
    RADIUS Vendor-Specific Attribute (VSA) and the Standard attribute
    space.  There was also considerable discussion relating to the
    process for review of RADIUS attributes specified by SDOs.  
    Ultimately, a consensus developed behind a model similar to that
    described in [RFC4663]. 


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 03:27:14 +0000
Message-ID: <BLU137-DAV746AB4419DBEEE3422F6193610@phx.gbl>
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Last look: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:26:44 -0700
Message-ID: <002201c907f4$bad33bb0$3079b310$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQAACM4PA=
Content-Language: en-us

The RADIUS Design Guidelines has recently been revised to reflect
the issues filed in RADEXT WG last call, and a draft PROTO writeup
has been submitted for WG inspection.  

The new document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-06.txt

The PROTO writeup is available here:
http://ops.ietf.org/lists/radiusext/2008/msg00520.html

If you filed an issue in RADEXT WG last call, please examine the
latest revision in order to determine whether the issue was resolved
to your satisfaction. 

Also, if you have not yet read the document, please do so. 

If you have comments on either the document or the PROTO writeup (see
previous message), please post them to the RADEXT WG mailing list
(radiusext@ops.ietf.org).  Document issues should be encapsulated 
in the format described in the RADEXT Issues List 
(http://www.drizzle.com/~aboba/RADEXT)

This "last look" will complete on September 7, 2008. 


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Wed, 27 Aug 2008 03:07:41 +0000
Message-ID: <BLU137-DAV16129148B46F358F280B793610@phx.gbl>
From: "Bernard Aboba" <Bernard_Aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: PROTO: RADIUS Design Guidelines
Date: Tue, 26 Aug 2008 20:06:26 -0700
Message-ID: <002101c907f1$e4ba09c0$ae2e1d40$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjk7kkcm5XO9/UrTbWQQ1Jbywbt2AjA0YZQ
Content-Language: en-us

Title:  RADIUS Design Guidelines
I-D:
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-06.txt
 
Status: Best Current Practice
 
Response to template:
 
1) Have the chairs personally reviewed this version of the ID and do
   they believe this ID is sufficiently baked to forward to the IESG
   for publication?
 
Yes.
 
2) Has the document had adequate review from both key WG members and
   key non-WG members? Do you have any concerns about the depth or
   breadth of the reviews that have been performed?
 
Yes. The ID has had 2 working group last calls.
 
3) Do you have concerns that the document needs more review from a
   particular (broader) perspective (e.g., security, operational
   complexity, someone familiar with AAA, etc.)?
 
No concerns.  
 
4) Do you have any specific concerns/issues with this document that
   you believe the ADs and/or IESG should be aware of? For example,
   perhaps you are uncomfortable with certain parts of the document,
   or whether there really is a need for it, etc., but at the same
   time these issues have been discussed in the WG and the WG has
   indicated it wishes to advance the document anyway.
 
No.
 
5) How solid is the WG consensus behind this document?  Does it
   represent the strong concurrence of a few individuals, with others
   being silent, or does the WG as a whole understand and agree with
   it?
 
There is solid consensus behind this document.  The overall approach
to the document has been extensively discussed, both in IETF meetings
and on the mailing list.  Over a dozen people have commented on various
aspects of the document during its development.  The issues raised in
WG last call, available for inspection at 
http://www.drizzle.com/~aboba/RADEXT/, were resolved in the -06
version of the document.
 
6) Has anyone threatened an appeal or otherwise indicated extreme
   discontent?  If so, please summarize what are they upset about.
 
No.
 
7) Have the chairs verified that the document adheres to _all_ of the
   ID nits?  (see http://www.ietf.org/ID-nits.html).
 
Yes. An output of the run on this revision of the ID by the online nits
checker:
 
idnits 2.08.10 

tmp/draft-ietf-radext-design-05.txt:

  Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ID-Checklist.html:
 
----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
 
----------------------------------------------------------------------------

     No issues found here.

  Checking references for intended status: Best Current Practice
 
----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  -- Looks like a reference, but probably isn't: '8' on line 1431
     'The Text field consists of UTF-8 encoded 10646 [8] characters....'


     Summary: 0 errors (**), 0 warnings (==), 1 comment (--).


8) Does the document a) split references into normative/informative,
   and b) are there normative references to IDs, where the IDs are not
   also ready for advancement or are otherwise in an unclear state?
   (Note: the RFC editor will not publish an RFC with normative
   references to IDs, it will delay publication until all such IDs are
   also ready for publication as RFCs.)
 
The document does split references into normative and informative ones.
There are no normative references to IDs.
 
9) For Standards Track and BCP documents, the IESG approval
   announcement includes a writeup section with the following
   sections:
 
   - Technical Summary
 
   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). 
 
   - Working Group Summary
 
    There have been 2 WGLCs on the document.  Much of the discussion on
    the document has centered around the design guidelines 
    surrounding complex attributes, as well as the relationship of the
    RADIUS Vendor-Specific Attribute (VSA) and the Standard attribute
    space.  There was also considerable discussion relating to the
    process for review of RADIUS attributes specified by SDOs.  
    Ultimately, a consensus developed behind a model similar to that
    described in [RFC4663]. 


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Tue, 26 Aug 2008 15:30:29 +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-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080826153001.7F8A83A6B7F@core3.amsl.com>
Date: Tue, 26 Aug 2008 08:30:01 -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, et al.
	Filename        : draft-ietf-radext-design-05.txt
	Pages           : 36
	Date            : 2008-08-26

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-05.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-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2008-08-26082119.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-data@psg.com
Delivery-date: Tue, 26 Aug 2008 15:22:03 +0000
Message-ID: <48B41F2D.40909@deployingradius.com>
Date: Tue, 26 Aug 2008 17:20:13 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: Comment on draft-ietf-radext-design-04.txt, Appendix A
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> There are a few cases where the text in Appendix A is not backed by 
> discussion in the rest of the document, and vice versa.  
...

  I've updated the document as suggested, with some minor word smithing.
 It should show up soon as an announcement.

  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-data@psg.com
Delivery-date: Mon, 25 Aug 2008 21:58:27 +0000
Message-ID: <48B32AB4.9050409@deployingradius.com>
Date: Mon, 25 Aug 2008 23:57:08 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-radext-status-server-01.txt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the RADIUS EXTensions Working Group of the IETF.
> 
> 	Title		: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol

  The changes from -00 reflect the discussion at the WG meeting in
Dublin.  Text on using the CoA port has been added.

  I don't think there's much else to do with the document at this point.

  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-data@psg.com
Delivery-date: Mon, 25 Aug 2008 21:15:41 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D ACTION:draft-ietf-radext-status-server-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080825211501.CDF2428C111@core3.amsl.com>
Date: Mon, 25 Aug 2008 14:15:01 -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		: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
	Author(s)	: A. DeKok
	Filename	: draft-ietf-radext-status-server-01.txt
	Pages		: 28
	Date		: 2008-8-25
	
RFC 2865 defines a Status-Server code for use in RADIUS, but labels
   it as "Experimental" without further discussion.  This document
   describes a practical use for the Status-Server packet code, which is
   to let clients query the status of a RADIUS server.  These queries,
   and responses (if any) enable the client to make more informed
   decisions.  The result is a more stable, and more robust RADIUS
   architecture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-status-server-01.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-status-server-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2008-8-25140857.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-data@psg.com
Delivery-date: Fri, 22 Aug 2008 15:44:38 +0000
Message-ID: <48AEDEC9.3060806@restena.lu>
Date: Fri, 22 Aug 2008 17:44:09 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: I-D Action:draft-ietf-radext-radsec-01.txt
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

this version reflects the discussions from IETF-72.

* normative section in the beginning, informative afterwards with 
explanations
* forbid integrity-only ciphers
* fixed shared "secret" ["radsec" for now, as I don't quite remember 
what we settled for, if anything]

Most of it is text re-shuffling, two notable changes:

* previous versions left CoA and Disconnect unspecified. The current 
draft includes it, the basic rationale being that to implement RadSec, 
new code is necessary anyways and the burden of at least answering to a 
Req with a NAK can be demanded IMO.
* one of the SHOULD ciphers which is based on MD5 is gone. It felt a bit 
awkward to complain about RADIUS' MD5 usage and then recommend a MD5 
based cipher.

If you have comments, I'll be happy to ignore them for the next two 
weeks, since I'll be at a completely-offline vacation. I'll get back to 
IETF business after that.

Greetings,

Stefan Winter

Internet-Drafts@ietf.org schrieb:
> 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           : TLS encryption for RADIUS over TCP (RadSec)
> 	Author(s)       : S. Winter, et al.
> 	Filename        : draft-ietf-radext-radsec-01.txt
> 	Pages           : 17
> 	Date            : 2008-08-22
>
> This document specifies security on the transport layer (TLS) for the
> RADIUS protocol [RFC2865] when transmitted over TCP
> [I-D.dekok-radext-tcp-transport].  This enables dynamic trust
> relationships between RADIUS servers.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-01.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.
>   


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 22 Aug 2008 14:31:05 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-radsec-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080822143001.BA4C63A697D@core3.amsl.com>
Date: Fri, 22 Aug 2008 07:30:01 -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           : TLS encryption for RADIUS over TCP (RadSec)
	Author(s)       : S. Winter, et al.
	Filename        : draft-ietf-radext-radsec-01.txt
	Pages           : 17
	Date            : 2008-08-22

This document specifies security on the transport layer (TLS) for the
RADIUS protocol [RFC2865] when transmitted over TCP
[I-D.dekok-radext-tcp-transport].  This enables dynamic trust
relationships between RADIUS servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-radsec-01.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-radsec-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2008-08-22071555.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-data@psg.com
Delivery-date: Mon, 18 Aug 2008 21:21:45 +0000
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Mon, 18 Aug 2008 17:21:21 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <7215774374A94535A323C71758E60AA7@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDAAEn0hlAAntbhEAAAuMDQ

Joseph Salowey writes...

> [Joe] There is some confusion.

I think an example packet exchange, showing how the client and server
"negotiate" the algorithm they will mutually use would be helpful.

> [Joe] I'll try to provide some text by the end of the week.

Thanks.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Mon, 18 Aug 2008 21:06:23 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Mon, 18 Aug 2008 14:05:48 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5065CB35C@xmb-sjc-225.amer.cisco.com>
Thread-Topic: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
thread-index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDAAEn0hlAAntbhEA==
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "David B. Nelson" <dnelson@elbrysnetworks.com>, <radiusext@ops.ietf.org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1918; t=1219093528; x=1219957528; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jsalowey@cisco.com; z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci sco.com> |Subject:=20RE=3A=20REMINDER=3A=20RADEXT=20WG=20Last=20Call =20on=20=22Crypto-Agility=20Requirements=20for=20RADIUS=22 |Sender:=20; bh=7Nw0/IbThR7Gi8opomxnHmv/p845j+NJswyX6KpHO00=; b=hNVTKzTF996+UrRHG1HB2fsA5kXgzb1OrBcQy7+b2blGeph3uMhLU0r8G+ CPAWhJeYPfnhQ1NdCD7cqXHjv4Fl4F5BOtKmGq/72FkbuzYwdNNYOoSloj83 z/xoziHyBc;
Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );

=20

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of David B. Nelson
> Sent: Friday, August 15, 2008 10:17 AM
> To: radiusext@ops.ietf.org
> Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility=20
> Requirements for RADIUS"
>=20
> Joseph Salowey writes...
>=20
> > 1. Section 4.2:
> >=20
> > In cases where the client needs to protect all or part of=20
> the radius=20
> > request the "hint and select" negotiation the client would provide=20
> > more than a hint when it chooses the algorithms for protection.
> > Perhaps hint and select is not quite the right term, may be specify=20
> > and select?
>=20
> While adding a more robust form of capabilities negotiation=20
> to RADIUS might be a useful thing, it's not a charted work=20
> item.  I think we are stuck with the current "hint and=20
> select" paradigm that is common usage in RADIUS today.
>=20
> Perhaps I've misunderstood your comment.  Could you give an example?
>=20
[Joe] There is some confusion.  I don't want to change the behavior, I
just think the term "hint and select" is a bit misleading since the
client will have to select some algorithm to protect its messages.  This
is a bit more than a "hint".  The client can "hint to the server what it
supports. =20

> > 2. Section 4.6:
> >=20
> > Section 4.6 makes reference to security considerations text=20
> about key=20
> > management.  Shouldn't this text be in this document?
>=20
> Yes, I think so.  Would anyone like to propose some text and=20
> a citation into RFC 4017?
>=20
[Joe] I'll try to provide some text by the end of the week. =20

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


Envelope-to: radiusext-data@psg.com
Delivery-date: Sun, 17 Aug 2008 10:13:29 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Sun, 17 Aug 2008 17:11:37 +0700
Message-ID: <005101c90051$a940b170$fbc21450$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcAAAWPE8AAp9nlQACan50A=
Content-Language: en-us

David B. Nelson <mailto://d.b.nelson@comcast.net> writes: 

> 
> Glen Zorn writes...
> 
> > What documents?
> 
> Those defining the cipher suites to be used.  Surely we're not going to
> attempt to define them within a RADIUS document?

Define what?  Whether the algorithm is mandatory to implement for use in
RADIUS?  I sincerely hope so!

> 
> > Since an Experimental RFC holds no standing as a standard, how can it
> > specify _anything_ as mandatory?
> 
> Sorry to be repetitive, buy why not?
> 
> > The last time I checked (please correct me if I'm wrong), the "hint"
> was
> > from a NAS to a server regarding what the NAS wanted returned.  In
> many
> > cases, these "hints" would not be anything of the sort; instead, they
> will
> > be a simple statement of the algorithm used by the NAS.
> 
> How is that not a hint?  

Some definitions of "hint":

an indirect suggestion
a slight indication
a clue

What about any of those suggests a declarative statement?

...

> > The only way that I can think of for the server to refuse the
> > "hint" would be if we were to hi-jack the Access-Challenge message,
> > which in itself constitutes a novel negotiation method for RADIUS.
> 
> Well, yes.  We discussed that briefly during an ill-fated attempt to
> add
> generic capabilities negotiation to RADIUS.  So, yes there is no "NAK"
> and
> counter-proposal capability, simply offer and accept or offer and
> reject.  I
> fail to see why that would not allow a rudimentary form of crypto-
> agility.
> The way a server refuses the hint by means of an Access-Reject message.

And the client knows that this is a refusal of this particular hint (instead
of the multiple other conditions that might elicit an Access-Reject how,
exactly?  Parsing the Reply-Message Attribute that may or may not be
present?

...

> 
> > > > Given that this is new and presumably desirable functionality,
> > > > why is a simple upgrade path not sufficient?
> > >
> > > A "fork-lift" upgrade?  :-)
> >
> > Hardly. New messages and or capabilities can fairly easily be
> introduced
> > in a piece-meal fashion, as long as it is done with care.
> 
> Well _that_ sounds a bit like "and a miracle occurs here".  

I guess miracles really do happen every day then ;-): support for EAP,
dynamic authorization, 802.11...

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 17 Aug 2008 09:47:57 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: <gdweber@gmail.com>
Cc: <radiusext@ops.ietf.org>
Subject: Issue 250
Date: Sun, 17 Aug 2008 16:30:25 +0700
Message-ID: <005001c9004b$e82b2a60$b8817f20$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckAS9S6yurFrCN3Q5qq1JZcS1a6XA==
Content-Language: en-us

"In section 5, the Ext-Length field is defined as the length of the Extended
Attribute.  I think you mean it's the length of the TLV (multiple TLVs can
be
in the Extended Attribute).  I think that would make the value ">=3", not
">=4"."

That being the case, maybe it would be more descriptive to make the names of
the fields to "TLV-type" & "TLV-Length"?


"It's probably worth calling out any artifacts of overloading attribute 26
which wouldn't apply to standard attributes in the original number space
(or apply to overloading a new attribute instead of 26)."  

Of course, since it's only the format that needs to be inherited from VSAs,
the overall Type can be changed...


"For example, attribute 26 is already specifically excluded from some RADIUS
message
types, e.g. CoA-NAK,"

Just out of curiosity, does anyone know why that is so?  


"so new Extended Attributes couldn't be included in
those messages, but new standard attribute could be."  

Extended Attributes could be legalized for those messages in the exactly the
same way as for new "standard" attributes: through an updating RFC.


"Also, are malformed VSAs always treated just like malformed non-VSAs?"

Don't the rules defined in RFC 2865 apply to all attributes?


"I think it would be useful to explicitly mention if recursive grouping is
allowed and that Extended Attributes cannot be grouped with non-Extended
Attributes."

I have no idea how recursive grouping could be done with this scheme, but if
it could I don't know why you would want to outlaw it; one of the benefits
of the (apparently confusing) sanctioning of Ext-Types 0-256 is that it
makes it impossible to encapsulate legacy attributes in Extended Attributes
(although the legacy attribute space _could_ be duplicated in the first 257
slots, possibly a decent idea...


"It's probably useful to mention what happens when an Extended Attribute's
tag is non-zero and it contains multiple TLVs (this does not seem to be
excluded -as multiple TLVs are when the M-bit is on)."

I thought that that was obvious...what is unclear?






--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 17 Aug 2008 07:35:51 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>, "'Alan DeKok'" <aland@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sun, 17 Aug 2008 14:34:40 +0700
Message-ID: <004d01c9003b$bddbaa10$3992fe30$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/rDWssMK/BbPQTCeqzMwkBEb8TQAdznfAAAXpGWA=
Content-Language: en-us

David B. Nelson <mailto://d.b.nelson@comcast.net> writes:

> >   See RFC 3579 Section 3.1:
> >
> >       If multiple
> >       EAP-Message attributes are contained within an Access-Request
> or
> >       Access-Challenge packet, they MUST be in order and they MUST be
> >       consecutive attributes in the Access-Request or Access-
> Challenge
> >       packet.
> 
> Damn.  When did that sneak in there?  :-)

Well, let's see, it was in 2869, so about 10 years ago :-)

> 
> 
> 
> --
> to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 17 Aug 2008 07:29:17 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: "'Greg Weber'" <gdweber@gmail.com>, "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sun, 17 Aug 2008 14:27:13 +0700
Message-ID: <004c01c9003a$b71268f0$25373ad0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/wwLBeFHtTgSyRLa72dQjisishAAc5EcQ
Content-Language: en-us

Bernard Aboba [mailto:aboba@internaut.com] writes:

...

> > Be that as it may, the link points to an issue raised by Bernard re:
> the
> > Fixes draft.
> 
> On Mozilla, the link does point to Issue 250.  
> What browser were you
> using?

IE 7.0.6.  Investigating further w/Opera & Safari, it appears that IE is not
handling references to internal points in the HTML file correctly: it just
opens radissues2.html & quits, leaving the pointer at the beginning (issue
#200).  Opera & Safari position the pointer correctly (after a (long) while
;-). 

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 17 Aug 2008 04:43:06 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sun, 17 Aug 2008 00:42:04 -0400
Message-ID: <001c01c90023$9a223c00$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/rDWssMK/BbPQTCeqzMwkBEb8TQAdznfA

>   See RFC 3579 Section 3.1:
> 
>       If multiple
>       EAP-Message attributes are contained within an Access-Request or
>       Access-Challenge packet, they MUST be in order and they MUST be
>       consecutive attributes in the Access-Request or Access-Challenge
>       packet.

Damn.  When did that sneak in there?  :-)



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 17:11:11 +0000
Date: Sat, 16 Aug 2008 10:10:37 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: Glen Zorn <glenzorn@comcast.net>
cc: 'Greg Weber' <gdweber@gmail.com>,  'Hannes Tschofenig' <Hannes.Tschofenig@gmx.net>, radiusext@ops.ietf.org
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Message-ID: <Pine.LNX.4.64.0808161003250.26442@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> 1) As you know, the issues list is not an official WG document, but a tool
> for the use of the Chairs & as such its state has no bearing on the status
> of a document.
> 2) All 3 of the issues assigned to the extended attributes document appear
> to actually refer to RFC 5080.

Issues 225, 250 and 251 all refer to the Extended Attributes document. 

> I suspect Hannes was referring to the open issues section in the draft's
> text, not the list maintained by the chairs.  Regarding the latter, the 
> issue that I filed (#250) was intended for your -00 draft, not RFC 5080.  
> 
> Be that as it may, the link points to an issue raised by Bernard re: the
> Fixes draft.

On Mozilla, the link does point to Issue 250.  What browser were you 
using? 

> I haven't read your current draft version yet to see if these comments were addressed;
> there was no response on the list -that I recall.  

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 14:27:46 +0000
Message-ID: <48A6E39C.5090604@deployingradius.com>
Date: Sat, 16 Aug 2008 16:26:36 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "David B. Nelson" <d.b.nelson@comcast.net>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David B. Nelson wrote:
> Glen Zorn writes...
>> ...   Any Extended
>> 	 Attributes containing multiple fragments of the same value MUST be
>> 	 in order and MUST be consecutive attributes in the packet.
> 
> It's the last sentence that I claim adds new requirements to RADIUS.  This
> is not required for EAP-Message Attributes,

  Nope.  See RFC 3579 Section 3.1:

       If multiple
      EAP-Message attributes are contained within an Access-Request or
      Access-Challenge packet, they MUST be in order and they MUST be
      consecutive attributes in the Access-Request or Access-Challenge
      packet.

  MUST be consecutive attributes would seem pretty clear.

> nor any others that I'm aware
> of.  I'm stopping short of claiming that this new requirement isn't backward
> compatible.  I can easily envision implementations where this would not be
> any sort of burden to enforce.  I'm just wondering if there are any
> implementations where it would be a burden?  I also see the advantage in
> terms of ease of implementation of parsing and reconstruction.

  It's a PITA to root through the packet, looking for the next attribute
which *might* be the same... and which isn't consecutive.  I've done
this for the previous version of the Extended-Attributes.  It's awkward.
 It's much easier just to check: Next attribute is the same?  Nope?
Dump the packet as malformed.

  It makes for less code, and fewer chances for programming errors.

  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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 14:15:52 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 10:15:45 -0400
Message-ID: <000301c8ffaa$93ad23e0$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/Z2dOQPRiYtQdTHiffyMYG1DQ9wAHyjLwAAgjzUAAANQ0sA==

Clarifying...

> > 	 Attributes containing multiple fragments of the same value MUST be
> > 	 in order and MUST be consecutive attributes in the packet.
> 
> It's the last sentence that I claim adds new requirements to RADIUS

I'm talking about the second MUST in that sentence.


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 14:13:43 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Sat, 16 Aug 2008 10:13:26 -0400
Message-ID: <000201c8ffaa$414abf40$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcAAAWPE8AAp9nlQ

Glen Zorn writes...

> What documents?

Those defining the cipher suites to be used.  Surely we're not going to
attempt to define them within a RADIUS document?

> Since an Experimental RFC holds no standing as a standard, how can it
> specify _anything_ as mandatory?

Sorry to be repetitive, buy why not?

> The last time I checked (please correct me if I'm wrong), the "hint" was
> from a NAS to a server regarding what the NAS wanted returned.  In many
> cases, these "hints" would not be anything of the sort; instead, they will
> be a simple statement of the algorithm used by the NAS.

How is that not a hint?  Sorry, but I simply don't see where you're going
with this.

> Examples are the User-Password Attribute & request
> authentication/integrity protection.

Eh?

> The only way that I can think of for the server to refuse the
> "hint" would be if we were to hi-jack the Access-Challenge message,
> which in itself constitutes a novel negotiation method for RADIUS.

Well, yes.  We discussed that briefly during an ill-fated attempt to add
generic capabilities negotiation to RADIUS.  So, yes there is no "NAK" and
counter-proposal capability, simply offer and accept or offer and reject.  I
fail to see why that would not allow a rudimentary form of crypto-agility.
The way a server refuses the hint by means of an Access-Reject message.

> > Therefore, it's reasonable to say that "Just use IPSec."
> > is out of scope for RADIUS crypto-agility.
> 
> The text to which I was referring is "Therefore, it is expected that
> proposals will utilize other techniques".

Well, if "Just use IPSec" is out of scope, doesn't it follow that "proposals
will use other methods" [besides IPSec)?  Again, I simply don't see where
you're going with this.

> > > I would _really_ like to see some rationale for this requirement
> > > (aside from "backward compatibility is sacred and must never be
> > > questioned" ;-).
> >
> > Given that the RADIUS protocol doesn't have a protocol version field,
> > maintaining backward compatibility seems pretty basic.
> 
> OK, so that sounds an awful lot like " backward compatibility is sacred
> and must never be questioned" to me.

If you say so...

> > > Given that this is new and presumably desirable functionality,
> > > why is a simple upgrade path not sufficient?
> >
> > A "fork-lift" upgrade?  :-)
> 
> Hardly. New messages and or capabilities can fairly easily be introduced
> in a piece-meal fashion, as long as it is done with care.

Well _that_ sounds a bit like "and a miracle occurs here".  That which is a
simple upgrade path to some is a deployment nightmare to others.  We need to
be a bit more specific, I think.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 13:59:13 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 09:59:03 -0400
Message-ID: <000101c8ffa8$3ed69ce0$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/Z2dOQPRiYtQdTHiffyMYG1DQ9wAHyjLwAAgjzUA=

Glen Zorn writes...

>    M (More)
> 
>       The More Flag is one (1) bit in length and MUST be present.  When
>       a value to be transmitted exceeds 246 octets in length it is
>       fragmented over two or more Extended Attributes.  If the More Flag
>       is set (1), this indicates that the Value field of the Extended
>       Attribute contains a fragment of a larger value, which is
>       continued in the next Extended Attribute of the same Ext-Type.
>       When the More Flag is clear (0), the final (or only) fragment of
>       the value is contained in the Extended Attribute.  Any Extended
> 	 Attributes containing multiple fragments of the same value MUST be
> 	 in order and MUST be consecutive attributes in the packet.

It's the last sentence that I claim adds new requirements to RADIUS.  This
is not required for EAP-Message Attributes, nor any others that I'm aware
of.  I'm stopping short of claiming that this new requirement isn't backward
compatible.  I can easily envision implementations where this would not be
any sort of burden to enforce.  I'm just wondering if there are any
implementations where it would be a burden?  I also see the advantage in
terms of ease of implementation of parsing and reconstruction.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 13:51:34 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 09:50:42 -0400
Message-ID: <000001c8ffa7$14466c40$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/aA2acCMyYpedS4GdGJl/49uH/wAIMVsQAAdgn5A=

Glen Zorn writes...

> > > Actually, I'd just as soon discard the examples: this draft has
> > > way too much flavor of a tutorial for my taste...
> >
> >   Sure.
> 
> Great!  Anybody married to section 6?  If not, it's gone...

I think examples sections (in this or any other document) are
extraordinarily helpful.  They help the reader to understand the details,
and the help the author by bringing to light incongruities in the normative
text.  I wouldn't be so quick to dispense with that section.  That fact that
it is raising issues tells me it has value.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 10:26:17 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 17:25:06 +0700
Message-ID: <002401c8ff8a$61b7bbe0$252733a0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/aA2acCMyYpedS4GdGJl/49uH/wAIMVsQ
Content-Language: en-us

Alan DeKok <mailto://aland@deployingradius.com> writes:

> 
> Glen Zorn wrote:
> > OK, are you saying that the existing text isn't clear?  It seems
> pretty
> > precise to me, should it be more vague (e.g., "long" & "short")?
> 
>   I just wanted to be sure I understood it.

OK.

> 
> >>       Two (2) octets.  Up-to-date values of the Ext-Type field are
> >>       specified in the most recent "Assigned Numbers" [IANA].
> Values
> >>       XXXX-YYYY are reserved.
> >>
> >>   I would suggest reserving the top 1K: 64512-65535
> >
> > Rationale?
> 
>   Numbers are better than XXXX-YYYY. :)  As for using the top 1K rather
> than 256, or 32, or 4.... it's small enough that we likely won't need
> the attribute numbers later, and large enough it gives a lot of room to
> work with.
> 
>   I'd say 32 may be too small, and anything over 1K is likely too
> large.

OK.  Any other opinions?

> 
> > Actually, I'd just as soon discard the examples: this draft has way
> too much
> > flavor of a tutorial for my taste...
> 
>   Sure.

Great!  Anybody married to section 6?  If not, it's gone...


> 
> >>   The examples could also given broken-out hex encoding of the
> >> attributes, which may be clearer than the ASCII art diagrams.  e.g.
> >>
> >>   1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f
> >
> > You're joking, right?
> 
>   Other RFC's have hex examples...

Sure, but I thought that we were writing not with any expectation of a
reasonable level of shared knowledge but for the LCD...

> 
> >>   I suggest leaving the first 0..255 attributes as unallocated, in
> >> order
> >> to avoid confusion with legacy RADIUS attributes.
> >
> > Presumably the people who would get confused are those who have to be
> told
> > to protect against buffer overflows (& send "hello" as five separate
> > attributes), right?
> 
>   Yes.
> 
>   I should put up a web page listing all of the "creative"
> interpretation of the RFC's.  Some people have put a lot of effort into
> doing the most inventive things.

"There is no end to the folly of men..."

> 
>   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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 10:15:10 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'David B. Nelson'" <dnelson@elbrysnetworks.com>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 17:13:42 +0700
Message-ID: <002301c8ff88$cb8734d0$62959e70$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj/Z2dOQPRiYtQdTHiffyMYG1DQ9wAHyjLw
Content-Language: en-us

Alan DeKok <mailto://aland@deployingradius.com> writes:

> Glen Zorn wrote:
> > I believe that he meant that all fragments of a given attribute must
> be
> > contiguous in the original packet...
> 
>   RFC 3579, Section 3.1:
> 
>       If multiple
>       EAP-Message attributes are contained within an Access-Request or
>       Access-Challenge packet, they MUST be in order and they MUST be
>       consecutive attributes in the Access-Request or Access-Challenge
>       packet.
> 
>   Requiring this for Extended-Attribute is a good idea.

Alright, how about this?

   M (More)

      The More Flag is one (1) bit in length and MUST be present.  When
      a value to be transmitted exceeds 246 octets in length it is
      fragmented over two or more Extended Attributes.  If the More Flag
      is set (1), this indicates that the Value field of the Extended
      Attribute contains a fragment of a larger value, which is
      continued in the next Extended Attribute of the same Ext-Type.
      When the More Flag is clear (0), the final (or only) fragment of
      the value is contained in the Extended Attribute.  Any Extended 
	Attributes containing multiple fragments of the same value MUST be 
	in order and MUST be consecutive attributes in the packet.

> 
>   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/>



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 08:18:55 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>, <radiusext@ops.ietf.org>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Sat, 16 Aug 2008 15:17:03 +0700
Message-ID: <000101c8ff78$854b6b90$8fe242b0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcAAAWPE8A==
Content-Language: en-us

David B. Nelson <mailto://dnelson@elbrysnetworks.com> writes:

> Glen Zorn writes...
> 
> > The WG Charter states that all of the existing crypto-agility
> > proposals are to be published as Experimental RFCs.  In that case,
> > how can the requirement that " at least one mandatory to implement
> > algorithm will be defined" (section 1.2) be fulfilled?
> 
> Why not?  The algorithms are defined in existing documents.

What documents?  Since an Experimental RFC holds no standing as a standard,
how can it specify _anything_ as mandatory?

...

> > Technical comments:
> >
> > Section 2, paragraph 2 states:
> >
> >    In the specific context of the RADIUS protocol and RADIUS
> >    implementations, crypto-agility may be better defined as the
> ability
> >    of RADIUS implementations to negotiate cryptographic algorithms
> for
> >    use in RADIUS exchanges, including the cryptographic algorithms
> used
> >    to protect RADIUS packets and to hide RADIUS Attributes.  This
> >    capability covers all RADIUS message types: Access-
> Request/Response,
> >    Accounting-Request/Response, and CoA/Disconnect-Request/Response.
> >
> > Since RADIUS has no negotiation method of I'm aware (hint &
> > accept/ignore is hardly a negotiation mechanism)...
> 
> Yeah, but it's what we've got.
> 
> >... I find these statements very curious, especially in light of the
> > earlier statement (section 2, paragraph 3) that the password-hiding
> > function will be negotiable.  Basically, what is being called for is
> > impossible in the context of the RADIUS protocol, implying that the
> > negotiations would take place outside of RADIUS (e.g., in TLS).
> 
> That wasn't what I understood when I transcribed that text.  It's true
> that
> "hint and consent" is a bit crude, but I'd like to see a more in-depth
> technical exploration of why you think it makes crypto-agility
> impossible
> within RADIUS

The last time I checked (please correct me if I'm wrong), the "hint" was
from a NAS to a server regarding what the NAS wanted returned.  In many
cases, these "hints" would not be anything of the sort; instead, they will
be a simple statement of the algorithm used by the NAS.  Examples are the
User-Password Attribute & request authentication/integrity protection.  The
only way that I can think of for the server to refuse the "hint" would be if
we were to hi-jack the Access-Challenge message, which in itself constitutes
a novel negotiation method for RADIUS.

> 
> > Section 4.1:
> > Once again, assuming a solution.  State the requirements that a
> solution
> > must meet, not your personal assumptions about the form which the
> solution
> > will take.  I say "personal" because a fair subset of the active WG
> (of
> > which this document is purportedly a product) _does not_ share the
> > expectation that " proposals will utilize other techniques".
> 
> I take that text to means that RADIUS over IPSec has already been
> defined,
> and therefore proposing RADIUS over IPSec is not what we're looking for
> to
> address RADIUS crypto-agility.  After all, if an existing solution
> needs
> everyone's needs, why waste time on a requirements document, never mind
> a
> solution document?  Therefore, it's reasonable to say that "Just use
> IPSec."
> is out of scope for RADIUS crypto-agility.

The text to which I was referring is "Therefore, it is expected that
proposals will utilize other techniques".

> 
> > Section 4.2, paragraph 2 states:
> >
> >    Included in negotiation techniques are "hint and consent"
> mechanisms
> >    where the NAS provides a list of algorithms and the server selects
> >    one.
> >
> > If the server is required to select from the list it can hardly be
> > called a hint.  Once again, I can't see at all how this mechanism
> > could be made to work in the case of the Access-Request message.
> 
> Please explain.

See above.

> 
> > Section 4.3, paragraph 1 states:
> >
> >    Solutions to the problem MUST demonstrate backward compatibility
> >    with existing RADIUS implementations.
> >
> > I would _really_ like to see some rationale for this requirement
> > (aside from "backward compatibility is sacred and must never be
> > questioned" ;-).
> 
> Given that the RADIUS protocol doesn't have a protocol version field,
> maintaining backward compatibility seems pretty basic.

OK, so that sounds an awful lot like " backward compatibility is sacred and
must never be questioned" to me.  

> 
> > Given that this is new and presumably desirable functionality,
> > why is a simple upgrade path not sufficient?
> 
> A "fork-lift" upgrade?  :-)

Hardly. New messages and or capabilities can fairly easily be introduced in
a piece-meal fashion, as long as it is done with care.
 
> 
> 
> 
> --
> to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 16 Aug 2008 06:12:12 +0000
Message-ID: <48A66F52.3060302@deployingradius.com>
Date: Sat, 16 Aug 2008 08:10:26 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: "'David B. Nelson'" <dnelson@elbrysnetworks.com>,  radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
> I believe that he meant that all fragments of a given attribute must be
> contiguous in the original packet...

  RFC 3579, Section 3.1:

      If multiple
      EAP-Message attributes are contained within an Access-Request or
      Access-Challenge packet, they MUST be in order and they MUST be
      consecutive attributes in the Access-Request or Access-Challenge
      packet.

  Requiring this for Extended-Attribute is a good idea.

  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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 22:45:04 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8FF28.741696EA"
Subject: RE: Help me about RFC3576
Date: Fri, 15 Aug 2008 15:43:59 -0700
Message-ID: <D492339CC466C84EA5E0AF1CECB20081062E44F1@xmb-sjc-21b.amer.cisco.com>
Thread-Topic: Help me about RFC3576
Thread-Index: Acj/Ew2NPy5SzbNqRqGrplLecXBW0wAFRlPQ
From: "Murtaza Chiba (mchiba)" <mchiba@cisco.com>
To: <bhcuong2005@yahoo.com>, <radiusext@ops.ietf.org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3108; t=1218840259; x=1219704259; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mchiba@cisco.com; z=From:=20=22Murtaza=20Chiba=20(mchiba)=22=20<mchiba@cisco.c om> |Subject:=20RE=3A=20Help=20me=20about=20RFC3576 |Sender:=20; bh=NpHE7bgONOHnP5Z69N/gDyIdVA3mvEYiNSSIwT+S9/o=; b=sw1AweM29chMfgo715QSX5n3BuY45Fp4kLGkp0GQuU5iMeNFIzrprP9wbU C5z/677kuppR7Rz3hUuXdeqVrTnS4YY+pRjzLZvaHotCdXDv+PELOC+xNB22 oz7CnSvG09;
Authentication-Results: sj-dkim-3; header.From=mchiba@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8FF28.741696EA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
Included radius extensions WG.   Not sure what was decided in the bis
portion.
=20
Thanks,
-Murtaza


________________________________

	From: Cuong Hoang Bui [mailto:bhcuong2005@yahoo.com]=20
	Sent: Friday, August 15, 2008 1:11 PM
	To: Murtaza Chiba (mchiba)
	Subject: Help me about RFC3576
=09
=09
Dear Mr. Chiba,

I have a question related to CoA messages.
If both supported attribute(s) and unsupported attribute(s) are included
in CoA-Request message, then what happens? NAS doesn't process packets
and return CoA-NAK back to Radius server or it processes only supported
attributes, but should it send CoA-NAK or CoA-ACK back to RADIUS server?

Thank you

Regards
Cuong
=09



------_=_NextPart_001_01C8FF28.741696EA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16674" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578094222-15082008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Included radius extensions WG.&nbsp;&nbsp; Not =
sure what=20
was decided in the bis portion.</FONT></SPAN></DIV>
<DIV><SPAN class=3D578094222-15082008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D578094222-15082008><FONT face=3DArial color=3D#0000ff =

size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D578094222-15082008><FONT face=3DArial color=3D#0000ff =

size=3D2>-Murtaza</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><BR></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Cuong Hoang Bui=20
  [mailto:bhcuong2005@yahoo.com] <BR><B>Sent:</B> Friday, August 15, =
2008 1:11=20
  PM<BR><B>To:</B> Murtaza Chiba (mchiba)<BR><B>Subject:</B> Help me =
about=20
  RFC3576<BR></FONT><BR></DIV>
  <DIV></DIV>
  <TABLE cellSpacing=3D0 cellPadding=3D0 border=3D0>
    <TBODY>
    <TR>
      <TD vAlign=3Dtop>Dear Mr. Chiba,<BR><BR>I have a question related =
to CoA=20
        messages.<BR>If both supported attribute(s) and unsupported =
attribute(s)=20
        are included in CoA-Request message, then what happens? NAS =
doesn't=20
        process packets and return CoA-NAK back to Radius server or it =
processes=20
        only supported attributes, but should it send CoA-NAK or CoA-ACK =
back to=20
        RADIUS server?<BR><BR>Thank=20
  =
you<BR><BR>Regards<BR>Cuong<BR></TD></TR></TBODY></TABLE><BR></BLOCKQUOTE=
></BODY></HTML>

------_=_NextPart_001_01C8FF28.741696EA--

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 17:36:14 +0000
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
Subject: RE: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 15 Aug 2008 13:35:20 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <5E154780AF9E4987A71861EDFD3750C9@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48QABNxhcA=

Glen Zorn writes...

> The WG Charter states that all of the existing crypto-agility
> proposals are to be published as Experimental RFCs.  In that case,
> how can the requirement that " at least one mandatory to implement 
> algorithm will be defined" (section 1.2) be fulfilled?

Why not?  The algorithms are defined in existing documents.

> Front page header:
> Since the source of the document is stated in section 1.1 to be
> the radext WG, David's role should probably be "Editor".

Yes.

> Section 1.2:
> s/propose one of more Internet Drafts/propose one or more Internet-Drafts/
> 
> Section 2:
> s/Crypto-Agility is the ability for/Crypto-agility is the ability of/

OK.

> Section 4.5, paragraph 5 states:
> 
>    Editorial Note: With the expected acceptance of the proposed RADEXT
>    WG Charter revision, some of the issues raised in the preceding
>    paragraphs become moot, and this section ought to be revised to
>    reflect the revised charter.
> 
> Haven't those charter revisions already taken place?

As of submission of the -00 draft, the IESG was still deliberating the
re-charter request.  Will be fixed in -01.

> Technical comments:
> 
> Section 2, paragraph 2 states:
> 
>    In the specific context of the RADIUS protocol and RADIUS
>    implementations, crypto-agility may be better defined as the ability
>    of RADIUS implementations to negotiate cryptographic algorithms for
>    use in RADIUS exchanges, including the cryptographic algorithms used
>    to protect RADIUS packets and to hide RADIUS Attributes.  This
>    capability covers all RADIUS message types: Access-Request/Response,
>    Accounting-Request/Response, and CoA/Disconnect-Request/Response.
> 
> Since RADIUS has no negotiation method of I'm aware (hint & 
> accept/ignore is hardly a negotiation mechanism)...

Yeah, but it's what we've got.

>... I find these statements very curious, especially in light of the
> earlier statement (section 2, paragraph 3) that the password-hiding
> function will be negotiable.  Basically, what is being called for is
> impossible in the context of the RADIUS protocol, implying that the
> negotiations would take place outside of RADIUS (e.g., in TLS).

That wasn't what I understood when I transcribed that text.  It's true that
"hint and consent" is a bit crude, but I'd like to see a more in-depth
technical exploration of why you think it makes crypto-agility impossible
within RADIUS

> Section 4.1:
> Once again, assuming a solution.  State the requirements that a solution
> must meet, not your personal assumptions about the form which the solution
> will take.  I say "personal" because a fair subset of the active WG (of
> which this document is purportedly a product) _does not_ share the
> expectation that " proposals will utilize other techniques".

I take that text to means that RADIUS over IPSec has already been defined,
and therefore proposing RADIUS over IPSec is not what we're looking for to
address RADIUS crypto-agility.  After all, if an existing solution needs
everyone's needs, why waste time on a requirements document, never mind a
solution document?  Therefore, it's reasonable to say that "Just use IPSec."
is out of scope for RADIUS crypto-agility.

> Section 4.2, paragraph 2 states:
> 
>    Included in negotiation techniques are "hint and consent" mechanisms
>    where the NAS provides a list of algorithms and the server selects
>    one.
> 
> If the server is required to select from the list it can hardly be 
> called a hint.  Once again, I can't see at all how this mechanism 
> could be made to work in the case of the Access-Request message.

Please explain.

> Section 4.3, paragraph 1 states:
> 
>    Solutions to the problem MUST demonstrate backward compatibility
>    with existing RADIUS implementations.
> 
> I would _really_ like to see some rationale for this requirement 
> (aside from "backward compatibility is sacred and must never be 
> questioned" ;-).

Given that the RADIUS protocol doesn't have a protocol version field,
maintaining backward compatibility seems pretty basic.

> Given that this is new and presumably desirable functionality,
> why is a simple upgrade path not sufficient?

A "fork-lift" upgrade?  :-)



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 17:17:48 +0000
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 15 Aug 2008 13:17:12 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <D4371E585AF84CD5BDF3EC1F35DABB59@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDAAEn0hlA=

Joseph Salowey writes...

> 1. Section 4.2:
> 
> In cases where the client needs to protect all or part of the radius
> request the "hint and select" negotiation the client would provide 
> more than a hint when it chooses the algorithms for protection. 
> Perhaps hint and select is not quite the right term, may be specify
> and select?

While adding a more robust form of capabilities negotiation to RADIUS might
be a useful thing, it's not a charted work item.  I think we are stuck with
the current "hint and select" paradigm that is common usage in RADIUS today.

Perhaps I've misunderstood your comment.  Could you give an example?

> 2. Section 4.6:
> 
> Section 4.6 makes reference to security considerations text about key
> management.  Shouldn't this text be in this document?

Yes, I think so.  Would anyone like to propose some text and a citation into
RFC 4017?



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 17:02:38 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Greg Weber'" <gdweber@gmail.com>
Cc: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Sat, 16 Aug 2008 00:01:35 +0700
Message-ID: <009c01c8fef8$9c532ba0$d4f982e0$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009D_01C8FF33.48B203A0"
Thread-Index: Acj+8B12LwlU9bUHS12+ZopF6L3EHgACEXFQ
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_009D_01C8FF33.48B203A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greg Weber [mailto:gdweber@gmail.com]  writes:

 

On Fri, Aug 15, 2008 at 11:50 AM, Glen Zorn <glenzorn@comcast.net> wrote:

.

 

I haven't read 

your current draft version yet to see if these comments were addressed;

there was no response on the list -that I recall.  

 

Probably not, since it was an individual submission & last time I checked
the authors of such have no obligation to respond to the WG, which in turn
has no control over the work.  

 

Of course, since the draft is now a WG item I'd love to address your
comments (if I could only see them ;-).

 

These were my comments on the -00 WG draft:

  http://ops.ietf.org/lists/radiusext/2008/msg00095.html

 

Thanks!

Not sure if these have been addressed or obviated by now- or if they

were originally valid...

 

Greg 

 

.

 


------=_NextPart_000_009D_01C8FF33.48B203A0
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=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;}
 /* 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;}
@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'>

<div>

<div>

<p class=3DMsoNormal><span style=3D'color:#00B050'>Greg Weber
[mailto:gdweber@gmail.com] &nbsp;writes:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal>On Fri, Aug 15, 2008 at 11:50 AM, Glen Zorn &lt;<a
href=3D"mailto:glenzorn@comcast.net">glenzorn@comcast.net</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<div>

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

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

<div>

<div>

<div>

<div>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&#8230;</span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#7030A0'>&nbsp;</span><o:p></o:p></p>

<p>I haven't read&nbsp;<o:p></o:p></p>

</div>

<div>

<p>your current draft version yet to see if these comments were =
addressed;<o:p></o:p></p>

</div>

</div>

<div>

<div>

<p>there was no response on the list -that I recall. =
&nbsp;<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p><span style=3D'font-size:11.0pt;color:#7030A0'>Probably not, since it =
was an
individual submission &amp; last time I checked the authors of such have =
no
obligation to respond to the WG, which in turn has no control over the
work.&nbsp; </span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

</div>

<p><span style=3D'font-size:11.0pt;color:#1F497D'>Of course, since the =
draft is
now a WG item I'd love to address your comments (if I could only see =
them ;-).</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>These were my comments on the -00 WG =
draft:<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;<a
href=3D"http://ops.ietf.org/lists/radiusext/2008/msg00095.html">http://op=
s.ietf.org/lists/radiusext/2008/msg00095.html</a><o:p></o:p></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'color:#00B050'>Thanks!<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal>Not sure if these have been addressed or obviated =
by now- or
if they<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>were originally valid...<o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<blockquote style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>

<div>

<div>

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

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

<div>

<div>

<div>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&#8230;</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</blockquote>

</div>

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

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_009D_01C8FF33.48B203A0--



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 17:00:56 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: "'Stefan Winter'" <stefan.winter@restena.lu>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 23:59:37 +0700
Message-ID: <009b01c8fef8$55f76400$01e62c00$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj+Q9IHh1Eq44ROQd2GY3z+cDCn5gAsjWSQ
Content-Language: en-us

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> >> Alan's wording "The More Flag MUST NOT be set if the Length is less
> >> than
> >> 255." sounds good to me.
> >
> > My point was that making these kinds of rules is pointless: if
> someone wants
> > to split "Hello" into 5 separate attributes they either have a very
> good
> > reason to do so that none of us can foresee or they will soon be
> finding
> > gainful employment in a different field.  In any case, it's not
> possible to
> > protect people from their own stupidity (besides, they could still do
> it
> > with tags).
> 
>   It's only one sentence.  

A sentence here, a sentence there & pretty soon you're outlawing driving
while blindfolded (http://www.whatcar.com/news-article.aspx?NA=229117)...

> And it will stop the stupid people from
> afflicting everyone else.

No, they can still do it (even more stupidly) with tags...

> 
>   RFC 2865 has comments saying:
> 
>       The secret MUST NOT be empty (length 0) since this would allow
>       packets to be trivially forged.
> 
>   Which were inserted because of real-world exposure to implementations
> having *no* configuration for shared secrets. (i.e. they were always
> NUL).

That may be stupid, or not, depending upon the level of other security in
the network...

> 
>   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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 16:44:07 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Stefan Winter'" <stefan.winter@restena.lu>, "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 23:42:20 +0700
Message-ID: <009a01c8fef5$f5273850$df75a8f0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj99HP/tjdafrPARXuHUs1IJ4c0YgA/a3wA
Content-Language: en-us

Stefan Weber <maito://stefan.winter@restena.lu> writes:

...

> TLV encoding rules: Ext-Length field misses its unit ... (in octets)...

OK

> 
> Example in Figure 3: VSA Length. 7 + 9 = 16, not 15.

OK

...

> Some nitbits:
> 
> - Intro: "101 or so have been". Or so sound a bit colloquial.
> - first example: "Extended-Type *of* 257 by IANA." ( not 0f)

OK

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 16:09:05 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 23:07:50 +0700
Message-ID: <006f01c8fef1$17fdc6a0$47f953e0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj98OGpJZ+vwklsSX6zK6+G8ry4pQA/omMg
Content-Language: en-us

Alan DeKok <mailto://aland@deployingradius.com> writes:

...

> Section 4:
> ...
>    o  The final octet of the header contains the More flag and Tag
>       field.  If the one bit More flag is set (1) this indicates that
>       the encapsulated TLV is continued in the following Extended
>       Attribute; if the More flag is clear (0) then all of the
>       encapsulated TLVs fit into the current Extended Attribute.  The
>       More flag MUST NOT be set if the Extended Attribute contains more
>       than one TLV.
> 
>   To be clear: this means that the Extended-Attribute can encapsulate
> multiple TLV's if they're short, or only one TLV if it's long.

OK, are you saying that the existing text isn't clear?  It seems pretty
precise to me, should it be more vague (e.g., "long" & "short")?

> 
> 
> Section 5:
> 
>    M (More)
> 
>       The More Flag is one (1) bit in length and MUST be present.  When
>       a value to be transmitted exceeds 246 octets in length it is
>       fragmented over two or more Extended Attributes.  If the More
> Flag
>       is set (1), this indicates that the Value field of the Extended
>       Attribute contains a fragment of a larger value, which is
>       continued in the next Extended Attribute of the same Ext-Type.
> 
>   Can we add a MUST?  i.e. If the More Flag is set, the next attribute
> MUST be an Extended-Attribute of the same Extended-Type.

Fine

...

>    Ext-Type
> 
>       Two (2) octets.  Up-to-date values of the Ext-Type field are
>       specified in the most recent "Assigned Numbers" [IANA].  Values
>       XXXX-YYYY are reserved.
> 
>   I would suggest reserving the top 1K: 64512-65535

Rationale?

...

>    Consider the following structure:
> 
>      struct
>        Integer a;
>        String  b;
>        Integer c;
>      endStruct
> 
>   What syntax is this?  I think I understand it, but I'm not sure
> everyone will come to a shared understanding.  Maybe instead the
> example
> can be given by reference to existing RADIUS data types.  e.g. A
> structure of RADIUS data types (integer, text, integer) would
> previously
> have to be encoded as three separate and independent attributes.  

Previously, such a structure was impossible to encode in RADIUS.

> Here,
> it can be encoded as 3 attributes sharing a common tag.

Or as 3 TLVs in a single attribute (depending upon the length of the string.

> 
>   Reading the rest of the example, I find the b(4,5) syntax very
> awkward.  I suggest discarding it, and just referring to the diagrams.

Actually, I'd just as soon discard the examples: this draft has way too much
flavor of a tutorial for my taste...

> 
>   The examples could also given broken-out hex encoding of the
> attributes, which may be clearer than the ASCII art diagrams.  e.g.
> 
>   1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f

You're joking, right?

> 
> 7.  Security Considerations
> 
>    I suggest adding a note that a new attribute encoding is an
> opportunity for buffer overflows, inadequate checks, etc.  Implementors
> SHOULD take care to validate the lengths, etc. before decoding the
> contents of the attributes.
> 
> 8.  IANA Considerations
> ...
>    It also requires that IANA set up a new registry for the RADIUS
>    Extended Attribute Types.
> 
>   I suggest leaving the first 0..255 attributes as unallocated, in
> order
> to avoid confusion with legacy RADIUS attributes.

Presumably the people who would get confused are those who have to be told
to protect against buffer overflows (& send "hello" as five separate
attributes), right?

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 16:01:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=eVRIXPD28BfH/7IB8rzb9cM4IcG9IiDznQkiAq39g50=; b=oRVtT09O4G06/ArRFJcrL9kFUl1sPDrNB7g1ThmkUIJaBxrpG/ZVsp8CMzc1mdPQLN CnqzX/RZgg6GCWM9h8PvypPD0Qi2oyAsAQ79usGe4nVJnY0Cq9XEkIxPyHngqCzUJq7i YlbBB7UIlLpfXDpn+Tw2WXQqSRPPOFN9icQzY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=GrjSa1UFHBgZbLQ0hbJnwkevv1g/ljJqxeOubpKPa6Zvyu4S3423RhGOwtgYF0oqYM J4K1hFffMvqHqunpQIqSMFvmxTh/xYPu/N/KXH/OIjJb+WPzrRa1U/L6vgP+hZZzYim9 XpJ0b4wxHLplGY0pUGCBmfPzjoKzQCuqnVrwQ=
Message-ID: <d11ef1350808150900o496b3c3as31ca2d073bfebc63@mail.gmail.com>
Date: Fri, 15 Aug 2008 12:00:59 -0400
From: "Greg Weber" <gdweber@gmail.com>
To: "Glen Zorn" <glenzorn@comcast.net>
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Cc: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, radiusext@ops.ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_90886_12638339.1218816059680"

------=_Part_90886_12638339.1218816059680
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Fri, Aug 15, 2008 at 11:50 AM, Glen Zorn <glenzorn@comcast.net> wrote:

>     =85
>
>
>
> I haven't read
>
> your current draft version yet to see if these comments were addressed;
>
> there was no response on the list -that I recall.
>
>
>
> Probably not, since it was an individual submission & last time I checked
> the authors of such have no obligation to respond to the WG, which in tur=
n
> has no control over the work.
>
>
>
> Of course, since the draft is now a WG item I'd love to address your
> comments (if I could only see them ;-).
>

These were my comments on the -00 WG draft:
  http://ops.ietf.org/lists/radiusext/2008/msg00095.html
Not sure if these have been addressed or obviated by now- or if they
were originally valid...

Greg

>
>
> =85
>

------=_Part_90886_12638339.1218816059680
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote">On Fri, Aug 15, 2008 at=
 11:50 AM, Glen Zorn <span dir=3D"ltr">&lt;<a href=3D"mailto:glenzorn@comca=
st.net">glenzorn@comcast.net</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex;">









<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div>

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

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

<div>

<div><div class=3D"Ih2E3d">

<div>

<p><span style=3D"font-size:11.0pt;color:#1F497D">=85</span></p>

<p><span style=3D"font-size:11.0pt;color:#7030A0">&nbsp;</span></p>

<p>I haven&#39;t read&nbsp;</p>

</div>

<div>

<p>your current draft version yet to see if these comments were
addressed;</p>

</div>

</div><div><div class=3D"Ih2E3d">

<p>there was no response on the list -that I recall. &nbsp;</p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></p>

<p><span style=3D"font-size:11.0pt;color:#7030A0">Probably not, since it wa=
s an individual submission &amp; last
time I checked the authors of such have no obligation to respond to the WG,=
 which
in turn has no control over the work.&nbsp; </span></p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></p>

</div><p><span style=3D"font-size:11.0pt;color:#1F497D">Of course, since th=
e draft is now a WG item I&#39;d love to address your
comments (if I could only see them ;-).</span></p></div></div></div></div><=
/div></div></div></blockquote><div><br></div><div>These were my comments on=
 the -00 WG draft:</div><div>&nbsp;&nbsp;<a href=3D"http://ops.ietf.org/lis=
ts/radiusext/2008/msg00095.html">http://ops.ietf.org/lists/radiusext/2008/m=
sg00095.html</a></div>
<div>Not sure if these have been addressed or obviated by now- or if they</=
div><div>were originally valid...</div><div><br></div><div>Greg&nbsp;</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><div style=3D"borde=
r:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div style=
=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><di=
v><div><div>
<p><span style=3D"font-size:11.0pt;color:#1F497D"></span></p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">&nbsp;</span></p>

<p><span style=3D"font-size:11.0pt;color:#1F497D">=85</span></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>


</blockquote></div><br></div>

------=_Part_90886_12638339.1218816059680--

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 15:52:26 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Glen Zorn'" <glenzorn@comcast.net>, "'Greg Weber'" <gdweber@gmail.com>
Cc: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 22:50:31 +0700
Message-ID: <005b01c8feee$ba955700$2fc00500$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005C_01C8FF29.66F45610"
Thread-Index: Acj+3Rj1HVv1sjaWSxmopbH4DOoxmwAChFmAAAG+UmA=
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_005C_01C8FF29.66F45610
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

.

 

I haven't read 

your current draft version yet to see if these comments were addressed;

there was no response on the list -that I recall.  

 

Probably not, since it was an individual submission & last time I checked
the authors of such have no obligation to respond to the WG, which in turn
has no control over the work.  

 

Of course, since the draft is now a WG item I'd love to address your
comments (if I could only see them ;-).

 

.


------=_NextPart_000_005C_01C8FF29.66F45610
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=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:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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'>

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

<div>

<div>

<div>

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

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

<p class=3DMsoNormal>I haven't read&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>your current draft version yet to see if these =
comments were
addressed;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>there was no response on the list -that I recall. =
&nbsp;<o:p></o:p></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:"Arial =
Black","sans-serif";
color:#7030A0'>Probably not, since it was an individual submission &amp; =
last
time I checked the authors of such have no obligation to respond to the =
WG, which
in turn has no control over the work.&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:"Arial =
Black","sans-serif";
color:#1F497D'>Of course, since the draft is now a WG item I'd love to =
address your
comments (if I could only see them ;-).<o:p></o:p></span></p>

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

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

</div>

</div>

</div>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_005C_01C8FF29.66F45610--



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 15:03:40 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Greg Weber'" <gdweber@gmail.com>
Cc: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 22:01:38 +0700
Message-ID: <005301c8fee7$e2d305c0$a8791140$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0054_01C8FF22.8F31DDC0"
Thread-Index: Acj+3Rj1HVv1sjaWSxmopbH4DOoxmwAChFmA
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_0054_01C8FF22.8F31DDC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greg Weber [mailto:gdweber@gmail.com]  writes:


On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn <glenzorn@comcast.net> wrote:

Hannes Tschofenig <mailto:// Hannes.Tschofenig@gmx.net> writes:

> Bernard,
>
> why is there is a working group last call on this document given that
> it
> still has an open issue section giving me the impression that the
> document is far from being ready?

1) As you know, the issues list is not an official WG document, but a tool
for the use of the Chairs & as such its state has no bearing on the status
of a document.
2) All 3 of the issues assigned to the extended attributes document appear
to actually refer to RFC 5080.

 

I suspect Hannes was referring to the open issues section in the draft's
text,

not the list maintained by the chairs.  Regarding the latter, the issue that
I

filed (#250) was intended for your -00 draft, not RFC 5080.  

 

Be that as it may, the link points to an issue raised by Bernard re: the
Fixes draft.

 

I haven't read 

your current draft version yet to see if these comments were addressed;

there was no response on the list -that I recall.  

 

Probably not, since it was an individual submission & last time I checked
the authors of such have no obligation to respond to the WG, which in turn
has no control over the work.  

 

Greg

 

 


>
> Ciao
> Hannes
>
> Bernard Aboba wrote:
> > This is a reminder of the RADEXT WG Last Call on "Extended
> > RADIUS Attributes", prior to requesting that the IESG publish it as a
> Proposed Standard.
> >
> > The document is available here:
> > http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> attributes-04.txt
> >
> > WG Last Call was originally to have completed on August 10, 2008.
> > However, due to lack of response to the RADEXT WG last call,
> > we will be extending the WG last call to August 31, 2008.  Please
> > review the document and post your comments to the RADEXT WG mailing
> list
> > (radiusext@ops.ietf.org) in the format described on the RADEXT WG
> Issues
> > list (http://www.drizzle.com/~aboba/RADEXT/).
> >
> > If you have read the document and approve of its publication, but
> have no
> > comments, please also post this to the list.
> >
> > --
> > to unsubscribe send a message to 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/>

 


------=_NextPart_000_0054_01C8FF22.8F31DDC0
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=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:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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'>

<div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Greg
Weber [mailto:gdweber@gmail.com] &nbsp;writes:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
</span>On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn &lt;<a
href=3D"mailto:glenzorn@comcast.net">glenzorn@comcast.net</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hannes Tschofenig =
&lt;mailto://
<a =
href=3D"mailto:Hannes.Tschofenig@gmx.net">Hannes.Tschofenig@gmx.net</a>&g=
t;
writes:<br>
<br>
&gt; Bernard,<br>
&gt;<br>
&gt; why is there is a working group last call on this document given =
that<br>
&gt; it<br>
&gt; still has an open issue section giving me the impression that =
the<br>
&gt; document is far from being ready?<o:p></o:p></p>

</div>

<p class=3DMsoNormal>1) As you know, the issues list is not an official =
WG
document, but a tool<br>
for the use of the Chairs &amp; as such its state has no bearing on the =
status<br>
of a document.<br>
2) All 3 of the issues assigned to the extended attributes document =
appear<br>
to actually refer to RFC 5080.<o:p></o:p></p>

<div>

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

</div>

<div>

<p class=3DMsoNormal>I suspect Hannes was referring to the open issues =
section in
the draft's text,<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>not the list maintained by the chairs. =
&nbsp;Regarding the
latter, the issue that I<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>filed (#250) was intended for your -00 draft, not =
RFC 5080.
&nbsp;<span style=3D'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:"Arial =
Black","sans-serif";
color:#7030A0'>Be that as it may, the link points to an issue raised by =
Bernard
re: the Fixes draft.<o:p></o:p></span></p>

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

<p class=3DMsoNormal>I haven't read&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>your current draft version yet to see if these =
comments were
addressed;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>there was no response on the list -that I recall. =
&nbsp;<o:p></o:p></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:"Arial =
Black","sans-serif";
color:#7030A0'>Probably not, since it was an individual submission &amp; =
last
time I checked the authors of such have no obligation to respond to the =
WG,
which in turn has no control over the work.&nbsp; <o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>Greg<o:p></o:p></p>

</div>

<div>

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

</div>

<blockquote style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>

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

<div>

<div>

<p class=3DMsoNormal><br>
&gt;<br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt;<br>
&gt; Bernard Aboba wrote:<br>
&gt; &gt; This is a reminder of the RADEXT WG Last Call on =
&quot;Extended<br>
&gt; &gt; RADIUS Attributes&quot;, prior to requesting that the IESG =
publish it
as a<br>
&gt; Proposed Standard.<br>
&gt; &gt;<br>
&gt; &gt; The document is available here:<br>
&gt; &gt; <a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-"
target=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-radext-e=
xtended-</a><br>
&gt; attributes-04.txt<br>
&gt; &gt;<br>
&gt; &gt; WG Last Call was originally to have completed on August 10, =
2008.<br>
&gt; &gt; However, due to lack of response to the RADEXT WG last =
call,<br>
&gt; &gt; we will be extending the WG last call to August 31, 2008.
&nbsp;Please<br>
&gt; &gt; review the document and post your comments to the RADEXT WG =
mailing<br>
&gt; list<br>
&gt; &gt; (<a =
href=3D"mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</a>)
in the format described on the RADEXT WG<br>
&gt; Issues<br>
&gt; &gt; list (<a href=3D"http://www.drizzle.com/~aboba/RADEXT/" =
target=3D"_blank">http://www.drizzle.com/~aboba/RADEXT/</a>).<br>
&gt; &gt;<br>
&gt; &gt; If you have read the document and approve of its publication, =
but<br>
&gt; have no<br>
&gt; &gt; comments, please also post this to the list.<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; to unsubscribe send a message to <a
href=3D"mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf=
.org</a>
with<br>
&gt; &gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; &gt; archive: &lt;<a href=3D"http://psg.com/lists/radiusext/" =
target=3D"_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; to unsubscribe send a message to <a
href=3D"mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf=
.org</a>
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;<a href=3D"http://psg.com/lists/radiusext/" =
target=3D"_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
<br>
<br>
<br>
--<br>
to unsubscribe send a message to <a =
href=3D"mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf=
.org</a>
with<br>
the word 'unsubscribe' in a single line as the message text body.<br>
archive: &lt;<a href=3D"http://psg.com/lists/radiusext/" =
target=3D"_blank">http://psg.com/lists/radiusext/</a>&gt;<o:p></o:p></p>

</div>

</div>

</blockquote>

</div>

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

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0054_01C8FF22.8F31DDC0--



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 13:45:25 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=S2AHwBBWOHoZ8zoJw8jzfReV8z6EYrX6ThToeAByDwc=; b=DaX1jXlf1afLtniFeKnXgDqg09q4krS/tDZhnt77ja1BH0KG0FqdsFYIK2Rfyz3hZc pDr4a/iuQj0M6GdvsJQ9pSN1XYwRHwqHewF/gVkqQPaY3aP6Vt/c4ep0w0X/6iDnNK0/ XtYHQdQ5eW2ZPl7bnpu7azasq+Tmv7wUk8UDE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=nWD8qCuglGBH9ovPfQQKxVaR1RFmLwwKjj5EjT5mdrTUZ4fp5Qd8F8iBVQE7fgNPyC ZRmQ6vLjD9cr2Q/gzYYPZtGDZQfI+yNDi9gTTS30CI5amFQ/iyUlw5mjPaP7w6qLt22e bcP1WgaLJ4M1FTcK5s+hhn+Pr9NwboSmmsnik=
Message-ID: <d11ef1350808150644v9a497d0ge954e20bf86b48a4@mail.gmail.com>
Date: Fri, 15 Aug 2008 09:44:51 -0400
From: "Greg Weber" <gdweber@gmail.com>
To: "Glen Zorn" <glenzorn@comcast.net>
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Cc: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, radiusext@ops.ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_88201_1355597.1218807891739"

------=_Part_88201_1355597.1218807891739
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn <glenzorn@comcast.net> wrote:

> Hannes Tschofenig <mailto:// Hannes.Tschofenig@gmx.net> writes:
>
> > Bernard,
> >
> > why is there is a working group last call on this document given that
> > it
> > still has an open issue section giving me the impression that the
> > document is far from being ready?
>
> 1) As you know, the issues list is not an official WG document, but a tool
> for the use of the Chairs & as such its state has no bearing on the status
> of a document.
> 2) All 3 of the issues assigned to the extended attributes document appear
> to actually refer to RFC 5080.


I suspect Hannes was referring to the open issues section in the draft's
text,
not the list maintained by the chairs.  Regarding the latter, the issue that
I
filed (#250) was intended for your -00 draft, not RFC 5080.  I haven't read
your current draft version yet to see if these comments were addressed;
there was no response on the list -that I recall.

Greg


>
>
> >
> > Ciao
> > Hannes
> >
> > Bernard Aboba wrote:
> > > This is a reminder of the RADEXT WG Last Call on "Extended
> > > RADIUS Attributes", prior to requesting that the IESG publish it as a
> > Proposed Standard.
> > >
> > > The document is available here:
> > > http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> > attributes-04.txt
> > >
> > > WG Last Call was originally to have completed on August 10, 2008.
> > > However, due to lack of response to the RADEXT WG last call,
> > > we will be extending the WG last call to August 31, 2008.  Please
> > > review the document and post your comments to the RADEXT WG mailing
> > list
> > > (radiusext@ops.ietf.org) in the format described on the RADEXT WG
> > Issues
> > > list (http://www.drizzle.com/~aboba/RADEXT/).
> > >
> > > If you have read the document and approve of its publication, but
> > have no
> > > comments, please also post this to the list.
> > >
> > > --
> > > to unsubscribe send a message to 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/>
>

------=_Part_88201_1355597.1218807891739
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Aug 15, 2008 at 6:10 AM, Glen Zorn <span dir="ltr">&lt;<a href="mailto:glenzorn@comcast.net">glenzorn@comcast.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">Hannes Tschofenig &lt;mailto:// <a href="mailto:Hannes.Tschofenig@gmx.net">Hannes.Tschofenig@gmx.net</a>&gt; writes:<br>
<br>
&gt; Bernard,<br>
&gt;<br>
&gt; why is there is a working group last call on this document given that<br>
&gt; it<br>
&gt; still has an open issue section giving me the impression that the<br>
&gt; document is far from being ready?<br>
<br>
</div>1) As you know, the issues list is not an official WG document, but a tool<br>
for the use of the Chairs &amp; as such its state has no bearing on the status<br>
of a document.<br>
2) All 3 of the issues assigned to the extended attributes document appear<br>
to actually refer to RFC 5080.</blockquote><div><br></div><div>I suspect Hannes was referring to the open issues section in the draft&#39;s text,</div><div>not the list maintained by the chairs. &nbsp;Regarding the latter, the issue that I</div>
<div>filed (#250) was intended for your -00 draft, not RFC 5080. &nbsp;I haven&#39;t read&nbsp;</div><div>your current draft version yet to see if these comments were addressed;</div><div>there was no response on the list -that I recall. &nbsp;</div>
<div><br></div><div>Greg</div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<div><div></div><div class="Wj3C7c"><br>
&gt;<br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt;<br>
&gt; Bernard Aboba wrote:<br>
&gt; &gt; This is a reminder of the RADEXT WG Last Call on &quot;Extended<br>
&gt; &gt; RADIUS Attributes&quot;, prior to requesting that the IESG publish it as a<br>
&gt; Proposed Standard.<br>
&gt; &gt;<br>
&gt; &gt; The document is available here:<br>
&gt; &gt; <a href="http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-" target="_blank">http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-</a><br>
&gt; attributes-04.txt<br>
&gt; &gt;<br>
&gt; &gt; WG Last Call was originally to have completed on August 10, 2008.<br>
&gt; &gt; However, due to lack of response to the RADEXT WG last call,<br>
&gt; &gt; we will be extending the WG last call to August 31, 2008. &nbsp;Please<br>
&gt; &gt; review the document and post your comments to the RADEXT WG mailing<br>
&gt; list<br>
&gt; &gt; (<a href="mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</a>) in the format described on the RADEXT WG<br>
&gt; Issues<br>
&gt; &gt; list (<a href="http://www.drizzle.com/~aboba/RADEXT/" target="_blank">http://www.drizzle.com/~aboba/RADEXT/</a>).<br>
&gt; &gt;<br>
&gt; &gt; If you have read the document and approve of its publication, but<br>
&gt; have no<br>
&gt; &gt; comments, please also post this to the list.<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; to unsubscribe send a message to <a href="mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf.org</a> with<br>
&gt; &gt; the word &#39;unsubscribe&#39; in a single line as the message text body.<br>
&gt; &gt; archive: &lt;<a href="http://psg.com/lists/radiusext/" target="_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; to unsubscribe send a message to <a href="mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf.org</a> with<br>
&gt; the word &#39;unsubscribe&#39; in a single line as the message text body.<br>
&gt; archive: &lt;<a href="http://psg.com/lists/radiusext/" target="_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
<br>
<br>
<br>
--<br>
to unsubscribe send a message to <a href="mailto:radiusext-request@ops.ietf.org">radiusext-request@ops.ietf.org</a> with<br>
the word &#39;unsubscribe&#39; in a single line as the message text body.<br>
archive: &lt;<a href="http://psg.com/lists/radiusext/" target="_blank">http://psg.com/lists/radiusext/</a>&gt;<br>
</div></div></blockquote></div><br></div>

------=_Part_88201_1355597.1218807891739--

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 12:26:19 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: <abhisht@microsoft.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Date: Fri, 15 Aug 2008 19:24:23 +0700
Message-ID: <003301c8fed1$e9571f00$bc055d00$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9swl5Q5+W+luPTBm1XAuPqNYzHABHQ7rQ
Content-Language: en-us

Glancing over this:

Since there's only one author, it would be good to move the apostrophe in
"Authors'" left.  

In the table in Section 3, move the abbreviation (ESP) next to "Payload".

Since new values of the Tunnel-Type Attribute are allocated by IETF
Consensus, it might be a better idea to separate this into 2 docs, one for
the ESP value & the other for the proprietary one.  In fact, because the
spec for the Microsoft Secure Socket Tunneling Protocol is public & appears
fairly stable, I would prefer that the allocation be part of an
Informational RFC describing the protocol.  At the very least, though, the
name needs to be changed to "Microsoft's Secure Socket Tunneling Protocol"
(or something similar) that identifies its proprietary nature.




--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 10:11:59 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Hannes Tschofenig'" <Hannes.Tschofenig@gmx.net>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 17:10:33 +0700
Message-ID: <002c01c8febf$2f4e04f0$8dea0ed0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj+NL1voI03o1KBT8O1QRUZ/eKMYAAiHH0Q
Content-Language: en-us

Hannes Tschofenig <mailto:// Hannes.Tschofenig@gmx.net> writes:

> Bernard,
> 
> why is there is a working group last call on this document given that
> it
> still has an open issue section giving me the impression that the
> document is far from being ready?

1) As you know, the issues list is not an official WG document, but a tool
for the use of the Chairs & as such its state has no bearing on the status
of a document.
2) All 3 of the issues assigned to the extended attributes document appear
to actually refer to RFC 5080.

> 
> Ciao
> Hannes
> 
> Bernard Aboba wrote:
> > This is a reminder of the RADEXT WG Last Call on "Extended
> > RADIUS Attributes", prior to requesting that the IESG publish it as a
> Proposed Standard.
> >
> > The document is available here:
> > http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> attributes-04.txt
> >
> > WG Last Call was originally to have completed on August 10, 2008.
> > However, due to lack of response to the RADEXT WG last call,
> > we will be extending the WG last call to August 31, 2008.  Please
> > review the document and post your comments to the RADEXT WG mailing
> list
> > (radiusext@ops.ietf.org) in the format described on the RADEXT WG
> Issues
> > list (http://www.drizzle.com/~aboba/RADEXT/).
> >
> > If you have read the document and approve of its publication, but
> have no
> > comments, please also post this to the list.
> >
> > --
> > to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 08:55:45 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
Subject: Comments  on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 15 Aug 2008 15:53:55 +0700
Message-ID: <002201c8feb4$81ee5df0$85cb19d0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9stY318jDuAAIQyK3rmdNRocQwAA+j48Q
Content-Language: en-us

Questions:

The WG Charter states that all of the existing crypto-agility proposals are
to be published as Experimental RFCs.  In that case, how can the requirement
that " at least one mandatory to implement algorithm will be defined"
(section 1.2) be fulfilled?


Editorial comments:

Front page header:
Since the source of the document is stated in section 1.1 to be the radext
WG, David's role should probably be "Editor".

Section 1.2:
s/propose one of more Internet Drafts/propose one or more Internet-Drafts/

Section 2:
s/Crypto-Agility is the ability for/Crypto-agility is the ability of/

Section 4.5, paragraph 5 states:

   Editorial Note: With the expected acceptance of the proposed RADEXT
   WG Charter revision, some of the issues raised in the preceding
   paragraphs become moot, and this section ought to be revised to
   reflect the revised charter.

Haven't those charter revisions already taken place?


Technical comments:

Section 2, paragraph 2 states:

   In the specific context of the RADIUS protocol and RADIUS
   implementations, crypto-agility may be better defined as the ability
   of RADIUS implementations to negotiate cryptographic algorithms for
   use in RADIUS exchanges, including the cryptographic algorithms used
   to protect RADIUS packets and to hide RADIUS Attributes.  This
   capability covers all RADIUS message types: Access-Request/Response,
   Accounting-Request/Response, and CoA/Disconnect-Request/Response.

Since RADIUS has no negotiation method of I'm aware (hint & accept/ignore is
hardly a negotiation mechanism) I find these statements very curious,
especially in light of the earlier statement (section 2, paragraph 3) that
the password-hiding function will be negotiable.  Basically, what is being
called for is impossible in the context of the RADIUS protocol, implying
that the negotiations would take place outside of RADIUS (e.g., in TLS).  I
think that it is at least inappropriate in a requirements document, in that
it assumes a solution.

Section 4.1: 
Once again, assuming a solution.  State the requirements that a solution
must meet, not your personal assumptions about the form which the solution
will take.  I say "personal" because a fair subset of the active WG (of
which this document is purportedly a product) _does not_ share the
expectation that " proposals will utilize other techniques".

Section 4.2, paragraph 2 states:

   Included in negotiation techniques are "hint and consent" mechanisms
   where the NAS provides a list of algorithms and the server selects
   one.

If the server is required to select from the list it can hardly be called a
hint.  Once again, I can't see at all how this mechanism could be made to
work in the case of the Access-Request message.

Section 4.3, paragraph 1 states:

   Solutions to the problem MUST demonstrate backward compatibility with
   existing RADIUS implementations.  

I would _really_ like to see some rationale for this requirement (aside from
"backward compatibility is sacred and must never be questioned" ;-).  Given
that this is new and presumably desirable functionality, why is a simple
upgrade path not sufficient?

Section 4.5, paragraph 3 states:

   Crypto-agility solutions SHOULD NOT require fundamental changes to
   the RADIUS operational model, such as the introduction of new
   commands or maintenance of state on the RADIUS server.  

OK, I'll bite: how, exactly, does the introduction of a new command
fundamentally change the RADIUS operational model?



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 15 Aug 2008 06:51:06 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>
Cc: "'Alan DeKok'" <aland@deployingradius.com>, <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 13:49:14 +0700
Message-ID: <002001c8fea3$19c89800$4d59c800$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj98OXV6Mdn/4x7RkyVEJ2+H8F8JAAKa5MAACH4/lA=
Content-Language: en-us

David B. Nelson <mailto:// dnelson@elbrysnetworks.com> writes:

> Alan DeKok writes...
> 
> >   Inserting *other* attributes in between a fragemented attribute
> > is annoying and pointless.  It's better to forbid this, and to
> > declare that packets failing this test are malformed, and SHOULD
> > be silently discarded.
> 
> I think this would introduce a new, non-backwards-compatible
> requirement.
> Today, RADIUS requires that attributes of the same type not be re-
> ordered in
> the PDU, e.g. by proxies. There is no such requirement for attributes
> of
> differing types.

I believe that he meant that all fragments of a given attribute must be
contiguous in the original packet...

> 
> >   What does "Foo(0,4)" mean?
> 
> I suppose it means the TLV with Type Code 4, assigned within the IETF
> allocation, i.e. Attribute 26, Vendor-ID 0.

This would be a perfectly reasonable interpretation, but it actually means
"octets 0-4 of attribute Foo".

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 20:05:07 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Thu, 14 Aug 2008 13:04:34 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5065592E5@xmb-sjc-225.amer.cisco.com>
Thread-Topic: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
thread-index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDA
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <aboba@internaut.com>, <radiusext@ops.ietf.org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2084; t=1218744278; x=1219608278; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jsalowey@cisco.com; z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci sco.com> |Subject:=20RE=3A=20REMINDER=3A=20RADEXT=20WG=20Last=20Call =20on=20=22Crypto-Agility=20Requirements=20for=20RADIUS=22 |Sender:=20; bh=eNLHBQ1Zdc2VxhjKIGHW/FNxqdVhdgg23O5nMZLGWp4=; b=Z51LD1H14aBvYg6ah+3fVJz6D+1FwDXHbdqYbP3dkFVw9eK1zH+6QM7wjz SZH/Ne/C6N7VcjWxjzWTP5+G4bsXl8L+Zg/UtFNzx32NC4/ZdpGpK5WKOegR pAidxI0IanlUZLc5oKO8ufrPez+CV2wsWG86GAN1dfj26g0uDW0kg=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );

I have read the draft and for the most part it looks good.

I have a few comments:

1. Section 4.2:

In cases where the client needs to protect all or part of the radius
request the "hint and select" negotiation the client would provide more
than a hint when it chooses the algorithms for protection.  Perhaps hint
and select is not quite the right term, may be specify and select?  The
client specifies what it uses and can specify a list it supports that
the server can use.=20

2. Section 4.6:

Section 4.6 makes reference to security considerations text about key
management.  Shouldn't this text be in this document?

Thanks,

Joe




> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
> Sent: Wednesday, August 13, 2008 7:06 PM
> To: radiusext@ops.ietf.org
> Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility=20
> Requirements for RADIUS"
>=20
> This is a reminder of the ongoing RADEXT WG Last Call on=20
> "Crypto-Agility Requirements for RADIUS" prior to requesting=20
> that the IESG publish it as an Informational RFC.=20
> =20
> The document is available here:
>
http://www.ietf.org/internet-drafts/draft-ietf-radext-crypto-agility-req
uirements-00.txt
> =20
> WG Last Call was to have lasted until August 10, 2008.   Since there=20
> have been no comments posted yet, we will extend the last=20
> call for another two weeks (until August 31, 2008).  Please=20
> review the document and post your comments to the RADEXT WG=20
> mailing list
> (radiusext@ops.ietf.org) in the format described on the=20
> RADEXT WG Issues=20
> list (http://www.drizzle.com/~aboba/RADEXT/).  =20
> =20
> If you have read the document and approve of its publication,=20
> but have no comments, please also post this to the list.=20
>=20
> --
> to unsubscribe send a message to=20
> radiusext-request@ops.ietf.org with the word 'unsubscribe' in=20
> a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=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/>


Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 14 Aug 2008 20:05:01 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Thu, 14 Aug 2008 13:04:34 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5065592E6@xmb-sjc-225.amer.cisco.com>
Thread-Topic: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
thread-index: Acj9soWfbWakFU5jQkOjx3ycw9HsgwAH3fDA
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <aboba@internaut.com>, <radiusext@ops.ietf.org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2084; t=1218744278; x=1219608278; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jsalowey@cisco.com; z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci sco.com> |Subject:=20RE=3A=20REMINDER=3A=20RADEXT=20WG=20Last=20Call =20on=20=22Crypto-Agility=20Requirements=20for=20RADIUS=22 |Sender:=20; bh=eNLHBQ1Zdc2VxhjKIGHW/FNxqdVhdgg23O5nMZLGWp4=; b=K1zVbDZl7hSbOaH907cYxXBZnYvd8SGpLLZqhIx5TFwPSrWEW0aDppYZB0 GpScm40idfnQjgHR3LKSFP5QOxkFdHeM1ckGqXmflU508dhOAnPd+0xBXq+Z jA0TYyww+L;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );

I have read the draft and for the most part it looks good.

I have a few comments:

1. Section 4.2:

In cases where the client needs to protect all or part of the radius
request the "hint and select" negotiation the client would provide more
than a hint when it chooses the algorithms for protection.  Perhaps hint
and select is not quite the right term, may be specify and select?  The
client specifies what it uses and can specify a list it supports that
the server can use.=20

2. Section 4.6:

Section 4.6 makes reference to security considerations text about key
management.  Shouldn't this text be in this document?

Thanks,

Joe




> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
> Sent: Wednesday, August 13, 2008 7:06 PM
> To: radiusext@ops.ietf.org
> Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility=20
> Requirements for RADIUS"
>=20
> This is a reminder of the ongoing RADEXT WG Last Call on=20
> "Crypto-Agility Requirements for RADIUS" prior to requesting=20
> that the IESG publish it as an Informational RFC.=20
> =20
> The document is available here:
>
http://www.ietf.org/internet-drafts/draft-ietf-radext-crypto-agility-req
uirements-00.txt
> =20
> WG Last Call was to have lasted until August 10, 2008.   Since there=20
> have been no comments posted yet, we will extend the last=20
> call for another two weeks (until August 31, 2008).  Please=20
> review the document and post your comments to the RADEXT WG=20
> mailing list
> (radiusext@ops.ietf.org) in the format described on the=20
> RADEXT WG Issues=20
> list (http://www.drizzle.com/~aboba/RADEXT/).  =20
> =20
> If you have read the document and approve of its publication,=20
> but have no comments, please also post this to the list.=20
>=20
> --
> to unsubscribe send a message to=20
> radiusext-request@ops.ietf.org with the word 'unsubscribe' in=20
> a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=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/>


Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 14 Aug 2008 19:47:42 +0000
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: "'Alan DeKok'" <aland@deployingradius.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 15:47:23 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <90797A5700C14358A7838274F4364A9D@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj+Q1yb5FtV6joZRmm9F5LXJQ3oRQAAIOJA

> > Yes, we do.  I can cite numerous examples.
> 
>   Where?

Section 7.1 of RFC 2865.  Section 2.1 of RFC 3580.  Section 2.2 of RFC 5176.
Section 2.1.1 of RFC 5080.  Section 6 of RFC 5090.

This is not an exhaustive list, but rather a sampling.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 19:27:50 +0000
Message-ID: <48A486FC.40007@deployingradius.com>
Date: Thu, 14 Aug 2008 21:26:52 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Glen Zorn <glenzorn@comcast.net>
CC: 'Stefan Winter' <stefan.winter@restena.lu>, radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
>> Alan's wording "The More Flag MUST NOT be set if the Length is less
>> than
>> 255." sounds good to me.
> 
> My point was that making these kinds of rules is pointless: if someone wants
> to split "Hello" into 5 separate attributes they either have a very good
> reason to do so that none of us can foresee or they will soon be finding
> gainful employment in a different field.  In any case, it's not possible to
> protect people from their own stupidity (besides, they could still do it
> with tags).

  It's only one sentence.  And it will stop the stupid people from
afflicting everyone else.

  RFC 2865 has comments saying:

      The secret MUST NOT be empty (length 0) since this would allow
      packets to be trivially forged.

  Which were inserted because of real-world exposure to implementations
having *no* configuration for shared secrets. (i.e. they were always NUL).

  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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 19:24:57 +0000
Message-ID: <48A48634.9030002@deployingradius.com>
Date: Thu, 14 Aug 2008 21:23:32 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "David B. Nelson" <dnelson@elbrysnetworks.com>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David B. Nelson wrote:
> I think this would introduce a new, non-backwards-compatible requirement.
> Today, RADIUS requires that attributes of the same type not be re-ordered in
> the PDU, e.g. by proxies. There is no such requirement for attributes of
> differing types.

  That's not *quite* what I meant.

  What I meant was interspersing attributes of disparate types.  I'm not
aware of any implementation that does this (e.g. for EAP-Message).  But
I've learned to be paranoid about RADIUS specifications.

>>   What does "Foo(0,4)" mean?
> 
> I suppose it means the TLV with Type Code 4, assigned within the IETF
> allocation, i.e. Attribute 26, Vendor-ID 0.

  Nope.  Read the rest of the doc.  It means "octets 0 through 4 of
attribute Foo".

> There is a long-standing typographical tradition of listing attributes as
> Attribute-Name (##).

  References?

[ struct ]
>>   What syntax is this?
> 
> Pseudo-code?  Maybe actually using ANSI C would be more universal.  I think
> the RADIUS data types are not a good way to express this concept, as
> witnessed by confusion in various drafts over the years. 

  I'm just asking for a definition of the terminology and concepts
referred to in the draft.  What's an "Integer", or a "String"?  Do these
relate to C definitions?  RADIUS?

> How is that different from good coding guidelines for *any* implementation
> of *any* protocol?  What about the on-the-wire protocol involved raises
> these risks?

  Er... nothing.

>> 9.  Open Issues
>>
>>    What is the numbering scheme for attributes that will be used by RFC
>>    writers going forward?  For example today we write user-name(1).
>>
>>   Uh... We do?
> 
> Yes, we do.  I can cite numerous examples.

  Where?

  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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 17:37:08 +0000
Message-ID: <48A46D3A.9000406@gmx.net>
Date: Thu, 14 Aug 2008 20:36:58 +0300
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bernard,

why is there is a working group last call on this document given that it 
still has an open issue section giving me the impression that the 
document is far from being ready?

Ciao
Hannes

Bernard Aboba wrote:
> This is a reminder of the RADEXT WG Last Call on "Extended 
> RADIUS Attributes", prior to requesting that the IESG publish it as a Proposed Standard. 
>  
> The document is available here:
> http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-04.txt
>  
> WG Last Call was originally to have completed on August 10, 2008.   
> However, due to lack of response to the RADEXT WG last call, 
> we will be extending the WG last call to August 31, 2008.  Please 
> review the document and post your comments to the RADEXT WG mailing list 
> (radiusext@ops.ietf.org) in the format described on the RADEXT WG Issues 
> list (http://www.drizzle.com/~aboba/RADEXT/).   
>  
> If you have read the document and approve of its publication, but have no
> comments, please also post this to the list. 
>
> --
> to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 17:35:05 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Stefan Winter'" <stefan.winter@restena.lu>
Cc: <radiusext@ops.ietf.org>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Fri, 15 Aug 2008 00:33:40 +0700
Message-ID: <004f01c8fe33$ed1b84d0$c7528e70$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: Acj+Ap5X2rEQpcmqQfK3am5RpDNpsQAMAXdA
Content-Language: en-us

Stefan Winter [mailto:stefan.winter@restena.lu] writes:

> Hi,
>=20
> >> Maybe just put a note like "If you are a total moron, stop
> >> reading now." in the Abstract?
> >>
> >
> > There certainly should be some other ways to say it.
> >
>=20
> Alan's wording "The More Flag MUST NOT be set if the Length is less
> than
> 255." sounds good to me.

My point was that making these kinds of rules is pointless: if someone =
wants
to split "Hello" into 5 separate attributes they either have a very good
reason to do so that none of us can foresee or they will soon be finding
gainful employment in a different field.  In any case, it's not possible =
to
protect people from their own stupidity (besides, they could still do it
with tags).

>=20
> Stefan
>=20
>=20
> --
>=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education =
Nationale et
> de la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473




--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 17:28:37 +0000
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
Cc: "'Alan DeKok'" <aland@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 13:27:42 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj98OXV6Mdn/4x7RkyVEJ2+H8F8JAAKa5MA

Alan DeKok writes...

>   Inserting *other* attributes in between a fragemented attribute
> is annoying and pointless.  It's better to forbid this, and to 
> declare that packets failing this test are malformed, and SHOULD
> be silently discarded.

I think this would introduce a new, non-backwards-compatible requirement.
Today, RADIUS requires that attributes of the same type not be re-ordered in
the PDU, e.g. by proxies. There is no such requirement for attributes of
differing types.

>   What does "Foo(0,4)" mean?

I suppose it means the TLV with Type Code 4, assigned within the IETF
allocation, i.e. Attribute 26, Vendor-ID 0.

Why not just refer to it as "Foo"?

There is a long-standing typographical tradition of listing attributes as
Attribute-Name (##).

>    Consider the following structure:
> 
>      struct
>        Integer a;
>        String  b;
>        Integer c;
>      endStruct
> 
>   What syntax is this?

Pseudo-code?  Maybe actually using ANSI C would be more universal.  I think
the RADIUS data types are not a good way to express this concept, as
witnessed by confusion in various drafts over the years. 

>   Reading the rest of the example, I find the b(4,5) syntax very
> awkward.

I think that's part of Glen's [potential] issue.

> 7.  Security Considerations
> 
>    I suggest adding a note that a new attribute encoding is an
> opportunity for buffer overflows, inadequate checks, etc. 
> Implementors SHOULD take care to validate the lengths, etc. 
> before decoding the contents of the attributes.

How is that different from good coding guidelines for *any* implementation
of *any* protocol?  What about the on-the-wire protocol involved raises
these risks?

> 9.  Open Issues
> 
>    What is the numbering scheme for attributes that will be used by RFC
>    writers going forward?  For example today we write user-name(1).
> 
>   Uh... We do?

Yes, we do.  I can cite numerous examples.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 11:41:34 +0000
Message-ID: <48A419C8.2030308@restena.lu>
Date: Thu, 14 Aug 2008 13:40:56 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
CC: Glen Zorn <glenzorn@comcast.net>, radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

>> Maybe just put a note like "If you are a total moron, stop 
>> reading now." in the Abstract?
>>     
>
> There certainly should be some other ways to say it. 
>   

Alan's wording "The More Flag MUST NOT be set if the Length is less than 
255." sounds good to me.

Stefan


-- 

Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 11:33:30 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 13:32:59 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04ECC5A7@307622ANEX5.global.avaya.com>
Thread-Topic: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Thread-Index: Acj99HP/tjdafrPARXuHUs1IJ4c0YgACReoAAAD28RA=
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Glen Zorn" <glenzorn@comcast.net>, "Stefan Winter" <stefan.winter@restena.lu>
Cc: <radiusext@ops.ietf.org>

=20

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org=20
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Glen Zorn
> Sent: Thursday, August 14, 2008 2:10 PM
> To: 'Stefan Winter'
> Cc: radiusext@ops.ietf.org
> Subject: RE: REMINDER: RADEXT WG Last call on "Extended=20
> RADIUS Attributes"
>=20
> Stefan Winter <mailto://stefan.winter@restena.lu> writes:
>=20

...

> > There also is no clarification whether fragmenting should=20
> only occur=20
> > when it is needed. Without requiring this, a compliant=20
> implementation=20
> > could as well split the 5-byte data "Hello" into five fragments. I=20
> > suggest to add a bit of wording to strongly discourage that.
>=20
> Maybe just put a note like "If you are a total moron, stop=20
> reading now." in the Abstract?
>=20
> ...

There certainly should be some other ways to say it.=20

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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 11:28:15 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Thu, 14 Aug 2008 18:26:49 +0700
Message-ID: <000801c8fe00$b50248a0$1f06d9e0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj9tI9KOI7i58ewR6q8qn9+WmSnywASr9SQ
Content-Language: en-us

Bernard Aboba <mailto://aboba@internaut.com> writes:

> Glen Zorn said:
> 
> "As I mentioned a couple of times at the Dublin session, the current
> definition of the Extended Attributes
> (http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-
> attributes-0
> 4.txt) doesn't in general allow the definition of an overall type for
> the
> Attribute in question:  an Extended Attribute is basically just an
> unordered set of TLVs.  This fact doesn't bother me much, if at all,
> but
> the second time I mentioned it there was some grumbling from the crowd,
> so
> I thought I'd bring it up one more time on the list..."
> 
> One question is how the grouping semantic differs from that of Diameter
> (RFC 3588), and what the impact is.  Looking at RFC 3588, it does seem
> that the agbility to name and define a Grouped AVP has some advantages.

Perhaps, but it also has disadvantages (such as the awkwardness of defining
new AVPs for simple, ad-hoc situations.

> 
> For example, it enables a formal definition of the grouped AVP,
> including
> a grammar.  

It's not clear that this is actually an advantage: a large majority of the
confusion I've seen reported by Diameter developers has been caused by ABNF.


> Without this, it is possible that the loose semantics would
> affect
> interoperability (e.g. arbitrary attribute groupings might not be
> supported understood).

I don't see how this could happen except for essentially the same reasons as
in Diameter (despite the over-specification of the protocol).  From your
quotation of RFC 3588 below:

'The data for the optional AVPs is represented in hex since the format of
these AVPs is neither known at the time of definition of the Example-AVP
group, nor (likely) at the time when the example instance of this AVP is
interpreted - except by Diameter implementations which support the same set
of AVPs...note that AVPs may be present in the Grouped AVP value which the
receiver cannot interpret...'

> 
> From RFC 3588 Section 4.4:
> 
> 4.4.  Grouped AVP Values
> 
>    The Diameter protocol allows AVP values of type 'Grouped.'  This
>    implies that the Data field is actually a sequence of AVPs.  It is
>    possible to include an AVP with a Grouped type within a Grouped
> type,
>    that is, to nest them.  AVPs within an AVP of type Grouped have the
>    same padding requirements as non-Grouped AVPs, as defined in Section
>    4.
> 
>    The AVP Code numbering space of all AVPs included in a Grouped AVP
> is
>    the same as for non-grouped AVPs.  Further, if any of the AVPs
>    encapsulated within a Grouped AVP has the 'M' (mandatory) bit set,
>    the Grouped AVP itself MUST also include the 'M' bit set.
> 
>    Every Grouped AVP defined MUST include a corresponding grammar,
> using
>    ABNF [ABNF] (with modifications), as defined below.
> 
>       grouped-avp-def  = name "::=" avp
> 
>       name-fmt         = ALPHA *(ALPHA / DIGIT / "-")
> 
>       name             = name-fmt
>                          ; The name has to be the name of an AVP,
>                          ; defined in the base or extended Diameter
>                          ; specifications.
> 
>       avp              = header  [ *fixed] [ *required] [ *optional]
>                          [ *fixed]
> 
>       header           = "<" "AVP-Header:" avpcode [vendor] ">"
> 
>       avpcode          = 1*DIGIT
>                          ; The AVP Code assigned to the Grouped AVP
> 
>       vendor           = 1*DIGIT
>                          ; The Vendor-ID assigned to the Grouped AVP.
>                          ; If absent, the default value of zero is
>                          ; used.
> 
> 4.4.1.  Example AVP with a Grouped Data type
> 
>    The Example-AVP (AVP Code 999999) is of type Grouped and is used to
>    clarify how Grouped AVP values work.  The Grouped Data field has the
>    following ABNF grammar:
> 
>       Example-AVP  ::= < AVP Header: 999999 >
>                        { Origin-Host }
>                      1*{ Session-Id }
>                       *[ AVP ]
> 
>    An Example-AVP with Grouped Data follows.
> 
>    The Origin-Host AVP is required (Section 6.3).  In this case:
> 
>       Origin-Host = "example.com".
> 
>    One or more Session-Ids must follow.  Here there are two:
> 
>       Session-Id =
>         "grump.example.com:33041;23432;893;0AF3B81"
> 
>       Session-Id =
>         "grump.example.com:33054;23561;2358;0AF3B82"
> 
>    optional AVPs included are
> 
>       Recovery-Policy = <binary>
>          2163bc1d0ad82371f6bc09484133c3f09ad74a0dd5346d54195a7cf0b35
>          2cabc881839a4fdcfbc1769e2677a4c1fb499284c5f70b48f58503a45c5
>          c2d6943f82d5930f2b7c1da640f476f0e9c9572a50db8ea6e51e1c2c7bd
>          f8bb43dc995144b8dbe297ac739493946803e1cee3e15d9b765008a1b2a
>          cf4ac777c80041d72c01e691cf751dbf86e85f509f3988e5875dc905119
>          26841f00f0e29a6d1ddc1a842289d440268681e052b30fb638045f7779c
>          1d873c784f054f688f5001559ecff64865ef975f3e60d2fd7966b8c7f92
> 
>       Futuristic-Acct-Record = <binary>
>          fe19da5802acd98b07a5b86cb4d5d03f0314ab9ef1ad0b67111ff3b90a0
>          57fe29620bf3585fd2dd9fcc38ce62f6cc208c6163c008f4258d1bc88b8
>          17694a74ccad3ec69269461b14b2e7a4c111fb239e33714da207983f58c
>          41d018d56fe938f3cbf089aac12a912a2f0d1923a9390e5f789cb2e5067
>          d3427475e49968f841
> 
>    The data for the optional AVPs is represented in hex since the
> format
>    of these AVPs is neither known at the time of definition of the
>    Example-AVP group, nor (likely) at the time when the example
> instance
>    of this AVP is interpreted - except by Diameter implementations
> which
>    support the same set of AVPs.  The encoding example illustrates how
>    padding is used and how length fields are calculated.  Also note
> that
>    AVPs may be present in the Grouped AVP value which the receiver
>    cannot interpret (here, the Recover-Policy and Futuristic-Acct-
> Record
>    AVPs).
> 
>    This AVP would be encoded as follows:
> 
>            0       1       2       3       4       5       6       7
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>      0 |     Example AVP Header (AVP Code = 999999), Length = 468
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>      8 |     Origin-Host AVP Header (AVP Code = 264), Length = 19
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     16 |  'e'  |  'x'  |  'a'  |  'm'  |  'p'  |  'l'  |  'e'  |  '.'
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     24 |  'c'  |  'o'  |  'm'  |Padding|     Session-Id AVP Header
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     32 | (AVP Code = 263), Length = 50 |  'g'  |  'r'  |  'u'  |  'm'
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     64 |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '1'
> |Padding|Padding|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     72 |     Session-Id AVP Header (AVP Code = 263), Length = 51
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>     80 |  'g'  |  'r'  |  'u'  |  'm'  |  'p'  |  '.'  |  'e'  |  'x'
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    104 |  '0'  |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '2'
> |Padding|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    112 |   Recovery-Policy Header (AVP Code = 8341), Length = 223
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    120 |  0x21 | 0x63  | 0xbc  | 0x1d  | 0x0a  | 0xd8  | 0x23  | 0x71
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    320 |  0x2f | 0xd7  | 0x96  | 0x6b  | 0x8c  | 0x7f  | 0x92
> |Padding|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    328 | Futuristic-Acct-Record Header (AVP Code = 15930), Length =
> 137|
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    336 |  0xfe | 0x19  | 0xda  | 0x58  | 0x02  | 0xac  | 0xd9  | 0x8b
> |
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>                                      . . .
>        +-------+-------+-------+-------+-------+-------+-------+-------
> +
>    464 |  0x41 |Padding|Padding|Padding|
>        +-------+-------+-------+-------+
> 
> 
> 
> 
> 
> --
> to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 11:11:21 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Stefan Winter'" <stefan.winter@restena.lu>
Cc: <radiusext@ops.ietf.org>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Date: Thu, 14 Aug 2008 18:10:19 +0700
Message-ID: <000701c8fdfe$5e220ef0$1a662cd0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj99HP/tjdafrPARXuHUs1IJ4c0YgACReoA
Content-Language: en-us

Stefan Winter <mailto://stefan.winter@restena.lu> writes:

> Hello,
> 
> a few comments:
> 
> TLV encoding and M flag: All examples stuff the maximum payload into
> the first fragment, set the M bit and put the remainder into the next
> fragment. This is fine and sensible, but not enforced in the
> description.
> One might also do any other split of the data, like if there is a 300
> byte data to be transmitted, 150 in the first fragment, 150 in the
> second.
> There also is no clarification whether fragmenting should only occur
> when it is needed. Without requiring this, a compliant implementation
> could as well split the 5-byte data "Hello" into five fragments. I
> suggest to add a bit of wording to strongly discourage that.

Maybe just put a note like "If you are a total moron, stop reading now." in
the Abstract?

...

> Finally, Security Considerations: This section is rather short, I
> suggest to expand the "TBD" :-)

Text is welcome.

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 10:40:50 +0000
Message-ID: <48A40B60.6010303@deployingradius.com>
Date: Thu, 14 Aug 2008 12:39:28 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Stefan Winter wrote:
> One might also do any other split of the data, like if there is a 300
> byte data to be transmitted, 150 in the first fragment, 150 in the second.
> There also is no clarification whether fragmenting should only occur
> when it is needed. Without requiring this, a compliant implementation
> could as well split the 5-byte data "Hello" into five fragments. I
> suggest to add a bit of wording to strongly discourage that.

  I would say:

  The More Flag MUST NOT be set if the Length is less than 255.

> - is it worth mentioning that this encoding is not the only one
> possible, since the order of the struct members doesn't need to be
> preserved during marshalling?

  Yes.  Attributes don't have order in RADIUS.

  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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 10:07:56 +0000
Message-ID: <48A403E7.1030000@restena.lu>
Date: Thu, 14 Aug 2008 12:07:35 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

 > A corrected figure is below:

Oh well. Add a line-break at the obvious place.

Stefan


-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 09:56:55 +0000
Message-ID: <48A40157.2050706@restena.lu>
Date: Thu, 14 Aug 2008 11:56:39 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hello,

a few comments:

TLV encoding and M flag: All examples stuff the maximum payload into the first fragment, set the M bit and put the remainder into the next fragment. This is fine and sensible, but not enforced in the description.
One might also do any other split of the data, like if there is a 300 byte data to be transmitted, 150 in the first fragment, 150 in the second.
There also is no clarification whether fragmenting should only occur when it is needed. Without requiring this, a compliant implementation could as well split the 5-byte data "Hello" into five fragments. I suggest to add a bit of wording to strongly discourage that.

TLV encoding rules: Ext-Length field misses its unit ... (in octets)...

Example in Figure 3: VSA Length. 7 + 9 = 16, not 15.

Figure 4: 

- is it worth mentioning that this encoding is not the only one possible, since the order of the struct members doesn't need to be preserved during marshalling? 

- There is a one-off in the encoding of String b. b is 251 octets, i.e. comprised of b[0] thru b[250].
The first fragment can (correct in the figure) hold up to 245 characters, i.e b[0] thru b[244]. Six(!) characters remain, b[245] thru b[250]. The encoding of the second fragment needs to be changed for a TLV data length of 6, which also changes Ext-Length to 3 + 6 = 9 and VSA-Length to 7 + 9 + 7 = 23. The byte-order of the last integer is odd, it looks like the last two bytes are swapped. This is neither big- not little-endian, and I suspect it's an error.
A corrected figure is below:

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type (26)   |    Length     |          Vendor-Id
   |               |  (7+9+7=23)   |             (0)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           Vendor-Id (cont)        |M|    Tag      |    Ext-Type
                 (0)               |0|    (42)     |      (0)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    Ext-Type (cont)|   Ext-Length  |     Value     |               |
         (259)     |   (3 + 6 = 9) |      (e)      |      ( )      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |               |               |    
   |      (e)      |      (n)      |      (d)      |      (.)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    Ext-Type (cont) Ext-type (cont)|   Ext-Length  |               |
         (0)             (271)     |   (3 + 4 = 7) |    (0x12)     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |               |               |
   |    (0x34)     |     (0x56)    |     (0x78)    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Some nitbits: 

- Intro: "101 or so have been". Or so sound a bit colloquial.
- first example: "Extended-Type *of* 257 by IANA." ( not 0f)

Finally, Security Considerations: This section is rather short, I suggest to expand the "TBD" :-)

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 09:29:58 +0000
Message-ID: <48A3FAA1.1020109@deployingradius.com>
Date: Thu, 14 Aug 2008 11:28:01 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> This is a reminder of the RADEXT WG Last Call on "Extended 
> RADIUS Attributes", prior to requesting that the IESG publish it as a Proposed Standard. 

Submitter name: Alan DeKok
Submitter email address: aland@deployingradius.com
Date first submitted: Aug 14 2008
Reference:
Document: [EXTEN]
Comment type: T
Priority: 2

Section 4:
...
   o  The final octet of the header contains the More flag and Tag
      field.  If the one bit More flag is set (1) this indicates that
      the encapsulated TLV is continued in the following Extended
      Attribute; if the More flag is clear (0) then all of the
      encapsulated TLVs fit into the current Extended Attribute.  The
      More flag MUST NOT be set if the Extended Attribute contains more
      than one TLV.

  To be clear: this means that the Extended-Attribute can encapsulate
multiple TLV's if they're short, or only one TLV if it's long.


Section 5:

   M (More)

      The More Flag is one (1) bit in length and MUST be present.  When
      a value to be transmitted exceeds 246 octets in length it is
      fragmented over two or more Extended Attributes.  If the More Flag
      is set (1), this indicates that the Value field of the Extended
      Attribute contains a fragment of a larger value, which is
      continued in the next Extended Attribute of the same Ext-Type.

  Can we add a MUST?  i.e. If the More Flag is set, the next attribute
MUST be an Extended-Attribute of the same Extended-Type.

  Inserting *other* attributes in between a fragemented attribute is
annoying and pointless.  It's better to forbid this, and to declare that
packets failing this test are malformed, and SHOULD be silently discarded.

   Ext-Type

      Two (2) octets.  Up-to-date values of the Ext-Type field are
      specified in the most recent "Assigned Numbers" [IANA].  Values
      XXXX-YYYY are reserved.

  I would suggest reserving the top 1K: 64512-65535

6.  Examples

   Consider an attribute called Foo of type String.  Foo has been
   allocated an Extended-Type 0f 257 by IANA.  The following figure
   shows the encoding of Foo(0,4) = "Hello":

  What does "Foo(0,4)" mean?  This is the first reference in that
document to that attribute naming scheme.  (I presume it's an attribute
naming scheme).  Why not just refer to it as "Foo"?

  The diagram also has Ext-Type (16 bits) of 257 split between two bytes
(8 bits) of 0 and 257.  I welcome the novel ability to count to 257 in
an 8-bit field, but perhaps this could be corrected. :)

  The examples should use numbers from the reserved space (i.e. 64512),
and not from the IANA allocated space (257).  The examples also use the
attribute name "Foo" multiple times.  It should instead use unique names.

   Figure 2 below
   illustrates the encoding of the first 7 octets of the first Extended
   Attribute (Foo(0,6) = "Hello W"), while Figure 3 shows how the second
   attribute (Foo(246,250) = "e end.") is encoded.

  Hmm... So Foo(N,M) is a reference to the fragments?  I don't see why
this is necessary.  We don't do it for EAP-Message.  I would suggest
just referring to it as "Foo", and "the first fragment (octets 0 through
245)", and "the second fragment (octets 246 through 250).

...
   Consider the following structure:

     struct
       Integer a;
       String  b;
       Integer c;
     endStruct

  What syntax is this?  I think I understand it, but I'm not sure
everyone will come to a shared understanding.  Maybe instead the example
can be given by reference to existing RADIUS data types.  e.g. A
structure of RADIUS data types (integer, text, integer) would previously
have to be encoded as three separate and independent attributes.  Here,
it can be encoded as 3 attributes sharing a common tag.

  Reading the rest of the example, I find the b(4,5) syntax very
awkward.  I suggest discarding it, and just referring to the diagrams.

  The examples could also given broken-out hex encoding of the
attributes, which may be clearer than the ASCII art diagrams.  e.g.

  1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f

7.  Security Considerations

   I suggest adding a note that a new attribute encoding is an
opportunity for buffer overflows, inadequate checks, etc.  Implementors
SHOULD take care to validate the lengths, etc. before decoding the
contents of the attributes.

8.  IANA Considerations
...
   It also requires that IANA set up a new registry for the RADIUS
   Extended Attribute Types.

  I suggest leaving the first 0..255 attributes as unallocated, in order
to avoid confusion with legacy RADIUS attributes.


9.  Open Issues

   What is the numbering scheme for attributes that will be used by RFC
   writers going forward?  For example today we write user-name(1).

  Uh... We do?  I've never seen that in an RFC.  I suggest deleting this
section entirely.

  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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 02:20:00 +0000
Date: Wed, 13 Aug 2008 19:19:07 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: Re: no overall type in Extended Attributes
Message-ID: <Pine.LNX.4.64.0808131912120.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Glen Zorn said:

"As I mentioned a couple of times at the Dublin session, the current
definition of the Extended Attributes 
(http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-0
4.txt) doesn't in general allow the definition of an overall type for the
Attribute in question:  an Extended Attribute is basically just an 
unordered set of TLVs.  This fact doesn't bother me much, if at all, but 
the second time I mentioned it there was some grumbling from the crowd, so 
I thought I'd bring it up one more time on the list..."

One question is how the grouping semantic differs from that of Diameter 
(RFC 3588), and what the impact is.  Looking at RFC 3588, it does seem 
that the agbility to name and define a Grouped AVP has some advantages. 

For example, it enables a formal definition of the grouped AVP, including 
a grammar.  Without this, it is possible that the loose semantics would affect 
interoperability (e.g. arbitrary attribute groupings might not be 
supported understood).  

>From RFC 3588 Section 4.4:

4.4.  Grouped AVP Values

   The Diameter protocol allows AVP values of type 'Grouped.'  This
   implies that the Data field is actually a sequence of AVPs.  It is
   possible to include an AVP with a Grouped type within a Grouped type,
   that is, to nest them.  AVPs within an AVP of type Grouped have the
   same padding requirements as non-Grouped AVPs, as defined in Section
   4.

   The AVP Code numbering space of all AVPs included in a Grouped AVP is
   the same as for non-grouped AVPs.  Further, if any of the AVPs
   encapsulated within a Grouped AVP has the 'M' (mandatory) bit set,
   the Grouped AVP itself MUST also include the 'M' bit set.

   Every Grouped AVP defined MUST include a corresponding grammar, using
   ABNF [ABNF] (with modifications), as defined below.

      grouped-avp-def  = name "::=" avp

      name-fmt         = ALPHA *(ALPHA / DIGIT / "-")

      name             = name-fmt
                         ; The name has to be the name of an AVP,
                         ; defined in the base or extended Diameter
                         ; specifications.

      avp              = header  [ *fixed] [ *required] [ *optional]
                         [ *fixed]

      header           = "<" "AVP-Header:" avpcode [vendor] ">"

      avpcode          = 1*DIGIT
                         ; The AVP Code assigned to the Grouped AVP

      vendor           = 1*DIGIT
                         ; The Vendor-ID assigned to the Grouped AVP.
                         ; If absent, the default value of zero is
                         ; used.

4.4.1.  Example AVP with a Grouped Data type

   The Example-AVP (AVP Code 999999) is of type Grouped and is used to
   clarify how Grouped AVP values work.  The Grouped Data field has the
   following ABNF grammar:

      Example-AVP  ::= < AVP Header: 999999 >
                       { Origin-Host }
                     1*{ Session-Id }
                      *[ AVP ]

   An Example-AVP with Grouped Data follows.

   The Origin-Host AVP is required (Section 6.3).  In this case:

      Origin-Host = "example.com".

   One or more Session-Ids must follow.  Here there are two:

      Session-Id =
        "grump.example.com:33041;23432;893;0AF3B81"

      Session-Id =
        "grump.example.com:33054;23561;2358;0AF3B82"

   optional AVPs included are

      Recovery-Policy = <binary>
         2163bc1d0ad82371f6bc09484133c3f09ad74a0dd5346d54195a7cf0b35
         2cabc881839a4fdcfbc1769e2677a4c1fb499284c5f70b48f58503a45c5
         c2d6943f82d5930f2b7c1da640f476f0e9c9572a50db8ea6e51e1c2c7bd
         f8bb43dc995144b8dbe297ac739493946803e1cee3e15d9b765008a1b2a
         cf4ac777c80041d72c01e691cf751dbf86e85f509f3988e5875dc905119
         26841f00f0e29a6d1ddc1a842289d440268681e052b30fb638045f7779c
         1d873c784f054f688f5001559ecff64865ef975f3e60d2fd7966b8c7f92

      Futuristic-Acct-Record = <binary>
         fe19da5802acd98b07a5b86cb4d5d03f0314ab9ef1ad0b67111ff3b90a0
         57fe29620bf3585fd2dd9fcc38ce62f6cc208c6163c008f4258d1bc88b8
         17694a74ccad3ec69269461b14b2e7a4c111fb239e33714da207983f58c
         41d018d56fe938f3cbf089aac12a912a2f0d1923a9390e5f789cb2e5067
         d3427475e49968f841

   The data for the optional AVPs is represented in hex since the format
   of these AVPs is neither known at the time of definition of the
   Example-AVP group, nor (likely) at the time when the example instance
   of this AVP is interpreted - except by Diameter implementations which
   support the same set of AVPs.  The encoding example illustrates how
   padding is used and how length fields are calculated.  Also note that
   AVPs may be present in the Grouped AVP value which the receiver
   cannot interpret (here, the Recover-Policy and Futuristic-Acct-Record
   AVPs).

   This AVP would be encoded as follows:

           0       1       2       3       4       5       6       7
       +-------+-------+-------+-------+-------+-------+-------+-------+
     0 |     Example AVP Header (AVP Code = 999999), Length = 468      |
       +-------+-------+-------+-------+-------+-------+-------+-------+
     8 |     Origin-Host AVP Header (AVP Code = 264), Length = 19      |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    16 |  'e'  |  'x'  |  'a'  |  'm'  |  'p'  |  'l'  |  'e'  |  '.'  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    24 |  'c'  |  'o'  |  'm'  |Padding|     Session-Id AVP Header     |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    32 | (AVP Code = 263), Length = 50 |  'g'  |  'r'  |  'u'  |  'm'  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
    64 |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '1'  |Padding|Padding|
       +-------+-------+-------+-------+-------+-------+-------+-------+
    72 |     Session-Id AVP Header (AVP Code = 263), Length = 51       |
       +-------+-------+-------+-------+-------+-------+-------+-------+
    80 |  'g'  |  'r'  |  'u'  |  'm'  |  'p'  |  '.'  |  'e'  |  'x'  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
   104 |  '0'  |  'A'  |  'F'  |  '3'  |  'B'  |  '8'  |  '2'  |Padding|
       +-------+-------+-------+-------+-------+-------+-------+-------+
   112 |   Recovery-Policy Header (AVP Code = 8341), Length = 223      |
       +-------+-------+-------+-------+-------+-------+-------+-------+
   120 |  0x21 | 0x63  | 0xbc  | 0x1d  | 0x0a  | 0xd8  | 0x23  | 0x71  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
   320 |  0x2f | 0xd7  | 0x96  | 0x6b  | 0x8c  | 0x7f  | 0x92  |Padding|
       +-------+-------+-------+-------+-------+-------+-------+-------+
   328 | Futuristic-Acct-Record Header (AVP Code = 15930), Length = 137|
       +-------+-------+-------+-------+-------+-------+-------+-------+
   336 |  0xfe | 0x19  | 0xda  | 0x58  | 0x02  | 0xac  | 0xd9  | 0x8b  |
       +-------+-------+-------+-------+-------+-------+-------+-------+
                                     . . .
       +-------+-------+-------+-------+-------+-------+-------+-------+
   464 |  0x41 |Padding|Padding|Padding|
       +-------+-------+-------+-------+





--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 02:09:45 +0000
Date: Wed, 13 Aug 2008 19:08:57 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: Subject: I-D Action:draft-tiwari-radext-tunnel-type-01.txt (fwd)
Message-ID: <Pine.LNX.4.64.0808131907000.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.

	Title           : New Tunnel-Type Values
	Author(s)       : A. Tiwari
	Filename        : draft-tiwari-radext-tunnel-type-01.txt
	Pages           : 6
	Date            : 2008-08-10

This document defines a set of values for the Tunnel-Type RADIUS
Attribute.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-type-01.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.

<ftp://ftp.ietf.org/internet-drafts/draft-tiwari-radext-tunnel-type-01.txt>

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 02:07:34 +0000
Date: Wed, 13 Aug 2008 19:06:49 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: REMINDER: Request for Minutes, Slides
Message-ID: <Pine.LNX.4.64.0808131906300.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

If you took minutes at the RADEXT WG meeting at IETF 72, please send them 
to me (Bernard_Aboba@hotmail.com) and/or Dave Nelson. 

Also, if you presented and did not send slides, please do so. 

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 02:07:27 +0000
Date: Wed, 13 Aug 2008 19:06:24 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Message-ID: <Pine.LNX.4.64.0808131905510.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

This is a reminder of the RADEXT WG Last Call on "Extended 
RADIUS Attributes", prior to requesting that the IESG publish it as a Proposed Standard. 
 
The document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-04.txt
 
WG Last Call was originally to have completed on August 10, 2008.   
However, due to lack of response to the RADEXT WG last call, 
we will be extending the WG last call to August 31, 2008.  Please 
review the document and post your comments to the RADEXT WG mailing list 
(radiusext@ops.ietf.org) in the format described on the RADEXT WG Issues 
list (http://www.drizzle.com/~aboba/RADEXT/).   
 
If you have read the document and approve of its publication, but have no
comments, please also post this to the list. 

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Thu, 14 Aug 2008 02:07:19 +0000
Date: Wed, 13 Aug 2008 19:05:48 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Message-ID: <Pine.LNX.4.64.0808131904270.24114@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

This is a reminder of the ongoing RADEXT WG Last Call on "Crypto-Agility 
Requirements for RADIUS" prior to requesting that the IESG publish it as 
an Informational RFC. 
 
The document is available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-crypto-agility-requirements-00.txt
 
WG Last Call was to have lasted until August 10, 2008.   Since there 
have been no comments posted yet, we will extend the last call for 
another two weeks (until August 31, 2008).  Please 
review the document and post your comments to the RADEXT WG mailing list 
(radiusext@ops.ietf.org) in the format described on the RADEXT WG Issues 
list (http://www.drizzle.com/~aboba/RADEXT/).   
 
If you have read the document and approve of its publication, but have no
comments, please also post this to the list. 

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Tue, 12 Aug 2008 13:58:48 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Tue, 12 Aug 2008 20:55:50 +0700
Message-ID: <004201c8fc83$3b46a520$b1d3ef60$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj8cH7yvNkKOzRlSyubqA/JJgcYlQABvSrgAAKxtHA=
Content-Language: en-us

David B. Nelson <mailto://d.b.nelson@comcast.net>  writes:

> Glen Zorn writes...
> 
> > ...the current definition of the Extended Attributes
> > doesn't in general allow the definition of an overall type for the
> > Attribute in question: an Extended Attribute is basically just an
> > unordered set of TLVs.
> 
> In other words, the Extended Attribute is a "super attribute" or
> "wrapper
> attribute" that contains other "attributes", 

In other words, the Extended Attributes have the same qualities as RFC 2865
VSAs.

> which you refer to as
> "TLVs",
> to distinguish them from standalone attributes.
> 
> The issue is that one cannot "name" any particular group of aggregated
> TLVs.

I wouldn't call it an "issue" -- whether it's an issue is what is to be
determined.  It is a characteristic.

> One solution is to simply add a Group-Name TLV to the Extended
> Attribute.
> I'm not sure that addresses the intended use, however.  I suspect that
> the
> use is to "call up" a pre-defined grouping by name.

I don't know what use it would actually be, outside of making discussions of
the protocol a little easier.  It certainly doesn't modify the operation of
the protocol.

> 
> I think I'd like to see some "real-world" examples of use cases
> discussed
> here before I would want to attempt to make a decision on whether this
> is a
> serious issue or not.
> 
> 
> 
> --
> to unsubscribe send a message to 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-data@psg.com
Delivery-date: Tue, 12 Aug 2008 12:41:26 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: no overall type in Extended Attributes
Date: Tue, 12 Aug 2008 08:40:18 -0400
Message-ID: <016201c8fc78$94551c60$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
thread-index: Acj8cH7yvNkKOzRlSyubqA/JJgcYlQABvSrg

Glen Zorn writes...

> ...the current definition of the Extended Attributes
> doesn't in general allow the definition of an overall type for the
> Attribute in question: an Extended Attribute is basically just an
> unordered set of TLVs.

In other words, the Extended Attribute is a "super attribute" or "wrapper
attribute" that contains other "attributes", which you refer to as "TLVs",
to distinguish them from standalone attributes.

The issue is that one cannot "name" any particular group of aggregated TLVs.
One solution is to simply add a Group-Name TLV to the Extended Attribute.
I'm not sure that addresses the intended use, however.  I suspect that the
use is to "call up" a pre-defined grouping by name.

I think I'd like to see some "real-world" examples of use cases discussed
here before I would want to attempt to make a decision on whether this is a
serious issue or not.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Tue, 12 Aug 2008 11:45:16 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: no overall type in Extended Attributes
Date: Tue, 12 Aug 2008 18:42:28 +0700
Message-ID: <003b01c8fc70$8b64b9b0$a22e2d10$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acj8cH7yvNkKOzRlSyubqA/JJgcYlQ==
Content-Language: en-us

As I mentioned a couple of times at the Dublin session, the current
definition of the Extended Attributes 
(http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-0
4.txt) doesn't in general allow the definition of an overall type for the
Attribute in question:  an Extended Attribute is basically just an unordered
set of TLVs.  This fact doesn't bother me much, if at all, but the second
time I mentioned it there was some grumbling from the crowd, so I thought
I'd bring it up one more time on the list...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 10 Aug 2008 12:30:19 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sun, 10 Aug 2008 08:29:20 -0400
Message-ID: <005201c8fae4$b7d05370$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
thread-index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycAASi42wACM1RVAAAsiLQA==

Glen Zorn writes...

> In fact, it may fall apart at 35, since a NAS-Port-Type was
> assigned for PHS (AKA PIAFS) in RFC 2865...

And your point is that Next Generation PHS is not sufficiently
differentiated from PHS?  I think I might agree, on the general principle
that "next generation" is always relative, and what do you call the sequel?

So you've made a concrete and useful contribution to expert review.
Congratulations!

We should probably request that IANA list this entry as "PHS-MOU" and not
"Next Generation PHS".

As long as the nomenclature is unambiguous and there is some reference to a
specification, standards forum, corporation or individual that can be
contacted by anyone who really wants to know "What is this port type,
exactly?", I think it's fine.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 10 Aug 2008 11:16:03 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <d.b.nelson@comcast.net>
Cc: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sun, 10 Aug 2008 18:12:55 +0700
Message-ID: <000a01c8fada$19355800$4ba00800$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycAASi42wACM1RVA=
Content-Language: en-us

David B. Nelson writes:

> Glen Zorn writes...
> 
> > ...the difference between uranium-238 and u-235 certainly seems
> > subtle to me (what's a couple of neutrons between friends? ;-)
> > but is certainly not subtle to a modern physicist...
> 
> Sure.  However, if you need U-238, and get mislabeled U-235 by mistake,
> you
> may not be satisfied.
> 
> > I wonder how many other people on this list did?
> 
> I did.
> 
> > In fact, I'm still not sure what, exactly, makes it unique enough
> > to require a separate number but (given that there are 3,999,999,965
> > of them left) I really don't care.
> 
> Would you care if, say a million of so of them were all assigned for
> "IEEE
> Wireless"?  I'd find that horribly confusing.  All I'm looking for is
> enough
> review to make sure that the naming is sufficiently clear such that
> "caveat
> emptor" can reasonably apply.  

Since we're tripping the light fantastic here, the expert review process
falls apart with more than a few entries anyway (if there were only a
million port types it would take more than a month to _scan_ them @ 1/sec.,
8 hrs./day).  In fact, it may fall apart at 35, since a NAS-Port-Type was
assigned for PHS (AKA PIAFS) in RFC 2865...

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 09 Aug 2008 18:24:54 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sat, 9 Aug 2008 14:23:33 -0400
Message-ID: <000c01c8fa4d$0a0d2ac0$fefea8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
thread-index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycAASi42w

Glen Zorn writes...

> ...the difference between uranium-238 and u-235 certainly seems
> subtle to me (what's a couple of neutrons between friends? ;-)
> but is certainly not subtle to a modern physicist...

Sure.  However, if you need U-238, and get mislabeled U-235 by mistake, you
may not be satisfied.

> I wonder how many other people on this list did?

I did.

> In fact, I'm still not sure what, exactly, makes it unique enough
> to require a separate number but (given that there are 3,999,999,965
> of them left) I really don't care.

Would you care if, say a million of so of them were all assigned for "IEEE
Wireless"?  I'd find that horribly confusing.  All I'm looking for is enough
review to make sure that the naming is sufficiently clear such that "caveat
emptor" can reasonably apply.  Truth/accuracy in labeling.  If folks want to
get assignments for their "secret sauce" specialized flavors of ports, I
agree, there is no scarcity issue.  I think there is an accuracy of
nomenclature issue.  I don't think it's fair to require IANA to make that
judgment.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sat, 09 Aug 2008 10:06:32 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Sat, 9 Aug 2008 17:03:40 +0700
Message-ID: <002b01c8fa07$4236ecb0$c6a4c610$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vAAHfQycA==
Content-language: en-us

David B. Nelson <mailto://dnelson@elbrysnetworks.com> writes:

> Glen Zorn writes...
> 
> > I forgot: what is the rationale behind such careful rationing
> > of the 4 billion (!) NAS-Port-Type values again?
> 
> I don't think the value is in rationing.  As you point out, it's not an
> overly scarce resource.  I think the value is in maintaining a decent
> signal-to-noise ratio in the IANA registry.  Given that there are 4
> billion
> possible values, 

Micro-managing the namespace is a waste of time.

> it's preferable to avoid duplicates or nearly-
> duplicates
> with ambiguously subtle distinctions.

The level of distinction that is considered to be subtle tends to vary both
with the state of the art & the expertise of the observer: the difference
between uranium-238 and u-235 certainly seems subtle to me (what's a couple
of neutrons between friends? ;-) but is certainly not subtle to a modern
physicist & even less so to a maker of atomic bombs.  My point is that,
because NAS-Port-Type values generally represent L2 protocols, it is
somewhat likely that IETF "experts" will lack the expertise to make these
kinds of decisions in the exotic cases anyway.  The current request is a
case in point: I will admit that I had no idea what PHS was (let alone
PHS-MoU) until I went off to the Web site to check.  I wonder how many other
people on this list did?  In fact, I'm still not sure what, exactly, makes
it unique enough to require a separate number but (given that there are
3,999,999,965 of them left) I really don't care.

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 08 Aug 2008 19:11:48 +0000
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Fri, 8 Aug 2008 15:09:57 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <8988E09E29584BE3918E25B4173305E3@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQAB0e7vA=

Glen Zorn writes...

> I forgot: what is the rationale behind such careful rationing
> of the 4 billion (!) NAS-Port-Type values again?

I don't think the value is in rationing.  As you point out, it's not an
overly scarce resource.  I think the value is in maintaining a decent
signal-to-noise ratio in the IANA registry.  Given that there are 4 billion
possible values, it's preferable to avoid duplicates or nearly-duplicates
with ambiguously subtle distinctions.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 08 Aug 2008 14:17:36 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=an/9L45pKEc3ADml82AS774Nh9xhQRsOesQopASZ0Lc=; b=oLZWg79cDqvHN9CXX2nbkVWjkaI7k9Esy439PXPKXDHFpfxJKcDt2Lq2MoWHxVRtbE vTGA5csAYC0aq5X/Mn/idZUh6QAmnFwWc/M14rO93Zm69m2vSjX7YqFFpMlNgRESo7R2 zwSl4d8DUlum4rldY2FcU750RPsuCb9wIeQLU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=mSpTdKuYrY1bm/it88EFTOdO1GY4KvrLql3gYoEasYw/B8Ve9/VTWyQujnc9/Il3Ln 7i28WfCKNCc90du5pu1ktWLT9CILmsLAFL9RRDCO+E1m7VsH1Qmrgw/3xKVtoO5WxWXb +0rQDdqNPbLlB6PH+wss44GdhXF4kGxMAPNDY=
Message-ID: <c3a174020808080716u3e7635d7x2068d0afeadfb468@mail.gmail.com>
Date: Fri, 8 Aug 2008 11:16:16 -0300
From: "Claudio Lapidus" <clapidus@gmail.com>
To: "Glen Zorn" <glenzorn@comcast.net>, "Bernard Aboba" <aboba@internaut.com>,  radiusext@ops.ietf.org
Subject: Re: Request for NAS-Port-Type Allocation
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, Aug 8, 2008 at 2:16 AM, Glen Zorn <glenzorn@comcast.net> wrote:
> what is the
> rationale behind such careful rationing of the 4 billion (!) NAS-Port-Type
> values again?

Hmm, perhaps is it that every new value will need to be properly
understood by all existing implementations, which in turn will need to
be retrofitted to handle it?

regards,
cl.

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 08 Aug 2008 05:18:33 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Fri, 8 Aug 2008 12:16:33 +0700
Message-ID: <006601c8f915$f4055a00$dc100e00$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
thread-index: Acjzr2Knd/gpPYOjRumill4S1vKVtgFZcYuQ
Content-Language: en-us

Bernard Aboba <mailto://aboba@internaut.com> writes:

> The IANA has received a request for a new NAS-Port-Type allocation.  As
> stated in RFC 3575, Section 2.1:
> 
>    Certain attributes (for example, NAS-Port-Type) in RADIUS define a
>    list of values to correspond with various meanings.  There can be 4
>    billion (2^32) values for each attribute.  Additional values can be
>    allocated by the Designated Expert.  The exception to this policy is
>    the Service-Type attribute (6), whose values define new modes of
>    operation for RADIUS.  Values 1-16 of the Service-Type attribute
> have
>    been allocated.  Allocation of new Service-Type values are by IETF
>    Consensus.  The intention is that any allocation will be accompanied
>    by a published RFC.
> 
> Are there any objections to granting the allocation as requested below?

My only objection is to being bothered with it ;-).  I forgot: what is the
rationale behind such careful rationing of the 4 billion (!) NAS-Port-Type
values again?

...



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Sun, 03 Aug 2008 15:28:48 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Bernard Aboba <aboba@internaut.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Sun, 3 Aug 2008 11:27:02 -0400
Subject: RE: Request for NAS-Port-Type Allocation
Thread-Topic: Request for NAS-Port-Type Allocation
Thread-Index: Acjzrww/JniR9YHcSBKqpH+cS5HpwwBzlTcy
Message-ID: <8A8CFE8F89C38B41A749C19328C76D6308A058A024@exchange02.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

Looks fine to me as well.

________________________________________
From: owner-radiusext@ops.ietf.org [owner-radiusext@ops.ietf.org] On Behalf=
 Of Bernard Aboba [aboba@internaut.com]
Sent: Friday, August 01, 2008 4:14 AM
To: radiusext@ops.ietf.org
Subject: Request for NAS-Port-Type Allocation

The IANA has received a request for a new NAS-Port-Type allocation.  As
stated in RFC 3575, Section 2.1:

   Certain attributes (for example, NAS-Port-Type) in RADIUS define a
   list of values to correspond with various meanings.  There can be 4
   billion (2^32) values for each attribute.  Additional values can be
   allocated by the Designated Expert.  The exception to this policy is
   the Service-Type attribute (6), whose values define new modes of
   operation for RADIUS.  Values 1-16 of the Service-Type attribute have
   been allocated.  Allocation of new Service-Type values are by IETF
   Consensus.  The intention is that any allocation will be accompanied
   by a published RFC.

Are there any objections to granting the allocation as requested below?

Contact Name :
Tomohiro Ichida

Contact Email :
t_ichida@willcom-inc.com

Type of Assignment :
I request the allocation of new NAS-Port-TYPE.

http://www.iana.org/assignments/radius-types
Values for RADIUS Attribute 61, NAS-Port-Type [RFC2865]:

Registry :
The value is "Wireless - XGP"

Description :
There is a standardization organization as PHS-MOU.
We'd like to prescribe the new number in NAS-PORT-TYPE.
And We'd like to use its number by the next generation PHS system.
it is same as "Wireless - CDMA2000","Wireless - IEEE 802.16"

PHS-MOU is explained as follows this URL
 http://www.phsmou.org/

Additional Info :
 The "Next Generation PHS" specification is is being made.
 A document is not open to the public,sorry.

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 01 Aug 2008 12:40:58 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] draft-lourdelet-radext-ipv6-dhcp-00 published
Date: Fri, 1 Aug 2008 14:40:03 +0200
Message-ID: <A05118C6DF9320488C77F3D5459B17B707E50CE4@xmb-ams-333.emea.cisco.com>
Thread-Topic: [dhcwg] draft-lourdelet-radext-ipv6-dhcp-00 published
Thread-Index: AcjyUC6ylRNCKry7R6KCPBISPaTeWwBgyt2w
From: "Benoit Lourdelet (blourdel)" <blourdel@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, <dhcwg@ietf.org>, <radiusext@ops.ietf.org>
Cc: <gwz@netcube.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1474; t=1217594371; x=1218458371; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=blourdel@cisco.com; z=From:=20=22Benoit=20Lourdelet=20(blourdel)=22=20<blourdel@ cisco.com> |Subject:=20RE=3A=20[dhcwg]=20draft-lourdelet-radext-ipv6-d hcp-00=20published |Sender:=20; bh=Ogs/0GMvXFuh8jZ2LUAvQimJUqaDtdsfowHioisT+58=; b=I6eQ5/K7RqqKgIlr9VF0mBra0nqjRMlHptut2k92+NNw4DKHRE97HwujgF nW5aTtj+sFZ7j4+IG2+7ALxzNbcDoVeTtgrirs6DqAbUXtXVYWkxx8ECaRCI 8i+zDJg2sA;
Authentication-Results: ams-dkim-2; header.From=blourdel@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );

FYI,

This individual work will be included in a revision of RFC3162 that Glen
Zorn and I are going to work on.


Regards

Benoit

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms (rdroms)
Sent: Wednesday, July 30, 2008 4:23 PM
To: dhcwg@ietf.org; radiusext@ops.ietf.org
Subject: Re: [dhcwg] draft-lourdelet-radext-ipv6-dhcp-00 published

Correction.  On a link with no router advertisements you need to
configure any addresses and prefixes manually and separately.

There is no expectation that the prefix from an assigned address is
necessarily on the link.  On-link prefixes are independent from assigned
addresses.

- Ralph

On Jul 30, 2008, at 8:01 AM, Hemant Singh (shemant) wrote:
>> What about the scenario where there is no router in the network or=20
>> not
> announcing router advertisement with prefix options? What length of=20
> prefix the >DHCPv6 client should use for address assignment?
>
>> Best Regards,
>> 	Janos
>
>
>
> There is no provision in DHCPv6 to include prefix length in a message=20
> to the client - I have said so several times to the DHCPv6 mailer. =20
> Check the email archives.  In a router-less network, you are hosed. =20
> You have to configure an address and prefix length manually.
>
> Hemant

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

--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 01 Aug 2008 11:22:54 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: Request for NAS-Port-Type Allocation
Date: Fri, 1 Aug 2008 07:21:47 -0400
Message-ID: <05b401c8f3c8$c9638350$6401a8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: Acjzr2Kn0c/WA3wOSYyrkViaWZSahgAGUDwQ

Bernard Aboba writes...

> Are there any objections to granting the allocation as requested below?

None from me.



--
to unsubscribe send a message to 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-data@psg.com
Delivery-date: Fri, 01 Aug 2008 08:36:38 +0000
Message-ID: <4892CAB6.1040200@deployingradius.com>
Date: Fri, 01 Aug 2008 10:35:02 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080502)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
CC: radiusext@ops.ietf.org
Subject: Re: Request for NAS-Port-Type Allocation
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Are there any objections to granting the allocation as requested below?

  It looks fine to me.

  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-data@psg.com
Delivery-date: Fri, 01 Aug 2008 08:15:58 +0000
Date: Fri, 1 Aug 2008 01:14:29 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: Request for NAS-Port-Type Allocation
Message-ID: <Pine.LNX.4.64.0808010108130.3452@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

The IANA has received a request for a new NAS-Port-Type allocation.  As 
stated in RFC 3575, Section 2.1:

   Certain attributes (for example, NAS-Port-Type) in RADIUS define a
   list of values to correspond with various meanings.  There can be 4
   billion (2^32) values for each attribute.  Additional values can be
   allocated by the Designated Expert.  The exception to this policy is
   the Service-Type attribute (6), whose values define new modes of
   operation for RADIUS.  Values 1-16 of the Service-Type attribute have
   been allocated.  Allocation of new Service-Type values are by IETF
   Consensus.  The intention is that any allocation will be accompanied
   by a published RFC.

Are there any objections to granting the allocation as requested below?

Contact Name :
Tomohiro Ichida

Contact Email :
t_ichida@willcom-inc.com

Type of Assignment :
I request the allocation of new NAS-Port-TYPE.

http://www.iana.org/assignments/radius-types
Values for RADIUS Attribute 61, NAS-Port-Type [RFC2865]:

Registry :
The value is "Wireless - XGP"

Description :
There is a standardization organization as PHS-MOU.
We'd like to prescribe the new number in NAS-PORT-TYPE.
And We'd like to use its number by the next generation PHS system.
it is same as "Wireless - CDMA2000","Wireless - IEEE 802.16"

PHS-MOU is explained as follows this URL
 http://www.phsmou.org/

Additional Info :
 The "Next Generation PHS" specification is is being made.
 A document is not open to the public,sorry.

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

