
From owner-radiusext@ops.ietf.org  Tue Feb  2 12:01:21 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6834028C0D7 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  2 Feb 2010 12:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.456
X-Spam-Level: 
X-Spam-Status: No, score=-105.456 tagged_above=-999 required=5 tests=[AWL=1.143, 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 f9v2FDwd0SBi for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  2 Feb 2010 12:01:20 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id E464D28C100 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  2 Feb 2010 12:01:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NcOtz-000080-EU for radiusext-data0@psg.com; Tue, 02 Feb 2010 19:59:11 +0000
Received: from [64.140.243.164] (helo=gumby.elbrysnetworks.com) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <dnelson@elbrysnetworks.com>) id 1NcOtw-00006A-9B for radiusext@ops.ietf.org; Tue, 02 Feb 2010 19:59:09 +0000
Received: (qmail 5178 invoked from network); 2 Feb 2010 19:58:58 -0000
Received: from dbn-imac.elbrysnetworks.com (172.22.19.12) by gumby.elbrysnetworks.com with SMTP; 2 Feb 2010 19:58:58 -0000
Cc:  <radiusext@ops.ietf.org>
Message-Id: <E52BFEA6-E4F6-46EA-B7B2-E449254CF30B@elbrysnetworks.com>
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
In-Reply-To: <BLU137-DS32C5AC85D3BBB6E7EB021935B0@phx.gbl>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Doodle: RADEXT Virtual Interim
Date: Tue, 2 Feb 2010 14:58:58 -0500
References: <808309809.21681.1264701333703.JavaMail.doodle@worker1> <4B61F28E.1000203@deployingradius.com> <BLU137-DS32C5AC85D3BBB6E7EB021935B0@phx.gbl>
X-Mailer: Apple Mail (2.936)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On Jan 28, 2010, at 7:46 PM, Bernard Aboba wrote:

> I have gotten some reports that the DOODLE link for the RADEXT  
> Virtual Interim is behaving strangely.
>
> Try this link instead:
> http://www.doodle.com/9huzzmkgi4vrvvrm

That doesn't seem to work better.  The first "invite" sent to the list  
had already been "consumed" by Dan R. and the second "invite" didn't  
appear to be a valid "invite" .  The web site says to contact Bernard  
for an "invite" to add to the poll.



--
to unsubscribe send a message to 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 Feb  2 13:35:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 424043A6972 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  2 Feb 2010 13:35:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.495
X-Spam-Level: 
X-Spam-Status: No, score=-103.495 tagged_above=-999 required=5 tests=[AWL=1.244, BAYES_20=-0.74, HTML_MESSAGE=0.001, 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 5o4BBuxzbM8o for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue,  2 Feb 2010 13:35:32 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id 512AD3A6765 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue,  2 Feb 2010 13:35:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NcQJw-000GOj-Jn for radiusext-data0@psg.com; Tue, 02 Feb 2010 21:30:04 +0000
Received: from [65.55.116.14] (helo=blu0-omc1-s3.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NcQJu-000GOB-DQ for radiusext@ops.ietf.org; Tue, 02 Feb 2010 21:30:02 +0000
Received: from BLU137-DS5 ([65.55.116.7]) by blu0-omc1-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Feb 2010 13:30:01 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS5117ABCDA9D26AC23808593570@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: New Doodle Poll on RADEXT Virtual Interim
Date: Tue, 2 Feb 2010 13:30:39 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0378_01CAA40B.E917FF60"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqkTvbzttsXRkCcS5qjeTznqb3oDA==
Content-Language: en-us
X-OriginalArrivalTime: 02 Feb 2010 21:30:01.0426 (UTC) FILETIME=[E07E5320:01CAA44E]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0378_01CAA40B.E917FF60
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Here is a link to a new Doodle poll for the RADEXT Virtual Interim.  Due to
the two week notice requirement, the new poll is for the week of February
22-26, 2010. 

 

Doodle Poll:

http://www.doodle.com/pc9p7y4dfb6fz48w

 

 


------=_NextPart_000_0378_01CAA40B.E917FF60
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>Here is a link to a new Doodle poll for the RADEXT =
Virtual
Interim.&nbsp; Due to the two week notice requirement, the new poll is =
for the week
of February 22-26, 2010. <o:p></o:p></p>

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

<p class=3DMsoNormal>Doodle Poll:<o:p></o:p></p>

<p class=3DMsoNormal><a =
href=3D"http://www.doodle.com/pc9p7y4dfb6fz48w">http://www.doodle.com/pc9=
p7y4dfb6fz48w</a><o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_0378_01CAA40B.E917FF60--

--
to unsubscribe send a message to 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 Feb  3 15:04:50 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B1763A69A3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 15:04:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.231
X-Spam-Level: 
X-Spam-Status: No, score=-0.231 tagged_above=-999 required=5 tests=[AWL=-2.151, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-vVfFNlTx5I for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 15:04:47 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 551213A6996 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  3 Feb 2010 15:04:47 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NcoDa-0008a7-RC for radiusext-data0@psg.com; Wed, 03 Feb 2010 23:01:06 +0000
Received: from [65.55.116.21] (helo=blu0-omc1-s10.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NcoDW-0008ZU-PE for radiusext@ops.ietf.org; Wed, 03 Feb 2010 23:01:02 +0000
Received: from BLU137-DS6 ([65.55.116.8]) by blu0-omc1-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Feb 2010 15:01:02 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS60EA45DB6619AE83D9CD693560@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: REMINDER:  Doodle Poll for RADEXT Virtual Interim Meeting
Date: Wed, 3 Feb 2010 15:01:01 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01CAA4E1.B3973AF0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqlJMGBswPppdhkSQKp4Ia3o90Sjg==
Content-Language: en-us
X-OriginalArrivalTime: 03 Feb 2010 23:01:02.0215 (UTC) FILETIME=[C1CA5970:01CAA524]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_003B_01CAA4E1.B3973AF0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

RADEXT WG is going to hold a Virtual Interim meeting the week of February
22, 2010.   If you haven't already done so, please fill in your potentially
available times:

http://www.doodle.com/pc9p7y4dfb6fz48w

 

The major topic of discussion for the Virtual Interim  will be resolving the
"Last Look" comments on the Design Guidelines document.   


------=_NextPart_000_003B_01CAA4E1.B3973AF0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>RADEXT WG is going to hold a Virtual Interim =
meeting the
week of February 22, 2010.&nbsp;&nbsp; If you haven&#8217;t already done =
so, please fill
in your potentially available times:<o:p></o:p></p>

<p class=3DMsoNormal><a =
href=3D"http://www.doodle.com/pc9p7y4dfb6fz48w">http://www.doodle.com/pc9=
p7y4dfb6fz48w</a><o:p></o:p></p>

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

<p class=3DMsoNormal>The major topic of discussion for the Virtual =
Interim&nbsp; will
be resolving the &#8220;Last Look&#8221; comments on the Design =
Guidelines document.&nbsp;&nbsp;
<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_003B_01CAA4E1.B3973AF0--

--
to unsubscribe send a message to 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 Feb  3 16:20:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D697D3A689C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 16:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.385
X-Spam-Level: 
X-Spam-Status: No, score=-1.385 tagged_above=-999 required=5 tests=[AWL=-0.891, 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 vDg00xs5WLOE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 16:20:19 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 414DE3A67AD for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  3 Feb 2010 16:20:18 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NcpQ0-000IGH-Si for radiusext-data0@psg.com; Thu, 04 Feb 2010 00:18:00 +0000
Received: from [65.55.116.32] (helo=blu0-omc1-s21.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NcpPl-000IEe-65 for radiusext@ops.ietf.org; Thu, 04 Feb 2010 00:17:45 +0000
Received: from BLU137-DS1 ([65.55.116.7]) by blu0-omc1-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Feb 2010 16:17:44 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS1E00B50A4DE6656D314EB93550@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-tcp-transport (Part I)
Date: Wed, 3 Feb 2010 16:17:43 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0066_01CAA4EC.6A4F27D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqlL3gql8AYAuqeR7CGu3QgwGzRQw==
Content-Language: en-us
X-OriginalArrivalTime: 04 Feb 2010 00:17:44.0158 (UTC) FILETIME=[78C31FE0:01CAA52F]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0066_01CAA4EC.6A4F27D0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Section 1

 

      Transport of fragmented UDP packets

      appears to be a poorly tested code path on network devices.  Some

      devices appear to be incapable of transporting fragmented UDP

      packets, making it difficult to deploy RADIUS in a network where

      those devices are deployed.

 

[BA] In particular, filters routers and firewalls often drop UDP fragments,
since otherwise they would need to reassemble them in order to apply the
filter rules. 

However, this is not a "transport" issue, so much as a forwarding/filtering
issue.  Instead of "Transport" you might say "handling". 

 

 

      * Connectionless transport.  Neither clients nor servers receive
      positive statements that a "connection" is down.  This information
      has to be deduced instead from the absence of a reply to a
      request.

 

[BA] The same thing is also true of TCP transport, unless you're willing to
wait for a Reset or connection timeout.  That's why the Watchdog timer is
needed. 

 

   As RADIUS is widely deployed, and has been widely deployed for well
   over a decade, these issues have been minor in some use-cases, and
   problematic in others..  New systems may be interested in choosing a
   different set of trade-offs than those outlined in [RFC2865
<http://tools.ietf.org/html/rfc2865> ] Section
   2.4.  New systems may also be interested in choosing a more reliable
   transport for use-cases such as inter-server proxying.  For those
   systems, we define RADIUS over TCP

 

[BA] Note double periods in first sentence, and no period in the last
sentence.  As I read the document, it is really only suggesting a different
set of tradeoffs for inter-server proxying.  So you might say "For use-cases
such as inter-server proxying, [RTLS] suggests an alternative transport and
security model -- RADIUS over TLS.  This document describes the transport
implications of running RADIUS over TLS/TCP."

 


1.1.  Applicability of Reliable Transport

 
 
   The intent of this document is to address transport issues related to
   RADIUS over TLS [RTLS
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport-04#ref-RTLS> ].
The use of "bare" TCP transport (i.e.
   without TLS) is NOT RECOMMENDED, as there has been little
   implementational or operational experience with it.  Additionally,
   [RFC2865] Section <http://tools.ietf.org/html/rfc2865#section-2.4>  2.4
contains a list of reasons why UDP was
   originally chosen as the transport protocol for RADIUS.  UDP SHOULD
   be used as transport protocol in all cases where the rationale given
   in [RFC2865] Section <http://tools.ietf.org/html/rfc2865#section-2.4>
2.4 applies.
 
   Deployment experience with RADIUS over TLS indicates that it is most
   useful for inter-server communication, such as inter-domain
   communication between proxies.  These situations benefit from the
   confidentiality and ciphersuite negotiation that can be provided by
   TLS. Since TLS is already widely available within the operating
   systems used by proxies, implementation barriers are low.
 
   RADIUS over TCP has a similar set of use cases.  Use of TCP as a
   transport between a NAS and RADIUS server is a poor fit, since as
   noted in [RFC3539 <http://tools.ietf.org/html/rfc3539> ], there is likely
to be insufficient traffic for
   the congestion window to remain above the minimum value on a long-
   term basis.  The result is an increase in packets due to ACKs as
   compared to UDP, without a corresponding set of benefits.
 
   In server-server communications the traffic levels in both directions
   are typically high enough to support a larger congestion window as
   well as ACK piggy-backing.  Through use of an application-layer
   watchdog as described in [RFC3539 <http://tools.ietf.org/html/rfc3539> ],
it is possible to address the
   objections to reliable transport described in [RFC2865] Section
<http://tools.ietf.org/html/rfc2865#section-2.4>  2.4.
   However, in these scenarios "bare" TCP does not provide for
   confidentiality or enable negotiation of stronger ciphersuites than
   are available in RADIUS.
 
   As a result of these considerations, use of RADIUS over TCP SHOULD be
   restricted to situations where RADIUS over TLS is employed.  RADIUS
   over "bare" TCP is NOT RECOMMENDED.
 
   There are still a number of benefits to using a reliable transport.
   For example, when RADIUS is used to carry EAP conversions [RFC3579
<http://tools.ietf.org/html/rfc3579> ],
   the EAP exchanges may involve 5 round trips at the RADIUS application
   layer.  We may assume a probability P of packet loss in each
   direction (with P having a value of 1% or less).  Any one
   authentication attempt will then have at least one lost packet, with
   a probability of approximately (10 * P).
 
   These lost packets require the supplicant and/or the NAS to re-
   transmit packets at the application layer.  The difficulty with this
   approach is that retransmission implementations have historically
   been poor.  Some implementations retransmit packets, others do not,
   and others send new packets rather then performing retransmission.
   Some implementations are incapable of detecting EAP retransmissions,
   and will instead treat the retransmitted packet as an error.
 
   These retransmissions have a high likelihood of causing the entire
   authentication session to fail.  For a system with a million logins a
   day, and having a packet loss probability of P=0.01%, we expect that
   0.1% of connections will experience a lost packet.  That is, 1,000
   user sessions each day will experience authentication failure.
 
   In addition, transport of fragmented UDP packets is a poorly tested
   code path on network devices.  Some devices appear to be incapable of
   transporting fragmented UDP packets, meaning that the packet loss
   rate for fragmented packets approaches 100 percent.  The net effect
   can be to prevent the deployment of authentication methods such as
   EAP-TLS that require large RADIUS packets.
 
   Using a reliable transport method such as TCP means that RADIUS
   implementations can remove all application-layer retransmissions, and
   instead rely on the Operating System (OS) kernel's well-tested TCP
   transport to ensure reliable delivery.  In addition, most TCP
   implementations discover Path MTU better than RADIUS application
   implementations, resulting in significantly fewer fragmented packets.
   Modern TCP implementations also implement anti-spoofing provisions,
   which is more difficult to do in UDP applications.
 
   Transporting RADIUS over TCP means that the RADIUS applications can
   leverage these additional protections offered by TCP.
 
   However, there are also some drawbacks to using TCP.  RADIUS over TCP
   has some drawbacks, as noted in [RFC2865] Section
<http://tools.ietf.org/html/rfc2865#section-2.4>  2.4.  [RFC3539]
<http://tools.ietf.org/html/rfc3539#section-2> 
 <http://tools.ietf.org/html/rfc3539#section-2>    Section 2 discusses
further issues with using TCP as a transport for
   Authentication, Authorization, and/or Accounting (AAA) protocols such
   as RADIUS.
 
   Specifically, as noted in [RFC3539] Section
<http://tools.ietf.org/html/rfc3539#section-2.1>  2.1, for systems
   originating low numbers of RADIUS request packets, inter-packet
   spacing is often larger than the packet RTT.  In those situations,
   RADIUS over TCP SHOULD NOT be used.
 
   In general, RADIUS clients generating small amounts of RADIUS traffic
   SHOULD NOT use TCP.  This suggestion will usually apply to most
   NASes, and to most clients that originate CoA-Request and Disconnect-
   Request packets.
 
   RADIUS over TCP is most applicable to RADIUS proxies that exchange a
   large volume of packets with RADIUS clients and servers (10's to
   1000's of packets per second).  In those situations, RADIUS over TCP
   may be a good fit, and may result in increased network stability and
   performance.

 

[BA]  Suggested rewrite:

 

Section 1.1

 

   The intent of this document is to address transport issues related to

   RADIUS over TLS [RTLS] in inter-server communications scenarios, 

   such as inter-domain communication between proxies.  These 

   situations benefit from the confidentiality and ciphersuite 

   negotiation that can be provided by TLS. Since TLS is already 

   widely available within the operating systems used by proxies, 

   implementation barriers are low.  

 

   In scenarios where RADIUS proxies exchange a large volume of

   packets (10+ packets per second), it is likely that there will be
sufficient

   traffic to enable the congestion window to be widened beyond

   the minimum value on a long-term basis, enabling ACK piggy-backing. 

   Through use of an application-layer watchdog as described in [RFC3539], 

   it is possible to address the objections to reliable transport 

   described in [RFC2865] Section 2.4 without substantial

   watchdog traffic, since regular traffic is expected in both 

   directions.  

 

   In addition, use of RADIUS over TLS/TCP has been found to

   improve operational performance when used with multi-round

   trip authentication mechanisms such as RADIUS over EAP [RFC3579].

   In such exchanges, it is typical for EAP fragmentation to

   increase the number of round-trips required.  For example, where

   EAP-TLS authentication [RFC5216] is attempted and both the EAP

   peer and server utilize certificate chains of 8KB, as many as

   15 round-trips can be required if RADIUS packets are restricted

   to 1500 octets in size.  Fragmentation of RADIUS over UDP packets

   is generally inadvisable due to lack of fragmentation support 

   within intermediate devices such as filtering routers, firewalls 

   and NATs.  However, since RADIUS over UDP implementations typically do

   not support MTU discovery, fragmentation can occur even when the

   maximum RADIUS over UDP packet size is restricted to 1500 octets. 

 

   These problems disappear if a 4096 application-layer payload

   can be used alongside RADIUS over TLS/TCP.  Since most TCP

   implementations support MTU discovery, the TCP MSS is automatically

   adjusted to account for the MTU, and the larger congestion

   window supported by TCP may allow multiple TCP segments to

   be sent within a single window.  As a result, RADIUS/EAP

   traffic required for an EAP-TLS authentication with 8KB

   certificate chains may be reduced to 7 round-trips or less, 

   resulting in substantially reduced authentication times. 

 

   In addition, experience indicates that EAP sessions transported 

   over RTLS are less likely to abort unsuccessfully.  Historically,

   RADIUS over UDP implementations have exhibited poor retransmission

   behavior.  Some implementations retransmit packets, others do not,

   and others send new packets rather then performing retransmission.

   Some implementations are incapable of detecting EAP retransmissions,

   and will instead treat the retransmitted packet as an error.  

   As a result, within RADIUS over UDP implementations, retransmissions

   have a high likeilhood of causing an EAP authentication session

   to fail.  For a system with a million logins a day running EAP-TLS

   mutual authentication with 15 round-trips, and having a packet loss 

   probability of P=0.01%, we expect that 0.3% of connections will
experience 

   at least one lost packet.  That is, 3,000 user sessions each day 

   will experience authentication failure.  This is an unacceptable

   failure rate for a mass-market network service. 

 

   Using a reliable transport method such as TCP means that RADIUS

   implementations can remove all application-layer retransmissions, and

   instead rely on the Operating System (OS) kernel's well-tested TCP

   transport to ensure reliable delivery.  In addition, most TCP

   implementations discover Path MTU better than RADIUS application

   implementations, resulting in significantly fewer fragmented packets.

   Modern TCP implementations also implement anti-spoofing provisions,

   which is more difficult to do in UDP applications.

 

   In contrast, use of TLS/TCP as a transport between a NAS and a 

   RADIUS server is a poor fit.  As noted in [RFC3539] Section 2.1, 

   for systems originating low numbers of RADIUS request packets, 

   inter-packet spacing is often larger than the packet RTT, and

   as a result, the congestion window will t ypically not remain

   above the minimum value on a long-term basis. The 

   result is an increase in packets due to ACKs as compared to UDP, 

   without a corresponding set of benefits.  In addition, the lack

   of substantial traffic implies the need for additional watchdog

   traffic to confirm reachability.  

 

   As a result, the objections to reliable transport indicated in 

   [RFC2865] Section 2.4 continue to apply to NAS-RADIUS server 

   communications and UDP SHOULD continue to be used as the transport 

   protocol in this scenario.  In addition, it is recommended that

   implementations of "RADIUS Dynamic AUthorization Extensions" [RFC5176]

   SHOULD continue to utilize UDP transport, since the volume of

   dynamic authorization traffic is usually expected to be small.  

 

   Since "bare" TCP does not provide for confidentiality or enable 

   negotiation of credible ciphersuites, its use is not appropriate for 

   inter-server communications where strong security is required.  As a
result 

   the use of "bare" TCP transport (i.e. without TLS) is NOT RECOMMENDED 

   for use in any situation, and there has been little or no

   operational experience with it.

 

 


------=_NextPart_000_0066_01CAA4EC.6A4F27D0
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:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.grey
	{mso-style-name:grey;}
.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>

<p class=3DMsoNormal>Section 1<o:p></o:p></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Transport of fragmented UDP packets<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
appears to be a poorly tested code path on network devices.&nbsp; =
Some<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
devices appear to be incapable of transporting fragmented =
UDP<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
packets, making it difficult to deploy RADIUS in a network =
where<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
those devices are deployed.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] In particular, =
filters routers
and firewalls often drop UDP fragments, since otherwise they would need =
to
reassemble them in order to apply the filter rules. =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>However, this is =
not a &#8220;transport&#8221;
issue, so much as a forwarding/filtering issue.&nbsp; Instead of =
&#8220;Transport&#8221;
you might say &#8220;handling&#8221;. <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * =
Connectionless transport.&nbsp; Neither clients nor servers =
receive<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; positive =
statements that a &quot;connection&quot; is down.&nbsp; This =
information<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has to be =
deduced instead from the absence of a reply to =
a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
request.<o:p></o:p></span></pre>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] The same thing =
is also
true of TCP transport, unless you&#8217;re willing to wait for a Reset =
or connection
timeout. &nbsp;That&#8217;s why the Watchdog timer is needed. =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; As RADIUS is widely deployed, =
and has been widely deployed for well<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; over a decade, these issues have =
been minor in some use-cases, and<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; problematic in others..&nbsp; =
New systems may be interested in choosing a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; different set of trade-offs than =
those outlined in [<a
href=3D"http://tools.ietf.org/html/rfc2865"
title=3D"&quot;Remote Authentication Dial In User Service =
(RADIUS)&quot;">RFC2865</a>] Section<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 2.4.&nbsp; New systems may also =
be interested in choosing a more reliable<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transport for use-cases such as =
inter-server proxying.&nbsp; For those<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; systems, we define RADIUS over =
TCP<o:p></o:p></span></pre>

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

<p class=3DMsoNormal>[BA] Note double periods in first sentence, and no =
period in
the last sentence.&nbsp; As I read the document, it is really only =
suggesting a
different set of tradeoffs for inter-server proxying.&nbsp; So you might =
say &#8220;For
use-cases such as inter-server proxying, [RTLS] suggests an alternative =
transport
and security model -- RADIUS over TLS. &nbsp;This document describes the
transport implications of running RADIUS over =
TLS/TCP.&#8221;<o:p></o:p></p>

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

<h3 style=3D'page-break-before:always'><a name=3Dsection-1.1><span =
lang=3DEN
style=3D'font-size:10.0pt'>1.1</span></a><span lang=3DEN =
style=3D'font-size:10.0pt'>.&nbsp;
Applicability of Reliable Transport<o:p></o:p></span></h3>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; The intent of this document is =
to address transport issues related to<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TLS [<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport-04#ref=
-RTLS"
title=3D"&quot;TLS encryption for RADIUS over TCP =
(RadSec)&quot;">RTLS</a>].&nbsp; The use of &quot;bare&quot; TCP =
transport (i.e.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; without TLS) is NOT RECOMMENDED, =
as there has been little<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementational or operational =
experience with it.&nbsp; Additionally,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; <a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a> contains a list of reasons why UDP =
was<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; originally chosen as the =
transport protocol for RADIUS.&nbsp; UDP =
SHOULD<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; be used as transport protocol in =
all cases where the rationale given<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; in <a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a> applies.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Deployment experience with =
RADIUS over TLS indicates that it is most<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; useful for inter-server =
communication, such as inter-domain<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; communication between =
proxies.&nbsp; These situations benefit from =
the<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; confidentiality and ciphersuite =
negotiation that can be provided by<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; TLS. Since TLS is already widely =
available within the operating<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; systems used by proxies, =
implementation barriers are low.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TCP has a similar =
set of use cases.&nbsp; Use of TCP as a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transport between a NAS and =
RADIUS server is a poor fit, since as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; noted in [<a
href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>], there is likely to be =
insufficient traffic for<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; the congestion window to remain =
above the minimum value on a long-<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; term basis.&nbsp; The result is =
an increase in packets due to ACKs as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; compared to UDP, without a =
corresponding set of benefits.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In server-server communications =
the traffic levels in both directions<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; are typically high enough to =
support a larger congestion window as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; well as ACK piggy-backing.&nbsp; =
Through use of an application-layer<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; watchdog as described in [<a
href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>], it is possible to address =
the<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; objections to reliable transport =
described in <a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a>.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; However, in these scenarios =
&quot;bare&quot; TCP does not provide for<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; confidentiality or enable =
negotiation of stronger ciphersuites than<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; are available in =
RADIUS.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; As a result of these =
considerations, use of RADIUS over TCP SHOULD =
be<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; restricted to situations where =
RADIUS over TLS is employed.&nbsp; RADIUS<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; over &quot;bare&quot; TCP is NOT =
RECOMMENDED.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; There are still a number of =
benefits to using a reliable transport.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; For example, when RADIUS is used =
to carry EAP conversions [<a
href=3D"http://tools.ietf.org/html/rfc3579"
title=3D"&quot;RADIUS (Remote Authentication Dial In User Service) =
Support For Extensible Authentication Protocol =
(EAP)&quot;">RFC3579</a>],<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; the EAP exchanges may involve 5 =
round trips at the RADIUS application<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; layer.&nbsp; We may assume a =
probability P of packet loss in each<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; direction (with P having a value =
of 1% or less).&nbsp; Any one<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; authentication attempt will then =
have at least one lost packet, with<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; a probability of approximately =
(10 * P).<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'> &nbsp;&nbsp;These lost packets require the =
supplicant and/or the NAS to re-<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transmit packets at the =
application layer.&nbsp; The difficulty with =
this<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; approach is that retransmission =
implementations have historically<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; been poor.&nbsp; Some =
implementations retransmit packets, others do =
not,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and others send new packets =
rather then performing retransmission.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Some implementations are =
incapable of detecting EAP retransmissions,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and will instead treat the =
retransmitted packet as an error.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; These retransmissions have a =
high likelihood of causing the entire<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; authentication session to =
fail.&nbsp; For a system with a million logins =
a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; day, and having a packet loss =
probability of P=3D0.01%, we expect that<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 0.1% of connections will =
experience a lost packet.&nbsp; That is, =
1,000<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; user sessions each day will =
experience authentication failure.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In addition, transport of =
fragmented UDP packets is a poorly tested<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; code path on network =
devices.&nbsp; Some devices appear to be incapable =
of<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transporting fragmented UDP =
packets, meaning that the packet loss<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; rate for fragmented packets =
approaches 100 percent.&nbsp; The net effect<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; can be to prevent the deployment =
of authentication methods such as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; EAP-TLS that require large =
RADIUS packets.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Using a reliable transport =
method such as TCP means that RADIUS<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementations can remove all =
application-layer retransmissions, and<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; instead rely on the Operating =
System (OS) kernel's well-tested TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transport to ensure reliable =
delivery.&nbsp; In addition, most TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementations discover Path =
MTU better than RADIUS application<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementations, resulting in =
significantly fewer fragmented packets.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Modern TCP implementations also =
implement anti-spoofing provisions,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; which is more difficult to do in =
UDP applications.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Transporting RADIUS over TCP =
means that the RADIUS applications can<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; leverage these additional =
protections offered by TCP.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; However, there are also some =
drawbacks to using TCP.&nbsp; RADIUS over =
TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; has some drawbacks, as noted in =
<a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a>.&nbsp; <a
href=3D"http://tools.ietf.org/html/rfc3539#section-2">[RFC3539]<o:p></o:p=
></a></span></pre><pre
style=3D'page-break-before:always'><span class=3DMsoHyperlink><span =
lang=3DEN
style=3D'font-size:10.0pt'><a =
href=3D"http://tools.ietf.org/html/rfc3539#section-2">&nbsp;&nbsp; =
Section&nbsp;2</a></span></span><span
lang=3DEN style=3D'font-size:10.0pt'> discusses further issues with =
using TCP as a transport for<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Authentication, Authorization, =
and/or Accounting (AAA) protocols such<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; as =
RADIUS.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Specifically, as noted in <a
href=3D"http://tools.ietf.org/html/rfc3539#section-2.1">[RFC3539] =
Section&nbsp;2.1</a>, for systems<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; originating low numbers of =
RADIUS request packets, inter-packet<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; spacing is often larger than the =
packet RTT.&nbsp; In those situations,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TCP SHOULD NOT be =
used.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In general, RADIUS clients =
generating small amounts of RADIUS traffic<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; SHOULD NOT use TCP.&nbsp; This =
suggestion will usually apply to most<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; NASes, and to most clients that =
originate CoA-Request and Disconnect-<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Request =
packets.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TCP is most =
applicable to RADIUS proxies that exchange a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; large volume of packets with =
RADIUS clients and servers (10's to<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1000's of packets per =
second).&nbsp; In those situations, RADIUS over =
TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; may be a good fit, and may =
result in increased network stability and<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; =
performance.<o:p></o:p></span></pre>

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

<p class=3DMsoNormal>[BA] &nbsp;Suggested rewrite:<o:p></o:p></p>

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

<p class=3DMsoNormal>Section 1.1<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; The intent of this document is to =
address
transport issues related to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; RADIUS over TLS [RTLS] in inter-server
communications scenarios, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; such as inter-domain communication =
between
proxies.&nbsp; These <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; situations benefit from the =
confidentiality and
ciphersuite <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; negotiation that can be provided by =
TLS. Since
TLS is already <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; widely available within the operating =
systems
used by proxies, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementation barriers are low.&nbsp; =
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; In scenarios where RADIUS proxies =
exchange a
large volume of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; packets (10+ packets per second), it =
is likely
that there will be sufficient<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; traffic to enable the congestion =
window to be
widened beyond<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; the minimum value on a long-term =
basis,
enabling ACK piggy-backing. <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Through use of an application-layer =
watchdog as
described in [RFC3539], <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; it is possible to address the =
objections to reliable
transport <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; described in [RFC2865] Section 2.4 =
without
substantial<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; watchdog traffic, since regular =
traffic is
expected in both <o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp; In addition, use of RADIUS over =
TLS/TCP has
been found to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; improve operational performance when =
used with
multi-round<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; trip authentication mechanisms such as =
RADIUS
over EAP [RFC3579].<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; In such exchanges, it is typical for =
EAP
fragmentation to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; increase the number of round-trips
required.&nbsp; For example, where<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; EAP-TLS authentication [RFC5216] is =
attempted
and both the EAP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; peer and server utilize certificate =
chains of
8KB, as many as<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; 15 round-trips can be required if =
RADIUS
packets are restricted<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; to 1500 octets in size.&nbsp; =
Fragmentation of
RADIUS over UDP packets<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; is generally inadvisable due to lack =
of
fragmentation support <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; within intermediate devices such as =
filtering
routers, firewalls <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; and NATs.&nbsp; However, since RADIUS =
over UDP
implementations typically do<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; not support MTU discovery, =
fragmentation can
occur even when the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp; &nbsp;maximum RADIUS over UDP packet size is
restricted to 1500 octets. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; These problems disappear if a 4096
application-layer payload<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; can be used alongside RADIUS over
TLS/TCP.&nbsp; Since most TCP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations support MTU discovery, =
the TCP
MSS is automatically<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; adjusted to account for the MTU, and =
the larger
congestion<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; window supported by TCP may allow =
multiple TCP
segments to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; be sent within a single window.&nbsp; =
As a
result, RADIUS/EAP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; traffic required for an EAP-TLS =
authentication
with 8KB<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; certificate chains may be reduced to 7
round-trips or less, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; resulting in substantially reduced
authentication times. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; In addition, experience indicates that =
EAP
sessions transported <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; over RTLS are less likely to abort
unsuccessfully.&nbsp; Historically,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; RADIUS over UDP implementations have =
exhibited
poor retransmission<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; behavior.&nbsp; Some implementations =
retransmit
packets, others do not,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; and others send new packets rather =
then
performing retransmission.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Some implementations are incapable of =
detecting
EAP retransmissions,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; and will instead treat the =
retransmitted packet
as an error.&nbsp; <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; As a result, within RADIUS over UDP
implementations, retransmissions<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; have a high likeilhood of causing an =
EAP
authentication session<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; to fail.&nbsp; For a system with a =
million
logins a day running EAP-TLS<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; mutual authentication with 15 =
round-trips, and
having a packet loss <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; probability of P=3D0.01%, we expect =
that 0.3% of
connections will experience <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; at least one lost packet.&nbsp; That =
is, 3,000
user sessions each day <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; will experience authentication =
failure.&nbsp;
This is an unacceptable<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; failure rate for a mass-market network =
service.
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; Using a reliable transport method such =
as TCP
means that RADIUS<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations can remove all
application-layer retransmissions, and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; instead rely on the Operating System =
(OS)
kernel's well-tested TCP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; transport to ensure reliable =
delivery.&nbsp; In
addition, most TCP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations discover Path MTU =
better than
RADIUS application<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations, resulting in =
significantly
fewer fragmented packets.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Modern TCP implementations also =
implement
anti-spoofing provisions,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; which is more difficult to do in UDP =
applications.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; In contrast, use of TLS/TCP as a =
transport
between a NAS and a <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; RADIUS server is a poor fit.&nbsp; As =
noted in
[RFC3539] Section 2.1, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; for systems originating low numbers of =
RADIUS
request packets, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; inter-packet spacing is often larger =
than the
packet RTT, and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; as a result, the congestion window =
will t
ypically not remain<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; above the minimum value on a long-term =
basis.
The <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; result is an increase in packets due =
to ACKs as
compared to UDP, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; without a corresponding set of =
benefits.&nbsp; In
addition, the lack<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; of substantial traffic implies the =
need for
additional watchdog<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; traffic to confirm reachability.&nbsp; =
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; As a result, the objections to =
reliable
transport indicated in <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; [RFC2865] Section 2.4 continue to =
apply to
NAS-RADIUS server <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; communications and UDP SHOULD continue =
to be
used as the transport <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; protocol in this scenario.&nbsp; In =
addition,
it is recommended that<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations of &quot;RADIUS =
Dynamic
AUthorization Extensions&quot; [RFC5176]<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; SHOULD continue to utilize UDP =
transport, since
the volume of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; dynamic authorization traffic is =
usually
expected to be small.&nbsp; <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; Since &quot;bare&quot; TCP does not =
provide for
confidentiality or enable <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; negotiation of credible ciphersuites, =
its use
is not appropriate for <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; inter-server communications where =
strong
security is required.&nbsp; As a result <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; the use of &quot;bare&quot; TCP =
transport (i.e.
without TLS) is NOT RECOMMENDED <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; for use in any situation, and there =
has been
little or no<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; operational experience with =
it.<o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_0066_01CAA4EC.6A4F27D0--

--
to unsubscribe send a message to 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 Feb  3 17:07:31 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C27F93A6856 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 17:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.363
X-Spam-Level: 
X-Spam-Status: No, score=-1.363 tagged_above=-999 required=5 tests=[AWL=-0.869, 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 zmy-SMfl8bR4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 17:07:20 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EBE6E3A67E3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  3 Feb 2010 17:07:18 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Ncq7x-000Mll-Ax for radiusext-data0@psg.com; Thu, 04 Feb 2010 01:03:25 +0000
Received: from [65.55.116.39] (helo=blu0-omc1-s28.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Ncq7p-000MkK-8P for radiusext@ops.ietf.org; Thu, 04 Feb 2010 01:03:17 +0000
Received: from BLU137-DS6 ([65.55.116.9]) by blu0-omc1-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Feb 2010 17:03:16 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS648B9E69F4725B4DC99BC93550@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
References:
In-Reply-To:
Subject: Review of draft-ietf-radext-tcp-transport (Part II)
Date: Wed, 3 Feb 2010 17:03:15 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0073_01CAA4F2.C70142F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqlL3gql8AYAuqeR7CGu3QgwGzRQwAAI1Tw
Content-Language: en-us
X-OriginalArrivalTime: 04 Feb 2010 01:03:16.0678 (UTC) FILETIME=[D5789660:01CAA535]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0073_01CAA4F2.C70142F0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Section 2

 

   Adding TCP as a RADIUS transport has a number of impacts on the

   protocol, on applications using the protocol, and on networks that

   deploy the protocol.  In short, RADIUS over TCP is little more than

   sending RADIUS formatted messages over a TCP connection.

 

   As always, there are additional details that need to be discussed.

   This section outlines the various impacts of using RADIUS over TCP,

   and the discusses the proposal in more detail.

 

[BA] How about this? 

 

RADIUS over TCP involves sending RADIUS formatted messages over a TCP
connection.  

In the sections that follow, we discuss the implications for the RADIUS
packet format

(Section 2.1),  port usage (Section 2.2), RADIUS MIBs (Section 2.3) and
RADIUS proxies

(Section 2.5).  TCP-specific issues are discussed in Section 2.6. 

 

Section 2.1

 

   The changes to RADIUS implementations required to implement this

   specification are largely limited to the portions that send and

   receive packets on the network.

 

[BA] Is this sentence necessary?  What portions of a RADIUS implementation
*don't* relate

To sending and receiving packets?   I'd recommend that it be deleted. 

 

Section 2.2

 

   These ports are unused by existing RADIUS applications.

   Implementations SHOULD use the assigned values as the default ports

   for RADIUS over TCP.

 

[BA] You might say "Since these ports are unused by existing RADIUS
implementations,

the assigned values SHOULD be used as the default ports for RADIUS over
TCP."

 

I would merge section 2.4 into this section so that one section can cover
ports

for both RADIUS over TCP and RADIUS over TLS. 

 

Section 2.3

 

You might revise this section to make it clear that the advice for use of
MIBs 

with RADIUS over TCP also applies to RADIUS over TLS. 

 

Section 2.4

 

I'd merge this with Section 2.2. 

 

Section 2.5

 

[BA] Suggest this section be renamed "Liveness Detection". 

 

   If a request is proxied through intermediate proxies, it is not

   possible to detect which of the later hops is responsible for the

   absence of a reply.  An intermediate proxy also cannot signal that

   the outage lies in a later hop because RADIUS does not have the

   ability to carry such signalling information.  This issue is further

   exacerbated by some proxy implementations that do not reply to a

   client if they do not receive a reply to a proxied request.

 

 

[BA] This paragraph makes it seem that absence of a response by a proxy is
incorrect behavior. 

Suggest:

 

   "Within RADIUS as defined in [RFC2865], proxies typically only forward

   traffic between the NAS and RADIUS server, and do not generate their

   own responses.  As a result, when a NAS does not receive a response to

   a request, this could be the result of packet loss between the NAS

   and proxy, a problem on the proxy, loss between the RADIUS proxy and

   server, or a problem with the server."  

 

 

   For RADIUS over TCP, the continued existence of the TCP connection

   SHOULD be used to deduce that the service on the other end of the

   connection is still responsive.  Further, the application layer

   watchdog defined in [RFC3539] Section
<http://tools.ietf.org/html/rfc3539#section-3.4>  3.4 enables clients to

   determine that the server is "live", even though it may not have

   responded recently to non-watchdog requests.

 

[BA] Suggest the following:

 

   "For RADIUS over TLS/TCP, it is RECOMMENDED that implementations

   utilize the existence of a TCP connection along with the 

   application layer watchdog defined in [RFC3539] Section
<http://tools.ietf.org/html/rfc3539#section-3.4>  3.4 to

   determine that the server is "live"."

 

 

   Additional issues with RADIUS proxies involve transport protocol

   changes where the proxy receives packets on one transport protocol,

   and forwards them on a different transport protocol.  There are

   several situations in which the law of "conservation of packets"

   could be violated on an end-to-end basis (e.g. where more packets

   could enter the system than could leave it on a short-term basis):

 

      * Where TCP is used between proxies, it is possible that the

      bandwidth consumed by incoming UDP packets destined to a given

      upstream server could exceed the sending rate of a single TCP

      connection to that server, based on the window size/RTT estimate.

 

      * It is possible for the incoming rate of TCP packets destined to

      a given realm to exceed the UDP throughput achievable using the

      transport guidelines established in [RFC5080
<http://tools.ietf.org/html/rfc5080> ].  This could happen,

      for example, where the TCP window between proxies has opened, but

      packet loss is being experienced on the UDP leg, so that the

      effective congestion window on the UDP side is 1.

 

   Intrinsically, proxy systems operate with multiple control loops

   instead of one end-to-end loop, and so are less stable.  This is true

   even for TCP-TCP proxies.  As discussed in [RFC3539
<http://tools.ietf.org/html/rfc3539> ], the only way to

   achieve stability equivalent to a single TCP connection is to mimic

   the end-to-end behavior of a single TCP connection.  This typically

   is not achievable with an application-layer RADIUS implementation,

   regardless of transport.

 

[BA] I suggest this material be put into a different section entitled

"Congestion Control Issues", since it doesn't relate to liveness detection

(the subject of the rest of the section). 

 

Section 2.6

 

   The guidelines defined in [RFC3539 <http://tools.ietf.org/html/rfc3539> ]
for implementing an AAA protocol

   operating over a reliable transport MUST be followed by implementors

   of this specification.

 

[BA] Not sure the MUST adds value here.  I suggest:

 

"The guidelines defined in [RFC3539] for implementing a AAA protocol over

reliable transport are applicable to RADIUS over TLS/TCP."

 

 

   Implementations MUST NOT confuse UDP and TCP transport.  That is,

   RADIUS clients and servers MUST be treated as unique based on a key

   of the three-tuple (IP address, port, transport protocol).

   Implementations MUST permit different shared secrets to be used for

   UDP and TCP connections to the same destination IP address and

   numerical port.

 

 

 

[BA] I'd suggest "RADIUS over TLS/TCP Implementations MUST support receiving
RADIUS packets over both UDP and TLS/TCP transports originating from the
same  endpoint. 

RADIUS packets received over UDP MUST be replied to over UDP;   RADIUS
packets received over TLS/TCP MUST be replied to over TLS/TCP.  That is,

   RADIUS clients and servers MUST be treated as unique based on a key

   of the three-tuple (IP address, port, transport protocol).

   Implementations MUST permit different shared secrets to be used for

   UDP and TLS/TCP connections to the same destination IP address and

   numerical port.

 


2.6.2.  Head of Line Blocking

 
 
   When using UDP as a transport for RADIUS, there is no ordering of
   packets.  If a packet sent by a client is lost, that loss has no
   effect on subsequent packets sent by that client.
 
   Unlike UDP, TCP is subject to issues related to Head of Line (HoL)
   blocking.  This occurs when when a TCP segment is lost and a
   subsequent TCP segment arrives out of order.  While the RADIUS server
   can process RADIUS packets out of order, the semantics of TCP makes
   this impossible.  This limitation can lower the maximum packet
   processing rate of RADIUS over TCP.

 

[BA] Suggest:

 

   When using UDP as a transport for RADIUS, there is no ordering of
   packets.  If a packet sent by a client is lost, that loss has no
   effect on subsequent packets sent by that client.
 
   Unlike UDP, TLS/TCP is subject to issues related to Head of Line (HoL)
   blocking.  This occurs when when a TLS/TCP segment is lost and a
   subsequent TLS/TCP segment arrives out of order.  While the RADIUS server
   can process RADIUS packets out of order, the semantics of TLS/TCP makes
   this impossible.  This limitation can lower the maximum packet
   processing rate of RADIUS over TLS/TCP.
 

2.6.3.  Shared Secrets

 
 
   The use of shared secrets in calculating the Response Authenticator,
   and other attributes such as User-Password or Message-Authenticator
   [RFC3579 <http://tools.ietf.org/html/rfc3579> ] MUST be unchanged from
previous specifications
 
[BA] I'd suggest that this text be merged with Section 2.1, and that the
above paragraph be changed to the following:
 
"The use of TLS/TCP transport does not change the calculation of
security-related
fields (such as the Response-Authenticator) in RADIUS [RFC2865] or RADIUS
Dynamic 
Authorization [RFC5176].  Calculation of attributes such as
User-Password [RFC2865] or Message-Authenticator [RFC3579] also does not
change." 

 

Section 2.6.4

 

   Implementations of this specification SHOULD treat the "silently

   discard" texts referenced above as "silently discard and close the

   connection."  

 

[BA] What is the alternative to this behavior?  Could this be a MUST?

 

   TCP connections MAY be closed if any of the circumstances outlined

   below are seen.  Alternatively, the TCP connection MAY remain open if

   any of the following circumstances are seen, but the invalid packet

   MUST BE silently discarded.

 

[BA] Not sure how you can do this in practice.  Are you assuming that the

Length field remains valid? 

 

Section 2.6.6

 

Given the discussion in Section 1.1, I'm wondering if this section (or some
other section)

shouldn't make a recommendation on the maximum RADIUS message size
applicable to use with 

RADIUS/EAP.  It seems to me that using a larger RADIUS message size would
make a lot of 

sense. 

 

 

 

 

 

 


------=_NextPart_000_0073_01CAA4F2.C70142F0
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:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
h4
	{mso-style-priority:9;
	mso-style-link:"Heading 4 Char";
	margin-top:10.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-style:italic;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.grey
	{mso-style-name:grey;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Heading4Char
	{mso-style-name:"Heading 4 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 4";
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-weight:bold;
	font-style:italic;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Section =
2<o:p></o:p></span></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Adding =
TCP as a
RADIUS transport has a number of impacts on the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
protocol, on
applications using the protocol, and on networks =
that<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; deploy =
the
protocol.&nbsp; In short, RADIUS over TCP is little more =
than<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
sending RADIUS
formatted messages over a TCP connection.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; As =
always,
there are additional details that need to be =
discussed.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; This =
section
outlines the various impacts of using RADIUS over =
TCP,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; and =
the
discusses the proposal in more detail.<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>[BA] How about this? =
<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>RADIUS over TCP =
involves sending
RADIUS formatted messages over a TCP connection.&nbsp; =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>In the sections that =
follow, we
discuss the implications for the RADIUS packet =
format<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>(Section 2.1), =
&nbsp;port usage
(Section 2.2), RADIUS MIBs (Section 2.3) and RADIUS =
proxies<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>(Section 2.5).&nbsp;
TCP-specific issues are discussed in Section 2.6. <o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Section =
2.1<o:p></o:p></span></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; The =
changes to
RADIUS implementations required to implement this<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
specification
are largely limited to the portions that send and<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
receive packets
on the network.<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>[BA] Is this sentence =
necessary?&nbsp;
What portions of a RADIUS implementation *<b>don&#8217;t</b>* =
relate<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>To sending and =
receiving
packets? &nbsp;&nbsp;I&#8217;d recommend that it be deleted. =
<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Section =
2.2<o:p></o:p></span></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; These =
ports are
unused by existing RADIUS applications.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
SHOULD use the assigned values as the default =
ports<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; for =
RADIUS over
TCP.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
You might say &#8220;Since these ports are unused by existing RADIUS
implementations,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>the
assigned values SHOULD be used as the default ports for RADIUS over =
TCP.&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>I
would merge section 2.4 into this section so that one section can cover =
ports<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>for
both RADIUS over TCP and RADIUS over TLS. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section
2.3<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>You
might revise this section to make it clear that the advice for use of =
MIBs <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>with
RADIUS over TCP also applies to RADIUS over TLS. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section
2.4<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>I&#8217;d
merge this with Section 2.2. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section
2.5<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
Suggest this section be renamed &#8220;Liveness Detection&#8221;. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; If a =
request is
proxied through intermediate proxies, it is not<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
possible to
detect which of the later hops is responsible for =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
absence of a
reply.&nbsp; An intermediate proxy also cannot signal =
that<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; the =
outage lies
in a later hop because RADIUS does not have the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
ability to
carry such signalling information.&nbsp; This issue is =
further<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
exacerbated by
some proxy implementations that do not reply to a<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; client =
if they
do not receive a reply to a proxied request.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
This paragraph makes it seem that absence of a response by a proxy is =
incorrect
behavior. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Suggest:<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
&#8220;Within RADIUS as defined in [RFC2865], proxies typically only =
forward<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
traffic between the NAS and RADIUS server, and do not generate =
their<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
own responses.&nbsp; As a result, when a NAS does not receive a response =
to<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
a request, this could be the result of packet loss between the =
NAS<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
and proxy, a problem on the proxy, loss between the RADIUS proxy =
and<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
server, or a problem with the server.&#8221; =
&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; For =
RADIUS over
TCP, the continued existence of the TCP connection<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; SHOULD =
be used
to deduce that the service on the other end of the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
connection is
still responsive.&nbsp; Further, the application =
layer<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
watchdog
defined in <a =
href=3D"http://tools.ietf.org/html/rfc3539#section-3.4">[RFC3539] =
Section&nbsp;3.4</a>
enables clients to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
determine that
the server is &quot;live&quot;, even though it may not =
have<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
responded
recently to non-watchdog requests.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
Suggest the following:<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
&#8220;For
RADIUS over TLS/TCP, it is RECOMMENDED that =
implementations<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
utilize the existence
of a TCP connection along with the <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
application
layer watchdog defined in <a
href=3D"http://tools.ietf.org/html/rfc3539#section-3.4">[RFC3539] =
Section&nbsp;3.4</a>
to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
determine that
the server is &quot;live&#8221;.&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Additional
issues with RADIUS proxies involve transport =
protocol<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
changes where
the proxy receives packets on one transport =
protocol,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; and =
forwards
them on a different transport protocol.&nbsp; There =
are<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
several
situations in which the law of &quot;conservation of =
packets&quot;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; could =
be
violated on an end-to-end basis (e.g. where more =
packets<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; could =
enter the
system than could leave it on a short-term basis):<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
* Where TCP is used between proxies, it is possible that =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
bandwidth consumed by incoming UDP packets destined to a =
given<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
upstream server could exceed the sending rate of a single =
TCP<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
connection to that server, based on the window size/RTT =
estimate.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
* It is possible for the incoming rate of TCP packets destined =
to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
a given realm to exceed the UDP throughput achievable using =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
transport guidelines established in [<a
href=3D"http://tools.ietf.org/html/rfc5080"
title=3D"&quot;Common Remote Authentication Dial In User Service =
(RADIUS) Implementation Issues and Suggested =
Fixes&quot;">RFC5080</a>].&nbsp;
This could happen,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
for example, where the TCP window between proxies has opened, =
but<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
packet loss is being experienced on the UDP leg, so that =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
effective congestion window on the UDP side is 1.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Intrinsically,
proxy systems operate with multiple control loops<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
instead of one
end-to-end loop, and so are less stable.&nbsp; This is =
true<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; even =
for
TCP-TCP proxies.&nbsp; As discussed in [<a
href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>],
the only way to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
achieve
stability equivalent to a single TCP connection is to =
mimic<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; the =
end-to-end
behavior of a single TCP connection.&nbsp; This =
typically<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; is not
achievable with an application-layer RADIUS =
implementation,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
regardless of
transport.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] I suggest this =
material
be put into a different section entitled<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&#8220;Congestion =
Control
Issues&#8221;, since it doesn&#8217;t relate to liveness =
detection<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>(the subject of the =
rest of
the section). <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section =
2.6<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; The =
guidelines
defined in [<a href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>]
for implementing an AAA protocol<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
operating over
a reliable transport MUST be followed by =
implementors<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of =
this
specification.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] Not sure the =
MUST adds
value here.&nbsp; I suggest:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&#8220;The =
guidelines
defined in [RFC3539] for implementing a AAA protocol =
over<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>reliable transport =
are
applicable to RADIUS over TLS/TCP.&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
MUST NOT confuse UDP and TCP transport.&nbsp; That =
is,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; RADIUS =
clients
and servers MUST be treated as unique based on a =
key<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of the
three-tuple (IP address, port, transport =
protocol).<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
MUST permit different shared secrets to be used =
for<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; UDP =
and TCP
connections to the same destination IP address and<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
numerical port.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'>[BA] I&#8217;d suggest &#8220;RADIUS over =
TLS/TCP Implementations
MUST support receiving RADIUS packets over both UDP and TLS/TCP =
transports originating
from the same &nbsp;endpoint. <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'>RADIUS packets received over UDP MUST be =
replied to
over UDP;&nbsp;&nbsp; RADIUS packets received over TLS/TCP MUST be =
replied to
over TLS/TCP. &nbsp;</span><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>That is,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; RADIUS =
clients
and servers MUST be treated as unique based on a =
key<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of the
three-tuple (IP address, port, transport =
protocol).<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
MUST permit different shared secrets to be used =
for<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; UDP =
and TLS/TCP
connections to the same destination IP address and<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
numerical port.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<h4 style=3D'page-break-before:always'><a name=3Dsection-2.6.2><span =
lang=3DEN
style=3D'font-size:10.0pt'>2.6.2</span></a><span lang=3DEN =
style=3D'font-size:10.0pt'>.&nbsp;
Head of Line Blocking<o:p></o:p></span></h4>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; When using UDP as a transport =
for RADIUS, there is no ordering of<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; packets.&nbsp; If a packet sent =
by a client is lost, that loss has no<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; effect on subsequent packets =
sent by that client.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Unlike UDP, TCP is subject to =
issues related to Head of Line (HoL)<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; blocking.&nbsp; This occurs when =
when a TCP segment is lost and a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; subsequent TCP segment arrives =
out of order.&nbsp; While the RADIUS server<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; can process RADIUS packets out =
of order, the semantics of TCP makes<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; this impossible.&nbsp; This =
limitation can lower the maximum packet<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; processing rate of RADIUS over =
TCP.<o:p></o:p></span></pre>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] =
Suggest:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; When using UDP as a transport =
for RADIUS, there is no ordering of<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; packets.&nbsp; If a packet sent =
by a client is lost, that loss has no<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; effect on subsequent packets =
sent by that client.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Unlike UDP, TLS/TCP is subject =
to issues related to Head of Line (HoL)<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; blocking.&nbsp; This occurs when =
when a TLS/TCP segment is lost and a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; subsequent TLS/TCP segment =
arrives out of order.&nbsp; While the RADIUS =
server<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; can process RADIUS packets out =
of order, the semantics of TLS/TCP makes<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; this impossible.&nbsp; This =
limitation can lower the maximum packet<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; processing rate of RADIUS over =
TLS/TCP.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre>

<h4 style=3D'page-break-before:always'><a name=3Dsection-2.6.3><span =
lang=3DEN
style=3D'font-size:10.0pt'>2.6.3</span></a><span lang=3DEN =
style=3D'font-size:10.0pt'>.&nbsp;
Shared Secrets<o:p></o:p></span></h4>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; The use of shared secrets in =
calculating the Response Authenticator,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and other attributes such as =
User-Password or Message-Authenticator<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; [<a
href=3D"http://tools.ietf.org/html/rfc3579"
title=3D"&quot;RADIUS (Remote Authentication Dial In User Service) =
Support For Extensible Authentication Protocol (EAP)&quot;">RFC3579</a>] =
MUST be unchanged from previous =
specifications<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>[BA] I&#8217;d suggest that this text be =
merged with Section 2.1, and that the<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>above paragraph be changed to the =
following:<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&#8220;The use of TLS/TCP transport does not =
change the calculation of security-related<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>fields (such as the Response-Authenticator) =
in RADIUS [RFC2865] or RADIUS Dynamic <o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>Authorization [RFC5176].&nbsp; Calculation of =
attributes such as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>User-Password [RFC2865] or =
Message-Authenticator [RFC3579] also does not change.&#8221; =
</span><span
lang=3DEN style=3D'font-size:10.0pt'><o:p></o:p></span></pre>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section =
2.6.4<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
of this specification SHOULD treat the =
&quot;silently<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
discard&quot;
texts referenced above as &quot;silently discard and close =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;
connection.&quot;&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>[BA] =
What is the
alternative to this behavior?&nbsp; Could this be a =
MUST?<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; TCP =
connections
MAY be closed if any of the circumstances outlined<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; below =
are
seen.&nbsp; Alternatively, the TCP connection MAY remain open =
if<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; any of =
the
following circumstances are seen, but the invalid =
packet<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; MUST =
BE
silently discarded.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] Not sure how =
you can do
this in practice.&nbsp; Are you assuming that the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Length field =
remains valid? <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section =
2.6.6<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Given the =
discussion in
Section 1.1, I&#8217;m wondering if this section (or some other =
section)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>shouldn&#8217;t =
make a
recommendation on the maximum RADIUS message size applicable to use with =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>RADIUS/EAP. =
&nbsp;It seems
to me that using a larger RADIUS message size would make a lot of =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>sense. =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

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

</div>

</body>

</html>

------=_NextPart_000_0073_01CAA4F2.C70142F0--

--
to unsubscribe send a message to 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 Feb  3 17:15:47 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CB5A3A69B2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 17:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.042
X-Spam-Level: 
X-Spam-Status: No, score=-0.042 tagged_above=-999 required=5 tests=[AWL=-2.148, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thbriAVzHobK for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed,  3 Feb 2010 17:15:46 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E1A953A69A1 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed,  3 Feb 2010 17:15:45 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NcqGo-000Nm9-Sr for radiusext-data0@psg.com; Thu, 04 Feb 2010 01:12:34 +0000
Received: from [65.55.116.21] (helo=blu0-omc1-s10.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NcqGl-000Nlk-D0 for radiusext@ops.ietf.org; Thu, 04 Feb 2010 01:12:31 +0000
Received: from BLU137-DS4 ([65.55.116.8]) by blu0-omc1-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Feb 2010 17:12:30 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS4F4F654FDF24869ACFA1A93550@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
References:
In-Reply-To:
Subject: RE: Review of draft-ietf-radext-tcp-transport (Part III)
Date: Wed, 3 Feb 2010 17:12:30 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0080_01CAA4F4.118DC680"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqlL3gql8AYAuqeR7CGu3QgwGzRQwABl9zw
Content-Language: en-us
X-OriginalArrivalTime: 04 Feb 2010 01:12:30.0919 (UTC) FILETIME=[1FD30D70:01CAA537]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0080_01CAA4F4.118DC680
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Additional comments

 

I am wondering whether this document should take a position on the
recommendations described in [RFC3539] Section 3, particularly:

 

3.2.  Use of Nagle Algorithm

3.3.  Multiple Connections

3.4.2 Primary/Secondary failover

3.4.3 Connection Load Balancing

3.6 Invalidation of Transport Parameter Estimates

3.7 Inability to Use Fast Retransmit

3.8 Head of Line Blocking

3.9 Congestion Avoidance

3.10 Premature Failover

 

 

 

 

 

 

 

 

 


------=_NextPart_000_0080_01CAA4F4.118DC680
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:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.grey
	{mso-style-name:grey;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Additional =
comments<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>I am wondering =
whether this
document should take a position on the recommendations described in =
[RFC3539]
Section 3, particularly:<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.2.&nbsp;
Use of Nagle Algorithm<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.3.&nbsp;
Multiple Connections<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.4.2
Primary/Secondary failover<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.4.3
Connection Load Balancing<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.6
Invalidation of Transport Parameter Estimates<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.7
Inability to Use Fast Retransmit<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.8
Head of Line Blocking<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.9
Congestion Avoidance<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.10
Premature Failover<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

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

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

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

</div>

</body>

</html>

------=_NextPart_000_0080_01CAA4F4.118DC680--

--
to unsubscribe send a message to 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 Feb  6 05:05:29 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91CC43A681D for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 05:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.108
X-Spam-Level: 
X-Spam-Status: No, score=0.108 tagged_above=-999 required=5 tests=[AWL=-1.998, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z1l7JRqieBz9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 05:05:27 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7A3D03A67F4 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 05:05:26 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NdkJm-000F95-AM for radiusext-data0@psg.com; Sat, 06 Feb 2010 13:03:22 +0000
Received: from [65.55.116.20] (helo=blu0-omc1-s9.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NdkJj-000F8c-UT for radiusext@ops.ietf.org; Sat, 06 Feb 2010 13:03:20 +0000
Received: from BLU137-DS6 ([65.55.116.8]) by blu0-omc1-s9.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 05:03:19 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS6B2770B9691F98F0BC27593530@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interm Date
Date: Sat, 6 Feb 2010 05:03:57 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012E_01CAA6E9.C9DFD240"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcqnLNe9DBGDR06bQDOc+0wrkHRP/g==
Content-Language: en-us
X-OriginalArrivalTime: 06 Feb 2010 13:03:19.0261 (UTC) FILETIME=[C10B18D0:01CAA72C]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_012E_01CAA6E9.C9DFD240
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The RADEXT Virtual Interim will take place on Tuesday, February 23, 2010
from 10 AM - 12:30 PM Pacific Time. 

 

Details will be forthcoming. 


------=_NextPart_000_012E_01CAA6E9.C9DFD240
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>The RADEXT Virtual Interim will take place on =
Tuesday,
February 23, 2010 from 10 AM &#8211; 12:30 PM Pacific Time. =
<o:p></o:p></p>

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

<p class=3DMsoNormal>Details will be forthcoming. <o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_012E_01CAA6E9.C9DFD240--

--
to unsubscribe send a message to 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 Feb  6 12:02:29 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89B8628C0E5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 12:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.267
X-Spam-Level: *
X-Spam-Status: No, score=1.267 tagged_above=-999 required=5 tests=[AWL=-3.054, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_OBFU_SPLIT_HR2=0.183, TVD_SPACE_RATIO=2.219]
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 PkaWhQgGPF9t for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 12:02:28 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6C9783A6C62 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 12:02:28 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NdqnQ-0008Dx-P6 for radiusext-data0@psg.com; Sat, 06 Feb 2010 19:58:24 +0000
Received: from [65.55.116.27] (helo=blu0-omc1-s16.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NdqnO-0008Dg-AY for radiusext@ops.ietf.org; Sat, 06 Feb 2010 19:58:22 +0000
Received: from BLU137-DS7 ([65.55.116.8]) by blu0-omc1-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 11:58:21 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS7151BA276DF1E00BBF0DA93530@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim
Date: Sat, 6 Feb 2010 11:58:56 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNAAOg8Cg
Content-Language: en-us
X-OriginalArrivalTime: 06 Feb 2010 19:58:21.0623 (UTC) FILETIME=[BC01FC70:01CAA766]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN=radiusext@ops.ietf.org;RSVP=TRUE:mailto:radiusext@ops.ietf.org
CLASS:PUBLIC
CREATED:20100206T195856Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: 702-473-3463 #222622\n\nNote: The GM
	T offset above does not reflect daylight saving time adjustments.\n\n*~*~*
	~*~*~*~*~*~*~*\n\nThe IETF RADEXT WG will hold a Virtual Interim on Februa
	ry 23\, 2010 10:00:AM PST. To join the Dimdim event simply click here <htt
	ps://webmeeting.dimdim.com/portal/JoinForm.action?confKey=baboba&email=ber
	nard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&attendeePwd=>  \nYou can also join by entering the Meeting Roo
	m "baboba" at Dimdim.com <http://www.dimdim.com/join>  at the time listed 
	above.  <https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=babo
	ba&email=bernard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40
	-4fc0-9835-cf1fdfcc0a4b&attendeePwd>    \n\nMeeting : RADEXT Virtual Inter
	im  \nKey:   \nDial In: 702-473-3463 \nPass Code: 222622   \nStart: Februa
	ry 23\, 2010 10:00:AM PST (Add to Outlook <https://webmeeting.dimdim.com/p
	ortal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&email
	=bernard.aboba@gmail.com&attendeePwd=> )   \nSchedule Ends At: Not Applica
	ble   \n\nThis meeting happens only once   \n\nMeeting Agenda:  TBD\n\nHin
	t: You don't need to be a member of Dimdim to attend this meeting.\n\n It'
	s easy to join and get started\, Click here to sign up for Dimdim Free. <h
	ttp://www.dimdim.com/registration/Dimdim_Signup.html>  \n\nBut you may fin
	d it helpful to check your bandwidth and your A/V setup here <http://www.d
	imdim.com/support/dimdim_tools.html> . \n\n\n
DTEND:20100223T203000Z
DTSTAMP:20100206T195856Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100206T195856Z
LOCATION:702-473-3463 #222622
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:1
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: 702-473-3463 #222622</FONT></SPAN></P>\n\
	n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset a
	bove does not reflect daylight saving time adjustments.</FONT></SPAN></P>\
	n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*<
	/FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Th
	e IETF RADEXT WG will hold a Virtual Interim on</FONT></SPAN><SPAN LANG="e
	n-us"><B> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PST</FONT></B><
	/SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.</FONT></SPAN><SPAN LANG="e
	n-us"> </SPAN><A HREF="https://webmeeting.dimdim.com/portal/JoinForm.actio
	n?confKey=baboba&amp\;email=bernard.aboba@gmail.com&amp\;asPresenter=false
	&amp\;meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp\;attendeePwd="><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">To join the Dimdi
	m event simply click here</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><
	SPAN LANG="en-us"><FONT FACE="Calibri"><BR>\nYou can also join by entering
	 the Meeting Room &quot\;baboba&quot\; at</FONT></SPAN><SPAN LANG="en-us">
	 </SPAN><A HREF="http://www.dimdim.com/join"><SPAN LANG="en-us"><U><FONT C
	OLOR="#0000FF" FACE="Calibri">Dimdim.com</FONT></U></SPAN><SPAN LANG="en-u
	s"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri"> at the time listed 
	above.</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="https://webmeeting
	.dimdim.com/portal/JoinForm.action?confKey=baboba&amp\;email=bernard.aboba
	@gmail.com&amp\;asPresenter=false&amp\;meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&amp\;attendeePwd"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"
	></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calib
	ri"></FONT></SPAN><SPAN LANG="en-us"></SPAN></SPAN><SPAN LANG="en-us"> <FO
	NT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><
	B><FONT FACE="Calibri">Meeting :</FONT></B></SPAN><SPAN LANG="en-us"> <FON
	T FACE="Calibri">RADEXT Virtual Interim  </FONT></SPAN></P>\n\n<P DIR=LTR
	><SPAN LANG="en-us"><B><FONT FACE="Calibri">Key:</FONT></B></SPAN><SPAN LA
	NG="en-us"> <FONT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN
	 LANG="en-us"><B><FONT FACE="Calibri">Dial In:</FONT></B></SPAN><SPAN LANG
	="en-us"> <FONT FACE="Calibri">702-473-3463 </FONT></SPAN></P>\n\n<P DIR=L
	TR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Pass Code:</FONT></B></SPAN>
	<SPAN LANG="en-us"> <FONT FACE="Calibri">222622   </FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Start:</FONT></B></SP
	AN><SPAN LANG="en-us"> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PS
	T (</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="https://webmeeting.dim
	dim.com/portal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0
	a4b&amp\;email=bernard.aboba@gmail.com&amp\;attendeePwd="><SPAN LANG="en-u
	s"><U><FONT COLOR="#0000FF" FACE="Calibri">Add to Outlook</FONT></U></SPAN
	><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">) 
	  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Cali
	bri">Schedule Ends At:</FONT></B></SPAN><SPAN LANG="en-us"> <FONT FACE="Ca
	libri">Not Applicable   </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-u
	s"><FONT FACE="Calibri">This meeting happens only once   </FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Meeting Agenda
	:&nbsp\; TBD</FONT></B></SPAN><SPAN LANG="en-us"><BR>\n<BR>\n<B><FONT FACE
	="Calibri">Hint:</FONT></B></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">
	 You don't need to be a member of Dimdim to attend this meeting.</FONT></S
	PAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;It's
	 easy to join and get started\,</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A
	 HREF="http://www.dimdim.com/registration/Dimdim_Signup.html"><SPAN LANG="
	en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">Click here to sign up for D
	imdim Free.</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-
	us"><FONT FACE="Calibri"> </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-
	us"><FONT FACE="Calibri">But you may find it helpful to check your bandwid
	th and your A/V setup</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="htt
	p://www.dimdim.com/support/dimdim_tools.html"><SPAN LANG="en-us"><U><FONT 
	COLOR="#0000FF" FACE="Calibri">here</FONT></U></SPAN><SPAN LANG="en-us"></
	SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">.<BR>\n</FONT></SPAN></P>
	\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTSEQTIME:20100206T195656Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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

From owner-radiusext@ops.ietf.org  Sat Feb  6 12:02:37 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A0753A6C62 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 12:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.119
X-Spam-Level: 
X-Spam-Status: No, score=0.119 tagged_above=-999 required=5 tests=[AWL=-1.801, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8OlLortIdHf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 12:02:36 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6964A3A68E8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 12:02:36 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Ndqny-0008HV-Dm for radiusext-data0@psg.com; Sat, 06 Feb 2010 19:58:58 +0000
Received: from [65.55.116.41] (helo=blu0-omc1-s30.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Ndqnv-0008HD-Vs for radiusext@ops.ietf.org; Sat, 06 Feb 2010 19:58:56 +0000
Received: from BLU137-DS6 ([65.55.116.9]) by blu0-omc1-s30.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 11:58:47 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS6C63CE1CD7E507805EF5393530@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Meeting:  February 23, 2010
Date: Sat, 6 Feb 2010 11:59:25 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_018C_01CAA723.D40C99D0"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcqnZuHjY5WTvlBdS1ChT0H7FQ7p4g==
Content-Language: en-us
X-OriginalArrivalTime: 06 Feb 2010 19:58:47.0015 (UTC) FILETIME=[CB247F70:01CAA766]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_018C_01CAA723.D40C99D0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The IETF RADEXT WG will hold a Virtual Interim on February 23, 2010 10:00:AM
PST. To join the Dimdim event simply click here
<https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=baboba&email=b
ernard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40-4fc0-9835-c
f1fdfcc0a4b&attendeePwd=> 

 

Meeting : RADEXT Virtual Interim  

Key:   

Dial In: 702-473-3463 

Pass Code: 222622   

Start: February 23, 2010 10:00:AM PST (Add to Outlook
<https://webmeeting.dimdim.com/portal/calendar.action?meetingId=3aaea628-1b4
0-4fc0-9835-cf1fdfcc0a4b&email=bernard.aboba@gmail.com&attendeePwd=> )   

Schedule Ends At: 12:30 PM Pacific Time

 

This meeting happens only once   

 

Meeting Agenda:  TBD

Hint: You don't need to be a member of Dimdim to attend this meeting.

 

 It's easy to join and get started, Click
<http://www.dimdim.com/registration/Dimdim_Signup.html>  here to sign up for
Dimdim Free. 

 

But you may find it helpful to check your bandwidth and your A/V setup here
<http://www.dimdim.com/support/dimdim_tools.html> . 



 

 


------=_NextPart_000_018C_01CAA723.D40C99D0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>The IETF RADEXT WG will hold a Virtual Interim on =
<b>February
23, 2010 10:00:AM PST</b>. <a
href=3D"https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=3Dba=
boba&amp;email=3Dbernard.aboba@gmail.com&amp;asPresenter=3Dfalse&amp;meet=
ingId=3D3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp;attendeePwd=3D"
target=3D"_blank">To join the Dimdim event simply click =
here</a><b><o:p></o:p></b></p>

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

<p class=3DMsoNormal><b>Meeting : </b>RADEXT Virtual Interim =
&nbsp;<o:p></o:p></p>

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

<p class=3DMsoNormal><b>Dial In: </b>702-473-3463 <o:p></o:p></p>

<p class=3DMsoNormal><b>Pass Code: </b>222622 &nbsp; <o:p></o:p></p>

<p class=3DMsoNormal><b>Start: </b>February 23, 2010 10:00:AM PST (<a
href=3D"https://webmeeting.dimdim.com/portal/calendar.action?meetingId=3D=
3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp;email=3Dbernard.aboba@gmail.com&=
amp;attendeePwd=3D"
target=3D"_blank">Add to Outlook</a>) &nbsp; <o:p></o:p></p>

<p class=3DMsoNormal><b>Schedule Ends At: </b>12:30 PM Pacific =
Time<o:p></o:p></p>

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

<p class=3DMsoNormal>This meeting happens only once &nbsp; =
<o:p></o:p></p>

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

<p class=3DMsoNormal><b>Meeting Agenda: &nbsp;TBD</b><br>
<br>
<b>Hint:</b> You don't need to be a member of Dimdim to attend this =
meeting.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;It's easy to join and get started, <a
href=3D"http://www.dimdim.com/registration/Dimdim_Signup.html" =
target=3D"_blank">Click
here to sign up for Dimdim Free.</a> <o:p></o:p></p>

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

<p class=3DMsoNormal>But you may find it helpful to check your bandwidth =
and your
A/V setup <a href=3D"http://www.dimdim.com/support/dimdim_tools.html"
target=3D"_blank">here</a>. <br>
<br>
<o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_018C_01CAA723.D40C99D0--

--
to unsubscribe send a message to 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 Feb  6 15:41:59 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5973028C0F3 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 15:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.058
X-Spam-Level: 
X-Spam-Status: No, score=-1.058 tagged_above=-999 required=5 tests=[AWL=-0.564, 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 XYyH+Ads0OjR for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 15:41:58 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 27E683A6452 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 15:41:58 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NduFJ-0001bd-CS for radiusext-data0@psg.com; Sat, 06 Feb 2010 23:39:25 +0000
Received: from [65.55.116.24] (helo=blu0-omc1-s13.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NduFG-0001bT-So for radiusext@ops.ietf.org; Sat, 06 Feb 2010 23:39:22 +0000
Received: from BLU137-W11 ([65.55.116.8]) by blu0-omc1-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 15:39:22 -0800
Message-ID: <BLU137-W11E7A39B6E682E9624AF8793530@phx.gbl>
Content-Type: multipart/alternative; boundary="_ff87476a-ab98-4816-901a-6f2e2bc0406f_"
X-Originating-IP: [72.11.66.126]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take One
Date: Sat, 6 Feb 2010 15:39:22 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Feb 2010 23:39:22.0253 (UTC) FILETIME=[9BF58BD0:01CAA785]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_ff87476a-ab98-4816-901a-6f2e2bc0406f_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


RADEXT Virtual Interim Meeting
Tuesday=2C February 23=2C 2010
10 AM - 12:30 PM Pacific Time

Conferencing Details:

Slide Presentations: http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/
Jabber room:  radext at jabber.ietf.org (Please join)
Dial-in Audioconference details:  http://ops.ietf.org/lists/radiusext/2010/=
msg00161.html

Agenda

10 AM - 10:15 AM PT: Preliminaries=20

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

Design Guidelines (60 minutes)

10:15 AM - 11:15 AM PT Design Guidelines=2C Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

RADSEC (60 minutes)

11:15 AM - 11:30 AM PT  RADSEC=2C Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec

11:30 AM - 11:45 AM PT NAI-Based Peer Discovery=2C Stefan Winter (15 minute=
s)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

11:45 AM - 12:00 PM PT  Status-Server=2C Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

12:00 PM PT - 12:15 PM PT RADIUS over TCP=2C Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport


Wrap-up (15 minutes)

12:15 PM PT =96 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (=
15 minutes)


 		 	   		  =

--_ff87476a-ab98-4816-901a-6f2e2bc0406f_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
RADEXT Virtual Interim Meeting<br>Tuesday=2C February 23=2C 2010<br>10 AM -=
 12:30 PM Pacific Time<br><br>Conferencing Details:<br><br>Slide Presentati=
ons: http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/<br>Jabber room:&nbsp=
=3B radext at jabber.ietf.org (Please join)<br>Dial-in Audioconference deta=
ils:&nbsp=3B http://ops.ietf.org/lists/radiusext/2010/msg00161.html<br><br>=
Agenda<br><br>10 AM - 10:15 AM PT: Preliminaries <br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B Conference issues/debugging<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B Attendance<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Note takers<br>&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B Agenda bash<br><br>Design Guidelines (60 minutes)<b=
r><br>10:15 AM - 11:15 AM PT Design Guidelines=2C Alan DeKok (60 minutes)<b=
r>http://tools.ietf.org/html/draft-ietf-radext-design-guidelines<br><br>RAD=
SEC (60 minutes)<br><br>11:15 AM - 11:30 AM PT&nbsp=3B RADSEC=2C Stefan Win=
ter (15 minutes)<br>http://tools.ietf.org/html/draft-ietf-radext-radsec<br>=
<br>11:30 AM - 11:45 AM PT NAI-Based Peer Discovery=2C Stefan Winter (15 mi=
nutes)<br>http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery<br=
><br>11:45 AM - 12:00 PM PT&nbsp=3B Status-Server=2C Alan DeKok (15 minutes=
)<br>http://tools.ietf.org/html/draft-ietf-radext-status-server<br><br>12:0=
0 PM PT - 12:15 PM PT RADIUS over TCP=2C Alan DeKok (15 minutes)<br>http://=
tools.ietf.org/html/draft-ietf-radext-tcp-transport<br><br><br>Wrap-up (15 =
minutes)<br><br>12:15 PM PT =96 12:30 PM PT&nbsp=3B&nbsp=3B Discussion and =
Next Steps:&nbsp=3B WG Chairs &amp=3B ADs (15 minutes)<br><br><table style=
=3D"border-top: 1px solid black=3B font-weight: bold=3B font-family: 'Segoe=
 UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><td><br></td></tr></tbody></table>=
 		 	   		  </body>
</html>=

--_ff87476a-ab98-4816-901a-6f2e2bc0406f_--

--
to unsubscribe send a message to 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 Feb  6 16:19:39 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14A063A6E7B for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 16:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[AWL=-0.554, 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 Z03nLG9T4rhM for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 16:19:36 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 99F3F3A68B8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 16:19:35 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NduqP-00056Q-Bt for radiusext-data0@psg.com; Sun, 07 Feb 2010 00:17:45 +0000
Received: from [65.55.116.42] (helo=blu0-omc1-s31.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NduqK-000566-SC for radiusext@ops.ietf.org; Sun, 07 Feb 2010 00:17:41 +0000
Received: from BLU137-W35 ([65.55.116.8]) by blu0-omc1-s31.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 16:17:40 -0800
Message-ID: <BLU137-W35CCBE493A9F2C672FE20C93520@phx.gbl>
Content-Type: multipart/alternative; boundary="_e6303a6f-9138-4e94-9116-b1205323940c_"
X-Originating-IP: [72.11.66.126]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-status-server-05 (part I)
Date: Sat, 6 Feb 2010 16:17:40 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2010 00:17:40.0302 (UTC) FILETIME=[F5B3FEE0:01CAA78A]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_e6303a6f-9138-4e94-9116-b1205323940c_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Overall=2C I believe that this document is very close to being ready for su=
bmission to the IESG as an Informational RFC.=20

Section 1.1

   This specification is also limited to being a "hop by hop" query.

   When RADIUS packets transition one or more RADIUS Proxies=2C any
   information about the status of downstreamservers is unavailable to
   the client.  In addition=2C it queries only the status of a RADIUS
   server=2C cannot carry information about specific realms.

   These limitations are discussed in more detail below.


[BA] My suggestion is that this material be moved to Section 2=2C since it =
doesn't relate to the
reasons why publication is recommended as an Informational RFC.=20

Section 2

This section includes a statement of the problem and justification for why =
the Status-Server solution was
chosen.   My suggestion is to begin this section with an explanation of wha=
t Status-Server does=2C then move
on from there. =20

Suggested rewrite:=20

Status-Server packets are sent by a RADIUS client to a RADIUS server in ord=
er to test the status of that=20
server.  Since a Status-Server packet MUST NOT be forwarded by a RADIUS pro=
xy or server=2C the destination
of a Status-Server packet is set to that of the server which is being teste=
d.  As a result=2C the=20
client is provided with an indication of the status of that server only=2C =
since no RADIUS proxies=20
are on the path between the RADIUS client and server.  Since servers respon=
d to a Status-Server packet=20
without examining the  User-Name attribute=2C the response to a Status-Serv=
er packet cannot be used to=20
infer any information about the reachability of specific realms.

The "hop by hop" functionality of Status-Server packets is useful to RADIUS=
 clients attempting to determine
the status of elements on the path between the client and a server.   Since=
 the Status-Server packet=20
is non-forwardable=2C lack of a response may only be due to packet loss or =
the failure of the server in the
destination IP address=2C not due to faults in downstream links=2C proxies =
or servers.  It therefore provides an unambiguous indication
of the status of a server.=20

This information may be useful in situations where the RADIUS client does n=
ot receive a response to
an Access-Request.  A client may have multiple proxies configured=2C with o=
ne proxy marked
as primary and another marked as secondary.  If the client does not
receive a response to a request sent to the primary proxy=2C it can
"fail over" to the secondary=2C and send requests to the secondary
instead of to the primary proxy.

However=2C it is possible that the lack of a response to requests sent
to the primary proxy was due not to a failure within the the
primary=2C but to alternative causes such as a failed link along the=20
path to the destination server=2C or the failure of the destination server.=
=20

In such a situation=2C it may be useful for the client to be able to
distinguish between failure causes so that it does not trigger failover
inappropriately.  For example=2C if the primary proxy is down=2C then quick
failover to the secondary proxy would be prudent=2C whereas if a downstream
failure is the cause=2C  then the value of failover to a secondary proxy wi=
ll
depend on whether packets forwarded by the secondary will utilize independe=
nt
links=2C intermediaries or destination servers.

The Status-Server packet is not a "Keep-Alive" as discussed in
[RFC2865] Section 2.6.  "Keep-Alives" are Access-Request packets sent to
determine whether a downstream server is responsive.  These packets
are typically sent only when a server is suspected to be down=2C and are
no longer sent as soon as the server is available again.=20


 		 	   		  =

--_e6303a6f-9138-4e94-9116-b1205323940c_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Overall=2C I believe that this document is very close to being ready for su=
bmission to the IESG as an Informational RFC. <br><br>Section 1.1<br><pre c=
lass=3D"newpage"><br>   This specification is also limited to being a "hop =
by hop" query.<br><br>   When RADIUS packets transition one or more RADIUS =
Proxies=2C any<br>   information about the status of downstreamservers is u=
navailable to<br>   the client.  In addition=2C it queries only the status =
of a RADIUS<br>   server=2C cannot carry information about specific realms.=
<br><br>   These limitations are discussed in more detail below.<br><br><br=
>[BA] My suggestion is that this material be moved to Section 2=2C since it=
 doesn't relate to the<br>reasons why publication is recommended as an Info=
rmational RFC. <br><br>Section 2<br><br>This section includes a statement o=
f the problem and justification for why the Status-Server solution was<br>c=
hosen.   My suggestion is to begin this section with an explanation of what=
 Status-Server does=2C then move<br>on from there.  <br><br>Suggested rewri=
te: <br><br>Status-Server packets are sent by a RADIUS client to a RADIUS s=
erver in order to test the status of that <br>server.  Since a Status-Serve=
r packet MUST NOT be forwarded by a RADIUS proxy or server=2C the destinati=
on<br>of a Status-Server packet is set to that of the server which is being=
 tested.  As a result=2C the <br>client is provided with an indication of t=
he status of that server only=2C since no RADIUS proxies <br>are on the pat=
h between the RADIUS client and server.  Since servers respond to a Status-=
Server packet <br>without examining the  User-Name attribute=2C the respons=
e to a Status-Server packet cannot be used to <br>infer any information abo=
ut the reachability of specific realms.<br><br>The "hop by hop" functionali=
ty of Status-Server packets is useful to RADIUS clients attempting to deter=
mine<br>the status of elements on the path between the client and a server.=
   Since the Status-Server packet <br>is non-forwardable=2C lack of a respo=
nse may only be due to packet loss or the failure of the server in the<br>d=
estination IP address=2C not due to faults in downstream links=2C proxies o=
r servers.  It therefore provides an unambiguous indication<br>of the statu=
s of a server. <br><br>This information may be useful in situations where t=
he RADIUS client does not receive a response to<br>an Access-Request.  A cl=
ient may have multiple proxies configured=2C with one proxy marked<br>as pr=
imary and another marked as secondary.  If the client does not<br>receive a=
 response to a request sent to the primary proxy=2C it can<br>"fail over" t=
o the secondary=2C and send requests to the secondary<br>instead of to the =
primary proxy.<br><br>However=2C it is possible that the lack of a response=
 to requests sent<br>to the primary proxy was due not to a failure within t=
he the<br>primary=2C but to alternative causes such as a failed link along =
the <br>path to the destination server=2C or the failure of the destination=
 server. <br><br>In such a situation=2C it may be useful for the client to =
be able to<br>distinguish between failure causes so that it does not trigge=
r failover<br>inappropriately.  For example=2C if the primary proxy is down=
=2C then quick<br>failover to the secondary proxy would be prudent=2C where=
as if a downstream<br>failure is the cause=2C  then the value of failover t=
o a secondary proxy will<br>depend on whether packets forwarded by the seco=
ndary will utilize independent<br>links=2C intermediaries or destination se=
rvers.<br><br>The Status-Server packet is not a "Keep-Alive" as discussed i=
n<br><a href=3D"http://tools.ietf.org/html/rfc2865#section-2.6">[RFC2865] S=
ection&nbsp=3B2.6</a>.  "Keep-Alives" are Access-Request packets sent to<br=
>determine whether a downstream server is responsive.  These packets<br>are=
 typically sent only when a server is suspected to be down=2C and are<br>no=
 longer sent as soon as the server is available again. <br><br><br></pre> 	=
	 	   		  </body>
</html>=

--_e6303a6f-9138-4e94-9116-b1205323940c_--

--
to unsubscribe send a message to 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 Feb  6 16:33:35 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98F4E3A68B8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 16:33:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.039
X-Spam-Level: 
X-Spam-Status: No, score=-1.039 tagged_above=-999 required=5 tests=[AWL=-0.545, 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 GZFxDZkEuBGL for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 16:33:34 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 83C983A6996 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 16:33:34 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Ndv4f-0006Gk-CZ for radiusext-data0@psg.com; Sun, 07 Feb 2010 00:32:29 +0000
Received: from [65.55.116.44] (helo=blu0-omc1-s33.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Ndv4d-0006GX-9U for radiusext@ops.ietf.org; Sun, 07 Feb 2010 00:32:27 +0000
Received: from BLU137-W6 ([65.55.116.7]) by blu0-omc1-s33.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 16:32:26 -0800
Message-ID: <BLU137-W6861B435730E1D4BA388293520@phx.gbl>
Content-Type: multipart/alternative; boundary="_34f144e5-0f72-47bb-b6f9-d40329427b27_"
X-Originating-IP: [72.11.66.126]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-status-server-05 (Part II)
Date: Sat, 6 Feb 2010 16:32:26 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2010 00:32:26.0595 (UTC) FILETIME=[05F99330:01CAA78D]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_34f144e5-0f72-47bb-b6f9-d40329427b27_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Sections 2.1 and Section 2.2

Section 2 explains the unique properties of Status-Server and why a RADIUS =
client might want to use it.  RFC 2865 Section 2.6
explains why "keepalives" are a bad idea.  Presumably this advice applies t=
o both RADIUS Access-Request and Accounting-Request keepalives.  Given that=
=2C Sections 2.1 and 2.2 belabor the point.  I'd suggest that they be delet=
ed.=20

Section 2.3

I would suggest deleting this section as well.=20

Section 2.3.1

My advice is to incorporate the material in this section into Section 2 (To=
 be retitled Overview).=20

Section 3

     Response Authenticator

         The value of the Authenticator field in Access-Accept=2C or
         Accounting-Response packets is called the Response
         Authenticator=2C and contains a one-way MD5 hash calculated over
         a stream of octets consisting of: the RADIUS packet=2C beginning
         with the Code field=2C including the Identifier=2C the Length=2C t=
he
         Request Authenticator field from the Status-Server packet=2C and
         the response Attributes (if any)=2C followed by the shared
         secret.  That is=2C ResponseAuth =3D
         MD5(Code+ID+Length+RequestAuth+Attributes+Secret) where +
         denotes concatenation.

[BA] Why is this material here?  If you need it at all (I don't think so)=
=2C you can just reference
RFC 2865 and/or 2866.=20

   Status-Server packets MAY include NAS-Identifier=2C and one of NAS-IP-
   Address or NAS-IPv6-Address.  These attributes are not necessary for
   the operation of Status-Server=2C but may be useful information to a
   server that receives those packets.

[BA] You might say that the server MUST ignore other attributes.=20

   Other attributes SHOULD NOT be included in a Status-Server packet.
   User authentication credentials such as User-Password=2C CHAP-Password=
=2C
   EAP-Message=2C etc. MUST NOT appear in a Status-Server packet sent to a
   RADIUS authentication port.  User or NAS accounting attributes such
   as Acct-Session-Id=2C Acct-Status-Type=2C Acct-Input-Octets=2C etc.  MUS=
T
   NOT appear in a Status-Server packet sent to a RADIUS accounting
   port.

[BA] Also=2C presumably User-Name is not included (relevant to the point ab=
out realms made earlier).=20



 		 	   		  =

--_34f144e5-0f72-47bb-b6f9-d40329427b27_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Sections 2.1 and Section 2.2<br><br>Section 2 explains the unique propertie=
s of Status-Server and why a RADIUS client might want to use it.&nbsp=3B RF=
C 2865 Section 2.6<br>explains why "keepalives" are a bad idea.&nbsp=3B Pre=
sumably this advice applies to both RADIUS Access-Request and Accounting-Re=
quest keepalives.&nbsp=3B Given that=2C Sections 2.1 and 2.2 belabor the po=
int.&nbsp=3B I'd suggest that they be deleted. <br><br>Section 2.3<br><br>I=
 would suggest deleting this section as well. <br><br>Section 2.3.1<br><br>=
My advice is to incorporate the material in this section into Section 2 (To=
 be retitled Overview). <br><br>Section 3<br><br><pre class=3D"newpage">   =
  Response Authenticator<br><br>         The value of the Authenticator fie=
ld in Access-Accept=2C or<br>         Accounting-Response packets is called=
 the Response<br>         Authenticator=2C and contains a one-way MD5 hash =
calculated over<br>         a stream of octets consisting of: the RADIUS pa=
cket=2C beginning<br>         with the Code field=2C including the Identifi=
er=2C the Length=2C the<br>         Request Authenticator field from the St=
atus-Server packet=2C and<br>         the response Attributes (if any)=2C f=
ollowed by the shared<br>         secret.  That is=2C ResponseAuth =3D<br> =
        MD5(Code+ID+Length+RequestAuth+Attributes+Secret) where +<br>      =
   denotes concatenation.<br><br>[BA] Why is this material here?  If you ne=
ed it at all (I don't think so)=2C you can just reference<br>RFC 2865 and/o=
r 2866. <br><br>   Status-Server packets MAY include NAS-Identifier=2C and =
one of NAS-IP-<br>   Address or NAS-IPv6-Address.  These attributes are not=
 necessary for<br>   the operation of Status-Server=2C but may be useful in=
formation to a<br>   server that receives those packets.<br><br>[BA] You mi=
ght say that the server MUST ignore other attributes. <br><br>   Other attr=
ibutes SHOULD NOT be included in a Status-Server packet.<br>   User authent=
ication credentials such as User-Password=2C CHAP-Password=2C<br>   EAP-Mes=
sage=2C etc. MUST NOT appear in a Status-Server packet sent to a<br>   RADI=
US authentication port.  User or NAS accounting attributes such<br>   as Ac=
ct-Session-Id=2C Acct-Status-Type=2C Acct-Input-Octets=2C etc.  MUST<br>   =
NOT appear in a Status-Server packet sent to a RADIUS accounting<br>   port=
.<br><br>[BA] Also=2C presumably User-Name is not included (relevant to the=
 point about realms made earlier). <br><br><br><br></pre> 		 	   		  </body=
>
</html>=

--_34f144e5-0f72-47bb-b6f9-d40329427b27_--

--
to unsubscribe send a message to 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 Feb  6 16:50:45 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED4D13A6C6E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 16:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.03
X-Spam-Level: 
X-Spam-Status: No, score=-1.03 tagged_above=-999 required=5 tests=[AWL=-0.536, 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 hsLuVrNTlZAr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 16:50:45 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EDFE23A6B10 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 16:50:44 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NdvJW-0007Uz-W3 for radiusext-data0@psg.com; Sun, 07 Feb 2010 00:47:50 +0000
Received: from [65.55.116.38] (helo=blu0-omc1-s27.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NdvJU-0007Uo-3G for radiusext@ops.ietf.org; Sun, 07 Feb 2010 00:47:48 +0000
Received: from BLU137-W19 ([65.55.116.7]) by blu0-omc1-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 16:47:47 -0800
Message-ID: <BLU137-W1951B040BEFCE55D331E9D93520@phx.gbl>
Content-Type: multipart/alternative; boundary="_0544eaae-d222-4b38-81d4-343cf222f213_"
X-Originating-IP: [72.11.66.126]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-status-server-05 (part III)
Date: Sat, 6 Feb 2010 16:47:47 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2010 00:47:47.0444 (UTC) FILETIME=[2AD7FB40:01CAA78F]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_0544eaae-d222-4b38-81d4-343cf222f213_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Section 4.3

On reading this section I am unsure about whether the discussion relates to=
 failover between proxies or servers.=20
Suggested rewrite:

4.3.  Fail-over with Status-Server

   A client may wish to failover from one proxy to another in the event tha=
t it does not receive a=20
   response to an Access-Request.  In order to determine whether the lack o=
f response is due to a=20
   problem with the proxy or a downstream server=2C  the client can send pe=
riodic Status-Server packets=20
   to a proxy after lack of a response.  The inter-packet period is Tw=2C a=
s described in Section 4.1.=20

   These packets will help the client determine if the failure was due to a=
n issue on the path between
   the client and proxy or the proxy itself=2C or whether the issue is occu=
rring downstream.=20

   If no response is received to Status-Server packets=2C the RADIUS client=
 can initiate failover to=20
   another proxy.  By continuing to send Status-Server packets to the origi=
nal proxy at an interval
   of Tw=2C the RADIUS client can determine when the original proxy becomes=
 responsive again.=20

   Once three time periods have passed where Status-Server packets have
   been sent and responded to=2C the original proxy should be deemed respon=
sive
   and RADIUS requests may sent to it again.  This determination should
   be made separately for each proxy that the client has a relationship
   with.  The same algorithm should be used for both authentication and
   accounting ports.  The client MUST treat each destination (ip=2C port)
   combination as a unique proxy for the purposes of this
   determination.

   The above behavior is modelled after [RFC3539] Section 3.4.1.  We
   note that if a reliable transport is used for RADIUS=2C then the
   algorithms specified in [RFC3539] MUST be used in preference to the
   ones given here.
Section 5

You might want to add a table entry for User-Name.=20
 		 	   		  =

--_0544eaae-d222-4b38-81d4-343cf222f213_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Section 4.3<br><br>On reading this section I am unsure about whether the di=
scussion relates to failover between proxies or servers. <br>Suggested rewr=
ite:<br><br><pre class=3D"newpage"><span class=3D"h3"><h3><a name=3D"sectio=
n-4.3">4.3</a>.  Fail-over with Status-Server</h3></span><br><br>   A clien=
t may wish to failover from one proxy to another in the event that it does =
not receive a <br>   response to an Access-Request.  In order to determine =
whether the lack of response is due to a <br>   problem with the proxy or a=
 downstream server=2C  the client can send periodic Status-Server packets <=
br>   to a proxy after lack of a response.  The inter-packet period is Tw=
=2C as described in Section 4.1. <br><br>   These packets will help the cli=
ent determine if the failure was due to an issue on the path between<br>   =
the client and proxy or the proxy itself=2C or whether the issue is occurri=
ng downstream. <br><br>   If no response is received to Status-Server packe=
ts=2C the RADIUS client can initiate failover to <br>   another proxy.  By =
continuing to send Status-Server packets to the original proxy at an interv=
al<br>   of Tw=2C the RADIUS client can determine when the original proxy b=
ecomes responsive again. <br><br>   Once three time periods have passed whe=
re Status-Server packets have<br>   been sent and responded to=2C the origi=
nal proxy should be deemed responsive<br>   and RADIUS requests may sent to=
 it again.  This determination should<br>   be made separately for each pro=
xy that the client has a relationship<br>   with.  The same algorithm shoul=
d be used for both authentication and<br>   accounting ports.  The client M=
UST treat each destination (ip=2C port)<br>   combination as a unique proxy=
 for the purposes of this<br>   determination.<br><br>   The above behavior=
 is modelled after <a href=3D"http://tools.ietf.org/html/rfc3539#section-3.=
4.1">[RFC3539] Section&nbsp=3B3.4.1</a>.  We<br>   note that if a reliable =
transport is used for RADIUS=2C then the<br>   algorithms specified in [<a =
href=3D"http://tools.ietf.org/html/rfc3539" title=3D"&quot=3BAuthentication=
=2C Authorization=2C and Accounting (AAA) Transport Profile&quot=3B">RFC353=
9</a>] MUST be used in preference to the<br>   ones given here.<br></pre>Se=
ction 5<br><br>You might want to add a table entry for User-Name. <br> 		 	=
   		  </body>
</html>=

--_0544eaae-d222-4b38-81d4-343cf222f213_--

--
to unsubscribe send a message to 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 Feb  6 22:51:51 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D61813A7008 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 22:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.463
X-Spam-Level: *
X-Spam-Status: No, score=1.463 tagged_above=-999 required=5 tests=[AWL=-3.044, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_OBFU_SPLIT_HR2=0.183, TVD_SPACE_RATIO=2.219]
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 9fu6Qcw74qnj for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat,  6 Feb 2010 22:51:51 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B49033A7004 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat,  6 Feb 2010 22:51:50 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Ne0xI-0007MN-JK for radiusext-data0@psg.com; Sun, 07 Feb 2010 06:49:16 +0000
Received: from [65.55.116.22] (helo=blu0-omc1-s11.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Ne0xF-0007M2-If for radiusext@ops.ietf.org; Sun, 07 Feb 2010 06:49:13 +0000
Received: from BLU137-DS3 ([65.55.116.7]) by blu0-omc1-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Feb 2010 22:49:13 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS37AC01122F6C69A0C5D6493520@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
CC: "'Klaas Wierenga'" <klaas@wierenga.net>
Subject: RADEXT Virtual Interim
Date: Sat, 6 Feb 2010 22:50:58 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNAAlSU3Q
Content-Language: en-us
X-OriginalArrivalTime: 07 Feb 2010 06:49:13.0131 (UTC) FILETIME=[A88537B0:01CAA7C1]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN='radiusext@ops.ietf.org';RSVP=TRUE:mailto:radiusext@ops.ietf.or
	g
ATTENDEE;CN="'Klaas Wierenga'";ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:klaas@
	wierenga.net
CLASS:PUBLIC
CREATED:20100207T065058Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: 702-473-3463 #222622\n\nNote: The GM
	T offset above does not reflect daylight saving time adjustments.\n\n*~*~*
	~*~*~*~*~*~*~*\n\nThe IETF RADEXT WG will hold a Virtual Interim on Februa
	ry 23\, 2010 10:00:AM PST. To join the Dimdim event simply click here <htt
	ps://webmeeting.dimdim.com/portal/JoinForm.action?confKey=baboba&email=ber
	nard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&attendeePwd=>  \nYou can also join by entering the Meeting Roo
	m "baboba" at Dimdim.com <http://www.dimdim.com/join>  at the time listed 
	above.  <https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=babo
	ba&email=bernard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40
	-4fc0-9835-cf1fdfcc0a4b&attendeePwd>    \n\nMeeting : RADEXT Virtual Inter
	im  \nKey:   \nDial In: 702-473-3463 \nPass Code: 222622   \nStart: Februa
	ry 23\, 2010 10:00:AM PST (Add to Outlook <https://webmeeting.dimdim.com/p
	ortal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&email
	=bernard.aboba@gmail.com&attendeePwd=> )   \nSchedule Ends At: 12:30 PM PS
	T\n\nHint: You don't need to be a member of Dimdim to attend this meeting.
	\n\n It's easy to join and get started\, Click here to sign up for Dimdim 
	Free. <http://www.dimdim.com/registration/Dimdim_Signup.html>  \n\nBut you
	 may find it helpful to check your bandwidth and your A/V setup here <http
	://www.dimdim.com/support/dimdim_tools.html> . \n\n\nRADEXT Virtual Interi
	m Meeting\nTuesday\, February 23\, 2010\n10 AM - 12:30 PM Pacific Time\n\n
	Conferencing Details:\n\nSlide Presentations: http://www.drizzle.com/~abob
	a/RADEXT/Feb-Interim/\nJabber room:  radext at jabber.ietf.org (Please joi
	n)\nDial-in Audioconference details:  http://ops.ietf.org/lists/radiusext/
	2010/msg00161.html\n\nAgenda\n\n10 AM - 10:15 AM PT: Preliminaries \n\n   
	  Conference issues/debugging\n     Attendance\n     Note takers\n     Age
	nda bash\n\nDesign Guidelines (60 minutes)\n\n10:15 AM - 11:15 AM PT Desig
	n Guidelines\, Alan DeKok (60 minutes)\nhttp://tools.ietf.org/html/draft-i
	etf-radext-design-guidelines\n\nRADSEC (60 minutes)\n\n11:15 AM - 11:30 AM
	 PT  RADSEC\, Stefan Winter (15 minutes)\nhttp://tools.ietf.org/html/draft
	-ietf-radext-radsec\n\n11:30 AM - 11:45 AM PT NAI-Based Peer Discovery\, S
	tefan Winter (15 minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-dy
	namic-discovery\n\n11:45 AM - 12:00 PM PT  Status-Server\, Alan DeKok (15 
	minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-status-server\n\n12
	:00 PM PT - 12:15 PM PT RADIUS over TCP\, Alan DeKok (15 minutes)\nhttp://
	tools.ietf.org/html/draft-ietf-radext-tcp-transport\n\n\nWrap-up (15 minut
	es)\n\n12:15 PM PT – 12:30 PM PT   Discussion and Next Steps:  WG Chairs
	 & ADs (15 minutes)\n
DTEND:20100223T203000Z
DTSTAMP:20100207T065058Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100207T065058Z
LOCATION:702-473-3463 #222622
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:2
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: 702-473-3463 #222622</FONT></SPAN></P>\n\
	n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset a
	bove does not reflect daylight saving time adjustments.</FONT></SPAN></P>\
	n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*<
	/FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Th
	e IETF RADEXT WG will hold a Virtual Interim on</FONT></SPAN><SPAN LANG="e
	n-us"><B> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PST</FONT></B><
	/SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.</FONT></SPAN><SPAN LANG="e
	n-us"> </SPAN><A HREF="https://webmeeting.dimdim.com/portal/JoinForm.actio
	n?confKey=baboba&amp\;email=bernard.aboba@gmail.com&amp\;asPresenter=false
	&amp\;meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp\;attendeePwd="><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">To join the Dimdi
	m event simply click here</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><
	SPAN LANG="en-us"><FONT FACE="Calibri"><BR>\nYou can also join by entering
	 the Meeting Room &quot\;baboba&quot\; at</FONT></SPAN><SPAN LANG="en-us">
	 </SPAN><A HREF="http://www.dimdim.com/join"><SPAN LANG="en-us"><U><FONT C
	OLOR="#0000FF" FACE="Calibri">Dimdim.com</FONT></U></SPAN><SPAN LANG="en-u
	s"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri"> at the time listed 
	above.</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="https://webmeeting
	.dimdim.com/portal/JoinForm.action?confKey=baboba&amp\;email=bernard.aboba
	@gmail.com&amp\;asPresenter=false&amp\;meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&amp\;attendeePwd"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"
	></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calib
	ri"></FONT></SPAN><SPAN LANG="en-us"></SPAN></SPAN><SPAN LANG="en-us"> <FO
	NT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><
	B><FONT FACE="Calibri">Meeting :</FONT></B></SPAN><SPAN LANG="en-us"> <FON
	T FACE="Calibri">RADEXT Virtual Interim  </FONT></SPAN></P>\n\n<P DIR=LTR
	><SPAN LANG="en-us"><B><FONT FACE="Calibri">Key:</FONT></B></SPAN><SPAN LA
	NG="en-us"> <FONT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN
	 LANG="en-us"><B><FONT FACE="Calibri">Dial In:</FONT></B></SPAN><SPAN LANG
	="en-us"> <FONT FACE="Calibri">702-473-3463 </FONT></SPAN></P>\n\n<P DIR=L
	TR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Pass Code:</FONT></B></SPAN>
	<SPAN LANG="en-us"> <FONT FACE="Calibri">222622   </FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Start:</FONT></B></SP
	AN><SPAN LANG="en-us"> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PS
	T (</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="https://webmeeting.dim
	dim.com/portal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0
	a4b&amp\;email=bernard.aboba@gmail.com&amp\;attendeePwd="><SPAN LANG="en-u
	s"><U><FONT COLOR="#0000FF" FACE="Calibri">Add to Outlook</FONT></U></SPAN
	><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">) 
	  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Cali
	bri">Schedule Ends At:</FONT></B></SPAN><SPAN LANG="en-us"> <FONT FACE="Ca
	libri">12:30 PM PST<BR>\n<BR>\n</FONT></SPAN><SPAN LANG="en-us"><B><FONT F
	ACE="Calibri">Hint:</FONT></B></SPAN><SPAN LANG="en-us"><FONT FACE="Calibr
	i"> You don't need to be a member of Dimdim to attend this meeting.</FONT>
	</SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;I
	t's easy to join and get started\,</FONT></SPAN><SPAN LANG="en-us"> </SPAN
	><A HREF="http://www.dimdim.com/registration/Dimdim_Signup.html"><SPAN LAN
	G="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">Click here to sign up fo
	r Dimdim Free.</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="
	en-us"><FONT FACE="Calibri"> </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="
	en-us"><FONT FACE="Calibri">But you may find it helpful to check your band
	width and your A/V setup</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="
	http://www.dimdim.com/support/dimdim_tools.html"><SPAN LANG="en-us"><U><FO
	NT COLOR="#0000FF" FACE="Calibri">here</FONT></U></SPAN><SPAN LANG="en-us"
	></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">.<BR>\n</FONT></SPAN><
	/P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG=
	"en-us"><FONT FACE="Calibri">RADEXT Virtual Interim Meeting<BR>\nTuesday\,
	 February 23\, 2010<BR>\n10 AM - 12:30 PM Pacific Time<BR>\n<BR>\nConferen
	cing Details:<BR>\n<BR>\nSlide Presentations:</FONT></SPAN><SPAN LANG="en-
	us"> </SPAN><A HREF="http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://www.drizzl
	e.com/~aboba/RADEXT/Feb-Interim/</FONT></U></SPAN><SPAN LANG="en-us"></SPA
	N></A><SPAN LANG="en-us"><BR>\n<FONT FACE="Calibri">Jabber room:  radext 
	at jabber.ietf.org (Please join)<BR>\nDial-in Audioconference details: </
	FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.org/lists/
	radiusext/2010/msg00161.html"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" 
	FACE="Calibri">http://ops.ietf.org/lists/radiusext/2010/msg00161.html</FON
	T></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><BR>\n<BR>\n
	<FONT FACE="Calibri">Agenda<BR>\n<BR>\n10 AM - 10:15 AM PT: Preliminaries<
	BR>\n<BR>\n     Conference issues/debugging<BR>\n     Attendance<B
	R>\n     Note takers<BR>\n     Agenda bash<BR>\n<BR>\nDesign Guide
	lines (60 minutes)<BR>\n<BR>\n10:15 AM - 11:15 AM PT Design Guidelines\, A
	lan DeKok (60 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HRE
	F="http://tools.ietf.org/html/draft-ietf-radext-design-guidelines"><SPAN L
	ANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf.org/
	html/draft-ietf-radext-design-guidelines</FONT></U></SPAN><SPAN LANG="en-u
	s"></SPAN></A><SPAN LANG="en-us"><BR>\n<BR>\n<FONT FACE="Calibri">RADSEC (
	60 minutes)<BR>\n<BR>\n11:15 AM - 11:30 AM PT  RADSEC\, Stefan Winter (15
	 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="http://too
	ls.ietf.org/html/draft-ietf-radext-radsec"><SPAN LANG="en-us"><U><FONT COL
	OR="#0000FF" FACE="Calibri">http://tools.ietf.org/html/draft-ietf-radext-r
	adsec</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><B
	R>\n<BR>\n<FONT FACE="Calibri">11:30 AM - 11:45 AM PT NAI-Based Peer Disco
	very\, Stefan Winter (15 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></
	SPAN><A HREF="http://tools.ietf.org/html/draft-ietf-radext-dynamic-discove
	ry"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tool
	s.ietf.org/html/draft-ietf-radext-dynamic-discovery</FONT></U></SPAN><SPAN
	 LANG="en-us"></SPAN></A><SPAN LANG="en-us"><BR>\n<BR>\n<FONT FACE="Calibr
	i">11:45 AM - 12:00 PM PT  Status-Server\, Alan DeKok (15 minutes)<BR>\n<
	/FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="http://tools.ietf.org/html
	/draft-ietf-radext-status-server"><SPAN LANG="en-us"><U><FONT COLOR="#0000
	FF" FACE="Calibri">http://tools.ietf.org/html/draft-ietf-radext-status-ser
	ver</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><BR>
	\n<BR>\n<FONT FACE="Calibri">12:00 PM PT - 12:15 PM PT RADIUS over TCP\, A
	lan DeKok (15 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HRE
	F="http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><SPAN LANG=
	"en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf.org/html
	/draft-ietf-radext-tcp-transport</FONT></U></SPAN><SPAN LANG="en-us"></SPA
	N></A><SPAN LANG="en-us"><BR>\n<BR>\n<BR>\n<FONT FACE="Calibri">Wrap-up (1
	5 minutes)<BR>\n<BR>\n12:15 PM PT – 12:30 PM PT   Discussion and Next 
	Steps:  WG Chairs &amp\; ADs (15 minutes)</FONT></SPAN><SPAN LANG="en-us"
	></SPAN></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTLASTSEQUENCE:1
X-MS-OLK-APPTSEQTIME:20100206T195856Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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

From owner-radiusext@ops.ietf.org  Sun Feb  7 01:15:15 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D428E3A7016 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun,  7 Feb 2010 01:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level: 
X-Spam-Status: No, score=-3.047 tagged_above=-999 required=5 tests=[AWL=-2.552, 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 qZdgqflUlPIQ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun,  7 Feb 2010 01:15:13 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7E6603A6898 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun,  7 Feb 2010 01:15:13 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Ne3CF-000Gx6-0f for radiusext-data0@psg.com; Sun, 07 Feb 2010 09:12:51 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1Ne3CB-000Gwo-Mi for radiusext@ops.ietf.org; Sun, 07 Feb 2010 09:12:47 +0000
Message-ID: <4B6E8410.6080801@deployingradius.com>
Date: Sun, 07 Feb 2010 10:12:48 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: RADEXT Virtual Interim Agenda, Take One
References: <BLU137-W11E7A39B6E682E9624AF8793530@phx.gbl>
In-Reply-To: <BLU137-W11E7A39B6E682E9624AF8793530@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> 10:15 AM - 11:15 AM PT Design Guidelines, Alan DeKok (60 minutes)
> http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

  Avi, etc.: Please provide a review of of the proposed -11 at

http://git.freeradius.org/ietf/

  This will help make the interim meeting more efficient.

  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 Feb 10 13:56:23 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BC3B3A75F9 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 13:56:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.231
X-Spam-Level: 
X-Spam-Status: No, score=-0.231 tagged_above=-999 required=5 tests=[AWL=-1.226, BAYES_05=-1.11, 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 viH-R0CiJqI1 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 13:56:20 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B02943A77C0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 10 Feb 2010 13:56:19 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NfKVN-000Q0m-66 for radiusext-data0@psg.com; Wed, 10 Feb 2010 21:53:53 +0000
Received: from [65.55.116.30] (helo=blu0-omc1-s19.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NfKVJ-000Q0A-By for radiusext@ops.ietf.org; Wed, 10 Feb 2010 21:53:49 +0000
Received: from BLU137-DS5 ([65.55.116.9]) by blu0-omc1-s19.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 13:53:48 -0800
X-Originating-IP: [131.107.0.77]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS570599EE0D8C6B358FD13934F0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take Two
Date: Wed, 10 Feb 2010 13:53:47 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004A_01CAAA58.78127540"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mA=
Content-Language: en-us
X-OriginalArrivalTime: 10 Feb 2010 21:53:48.0606 (UTC) FILETIME=[8676B5E0:01CAAA9B]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_004A_01CAAA58.78127540
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (60 minutes)

11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines


Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


------=_NextPart_000_004A_01CAAA58.78127540
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time<br>
<br>
Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines (60 =
minutes)<br>
<br>
11:15 AM &#8211; 12:15 PM PT Design Guidelines, Alan DeKok (60 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_004A_01CAAA58.78127540--

--
to unsubscribe send a message to 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 Feb 10 20:55:54 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6666228C0D6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 20:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.966
X-Spam-Level: 
X-Spam-Status: No, score=-0.966 tagged_above=-999 required=5 tests=[AWL=-0.472, 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 SGSH3bHZkkg4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 20:55:52 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5CA9728C17B for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 10 Feb 2010 20:55:52 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NfR2T-0005KK-3p for radiusext-data0@psg.com; Thu, 11 Feb 2010 04:52:29 +0000
Received: from [65.55.116.18] (helo=blu0-omc1-s7.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NfR2M-0005Ih-Vl for radiusext@ops.ietf.org; Thu, 11 Feb 2010 04:52:23 +0000
Received: from BLU137-DS6 ([65.55.116.7]) by blu0-omc1-s7.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 20:52:22 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS6E2C2B13FFF8C7F31A223934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Updated RADEXT Virtual Interim Conference Parameters
Date: Wed, 10 Feb 2010 20:53:02 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0152_01CAAA93.0947DF20"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acqq08fGATi+Z0ibT8mY/2G7aWWbmAAAgpCg
Content-Language: en-us
X-OriginalArrivalTime: 11 Feb 2010 04:52:22.0176 (UTC) FILETIME=[FF516200:01CAAAD5]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_0152_01CAAA93.0947DF20
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

IETF Secretariat invites you to attend this online meeting.=20

Topic: RADEXT WG Virtual Meeting=20
Date: Tuesday, February 23, 2010=20
Time: 10:00 am, Pacific Standard Time (San Francisco, GMT-08:00)=20
Meeting Number: 962 354 516=20
Meeting Password: (This meeting does not require a password.)=20


-------------------------------------------------------=20
To join the online meeting (Now from iPhones too!)=20
-------------------------------------------------------=20
1. Go to https://workgreen.webex.com/workgreen/j.php?ED=3D131933892 =
<https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&UID=3D1115189=
972&RT=3DMiM0> &UID=3D1115189972&RT=3DMiM0=20
2. Enter your name and email address.=20
3. Enter the meeting password: (This meeting does not require a =
password.)=20
4. Click "Join Now".=20

To view in other time zones or languages, please click the link:=20
https://workgreen.webex.com/workgreen/j.php?ED=3D131933892 =
<https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&UID=3D1115189=
972&ORT=3DMiM0> &UID=3D1115189972&ORT=3DMiM0=20

-------------------------------------------------------=20
To join the audio conference only=20
-------------------------------------------------------=20
To receive a call back, provide your phone number when you join the =
meeting, or call the number below and enter the access code.=20
Call-in toll number (US/Canada): 1-408-792-6300=20
Global call-in numbers: =
https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=3DMC =
<https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=3DMC&=
ED=3D131933892&tollFree=3D0> &ED=3D131933892&tollFree=3D0=20

Access code:962 354 516=20

-------------------------------------------------------=20
For assistance=20
-------------------------------------------------------=20
1. Go to https://workgreen.webex.com/workgreen/mc=20
2. On the left navigation bar, click "Support".=20

You can contact me at:=20
amorris@amsl.com=20
1-510-492-4081=20

To add this meeting to your calendar program (for example Microsoft =
Outlook), click this link:=20
https://workgreen.webex.com/workgreen/j.php?ED=3D131933892 =
<https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&UID=3D1115189=
972&ICS=3DMI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DPpj3MUqKboUgp-uDBR-4R-ROZCDrjedd=
whYuFW9GSq8=3D&RT=3DMiM0> =
&UID=3D1115189972&ICS=3DMI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DPpj3MUqKboUgp-uDBR=
-4R-ROZCDrjeddwhYuFW9GSq8=3D&RT=3DMiM0=20

The playback of UCF (Universal Communications Format) rich media files =
requires appropriate players. To view this type of rich media files in =
the meeting, please check whether you have the players installed on your =
computer by going to =
https://workgreen.webex.com/workgreen/systemdiagnosis.php=20

Sign up for a free trial of WebEx=20
http://www.webex.com/go/mcemfreetrial=20

http://www.webex.com=20



IMPORTANT NOTICE: This WebEx service includes a feature that allows =
audio and any documents and other materials exchanged or viewed during =
the session to be recorded. By joining this session, you automatically =
consent to such recordings. If you do not consent to the recording, do =
not join the session.=20


------=_NextPart_000_0152_01CAAA93.0947DF20
Content-Type: text/html; charset="UTF-8"
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=3Dutf-8">
<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;}
 /* 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>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>IETF
Secretariat invites you to attend this online meeting. <br>
<br>
Topic: RADEXT WG Virtual Meeting <br>
Date: Tuesday, February 23, 2010 <br>
<span style=3D'color:black'>Time: 10:00 am, Pacific Standard Time (San =
Francisco,
GMT-08:00)</span> <br>
Meeting Number: 962 354 516 <br>
Meeting Password: (This meeting does not require a password.) <br>
<br>
<br>
------------------------------------------------------- <br>
To join the online meeting (Now from iPhones too!) <br>
------------------------------------------------------- <br>
1. Go to <a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&amp;UI=
D=3D1115189972&amp;RT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D131933=
892&amp;UID=3D1115189972&amp;RT=3DMiM0</a>
<br>
2. Enter your name and email address. <br>
3. Enter the meeting password: (This meeting does not require a =
password.) <br>
4. Click &quot;Join Now&quot;. <br>
<br>
To view in other time zones or languages, please click the link: <br>
<a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&amp;UI=
D=3D1115189972&amp;ORT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D131933=
892&amp;UID=3D1115189972&amp;ORT=3DMiM0</a>
<br>
<br>
------------------------------------------------------- <br>
To join the audio conference only <br>
------------------------------------------------------- <br>
To receive a call back, provide your phone number when you join the =
meeting, or
call the number below and enter the access code. <br>
Call-in toll number (US/Canada): 1-408-792-6300 <br>
Global call-in numbers: <a
href=3D"https://workgreen.webex.com/workgreen/globalcallin.php?serviceTyp=
e=3DMC&amp;ED=3D131933892&amp;tollFree=3D0"
target=3D"_blank">https://workgreen.webex.com/workgreen/globalcallin.php?=
serviceType=3DMC&amp;ED=3D131933892&amp;tollFree=3D0</a>
<br>
<br>
Access code:962 354 516 <br>
<br>
------------------------------------------------------- <br>
For assistance <br>
------------------------------------------------------- <br>
1. Go to <a href=3D"https://workgreen.webex.com/workgreen/mc" =
target=3D"_blank">https://workgreen.webex.com/workgreen/mc</a>
<br>
2. On the left navigation bar, click &quot;Support&quot;. <br>
<br>
You can contact me at: <br>
<a href=3D"mailto:amorris@amsl.com">amorris@amsl.com</a> <br>
1-510-492-4081 <br>
<br>
To add this meeting to your calendar program (for example Microsoft =
Outlook),
click this link: <br>
<a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&amp;UI=
D=3D1115189972&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SHA2=3DP=
pj3MUqKboUgp-uDBR-4R-ROZCDrjeddwhYuFW9GSq8=3D&amp;RT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D131933=
892&amp;UID=3D1115189972&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&am=
p;SHA2=3DPpj3MUqKboUgp-uDBR-4R-ROZCDrjeddwhYuFW9GSq8=3D&amp;RT=3DMiM0</a>=

<br>
<br>
The playback of UCF (Universal Communications Format) rich media files =
requires
appropriate players. To view this type of rich media files in the =
meeting,
please check whether you have the players installed on your computer by =
going
to <a href=3D"https://workgreen.webex.com/workgreen/systemdiagnosis.php"
target=3D"_blank">https://workgreen.webex.com/workgreen/systemdiagnosis.p=
hp</a> <br>
<br>
Sign up for a free trial of WebEx <br>
<a href=3D"http://www.webex.com/go/mcemfreetrial" =
target=3D"_blank">http://www.webex.com/go/mcemfreetrial</a>
<br>
<br>
<a href=3D"http://www.webex.com" =
target=3D"_blank">http://www.webex.com</a> <br>
<br>
<br>
<br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows =
audio and
any documents and other materials exchanged or viewed during the session =
to be
recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, do not join the =
session. </span><o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0152_01CAAA93.0947DF20--

--
to unsubscribe send a message to 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 Feb 10 20:58:14 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBB5A28C17B for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 20:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.449
X-Spam-Level: *
X-Spam-Status: No, score=1.449 tagged_above=-999 required=5 tests=[AWL=-2.875, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, TVD_SPACE_RATIO=2.219]
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 Q-CPnrwEnT+0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 20:58:14 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BFCD428C0D6 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 10 Feb 2010 20:58:13 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NfR6v-0005ub-Vo for radiusext-data0@psg.com; Thu, 11 Feb 2010 04:57:06 +0000
Received: from [65.55.116.32] (helo=blu0-omc1-s21.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NfR6s-0005uJ-Mj for radiusext@ops.ietf.org; Thu, 11 Feb 2010 04:57:02 +0000
Received: from BLU137-DS6 ([65.55.116.7]) by blu0-omc1-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 20:57:02 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS6E50466CDC7C50900A285934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
CC: "'Klaas Wierenga'" <klaas@wierenga.net>
Subject: RADEXT Virtual Interim
Date: Wed, 10 Feb 2010 20:57:41 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNADqfvdg
Content-Language: en-us
X-OriginalArrivalTime: 11 Feb 2010 04:57:02.0076 (UTC) FILETIME=[A626BBC0:01CAAAD6]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN='radiusext@ops.ietf.org';RSVP=TRUE:mailto:radiusext@ops.ietf.or
	g
ATTENDEE;CN="'Klaas Wierenga'";ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:klaas@
	wierenga.net
CLASS:PUBLIC
CREATED:20100211T045741Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: WebEx\n\nNote: The GMT offset above 
	does not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\
	n\nRADEXT Virtual Interim Meeting\nTuesday\, February 23\, 2010\n10 AM - 1
	2:30 PM Pacific Time\n\nJabber room (please join):  radext at jabber.ietf.
	org\nAgenda: http://ops.ietf.org/lists/radiusext/2010/msg00168.html\nPrese
	ntations:  http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/\nWebEx parame
	ters:  http://ops.ietf.org/lists/radiusext/2010/msg00169.html\n\n
DTEND:20100223T203000Z
DTSTAMP:20100211T045741Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100211T045741Z
LOCATION:WebEx
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:3
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: WebEx</FONT></SPAN></P>\n\n<P DIR=LTR><SP
	AN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset above does not r
	eflect daylight saving time adjustments.</FONT></SPAN></P>\n\n<P DIR=LTR><
	SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*</FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN
	 LANG="en-us"><FONT COLOR="#000000" SIZE=2 FACE="Verdana">RADEXT Virtual I
	nterim Meeting<BR>\nTuesday\, February 23\, 2010<BR>\n10 AM - 12:30 PM Pac
	ific Time</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN 
	LANG="en-us"></SPAN><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Jabber r
	oom (please join):&nbsp\; radext at jabber.ietf.org</FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Agenda:</FONT></SP
	AN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.org/lists/radiusext
	/2010/msg00168.html"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><
	SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">http://ops
	.ietf.org/lists/radiusext/2010/msg00168.html</FONT></U></SPAN><SPAN LANG="
	en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPA
	N LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 F
	ACE="Tahoma">Presentations:&nbsp\;</FONT></SPAN><SPAN LANG="en-us"> </SPAN
	><A HREF="http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><SPAN LANG="e
	n-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><U><FONT COLOR="
	#0000FF" SIZE=2 FACE="Tahoma">http://www.drizzle.com/~aboba/RADEXT/Feb-Int
	erim/</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></
	SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LT
	R><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">WebEx parameters:&nbsp\;</
	FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.org/lists/
	radiusext/2010/msg00169.html"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"
	></SPAN><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">h
	ttp://ops.ietf.org/lists/radiusext/2010/msg00169.html</FONT></U></SPAN><SP
	AN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></
	SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPA
	N></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTLASTSEQUENCE:2
X-MS-OLK-APPTSEQTIME:20100207T065058Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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

From owner-radiusext@ops.ietf.org  Wed Feb 10 21:41:03 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 069723A7162 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 21:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.701
X-Spam-Level: *
X-Spam-Status: No, score=1.701 tagged_above=-999 required=5 tests=[AWL=-3.056, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_SORBS_WEB=0.619, RDNS_NONE=0.1, TVD_SPACE_RATIO=2.219]
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 Z6zz-dFuTFo6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 10 Feb 2010 21:41:02 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7AE4E3A6DBE for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 10 Feb 2010 21:41:01 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NfRle-000C08-P9 for radiusext-data0@psg.com; Thu, 11 Feb 2010 05:39:10 +0000
Received: from [65.55.116.45] (helo=blu0-omc1-s34.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NfRlc-000Bzt-2s for radiusext@ops.ietf.org; Thu, 11 Feb 2010 05:39:08 +0000
Received: from BLU137-DS1 ([65.55.116.9]) by blu0-omc1-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 21:39:07 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS18C7E0625FD2D1AF0530E934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
CC: "'Klaas Wierenga'" <klaas@wierenga.net>
Subject: RADEXT Virtual Interim
Date: Wed, 10 Feb 2010 21:39:47 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNADr90Lg
Content-Language: en-us
X-OriginalArrivalTime: 11 Feb 2010 05:39:07.0562 (UTC) FILETIME=[877550A0:01CAAADC]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN='radiusext@ops.ietf.org';RSVP=TRUE:mailto:radiusext@ops.ietf.or
	g
ATTENDEE;CN="'Klaas Wierenga'";ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:klaas@
	wierenga.net
CLASS:PUBLIC
CREATED:20100211T053946Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: WebEx\n\nNote: The GMT offset above 
	does not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\
	n\nRADEXT Virtual Interim Meeting\nTuesday\, February 23\, 2010\n10 AM - 1
	2:30 PM Pacific Time\n\nJabber room (please join):  radext at jabber.ietf.
	org\nAgenda: http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/agenda.txt\n
	Presentations:  http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/\nWebEx p
	arameters:  http://ops.ietf.org/lists/radiusext/2010/msg00169.html\n\n
DTEND:20100223T203000Z
DTSTAMP:20100211T053946Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100211T053946Z
LOCATION:WebEx
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:4
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: WebEx</FONT></SPAN></P>\n\n<P DIR=LTR><SP
	AN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset above does not r
	eflect daylight saving time adjustments.</FONT></SPAN></P>\n\n<P DIR=LTR><
	SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*</FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN
	 LANG="en-us"><FONT COLOR="#000000" SIZE=2 FACE="Verdana">RADEXT Virtual I
	nterim Meeting<BR>\nTuesday\, February 23\, 2010<BR>\n10 AM - 12:30 PM Pac
	ific Time</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN 
	LANG="en-us"></SPAN><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Jabber r
	oom (please join):&nbsp\; radext at jabber.ietf.org</FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Agenda:</FONT></SP
	AN><SPAN LANG="en-us"> </SPAN><A HREF="http://www.drizzle.com/~aboba/RADEX
	T/Feb-Interim/agenda.txt"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></S
	PAN><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">http:
	//www.drizzle.com/~aboba/RADEXT/Feb-Interim/agenda.txt</FONT></U></SPAN><S
	PAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><
	/SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FON
	T SIZE=2 FACE="Tahoma">Presentations:&nbsp\;</FONT></SPAN><SPAN LANG="en-u
	s"> </SPAN><A HREF="http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><SP
	AN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><U><FO
	NT COLOR="#0000FF" SIZE=2 FACE="Tahoma">http://www.drizzle.com/~aboba/RADE
	XT/Feb-Interim/</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG=
	"en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN></P>\n\
	n<P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">WebEx parameters
	:&nbsp\;</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.
	org/lists/radiusext/2010/msg00169.html"><SPAN LANG="en-us"></SPAN><SPAN LA
	NG="en-us"></SPAN><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE=
	"Tahoma">http://ops.ietf.org/lists/radiusext/2010/msg00169.html</FONT></U>
	</SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG=
	"en-us"></SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"></SPAN></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTLASTSEQUENCE:3
X-MS-OLK-APPTSEQTIME:20100211T045741Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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

From owner-radiusext@ops.ietf.org  Thu Feb 11 00:38:00 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52D193A7243 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 11 Feb 2010 00:38:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.484
X-Spam-Level: 
X-Spam-Status: No, score=-1.484 tagged_above=-999 required=5 tests=[AWL=-0.990, 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 DGOdA247Rjx2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 11 Feb 2010 00:37:55 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id CA6223A68D6 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 11 Feb 2010 00:37:54 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NfUWD-00087d-83 for radiusext-data0@psg.com; Thu, 11 Feb 2010 08:35:25 +0000
Received: from [198.152.71.100] (helo=de307622-de-outbound.net.avaya.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <dromasca@avaya.com>) id 1NfUW8-00086t-LI for radiusext@ops.ietf.org; Thu, 11 Feb 2010 08:35:21 +0000
X-IronPort-AV: E=Sophos;i="4.49,450,1262581200";  d="scan'208,217";a="176020361"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Feb 2010 03:35:16 -0500
X-IronPort-AV: E=Sophos;i="4.49,450,1262581200";  d="scan'208,217";a="444596195"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Feb 2010 03:35:14 -0500
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_01CAAAF5.011C3211"
Subject: RE: RADEXT Virtual Interim Agenda, Take Two
Date: Thu, 11 Feb 2010 09:34:17 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0E357@307622ANEX5.global.avaya.com>
In-Reply-To: <BLU137-DS570599EE0D8C6B358FD13934F0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RADEXT Virtual Interim Agenda, Take Two
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAAFhM7wA==
References: <BLU137-DS570599EE0D8C6B358FD13934F0@phx.gbl>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <radiusext@ops.ietf.org>
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_01CAAAF5.011C3211
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> 11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines
<http://tools.ietf.org/html/draft-ietf-radext-design-guidelines>=20
=20
I hope that the WG will use the time until the virtual meeting and the
meeting itself to make progress and clean up the remaining open issues.
I suggested a few weeks ago that Avi and Alan work together on the text
that describes what this document exactly covers and what is being left
for future work. I do not know if this happened, but we have new text
proposals. I suggest that Avi, Woj, and the other WG participants who
made comments during the 'Last Look' period address the changes in the
document suggested by Alan and send back feedback and comments to the
list or their agreement with the proposed changes even before the
virtual meeting. All participants in the WG are  of course welcome and
invited to express their opinions with comments or 'I am OK with the
document' messages.
=20
Thanks and Regards,
=20
Dan
=20


________________________________

	From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
	Sent: Wednesday, February 10, 2010 11:54 PM
	To: radiusext@ops.ietf.org
	Subject: RADEXT Virtual Interim Agenda, Take Two
=09
=09

	RADEXT Virtual Interim Meeting
	Tuesday, February 23, 2010
	10 AM - 12:30 PM Pacific Time
=09
	Agenda
=09
	10 AM - 10:15 AM PT: Preliminaries=20
=09
	     Conference issues/debugging
	     Attendance
	     Note takers
	     Agenda bash
=09
	RADSEC (60 minutes)
=09
	10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
	http://tools.ietf.org/html/draft-ietf-radext-status-server

	10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15
minutes)
	http://tools.ietf.org/html/draft-ietf-radext-tcp-transport
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>=20

	10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
	http://tools.ietf.org/html/draft-ietf-radext-radsec

=09
	11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter
(15 minutes)
	http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

	Design Guidelines (60 minutes)
=09
	11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60
minutes)
	http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

=09
	Wrap-up (15 minutes)
=09
	12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG
Chairs & ADs (15 minutes)


------_=_NextPart_001_01CAAAF5.011C3211
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: =
auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal
}
SPAN.EmailStyle19 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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 vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D187272508-11022010><FONT color=3D#0000ff =
size=3D2><FONT=20
face=3DVerdana color=3D#000000>&gt; 11:15 AM &#8211; 12:15 PM PT Design =
Guidelines, Alan=20
DeKok (60 minutes) </FONT><A=20
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines"><=
FONT=20
face=3DVerdana>http://tools.ietf.org/html/draft-ietf-radext-design-guidel=
ines</FONT></A></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT color=3D#0000ff=20
size=3D2><o:p></o:p></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2>I hope=20
that the WG will use the time until the virtual meeting and the meeting =
itself=20
to make progress and clean up the remaining open issues. I suggested a =
few weeks=20
ago that Avi and Alan work together on the text that describes what this =

document exactly covers and what is being left for future work. I do not =
know if=20
this happened, but we have new text proposals. I suggest that <SPAN =
lang=3DEN>Avi,=20
Woj, and the other WG participants who made comments during =
the&nbsp;'Last Look'=20
period address the changes in the document suggested by Alan and send =
back=20
feedback&nbsp;and comments to the list or their <FONT face=3D"Times New =
Roman"=20
size=3D3>agreement with the proposed changes</FONT>&nbsp;even =
before&nbsp;the=20
virtual meeting.&nbsp;All participants in the WG are&nbsp; of course =
welcome and=20
invited to express their opinions with comments or 'I am OK with the =
document'=20
messages.</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN>Thanks and Regards,</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN>Dan</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN></SPAN></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=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> owner-radiusext@ops.ietf.org =

  [mailto:owner-radiusext@ops.ietf.org] <B>On Behalf Of </B>Bernard=20
  Aboba<BR><B>Sent:</B> Wednesday, February 10, 2010 11:54 =
PM<BR><B>To:</B>=20
  radiusext@ops.ietf.org<BR><B>Subject:</B> RADEXT Virtual Interim =
Agenda, Take=20
  Two<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">RADEXT=20
  Virtual Interim Meeting<BR>Tuesday, February 23, 2010<BR>10 AM - 12:30 =
PM=20
  Pacific Time<BR><BR>Agenda<BR><BR>10 AM - 10:15 AM PT: Preliminaries=20
  <BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; Conference=20
  issues/debugging<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  Attendance<BR>&nbsp;&nbsp;&nbsp;&nbsp; Note =
takers<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  Agenda bash<BR><BR>RADSEC (60 minutes)<BR><BR>10:15 AM &#8211; 10:30 =
AM PT&nbsp;=20
  Status-Server, Alan DeKok (15 minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</A></SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:30=20
  AM PT &#8211; 10:45 AM PT RADIUS over TCP, Alan DeKok (15 =
minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><SPAN=
=20
  style=3D"COLOR: =
black">http://tools.ietf.org/html/draft-ietf-radext-tcp-transport</SPAN><=
/A></SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:45=20
  AM - 11:00 AM PT&nbsp; RADSEC, Stefan Winter (15 minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</A><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>11:00=20
  AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</A><o:p></o=
:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Design=20
  Guidelines (60 minutes)<BR><BR>11:15 AM &#8211; 12:15 PM PT Design =
Guidelines, Alan=20
  DeKok (60 minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</A><o:p></o=
:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>Wrap-up=20
  (15 minutes)<BR><BR>12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; =
Discussion and Next=20
  Steps:&nbsp; WG Chairs &amp; ADs (15=20
minutes)<o:p></o:p></SPAN></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAAAF5.011C3211--

--
to unsubscribe send a message to 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 Feb 11 05:06:56 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D76933A76DB for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 11 Feb 2010 05:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.888
X-Spam-Level: 
X-Spam-Status: No, score=-0.888 tagged_above=-999 required=5 tests=[AWL=-0.394, 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 ZRNDhVb3RbVX for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 11 Feb 2010 05:06:52 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0155228C1C8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 11 Feb 2010 05:06:52 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NfYgR-000B4K-Fp for radiusext-data0@psg.com; Thu, 11 Feb 2010 13:02:15 +0000
Received: from [65.55.116.97] (helo=blu0-omc3-s22.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NfYgN-000B3S-UH for radiusext@ops.ietf.org; Thu, 11 Feb 2010 13:02:12 +0000
Received: from BLU137-DS1 ([65.55.116.72]) by blu0-omc3-s22.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Feb 2010 05:02:11 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS1D3D18B35F5FC5597400A934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <radiusext@ops.ietf.org>
References: <BLU137-DS570599EE0D8C6B358FD13934F0@phx.gbl> <EDC652A26FB23C4EB6384A4584434A0401F0E357@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F0E357@307622ANEX5.global.avaya.com>
Subject: RE: RADEXT Virtual Interim Agenda, Take Two
Date: Thu, 11 Feb 2010 05:02:51 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AD_01CAAAD7.76E5E970"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAAFhM7wAAJjiAQ
Content-Language: en-us
X-OriginalArrivalTime: 11 Feb 2010 13:02:11.0347 (UTC) FILETIME=[6CA0FE30:01CAAB1A]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_01AD_01CAAAD7.76E5E970
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

For those interested in reviewing the proposed changes to Design Guidelines,
I believe that the strawman is available here:

http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt

 

Changes between -10 and -11 are available here:

http://git.freeradius.org/ietf/10-11-diff.html

 

 

 

From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, February 11, 2010 12:34 AM
To: Bernard Aboba; radiusext@ops.ietf.org
Subject: RE: RADEXT Virtual Interim Agenda, Take Two

 

> 11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
<http://tools.ietf.org/html/draft-ietf-radext-design-guidelines>
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

 

I hope that the WG will use the time until the virtual meeting and the
meeting itself to make progress and clean up the remaining open issues. I
suggested a few weeks ago that Avi and Alan work together on the text that
describes what this document exactly covers and what is being left for
future work. I do not know if this happened, but we have new text proposals.
I suggest that Avi, Woj, and the other WG participants who made comments
during the 'Last Look' period address the changes in the document suggested
by Alan and send back feedback and comments to the list or their agreement
with the proposed changes even before the virtual meeting. All participants
in the WG are  of course welcome and invited to express their opinions with
comments or 'I am OK with the document' messages.

 

Thanks and Regards,

 

Dan

 

 

  _____  

From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Bernard Aboba
Sent: Wednesday, February 10, 2010 11:54 PM
To: radiusext@ops.ietf.org
Subject: RADEXT Virtual Interim Agenda, Take Two

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (60 minutes)

11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines


Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


------=_NextPart_000_01AD_01CAAAD7.76E5E970
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

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

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

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For those interested in reviewing the proposed changes to =
Design
Guidelines, I believe that the strawman is available =
here:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href=3D"http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt">h=
ttp://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt</a><o:p></o=
:p></span></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Changes between -10 and -11 are available =
here:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a =
href=3D"http://git.freeradius.org/ietf/10-11-diff.html">http://git.freera=
dius.org/ietf/10-11-diff.html</a><o:p></o:p></span></p>

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

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] <b>On =
Behalf
Of </b>Romascanu, Dan (Dan)<br>
<b>Sent:</b> Thursday, February 11, 2010 12:34 AM<br>
<b>To:</b> Bernard Aboba; radiusext@ops.ietf.org<br>
<b>Subject:</b> RE: RADEXT Virtual Interim Agenda, Take =
Two<o:p></o:p></span></p>

</div>

</div>

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

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>&gt; 11:15 AM &#8211; 12:15 PM PT Design Guidelines, Alan =
DeKok (60
minutes) </span><span style=3D'font-size:10.0pt;color:blue'><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines"><=
span
style=3D'font-family:"Verdana","sans-serif"'>http://tools.ietf.org/html/d=
raft-ietf-radext-design-guidelines</span></a></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<span =
style=3D'font-size:10.0pt;color:blue'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I hope that the WG will use the time until the virtual =
meeting and
the meeting itself to make progress and clean up the remaining open =
issues. I
suggested a few weeks ago that Avi and Alan work together on the text =
that
describes what this document exactly covers and what is being left for =
future
work. I do not know if this happened, but we have new text proposals. I =
suggest
that </span><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Avi, Woj, and the other WG participants who made comments =
during
the&nbsp;'Last Look' period address the changes in the document =
suggested by
Alan and send back feedback&nbsp;and comments to the list or their =
</span><span
lang=3DEN style=3D'color:blue'>agreement with the proposed =
changes</span><span
lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>&n=
bsp;even
before&nbsp;the virtual meeting.&nbsp;All participants in the WG =
are&nbsp; of
course welcome and invited to express their opinions with comments or 'I =
am OK
with the document' messages.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Thanks and Regards,</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Dan</span><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 blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] <b>On Behalf Of </b>Bernard =
Aboba<br>
<b>Sent:</b> Wednesday, February 10, 2010 11:54 PM<br>
<b>To:</b> radiusext@ops.ietf.org<br>
<b>Subject:</b> RADEXT Virtual Interim Agenda, Take =
Two</span><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time<br>
<br>
Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines (60 =
minutes)<br>
<br>
11:15 AM &#8211; 12:15 PM PT Design Guidelines, Alan DeKok (60 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_01AD_01CAAAD7.76E5E970--

--
to unsubscribe send a message to 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 Feb 13 18:17:40 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8121328C0F2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 13 Feb 2010 18:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.892
X-Spam-Level: 
X-Spam-Status: No, score=-0.892 tagged_above=-999 required=5 tests=[AWL=-0.398, 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 pDocpVSIoGQ4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sat, 13 Feb 2010 18:17:34 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id ADE533A761C for <radext-archive-IeZ9sae2@lists.ietf.org>; Sat, 13 Feb 2010 18:17:33 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NgTyh-000KZl-IW for radiusext-data0@psg.com; Sun, 14 Feb 2010 02:12:55 +0000
Received: from [65.55.116.33] (helo=blu0-omc1-s22.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NgTyd-000KZO-ME for radiusext@ops.ietf.org; Sun, 14 Feb 2010 02:12:51 +0000
Received: from BLU137-DS2 ([65.55.116.8]) by blu0-omc1-s22.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 13 Feb 2010 18:12:51 -0800
X-Originating-IP: [64.134.221.168]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS2801F368B1134D7EA2B3E934B0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: REQUIRED READING: RADEXT Virtual Interim Design Guidelines Discussion
Date: Sat, 13 Feb 2010 18:14:46 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CAACD8.6CD963A0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqtGmp+Mp9kWH1mT7SZV3/KM1CU2gAACIrQ
Content-Language: en-us
X-OriginalArrivalTime: 14 Feb 2010 02:12:51.0087 (UTC) FILETIME=[35BE59F0:01CAAD1B]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_000A_01CAACD8.6CD963A0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dan Romascanu said:

 

"I hope that the WG will use the time until the virtual meeting and the
meeting itself to make progress and clean up the remaining open issues. I
suggested a few weeks ago that Avi and Alan work together on the text that
describes what this document exactly covers and what is being left for
future work. I do not know if this happened, but we have new text proposals.
I suggest that Avi, Woj, and the other WG participants who made comments
during the 'Last Look' period address the changes in the document suggested
by Alan and send back feedback and comments to the list or their agreement
with the proposed changes even before the virtual meeting. All participants
in the WG are  of course welcome and invited to express their opinions with
comments or 'I am OK with the document' messages."

 
[BA]  I have collected Avi Lior's review of the -10 text (and suggested
changes) within Issue 327:
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327>
Applicability .  Joe Salowey's review is 
provided in Issue 325:
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325> Review .
As noted in a previous message summarizing the results of the "Last Look" (
<http://ops.ietf.org/lists/radiusext/2010/msg00150.html>
http://ops.ietf.org/lists/radiusext/2010/msg00150.html) there appears to be
WG consensus to make changes to the document to address the concerns that
have been raised.
 
In order for the interim meeting to go smoothly on February 23, 2010, it
would be ideal to have proposed text changes to resolve each issue, as Dan
suggests.  To further this, it would be ideal for Avi and Joe to examine the
modified text and confirm (or deny) that their issues have been addressed:

http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt

 Changes between -10 and -11 are available here:

http://git.freeradius.org/ietf/10-11-diff.html

 
Note that if we do not have proposed text changes by February 20, 2010 then
the chairs will go over the existing issues and propose changes on the
mailing list which we will discuss at the Interim.  
 
 
 
 

 


------=_NextPart_000_000A_01CAACD8.6CD963A0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal>Dan Romascanu said:<o:p></o:p></p>

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

<p class=3DMsoNormal>&#8220;<span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I hope that the WG will use the time until the virtual =
meeting and
the meeting itself to make progress and clean up the remaining open =
issues. I
suggested a few weeks ago that Avi and Alan work together on the text =
that
describes what this document exactly covers and what is being left for =
future
work. I do not know if this happened, but we have new text proposals. I =
suggest
that </span><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Avi, Woj, and the other WG participants who made comments =
during
the&nbsp;'Last Look' period address the changes in the document =
suggested by
Alan and send back feedback&nbsp;and comments to the list or their =
</span><span
lang=3DEN style=3D'color:blue'>agreement with the proposed =
changes</span><span
lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>&n=
bsp;even
before&nbsp;the virtual meeting.&nbsp;All participants in the WG =
are&nbsp; of
course welcome and invited to express their opinions with comments or 'I =
am OK
with the document' messages.</span>&#8221;<o:p></o:p></p>

<pre><o:p>&nbsp;</o:p></pre><pre><span style=3D'color:black'>[BA] =
&nbsp;I have collected Avi Lior&#8217;s review of the -10 text (and =
suggested changes) within Issue 327: <a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
327"><span
style=3D'color:black'>Applicability</span></a> .&nbsp; Joe =
Salowey&#8217;s review is <o:p></o:p></span></pre><pre><span
style=3D'color:black'>provided in Issue 325: <a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
325"><span
style=3D'color:black'>Review</span></a> .&nbsp; As noted in a previous =
message summarizing the results of the &#8220;Last Look&#8221; (<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00150.html"><span
style=3D'color:black'>http://ops.ietf.org/lists/radiusext/2010/msg00150.h=
tml</span></a>) there appears to be WG consensus to make changes to the =
document to address the concerns that have been =
raised.<o:p></o:p></span></pre><pre><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'color:black'>In order for the interim meeting to go smoothly on =
February 23, 2010, it would be ideal to have proposed text changes to =
resolve each issue, as Dan suggests.&nbsp; To further this, it would be =
ideal for Avi and Joe to examine the modified text and confirm (or deny) =
that their issues have been addressed:<o:p></o:p></span></pre>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:#1F497D'><a
href=3D"http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt">h=
ttp://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt</a></span><=
span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:#1F497D'>&nbsp;Changes between -10 and -11 are available =
here:</span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:#1F497D'><a =
href=3D"http://git.freeradius.org/ietf/10-11-diff.html">http://git.freera=
dius.org/ietf/10-11-diff.html</a></span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<pre><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'color:black'>Note that if we do not have proposed text changes =
by February 20, 2010 then the chairs will go over the existing issues =
and propose changes on the mailing list which we will discuss at the =
Interim. =
&nbsp;<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><pre><o:p>&nbsp=
;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre>

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

</div>

</body>

</html>

------=_NextPart_000_000A_01CAACD8.6CD963A0--

--
to unsubscribe send a message to 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 Feb 14 13:38:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4E4028C114 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 14 Feb 2010 13:38:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.888
X-Spam-Level: 
X-Spam-Status: No, score=-0.888 tagged_above=-999 required=5 tests=[AWL=-0.394, 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 fuvceE4AYDIL for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 14 Feb 2010 13:38:30 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5256628C0F8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 14 Feb 2010 13:38:29 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Ngm3h-000GyQ-QD for radiusext-data0@psg.com; Sun, 14 Feb 2010 21:31:17 +0000
Received: from [65.55.116.21] (helo=blu0-omc1-s10.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Ngm3a-000GxZ-Ug for radiusext@ops.ietf.org; Sun, 14 Feb 2010 21:31:11 +0000
Received: from BLU137-W37 ([65.55.116.7]) by blu0-omc1-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 14 Feb 2010 13:31:10 -0800
Message-ID: <BLU137-W377F2298AEEB878B736E09934B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Proposal for resolution of Issue 327:  Applicability
Date: Sun, 14 Feb 2010 13:31:10 -0800
Importance: Normal
In-Reply-To: <BLU137-DS3D85750A8B968C9620D0F934B0@phx.gbl>
References: <BLU137-DS3D85750A8B968C9620D0F934B0@phx.gbl>
MIME-Version: 1.0
X-OriginalArrivalTime: 14 Feb 2010 21:31:10.0398 (UTC) FILETIME=[068F9DE0:01CAADBD]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The concerns expressed in Issue 327 appear to apply to Sections 1=2C 1.3=2C=
 3.1.2=2C 3.1.3 and 3.1.4.=20

Here is a proposed resolution.  Comments welcome.=20
















Section 1

=20

   This document provides guidelines for the design of
RADIUS attributes

   both within the IETF as well as within other SDOs.  By
articulating

   RADIUS design guidelines=2C it is hoped that this document
will

   encourage the development and publication of high quality
RADIUS

   attribute specifications.

=20

   However=2C the advice in this document will not be helpful
unless it is

   put to use.  As with "Guidelines for Authors and
Reviewers of MIB

   Documents" [RFC4181]=2C it is expected that this document
will be used

   by authors to check their document against the guidelines
prior to

   requesting review (such as an "Expert Review"
described in

   [RFC3575]).  Similarly=2C it is expected that this document
will used

   by reviewers (such as WG participants or the AAA Doctors
[DOCTORS])=2C

   resulting in an improvement in the consistency of
reviews.

=20

   In order to meet these objectives=2C this document needs to
cover not

   only the science of attribute design=2C but also the art.=20
Therefore=2C

   in addition to covering the most frequently encountered
issues=2C this

   document attempts to provide some of the considerations
motivating

   the guidelines.

=20

   In order to characterize current attribute usage=2C both
the basic and

   complex data types defined in the existing RADIUS RFCs
are reviewed.

=20

[BA] Proposed
change is to replace Section 1 with the following:


=20

   "This document provides guidelines for the design of
RADIUS attributes

   used to encode service-provisioning or authentication
data=2C=20

   based on the data model and attribute formats defined in
RFC 2865 and

   subsequent RADIUS RFCs.   In order to characterize
current attribute=20

   usage=2C both the basic and complex data types defined in
the existing=20

   RADIUS RFCs are reviewed. Since the RADEXT WG is
currently considering

   extensions to the RADIUS data model and attribute
formats=2C=20

   future documents may extend the data model and guidelines
provided here.

=20

   In order to meet these objectives=2C this document needs to
cover not

   only the science of attribute design=2C but also the art.=20
Therefore=2C

   in addition to covering the most frequently encountered
issues=2C this

   document attempts to provide some of the considerations
motivating

   the guidelines.

=20

   RADIUS protocol changes=2C or specification of attributes=20

   (such as Service-Type) that can be used to=2C in effect=2C
provide=20

   new RADIUS commands require greater expertise and deeper
review=2C=20

   as do changes to the RADIUS operational model as
discussed in Section=20

   3.3.  As a result=2C such changes are outside the scope of
this

   document and MUST NOT be undertaken outside the IETF.=20
Registration policies

   for RADIUS parameters are discussed in [RFC3575] Section
2.1."=20

=20

1.3.  Applicability

=20

   As RADIUS has become more widely accepted as a management
protocol=2C

   its usage has become more prevalent=2C both within the IETF
as well as

   within other SDOs.  Given the expanded utilization of
RADIUS=2C it has

   become apparent that requiring SDOs to accomplish all
their RADIUS

   work within the IETF is inherently inefficient and
unscalable.  By

   articulating guidelines for RADIUS attribute design=2C this
document

   enables SDOs out of the IETF to design their own RADIUS
attributes

   within the Vendor-Specific Attribute (VSA) space.

=20

   It is RECOMMENDED that SDOs follow the guidelines
articulated in this

   document.  Doing so will ensure the widest possible
applicability and

   interoperability of the specifications=2C while requiring
minimal

   changes to existing systems.  Specifications that do not
follow the

   guidelines articulated herein are NOT RECOMMENDED.=20
However=2C we

   recognize that there are some situations where SDOs or
vendors

   require the creation of specifications not following these

   guidelines.  We do not forbid these specifications=2C but
it is

   RECOMMENDED that they are created only if they have a
limited scope

   of applicability=2C and all attributes defined in those
specifications

   are VSAs=2C as discussed Appendix A.5=2C below.

=20

   It is RECOMMENDED that SDOs and vendors seek review of
RADIUS

   attribute specifications from the IETF.  However=2C when
specifications

   are SDO specific=2C re-use existing data types=2C and follow
these

   guidelines=2C they do not require IETF review.

=20

   In order to enable IETF review of such specifications=2C
the authors

   recommend that:

=20

      * SDOs make their RADIUS attribute specifications
publicly

      available=3B

=20

      * SDOs request review of RADIUS attribute
specifications by

      sending email to the AAA Doctors [DOCTORS] or
equivalent mailing

      list=3B

=20

      * IETF and SDO RADIUS attribute specifications are
reviewed

      according to the guidelines proposed in this document=3B

=20

      * Reviews of specifications are posted to the RADEXT
WG mailing

      list=2C the AAA Doctors mailing list [DOCTORS] or
another IETF

      mailing list suggested by the Operations &
Management Area

      Directors of the IETF.

=20

   These reviews can assist with creation of specifications
that meet

   the SDO requirements=2C and which are also compatible with
the

   traditional data model and uses of RADIUS.  While these
reviews

   require access to public specifications=2C the review
process does not

   require publication of an IETF RFC.

=20

   The advice in this document applies to attributes used to
encode

   service-provisioning or authentication data.  RADIUS
protocol

   changes=2C or specification of attributes (such as
Service-Type) that

   can be used to=2C in effect=2C provide new RADIUS commands
require

   greater expertise and deeper review=2C as do changes to the
RADIUS

   operational model as discussed below in Section 3.3.=20
Such changes

   MUST NOT be undertaken outside the IETF and when handled
within the

   IETF require "IETF Consensus" for adoption=2C as
noted in [RFC3575]

   Section 2.1.



=20

[BA] Proposed change is to replace Section 1.3 with the following:=20

=20

   "   As RADIUS has become more widely accepted as a
management protocol=2C

   its usage has become more prevalent=2C by vendors as well
as the IETF and

  other SDOs.  By articulating RADIUS design guidelines=2C it
is hoped that

   this document will encourage the development and
publication of=20

   high quality RADIUS attribute specifications.  As with
"Guidelines=20

   for Authors and Reviewers of MIB Documents"
[RFC4181]=2C it is=20

   expected that this document will be used by authors to
check their=20

   document against the guidelines prior to requesting
review=20

   (such as an "Expert Review" described in

   [RFC3575]).  Similarly=2C it is expected that this document
will used

   by reviewers (such as WG participants or the AAA Doctors
[DOCTORS])=2C

   resulting in an improvement in the consistency of
reviews.

=20

   The guidelines articulated in this document enable the
design

   of attributes with the widest possible interoperability=2C

   while requiring minimal changes to existing systems.

   As a result=2C they are suitable for application to
attributes=20

   designed for general usage.  It is RECOMMENDED=20

   that these guidelines be applied to review of documents=20

   requesting allocations within the IETF standard attribute


   space defined in [RFC2865].=20

=20

   These guidelines may also prove useful in the design of=20

   attributes within the Vendor-Specific Attribute (VSA)

   space.  As noted in RFC 2865 Section 5.26=2C RADIUS VSAs=20

   were created "to allow vendors to support their own
extended=20

   Attributes not suitable for general usage." =20

   Rather than requesting allocation of standard attributes

   for those uses=2C [RFC2865] Section 6.2 notes that
utilization

   of VSAs "should be encouraged instead of allocation
of global=20

   attribute types=2C for functions specific only to one
vendor's=20

   implementation of RADIUS=2C where no interoperability is
deemed useful."=20

=20

   However=2C experience has shown that attributes not
originally=20

   designed for general usage can subsequently garner
wide-spread=20

   deployment.  An example is the vendor-specific attributes


   defined in [RFC2548]=2C which have been widely implemented=20

   within IEEE 802.11 Access Points.=20

=20

   As a result=2C while SDOs and vendors MAY choose to create=20

   specifications not following these guidelines for use in

   scenarios within a limited scope of applicability=2C

   where general usage is possible=2C  adhering to the=20

   design guidelines is RECOMMENDED.  Discussion of

   vendor allocations is provided in Section 3.1.2=3B=20

   discussion of SDO allocations is provided in Section

   3.1.3.   SDOs and vendors desiring review of their=20

   specifications by the IETF are encouraged to follow=20

   the advice presented in Section 3.1.4."=20

=20

3.1.2.  Vendor Allocations

=20

   Vendor RADIUS Attribute specifications SHOULD allocate
attributes

   from the vendor space=2C rather than requesting an
allocation from the

   RADIUS standard attribute space.

=20

   As discussed in [RFC2865] Section 5.26=2C the vendor space
is intended

   for vendors to support their own Attributes not suitable
for general

   use.  However=2C it is RECOMMENDED that vendors follow the
guidelines

   outlined here=2C which are intended to enable maximum
interoperability

   with minimal changes to existing systems.

=20

   Following these guidelines means that RADIUS servers can
be updated

   to support the vendor's equipment by editing a RADIUS
dictionary.  If

   these guidelines are not followed=2C then the vendor's
equipment can

   only be supported via code changes in RADIUS server
implementations.

   Such code changes add complexity and delay to
implementations.

=20

[BA] Proposed change is to replace Section 3.1.2 with the following:


=20

"  As noted in [RFC3575] Section 2.1=2C vendors are
encouraged

   to utilize VSAs to define functions "specific only
to one vendor's

   implementation of RADIUS=2C where no interoperability is
deemed useful.

   For functions specific only to one vendor's
implementation of RADIUS=2C

   the use of that should be encouraged instead of the
allocation of

   global attribute types."

=20

   Nevertheless=2C following the guidelines outlined within
this document

   has several advantages=2C including maximum
interoperability with

   minimal changes to existing systems.  Following these
guidelines=20

   means that RADIUS servers can be updated to support the
vendor's=20

   equipment by editing a RADIUS dictionary.  If these
guidelines are=20

   not followed=2C then the vendor's equipment can only be
supported=20

   via code changes in RADIUS server implementations.

   Such code changes add complexity and delay to
implementations."

=20

3.1.3.  SDO Allocations

=20

   SDO RADIUS Attribute specifications SHOULD allocate
attributes from

   the vendor space=2C rather than requesting an allocation
from the

   RADIUS standard attribute space=2C for attributes matching
any of the

   following criteria:

=20

      * attributes relying on data types not defined within
RADIUS

=20

      * attributes intended primarily for use within an SDO

=20

      * attributes intended primarily for use within a group
of SDOs.

=20

   Any new RADIUS attributes or values intended for
interoperable use

   across a broad spectrum of the Internet Community SHOULD
follow the

   normal IETF process=2C and SHOULD result in allocations
from the RADIUS

   standard space.

=20

   The recommendation for SDOs to allocate attributes from a
vendor

   space rather than via the IETF process is a recognition
that SDOs may

   desire to assert change control over their own RADIUS
specifications.

   This change control can be obtained by requesting a PEC
from the

   Internet Assigned Number Authority (IANA)=2C for use as a
Vendor-Id

   within a Vendor-Specific attribute.  Further allocation
of attributes

   inside of the VSA space defined by that Vendor-Id is
subject solely

   to the discretion of the SDO.  Similarly=2C the use of data
types

   (complex or not) within that VSA space is solely under
the discretion

   of the SDO.  It is RECOMMENDED that SDOs follow the
guidelines

   outlined here=2C which are intended to enable maximum
interoperability

   with minimal changes to existing systems.

=20

   It should be understood that SDOs do not have to rehost
VSAs into the

   standards space solely for the purpose of obtaining IETF
review.

   Rehosting puts pressure on the standards space=2C and may
be harmful to

   interoperability=2C since it can create two ways to
provision the same

   service.  Rehosting may also require changes to the
RADIUS data model

   which will affect implementations that do not intend to
support the

   SDO specifications.

=20

[BA] Proposed change is to replace Section 3.1.3 with the following:


=20

"  Given the expanded utilization of RADIUS=2C it has

   become apparent that requiring SDOs to accomplish all
their RADIUS

   work within the IETF is inherently inefficient and
unscalable. =20

=20

  SDO RADIUS Attribute specifications SHOULD allocate
attributes from

   the vendor space=2C rather than requesting an allocation
from the

   RADIUS standard attribute space=2C for attributes matching
any of the

   following criteria:

=20

      * attributes relying on data types not defined within
RADIUS

=20

      * attributes intended primarily for use within an SDO

=20

      * attributes intended primarily for use within a group
of SDOs.

=20

   Allocation of new RADIUS attributes or values intended
for interoperable use

   across a broad spectrum of the Internet Community SHOULD
follow the

   allocation process defined in [RFC3575].=20

=20

   The recommendation for SDOs to allocate attributes from
the vendor

   space rather than via the IETF process recognizes the
need for SDOs

   to assert change control over their own RADIUS
specifications.

   SDOs desiring to define their VSAs are encouraged to=20

   request allocation of a Private Enterprise Code (PEC)
from the

   Internet Assigned Number Authority (IANA)=2C for use as a
Vendor-Id. =20

   The SDO can then allocate attributes within the VSA space
defined=20

   by that Vendor-Id=2C at their sole discretion.  Similarly=2C
the use of=20

   data types (complex or otherwise) within that VSA space
is solely

   under the discretion of the SDO."

=20

3.1.4.  Publication of specifications

=20

   SDOs are encouraged to seek early review of SSA
specifications by the

   IETF.  This review may be initiated by sending mail to
the AAA

   Doctors list [DOCTORS]=2C with the understanding that this
review is a

   voluntary-based service offered on best-effort basis.=20
Since the IETF

   is not a membership organization=2C in order to enable the
RADIUS SSA

   specification to be reviewed=2C it is RECOMMENDED that it
be made

   publicly available=3B this also encourages interoperability.=20
Where the

   RADIUS SSA specification is embedded within a larger
document which

   cannot be made public=2C the RADIUS attribute and value
definitions

   SHOULD be published instead as an Informational RFC=2C as
with

   [RFC4679].  This process SHOULD be followed instead of
requesting

   IANA allocations from within the standard RADIUS
attribute space.

=20

   Similarly=2C vendors are encouraged to make their
specifications

   publicly available=2C for maximum interoperability.=20
However=2C it is not

   necessary for them to request publication of their VSA
specifications

   as Informational RFCs by the IETF.

=20

   All other specifications=2C including new authentication=2C

   authorization=2C and/or security mechanisms SHOULD be
allocated via the

   standard RADIUS space=2C as noted in [RFC3575] Section 2.1.

=20

[BA] Proposed change is to replace Section 3.1.4 with the following:

=20

"  SDOs or vendors desiring review of their RADIUS
specifications=20

   by the IETF are  encouraged to seek review as early as
possible=2C=20

   so as to avoid potential delays.  Since reviews are
handled by volunteers=2C=20

   responses are provided on a best-effort basis=2C with no
service

   level guarantees.   In order to provide reviewers with
access to the

   specification=2C  SDOs and vendors are encouraged to make
them publicly available.

   Where the RADIUS specification is embedded within a
larger document which

   cannot be made public=2C the RADIUS attribute and value
definitions

   can be made available on a public web site or can be
published as=20

   an Informational RFC=2C as with [RFC4679].=20

=20

   Review can be requested by sending email to the AAA
Doctors [DOCTORS]

   or equivalent mailing list.  The IETF Operations &
Management

   Area Directors will then arrange for the review to be

   completed and posted to the AAA Doctors mailing list

   [DOCTORS]=2C RADEXT WG mailing list=2C or other IETF mailing

   list. =20

=20

   The review process requires neither allocation of
attributes=20

   within the IETF standard attribute space nor publication
of an=20

   IETF RFC.  Requiring SDOs or vendors to rehost VSAs into
the IETF standards=20

   attribute space solely for the purpose of obtaining
review

   would put pressure on the standards space=2C and may be
harmful to

   interoperability=2C since it can create two ways to
provision the same

   service.  Rehosting may also require changes to the
RADIUS data model

   which will affect implementations that do not intend to
support the

   SDO or vendor specifications."

 		 	   		  =

--_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The concerns expressed in Issue 327 appear to apply to Sections 1=2C 1.3=2C=
 3.1.2=2C 3.1.3 and 3.1.4. <br><br>Here is a proposed resolution.&nbsp=3B C=
omments welcome. <br><br>






<style>
.ExternalClass p.ecxMsoNormal=2C .ExternalClass li.ecxMsoNormal=2C .Externa=
lClass div.ecxMsoNormal
{margin-bottom:.0001pt=3Bfont-size:11.0pt=3Bfont-family:'Calibri'=2C'sans-s=
erif'=3B}
.ExternalClass a:link=2C .ExternalClass span.ecxMsoHyperlink
{color:blue=3Btext-decoration:underline=3B}
.ExternalClass a:visited=2C .ExternalClass span.ecxMsoHyperlinkFollowed
{color:purple=3Btext-decoration:underline=3B}
.ExternalClass span.ecxEmailStyle17
{font-family:'Calibri'=2C'sans-serif'=3Bcolor:windowtext=3B}
.ExternalClass .ecxMsoChpDefault
{=3B}
@page Section1
{size:8.5in 11.0in=3B}
.ExternalClass div.ecxSection1
{page:Section1=3B}
</style>





<div class=3D"ecxSection1">

<p class=3D"ecxMsoNormal">Section 1</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B This document provides guideline=
s for the design of
RADIUS attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B both within the IETF as well as =
within other SDOs.&nbsp=3B By
articulating</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS design guidelines=2C it i=
s hoped that this document
will</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B encourage the development and pu=
blication of high quality
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B However=2C the advice in this do=
cument will not be helpful
unless it is</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B put to use.&nbsp=3B As with "Gui=
delines for Authors and
Reviewers of MIB</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Documents" [RFC4181]=2C it is ex=
pected that this document
will be used</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by authors to check their docume=
nt against the guidelines
prior to</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B requesting review (such as an "E=
xpert Review"
described in</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [RFC3575]).&nbsp=3B Similarly=2C=
 it is expected that this document
will used</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by reviewers (such as WG partici=
pants or the AAA Doctors
[DOCTORS])=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B resulting in an improvement in t=
he consistency of
reviews.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to meet these objective=
s=2C this document needs to
cover not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B only the science of attribute de=
sign=2C but also the art.&nbsp=3B
Therefore=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B in addition to covering the most=
 frequently encountered
issues=2C this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document attempts to provide som=
e of the considerations
motivating</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the guidelines.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to characterize current=
 attribute usage=2C both
the basic and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B complex data types defined in th=
e existing RADIUS RFCs
are reviewed.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed
change is to replace Section 1 with the following:<br></p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B "This document provides guidelin=
es for the design of
RADIUS attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B used to encode service-provision=
ing or authentication
data=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B based on the data model and attr=
ibute formats defined in
RFC 2865 and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B subsequent RADIUS RFCs.&nbsp=3B&=
nbsp=3B In order to characterize
current attribute </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B usage=2C both the basic and comp=
lex data types defined in
the existing </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS RFCs are reviewed. Since =
the RADEXT WG is
currently considering</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B extensions to the RADIUS data mo=
del and attribute
formats=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B future documents may extend the =
data model and guidelines
provided here.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to meet these objective=
s=2C this document needs to
cover not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B only the science of attribute de=
sign=2C but also the art.&nbsp=3B
Therefore=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B in addition to covering the most=
 frequently encountered
issues=2C this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document attempts to provide som=
e of the considerations
motivating</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the guidelines.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS protocol changes=2C or sp=
ecification of attributes </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B (such as Service-Type) that can =
be used to=2C in effect=2C
provide </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B new RADIUS commands require grea=
ter expertise and deeper
review=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B as do changes to the RADIUS oper=
ational model as
discussed in Section </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B 3.3.&nbsp=3B As a result=2C such=
 changes are outside the scope of
this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document and MUST NOT be underta=
ken outside the IETF.&nbsp=3B
Registration policies</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for RADIUS parameters are discus=
sed in [RFC3575] Section
2.1." </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">1.3.&nbsp=3B Applicability</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As RADIUS has become more widely=
 accepted as a management
protocol=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B its usage has become more preval=
ent=2C both within the IETF
as well as</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within other SDOs.&nbsp=3B Given=
 the expanded utilization of
RADIUS=2C it has</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B become apparent that requiring S=
DOs to accomplish all
their RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B work within the IETF is inherent=
ly inefficient and
unscalable.&nbsp=3B By</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B articulating guidelines for RADI=
US attribute design=2C this
document</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B enables SDOs out of the IETF to =
design their own RADIUS
attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within the Vendor-Specific Attri=
bute (VSA) space.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B It is RECOMMENDED that SDOs foll=
ow the guidelines
articulated in this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document.&nbsp=3B Doing so will =
ensure the widest possible
applicability and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B interoperability of the specific=
ations=2C while requiring
minimal</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B changes to existing systems.&nbs=
p=3B Specifications that do not
follow the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B guidelines articulated herein ar=
e NOT RECOMMENDED.&nbsp=3B
However=2C we</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B recognize that there are some si=
tuations where SDOs or
vendors</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B require the creation of specific=
ations not following these</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B guidelines.&nbsp=3B We do not fo=
rbid these specifications=2C but
it is</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RECOMMENDED that they are create=
d only if they have a
limited scope</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of applicability=2C and all attr=
ibutes defined in those
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B are VSAs=2C as discussed Appendi=
x A.5=2C below.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B It is RECOMMENDED that SDOs and =
vendors seek review of
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute specifications from th=
e IETF.&nbsp=3B However=2C when
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B are SDO specific=2C re-use exist=
ing data types=2C and follow
these</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B guidelines=2C they do not requir=
e IETF review.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to enable IETF review o=
f such specifications=2C
the authors</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B recommend that:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * SDOs m=
ake their RADIUS attribute specifications
publicly</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B availabl=
e=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * SDOs r=
equest review of RADIUS attribute
specifications by</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B sending =
email to the AAA Doctors [DOCTORS] or
equivalent mailing</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B list=3B<=
/p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * IETF a=
nd SDO RADIUS attribute specifications are
reviewed</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B accordin=
g to the guidelines proposed in this document=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * Review=
s of specifications are posted to the RADEXT
WG mailing</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B list=2C =
the AAA Doctors mailing list [DOCTORS] or
another IETF</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B mailing =
list suggested by the Operations &amp=3B
Management Area</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Director=
s of the IETF.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B These reviews can assist with cr=
eation of specifications
that meet</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the SDO requirements=2C and whic=
h are also compatible with
the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B traditional data model and uses =
of RADIUS.&nbsp=3B While these
reviews</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B require access to public specifi=
cations=2C the review
process does not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B require publication of an IETF R=
FC.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The advice in this document appl=
ies to attributes used to
encode</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B service-provisioning or authenti=
cation data.&nbsp=3B RADIUS
protocol</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B changes=2C or specification of a=
ttributes (such as
Service-Type) that</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B can be used to=2C in effect=2C p=
rovide new RADIUS commands
require</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B greater expertise and deeper rev=
iew=2C as do changes to the
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B operational model as discussed b=
elow in Section 3.3.&nbsp=3B
Such changes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B MUST NOT be undertaken outside t=
he IETF and when handled
within the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IETF require "IETF Consensus" fo=
r adoption=2C as
noted in [RFC3575]</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Section 2.1.</p>



<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 1.3 wi=
th the following: </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B "&nbsp=3B&nbsp=3B As RADIUS has =
become more widely accepted as a
management protocol=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B its usage has become more preval=
ent=2C by vendors as well
as the IETF and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B other SDOs. &nbsp=3BBy articulating RADI=
US design guidelines=2C it
is hoped that</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B this document will encourage the=
 development and
publication of </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B high quality RADIUS attribute sp=
ecifications.&nbsp=3B As with
"Guidelines </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for Authors and Reviewers of MIB=
 Documents"
[RFC4181]=2C it is </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B expected that this document will=
 be used by authors to
check their </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document against the guidelines =
prior to requesting
review </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B (such as an "Expert Review" desc=
ribed in</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [RFC3575]).&nbsp=3B Similarly=2C=
 it is expected that this document
will used</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by reviewers (such as WG partici=
pants or the AAA Doctors
[DOCTORS])=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B resulting in an improvement in t=
he consistency of
reviews.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The guidelines articulated in th=
is document enable the
design</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of attributes with the widest po=
ssible interoperability=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B while requiring minimal changes =
to existing systems.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As a result=2C they are suitable=
 for application to
attributes </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B designed for general usage.&nbsp=
=3B It is RECOMMENDED </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B that these guidelines be applied=
 to review of documents </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B requesting allocations within th=
e IETF standard attribute
</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space defined in [RFC2865]. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B These guidelines may also prove =
useful in the design of </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attributes within the Vendor-Spe=
cific Attribute (VSA)</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space.&nbsp=3B As noted in RFC 2=
865 Section 5.26=2C RADIUS VSAs </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B were created "to allow vendors t=
o support their own
extended </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Attributes not suitable for gene=
ral usage."&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Rather than requesting allocatio=
n of standard attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for those uses=2C [RFC2865] Sect=
ion 6.2 notes that
utilization</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of VSAs "should be encouraged in=
stead of allocation
of global </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute types=2C for functions=
 specific only to one
vendor's </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B implementation of RADIUS=2C wher=
e no interoperability is
deemed useful." </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B However=2C experience has shown =
that attributes not
originally </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B designed for general usage can s=
ubsequently garner
wide-spread </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B deployment.&nbsp=3B An example i=
s the vendor-specific attributes
</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B defined in [RFC2548]=2C which ha=
ve been widely implemented </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within IEEE 802.11 Access Points=
. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As a result=2C while SDOs and ve=
ndors MAY choose to create </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specifications not following the=
se guidelines for use in</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B scenarios within a limited scope=
 of applicability=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B where general usage is possible=
=2C&nbsp=3B adhering to the </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B design guidelines is RECOMMENDED=
.&nbsp=3B Discussion of</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B vendor allocations is provided i=
n Section 3.1.2=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B discussion of SDO allocations is=
 provided in Section</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B 3.1.3. &nbsp=3B&nbsp=3BSDOs and =
vendors desiring review of their </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specifications by the IETF are e=
ncouraged to follow </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the advice presented in Section =
3.1.4." </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">3.1.2.&nbsp=3B Vendor Allocations</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Vendor RADIUS Attribute specific=
ations SHOULD allocate
attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B from the vendor space=2C rather =
than requesting an
allocation from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS standard attribute space.=
</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As discussed in [RFC2865] Sectio=
n 5.26=2C the vendor space
is intended</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for vendors to support their own=
 Attributes not suitable
for general</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B use.&nbsp=3B However=2C it is RE=
COMMENDED that vendors follow the
guidelines</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B outlined here=2C which are inten=
ded to enable maximum
interoperability</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B with minimal changes to existing=
 systems.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Following these guidelines means=
 that RADIUS servers can
be updated</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to support the vendor's equipmen=
t by editing a RADIUS
dictionary.&nbsp=3B If</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B these guidelines are not followe=
d=2C then the vendor's
equipment can</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B only be supported via code chang=
es in RADIUS server
implementations.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Such code changes add complexity=
 and delay to
implementations.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 3.1.2 =
with the following:<br></p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">"&nbsp=3B As noted in [RFC3575] Section 2.1=2C ve=
ndors are
encouraged</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to utilize VSAs to define functi=
ons "specific only
to one vendor's</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B implementation of RADIUS=2C wher=
e no interoperability is
deemed useful.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B For functions specific only to o=
ne vendor's
implementation of RADIUS=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the use of that should be encour=
aged instead of the
allocation of</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B global attribute types."</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Nevertheless=2C following the gu=
idelines outlined within
this document</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B has several advantages=2C includ=
ing maximum
interoperability with</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B minimal changes to existing syst=
ems.&nbsp=3B Following these
guidelines </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B means that RADIUS servers can be=
 updated to support the
vendor's </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B equipment by editing a RADIUS di=
ctionary.&nbsp=3B If these
guidelines are </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B not followed=2C then the vendor'=
s equipment can only be
supported </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B via code changes in RADIUS serve=
r implementations.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Such code changes add complexity=
 and delay to
implementations."</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">3.1.3.&nbsp=3B SDO Allocations</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDO RADIUS Attribute specificati=
ons SHOULD allocate
attributes from</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the vendor space=2C rather than =
requesting an allocation
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS standard attribute space=
=2C for attributes matching
any of the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B following criteria:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes relying on data types not defined within
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within an SDO</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within a group
of SDOs.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Any new RADIUS attributes or val=
ues intended for
interoperable use</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B across a broad spectrum of the I=
nternet Community SHOULD
follow the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B normal IETF process=2C and SHOUL=
D result in allocations
from the RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B standard space.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The recommendation for SDOs to a=
llocate attributes from a
vendor</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space rather than via the IETF p=
rocess is a recognition
that SDOs may</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B desire to assert change control =
over their own RADIUS
specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B This change control can be obtai=
ned by requesting a PEC
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Internet Assigned Number Authori=
ty (IANA)=2C for use as a
Vendor-Id</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within a Vendor-Specific attribu=
te.&nbsp=3B Further allocation
of attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B inside of the VSA space defined =
by that Vendor-Id is
subject solely</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to the discretion of the SDO.&nb=
sp=3B Similarly=2C the use of data
types</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B (complex or not) within that VSA=
 space is solely under
the discretion</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of the SDO.&nbsp=3B It is RECOMM=
ENDED that SDOs follow the
guidelines</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B outlined here=2C which are inten=
ded to enable maximum
interoperability</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B with minimal changes to existing=
 systems.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B It should be understood that SDO=
s do not have to rehost
VSAs into the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B standards space solely for the p=
urpose of obtaining IETF
review.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Rehosting puts pressure on the s=
tandards space=2C and may
be harmful to</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B interoperability=2C since it can=
 create two ways to
provision the same</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B service.&nbsp=3B Rehosting may a=
lso require changes to the
RADIUS data model</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B which will affect implementation=
s that do not intend to
support the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDO specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 3.1.3 =
with the following:<br></p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">"&nbsp=3B Given the expanded utilization of RADIU=
S=2C it has</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B become apparent that requiring S=
DOs to accomplish all
their RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B work within the IETF is inherent=
ly inefficient and
unscalable.&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B SDO RADIUS Attribute specifications SHOU=
LD allocate
attributes from</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the vendor space=2C rather than =
requesting an allocation
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS standard attribute space=
=2C for attributes matching
any of the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B following criteria:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes relying on data types not defined within
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within an SDO</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within a group
of SDOs.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Allocation of new RADIUS attribu=
tes or values intended
for interoperable use</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B across a broad spectrum of the I=
nternet Community SHOULD
follow the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B allocation process defined in [R=
FC3575]. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The recommendation for SDOs to a=
llocate attributes from
the vendor</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space rather than via the IETF p=
rocess recognizes the
need for SDOs</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to assert change control over th=
eir own RADIUS
specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDOs desiring to define their VS=
As are encouraged to </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B request allocation of a Private =
Enterprise Code (PEC)
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Internet Assigned Number Authori=
ty (IANA)=2C for use as a
Vendor-Id.&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The SDO can then allocate attrib=
utes within the VSA space
defined </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by that Vendor-Id=2C at their so=
le discretion.&nbsp=3B Similarly=2C
the use of </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B data types (complex or otherwise=
) within that VSA space
is solely</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B under the discretion of the SDO.=
"</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">3.1.4.&nbsp=3B Publication of specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDOs are encouraged to seek earl=
y review of SSA
specifications by the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IETF.&nbsp=3B This review may be=
 initiated by sending mail to
the AAA</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Doctors list [DOCTORS]=2C with t=
he understanding that this
review is a</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B voluntary-based service offered =
on best-effort basis.&nbsp=3B
Since the IETF</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B is not a membership organization=
=2C in order to enable the
RADIUS SSA</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specification to be reviewed=2C =
it is RECOMMENDED that it
be made</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B publicly available=3B this also =
encourages interoperability.&nbsp=3B
Where the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS SSA specification is embe=
dded within a larger
document which</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B cannot be made public=2C the RAD=
IUS attribute and value
definitions</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SHOULD be published instead as a=
n Informational RFC=2C as
with</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [RFC4679].&nbsp=3B This process =
SHOULD be followed instead of
requesting</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IANA allocations from within the=
 standard RADIUS
attribute space.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Similarly=2C vendors are encoura=
ged to make their
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B publicly available=2C for maximu=
m interoperability.&nbsp=3B
However=2C it is not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B necessary for them to request pu=
blication of their VSA
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B as Informational RFCs by the IET=
F.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B All other specifications=2C incl=
uding new authentication=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B authorization=2C and/or security=
 mechanisms SHOULD be
allocated via the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B standard RADIUS space=2C as note=
d in [RFC3575] Section 2.1.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 3.1.4 =
with the following:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">"&nbsp=3B SDOs or vendors desiring review of thei=
r RADIUS
specifications </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by the IETF are&nbsp=3B encourag=
ed to seek review as early as
possible=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B so as to avoid potential delays.=
&nbsp=3B Since reviews are
handled by volunteers=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B responses are provided on a best=
-effort basis=2C with no
service</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B level guarantees.&nbsp=3B&nbsp=
=3B In order to provide reviewers with
access to the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specification=2C&nbsp=3B SDOs an=
d vendors are encouraged to make
them publicly available.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Where the RADIUS specification i=
s embedded within a
larger document which</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B cannot be made public=2C the RAD=
IUS attribute and value
definitions</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B can be made available on a publi=
c web site or can be
published as </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B an Informational RFC=2C as with =
[RFC4679]. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Review can be requested by sendi=
ng email to the AAA
Doctors [DOCTORS]</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B or equivalent mailing list.&nbsp=
=3B The IETF Operations &amp=3B
Management</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Area Directors will then arrange=
 for the review to be</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B completed and posted to the AAA =
Doctors mailing list</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [DOCTORS]=2C RADEXT WG mailing l=
ist=2C or other IETF mailing</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B list.&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The review process requires neit=
her allocation of
attributes </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within the IETF standard attribu=
te space nor publication
of an </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IETF RFC.&nbsp=3B Requiring SDOs=
 or vendors to rehost VSAs into
the IETF standards </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute space solely for the p=
urpose of obtaining
review</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B would put pressure on the standa=
rds space=2C and may be
harmful to</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B interoperability=2C since it can=
 create two ways to
provision the same</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B service.&nbsp=3B Rehosting may a=
lso require changes to the
RADIUS data model</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B which will affect implementation=
s that do not intend to
support the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDO or vendor specifications."</=
p>

</div> 		 	   		  </body>
</html>=

--_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_--

--
to unsubscribe send a message to 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 Feb 14 18:10:57 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90A9728C0D0 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 14 Feb 2010 18:10:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[AWL=-3.714, 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 QXMu0hCpxn9w for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Sun, 14 Feb 2010 18:10:56 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id EA3323A748E for <radext-archive-IeZ9sae2@lists.ietf.org>; Sun, 14 Feb 2010 18:10:54 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NgqMi-000BkH-P7 for radiusext-data0@psg.com; Mon, 15 Feb 2010 02:07:12 +0000
Received: from [76.96.62.80] (helo=qmta08.westchester.pa.mail.comcast.net) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <d.b.nelson@comcast.net>) id 1NgqMg-000Bk2-03 for radiusext@ops.ietf.org; Mon, 15 Feb 2010 02:07:10 +0000
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta08.westchester.pa.mail.comcast.net with comcast id hsa41d0040bG4ec58274oe; Mon, 15 Feb 2010 02:07:04 +0000
Received: from NEWTON603 ([71.232.143.198]) by omta03.westchester.pa.mail.comcast.net with comcast id i2741d0054H2mdz3P274b0; Mon, 15 Feb 2010 02:07:04 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
References: <BLU137-DS3D85750A8B968C9620D0F934B0@phx.gbl> <BLU137-W377F2298AEEB878B736E09934B0@phx.gbl>
Subject: RE: Proposal for resolution of Issue 327:  Applicability
Date: Sun, 14 Feb 2010 21:07:03 -0500
Message-ID: <F5236010EB2D41B987DB4ED8D390A173@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BLU137-W377F2298AEEB878B736E09934B0@phx.gbl>
Thread-Index: AcqtviIKEF5ysBQ5Q/qwbbyUB5JzPAAJT5Gw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba writes...

> The concerns expressed in Issue 327 appear to apply to
> Sections 1, 1.3, 3.1.2, 3.1.3 and 3.1.4.=20
>
> Here is a proposed resolution.=A0 Comments welcome.

I think this is helpful.



--
to unsubscribe send a message to 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 Feb 16 06:53:40 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E5C53A7B5D for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 06:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=-2.042, 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 1x+HGW-uN4YM for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 06:53:39 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9E85A3A7698 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 16 Feb 2010 06:53:39 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NhOmS-0009ve-QY for radiusext-data0@psg.com; Tue, 16 Feb 2010 14:52:04 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NhOmN-0009tX-1P for radiusext@ops.ietf.org; Tue, 16 Feb 2010 14:51:59 +0000
Message-ID: <4B7AB10D.4010005@deployingradius.com>
Date: Tue, 16 Feb 2010 15:51:57 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (part I)
References: <BLU137-W35CCBE493A9F2C672FE20C93520@phx.gbl>
In-Reply-To: <BLU137-W35CCBE493A9F2C672FE20C93520@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> [BA] My suggestion is that this material be moved to Section 2, since it doesn't relate to the
> reasons why publication is recommended as an Informational RFC. 

  OK.

  I've added that text with minor rewording, and integrated Section
2.3.1 as per your other suggestion.

  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 Feb 16 06:54:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 213BC3A7698 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 06:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=-1.701, 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 yCcwXMow9HD8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 06:54:32 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 254B73A70E2 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 16 Feb 2010 06:54:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NhOmQ-0009v6-EF for radiusext-data0@psg.com; Tue, 16 Feb 2010 14:52:02 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NhOmN-0009sz-1P for radiusext@ops.ietf.org; Tue, 16 Feb 2010 14:51:59 +0000
Message-ID: <4B7AB10C.5030800@deployingradius.com>
Date: Tue, 16 Feb 2010 15:51:56 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl>
In-Reply-To: <BLU137-W6861B435730E1D4BA388293520@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> Sections 2.1 and Section 2.2
> 
> Section 2 explains the unique properties of Status-Server and why a
> RADIUS client might want to use it.  RFC 2865 Section 2.6
> explains why "keepalives" are a bad idea.  Presumably this advice
> applies to both RADIUS Access-Request and Accounting-Request
> keepalives.  Given that, Sections 2.1 and 2.2 belabor the point.  I'd
> suggest that they be deleted.

  I think that they have some use.  There are a number of
implementations which "overload" Access-Requests for all kinds of
functionality.  Having an explanation as to why this is bad can help
guide implementors.

> Section 2.3
> 
> I would suggest deleting this section as well.

  OK.

> Section 2.3.1
> 
> My advice is to incorporate the material in this section into Section 2
> (To be retitled Overview).

  Done.

> Section 3
> 
>      Response Authenticator
> 
>          The value of the Authenticator field in Access-Accept, or
>          Accounting-Response packets is called the Response
>          Authenticator, and contains a one-way MD5 hash calculated over
>          a stream of octets consisting of: the RADIUS packet, beginning
>          with the Code field, including the Identifier, the Length, the
>          Request Authenticator field from the Status-Server packet, and
>          the response Attributes (if any), followed by the shared
>          secret.  That is, ResponseAuth =
>          MD5(Code+ID+Length+RequestAuth+Attributes+Secret) where +
>          denotes concatenation.
> 
> [BA] Why is this material here?  If you need it at all (I don't think so), you can just reference
> RFC 2865 and/or 2866. 

  Otherwise there will be confusion over how to calculate it.  The other
RFCs define how the Response Authenticator is calculated for response
packets.  It's not a *bad* idea to include similar text here.

>    Status-Server packets MAY include NAS-Identifier, and one of NAS-IP-
>    Address or NAS-IPv6-Address.  These attributes are not necessary for
>    the operation of Status-Server, but may be useful information to a
>    server that receives those packets.
> 
> [BA] You might say that the server MUST ignore other attributes. 

  OK.

>    Other attributes SHOULD NOT be included in a Status-Server packet.
>    User authentication credentials such as User-Password, CHAP-Password,
>    EAP-Message, etc. MUST NOT appear in a Status-Server packet sent to a
>    RADIUS authentication port.  User or NAS accounting attributes such
>    as Acct-Session-Id, Acct-Status-Type, Acct-Input-Octets, etc.  MUST
>    NOT appear in a Status-Server packet sent to a RADIUS accounting
>    port.
> 
> [BA] Also, presumably User-Name is not included (relevant to the point about realms made earlier). 

  Yes.  I'll add that in.

  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 Feb 16 07:00:30 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7C033A7698 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 07:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-1.458, 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 hd0mhgJ-hZ1J for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 07:00:30 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E2D063A6906 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 16 Feb 2010 07:00:29 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NhOu7-000B24-OW for radiusext-data0@psg.com; Tue, 16 Feb 2010 14:59:59 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NhOu1-000B0e-7U for radiusext@ops.ietf.org; Tue, 16 Feb 2010 14:59:53 +0000
Message-ID: <4B7AB2E8.4070108@deployingradius.com>
Date: Tue, 16 Feb 2010 15:59:52 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (part III)
References: <BLU137-W1951B040BEFCE55D331E9D93520@phx.gbl>
In-Reply-To: <BLU137-W1951B040BEFCE55D331E9D93520@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> Section 4.3
> 
> On reading this section I am unsure about whether the discussion relates
> to failover between proxies or servers.
> Suggested rewrite:
> 
> 
>       4.3. Fail-over with Status-Server

  OK.  Looks good to me.

> Section 5
> 
> You might want to add a table entry for User-Name.

  OK, and User-Password, CHAP-Password, etc.

  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 Feb 16 08:33:17 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DAD728C0DF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 08:33:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.095
X-Spam-Level: 
X-Spam-Status: No, score=-102.095 tagged_above=-999 required=5 tests=[AWL=0.505, 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 4OJgjzcWXzu4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 16 Feb 2010 08:33:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 303E33A71A6 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 16 Feb 2010 08:33:16 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NhQKs-000NKz-4X for radiusext-data0@psg.com; Tue, 16 Feb 2010 16:31:42 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <root@core3.amsl.com>) id 1NhQKo-000NKQ-B8 for radiusext@ops.ietf.org; Tue, 16 Feb 2010 16:31:38 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 11B5E3A7B72; Tue, 16 Feb 2010 08:30:01 -0800 (PST)
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-06.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100216163002.11B5E3A7B72@core3.amsl.com>
Date: Tue, 16 Feb 2010 08:30:02 -0800 (PST)
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-06.txt
	Pages           : 24
	Date            : 2010-02-16

This document describes a deployed extension to the Remote
Authentication Dial In User Service (RADIUS) protocol, enabling
clients to query the status of a RADIUS server.  This extension
utilizes the Status-Server (12) Code, which was reserved for
experimental use in RFC 2865.

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

Content-Type: text/plain
Content-ID:     <2010-02-16081609.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  Thu Feb 18 11:33:44 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0617B3A8039 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 18 Feb 2010 11:33:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.546
X-Spam-Level: 
X-Spam-Status: No, score=-9.546 tagged_above=-999 required=5 tests=[AWL=-1.053, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 yerkEU5mBOMr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 18 Feb 2010 11:33:40 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 970E93A803A for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 18 Feb 2010 11:33:39 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiC49-000DFC-5F for radiusext-data0@psg.com; Thu, 18 Feb 2010 19:29:37 +0000
Received: from [64.102.122.148] (helo=rtp-iport-1.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <wdec@cisco.com>) id 1NiC46-000DEs-BU for radiusext@ops.ietf.org; Thu, 18 Feb 2010 19:29:34 +0000
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgFAFIjfUtAZnwN/2dsb2JhbACBQplGdKUzl3yEZwQ
X-IronPort-AV: E=Sophos;i="4.49,498,1262563200";  d="scan'208,217";a="87149060"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 18 Feb 2010 19:29:33 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o1IJTWQx028805; Thu, 18 Feb 2010 19:29:32 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Feb 2010 20:29:31 +0100
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_01CAB0D0.B1CE620F"
Subject: RE: RADEXT Virtual Interim Agenda, Take Two
Date: Thu, 18 Feb 2010 20:29:26 +0100
Message-ID: <A16B9A4922C4A544A94565E870362B5001457C15@XMB-AMS-111.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RADEXT Virtual Interim Agenda, Take Two
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAAG6JCIAFxmguQ
References: <BLU137-DS570599EE0D8C6B358FD13934F0@phx.gbl> 
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>
Cc: <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 18 Feb 2010 19:29:31.0829 (UTC) FILETIME=[B1ED5E50:01CAB0D0]
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_01CAB0D0.B1CE620F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Resending, as I have not seen a response.


________________________________

	From: Wojciech Dec (wdec)=20
	Sent: 11 February 2010 12:05
	To: 'Bernard Aboba'
	Subject: RE: RADEXT Virtual Interim Agenda, Take Two
=09
=09
	Hi Bernard,
	=20
	could you add a 10min slot for
draft-lourdelet-radext-ipv6-access to the agenda?
	=20
	Thanks,
	Woj.


________________________________

		From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
		Sent: 10 February 2010 22:54
		To: radiusext@ops.ietf.org
		Subject: RADEXT Virtual Interim Agenda, Take Two
	=09
	=09

		RADEXT Virtual Interim Meeting
		Tuesday, February 23, 2010
		10 AM - 12:30 PM Pacific Time
	=09
		Agenda
	=09
		10 AM - 10:15 AM PT: Preliminaries=20
	=09
		     Conference issues/debugging
		     Attendance
		     Note takers
		     Agenda bash
	=09
		RADSEC (60 minutes)
	=09
		10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15
minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-status-server

		10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok
(15 minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>=20

		10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15
minutes)
		http://tools.ietf.org/html/draft-ietf-radext-radsec

	=09
		11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan
Winter (15 minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

		Design Guidelines (60 minutes)
	=09
		11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60
minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

	=09
		Wrap-up (15 minutes)
	=09
		12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:
WG Chairs & ADs (15 minutes)


------_=_NextPart_001_01CAB0D0.B1CE620F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5880" name=3DGENERATOR>
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D952272719-18022010>Resending, as I have not seen a=20
response.</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 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> Wojciech Dec (wdec) =
<BR><B>Sent:</B> 11=20
  February 2010 12:05<BR><B>To:</B> 'Bernard Aboba'<BR><B>Subject:</B> =
RE:=20
  RADEXT Virtual Interim Agenda, Take Two<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2>Hi Bernard,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial><FONT=20
  size=3D2>could you add a 10min slot =
for&nbsp;draft-lourdelet-radext-ipv6-access=20
  to the agenda<SPAN=20
class=3D983360411-11022010>?</SPAN></FONT></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2>Thanks,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2>Woj.</FONT></SPAN></DIV></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 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> =
owner-radiusext@ops.ietf.org=20
    [mailto:owner-radiusext@ops.ietf.org] <B>On Behalf Of </B>Bernard=20
    Aboba<BR><B>Sent:</B> 10 February 2010 22:54<BR><B>To:</B>=20
    radiusext@ops.ietf.org<BR><B>Subject:</B> RADEXT Virtual Interim =
Agenda,=20
    Take Two<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">RADEXT=20
    Virtual Interim Meeting<BR>Tuesday, February 23, 2010<BR>10 AM - =
12:30 PM=20
    Pacific Time<BR><BR>Agenda<BR><BR>10 AM - 10:15 AM PT: Preliminaries =

    <BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; Conference=20
    issues/debugging<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
    Attendance<BR>&nbsp;&nbsp;&nbsp;&nbsp; Note=20
    takers<BR>&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<BR><BR>RADSEC (60=20
    minutes)<BR><BR>10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, =
Alan DeKok (15=20
    minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</A></SPAN><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:30=20
    AM PT &#8211; 10:45 AM PT RADIUS over TCP, Alan DeKok (15 =
minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><SPAN=
=20
    style=3D"COLOR: =
black">http://tools.ietf.org/html/draft-ietf-radext-tcp-transport</SPAN><=
/A></SPAN><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:45=20
    AM - 11:00 AM PT&nbsp; RADSEC, Stefan Winter (15 minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</A><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>11:00=20
    AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</A><o:p></o=
:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Design=20
    Guidelines (60 minutes)<BR><BR>11:15 AM &#8211; 12:15 PM PT Design =
Guidelines,=20
    Alan DeKok (60 minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</A><o:p></o=
:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>Wrap-up=20
    (15 minutes)<BR><BR>12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; =
Discussion and=20
    Next Steps:&nbsp; WG Chairs &amp; ADs (15=20
    =
minutes)<o:p></o:p></SPAN></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HT=
ML>

------_=_NextPart_001_01CAB0D0.B1CE620F--

--
to unsubscribe send a message to 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 Feb 19 02:15:06 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFEE33A8102 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:15:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.746
X-Spam-Level: 
X-Spam-Status: No, score=-1.746 tagged_above=-999 required=5 tests=[AWL=-1.251, 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 qOIE8VQbhJQJ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:15:02 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3DCA728C11B for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 02:15:01 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiPr7-000EJT-3g for radiusext-data0@psg.com; Fri, 19 Feb 2010 10:13:05 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NiPr4-000EA5-GW for radiusext@ops.ietf.org; Fri, 19 Feb 2010 10:13:02 +0000
Message-ID: <4B7E642C.2080705@deployingradius.com>
Date: Fri, 19 Feb 2010 11:13:00 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-tcp-transport (Part I)
References: <BLU137-DS1E00B50A4DE6656D314EB93550@phx.gbl>
In-Reply-To: <BLU137-DS1E00B50A4DE6656D314EB93550@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> [BA] In particular, filters routers and firewalls often drop UDP
> fragments, since otherwise they would need to reassemble them in order
> to apply the filter rules.
> 
> However, this is not a “transport” issue, so much as a
> forwarding/filtering issue.  Instead of “Transport” you might say
> “handling”.

  OK.

> [BA] Note double periods in first sentence, and no period in the last
> sentence.  As I read the document, it is really only suggesting a
> different set of tradeoffs for inter-server proxying.  So you might say
> “For use-cases such as inter-server proxying, [RTLS] suggests an
> alternative transport and security model -- RADIUS over TLS.  This
> document describes the transport implications of running RADIUS over
> TLS/TCP.”

  OK.

> [BA]  Suggested rewrite:
> ...the larger congestion
>    window supported by TCP may allow multiple TCP segments to
>    be sent within a single window.  As a result, RADIUS/EAP
>    traffic required for an EAP-TLS authentication with 8KB
>    certificate chains may be reduced to 7 round-trips or less,
>    resulting in substantially reduced authentication times.

  Is that really true?  The common limitation on EAP is the 1022 byte
maximum overhead for EAPoL.  Allowing 4K RADIUS packet sizes helps only
when doing EAP *without* EAPoL.  That's a pretty rare occurance.

...  In addition, most TCP
>    implementations discover Path MTU better than RADIUS application
>    implementations, resulting in significantly fewer fragmented packets.

  This is duplicate text.

  I've done some word-smithing, and updated the doc.

  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 Feb 19 02:42:10 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C89D928C248 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:42:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[AWL=-1.126, 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 0h8qxLgsnkpl for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:42:09 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8E82128C243 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 02:42:09 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiQHJ-000Hu2-SF for radiusext-data0@psg.com; Fri, 19 Feb 2010 10:40:09 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NiQHH-000Ht4-2i for radiusext@ops.ietf.org; Fri, 19 Feb 2010 10:40:07 +0000
Message-ID: <4B7E6A83.9000600@deployingradius.com>
Date: Fri, 19 Feb 2010 11:40:03 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-tcp-transport (Part II)
References: <BLU137-DS648B9E69F4725B4DC99BC93550@phx.gbl>
In-Reply-To: <BLU137-DS648B9E69F4725B4DC99BC93550@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> [BA] How about this?

  OK.

>    The changes to RADIUS implementations required to implement this
>    specification are largely limited to the portions that send and
>    receive packets on the network.
>  
> 
> [BA] Is this sentence necessary?  What portions of a RADIUS
> implementation **don’t** relate
> To sending and receiving packets?   I’d recommend that it be deleted.

  Implementations have re-tranmission timers for UDP sockets.  These
timers need to be disabled for TCP sockets.

  The timers are usually "internal" to an implementation, and don't
directly involve recv() or send() calls.

> [BA] You might say “Since these ports are unused by existing RADIUS
> implementations, 
> the assigned values SHOULD be used as the default ports for RADIUS over
> TCP.”

  OK.

> I would merge section 2.4 into this section so that one section can
> cover ports 
> for both RADIUS over TCP and RADIUS over TLS.

  OK.

> You might revise this section to make it clear that the advice for use
> of MIBs 
> with RADIUS over TCP also applies to RADIUS over TLS.

  I thought I'd leave that to the RTLS document.

> [BA] Suggest this section be renamed “Liveness Detection”.

  How about "detecting live servers" ?

>    Implementations of this specification SHOULD treat the "silently 
>    discard" texts referenced above as "silently discard and close the
>    connection." 
> 
> [BA] What is the alternative to this behavior?  Could this be a MUST?

  There are some cases where "silently discard" is OK for TCP.  I don't
recall right now, but I do remember auditing the previous documents.

  The text following that sentence outlines the situations where closing
the connection is a MUST.

>    TCP connections MAY be closed if any of the circumstances outlined 
>    below are seen.  Alternatively, the TCP connection MAY remain open if
>    any of the following circumstances are seen, but the invalid packet
>    MUST BE silently discarded.
>
> [BA] Not sure how you can do this in practice.  Are you assuming that the 
> Length field remains valid?

  Yes.  The previous MUST requirement are applied first.

  How about the clarifications to the text:

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

> Section 2.6.6
>
> Given the discussion in Section 1.1, I’m wondering if this section (or
> some other section) 
> shouldn’t make a recommendation on the maximum RADIUS message size
> applicable to use with
> RADIUS/EAP.  It seems to me that using a larger RADIUS message size
> would make a lot of sense. 

  Only when the transport protocol to the supplicant allows large EAP
packets.

  If the NAS sends a Framed-MTU, most RADIUS servers will honor it.
This works today when large packets are allowed.

  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 Feb 19 02:44:16 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2DAC28C24A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.519
X-Spam-Level: 
X-Spam-Status: No, score=-1.519 tagged_above=-999 required=5 tests=[AWL=-1.024, 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 ggbIq2ejv5hI for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:44:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E655128C249 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 02:44:15 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiQKx-000ISv-AI for radiusext-data0@psg.com; Fri, 19 Feb 2010 10:43:55 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NiQKv-000ISV-48 for radiusext@ops.ietf.org; Fri, 19 Feb 2010 10:43:53 +0000
Message-ID: <4B7E6B68.5070006@deployingradius.com>
Date: Fri, 19 Feb 2010 11:43:52 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-tcp-transport (Part III)
References: <BLU137-DS4F4F654FDF24869ACFA1A93550@phx.gbl>
In-Reply-To: <BLU137-DS4F4F654FDF24869ACFA1A93550@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> I am wondering whether this document should take a position on the
> recommendations described in [RFC3539] Section 3, particularly:
> 
> 3.2.  Use of Nagle Algorithm
> 3.3.  Multiple Connections
> 3.4.2 Primary/Secondary failover
> 3.4.3 Connection Load Balancing
> 3.6 Invalidation of Transport Parameter Estimates
> 3.7 Inability to Use Fast Retransmit
> 3.8 Head of Line Blocking
> 3.9 Congestion Avoidance
> 3.10 Premature Failover

  There's already a "catch-all" sentence in the doc:

The guidelines defined in [RFC3539] for implementing a AAA protocol
over reliable transport are applicable to RADIUS over TLS/TCP.


  I think that should be fine.  I don't want to reproduce 3539 here, or
do a section-by-section review, saying "this applies, too".

  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 Feb 19 02:47:53 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D95828C249 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gu7GT4dh0e7K for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 02:47:52 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7738328C242 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 02:47:49 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiQNr-000Iw0-F9 for radiusext-data0@psg.com; Fri, 19 Feb 2010 10:46:55 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <root@core3.amsl.com>) id 1NiQNl-000Iva-Hk for radiusext@ops.ietf.org; Fri, 19 Feb 2010 10:46:49 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 1FE9328C185; Fri, 19 Feb 2010 02:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-tcp-transport-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100219104502.1FE9328C185@core3.amsl.com>
Date: Fri, 19 Feb 2010 02:45:02 -0800 (PST)
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 Over TCP
	Author(s)       : A. DeKok
	Filename        : draft-ietf-radext-tcp-transport-05.txt
	Pages           : 18
	Date            : 2010-02-19

The Remote Authentication Dial In User Server (RADIUS) Protocol has
traditionally used the User Datagram Protocol (UDP) as its underlying
transport layer.  This document defines RADIUS over the Transmission
Control Protocol (TCP), in order to address handling issues related
to RADIUS over TLS [RTLS].  It is not intended to define TCP as a
transport protocol for RADIUS in the absence of TLS.

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

Content-Type: text/plain
Content-ID:     <2010-02-19024419.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 Feb 19 05:00:17 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A230628C258 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 05:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.433
X-Spam-Level: 
X-Spam-Status: No, score=-1.433 tagged_above=-999 required=5 tests=[AWL=-0.938, 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 I6L4N1U4R4vn for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 05:00:15 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D3DBB28C241 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 05:00:14 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiSQS-000ERM-6X for radiusext-data0@psg.com; Fri, 19 Feb 2010 12:57:44 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NiSQN-000EQc-Jx for radiusext@ops.ietf.org; Fri, 19 Feb 2010 12:57:39 +0000
Message-ID: <4B7E8AC1.80702@deployingradius.com>
Date: Fri, 19 Feb 2010 13:57:37 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: REQUIRED READING: RADEXT Virtual Interim Design Guidelines Discussion
References: <BLU137-DS2801F368B1134D7EA2B3E934B0@phx.gbl>
In-Reply-To: <BLU137-DS2801F368B1134D7EA2B3E934B0@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> [BA]  I have collected Avi Lior’s review of the -10 text (and suggested changes) within Issue 327: Applicability <http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327> .  Joe Salowey’s review is  
> provided in Issue 325: Review <http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325> .  As noted in a previous message summarizing the results of the “Last Look” (http://ops.ietf.org/lists/radiusext/2010/msg00150.html) there appears to be WG consensus to make changes to the document to address the concerns that have been raised.

  I've submitted a -11 version of the document.  The only change from
the previous -11 version on my web site is a paragraph addressing one of
Joe's comments.  The text was proposed on the list, and accepted.

  A full review of all issues is below.  At this point, I think that all
open issues have been addressed.



300: replacement text

In order to characterize current attribute usage, both the basic and
complex data types defined in the existing RADIUS RFCs are reviewed.

301: replacement text

Does the data fit within the basic data types described in Section
2.1.1, as outlined below?  If so, it SHOULD be encapsulated in a
[RFC2865] format RADIUS attribute, or in a [RFC2865] format RADIUS VSA
that uses one of the existing RADIUS data types.

302: deleted references to [EXTEN]

304: addressed in prior revisions

311: addressed in prior revisions

312: removed references to [EXTEN] in prior revisions

313: clarified in prior revisions

314: issue was closed

318: rejected.

319: addressed in prior revisions

320: addressed in prior revisions

325: addresed in -11

327: addressed in -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  Fri Feb 19 05:02:52 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F220C28C24C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 05:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.358
X-Spam-Level: 
X-Spam-Status: No, score=-102.358 tagged_above=-999 required=5 tests=[AWL=0.242, 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 aUNhP4bc0nhM for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 05:02:51 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1ECB328C24A for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 05:02:51 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NiSUV-000FQN-4x for radiusext-data0@psg.com; Fri, 19 Feb 2010 13:01:55 +0000
Received: from [2001:1890:1112:1::20] (helo=mail.ietf.org) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <root@core3.amsl.com>) id 1NiSUQ-000FMJ-4w for radiusext@ops.ietf.org; Fri, 19 Feb 2010 13:01:50 +0000
Received: by core3.amsl.com (Postfix, from userid 0) id 4170428C1F7; Fri, 19 Feb 2010 05:00:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-design-11.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100219130002.4170428C1F7@core3.amsl.com>
Date: Fri, 19 Feb 2010 05:00:02 -0800 (PST)
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-11.txt
	Pages           : 38
	Date            : 2010-02-19

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

Content-Type: text/plain
Content-ID:     <2010-02-19045428.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 Feb 19 23:07:07 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58AD628C0F2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 23:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.99
X-Spam-Level: 
X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[AWL=-0.496, 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 O5iKSsMBWeX2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 23:07:03 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 78E0A3A7C11 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 23:07:02 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NijOc-00046M-6y for radiusext-data0@psg.com; Sat, 20 Feb 2010 07:04:58 +0000
Received: from [65.55.116.23] (helo=blu0-omc1-s12.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NijOZ-00045x-07 for radiusext@ops.ietf.org; Sat, 20 Feb 2010 07:04:55 +0000
Received: from BLU137-DS4 ([65.55.116.7]) by blu0-omc1-s12.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Feb 2010 23:04:54 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS459F4850D1779DFC7D27A93450@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take Three
Date: Fri, 19 Feb 2010 23:05:37 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0113_01CAB1B8.0C9A2D50"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAB15MsgA==
Content-Language: en-us
X-OriginalArrivalTime: 20 Feb 2010 07:04:54.0390 (UTC) FILETIME=[00ECB160:01CAB1FB]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

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

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (50 minutes)

11:15 AM - 12:05 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

Issue 325: Review
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325>  (Submitted
by Joe Salowey) 

Issue 327: Applicability
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327>  (Submitted
by Avi Lior)    Proposed
<http://ops.ietf.org/lists/radiusext/2010/msg00175.html>  Resolution


Pre-Work Item Review (10 minutes)

12:05 PM PT - 12:15 PT RADIUS Attributes for IPv6 Networks, W. Dec (10
minutes)

http://tools.ietf.org/html/
<http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access>
draft-lourdelet-radext-ipv6-access

Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


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

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time<br>
<br>
Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a></span><=
span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines =
(</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>5</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'=
>0
minutes)<br>
<br>
11:15 AM &#8211; 12:</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>0</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>5 PM PT Design Guidelines, Alan DeKok (60 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 325: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
325">Review</a>
(Submitted by Joe Salowey) <span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 327: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
327">Applicability</a>
(Submitted by Avi Lior)<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> &nbsp;&nbsp;&nbsp;<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00175.html">Proposed
Resolution</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Pre-Work Item Review (</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>1</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>0 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>12:05 PM PT &#8211; =
12:15 PT RADIUS
Attributes for IPv6 Networks, W. Dec (10 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/<span
style=3D'font-family:"Arial","sans-serif"'>draft-lourdelet-radext-ipv6-ac=
cess</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_0113_01CAB1B8.0C9A2D50--

--
to unsubscribe send a message to 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 Feb 19 23:33:45 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 870DC3A7C6C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 23:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.221
X-Spam-Level: 
X-Spam-Status: No, score=0.221 tagged_above=-999 required=5 tests=[AWL=-1.699, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWArP4y4kWFf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 23:33:43 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D080F3A7C1D for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 23:33:42 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NijqG-0006w6-Te for radiusext-data0@psg.com; Sat, 20 Feb 2010 07:33:32 +0000
Received: from [65.55.116.15] (helo=blu0-omc1-s4.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NijqC-0006vj-OF for radiusext@ops.ietf.org; Sat, 20 Feb 2010 07:33:28 +0000
Received: from BLU137-DS7 ([65.55.116.8]) by blu0-omc1-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Feb 2010 23:33:27 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS7BB6FA4E8DDFCA13B99DD93450@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Virtual interim presenters:  Request for Slides
Date: Fri, 19 Feb 2010 23:34:05 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0134_01CAB1BC.0A456B10"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acqx/xTIJb9wP7HMQgGf/lwMnO1XVA==
Content-Language: en-us
x-cr-hashedpuzzle: Alao A4Mt A81X CSaK CWMy DDk+ DUes FqeV F6Be HJIe HJkH Hdvx HeS6 Hrsg JDoC KPze;1;cgBhAGQAaQB1AHMAZQB4AHQAQABvAHAAcwAuAGkAZQB0AGYALgBvAHIAZwA=;Sosha1_v1;7;{D70428FE-ECF9-4360-AD06-A37B26AB32EB};YgBlAHIAbgBhAHIAZABhAEAAbQBpAGMAcgBvAHMAbwBmAHQALgBjAG8AbQA=;Sat, 20 Feb 2010 07:34:05 GMT;VgBpAHIAdAB1AGEAbAAgAGkAbgB0AGUAcgBpAG0AIABwAHIAZQBzAGUAbgB0AGUAcgBzADoAIAAgAFIAZQBxAHUAZQBzAHQAIABmAG8AcgAgAFMAbABpAGQAZQBzAA==
x-cr-puzzleid: {D70428FE-ECF9-4360-AD06-A37B26AB32EB}
X-OriginalArrivalTime: 20 Feb 2010 07:33:27.0905 (UTC) FILETIME=[FE425510:01CAB1FE]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

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

If you're on the agenda for the RADEXT Virtual Interim meeting on February
23, 2010, please send your slides to myself or Dave no later than Tuesday,
February 22, so that we can get them up on the archive in time. 

 

Thanks in advance!


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

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>If you&#8217;re on the agenda for the RADEXT =
Virtual Interim
meeting on February 23, 2010, please send your slides to myself or Dave =
no
later than Tuesday, February 22, so that we can get them up on the =
archive in
time. <o:p></o:p></p>

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

<p class=3DMsoNormal>Thanks in advance!<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0134_01CAB1BC.0A456B10--

--
to unsubscribe send a message to 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 Feb 19 23:34:16 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BFE23A7D29 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 23:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.971
X-Spam-Level: 
X-Spam-Status: No, score=-0.971 tagged_above=-999 required=5 tests=[AWL=-0.477, 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 7J442fSdkYfr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 19 Feb 2010 23:34:11 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7783C3A80CE for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 19 Feb 2010 23:34:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nijnz-0006jI-Ut for radiusext-data0@psg.com; Sat, 20 Feb 2010 07:31:11 +0000
Received: from [65.55.116.18] (helo=blu0-omc1-s7.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Nijnu-0006ir-JR for radiusext@ops.ietf.org; Sat, 20 Feb 2010 07:31:06 +0000
Received: from BLU137-DS5 ([65.55.116.8]) by blu0-omc1-s7.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Feb 2010 23:31:05 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS54DF70EC3EAA60F5015EE93450@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take Four
Date: Fri, 19 Feb 2010 23:31:48 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012A_01CAB1BB.B55BBF50"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAB15MsgAAA2mBQAABiObA=
Content-Language: en-us
X-OriginalArrivalTime: 20 Feb 2010 07:31:05.0844 (UTC) FILETIME=[A9958B40:01CAB1FE]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_012A_01CAB1BB.B55BBF50
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Jabber room:  radext at jabber.ietf.org (please join)

Presentations:  <http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/>
http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/

WebEx conference parameters:
<http://ops.ietf.org/lists/radiusext/2010/msg00169.html>
http://ops.ietf.org/lists/radiusext/2010/msg00169.html

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (50 minutes)

11:15 AM - 12:05 PM PT Design Guidelines, Alan DeKok (50 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

Issue 325: Review
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325>  (Submitted
by Joe Salowey) 

Issue 327: Applicability
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327>  (Submitted
by Avi Lior)    Proposed
<http://ops.ietf.org/lists/radiusext/2010/msg00175.html>  Resolution


Pre-Work Item Review (10 minutes)

12:05 PM PT - 12:15 PT RADIUS Attributes for IPv6 Networks, W. Dec (10
minutes)

http://tools.ietf.org/html/
<http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access>
draft-lourdelet-radext-ipv6-access

Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


------=_NextPart_000_012A_01CAB1BB.B55BBF50
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time</span><span =
style=3D'font-size:10.0pt;font-family:
"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>Jabber room:&nbsp; =
radext at
jabber.ietf.org (please join)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>Presentations: <a
href=3D"http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><span
style=3D'color:black'>http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/</=
span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>WebEx conference =
parameters: </span><span
style=3D'color:black'><a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00169.html"><span
style=3D'color:black'>http://ops.ietf.org/lists/radiusext/2010/msg00169.h=
tml</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a></span><=
span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines =
(</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>5</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'=
>0 minutes)<br>
<br>
11:15 AM &#8211; 12:</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>0</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>5 PM PT Design Guidelines, Alan DeKok (</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>5</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'=
>0
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 325: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
325">Review</a>
(Submitted by Joe Salowey) <span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 327: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
327">Applicability</a>
(Submitted by Avi Lior)<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> &nbsp;&nbsp;&nbsp;<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00175.html">Proposed
Resolution</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Pre-Work Item Review (</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>1</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>0 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>12:05 PM PT &#8211; =
12:15 PT RADIUS
Attributes for IPv6 Networks, W. Dec (10 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/<span
style=3D'font-family:"Arial","sans-serif"'>draft-lourdelet-radext-ipv6-ac=
cess</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_012A_01CAB1BB.B55BBF50--

--
to unsubscribe send a message to 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 Feb 22 12:15:23 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E80013A81AB for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 22 Feb 2010 12:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[AWL=-0.626, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_WEOFFER=0.3]
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 aAg+IzPxg5Yr for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Mon, 22 Feb 2010 12:15:18 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6D38F28C164 for <radext-archive-IeZ9sae2@lists.ietf.org>; Mon, 22 Feb 2010 12:15:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NjedS-0008mX-D9 for radiusext-data0@psg.com; Mon, 22 Feb 2010 20:12:06 +0000
Received: from [65.55.116.26] (helo=blu0-omc1-s15.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NjedP-0008mE-AF for radiusext@ops.ietf.org; Mon, 22 Feb 2010 20:12:03 +0000
Received: from BLU137-DS7 ([65.55.116.7]) by blu0-omc1-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 22 Feb 2010 12:12:02 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS7B020CCE718F044DE2A1793430@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
References: <7735D8F6-FD9E-43AB-B655-07AD53481AA5@bridgewatersystems.com>
In-Reply-To: <7735D8F6-FD9E-43AB-B655-07AD53481AA5@bridgewatersystems.com>
Subject: FW: Review of Radius Guidelines 11
Date: Mon, 22 Feb 2010 12:12:04 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHZqC/5zypIw/6vMRSzbnyC1HnsVpG0pjBQ
Content-Language: en-us
X-OriginalArrivalTime: 22 Feb 2010 20:12:02.0665 (UTC) FILETIME=[4BFF0D90:01CAB3FB]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

-----Original Message-----
From: Avi Lior [mailto:avi@bridgewatersystems.com] 
Sent: Monday, February 22, 2010 11:32 AM
To: Bernard Aboba; Alan DeKok DeKok
Subject: Review of Radius Guidelines 11

Review of RADIUS Design Guidelines - this is the version that Alan sent to
me earlier.  The one uploaded may have some slight corrections

-------

I am a little confused about the purpose of section 2 RADIUS Data Model and
the purpose of Section 3 Data Model Issues.

Is the intent of section 2 to describe the data model then it should just do
that and move discussions of issues to section 3.

---------------
Section 2:
Please define Standard Space
Please define complex attributes. (you do so much later) or give a reference
to where they are defined.

"The format of this space is defined by individual vendors but the same TLV
encoding used by the standard space..."

Change to:

"The format of the payload of these attributes is defined by individual
vendors but the same TLV encoding...."
-----------------
2.1.1

   "However in order
   to prevent future ambiguities, it is recommended that future RADIUS
   attribute specifications explicitly define newly created data types
   at the beginning of the document, and indicate clearly the data type
   to be used for each attribute."

Do we care about the structure of the document.  I think the issue is that
specification should define newly created data types and indicate clearly
the data type to be used for each attribute.  

Second issue: It seems to me that we are okay with folks creating new data
types in standard space.  I think creation of new data types should be
discouraged right?
-----------------------

" It is worth noting that since RADIUS only supports unsigned integers
   of 32 bits, attributes using signed integer data types or unsigned
   integer types of other sizes will require code changes, and SHOULD be
   avoided."

Why are we talking specifically signed integers?  This is already covered in
the discussion of creating new types.

But since we do bring this up - I suppose that we are talking about this
because this is a common issue.  After all there is no way to represent
negative numbers in RADIUS (or signed integers).  This creates a problem in
general and specific when translating Diameter signed integers to RADIUS.  I
think this document should either remove this paragraph or offer
guidance/solution.
--------------
2.1.2

" For these reasons, the tagging scheme described in RFC 2868 is NOT
   RECOMMENDED for use as a generic grouping mechanism."

What do you mean by generic grouping mechanism?

What about guidance on how to achieve this?

--------------------
Section 2.1.3 Complex Types

Can we not re-write this section to be a little more concise and to the
point? 

Complex types and New Types require code changes in the client and/or the
server.
Code changes creates security risks see security consideration section.

Thus one should avoid creating new types or using complex types.

--------

"However, some standard attributes do not follow this format."
Please give an example of an attribute.

 "Attributes that use sub-fields instead of using a basic data type are
   known as "complex attributes". "

What are sub-fields.
Is an attribute that codefies a bit map a complex attribute?  I think yes.
This is probably the most common complex type that people use.  What
guidance do we offer to designers that need a bit-field?  Each bit is an
attribute?  

---------

"   * it is easier for the user to enter the data as well-known
        types, rather than complex structures;"
This bullet should be removed.  Following good engineer practices of
seperation of concerns and in this case seperation of presentation and the
model (MVC).  We dont want to encourage users to edit raw data as codefied
by the RADIUS protocol.  For example, we dont want user to enter a IPv4
address as a 32bit value or an Address type. But rather as an IP address in
dot notation.

--------
      * it enables additional error checking by leveraging the
        parsing and validation routines for well-known types;

      * it simplifies implementations by eliminating special-case
        attribute-specific parsing.

These two bullets are the same and should be combined.

--------------

One of the fundamental goals of the RADIUS protocol design was to
   allow RADIUS servers to be configured to support new attributes
   without requiring server code changes.  RADIUS server implementations
   typically provide support for basic data types, and define attributes
   in a data dictionary.  This architecture enables a new attribute to
   be supported by the addition of a dictionary entry, without requiring
   other RADIUS server code changes.

This is totally misleading.  We should explain when this is true -- it is
mostly not true today since RADIUS is increasingly supporting dynamic
policies and thus always requires code change to handle the introduction of
any new attribute whether it is an attribute of an existing type or not.

As well the above appears under the complex attribute section 2.1.3 - It is
true also if we were to introduce a new attribute type.
----------

" On the RADIUS client, code changes are typically required in order to
   implement a new attribute. "

A new attribute or a new attribute type or a complex attribute? Which one?
----

  "The RADIUS client typically has to
   compose the attribute dynamically when sending.  When receiving, a
  RADIUS client needs to be able to parse the attribute and carry out
   the requested service.  As a result, a detailed understanding of the
   new attribute is required on clients, and data dictionaries are less
   useful on clients than on servers.

Many of the reasons given here are also true for servers. 

----------

  "The RADIUS server can be configured to send a new static attribute by
   entering its type and data format in the RADIUS server dictionary,
   and then filling in the value within a policy based on the attribute
   name, data type and type-specific value."

The above is only true if the new static attribute is an existing type.
--------

"Code changes can also be required in policy management and in the
   RADIUS server's receive path.  These changes are due to limitations
   in RADIUS server policy languages, which typically only provide for
   limited operations (such as comparisons or arithmetic operations) on
   the existing data types.  Many existing RADIUS policy languages
   typically are not capable of parsing sub-elements, or providing
   sophisticated matching functionality."

What is a RADIUS server policy language?  
RADIUS policy languages are not part of the IETF - the IETF did not conduct
a survey and thus cannot make statements such as these.
Most policy languages i know about contain REgExp that is sophisticated and
can extract any information out of any type. Typicially these have been
first added to be able to parse the RADIUS username.
Remove this paragraph.

------------------
The paragraph starting with "Given these limitations..." seems out of place
since it talks about new types, not complex types....
Then it talks about attribute specific parsing which is not really related
to new types.

Then it talks about the intoduction of new complex data types within RADIUS
attribute specification be avoided.

So now we have a new thing called a "new complex data type".    Dont we mean
new types and complex data types?


Also this paragraph repeats text made earilier  by the bullet points.
-----
"The only other exception to the recommendation against complex types
   is for types that can be treated as opaque data by the RADIUS server."

The assertions that the document is making in this sentence is wrong and we
should remove this statement.  We have seen examples like in RADIUS digest
where we flattened out an attribute to create more then a dozen attributes.
There are other cases as well.  Remove this paragraph.

------

 " If the RADIUS Server simply passes the contents of an attribute to
   some non-RADIUS portion of the network, then the data is opaque, and
   SHOULD be defined to be of type String.  A concrete way of judging
   this requirement is whether or not the attribute definition in the
   RADIUS document contains delineated fields for sub-parts of the data.
   If those fields need to be delineated in RADIUS, then the data is not
   opaque, and it SHOULD be separated into individual RADIUS attributes."


The document is attempting to define a RADIUS Server architecture.  We
should do this properly.  An equally valid architecture is the Diameter one
where the Server is composed of a lower layer defined by RFC 3588 and an
application layer.  We should state that as well.

Here the document gives an impression that the only "application" layer
possible is some foreign entity not part of the RADIUS server - that is just
not true today.

---------
2.1.4
" RADIUS specifications define how an existing service or protocol can
   be provisioned using RADIUS.  Therefore, it is expected that a RADIUS
   attribute specification will reference documents defining the
   protocol or service to be provisioned.  Within the IETF, a RADIUS
   attribute specification SHOULD NOT be used to define the protocol or
   service being provisioned.  New services using RADIUS for
   provisioning SHOULD be defined elsewhere and referenced in the RADIUS
   specification."


I am confused by what we are trying to say in this section.

-------

"New attributes, or new values of existing attributes, SHOULD NOT be
   used to define new RADIUS commands.  RADIUS attributes are intended
   to:"

Shouldn't this be a different section.

----------
2.2

" However, instead of doing this, vendors have defined the following
   non-standard VSA formats:"

The standard allows Vendors to define their VSA as they wish.  How can you
say "non-standard VSA formats"?

Howecer instead of following the recommendation vendors have defiend the
following:

------------

  "All VSA schemes that do not follow the [RFC2865] recommendations are
   NOT RECOMMENDED.  These non-standard formats will typically not be
   implementable without RADIUS server code changes.  This includes all
   the above formats, as well as Vendor types of more than 8 bits,
   vendor lengths of less than 8 bits, vendor lengths of more than 8
   bits and Vendor-Specific contents that are not in Type-Length-Value
   format."

Its up to the vendors or SDO to decide and the specification allows for
that.  RFC2865 makes a recommendation and we should just leave it at that.
You can state the problems that this may create but I think the document is
out of bounds when it states that it is not recommended.  2865 makes a
recommendation and that is enough.

---------------

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

What do you mean by on-the-wire format?  
     
---------
Section 3 is not only about data model issues.

We need a better name.
-----------

3.3

Why are we repeating the recommendations fo 5080.  Just remind people that
they need to read it.

---------

Section 5

"Where new RADIUS attributes encapsulate complex data types, or transport
opaque data, the security considerations discussed in Sectiont 2.1.4 SHOULD
be addressed"

The contents of 2.1.4 was moved to the security section
-----
5.1

The title should be Complex Types and New Data types no?

The text in this section should be fixed as well.  Sometimes it refers to
one where the other is also applicable.

-------

   "Any system consuming opaque data that originates from a RADIUS system
   SHOULD be properly isolated from that RADIUS system, and SHOULD run
   with minimal privileges.  Any potential vulnerabilities in the non-
   RADIUS system will then have minimal impact on the security of the
   system as a whole."

fear mongering a bit here and not true???  I can inject code in the opaque
data which could cause the system to run at higher privelages. Can we make
more concrete recommendations such as use care to validate the opaque data
for example to ensure no buffer overruns etc etc....It is pretty standard
practice to validate data coming from potentially untrusted sources or that
can be compromized along the way.
 


Appendix A

A.1

Simple Data vs Radius Data types.  They are the same no?  We need to use the
term consistantly throughout the document.

A.1.2

*Complex data types...which the RADIUS servers are expected to parse..."

I think you need to explain the model here.  This is a common theme
throughout the document.  What is a RADIUS server?

A.3





--
to unsubscribe send a message to 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 Feb 23 06:33:07 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FD2A28C1ED for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 06:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.178
X-Spam-Level: 
X-Spam-Status: No, score=0.178 tagged_above=-999 required=5 tests=[AWL=0.591, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, 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 HBBnWX7-MBXW for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 06:33:06 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 463D628C125 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 06:33:06 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Njvno-00009i-O8 for radiusext-data0@psg.com; Tue, 23 Feb 2010 14:31:56 +0000
Received: from [156.54.233.200] (helo=GRFEDG701BA020.telecomitalia.it) by psg.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.71 (FreeBSD)) (envelope-from <roberta.maglione@telecomitalia.it>) id 1Njvnl-00009F-2b for radiusext@ops.ietf.org; Tue, 23 Feb 2010 14:31:53 +0000
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 23 Feb 2010 15:31:51 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Tue, 23 Feb 2010 15:31:50 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
CC: Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Tue, 23 Feb 2010 15:31:49 +0100
Subject: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Index: Acq0dWLIIt4q+HckQ/ehIwN9aQMNRQAEzSmw
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi All,
     we have just posted a new draft about RADIUS attributes for IPv6 stati=
stics:
http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
Your comments are welcome.

Thanks,
Regards,
Roberta

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
Sent: Tuesday, February 23, 2010 11:43 AM
To: Maglione Roberta
Cc: suresh.krishnan@ericsson.com; alan.kavanagh@ericsson.com; varga.balazs@=
telekom.hu
Subject: New Version Notification for draft-maglione-radext-ipv6-acct-exten=
sions-00


A new version of I-D, draft-maglione-radext-ipv6-acct-extensions-00.txt has=
 been successfuly submitted by Roberta Maglione and posted to the IETF repo=
sitory.

Filename:        draft-maglione-radext-ipv6-acct-extensions
Revision:        00
Title:           RADIUS Accounting Extensions for IPv6
Creation_date:   2010-02-23
WG ID:           Independent Submission
Number_of_pages: 10

Abstract:
This document describes additional RADIUS attributes to be used for
collecting IPv6 statistics in RADIUS Accounting messages.



The IETF Secretariat.



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, 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  Tue Feb 23 09:39:04 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B28E28C32C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 09:39:04 -0800 (PST)
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 GSPhurkcx30o for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 09:39:03 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4187928C341 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 09:39:03 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NjyiH-000Nkw-Al for radiusext-data0@psg.com; Tue, 23 Feb 2010 17:38:25 +0000
Received: from [216.82.241.99] (helo=mail51.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1NjyiD-000NkQ-SI for radiusext@ops.ietf.org; Tue, 23 Feb 2010 17:38:22 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-10.tower-51.messagelabs.com!1266946699!75234329!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 13717 invoked from network); 23 Feb 2010 17:38:20 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-10.tower-51.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2010 17:38:20 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Tue, 23 Feb 2010 12:38:19 -0500
From: Avi Lior <avi@bridgewatersystems.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Tue, 23 Feb 2010 12:38:18 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Index: Acq0rvzFN72H/re8Rni0tRhA8+Eeyg==
Message-ID: <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi,'

What makes you say that the existing accounting attributes for octet/packet=
 counts are for IPv4 ?

Wouldn't the IP address contained in the IP session be sufficient to create=
 the context for the accounting message?


On 23-02-2010, at 06:31 , Maglione Roberta wrote:

> Hi All,
>     we have just posted a new draft about RADIUS attributes for IPv6 stat=
istics:
> http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
> Your comments are welcome.
>=20
> Thanks,
> Regards,
> Roberta
>=20
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Tuesday, February 23, 2010 11:43 AM
> To: Maglione Roberta
> Cc: suresh.krishnan@ericsson.com; alan.kavanagh@ericsson.com; varga.balaz=
s@telekom.hu
> Subject: New Version Notification for draft-maglione-radext-ipv6-acct-ext=
ensions-00
>=20
>=20
> A new version of I-D, draft-maglione-radext-ipv6-acct-extensions-00.txt h=
as been successfuly submitted by Roberta Maglione and posted to the IETF re=
pository.
>=20
> Filename:        draft-maglione-radext-ipv6-acct-extensions
> Revision:        00
> Title:           RADIUS Accounting Extensions for IPv6
> Creation_date:   2010-02-23
> WG ID:           Independent Submission
> Number_of_pages: 10
>=20
> Abstract:
> This document describes additional RADIUS attributes to be used for
> collecting IPv6 statistics in RADIUS Accounting messages.
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20
>=20
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle p=
ersone indicate. La diffusione, copia o qualsiasi altra azione derivante da=
lla conoscenza di queste informazioni sono rigorosamente vietate. Qualora a=
bbiate ricevuto questo documento per errore siete cortesemente pregati di d=
arne immediata comunicazione al mittente e di provvedere alla sua distruzio=
ne, Grazie.
>=20
> This e-mail and any attachments is confidential and may contain privilege=
d information intended for the addressee(s) only. Dissemination, copying, p=
rinting or use by anybody else is unauthorised. If you are not the intended=
 recipient, please delete this message and any attachments and advise the s=
ender by return e-mail, Thanks.
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


--
to unsubscribe send a message to 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 Feb 23 12:19:13 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76B283A8428 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 12:19:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.518
X-Spam-Level: 
X-Spam-Status: No, score=-1.518 tagged_above=-999 required=5 tests=[AWL=-1.081, 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 McvUzorTk1-l for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 12:19:12 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4A63E3A848C for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 12:19:12 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nk1Bc-000FvT-6h for radiusext-data0@psg.com; Tue, 23 Feb 2010 20:16:52 +0000
Received: from [213.165.64.20] (helo=mail.gmx.net) by psg.com with smtp (Exim 4.71 (FreeBSD)) (envelope-from <Hannes.Tschofenig@gmx.net>) id 1Nk1BV-000FuQ-NX for radiusext@ops.ietf.org; Tue, 23 Feb 2010 20:16:48 +0000
Received: (qmail invoked by alias); 23 Feb 2010 20:07:50 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO 4FIL42860) [88.115.222.204] by mail.gmx.net (mp071) with SMTP; 23 Feb 2010 21:07:50 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18W+Sh67TIWTYluNZGSn8vSKBgTQ2ErOFkAeNWFQE 4h6RRTi24tKg7y
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: <radiusext@ops.ietf.org>
Subject: My Suggestions regarding the RADIUS Design Guidelines Document
Date: Tue, 23 Feb 2010 22:07:04 +0200
Message-ID: <000001cab4c3$c7ca5970$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acq0w8SHLK8n3aorSWOrkCaPAkSXIg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.56000000000000005
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

-- I believe this mail never made it to the list (and I hope I got the right
version)

Hi all, 

I was asked what specifically has to be changed in the document in order to
address my comments. Here is a short summary: 

1) Shorten Section 2 and Section 3 considerably. I believe that readability
can be improved by shortening the text. Funny enough the right text is
already in the draft, namely in the appendix. I am proposing a new structure
at the bottom of this mail. 

2) Be precise what you mean by "basic" vs. "complex" attribute

Section 2 is quite fuzzy in it's description. I would instead re-use the
text you have in the appendix. 

Ciao
Hannes

-----------------------

2.  RADIUS Data Model

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

Unlike SNMP, first defined in [RFC1157] and [RFC1155], RADIUS does not
define a formal data definition language.  The data type of RADIUS
attributes is not transported on the wire.  Rather, the data type of a
RADIUS attribute is fixed when an attribute is defined.

To explain the implications of this early RADIUS design decision we
distinguish two types of attributes, namely 'basic' and 'complex'. Basic
attributes are those encapsulated in a [RFC2865] format RADIUS attribute, or
in a [RFC2865] format RADIUS VSA that uses one of the existing RADIUS data
types:

 * << Copy the text from Section A.1.1 in here. >> 

All other attributes are referred as complex attributes. 

When designing new RADIUS attributes a protocol designer has to ask himself
/ herself the following two questions: 

 (a) Will this attribute require code changes at the RADIUS server when sent
from the RADIUS server to the RADIUS client? Typically, data than can be
encoded using basic data types will not require code changes to a RADIUS
server. 

 (b) Will this attribute require code changes at the RADIUS server when
received by the RADIUS server?  

Note: It is assumed that code changes to the RADIUS client are always
necessary to implement the additional functionality offered by the newly
defined RADIUS attribute(s).
 
Many RADIUS server implementations utilize a data dictionary to recognize
data types and also offer a simple policy language that only provides
limited operations (such as comparisons or arithmetic operations) on these
basic data types. Many existing RADIUS policy languages typically are not
capable of parsing sub-elements, or providing sophisticated matching
functionality.

Ideally, a protocol designer might want to write a specification that does
not require code changes to most exist RADIUS servers. Sometimes, however,
code changes will be unavoidable and they lead to additional implementation
efforts, more testing overhead and additional security vulernabilities as
more lines of code lead to more potential vulnerabilities. It is RECOMMENDED
that protocol designers briefly describe their expected processing model and
in particular if they expect RADIUS server changes (for example due to the
need for the RADIUS server to analyse incoming RADIUS attributes and to
return responses based on the presence of a more sophisticated policy
language). 

>>> I wouldn't actually say too much more here in this section. I don't have
a good suggestion for placing the text about the polymorphic attributes. <<<


3. Standard vs. Vendor-specific Attribute Space

>>> discussion about standard vs. vendor-specific attribute space. 


--
to unsubscribe send a message to 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 Feb 23 12:20:54 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44EB63A8469 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 12:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.232
X-Spam-Level: 
X-Spam-Status: No, score=0.232 tagged_above=-999 required=5 tests=[AWL=-1.688, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdNpAeyvTrrL for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 12:20:53 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4EA943A840A for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 12:20:53 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nk1CO-000G0b-Nl for radiusext-data0@psg.com; Tue, 23 Feb 2010 20:17:40 +0000
Received: from [65.55.116.26] (helo=blu0-omc1-s15.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Nk1CL-000Fzt-4I for radiusext@ops.ietf.org; Tue, 23 Feb 2010 20:17:37 +0000
Received: from BLU137-DS3 ([65.55.116.9]) by blu0-omc1-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Feb 2010 12:17:36 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Date: Tue, 23 Feb 2010 12:17:39 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CAB482.336844E0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq0xT8uBPxYy20STV+Ko3u61xMO7g==
Content-Language: en-us
x-cr-hashedpuzzle: ANZd A8Cx BE8z BQK1 CgER Cnu5 C9v7 ELoi FGQw FiBd GsBg ITca JMbc KdYu KovZ LJr8;1;cgBhAGQAaQB1AHMAZQB4AHQAQABvAHAAcwAuAGkAZQB0AGYALgBvAHIAZwA=;Sosha1_v1;7;{64A7544C-F5CA-4FE4-B65A-8428CA208870};YgBlAHIAbgBhAHIAZABhAEAAbQBpAGMAcgBvAHMAbwBmAHQALgBjAG8AbQA=;Tue, 23 Feb 2010 20:17:39 GMT;QwBhAGwAbAAgAGYAbwByACAAYQBkAG8AcAB0AGkAbwBuACAAbwBmACAAIgBSAEEARABJAFUAUwAgAEEAdAB0AHIAaQBiAHUAdABlAHMAIABmAG8AcgAgAEkAUAB2ADYAIABBAGMAYwBlAHMAcwAgAE4AZQB0AHcAbwByAGsAcwAiAA==
x-cr-puzzleid: {64A7544C-F5CA-4FE4-B65A-8428CA208870}
X-OriginalArrivalTime: 23 Feb 2010 20:17:36.0510 (UTC) FILETIME=[3D6581E0:01CAB4C5]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_000A_01CAB482.336844E0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

During the RADEXT Virtual Interim, we discussed adoption of "RADIUS
Attributes for IPv6 Access Networks" as a RADEXT WG work item. 

 

We would now like to request mailing list confirmation of the decision to
adopt this draft. 

 

The document is available here:

http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02

 

If you have an opinion on the adoption  of this document as a RADEXT WG work
item, please reply to this email. 

 

 

 


------=_NextPart_000_000A_01CAB482.336844E0
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:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal>During the RADEXT Virtual Interim, we discussed =
adoption of &quot;RADIUS
Attributes for IPv6 Access Networks&quot; as a RADEXT WG work item. =
<o:p></o:p></p>

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

<p class=3DMsoNormal>We would now like to request mailing list =
confirmation of
the decision to adopt this draft. <o:p></o:p></p>

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

<p class=3DMsoNormal>The document is available here:<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-=
access-02<o:p></o:p></p>

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

<p class=3DMsoNormal>If you have an opinion on the adoption&nbsp; of =
this
document as a RADEXT WG work item, please reply to this email. =
<o:p></o:p></p>

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

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

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

</div>

</body>

</html>

------=_NextPart_000_000A_01CAB482.336844E0--

--
to unsubscribe send a message to 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 Feb 23 12:44:20 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 549D028C103 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 12:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.432
X-Spam-Level: 
X-Spam-Status: No, score=-5.432 tagged_above=-999 required=5 tests=[AWL=-0.937, 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 NetEeOdwCzCo for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 12:44:19 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3C78928C0D9 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 12:44:19 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nk1bA-000If7-HF for radiusext-data0@psg.com; Tue, 23 Feb 2010 20:43:16 +0000
Received: from [198.24.6.3] (helo=imr2.ericy.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <suresh.krishnan@ericsson.com>) id 1Nk1b7-000Ien-4E for radiusext@ops.ietf.org; Tue, 23 Feb 2010 20:43:13 +0000
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id o1NKjEcG013603; Tue, 23 Feb 2010 14:45:15 -0600
Received: from [142.133.10.113] (147.117.20.212) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.1.375.2; Tue, 23 Feb 2010 15:43:10 -0500
Message-ID: <4B843CD2.8080406@ericsson.com>
Date: Tue, 23 Feb 2010 15:38:42 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Maglione Roberta <roberta.maglione@telecomitalia.it>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, "=?ISO-8859-1?Q?Varga_Bal=E1?= =?ISO-8859-1?Q?zs?=" <varga.balazs@telekom.hu>
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com>
In-Reply-To: <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi Avi,
   Thanks for your comments.

On 10-02-23 12:38 PM, Avi Lior wrote:
> Hi,'
> 
> What makes you say that the existing accounting attributes for octet/packet counts are for IPv4 ?

You are right. They are not. They are not protocol specific. We are 
looking to define separate counters for IPv6. We will change the wording 
in the draft to correspond to this.

> 
> Wouldn't the IP address contained in the IP session be sufficient to create the context for the accounting message?

This will require us to send two different messages (one for IPv6 only 
and one for all protocols combined together).

Thanks
Suresh

--
to unsubscribe send a message to 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 Feb 23 13:20:14 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9128B28C0DF for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 13:20:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.361
X-Spam-Level: 
X-Spam-Status: No, score=-1.361 tagged_above=-999 required=5 tests=[AWL=-0.866, 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 ZaXxVGuOG6mv for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 13:20:12 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id CFA0E28C1A8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 13:20:10 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nk2Aa-000MuN-32 for radiusext-data0@psg.com; Tue, 23 Feb 2010 21:19:52 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1Nk2AW-000Mtp-LM for radiusext@ops.ietf.org; Tue, 23 Feb 2010 21:19:48 +0000
Message-ID: <4B844673.1080206@deployingradius.com>
Date: Tue, 23 Feb 2010 22:19:47 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
CC: radiusext@ops.ietf.org
Subject: Re: My Suggestions regarding the RADIUS Design Guidelines Document
References: <000001cab4c3$c7ca5970$04ffa8c0@nsnintra.net>
In-Reply-To: <000001cab4c3$c7ca5970$04ffa8c0@nsnintra.net>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hannes Tschofenig wrote:
> I was asked what specifically has to be changed in the document in order to
> address my comments. Here is a short summary: 
> 
> 1) Shorten Section 2 and Section 3 considerably. I believe that readability
> can be improved by shortening the text. Funny enough the right text is
> already in the draft, namely in the appendix. I am proposing a new structure
> at the bottom of this mail. 

  On a quick scan, it looks good.

> 2) Be precise what you mean by "basic" vs. "complex" attribute

  "basic" == "defined (mostly) in an existing RFC"

  "complex" == "everything else".

> Section 2 is quite fuzzy in it's description. I would instead re-use the
> text you have in the appendix. 

  OK.

  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 Feb 23 14:03:20 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 389AB3A8253 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 14:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.459
X-Spam-Level: 
X-Spam-Status: No, score=-5.459 tagged_above=-999 required=5 tests=[AWL=-0.964, 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 FC4yB6RDfcbP for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 14:03:19 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E15E228C36C for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 14:03:18 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nk2qr-0001Wb-BA for radiusext-data0@psg.com; Tue, 23 Feb 2010 22:03:33 +0000
Received: from [216.82.249.147] (helo=mail29.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1Nk2qn-0001WE-T1 for radiusext@ops.ietf.org; Tue, 23 Feb 2010 22:03:30 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-6.tower-29.messagelabs.com!1266962607!44453574!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 9413 invoked from network); 23 Feb 2010 22:03:28 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-6.tower-29.messagelabs.com with RC4-SHA encrypted SMTP; 23 Feb 2010 22:03:28 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Tue, 23 Feb 2010 17:03:27 -0500
From: Avi Lior <avi@bridgewatersystems.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
CC: Maglione Roberta <roberta.maglione@telecomitalia.it>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Tue, 23 Feb 2010 17:03:25 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq01AapUUCqFjABR1CW7ENRLjZowg==
Message-ID: <1456B38F-1724-4C35-BCE6-8E54E1A79D9E@bridgewatersystems.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com> <4B843CD2.8080406@ericsson.com>
In-Reply-To: <4B843CD2.8080406@ericsson.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Why do you need separate counters for IPv6?

Is it because you want to have different counters for different IP technolo=
gy at the same time in the accounting stream?

If yes there are other problems with that approach.  Accounting is used for=
 both volume and time accounting.  While having distinct volume counters fo=
r one technology may solve the volume aspect it does not address the time a=
spect.  Consider the fact that even if you have both IPv4 and IPv6 enabled =
one may start at a different time then the other and one may stop at a diff=
erent time then the other.

There are other information elements that are accounted for that may be spe=
cific to a particular IP technology and not the other.

As well, a user may have multiple IPv4 addresses and multiple IPv6 addresse=
s.

So I am concerned that you are not really addressing all the issues. =20

Separate accounting streams per IP session solves these problems.

What is the problem with having separate accounting streams per IP session?

> Hi Avi,
>   Thanks for your comments.
>=20
> On 10-02-23 12:38 PM, Avi Lior wrote:
>> Hi,'
>>=20
>> What makes you say that the existing accounting attributes for octet/pac=
ket counts are for IPv4 ?
>=20
> You are right. They are not. They are not protocol specific. We are=20
> looking to define separate counters for IPv6. We will change the wording=
=20
> in the draft to correspond to this.
>=20
>>=20
>> Wouldn't the IP address contained in the IP session be sufficient to cre=
ate the context for the accounting message?
>=20
> This will require us to send two different messages (one for IPv6 only=20
> and one for all protocols combined together).
>=20
> Thanks
> Suresh


--
to unsubscribe send a message to 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 Feb 23 18:59:20 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ADFD3A829F for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 18:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.966
X-Spam-Level: 
X-Spam-Status: No, score=-0.966 tagged_above=-999 required=5 tests=[AWL=-0.472, 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 VQXyrCNMYjUo for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 18:59:19 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 49C5F3A7F0A for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 18:59:19 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nk7Q6-0003jT-JT for radiusext-data0@psg.com; Wed, 24 Feb 2010 02:56:14 +0000
Received: from [65.55.116.22] (helo=blu0-omc1-s11.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Nk7Q3-0003ip-6c for radiusext@ops.ietf.org; Wed, 24 Feb 2010 02:56:11 +0000
Received: from BLU137-DS15 ([65.55.116.7]) by blu0-omc1-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Feb 2010 18:56:10 -0800
X-Originating-IP: [131.107.0.104]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS15DE29B915A016EA5984F093410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Internet Draft Cut-off Dates Reminder (fwd)
Date: Tue, 23 Feb 2010 18:56:10 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_047F_01CAB4B9.DD283670"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq0/OsOsfaxAXO+St+/+lUubkIr6A==
Content-Language: en-us
X-OriginalArrivalTime: 24 Feb 2010 02:56:10.0810 (UTC) FILETIME=[EB6E19A0:01CAB4FC]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

------=_NextPart_000_047F_01CAB4B9.DD283670
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit





From: IETF Secretariat <ietf-secretariat
<mailto:ietf-secretariat%20at%20ietf.org>  at ietf.org>

Date: February 22, 2010 9:00:01 PM CEST

To: ietf-announce at ietf.org <mailto:ietf-announce%20at%20ietf.org> 

Subject: Internet Draft Cut-off Dates Reminder 

 


This is a reminder that the Internet Draft Cut-off Dates are approaching.


The initial draft (version -00) cut-off date is Monday, March 1, 2010. 
These submissions are due by 17:00 PST (01:00 Tuesday, March 2 UTC).

The Internet Draft final submission (version -01 and up) cut-off is
Monday, March 8, 2010 at 17:00 PST (01:00 Tuesday, March 2 UTC).

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/idst/upload.cgi
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

 


------=_NextPart_000_047F_01CAB4B9.DD283670
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.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>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>From: </span></b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif"'>IETF
Secretariat &lt;<a =
href=3D"mailto:ietf-secretariat%20at%20ietf.org">ietf-secretariat
at ietf.org</a>&gt;</span><o:p></o:p></p>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>Date: </span></b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif"'>February
22, 2010 9:00:01 PM CEST</span><o:p></o:p></p>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>To: </span></b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif"'><a
href=3D"mailto:ietf-announce%20at%20ietf.org">ietf-announce at =
ietf.org</a></span><o:p></o:p></p>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>Subject: </span></b><b><span =
style=3D'font-size:10.5pt;font-family:
"Helvetica","sans-serif"'>Internet Draft Cut-off Dates Reminder<span
class=3Dapple-converted-space>&nbsp;</span></span></b><o:p></o:p></p>

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

<p class=3DMsoNormal><br>
This is a reminder that the Internet Draft Cut-off Dates are =
approaching.<br>
<br>
<br>
The initial draft (version -00) cut-off date is Monday, March 1, 2010. =
<br>
These submissions are due by 17:00 PST (01:00 Tuesday, March 2 UTC).<br>
<br>
The Internet Draft final submission (version -01 and up) cut-off is<br>
Monday, March 8, 2010 at 17:00 PST (01:00 Tuesday, March 2 UTC).<br>
<br>
All drafts can be uploaded using the ID submission tool located =
here:<br>
<a =
href=3D"https://datatracker.ietf.org/idst/upload.cgi">https://datatracker=
.ietf.org/idst/upload.cgi</a><br>
_______________________________________________<br>
IETF-Announce mailing list<br>
IETF-Announce at ietf.org<br>
https://www.ietf.org/mailman/listinfo/ietf-announce<o:p></o:p></p>

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

</div>

</body>

</html>

------=_NextPart_000_047F_01CAB4B9.DD283670--

--
to unsubscribe send a message to 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 Feb 23 22:07:45 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC13E28C1F8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 22:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.962
X-Spam-Level: 
X-Spam-Status: No, score=-0.962 tagged_above=-999 required=5 tests=[AWL=-0.468, 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 fyDFAKvhWPxf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 22:07:43 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id AC3D33A7B36 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 22:07:41 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkAOS-000Lr7-RH for radiusext-data0@psg.com; Wed, 24 Feb 2010 06:06:44 +0000
Received: from [65.55.116.26] (helo=blu0-omc1-s15.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NkAON-000Lqa-Kc for radiusext@ops.ietf.org; Wed, 24 Feb 2010 06:06:39 +0000
Received: from BLU137-W23 ([65.55.116.9]) by blu0-omc1-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Feb 2010 22:06:39 -0800
Message-ID: <BLU137-W238F693E6D06B45058E0C393410@phx.gbl>
Content-Type: multipart/alternative; boundary="_3c60324e-b72b-4e3b-9588-a8fab915295b_"
X-Originating-IP: [24.19.160.219]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: PROTO writeup for Status-Server document
Date: Tue, 23 Feb 2010 22:06:39 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Feb 2010 06:06:39.0069 (UTC) FILETIME=[873408D0:01CAB517]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_3c60324e-b72b-4e3b-9588-a8fab915295b_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


PROTO Writeup for draft-ietf-radext-status-server
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
http://tools.ietf.org/html/draft-ietf-radext-status-server
=20
   (1.a)  Who is the Document Shepherd for this document?  Has the
      Document Shepherd personally reviewed this version of the document
      and=2C in particular=2C does he or she believe this version is ready
      for forwarding to the IESG for publication?
=20
Bernard Aboba is the document shepherd.  I have personally reviewed
the document=2C and believe it is ready for publication as an Informational
RFC.=20
=20
   (1.b)  Has the document had adequate review both from key members of
      the interested community and others?  Does the Document Shepherd
      have any concerns about the depth or breadth of the reviews that
      have been performed?
=20
The goal of this document is to specify the Status-Server functionality
that has been implemented in the field.  Therefore=2C the major concern
is whether the document reflects existing implementations.  So
far the specification has been reviewed by the implementers of the
RADIATOR and FreeRADIUS servers=2C both of which support Status-Server.
This would appear to address the review depth issue.=20

   (1.c)  Does the Document Shepherd have concerns that the document
      needs more review from a particular or broader perspective=2C e.g.=2C
      security=2C operational complexity=2C someone familiar with AAA=2C
      internationalization or XML?
=20
No.=20
=20
   (1.d)  Does the Document Shepherd have any specific concerns or
      issues with this document that the Responsible Area Director
      and/or the IESG should be aware of?  For example=2C perhaps he or
      she is uncomfortable with certain parts of the document=2C or has
      concerns whether there really is a need for it.  In any event=2C if
      the interested community has discussed those issues and has
      indicated that it still wishes to advance the document=2C detail
      those concerns here.
=20
Status-Server is being published as an Informational RFC due to
limitations of the design which are documented in the Applicability
section.  However=2C the goal is largely to document what has
been implemented rather than trying to re-design it.=20

   (1.e)  How solid is the consensus of the interested community behind
      this document?  Does it represent the strong concurrence of a few
      individuals=2C with others being silent=2C or does the interested
      community as a whole understand and agree with it?
=20
There is consensus within the RADEXT WG to publish the document as
an Informational RFC. =20
=20
   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
      discontent?  If so=2C please summarise the areas of conflict in
      separate email messages to the Responsible Area Director.  (It
      should be in a separate email because this questionnaire is
      entered into the ID Tracker.)
=20
No.=20
=20
   (1.g)  Has the Document Shepherd personally verified that the
      document satisfies all ID nits?  (See
      http://www.ietf.org/ID-Checklist.html and
      http://tools.ietf.org/tools/idnits/).  Boilerplate checks are not
      enough=3B this check needs to be thorough.  Has the document met all
      formal review criteria it needs to=2C such as the MIB Doctor=2C media
      type and URI type reviews?
=20
The document is clean in idnits:

idnits 2.12.00=20

tmp/draft-ietf-radext-status-server-06.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  -------------------------------------------------------------------------=
---

     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: Informational
  -------------------------------------------------------------------------=
---

     No issues found here.

     No nits found.
---------------------------------------------------------------------------=
-----
=20
   (1.h)  Has the document split its references into normative and
      informative?  Are there normative references to documents that are
      not ready for advancement or are otherwise in an unclear state?
      If such normative references exist=2C what is the strategy for their
      completion?  Are there normative references that are downward
      references=2C as described in [RFC3967]?  If so=2C list these downwar=
d
      references to support the Area Director in the Last Call procedure
      for them [RFC3967].
=20
The references in the document have been split into normative and
informative.=20

Normative references are all stable documents published as RFCs.
=20
   (1.i)  Has the Document Shepherd verified that the document IANA
      consideration section exists and is consistent with the body of
      the document?  If the document specifies protocol extensions=2C are
      reservations requested in appropriate IANA registries?  Are the
      IANA registries clearly identified?  If the document creates a new
      registry=2C does it define the proposed initial contents of the
      registry and an allocation procedure for future registrations?
      Does it suggested a reasonable name for the new registry?  See
      [I-D.narten-iana-considerations-rfc2434bis].  If the document
      describes an Expert Review process has Shepherd conferred with the
      Responsible Area Director so that the IESG can appoint the needed
      Expert during the IESG Evaluation?
=20
The IANA considerations section (7) exists=2C and is consistent with
the body of the document.  Note that no new registries are created
nor does the document require assignment of any new protocol parameters=2C=
=20
since the Status-Server Code (12) was assigned in RFC 2865.=20
=20
   (1.j)  Has the Document Shepherd verified that sections of the
      document that are written in a formal language=2C such as XML code=2C
      BNF rules=2C MIB definitions=2C etc.=2C validate correctly in an
      automated checker?

Not applicable.
=20
   (1.k)  The IESG approval announcement includes a Document
      Announcement Write-Up.  Please provide such a Document
      Announcement Writeup?  Recent examples can be found in the
      "Action" announcements for approved documents.  The approval
      announcement contains the following sections:
=20
      Technical Summary

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

The RADEXT WG elected to recommend this document for publication
as an Informational RFC rather than as a standards-Track RFC due
to concerns about problems with deployed implementations.  The
fixes recommended within the document are compatible with=20
existing servers that receive Status-Server packets=2C but impose new
security requirements on clients that send Status-Server packets.
=20
      Document Quality
=20
The document has been reviewed by IETF RADEXT WG members.=20
An expert review has been carried out by Ignacio Goyret.=20
=20
Status-Server has been implemented by multiple vendors=2C=20
including RADIATOR=2C FreeRADIUS and Cistron.=20
=20
      Personnel
=20
Bernard Aboba is the document shepherd for this document.=20
Dan Romascanu is the responsible AD.=20










 		 	   		  =

--_3c60324e-b72b-4e3b-9588-a8fab915295b_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
PROTO Writeup for draft-ietf-radext-status-server<br>=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>&nbsp=3B<br>http://t=
ools.ietf.org/html/draft-ietf-radext-status-server<br>&nbsp=3B<br>&nbsp=3B&=
nbsp=3B (1.a)&nbsp=3B Who is the Document Shepherd for this document?&nbsp=
=3B Has the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Document Shepherd p=
ersonally reviewed this version of the document<br>&nbsp=3B&nbsp=3B&nbsp=3B=
&nbsp=3B&nbsp=3B and=2C in particular=2C does he or she believe this versio=
n is ready<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B for forwarding to th=
e IESG for publication?<br>&nbsp=3B<br>Bernard Aboba is the document shephe=
rd.&nbsp=3B I have personally reviewed<br>the document=2C and believe it is=
 ready for publication as an Informational<br>RFC. <br>&nbsp=3B<br>&nbsp=3B=
&nbsp=3B (1.b)&nbsp=3B Has the document had adequate review both from key m=
embers of<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B the interested commun=
ity and others?&nbsp=3B Does the Document Shepherd<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B have any concerns about the depth or breadth of the rev=
iews that<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B have been performed?<=
br>&nbsp=3B<br>The goal of this document is to specify the Status-Server fu=
nctionality<br>that has been implemented in the field.&nbsp=3B Therefore=2C=
 the major concern<br>is whether the document reflects existing implementat=
ions.&nbsp=3B So<br>far the specification has been reviewed by the implemen=
ters of the<br>RADIATOR and FreeRADIUS servers=2C both of which support Sta=
tus-Server.<br>This would appear to address the review depth issue. <br><br=
>&nbsp=3B&nbsp=3B (1.c)&nbsp=3B Does the Document Shepherd have concerns th=
at the document<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B needs more revi=
ew from a particular or broader perspective=2C e.g.=2C<br>&nbsp=3B&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B security=2C operational complexity=2C someone famil=
iar with AAA=2C<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B internationaliz=
ation or XML?<br>&nbsp=3B<br>No. <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.d)&nbs=
p=3B Does the Document Shepherd have any specific concerns or<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B issues with this document that the Responsib=
le Area Director<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B and/or the IES=
G should be aware of?&nbsp=3B For example=2C perhaps he or<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B she is uncomfortable with certain parts of the =
document=2C or has<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B concerns whe=
ther there really is a need for it.&nbsp=3B In any event=2C if<br>&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B the interested community has discussed thos=
e issues and has<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B indicated that=
 it still wishes to advance the document=2C detail<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B those concerns here.<br>&nbsp=3B<br>Status-Server is be=
ing published as an Informational RFC due to<br>limitations of the design w=
hich are documented in the Applicability<br>section.&nbsp=3B However=2C the=
 goal is largely to document what has<br>been implemented rather than tryin=
g to re-design it. <br><br>&nbsp=3B&nbsp=3B (1.e)&nbsp=3B How solid is the =
consensus of the interested community behind<br>&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B this document?&nbsp=3B Does it represent the strong concurren=
ce of a few<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B individuals=2C with=
 others being silent=2C or does the interested<br>&nbsp=3B&nbsp=3B&nbsp=3B&=
nbsp=3B&nbsp=3B community as a whole understand and agree with it?<br>&nbsp=
=3B<br>There is consensus within the RADEXT WG to publish the document as<b=
r>an Informational RFC.&nbsp=3B <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.f)&nbsp=
=3B Has anyone threatened an appeal or otherwise indicated extreme<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B discontent?&nbsp=3B If so=2C please sum=
marise the areas of conflict in<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
 separate email messages to the Responsible Area Director.&nbsp=3B (It<br>&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B should be in a separate email becau=
se this questionnaire is<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B entere=
d into the ID Tracker.)<br>&nbsp=3B<br>No. <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B=
 (1.g)&nbsp=3B Has the Document Shepherd personally verified that the<br>&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B document satisfies all ID nits?&nbsp=
=3B (See<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B http://www.ietf.org/ID=
-Checklist.html and<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B http://tool=
s.ietf.org/tools/idnits/).&nbsp=3B Boilerplate checks are not<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B enough=3B this check needs to be thorough.&n=
bsp=3B Has the document met all<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
 formal review criteria it needs to=2C such as the MIB Doctor=2C media<br>&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B type and URI type reviews?<br>&nbsp=
=3B<br>The document is clean in idnits:<br><br>idnits 2.12.00 <br><br>tmp/d=
raft-ietf-radext-status-server-06.txt:<br><br>&nbsp=3B Checking boilerplate=
 required by RFC 5378 and the IETF Trust (see<br>&nbsp=3B http://trustee.ie=
tf.org/license-info):<br>&nbsp=3B -----------------------------------------=
-----------------------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
 No issues found here.<br><br>&nbsp=3B Checking nits according to http://ww=
w.ietf.org/ietf/1id-guidelines.txt:<br>&nbsp=3B ---------------------------=
-------------------------------------------------<br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B No issues found here.<br><br>&nbsp=3B Checking nits accordin=
g to http://www.ietf.org/ID-Checklist.html:<br>&nbsp=3B -------------------=
---------------------------------------------------------<br><br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B No issues found here.<br><br>&nbsp=3B Miscellaneous =
warnings:<br>&nbsp=3B -----------------------------------------------------=
-----------------------<br><br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issu=
es found here.<br><br>&nbsp=3B Checking references for intended status: Inf=
ormational<br>&nbsp=3B ----------------------------------------------------=
------------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issues =
found here.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No nits found.<br>-----=
---------------------------------------------------------------------------=
<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.h)&nbsp=3B Has the document split its r=
eferences into normative and<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B in=
formative?&nbsp=3B Are there normative references to documents that are<br>=
&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B not ready for advancement or are o=
therwise in an unclear state?<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B I=
f such normative references exist=2C what is the strategy for their<br>&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B completion?&nbsp=3B Are there normativ=
e references that are downward<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B =
references=2C as described in [RFC3967]?&nbsp=3B If so=2C list these downwa=
rd<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B references to support the Ar=
ea Director in the Last Call procedure<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&=
nbsp=3B for them [RFC3967].<br>&nbsp=3B<br>The references in the document h=
ave been split into normative and<br>informative. <br><br>Normative referen=
ces are all stable documents published as RFCs.<br>&nbsp=3B<br>&nbsp=3B&nbs=
p=3B (1.i)&nbsp=3B Has the Document Shepherd verified that the document IAN=
A<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B consideration section exists =
and is consistent with the body of<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B the document?&nbsp=3B If the document specifies protocol extensions=2C =
are<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B reservations requested in a=
ppropriate IANA registries?&nbsp=3B Are the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B IANA registries clearly identified?&nbsp=3B If the document cr=
eates a new<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B registry=2C does it=
 define the proposed initial contents of the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B registry and an allocation procedure for future registrations=
?<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Does it suggested a reasonabl=
e name for the new registry?&nbsp=3B See<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B [I-D.narten-iana-considerations-rfc2434bis].&nbsp=3B If the doc=
ument<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B describes an Expert Revie=
w process has Shepherd conferred with the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B Responsible Area Director so that the IESG can appoint the need=
ed<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Expert during the IESG Evalu=
ation?<br>&nbsp=3B<br>The IANA considerations section (7) exists=2C and is =
consistent with<br>the body of the document.&nbsp=3B Note that no new regis=
tries are created<br>nor does the document require assignment of any new pr=
otocol parameters=2C <br>since the Status-Server Code (12) was assigned in =
RFC 2865. <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.j)&nbsp=3B Has the Document S=
hepherd verified that sections of the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B document that are written in a formal language=2C such as XML code=
=2C<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B BNF rules=2C MIB definition=
s=2C etc.=2C validate correctly in an<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B automated checker?<br><br>Not applicable.<br>&nbsp=3B<br>&nbsp=3B&nb=
sp=3B (1.k)&nbsp=3B The IESG approval announcement includes a Document<br>&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Announcement Write-Up.&nbsp=3B Plea=
se provide such a Document<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Anno=
uncement Writeup?&nbsp=3B Recent examples can be found in the<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B "Action" announcements for approved document=
s.&nbsp=3B The approval<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B announc=
ement contains the following sections:<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B Technical Summary<br><br>This document specifies a depl=
oyed extenion to RADIUS which enables<br>clients to query the status of a R=
ADIUS server.&nbsp=3B While the<br>Status-Server Code (12) was defined as e=
xperimental in RFC 2865<br>Section 3=2C details of the protocol's operation=
 have not been<br>documented until now.&nbsp=3B <br>&nbsp=3B<br>&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B Working Group Summary<br><br>The RADEXT WG el=
ected to recommend this document for publication<br>as an Informational RFC=
 rather than as a standards-Track RFC due<br>to concerns about problems wit=
h deployed implementations.&nbsp=3B The<br>fixes recommended within the doc=
ument are compatible with <br>existing servers that receive Status-Server p=
ackets=2C but impose new<br>security requirements on clients that send Stat=
us-Server packets.<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B =
Document Quality<br>&nbsp=3B<br>The document has been reviewed by IETF RADE=
XT WG members. <br>An expert review has been carried out by Ignacio Goyret.=
 <br>&nbsp=3B<br>Status-Server has been implemented by multiple vendors=2C =
<br>including RADIATOR=2C FreeRADIUS and Cistron. <br>&nbsp=3B<br>&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Personnel<br>&nbsp=3B<br>Bernard Aboba is t=
he document shepherd for this document. <br>Dan Romascanu is the responsibl=
e AD. <br><br><br><br><br><br><br><br><br><br><table style=3D"border-top: 1=
px solid black=3B font-weight: bold=3B font-family: 'Segoe UI'=2CTahoma=2Cs=
an-serif=3B"><tbody><tr><td><a href=3D"http://im.live.com/Messenger/IM/Home=
/?source=3DEML_WLHM_GreaterGood" style=3D"font-size: 9pt=3B color: rgb(1=2C=
 132=2C 203)=3B text-decoration: none=3B"><span style=3D"padding: 0px 24px=
=3B font-size: 8pt=3B color: rgb(63=2C 181=2C 85)=3B text-decoration: under=
line=3B"></span></a><br></td></tr></tbody></table> 		 	   		  </body>
</html>=

--_3c60324e-b72b-4e3b-9588-a8fab915295b_--

--
to unsubscribe send a message to 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 Feb 23 23:54:33 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A46828C163 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 23:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z+vFjNDKG4FJ for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Tue, 23 Feb 2010 23:54:32 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6F51528C0D7 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 23 Feb 2010 23:54:32 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkC3O-0005wT-O7 for radiusext-data0@psg.com; Wed, 24 Feb 2010 07:53:06 +0000
Received: from [2001:a18:1::62] (helo=smtprelay.restena.lu) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <stefan.winter@restena.lu>) id 1NkC3M-0005w8-Aw for radiusext@ops.ietf.org; Wed, 24 Feb 2010 07:53:04 +0000
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 9F479105FF for <radiusext@ops.ietf.org>; Wed, 24 Feb 2010 08:53:02 +0100 (CET)
Received: from [IPv6:2001:a18:1:8::155] (unknown [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 8E070105FD for <radiusext@ops.ietf.org>; Wed, 24 Feb 2010 08:53:02 +0100 (CET)
Message-ID: <4B84DAD8.1000700@restena.lu>
Date: Wed, 24 Feb 2010 08:52:56 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0
MIME-Version: 1.0
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Issue 306: Suggested text
X-Enigmail-Version: 1.0.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig314D86BC6D608DEBD9A65BBA"
X-Virus-Scanned: ClamAV
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig314D86BC6D608DEBD9A65BBA
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Hi,

I'm currently assembling the -06 draft of RADIUS over TLS. This is a
proposed new section 2.3 to cover issue "NAS Identity":

Please comment...

2.3.  Connecting Client Identity

   In RADIUS, clients are uniquely identified by their IP address.  This
   does not permit to determine whether the connecting entity is a NAS
   or a different server which proxies a request.  When NAT is used on
   the path to the server, it also does not permit to determine whether
   there is more than one entity connecting from the same IP address.

   RADIUS over TLS makes it possible to preserve this traditional RADIUS
   semantics by identifying a connecting client by the IP address which
   initiated the TLS connection.  In addition, it does permit a much
   more fine-grained identification.  The parameters of the TLS
   connection can be attributed to the RADIUS packets inside the TLS
   connection.  An implementation of RADIUS over TLS should expose as
   many details of the TLS connection which belongs to an incoming
   RADIUS packet as possible to the application administrator to allow
   the administrator to define the identification criteria which are
   applicable to his desired operational model.  In X.509 certificate
   operation, at least the following parameters of the TLS connection
   should be exposed:

   o  Originating IP address

   o  Certificate Fingerprint

   o  Issuer

   o  Subject

   o  all X509v3 Extended Key Usage

   o  all X509v3 Subject Alternative Name

   o  all X509v3 Certificate Policies

   In TLS-PSK operation, at least the following parameters of the TLS
   connection should be exposed:

   o  Originating IP address

   o  TLS Identifier

Greetings,

Stefan Winter

(I created this text outside of my sponsor project's time)

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473



--------------enig314D86BC6D608DEBD9A65BBA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuE2t4ACgkQ+jm90f8eFWaqiACfZV7cuaGVeVlZITtdjRpRuk4T
s1IAn2DSMdvZED+MLZmUh+9jh00CJ6sc
=QHDY
-----END PGP SIGNATURE-----

--------------enig314D86BC6D608DEBD9A65BBA--

--
to unsubscribe send a message to 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 Feb 24 01:35:21 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 149303A80F5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 01:35:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.254
X-Spam-Level: 
X-Spam-Status: No, score=-1.254 tagged_above=-999 required=5 tests=[AWL=-0.759, 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 VVNF2JvGnPIf for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 01:35:20 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1AEC43A6AD0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 01:35:20 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkDce-000Fey-Gp for radiusext-data0@psg.com; Wed, 24 Feb 2010 09:33:36 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkDcb-000Feb-Mb for radiusext@ops.ietf.org; Wed, 24 Feb 2010 09:33:33 +0000
Message-ID: <4B84F26C.8070305@deployingradius.com>
Date: Wed, 24 Feb 2010 10:33:32 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
References: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
In-Reply-To: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> We would now like to request mailing list confirmation of the decision
> to adopt this draft.

  I support adoption.

Nits: IPv6-DNS-Server-Address doesn't follow the same naming schema as
"NAS-IPv6-Address" and others.  It could instead be
"DNS-Server-IPv6-Address".

  This is minor, though.  It doesn't really matter either way.

  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 Feb 24 01:55:26 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1D1E3A7C0A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 01:55:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sUvnGE3prQR for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 01:55:26 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id C551A3A8351 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 01:55:25 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkDx1-000IXx-64 for radiusext-data0@psg.com; Wed, 24 Feb 2010 09:54:39 +0000
Received: from [2001:a18:1::62] (helo=smtprelay.restena.lu) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <stefan.winter@restena.lu>) id 1NkDwx-000IXN-I1 for radiusext@ops.ietf.org; Wed, 24 Feb 2010 09:54:35 +0000
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id A6ADC105FF for <radiusext@ops.ietf.org>; Wed, 24 Feb 2010 10:54:34 +0100 (CET)
Received: from [IPv6:2001:a18:1:8::155] (unknown [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 8ED2610598 for <radiusext@ops.ietf.org>; Wed, 24 Feb 2010 10:54:34 +0100 (CET)
Message-ID: <4B84F755.2080803@restena.lu>
Date: Wed, 24 Feb 2010 10:54:29 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
References: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
In-Reply-To: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
X-Enigmail-Version: 1.0.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6AECE5BB270C1FDEC2A3E046"
X-Virus-Scanned: ClamAV
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6AECE5BB270C1FDEC2A3E046
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Am 23.02.2010 21:17, schrieb Bernard Aboba:
>
> During the RADEXT Virtual Interim, we discussed adoption of "RADIUS
> Attributes for IPv6 Access Networks" as a RADEXT WG work item.
>
> =20
>
> We would now like to request mailing list confirmation of the decision
> to adopt this draft.
>
> =20
>
> The document is available here:
>
> http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02
>
> =20
>
> If you have an opinion on the adoption  of this document as a RADEXT
> WG work item, please reply to this email.
>

The presentation yesterday convinced me that it solves a real-world
problem. I support adoption of the document.

Greetings,

Stefan Winter

> =20
>
> =20
>
> =20
>


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473



--------------enig6AECE5BB270C1FDEC2A3E046
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuE91kACgkQ+jm90f8eFWYBWQCfU4zVJ1B6HncKs9qx2p/oheKJ
LX4An2r4mS4AonQBTBkBiBYUPF1KB7hA
=NCxp
-----END PGP SIGNATURE-----

--------------enig6AECE5BB270C1FDEC2A3E046--

--
to unsubscribe send a message to 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 Feb 24 06:19:41 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1F4028C17E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 06:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.056
X-Spam-Level: 
X-Spam-Status: No, score=-1.056 tagged_above=-999 required=5 tests=[AWL=-0.861, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_WEOFFER=0.3]
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 bRYO28f8p2Nb for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 06:19:40 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4E72D28C108 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 06:19:39 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkI05-0000vI-S0 for radiusext-data0@psg.com; Wed, 24 Feb 2010 14:14:05 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkHzu-0000ts-BK for radiusext@ops.ietf.org; Wed, 24 Feb 2010 14:13:55 +0000
Message-ID: <4B85341E.4050902@deployingradius.com>
Date: Wed, 24 Feb 2010 15:13:50 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11
References: <7735D8F6-FD9E-43AB-B655-07AD53481AA5@bridgewatersystems.com> <BLU137-DS7B020CCE718F044DE2A1793430@phx.gbl>
In-Reply-To: <BLU137-DS7B020CCE718F044DE2A1793430@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

From: Avi Lior [mailto:avi@bridgewatersystems.com]
...
> -------
> 
> I am a little confused about the purpose of section 2 RADIUS Data Model and
> the purpose of Section 3 Data Model Issues.
> 
> Is the intent of section 2 to describe the data model then it should just do
> that and move discussions of issues to section 3.

  We can simplify that text.  Do you have any suggestions, or comments
on the suggestions from Hannes?

> ---------------
> Section 2:
> Please define Standard Space

  IANA managed RADIUS attribute space.

> Please define complex attributes. (you do so much later) or give a reference
> to where they are defined.

  Attributes of type *other* than the 5-6 "basic" types already defined.
 (RFC 2865, plus additions)

> "The format of this space is defined by individual vendors but the same TLV
> encoding used by the standard space..."
> 
> Change to:
> 
> "The format of the payload of these attributes is defined by individual
> vendors but the same TLV encoding...."

  OK.

> -----------------
> 2.1.1
> 
>    "However in order
>    to prevent future ambiguities, it is recommended that future RADIUS
>    attribute specifications explicitly define newly created data types
>    at the beginning of the document, and indicate clearly the data type
>    to be used for each attribute."
> 
> Do we care about the structure of the document.  I think the issue is that
> specification should define newly created data types and indicate clearly
> the data type to be used for each attribute.  

  The types should be defined before they are used in the document.

> Second issue: It seems to me that we are okay with folks creating new data
> types in standard space.  I think creation of new data types should be
> discouraged right?

  The doc doesn't say it's OK to create new data types in the standard
space.  It says that the IETF has change control over IETF protocols.
It says that no one else has change control over the "standard space".

> -----------------------
> 
> " It is worth noting that since RADIUS only supports unsigned integers
>    of 32 bits, attributes using signed integer data types or unsigned
>    integer types of other sizes will require code changes, and SHOULD be
>    avoided."
> 
> Why are we talking specifically signed integers?  This is already covered in
> the discussion of creating new types.

  Yes.

> But since we do bring this up - I suppose that we are talking about this
> because this is a common issue.  After all there is no way to represent
> negative numbers in RADIUS (or signed integers).  This creates a problem in
> general and specific when translating Diameter signed integers to RADIUS.  I
> think this document should either remove this paragraph or offer
> guidance/solution.

  Solutions are explicitly *out of scope* of this document.

> --------------
> 2.1.2
> 
> " For these reasons, the tagging scheme described in RFC 2868 is NOT
>    RECOMMENDED for use as a generic grouping mechanism."
> 
> What do you mean by generic grouping mechanism?

  Grouping of attributes?

> What about guidance on how to achieve this?

  Solutions are explicitly *out of scope* of this document.

> --------------------
> Section 2.1.3 Complex Types
> 
> Can we not re-write this section to be a little more concise and to the
> point? 

  Suggested text is welcome.

> "However, some standard attributes do not follow this format."
> Please give an example of an attribute.

  Hmm... I'm not sure what that text is doing there.  I suggest simply
deleting it.

>  "Attributes that use sub-fields instead of using a basic data type are
>    known as "complex attributes". "
> 
> What are sub-fields.

  I'm not sure what's unclear about that.

> Is an attribute that codefies a bit map a complex attribute?  I think yes.
> This is probably the most common complex type that people use.  What
> guidance do we offer to designers that need a bit-field?  Each bit is an
> attribute?  

  We don't.  Solutions are explicitly *out of scope* of this document.

> ---------
> 
> "   * it is easier for the user to enter the data as well-known
>         types, rather than complex structures;"
> This bullet should be removed.  Following good engineer practices of
> seperation of concerns and in this case seperation of presentation and the
> model (MVC).  We dont want to encourage users to edit raw data as codefied
> by the RADIUS protocol.  For example, we dont want user to enter a IPv4
> address as a 32bit value or an Address type. But rather as an IP address in
> dot notation.

  Of course.  So why would we remove text that says entering data as the
proper type?

> --------
>       * it enables additional error checking by leveraging the
>         parsing and validation routines for well-known types;
> 
>       * it simplifies implementations by eliminating special-case
>         attribute-specific parsing.
> 
> These two bullets are the same and should be combined.

  OK.

> --------------
> 
> One of the fundamental goals of the RADIUS protocol design was to
>    allow RADIUS servers to be configured to support new attributes
>    without requiring server code changes.  RADIUS server implementations
>    typically provide support for basic data types, and define attributes
>    in a data dictionary.  This architecture enables a new attribute to
>    be supported by the addition of a dictionary entry, without requiring
>    other RADIUS server code changes.
> 
> This is totally misleading.  We should explain when this is true -- it is
> mostly not true today since RADIUS is increasingly supporting dynamic
> policies and thus always requires code change to handle the introduction of
> any new attribute whether it is an attribute of an existing type or not.

  Sorry, but this point has been hashed to death.

  Every single RADIUS server implementation supports at *least* the
functionality above.  If your implementation supports a more complex
dictionary capability, then it is *also* covered by the above text.

  There is no need to change the text.

> As well the above appears under the complex attribute section 2.1.3 - It is
> true also if we were to introduce a new attribute type.

  Of course.  But that is outside of the scope of the guidelines docuemnt.

> ----------
> 
> " On the RADIUS client, code changes are typically required in order to
>    implement a new attribute. "
> 
> A new attribute or a new attribute type or a complex attribute? Which one?

  The text is clear as-is.  "new" attribute means "new attribute".

> ----
> 
>   "The RADIUS client typically has to
>    compose the attribute dynamically when sending.  When receiving, a
>   RADIUS client needs to be able to parse the attribute and carry out
>    the requested service.  As a result, a detailed understanding of the
>    new attribute is required on clients, and data dictionaries are less
>    useful on clients than on servers.
> 
> Many of the reasons given here are also true for servers. 

  OK.

> ----------
> 
>   "The RADIUS server can be configured to send a new static attribute by
>    entering its type and data format in the RADIUS server dictionary,
>    and then filling in the value within a policy based on the attribute
>    name, data type and type-specific value."
> 
> The above is only true if the new static attribute is an existing type.

  Or if your dictionary definitions support more than existing types.

> --------
> 
> "Code changes can also be required in policy management and in the
>    RADIUS server's receive path.  These changes are due to limitations
>    in RADIUS server policy languages, which typically only provide for
>    limited operations (such as comparisons or arithmetic operations) on
>    the existing data types.  Many existing RADIUS policy languages
>    typically are not capable of parsing sub-elements, or providing
>    sophisticated matching functionality."
> 
> What is a RADIUS server policy language?  

  Do you have a suggested definition, or is "policy language" unclear?

> RADIUS policy languages are not part of the IETF - the IETF did not conduct
> a survey and thus cannot make statements such as these.

  Addressing implementation limitations is well within the scope of
IETF.  The alternative is to pretend that we know nothing about
implementations because we didn't commission an official survey.

> Most policy languages i know about contain REgExp that is sophisticated and
> can extract any information out of any type. Typicially these have been
> first added to be able to parse the RADIUS username.

  Yes.  That functionality goes back if not to the Livingston server,
then at least to multiple implementations after 1996.

> Remove this paragraph.

  There is no demonstrated need.

> ------------------
> The paragraph starting with "Given these limitations..." seems out of place
> since it talks about new types, not complex types....

  I don't see why.  A signed 8-bit integer is a new type that could
require code changes.  It's definitely not a complex type.

> Then it talks about attribute specific parsing which is not really related
> to new types.

  That could be "parsing of new types", or refer to "ad hoc" attributes
that define a new complex type unique to that attribute.

> Then it talks about the intoduction of new complex data types within RADIUS
> attribute specification be avoided.
> 
> So now we have a new thing called a "new complex data type".    Dont we mean
> new types and complex data types?

  Yes.

> Also this paragraph repeats text made earilier  by the bullet points.
> -----
> "The only other exception to the recommendation against complex types
>    is for types that can be treated as opaque data by the RADIUS server."
> 
> The assertions that the document is making in this sentence is wrong and we
> should remove this statement.  We have seen examples like in RADIUS digest
> where we flattened out an attribute to create more then a dozen attributes.
> There are other cases as well.  Remove this paragraph.

  There is no need.  The rest of the text in the document should make it
clear that design is a balancing act, not a set of hard and fast rules.

> ------
> 
>  " If the RADIUS Server simply passes the contents of an attribute to
>    some non-RADIUS portion of the network, then the data is opaque, and
>    SHOULD be defined to be of type String.  A concrete way of judging
>    this requirement is whether or not the attribute definition in the
>    RADIUS document contains delineated fields for sub-parts of the data.
>    If those fields need to be delineated in RADIUS, then the data is not
>    opaque, and it SHOULD be separated into individual RADIUS attributes."
> 
> 
> The document is attempting to define a RADIUS Server architecture.

  No.  It is acknowledging that RADIUS servers may exist within a wider
framework.

  Is this idea controversial?

>  We
> should do this properly.  An equally valid architecture is the Diameter one
> where the Server is composed of a lower layer defined by RFC 3588 and an
> application layer.  We should state that as well.

  Defining new RADIUS architectures is *out of scope* of this document.

> Here the document gives an impression that the only "application" layer
> possible is some foreign entity not part of the RADIUS server - that is just
> not true today.

  The text contains no reference to an "application" layer.  And there
is nothing in the text that restricts it to *only* an application layer.

  So your comment is therefore not relevant to the document.

> ---------
> 2.1.4
> " RADIUS specifications define how an existing service or protocol can
>    be provisioned using RADIUS.  Therefore, it is expected that a RADIUS
>    attribute specification will reference documents defining the
>    protocol or service to be provisioned.  Within the IETF, a RADIUS
>    attribute specification SHOULD NOT be used to define the protocol or
>    service being provisioned.  New services using RADIUS for
>    provisioning SHOULD be defined elsewhere and referenced in the RADIUS
>    specification."
> 
> 
> I am confused by what we are trying to say in this section.

  OK.

> -------
> 
> "New attributes, or new values of existing attributes, SHOULD NOT be
>    used to define new RADIUS commands.  RADIUS attributes are intended
>    to:"
> 
> Shouldn't this be a different section.

  Like... where?

> ----------
> 2.2
> 
> " However, instead of doing this, vendors have defined the following
>    non-standard VSA formats:"
> 
> The standard allows Vendors to define their VSA as they wish.  How can you
> say "non-standard VSA formats"?

  RFC 2865 defines a suggested VSA format.  Vendors are free to do as
they wish, including defining formats not recommended by the standards.
 So... this means "non-standard format".

> Howecer instead of following the recommendation vendors have defiend the
> following:
> 
> ------------
> 
>   "All VSA schemes that do not follow the [RFC2865] recommendations are
>    NOT RECOMMENDED.  These non-standard formats will typically not be
>    implementable without RADIUS server code changes.  This includes all
>    the above formats, as well as Vendor types of more than 8 bits,
>    vendor lengths of less than 8 bits, vendor lengths of more than 8
>    bits and Vendor-Specific contents that are not in Type-Length-Value
>    format."
> 
> Its up to the vendors or SDO to decide and the specification allows for
> that.  RFC2865 makes a recommendation and we should just leave it at that.

  So the guidelines document shouldn't have guidelines for attribute design?

> You can state the problems that this may create but I think the document is
> out of bounds when it states that it is not recommended.  2865 makes a
> recommendation and that is enough.

  If that's true, the *entire* guidelines document is unnecessary.

  However... vendors have created *unnecessarily* different VSA
encodings.  The IETF is well within it's right as owner of the RADIUS
protocol to recommend how vendors use it.

> ---------------
> 
> " Although [RFC2865] does not mandate it, implementations commonly
>    assume that the Vendor Id can be used as a key to determine the on-
>    the-wire format of a VSA.  Vendors therefore SHOULD NOT use multiple
>    formats for VSAs that are associated with a particular Vendor Id.  A
>    vendor wishing to use multiple VSA formats SHOULD request one Vendor
>    Id for each VSA format that they will use."
> 
> What do you mean by on-the-wire format?  

  I'm unsure how to answer that.  The definition should be clear.

> ---------
> Section 3 is not only about data model issues.
> 
> We need a better name.

  Do you have a suggestion?

> -----------
> 
> 3.3
> 
> Why are we repeating the recommendations fo 5080.  Just remind people that
> they need to read it.

  Do you have suggested replacement text?

> ---------
> 
> Section 5
> 
> "Where new RADIUS attributes encapsulate complex data types, or transport
> opaque data, the security considerations discussed in Sectiont 2.1.4 SHOULD
> be addressed"
> 
> The contents of 2.1.4 was moved to the security section

  OK.

> -----
> 5.1
> 
> The title should be Complex Types and New Data types no?

  Sure.

> The text in this section should be fixed as well.  Sometimes it refers to
> one where the other is also applicable.

  Do you have suggested replacement text?

> -------
> 
>    "Any system consuming opaque data that originates from a RADIUS system
>    SHOULD be properly isolated from that RADIUS system, and SHOULD run
>    with minimal privileges.  Any potential vulnerabilities in the non-
>    RADIUS system will then have minimal impact on the security of the
>    system as a whole."
> 
> fear mongering a bit here and not true???  I can inject code in the opaque
> data which could cause the system to run at higher privelages. Can we make
> more concrete recommendations such as use care to validate the opaque data
> for example to ensure no buffer overruns etc etc....It is pretty standard
> practice to validate data coming from potentially untrusted sources or that
> can be compromized along the way.

  Do you have suggested replacement text?

> 
> 
> Appendix A
> 
> A.1
> 
> Simple Data vs Radius Data types.  They are the same no?  We need to use the
> term consistantly throughout the document.

  Sure.

> A.1.2
> 
> *Complex data types...which the RADIUS servers are expected to parse..."
> 
> I think you need to explain the model here.  This is a common theme
> throughout the document.  What is a RADIUS server?

  Suggest some text.

  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 Feb 24 06:46:01 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F317B28C194 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 06:46:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.412
X-Spam-Level: 
X-Spam-Status: No, score=-0.412 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, 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 zc54GP40h32I for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 06:46:00 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id A20AB28C163 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 06:45:58 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkISj-0004Mq-F7 for radiusext-data0@psg.com; Wed, 24 Feb 2010 14:43:41 +0000
Received: from [217.169.121.21] (helo=GRFEDG702RM001.telecomitalia.it) by psg.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.71 (FreeBSD)) (envelope-from <roberta.maglione@telecomitalia.it>) id 1NkIS4-0004J9-GE for radiusext@ops.ietf.org; Wed, 24 Feb 2010 14:43:38 +0000
Content-Type: multipart/mixed; boundary="_3a074c2f-6ef7-4451-9e2b-960e668eb16e_"
Received: from GRFHUB704RM001.griffon.local (10.19.3.67) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 24 Feb 2010 15:42:58 +0100
Received: from GRFHUB703BA020.griffon.local (10.188.101.113) by GRFHUB704RM001.griffon.local (10.19.3.67) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 24 Feb 2010 15:42:55 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by GRFHUB703BA020.griffon.local ([10.188.101.113]) with mapi; Wed, 24 Feb 2010 15:42:55 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Bernard Aboba' <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Wed, 24 Feb 2010 15:42:54 +0100
Subject: RE: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Thread-Topic: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Thread-Index: Acq0xT8uBPxYy20STV+Ko3u61xMO7gAmd+UA
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35163B@GRFMBX704BA020.griffon.local>
References: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
In-Reply-To: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, it-IT
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_3a074c2f-6ef7-4451-9e2b-960e668eb16e_
Content-Type: multipart/alternative;
	boundary="_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_"

--_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


I support adoption of this document as WG item: this work is needed for IPv=
6 deployment in Broadband access environment.

Best Regards,
Roberta

________________________________
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On=
 Behalf Of Bernard Aboba
Sent: Tuesday, February 23, 2010 9:18 PM
To: radiusext@ops.ietf.org
Subject: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"

During the RADEXT Virtual Interim, we discussed adoption of "RADIUS Attribu=
tes for IPv6 Access Networks" as a RADEXT WG work item.

We would now like to request mailing list confirmation of the decision to a=
dopt this draft.

The document is available here:
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02

If you have an opinion on the adoption  of this document as a RADEXT WG wor=
k item, please reply to this email.



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.

[cid:00000000000000000000000000000001@TI.Disclaimer]Rispetta l'ambiente. No=
n stampare questa mail se non ? necessario.


--_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:ns1=3D"http://schemas.microsoft.com/office/20=
04/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:offic=
e:smarttags" name=3D"PersonName" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=3D"IT" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial">I support adoption of this document as WG item: t=
his work is needed for IPv6 deployment in Broadband access environment.<o:p=
></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial">Best Regards,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial">Roberta<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:Arial;color:navy"><o:=
p>&nbsp;</o:p></span></font></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt;font-family:
&quot;Times New Roman&quot;">
<hr size=3D"3" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</=
span></font></b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:Tahoma"> owner-<st1:PersonName w:st=3D"on"=
>radiusext@ops.ietf.org</st1:PersonName>
 [mailto:owner-<st1:PersonName w:st=3D"on">radiusext@ops.ietf.org</st1:Pers=
onName>]
<b><span style=3D"font-weight:
bold">On Behalf Of </span></b>Bernard Aboba<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, February 23, =
2010 9:18 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> <st1:PersonName w:st=3D"=
on">radiusext@ops.ietf.org</st1:PersonName><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Call for adoption o=
f &quot;RADIUS Attributes for IPv6 Access Networks&quot;</span></font><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt;
font-family:&quot;Times New Roman&quot;"><o:p></o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">During the RADEXT Virtual Interim, we discussed adoption of &quot;R=
ADIUS Attributes for IPv6 Access Networks&quot; as a RADEXT WG work item.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">We would now like to request mailing list confirmation of the decis=
ion to adopt this draft.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">The document is available here:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02<o:=
p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">If you have an opinion on the adoption&nbsp; of this document as a =
RADEXT WG work item, please reply to this email.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<style type=3D"text/css">
<!--
span.GramE {mso-style-name:"";
	mso-gram-e:yes;}
-->
</style>
<table style=3D"width:600px;">
<tbody>
<tr>
<td style=3D"width:585px; font-family: Verdana, Arial; font-size:12px; colo=
r:#000; text-align: justify" width=3D"395">
<div align=3D"justify"><span class=3D"MsoNormal" style=3D"text-align:justif=
y; line-height:normal"><span style=3D"font-size:7.5pt;font-family:Verdana">=
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi
 altra azione derivante dalla conoscenza di queste informazioni sono rigoro=
samente vietate. Qualora abbiate ricevuto questo documento per errore siete=
 cortesemente pregati di darne immediata comunicazione al mittente e di pro=
vvedere alla sua distruzione, Grazie.
</span></span></div>
<p align=3D"justify"><span class=3D"MsoNormal" style=3D"text-align:justify;=
 line-height:normal"><i><span lang=3D"EN-GB" style=3D"font-size:7.5pt;font-=
family:Verdana;mso-ansi-language:EN-GB">This e-mail and any attachments</sp=
an></i><i><span lang=3D"EN-GB" style=3D"font-size:
  7.5pt;mso-bidi-font-size:11.0pt;font-family:Verdana;mso-ansi-language:EN-=
GB">&nbsp;<span class=3D"GramE">is</span>&nbsp;</span></i><i><span lang=3D"=
EN-GB" style=3D"font-size:
  7.5pt;font-family:Verdana;mso-ansi-language:EN-GB">confidential
 and may contain privileged information intended for the addressee(s) only.=
 Dissemination, copying, printing or use by anybody else is unauthorised. I=
f you are not the intended recipient, please delete this message and any at=
tachments and advise the sender
 by return e-mail, Thanks.</span></i><span lang=3D"EN-GB" style=3D"mso-ansi=
-language:EN-GB">
</span></span></p>
<b><span style=3D"font-size:7.5pt;
  font-family:Verdana"><img src=3D"cid:00000000000000000000000000000001@TI.=
Disclaimer" alt=3D"rispetta l'ambiente" width=3D"26" height=3D"40">Rispetta=
 l'ambiente. Non stampare questa mail se non &egrave; necessario.</span></b=
>
<p></p>
</td>
</tr>
</tbody>
</table>
</body>
</html>

--_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_--

--_3a074c2f-6ef7-4451-9e2b-960e668eb16e_
Content-Description: logo Ambiente_foglia.jpg
Content-Type: image/jpeg; name="logo Ambiente_foglia.jpg"
Content-Disposition: inline; filename="logo Ambiente_foglia.jpg"
Content-Transfer-Encoding: base64
Content-ID: 00000000000000000000000000000001@TI.Disclaimer

R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo
8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5
+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9
p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxw
SBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0
FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6
YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfl
uh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds
3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaV
OmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDi
oY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAkn
qnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=

--_3a074c2f-6ef7-4451-9e2b-960e668eb16e_--

--
to unsubscribe send a message to 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 Feb 24 06:52:27 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 314D928C1B8 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 06:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.958
X-Spam-Level: 
X-Spam-Status: No, score=-0.958 tagged_above=-999 required=5 tests=[AWL=-0.464, 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 zRCCcqp0INuL for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 06:52:25 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8905A28C1AF for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 06:52:23 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkIXv-00054i-CO for radiusext-data0@psg.com; Wed, 24 Feb 2010 14:49:03 +0000
Received: from [65.55.116.23] (helo=blu0-omc1-s12.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NkIXr-00053I-3R for radiusext@ops.ietf.org; Wed, 24 Feb 2010 14:48:59 +0000
Received: from BLU137-DS4 ([65.55.116.7]) by blu0-omc1-s12.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Feb 2010 06:48:58 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS4C503CEF590C0E9F1C99B93410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: PROTO writeup for RADIUS over TCP document
Date: Wed, 24 Feb 2010 06:49:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007E_01CAB51D.8BACFF10"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq1YJk2CQYmRG6TRi2lGYxForhuCg==
Content-Language: en-us
X-OriginalArrivalTime: 24 Feb 2010 14:48:58.0573 (UTC) FILETIME=[7F00D7D0:01CAB560]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

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

PROTO Writeup for draft-ietf-radext-tcp-transport

=================================================

 

http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

 

   (1.a)  Who is the Document Shepherd for this document?  Has the

      Document Shepherd personally reviewed this version of the document

      and, in particular, does he or she believe this version is ready

      for forwarding to the IESG for publication?

 

Bernard Aboba is the document shepherd.  I have personally reviewed

the document, and believe it is ready for publication as an Experimental

RFC. 

 

   (1.b)  Has the document had adequate review both from key members of

      the interested community and others?  Does the Document Shepherd

      have any concerns about the depth or breadth of the reviews that

      have been performed?

 

The document has undergone review within the community of RTLS

implementers, as well as within the RADEXT WG.  It could benefit

from additional review by the transport community. 

 

   (1.c)  Does the Document Shepherd have concerns that the document

      needs more review from a particular or broader perspective, e.g.,

      security, operational complexity, someone familiar with AAA,

      internationalization or XML?

 

This document should be reviewed by the Transport Directorate prior

to publication. 

 

   (1.d)  Does the Document Shepherd have any specific concerns or

      issues with this document that the Responsible Area Director

      and/or the IESG should be aware of?  For example, perhaps he or

      she is uncomfortable with certain parts of the document, or has

      concerns whether there really is a need for it.  In any event, if

      the interested community has discussed those issues and has

      indicated that it still wishes to advance the document, detail

      those concerns here.

 

As noted in Section 2.5, there are situations (such as NAS avalanche
restart)

where a proxy implementing RADIUS over TCP/TLS would be unable to keep up

with the UDP packets generated by NAS devices not implementing the 

congestion control algorithm described in RFC 5080 Section 2.2.1.

 

   (1.e)  How solid is the consensus of the interested community behind

      this document?  Does it represent the strong concurrence of a few

      individuals, with others being silent, or does the interested

      community as a whole understand and agree with it?

 

There is consensus within the RADEXT WG to publish the document as

an Experimental RFC. 

 

   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme

      discontent?  If so, please summarise the areas of conflict in

      separate email messages to the Responsible Area Director.  (It

      should be in a separate email because this questionnaire is

      entered into the ID Tracker.)

 

No. 

 

   (1.g)  Has the Document Shepherd personally verified that the

      document satisfies all ID nits?  (See

      http://www.ietf.org/ID-Checklist.html and

      http://tools.ietf.org/tools/idnits/).  Boilerplate checks are not

      enough; this check needs to be thorough.  Has the document met all

      formal review criteria it needs to, such as the MIB Doctor, media

      type and URI type reviews?

 

idnits is clean:

 

idnits 2.12.00 

 

tmp/draft-ietf-radext-tcp-transport-05.txt:

 

  Checking boilerplate required by RFC 5378 and the IETF Trust (see

  http://trustee.ietf.org/license-info):

 
----------------------------------------------------------------------------

 

     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: Experimental

 
----------------------------------------------------------------------------

 

  -- Unexpected draft version: The latest known version of 

     draft-ietf-radext-status-server is -03, but you're referring to -06.

     (However, the state information for draft-ietf-radext-status-server is

     not up-to-date.  The last update was 2009-02-13)

 

 

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

 

   (1.h)  Has the document split its references into normative and

      informative?  Are there normative references to documents that are

      not ready for advancement or are otherwise in an unclear state?

      If such normative references exist, what is the strategy for their

      completion?  Are there normative references that are downward

      references, as described in [RFC3967]?  If so, list these downward

      references to support the Area Director in the Last Call procedure

      for them [RFC3967].

 

The references in the document have been split into normative and

informative. 

 

Normative references are all stable documents published as RFCs.

 

   (1.i)  Has the Document Shepherd verified that the document IANA

      consideration section exists and is consistent with the body of

      the document?  If the document specifies protocol extensions, are

      reservations requested in appropriate IANA registries?  Are the

      IANA registries clearly identified?  If the document creates a new

      registry, does it define the proposed initial contents of the

      registry and an allocation procedure for future registrations?

      Does it suggested a reasonable name for the new registry?  See

      [I-D.narten-iana-considerations-rfc2434bis].  If the document

      describes an Expert Review process has Shepherd conferred with the

      Responsible Area Director so that the IESG can appoint the needed

      Expert during the IESG Evaluation?

 

The IANA Considerations section exists (section 4).  It requires no

action by IANA. 

 

   (1.j)  Has the Document Shepherd verified that sections of the

      document that are written in a formal language, such as XML code,

      BNF rules, MIB definitions, etc., validate correctly in an

      automated checker?

 

Not applicable.

 

   (1.k)  The IESG approval announcement includes a Document

      Announcement Write-Up.  Please provide such a Document

      Announcement Writeup?  Recent examples can be found in the

      "Action" announcements for approved documents.  The approval

      announcement contains the following sections:

 

      Technical Summary

 

RADIUS has traditionally used UDP as its underlying transport layer, for

reasons described in RFC 2865 Section 2.4.  This document defines RADIUS

over TCP, in order to address handling issues related to RADIUS over TLS

(RTLS).  It is not intended to define TCP as a transport protocol for

RADIUS in the absence of TLS.   

 

      Working Group Summary

 

This document is part of a set (including the Status-Server and RTLS

specifications) which together define RADIUS over TLS (RTLS).

This document has completed RADEXT WG last call, with the primary

areas of discussion relating to liveness detection and congestion control. 

 

      Document Quality

 

The document has been reviewed by IETF RADEXT WG members. 

 

RADIUS over TLS/TCP has been implemented by multiple vendors, 

including RADIATOR and FreeRADIUS.  The protocol is currently

the subject of a large scale experiment involving deployment 

by EDUROAM, an educational roaming consortium supporting more

than one million users worldwide.

 

      Personnel

 

Bernard Aboba is the document shepherd for this document. 

Dan Romascanu is the responsible AD.


------=_NextPart_000_007E_01CAB51D.8BACFF10
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>PROTO Writeup for =
draft-ietf-radext-tcp-transport<o:p></o:p></p>

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

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

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-tcp-transp=
ort<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.a)&nbsp; Who is the Document =
Shepherd for this document?&nbsp;
Has the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Document Shepherd =
personally reviewed this version of
the document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and, in particular, =
does he or she believe this
version is ready<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for forwarding to =
the IESG for publication?<o:p></o:p></p>

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

<p class=3DMsoNormal>Bernard Aboba is the document shepherd.&nbsp; I =
have personally
reviewed<o:p></o:p></p>

<p class=3DMsoNormal>the document, and believe it is ready for =
publication as an
Experimental<o:p></o:p></p>

<p class=3DMsoNormal>RFC. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.b)&nbsp; Has the document had =
adequate review both from key
members of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the interested =
community and others?&nbsp; Does the
Document Shepherd<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have any concerns =
about the depth or breadth of the
reviews that<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have been =
performed?<o:p></o:p></p>

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

<p class=3DMsoNormal>The document has undergone review within the =
community of
RTLS<o:p></o:p></p>

<p class=3DMsoNormal>implementers, as well as within the RADEXT =
WG.&nbsp; It could
benefit<o:p></o:p></p>

<p class=3DMsoNormal>from additional review by the transport community. =
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.c)&nbsp; Does the Document Shepherd =
have concerns that the
document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs more review =
from a particular or broader
perspective, e.g.,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;security, =
operational complexity, someone familiar
with AAA,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; internationalization =
or XML?<o:p></o:p></p>

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

<p class=3DMsoNormal>This document should be reviewed by the Transport
Directorate prior<o:p></o:p></p>

<p class=3DMsoNormal>to publication. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.d)&nbsp; Does the Document Shepherd =
have any specific
concerns or<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; issues with this =
document that the Responsible Area
Director<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and/or the IESG =
should be aware of?&nbsp; For example,
perhaps he or<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; she is uncomfortable =
with certain parts of the
document, or has<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; concerns whether =
there really is a need for it.&nbsp; In
any event, if<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the interested =
community has discussed those issues
and has<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicated that it =
still wishes to advance the
document, detail<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; those concerns =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>As noted in Section 2.5, there are situations (such =
as NAS
avalanche restart)<o:p></o:p></p>

<p class=3DMsoNormal>where a proxy implementing RADIUS over TCP/TLS =
would be
unable to keep up<o:p></o:p></p>

<p class=3DMsoNormal>with the UDP packets generated by NAS devices not
implementing the <o:p></o:p></p>

<p class=3DMsoNormal>congestion control algorithm described in RFC 5080 =
Section
2.2.1.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.e)&nbsp; How solid is the consensus =
of the interested
community behind<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this document?&nbsp; =
Does it represent the strong
concurrence of a few<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; individuals, with =
others being silent, or does the
interested<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; community as a whole =
understand and agree with it?<o:p></o:p></p>

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

<p class=3DMsoNormal>There is consensus within the RADEXT WG to publish =
the
document as<o:p></o:p></p>

<p class=3DMsoNormal>an Experimental RFC. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.f)&nbsp; Has anyone threatened an =
appeal or otherwise
indicated extreme<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discontent?&nbsp; If =
so, please summarise the areas of
conflict in<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separate email =
messages to the Responsible Area
Director.&nbsp; (It<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be in a =
separate email because this
questionnaire is<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entered into the ID =
Tracker.)<o:p></o:p></p>

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

<p class=3DMsoNormal>No. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.g)&nbsp; Has the Document Shepherd =
personally verified that
the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document satisfies =
all ID nits?&nbsp; (See<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
http://www.ietf.org/ID-Checklist.html and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
http://tools.ietf.org/tools/idnits/).&nbsp; Boilerplate
checks are not<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enough; this check =
needs to be thorough.&nbsp; Has the
document met all<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; formal review =
criteria it needs to, such as the MIB
Doctor, media<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type and URI type =
reviews?<o:p></o:p></p>

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

<p class=3DMsoNormal>idnits is clean:<o:p></o:p></p>

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

<p class=3DMsoNormal>idnits 2.12.00 <o:p></o:p></p>

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

<p =
class=3DMsoNormal>tmp/draft-ietf-radext-tcp-transport-05.txt:<o:p></o:p><=
/p>

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

<p class=3DMsoNormal>&nbsp; Checking boilerplate required by RFC 5378 =
and the IETF
Trust (see<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp; =
http://trustee.ietf.org/license-info):<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp; Checking nits according to
http://www.ietf.org/ietf/1id-guidelines.txt:<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp; Checking nits according to
http://www.ietf.org/ID-Checklist.html:<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

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

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp; Checking references for intended status: =
Experimental<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp; -- Unexpected draft version: The latest =
known version of <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ietf-radext-status-server is -03, but you're
referring to -06.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; (However, the state =
information for draft-ietf-radext-status-server
is<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; not up-to-date.&nbsp; The =
last update was 2009-02-13)<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Summary: 0 errors (**), 0 =
warnings (=3D=3D), 1 comment
(--).<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.h)&nbsp; Has the document split its =
references into
normative and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informative?&nbsp; =
Are there normative references to
documents that are<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not ready for =
advancement or are otherwise in an
unclear state?<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If such normative =
references exist, what is the
strategy for their<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; completion?&nbsp; =
Are there normative references that are
downward<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; references, as =
described in [RFC3967]?&nbsp; If so, list
these downward<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; references to =
support the Area Director in the Last
Call procedure<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for them =
[RFC3967].<o:p></o:p></p>

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

<p class=3DMsoNormal>The references in the document have been split into
normative and<o:p></o:p></p>

<p class=3DMsoNormal>informative. <o:p></o:p></p>

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

<p class=3DMsoNormal>Normative references are all stable documents =
published as
RFCs.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.i)&nbsp; Has the Document Shepherd =
verified that the
document IANA<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; consideration =
section exists and is consistent with
the body of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the document?&nbsp; =
If the document specifies protocol extensions,
are<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; reservations =
requested in appropriate IANA
registries?&nbsp; Are the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IANA registries =
clearly identified?&nbsp; If the document
creates a new<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; registry, does it =
define the proposed initial contents
of the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; registry and an =
allocation procedure for future
registrations?<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does it suggested a =
reasonable name for the new
registry?&nbsp; See<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[I-D.narten-iana-considerations-rfc2434bis].&nbsp; If the
document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; describes an Expert =
Review process has Shepherd
conferred with the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Responsible Area =
Director so that the IESG can appoint
the needed<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Expert during the =
IESG Evaluation?<o:p></o:p></p>

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

<p class=3DMsoNormal>The IANA Considerations section exists (section =
4).&nbsp; It
requires no<o:p></o:p></p>

<p class=3DMsoNormal>action by IANA. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.j)&nbsp; Has the Document Shepherd =
verified that sections
of the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document that are =
written in a formal language, such
as XML code,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BNF rules, MIB =
definitions, etc., validate correctly
in an<o:p></o:p></p>

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

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

<p class=3DMsoNormal>Not applicable.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.k)&nbsp; The IESG approval =
announcement includes a Document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Announcement =
Write-Up.&nbsp; Please provide such a Document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Announcement =
Writeup?&nbsp; Recent examples can be found in
the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Action&quot; =
announcements for approved
documents.&nbsp; The approval<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; announcement =
contains the following sections:<o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>RADIUS has traditionally used UDP as its underlying
transport layer, for<o:p></o:p></p>

<p class=3DMsoNormal>reasons described in RFC 2865 Section 2.4.&nbsp; =
This document
defines RADIUS<o:p></o:p></p>

<p class=3DMsoNormal>over TCP, in order to address handling issues =
related to
RADIUS over TLS<o:p></o:p></p>

<p class=3DMsoNormal>(RTLS).&nbsp; It is not intended to define TCP as a =
transport
protocol for<o:p></o:p></p>

<p class=3DMsoNormal>RADIUS in the absence of TLS.&nbsp;&nbsp; =
<o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>This document is part of a set (including the =
Status-Server
and RTLS<o:p></o:p></p>

<p class=3DMsoNormal>specifications) which together define RADIUS over =
TLS
(RTLS).<o:p></o:p></p>

<p class=3DMsoNormal>This document has completed RADEXT WG last call, =
with the
primary<o:p></o:p></p>

<p class=3DMsoNormal>areas of discussion relating to liveness detection =
and
congestion control. <o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>The document has been reviewed by IETF RADEXT WG =
members. <o:p></o:p></p>

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

<p class=3DMsoNormal>RADIUS over TLS/TCP has been implemented by =
multiple
vendors, <o:p></o:p></p>

<p class=3DMsoNormal>including RADIATOR and FreeRADIUS.&nbsp; The =
protocol is
currently<o:p></o:p></p>

<p class=3DMsoNormal>the subject of a large scale experiment involving =
deployment
<o:p></o:p></p>

<p class=3DMsoNormal>by EDUROAM, an educational roaming consortium =
supporting
more<o:p></o:p></p>

<p class=3DMsoNormal>than one million users worldwide.<o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>Bernard Aboba is the document shepherd for this =
document. <o:p></o:p></p>

<p class=3DMsoNormal>Dan Romascanu is the responsible AD.<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_007E_01CAB51D.8BACFF10--

--
to unsubscribe send a message to 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 Feb 24 07:05:13 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7576228C1A4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 07:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.968
X-Spam-Level: 
X-Spam-Status: No, score=-0.968 tagged_above=-999 required=5 tests=[AWL=-0.473, 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 spUImBxU-bnz for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 07:05:12 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5753C28C108 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 07:05:12 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkImm-0007DS-5Z for radiusext-data0@psg.com; Wed, 24 Feb 2010 15:04:24 +0000
Received: from [65.55.116.48] (helo=blu0-omc1-s37.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NkImg-0007Cj-OF for radiusext@ops.ietf.org; Wed, 24 Feb 2010 15:04:18 +0000
Received: from BLU137-DS9 ([65.55.116.7]) by blu0-omc1-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Feb 2010 07:04:18 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS9EB161DAD2A5C53B137E193410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
References: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl> <4B84F755.2080803@restena.lu>
In-Reply-To: <4B84F755.2080803@restena.lu>
Subject: RE: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Date: Wed, 24 Feb 2010 07:05:02 -0800
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: Acq1N9XnMYpsV1LWTOKq5YlJyZMrXwAKs8uA
Content-Language: en-us
X-OriginalArrivalTime: 24 Feb 2010 15:04:18.0135 (UTC) FILETIME=[A31ADE70:01CAB562]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

I agree that the presentation was helpful (the first coherent =
explanation of
how it works), and I
also support adoption.=20

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] =
On
Behalf Of Stefan Winter
Sent: Wednesday, February 24, 2010 1:54 AM
To: radiusext@ops.ietf.org
Subject: Re: Call for adoption of "RADIUS Attributes for IPv6 Access
Networks"

Am 23.02.2010 21:17, schrieb Bernard Aboba:
>
> During the RADEXT Virtual Interim, we discussed adoption of "RADIUS=20
> Attributes for IPv6 Access Networks" as a RADEXT WG work item.
>
> =20
>
> We would now like to request mailing list confirmation of the decision =

> to adopt this draft.
>
> =20
>
> The document is available here:
>
> http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02
>
> =20
>
> If you have an opinion on the adoption  of this document as a RADEXT=20
> WG work item, please reply to this email.
>

The presentation yesterday convinced me that it solves a real-world =
problem.
I support adoption of the document.

Greetings,

Stefan Winter

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

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  Wed Feb 24 08:13:58 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FF9428C1E5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 08:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.156
X-Spam-Level: 
X-Spam-Status: No, score=-1.156 tagged_above=-999 required=5 tests=[AWL=-0.661, 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 7hizQbVo9jZ2 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 08:13:56 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4182728C1DF for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 08:13:56 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkJqT-000Fqd-NW for radiusext-data0@psg.com; Wed, 24 Feb 2010 16:12:17 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkJqR-000FqE-BO for radiusext@ops.ietf.org; Wed, 24 Feb 2010 16:12:15 +0000
Message-ID: <4B854FDD.3080203@deployingradius.com>
Date: Wed, 24 Feb 2010 17:12:13 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11
References: <7735D8F6-FD9E-43AB-B655-07AD53481AA5@bridgewatersystems.com> <BLU137-DS7B020CCE718F044DE2A1793430@phx.gbl> <4B85341E.4050902@deployingradius.com>
In-Reply-To: <4B85341E.4050902@deployingradius.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan DeKok wrote:

  To summarize: the comments can be divided into a few rough areas:

- minor fixes
  - these should be addressed

- requests to define *new* methods/architectures in the document
  - these should be rejected

- requests to change the document or add explanations
  - I would appreciate suggested text.

  As editor, I welcome suggestions from the WG on how to improve the
document.  I have offered many suggestions in the past, and given the
volume of requested changes, ask for guidance from the WG on what to do
next.

  Alan DeKok.

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

From owner-radiusext@ops.ietf.org  Wed Feb 24 08:48:52 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4301A28C1D5 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 08:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.964
X-Spam-Level: 
X-Spam-Status: No, score=-0.964 tagged_above=-999 required=5 tests=[AWL=-0.469, 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 WeCsrvd0bKNR for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 08:48:50 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6A05728C182 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 08:48:50 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkKMN-000KQZ-O1 for radiusext-data0@psg.com; Wed, 24 Feb 2010 16:45:15 +0000
Received: from [65.55.116.14] (helo=blu0-omc1-s3.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NkKML-000KQ9-9n for radiusext@ops.ietf.org; Wed, 24 Feb 2010 16:45:13 +0000
Received: from BLU137-DS4 ([65.55.116.9]) by blu0-omc1-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Feb 2010 08:45:12 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS471C4718699DFD2B3E87493410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>
CC: <radiusext@ops.ietf.org>
References: <7735D8F6-FD9E-43AB-B655-07AD53481AA5@bridgewatersystems.com> <BLU137-DS7B020CCE718F044DE2A1793430@phx.gbl> <4B85341E.4050902@deployingradius.com> <4B854FDD.3080203@deployingradius.com>
In-Reply-To: <4B854FDD.3080203@deployingradius.com>
Subject: RE: FW: Review of Radius Guidelines 11
Date: Wed, 24 Feb 2010 08:45:57 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq1bLmx0z7jpBMbSYml+AmkmZj9xAAA+fYQ
Content-Language: en-us
X-OriginalArrivalTime: 24 Feb 2010 16:45:12.0672 (UTC) FILETIME=[BBE3E600:01CAB570]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

In terms of process, my suggestion is to discuss proposed changes to the
text on the list, and incorporate them within a -12 version to be submitted
by the deadline.  At IETF 77, we can then go over what additional changes
(if any) are necessary. 

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Alan DeKok
Sent: Wednesday, February 24, 2010 8:12 AM
To: Bernard Aboba
Cc: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11

Alan DeKok wrote:

  To summarize: the comments can be divided into a few rough areas:

- minor fixes
  - these should be addressed

- requests to define *new* methods/architectures in the document
  - these should be rejected

- requests to change the document or add explanations
  - I would appreciate suggested text.

  As editor, I welcome suggestions from the WG on how to improve the
document.  I have offered many suggestions in the past, and given the
volume of requested changes, ask for guidance from the WG on what to do
next.

  Alan DeKok.

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


--
to unsubscribe send a message to 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 Feb 24 13:23:17 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4370F3A84EC for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 13:23:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level: 
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[AWL=-0.624, 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 0f8gN1KmKoJa for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 13:23:16 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id F34AB3A831D for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 13:23:09 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkOfw-0007zH-Eg for radiusext-data0@psg.com; Wed, 24 Feb 2010 21:21:44 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkOft-0007yR-HC for radiusext@ops.ietf.org; Wed, 24 Feb 2010 21:21:41 +0000
Message-ID: <4B859860.9060001@deployingradius.com>
Date: Wed, 24 Feb 2010 22:21:36 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>,  Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?ISO-8859-1?Q?Varga_B?= =?ISO-8859-1?Q?al=E1zs?= <varga.balazs@telekom.hu>
Subject: Re: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Maglione Roberta wrote:
> Hi All,
>      we have just posted a new draft about RADIUS attributes for IPv6 statistics:
> http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
> Your comments are welcome.

   [RFC2866]and [RFC2869] specify RADIUS attributes to be used for
   carrying statistics regarding how many packets/octets/Gigawords have
   been sent/received over a port while delivering the service.  These
   attributes are IPv4 specific.

 That isn't correct.  RFC 2866 has *no* references to IPv4.  I suggest
deleting it.

   With the introduction of the IPv6 in
   broadband environment there is a need to be able to collect IPv4 and
   IPv6 statistics separately, thus new RADIUS attribute have to be
   defined.

 That might be true, and is a better problem statement than the previous
sentence.

  However, there is a LOT of information that could potentially be
carried in RADIUS accounting.  There have been requests to track data
down to specific applications and/or ports.  These suggestions have a
number of problems in practice.  (Which I won't go into here.)

4. Operation
...

  This section repeats existing definitions of RADIUS accounting.  I
suggest deleting it.


5.
...
   This section defines six new RADIUS attributes for IPv6 statistics.
   These attributes correspond to the attributes Acct-Input-Octets,
   Acct-Output-Octets,Acct-Input-Packets, Acct-Output-Packets, Acct-
   Input-Gigawords and Acct-Output-Gigawords as defined in
   [RFC2866][RFC2869] that are defined for collecting combined
   statistics for IPv4 and IPv6 traffic.

  This last sentence directly contradicts the sentence in the
introduction.  It would be good to have the document internally consistent.


   Since service providers may
   like to collect statistics for IPv6 traffic separately from IPv4
   traffic, separate counters for IPv6 traffic are needed.

  Repetition of the justification is unnecessary, and can be deleted.

  It would be good to add a sentence or two on how these attributes
interact with the existing counters.  e.g. how IPv4-specific counters
can be derived.

  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 Feb 24 14:06:47 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61C383A8532 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 14:06:47 -0800 (PST)
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.591, 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 0PUQA2s0cGku for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 14:06:45 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 724FD28C176 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 14:06:45 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkPN3-000CBZ-K2 for radiusext-data0@psg.com; Wed, 24 Feb 2010 22:06:17 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkPN1-000CBH-7A for radiusext@ops.ietf.org; Wed, 24 Feb 2010 22:06:15 +0000
Message-ID: <4B85A2D5.2020906@deployingradius.com>
Date: Wed, 24 Feb 2010 23:06:13 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Ignacio Goyret <i.goyret@alcatel-lucent.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl> <4B7AB10C.5030800@deployingradius.com> <201002242136.o1OLaSc0017148@cliff.eng.ascend.com>
In-Reply-To: <201002242136.o1OLaSc0017148@cliff.eng.ascend.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Ignacio Goyret wrote:
>>> [BA] You might say that the server MUST ignore other attributes. 
>                                       ^^^^
> Why MUST?
> 
> Shouldn't that be up to the server's local policy?
> What if the server needs/wants to check one of those extra attributes?
> (possibly including vendor-specific attributes)

  What are the checks for?  The only possible decision that can be made
is whether or not to reply to a Status-Server.

  Would it be useful to allow a server to *not* respond, if it saw a VSA
with a particular value?

  I could see this being useful for checking "liveliness" of upstream
realms.  But some providers have dozens, if not hundreds of realms, and
this functionality gets awkward pretty quickly.

  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 Feb 24 14:27:34 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F9C03A85CD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 14:27:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.66
X-Spam-Level: 
X-Spam-Status: No, score=-0.66 tagged_above=-999 required=5 tests=[AWL=-0.784, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_SORBS_WEB=0.619, 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 ZA5nUNl9N4gp for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 14:27:33 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1F5783A8557 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 14:27:33 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkPhH-000EGL-05 for radiusext-data0@psg.com; Wed, 24 Feb 2010 22:27:11 +0000
Received: from [65.55.116.45] (helo=blu0-omc1-s34.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NkPhE-000EFo-G6 for radiusext@ops.ietf.org; Wed, 24 Feb 2010 22:27:08 +0000
Received: from BLU137-DS4 ([65.55.116.8]) by blu0-omc1-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Feb 2010 14:27:07 -0800
X-Originating-IP: [131.107.0.77]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS451546B1E94A9DAD9779993410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>, "'Ignacio Goyret'" <i.goyret@alcatel-lucent.com>
CC: <radiusext@ops.ietf.org>
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl> <4B7AB10C.5030800@deployingradius.com> <201002242136.o1OLaSc0017148@cliff.eng.ascend.com> <4B85A2D5.2020906@deployingradius.com>
In-Reply-To: <4B85A2D5.2020906@deployingradius.com>
Subject: RE: Review of draft-ietf-radext-status-server-05 (Part II)
Date: Wed, 24 Feb 2010 14:27:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq1nfuntwwGqiS6SBCzHY8YE4NrxQAAl/fA
Content-Language: en-us
X-OriginalArrivalTime: 24 Feb 2010 22:27:07.0530 (UTC) FILETIME=[7FB2CEA0:01CAB5A0]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan said:

"  I could see this being useful for checking "liveliness" of upstream
realms.  But some providers have dozens, if not hundreds of realms, and
this functionality gets awkward pretty quickly."

[BA] Since Status-Server isn't forwardable, I'm not sure how it could help
with the realm reachability issue.  


--
to unsubscribe send a message to 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 Feb 24 22:34:23 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A95C73A8639 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 22:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.057
X-Spam-Level: 
X-Spam-Status: No, score=-1.057 tagged_above=-999 required=5 tests=[AWL=-0.562, 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 7ACACMKtOW2y for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 22:34:22 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 4340D3A863F for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 22:34:21 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkXGy-0008QF-6k for radiusext-data0@psg.com; Thu, 25 Feb 2010 06:32:32 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkXGv-0008Pr-Pw for radiusext@ops.ietf.org; Thu, 25 Feb 2010 06:32:29 +0000
Message-ID: <4B86197B.20906@deployingradius.com>
Date: Thu, 25 Feb 2010 07:32:27 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: 'Ignacio Goyret' <i.goyret@alcatel-lucent.com>,  radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl> <4B7AB10C.5030800@deployingradius.com> <201002242136.o1OLaSc0017148@cliff.eng.ascend.com> <4B85A2D5.2020906@deployingradius.com> <BLU137-DS451546B1E94A9DAD9779993410@phx.gbl>
In-Reply-To: <BLU137-DS451546B1E94A9DAD9779993410@phx.gbl>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Bernard Aboba wrote:
> Alan said:
> [BA] Since Status-Server isn't forwardable, I'm not sure how it could help
> with the realm reachability issue.  

  Say a NAS has two paths to realm FOO.  It can ask each one; can *you*
reach FOO?  The one that answers "yes" has packets sent to it.

  The Status-Server isn't being forwarded.  But the NAS still finds out
the proxies view of the reachability of realm FOO.

  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 Feb 24 23:06:20 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E057C3A8352 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 23:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.03
X-Spam-Level: 
X-Spam-Status: No, score=-1.03 tagged_above=-999 required=5 tests=[AWL=-0.535, 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 qYWKHubbt81q for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 24 Feb 2010 23:06:20 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E62F33A82A8 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 24 Feb 2010 23:06:19 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkXn6-000C7r-KP for radiusext-data0@psg.com; Thu, 25 Feb 2010 07:05:44 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkXn4-000C6R-49 for radiusext@ops.ietf.org; Thu, 25 Feb 2010 07:05:42 +0000
Message-ID: <4B862144.6050704@deployingradius.com>
Date: Thu, 25 Feb 2010 08:05:40 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Ignacio Goyret <i.goyret@alcatel-lucent.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl> <4B7AB10C.5030800@deployingradius.com> <201002242136.o1OLaSc0017148@cliff.eng.ascend.com> <4B85A2D5.2020906@deployingradius.com> <201002242229.o1OMTVqo019416@cliff.eng.ascend.com>
In-Reply-To: <201002242229.o1OMTVqo019416@cliff.eng.ascend.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Ignacio Goyret wrote:
> I'm just questioning the choice of MUST vs SHOULD.
> I've seen far too many specs that include MUSTs that should
> have been less restrictive.

  I agree.

> So, unless it hurts interoperability, I'd suggest replacing
> that MUST with a SHOULD, leaving the door open for servers
> to use other attributes, if their admins choose to do so.

  It won't hurt interoperability, so far as I can tell.

> Makes sense?

  Yes.

  I don't have strong opinions either way.

  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 Feb 25 00:44:13 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 346F928C128 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 00:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.412
X-Spam-Level: 
X-Spam-Status: No, score=-0.412 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, 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 dr7Yc5OkXlPH for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 00:44:12 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E1E5E3A865A for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 25 Feb 2010 00:44:11 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkZHX-000Lhc-W1 for radiusext-data0@psg.com; Thu, 25 Feb 2010 08:41:16 +0000
Received: from [217.169.121.21] (helo=GRFEDG702RM001.telecomitalia.it) by psg.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.71 (FreeBSD)) (envelope-from <roberta.maglione@telecomitalia.it>) id 1NkZHR-000LgB-Aj for radiusext@ops.ietf.org; Thu, 25 Feb 2010 08:41:09 +0000
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 25 Feb 2010 09:41:06 +0100
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by grfhub703rm001.griffon.local (10.19.3.10) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 25 Feb 2010 09:41:05 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by grfhub701ba020.griffon.local ([10.188.101.111]) with mapi; Thu, 25 Feb 2010 09:41:05 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Alan DeKok' <aland@deployingradius.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Thu, 25 Feb 2010 09:41:04 +0100
Subject: RE: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq1l1nTYyKCMXOGS8O53zgkHYE6UgAXeG1w
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7E61FC79@GRFMBX704BA020.griffon.local>
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <4B859860.9060001@deployingradius.com>
In-Reply-To: <4B859860.9060001@deployingradius.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hello Alan,
    thanks for your comments.

-----Original Message-----
From: Alan DeKok [mailto:aland@deployingradius.com]
Sent: Wednesday, February 24, 2010 10:22 PM
To: Maglione Roberta
Cc: radiusext@ops.ietf.org; Alan Kavanagh; Suresh Krishnan; Varga Bal=E1zs
Subject: Re: FW: New Version Notification for draft-maglione-radext-ipv6-ac=
ct-extensions-00

Maglione Roberta wrote:
> Hi All,
>      we have just posted a new draft about RADIUS attributes for IPv6 sta=
tistics:
> http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
> Your comments are welcome.

   [RFC2866]and [RFC2869] specify RADIUS attributes to be used for
   carrying statistics regarding how many packets/octets/Gigawords have
   been sent/received over a port while delivering the service.  These
   attributes are IPv4 specific.

 That isn't correct.  RFC 2866 has *no* references to IPv4.  I suggest
deleting it.

[RM] ok, we will delete it

   With the introduction of the IPv6 in
   broadband environment there is a need to be able to collect IPv4 and
   IPv6 statistics separately, thus new RADIUS attribute have to be
   defined.

 That might be true, and is a better problem statement than the previous
sentence.

[RM] This is the main intent of document

  However, there is a LOT of information that could potentially be
carried in RADIUS accounting.  There have been requests to track data
down to specific applications and/or ports.  These suggestions have a
number of problems in practice.  (Which I won't go into here.)


4. Operation
...

  This section repeats existing definitions of RADIUS accounting.  I
suggest deleting it.


5.
...
   This section defines six new RADIUS attributes for IPv6 statistics.
   These attributes correspond to the attributes Acct-Input-Octets,
   Acct-Output-Octets,Acct-Input-Packets, Acct-Output-Packets, Acct-
   Input-Gigawords and Acct-Output-Gigawords as defined in
   [RFC2866][RFC2869] that are defined for collecting combined
   statistics for IPv4 and IPv6 traffic.

  This last sentence directly contradicts the sentence in the
introduction.  It would be good to have the document internally consistent.

[RM] We will re-word this sentence to make it consistent

   Since service providers may
   like to collect statistics for IPv6 traffic separately from IPv4
   traffic, separate counters for IPv6 traffic are needed.

  Repetition of the justification is unnecessary, and can be deleted.

  It would be good to add a sentence or two on how these attributes
interact with the existing counters.  e.g. how IPv4-specific counters
can be derived.

[RM] ok we will add it

Thanks,
Roberta

  Alan DeKok.

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, 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  Thu Feb 25 04:20:18 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B7583A86C6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 04:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 ULUVxrwsgKsU for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 04:20:17 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8BA233A86C7 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 25 Feb 2010 04:20:16 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nkcez-000NKd-Iz for radiusext-data0@psg.com; Thu, 25 Feb 2010 12:17:41 +0000
Received: from [217.5.214.110] (helo=tcmail53.telekom.de) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <Olaf.Bonness@telekom.de>) id 1Nkcew-000NJF-VT for radiusext@ops.ietf.org; Thu, 25 Feb 2010 12:17:39 +0000
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail51.telekom.de with ESMTP; 25 Feb 2010 13:17:34 +0100
Received: from S4DE9JSAACY.ost.t-com.de ([10.125.177.233]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Feb 2010 13:17:35 +0100
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_01CAB614.8394DA26"
Subject: AW: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Date: Thu, 25 Feb 2010 13:17:35 +0100
Message-ID: <D83105B2AC38794CB78ADA2959F2C44F03F07461@S4DE9JSAACY.ost.t-com.de>
In-Reply-To: <A16B9A4922C4A544A94565E870362B5001531094@XMB-AMS-111.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
thread-index: Acq0xT8uBPxYy20STV+Ko3u61xMO7gAmQM/QAC1I/qA=
References: <A16B9A4922C4A544A94565E870362B5001531094@XMB-AMS-111.cisco.com>
From: <Olaf.Bonness@telekom.de>
To: <radiusext@ops.ietf.org>
X-OriginalArrivalTime: 25 Feb 2010 12:17:35.0811 (UTC) FILETIME=[83AB1930:01CAB614]
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_01CAB614.8394DA26
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

 I think SPs that are operating access networks (like DSL) need to =
transport these attributes between NAS and their Radius servers and am =
that's why in favour to adopt this I-D as WG item.
Regards
    Olaf
=20
  _____ =20

From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] =
On Behalf Of Bernard Aboba
Sent: 23 February 2010 21:18
To: radiusext@ops.ietf.org
Subject: Call for adoption of "RADIUS Attributes for IPv6 Access =
Networks"



During the RADEXT Virtual Interim, we discussed adoption of "RADIUS =
Attributes for IPv6 Access Networks" as a RADEXT WG work item.=20

=20

We would now like to request mailing list confirmation of the decision =
to adopt this draft.=20

=20

The document is available here:

http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02

=20

If you have an opinion on the adoption  of this document as a RADEXT WG =
work item, please reply to this email.=20

=20

=20

=20


------_=_NextPart_001_01CAB614.8394DA26
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D608370912-25022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;I think SPs that are operating access =
networks (like=20
DSL) need to transport these attributes between NAS and their Radius =
servers and=20
am that's why in favour to adopt this I-D as WG =
item.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D608370912-25022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D608370912-25022010>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>Olaf</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D608370912-25022010>&nbsp;</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=20
owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] <B>On =
Behalf=20
Of </B>Bernard Aboba<BR><B>Sent:</B> 23 February 2010 =
21:18<BR><B>To:</B>=20
radiusext@ops.ietf.org<BR><B>Subject:</B> Call for adoption of "RADIUS=20
Attributes for IPv6 Access Networks"<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal>During the RADEXT Virtual Interim, we discussed =
adoption of=20
  "RADIUS Attributes for IPv6 Access Networks" as a RADEXT WG work item. =

  <o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>We would now like to request mailing list =
confirmation of=20
  the decision to adopt this draft. <o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>The document is available here:<o:p></o:p></P>
  <P=20
  =
class=3DMsoNormal>http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-=
access-02<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>If you have an opinion on the adoption&nbsp; of =
this=20
  document as a RADEXT WG work item, please reply to this email. =
<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P =
class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAB614.8394DA26--

--
to unsubscribe send a message to 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 Feb 25 09:52:11 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FD213A84FE for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 09:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.963
X-Spam-Level: 
X-Spam-Status: No, score=-0.963 tagged_above=-999 required=5 tests=[AWL=-0.468, 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 7DSMPbYNei61 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 09:52:10 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 6F9D93A84A3 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 25 Feb 2010 09:52:03 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nkhq5-000Aw0-Qd for radiusext-data0@psg.com; Thu, 25 Feb 2010 17:49:29 +0000
Received: from [65.55.111.171] (helo=blu0-omc4-s32.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1Nkhq1-000AvZ-6q for radiusext@ops.ietf.org; Thu, 25 Feb 2010 17:49:25 +0000
Received: from BLU137-DS7 ([65.55.111.135]) by blu0-omc4-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Feb 2010 09:49:24 -0800
X-Originating-IP: [131.107.0.77]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS7D5C366B3876B0A69BC8693400@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>
CC: "'Ignacio Goyret'" <i.goyret@alcatel-lucent.com>, <radiusext@ops.ietf.org>
References: <BLU137-W6861B435730E1D4BA388293520@phx.gbl> <4B7AB10C.5030800@deployingradius.com> <201002242136.o1OLaSc0017148@cliff.eng.ascend.com> <4B85A2D5.2020906@deployingradius.com> <BLU137-DS451546B1E94A9DAD9779993410@phx.gbl> <4B86197B.20906@deployingradius.com>
In-Reply-To: <4B86197B.20906@deployingradius.com>
Subject: RE: Review of draft-ietf-radext-status-server-05 (Part II)
Date: Thu, 25 Feb 2010 09:49:23 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acq15EzZkptTkcTyQP+SHbQKdpv3PgAXiJRg
Content-Language: en-us
X-OriginalArrivalTime: 25 Feb 2010 17:49:24.0264 (UTC) FILETIME=[DE07F280:01CAB642]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Alan said:

"  Say a NAS has two paths to realm FOO.  It can ask each one; can *you*
reach FOO?  The one that answers "yes" has packets sent to it.

  The Status-Server isn't being forwarded.  But the NAS still finds out
the proxies view of the reachability of realm FOO."


[BA] The effectiveness of this will depend on the definition of
"reachability" in this context. For example, does a "yes" mean:

1. "Proxy has realm FOO in its routing table"  OR
2. "Proxy got a response from realm FOO in the last X seconds" OR
3. "Proxy tested reachability to realm FOO as a result of receiving
Status-Server with a realm request and got a response"


--
to unsubscribe send a message to 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 Feb 25 09:59:16 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 527323A86F6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 09:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.659
X-Spam-Level: 
X-Spam-Status: No, score=-0.659 tagged_above=-999 required=5 tests=[AWL=-0.765, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_72=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 GUiqbWohadqe for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 09:59:15 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9D5433A77DE for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 25 Feb 2010 09:59:14 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkhxL-000Brf-Jj for radiusext-data0@psg.com; Thu, 25 Feb 2010 17:56:59 +0000
Received: from [65.55.116.16] (helo=blu0-omc1-s5.blu0.hotmail.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <bernard_aboba@hotmail.com>) id 1NkhxE-000BpI-Rh for radiusext@ops.ietf.org; Thu, 25 Feb 2010 17:56:53 +0000
Received: from BLU137-W23 ([65.55.116.7]) by blu0-omc1-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Feb 2010 09:56:52 -0800
Message-ID: <BLU137-W2396B4A27DAEA704629FC793400@phx.gbl>
Content-Type: multipart/alternative; boundary="_29310c53-70ee-4345-99a0-ac23683b7125_"
X-Originating-IP: [131.107.0.86]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: FW: draft-ietf-radext-dynamic-discovery-01.txt
Date: Thu, 25 Feb 2010 09:56:52 -0800
Importance: Normal
In-Reply-To: <4B868F6F.2010303@stefan-winter.de>
References: <4B02F005.3060407@thinkingcat.com>,<4B868F6F.2010303@stefan-winter.de>
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Feb 2010 17:56:52.0303 (UTC) FILETIME=[E91545F0:01CAB643]
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

--_29310c53-70ee-4345-99a0-ac23683b7125_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


> Date: Thu=2C 25 Feb 2010 15:55:43 +0100
> From: mail@stefan-winter.de
> To: leslie@thinkingcat.com
> CC: mikem@open.com.au=3B Bernard_Aboba@hotmail.com=3B d.b.nelson@comcast.=
net
> Subject: Re: draft-ietf-radext-dynamic-discovery-01.txt
>=20
> Hi=2C
>=20
> sorry for being so late to get back to you.
>=20
> > You may find that S-NAPTR (RFC3958) does the trick for you.
>=20
> Indeed it does! After looking through 3958=2C it looks like an almost
> perfect match. It's not quite a 100%=2C but if I may=2C I'd like to solic=
it
> your opinion on what could be done to make it so. In very short terms:
>=20
> The service my draft describes is "roaming" based on NAI user names
> (which are derived from DNS domain names). It can=2C among others=2C be u=
sed
> with the protocol RADIUS over TLS. On first glance=2C it would thus seem
> prudent to register a service "roaming" and an application type
> "radius.tls" for the S-NAPTR DDDS application=2C like
>=20
> host -t NAPTR restena.lu
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming:radius.tls" "" radius-1.r=
estena.lu.
>=20
>=20
> That is unfortunately barely short of what's needed. Roaming consortia
> are usually selective about who they peer with. It may be possible that
> one realm participates in "n" roaming consortia=2C and thus has multiple
> NAPTR records for those. Iterating through all NAPTR resolutions and
> trying which TLS connection will actually be accepted is one way of
> course=2C but not very efficient and might cause end-user delays. A uniqu=
e
> per-consortium label would be beneficial here.
>=20
> The short and cheap solution is to use a label "x-consortium" to avoid
> writing an RFC for the consortium and circumvent IANA registration. In
> our specific case=2C we could do x-eduroam.
>=20
> But I was wondering about a more elegant solution to this=2C that doesn't
> force operators to flee to dimension x-. If the service label were to
> contain a sub-space with arbitrary but unique consortium handles=2C this
> would be rather elegant. I'm envisaging sth like
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#eduroam:radius.tls" "" ra=
dius-1.restena.lu.
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#3gpp:radius.tls" "" radiu=
s-1.restena.lu.
> restena.lu has NAPTR record 100 10 "a" "roaming#wimax:radius.tls" "" radi=
us-1.restena.lu.
>=20
>=20
> This would of course require charging IANA with handling a "sub-registry"=
 below "roaming"=2C and I'm not sure if that's what's wanted. To take the l=
oad off IANA=2C it can also be imagined to ensure uniqueness of the sub-spa=
ce by piggybacking it on an established namespace registry=2C like DNS name=
s of the consortia. Like
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#eduroam.org:radius.tls" "=
" radius-1.restena.lu.
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#3gppnetworks.org:radius.t=
ls" "" radius-1.restena.lu.
> restena.lu has NAPTR record 100 10 "a" "roaming#wimaxforum.com:radius.tls=
" "" radius-1.restena.lu.
>=20
> Do you think such a "wildcard" subspace allocation would fly?
>=20
> Thanks for any advice=2C
>=20
> Stefan Winter
>=20
>=20
 		 	   		  =

--_29310c53-70ee-4345-99a0-ac23683b7125_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
&gt=3B Date: Thu=2C 25 Feb 2010 15:55:43 +0100<br>&gt=3B From: mail@stefan-=
winter.de<br>&gt=3B To: leslie@thinkingcat.com<br>&gt=3B CC: mikem@open.com=
.au=3B Bernard_Aboba@hotmail.com=3B d.b.nelson@comcast.net<br>&gt=3B Subjec=
t: Re: draft-ietf-radext-dynamic-discovery-01.txt<br>&gt=3B <br>&gt=3B Hi=
=2C<br>&gt=3B <br>&gt=3B sorry for being so late to get back to you.<br>&gt=
=3B <br>&gt=3B &gt=3B You may find that S-NAPTR (RFC3958) does the trick fo=
r you.<br>&gt=3B <br>&gt=3B Indeed it does! After looking through 3958=2C i=
t looks like an almost<br>&gt=3B perfect match. It's not quite a 100%=2C bu=
t if I may=2C I'd like to solicit<br>&gt=3B your opinion on what could be d=
one to make it so. In very short terms:<br>&gt=3B <br>&gt=3B The service my=
 draft describes is "roaming" based on NAI user names<br>&gt=3B (which are =
derived from DNS domain names). It can=2C among others=2C be used<br>&gt=3B=
 with the protocol RADIUS over TLS. On first glance=2C it would thus seem<b=
r>&gt=3B prudent to register a service "roaming" and an application type<br=
>&gt=3B "radius.tls" for the S-NAPTR DDDS application=2C like<br>&gt=3B <br=
>&gt=3B host -t NAPTR restena.lu<br>&gt=3B <br>&gt=3B restena.lu has NAPTR =
record 100 10 "a" "roaming:radius.tls" "" radius-1.restena.lu.<br>&gt=3B <b=
r>&gt=3B <br>&gt=3B That is unfortunately barely short of what's needed. Ro=
aming consortia<br>&gt=3B are usually selective about who they peer with. I=
t may be possible that<br>&gt=3B one realm participates in "n" roaming cons=
ortia=2C and thus has multiple<br>&gt=3B NAPTR records for those. Iterating=
 through all NAPTR resolutions and<br>&gt=3B trying which TLS connection wi=
ll actually be accepted is one way of<br>&gt=3B course=2C but not very effi=
cient and might cause end-user delays. A unique<br>&gt=3B per-consortium la=
bel would be beneficial here.<br>&gt=3B <br>&gt=3B The short and cheap solu=
tion is to use a label "x-consortium" to avoid<br>&gt=3B writing an RFC for=
 the consortium and circumvent IANA registration. In<br>&gt=3B our specific=
 case=2C we could do x-eduroam.<br>&gt=3B <br>&gt=3B But I was wondering ab=
out a more elegant solution to this=2C that doesn't<br>&gt=3B force operato=
rs to flee to dimension x-. If the service label were to<br>&gt=3B contain =
a sub-space with arbitrary but unique consortium handles=2C this<br>&gt=3B =
would be rather elegant. I'm envisaging sth like<br>&gt=3B <br>&gt=3B reste=
na.lu has NAPTR record 100 10 "a" "roaming#eduroam:radius.tls" "" radius-1.=
restena.lu.<br>&gt=3B <br>&gt=3B restena.lu has NAPTR record 100 10 "a" "ro=
aming#3gpp:radius.tls" "" radius-1.restena.lu.<br>&gt=3B restena.lu has NAP=
TR record 100 10 "a" "roaming#wimax:radius.tls" "" radius-1.restena.lu.<br>=
&gt=3B <br>&gt=3B <br>&gt=3B This would of course require charging IANA wit=
h handling a "sub-registry" below "roaming"=2C and I'm not sure if that's w=
hat's wanted. To take the load off IANA=2C it can also be imagined to ensur=
e uniqueness of the sub-space by piggybacking it on an established namespac=
e registry=2C like DNS names of the consortia. Like<br>&gt=3B <br>&gt=3B re=
stena.lu has NAPTR record 100 10 "a" "roaming#eduroam.org:radius.tls" "" ra=
dius-1.restena.lu.<br>&gt=3B <br>&gt=3B restena.lu has NAPTR record 100 10 =
"a" "roaming#3gppnetworks.org:radius.tls" "" radius-1.restena.lu.<br>&gt=3B=
 restena.lu has NAPTR record 100 10 "a" "roaming#wimaxforum.com:radius.tls"=
 "" radius-1.restena.lu.<br>&gt=3B <br>&gt=3B Do you think such a "wildcard=
" subspace allocation would fly?<br>&gt=3B <br>&gt=3B Thanks for any advice=
=2C<br>&gt=3B <br>&gt=3B Stefan Winter<br>&gt=3B <br>&gt=3B <br> 		 	   		 =
 </body>
</html>=

--_29310c53-70ee-4345-99a0-ac23683b7125_--

--
to unsubscribe send a message to 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 Feb 25 12:03:48 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EA453A7B51 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 12:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.385
X-Spam-Level: 
X-Spam-Status: No, score=-5.385 tagged_above=-999 required=5 tests=[AWL=-0.890, 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 pUcVrfSNeBjW for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Thu, 25 Feb 2010 12:03:46 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 455D328C2A9 for <radext-archive-IeZ9sae2@lists.ietf.org>; Thu, 25 Feb 2010 12:03:24 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkjuL-00012T-MA for radiusext-data0@psg.com; Thu, 25 Feb 2010 20:02:01 +0000
Received: from [216.82.254.195] (helo=mail200.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1NkjuJ-00011v-0F for radiusext@ops.ietf.org; Thu, 25 Feb 2010 20:01:59 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-5.tower-200.messagelabs.com!1267128117!78985084!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 3133 invoked from network); 25 Feb 2010 20:01:57 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-5.tower-200.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2010 20:01:57 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Thu, 25 Feb 2010 15:01:57 -0500
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan Kavanagh <alan.kavanagh@ericsson.com>
CC: Suresh Krishnan <suresh.krishnan@ericsson.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Thu, 25 Feb 2010 15:01:55 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq2VWIw48L/T/CfTCOvPlPcWeVsGQ==
Message-ID: <8AC4AAEC-D587-4C84-A9E2-A56B9FC2776F@bridgewatersystems.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com> <4B843CD2.8080406@ericsson.com> <1456B38F-1724-4C35-BCE6-8E54E1A79D9E@bridgewatersystems.com> <1B6D0317D3AD964FBF3956DEFA3524D50482535481@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <1B6D0317D3AD964FBF3956DEFA3524D50482535481@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

On 23-02-2010, at 20:40 , Alan Kavanagh wrote:

> Hi Avi
>=20
>=20
>=20
> -----Original Message-----
> From: Avi Lior [mailto:avi@bridgewatersystems.com]=20
> Sent: February 23, 2010 5:03 PM
> To: Suresh Krishnan
> Cc: Maglione Roberta; radiusext@ops.ietf.org; Alan Kavanagh; Varga Bal=E1=
zs
> Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct=
-extensions-00
>=20
> Why do you need separate counters for IPv6?
>=20
> Is it because you want to have different counters for different IP techno=
logy at the same time in the accounting stream?
>>> A.K.--> it may be that you have some sessions that are IPv4 only as we =
have today, some sessions that are IPv6 only and some sessions for dual sta=
ck hosts where the SP wants to count the traffic volume seperately for IPv4=
 and IPv6 for stats purposes as one example. Also, in the dual stack host c=
ase, if the AAA assigns both IPv4/v6 Addresses, there are some cases that t=
he IPv4 address does not get assigned down to the end host until some spefi=
cied time x and as such we still want to count the IPv6 packets for an ongo=
ing current session.
>=20
> If yes there are other problems with that approach.  Accounting is used f=
or both volume and time accounting.  While having distinct volume counters =
for one technology may solve the volume aspect it does not address the time=
 aspect.  Consider the fact that even if you have both IPv4 and IPv6 enable=
d one may start at a different time then the other and one may stop at a di=
fferent time then the other.
>=20
>>> A.K.--> Agree as I noted above we agree on this and the intention of th=
e draft is primarily for volume based accounting.
Avi: Here I have an issue.  You can't solve the problem only for Volume Bas=
ed and even for volume based you are not solving the problem in general.  Y=
ou are only assuming that the device is getting one IPv4 and one IPv6 addre=
ss - that is not the case always.  The current model already supports Volum=
e Based and Time Based and other things.  The current model is to send an a=
ccounting packet for each IP session.
>=20
> There are other information elements that are accounted for that may be s=
pecific to a particular IP technology and not the other.
>=20
> As well, a user may have multiple IPv4 addresses and multiple IPv6 addres=
ses.
>=20
>>> A.K.--> Can you expand on this a little more, are you siting a prefix a=
s oppsoed to a 128-bit address?
Avi:  Regarding multiple IP addresses.  I am not talking about a prefix vs =
128-bit addresses.  That can always be true.  What I am talking about is a =
given session can be assigned multiple IPv4 addresses only, multiple IPv6 a=
ddresses only or any combination of multiple IPv4 and multiple IPv6 address=
es.  Your proposed solution can only handle the case where a single IPv4 an=
d/or Single IPv6 address is assigned.

>=20
> So I am concerned that you are not really addressing all the issues. =20
>=20
> Separate accounting streams per IP session solves these problems.
>=20
> What is the problem with having separate accounting streams per IP sessio=
n?
>=20
>>> A.K.--> nothing prevents you from doing that, but you still require to =
count IPv6 packets when you have a dual stack session that are logically co=
mbined at the NAS.
But I don't need to have distinct IPv6 counters.  You can do what you want =
to achieve without creation of distinct IPv6 counters.  My argument is that=
 you can do a better (better =3D more general flexible solution) job with t=
he current approach.


>=20
> //Alan
>=20
>> Hi Avi,
>>  Thanks for your comments.
>>=20
>> On 10-02-23 12:38 PM, Avi Lior wrote:
>>> Hi,'
>>>=20
>>> What makes you say that the existing accounting attributes for octet/pa=
cket counts are for IPv4 ?
>>=20
>> You are right. They are not. They are not protocol specific. We are=20
>> looking to define separate counters for IPv6. We will change the=20
>> wording in the draft to correspond to this.
>>=20
>>>=20
>>> Wouldn't the IP address contained in the IP session be sufficient to cr=
eate the context for the accounting message?
>>=20
>> This will require us to send two different messages (one for IPv6 only=20
>> and one for all protocols combined together).
>>=20
>> Thanks
>> Suresh
>=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  Fri Feb 26 01:32:56 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D13D3A84FD for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 01:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.006
X-Spam-Level: 
X-Spam-Status: No, score=-1.006 tagged_above=-999 required=5 tests=[AWL=-0.511, 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 DfEQcA+fhXe6 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 01:32:55 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5C5DD3A82BE for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 26 Feb 2010 01:32:55 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1NkwWc-0000sk-R8 for radiusext-data0@psg.com; Fri, 26 Feb 2010 09:30:22 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1NkwWX-0000qf-QO for radiusext@ops.ietf.org; Fri, 26 Feb 2010 09:30:18 +0000
Message-ID: <4B8794A7.3070105@deployingradius.com>
Date: Fri, 26 Feb 2010 10:30:15 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Maglione Roberta <roberta.maglione@telecomitalia.it>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>,  Suresh Krishnan <suresh.krishnan@ericsson.com>, =?ISO-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com>
In-Reply-To: <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Avi Lior wrote:
> Wouldn't the IP address contained in the IP session be sufficient to create the context for the accounting message?

  I suppose you could distinguish traffic IPv4/v6 for a session by
simply sending two different accounting streams.  e.g. one with an IPv4
address, and another with an IPv6 address.  The Acct-Multi-Session-Id
attribute would be good for this.

  e.g. for IPv4, send:

Framed-IP-Address = ...
Acct-Session-Id = 1234
Acct-Multi-Session-Id = foo
(octets / packet counters)

  For IPv6, send:

Framed-IPv6-Address = ... (presuming draft-lourdelet is standardized)
Acct-Session-Id = 5678
Acct-Multi-Session-Id = foo
(octets / packet counters)

  IIRC, this functionality is already used to track different kinds of
user traffic in certain environments.  It's not widely supported in the
ISP / dial-up environment, but it shouldn't be hard to add.

  Leveraging the existing functionality of RADIUS would mean that this
document is unnecessary.

  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 Feb 26 07:03:10 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30AFE28C14C for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 07:03:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.045
X-Spam-Level: 
X-Spam-Status: No, score=-0.045 tagged_above=-999 required=5 tests=[AWL=0.368, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, 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 q8J0YrK9H110 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 07:03:09 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id B806628C128 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 26 Feb 2010 07:03:08 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nl1gd-000LIT-7H for radiusext-data0@psg.com; Fri, 26 Feb 2010 15:01:03 +0000
Received: from [156.54.233.201] (helo=GRFEDG702BA020.telecomitalia.it) by psg.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.71 (FreeBSD)) (envelope-from <roberta.maglione@telecomitalia.it>) id 1Nl1gX-000LGy-3d for radiusext@ops.ietf.org; Fri, 26 Feb 2010 15:00:57 +0000
Received: from GRFHUB703BA020.griffon.local (10.188.101.113) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 26 Feb 2010 16:00:53 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by GRFHUB703BA020.griffon.local ([10.188.101.113]) with mapi; Fri, 26 Feb 2010 16:00:52 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Alan DeKok' <aland@deployingradius.com>, Avi Lior <avi@bridgewatersystems.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Fri, 26 Feb 2010 16:00:51 +0100
Subject: RE: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq2xlNRWlEz1mBZS3qffNv5QNj9yAALCbfQ
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7E61FC82@GRFMBX704BA020.griffon.local>
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com> <4B8794A7.3070105@deployingradius.com>
In-Reply-To: <4B8794A7.3070105@deployingradius.com>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Hi Alan,

>  I suppose you could distinguish traffic IPv4/v6 for a session by
> simply sending two different accounting streams.  e.g. one with an IPv4
> address, and another with an IPv6 address.  The Acct-Multi-Session-Id
> attribute would be good for this.

I'm not sure we could use the Acct-Multi-Session-Id for this purpose becaus=
e according to the definition in RFC 2866, Acct-Multi-Session-Id links toge=
ther multiple sessions with different Acct-Session-Id

"5.11  This attribute is a unique Accounting ID to make it easy to link
      together multiple related sessions in a log file.  Each session
      linked together would have a unique Acct-Session-Id but the same
      Acct-Multi-Session-Id."

While in the described scenario there is a single session that carries mult=
iple traffic flows: IPv4 and IPv6.

In addition I see an operational issue in terms of efficiency in doubling t=
he number of Accounting streams, because we usually have around 20-30 thous=
and active subscribers in a single NAS thus  sending the Accounting stream =
twice may affect the performance of the NAS.

Regards,
Roberta

-----Original Message-----
From: Alan DeKok [mailto:aland@deployingradius.com]
Sent: Friday, February 26, 2010 10:30 AM
To: Avi Lior
Cc: Maglione Roberta; radiusext@ops.ietf.org; Alan Kavanagh; Suresh Krishna=
n; Varga Bal=E1zs
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-e=
xtensions-00

Avi Lior wrote:
> Wouldn't the IP address contained in the IP session be sufficient to crea=
te the context for the accounting message?

  I suppose you could distinguish traffic IPv4/v6 for a session by
simply sending two different accounting streams.  e.g. one with an IPv4
address, and another with an IPv6 address.  The Acct-Multi-Session-Id
attribute would be good for this.

  e.g. for IPv4, send:

Framed-IP-Address =3D ...
Acct-Session-Id =3D 1234
Acct-Multi-Session-Id =3D foo
(octets / packet counters)

  For IPv6, send:

Framed-IPv6-Address =3D ... (presuming draft-lourdelet is standardized)
Acct-Session-Id =3D 5678
Acct-Multi-Session-Id =3D foo
(octets / packet counters)

  IIRC, this functionality is already used to track different kinds of
user traffic in certain environments.  It's not widely supported in the
ISP / dial-up environment, but it shouldn't be hard to add.

  Leveraging the existing functionality of RADIUS would mean that this
document is unnecessary.

  Alan DeKok.

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, 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 Feb 26 07:35:58 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4DF13A87BC for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 07:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.983
X-Spam-Level: 
X-Spam-Status: No, score=-0.983 tagged_above=-999 required=5 tests=[AWL=-0.488, 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 t1d6M5mRio5E for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 07:35:57 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 9864C3A87F0 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 26 Feb 2010 07:35:57 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nl2Dg-0000PZ-4b for radiusext-data0@psg.com; Fri, 26 Feb 2010 15:35:12 +0000
Received: from [88.191.76.128] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1Nl2DY-0000OE-W2 for radiusext@ops.ietf.org; Fri, 26 Feb 2010 15:35:05 +0000
Message-ID: <4B87EA27.2020206@deployingradius.com>
Date: Fri, 26 Feb 2010 16:35:03 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
CC: Avi Lior <avi@bridgewatersystems.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>,  Suresh Krishnan <suresh.krishnan@ericsson.com>, =?ISO-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
References: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local> <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com> <4B8794A7.3070105@deployingradius.com> <282BBE8A501E1F4DA9C775F964BB21FE3E7E61FC82@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3E7E61FC82@GRFMBX704BA020.griffon.local>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

Maglione Roberta wrote:
> I'm not sure we could use the Acct-Multi-Session-Id for this purpose because according to the definition in RFC 2866, Acct-Multi-Session-Id links together multiple sessions with different Acct-Session-Id
> 
> "5.11  This attribute is a unique Accounting ID to make it easy to link
>       together multiple related sessions in a log file.  Each session
>       linked together would have a unique Acct-Session-Id but the same
>       Acct-Multi-Session-Id."
> 
> While in the described scenario there is a single session that carries multiple traffic flows: IPv4 and IPv6.

  Yes, I understood that.  I still proposed the solution because:

(a) it works
(b) it's not actually forbidden by the RFCs
(c) it seems to be a practical use-case for Acct-Multi-Session-Id

> In addition I see an operational issue in terms of efficiency in doubling the number of Accounting streams, because we usually have around 20-30 thousand active subscribers in a single NAS thus  sending the Accounting stream twice may affect the performance of the NAS.

  RADIUS isn't perfect.  You have to make trade-offs somewhere.   The
choice is between more traffic for the NAS (but with well-defined
semantics), or more attributes in the standard space.

  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 Feb 26 08:27:31 2010
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4831228C1D4 for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 08:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.572
X-Spam-Level: 
X-Spam-Status: No, score=-4.572 tagged_above=-999 required=5 tests=[AWL=-1.577, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_ASCII0=1.5, 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 YmP152HGVBmw for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Fri, 26 Feb 2010 08:27:27 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3C07328C1D1 for <radext-archive-IeZ9sae2@lists.ietf.org>; Fri, 26 Feb 2010 08:27:27 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Nl31a-0008Fh-8q for radiusext-data0@psg.com; Fri, 26 Feb 2010 16:26:46 +0000
Received: from [216.82.241.83] (helo=mail37.messagelabs.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <avi@bridgewatersystems.com>) id 1Nl31X-0008FA-1p for radiusext@ops.ietf.org; Fri, 26 Feb 2010 16:26:43 +0000
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-6.tower-37.messagelabs.com!1267201592!39097069!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 1725 invoked from network); 26 Feb 2010 16:26:37 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-6.tower-37.messagelabs.com with RC4-SHA encrypted SMTP; 26 Feb 2010 16:26:37 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Fri, 26 Feb 2010 11:26:32 -0500
From: Avi Lior <avi@bridgewatersystems.com>
To: "'aland@deployingradius.com'" <aland@deployingradius.com>, "'roberta.maglione@telecomitalia.it'" <roberta.maglione@telecomitalia.it>
CC: "'radiusext@ops.ietf.org'" <radiusext@ops.ietf.org>, "'alan.kavanagh@ericsson.com'" <alan.kavanagh@ericsson.com>, "'suresh.krishnan@ericsson.com'" <suresh.krishnan@ericsson.com>, "'varga.balazs@telekom.hu'" <varga.balazs@telekom.hu>
Date: Fri, 26 Feb 2010 11:26:33 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq2+UXTaTa5E/pLT6q9ZmdALCDXmwABy98Z
Message-ID: <AF6CC6ADFC631348B9C22998A699B9EC02FAE0@m679t05.fpmis.bridgewatersys.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>

SSBhZ3JlZSB3aXRoIEFsYW4uICBUaGlzIGlzIGluZmFjdCB3aGF0IGlzIGJlaW5nIGRvbmUgaW4g
d2ltYXggYW5kIDNncHAyLg0KDQpGdXJ0aGVybW9yZSwgIGhhdmluZyBtdWx0aXBsZSBhY2NvdW50
aW5nIHNlc3Npb24gZm9yIGEgc2luZ2xlIGFjY2VzcyByZXF1ZXN0IGlzIGFsbG93ZWQgYW5kIGlz
IHVzZWQgLSBldmVuIGZvciBhIHNpbmdsZSBpcCBzZXNzaW9uLg0KDQpBcyBJIHNhaWQgYmVmb3Jl
LCB0aGUgcHJvcG9zZWQgc29sdXRpb24gZmFsbHMgc2hvcnQgaW4gbWFueSBhc3BlY3RzLg0KDQoN
Ci0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IEFsYW4gRGVLb2sgPGFsYW5kQGRl
cGxveWluZ3JhZGl1cy5jb20+DQpUbzogTWFnbGlvbmUgUm9iZXJ0YSA8cm9iZXJ0YS5tYWdsaW9u
ZUB0ZWxlY29taXRhbGlhLml0Pg0KQ2M6IEF2aSBMaW9yOyByYWRpdXNleHRAb3BzLmlldGYub3Jn
IDxyYWRpdXNleHRAb3BzLmlldGYub3JnPjsgQWxhbiBLYXZhbmFnaCA8YWxhbi5rYXZhbmFnaEBl
cmljc3Nvbi5jb20+OyBTdXJlc2ggS3Jpc2huYW4gPHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5j
b20+OyBWYXJnYSBCYWzDoXpzIDx2YXJnYS5iYWxhenNAdGVsZWtvbS5odT4NClNlbnQ6IEZyaSBG
ZWIgMjYgMTA6MzU6MDMgMjAxMApTdWJqZWN0OiBSZTogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9u
IGZvciBkcmFmdC1tYWdsaW9uZS1yYWRleHQtaXB2Ni1hY2N0LWV4dGVuc2lvbnMtMDANCg0KTWFn
bGlvbmUgUm9iZXJ0YSB3cm90ZToNCj4gSSdtIG5vdCBzdXJlIHdlIGNvdWxkIHVzZSB0aGUgQWNj
dC1NdWx0aS1TZXNzaW9uLUlkIGZvciB0aGlzIHB1cnBvc2UgYmVjYXVzZSBhY2NvcmRpbmcgdG8g
dGhlIGRlZmluaXRpb24gaW4gUkZDIDI4NjYsIEFjY3QtTXVsdGktU2Vzc2lvbi1JZCBsaW5rcyB0
b2dldGhlciBtdWx0aXBsZSBzZXNzaW9ucyB3aXRoIGRpZmZlcmVudCBBY2N0LVNlc3Npb24tSWQN
Cj4gDQo+ICI1LjExICBUaGlzIGF0dHJpYnV0ZSBpcyBhIHVuaXF1ZSBBY2NvdW50aW5nIElEIHRv
IG1ha2UgaXQgZWFzeSB0byBsaW5rDQo+ICAgICAgIHRvZ2V0aGVyIG11bHRpcGxlIHJlbGF0ZWQg
c2Vzc2lvbnMgaW4gYSBsb2cgZmlsZS4gIEVhY2ggc2Vzc2lvbg0KPiAgICAgICBsaW5rZWQgdG9n
ZXRoZXIgd291bGQgaGF2ZSBhIHVuaXF1ZSBBY2N0LVNlc3Npb24tSWQgYnV0IHRoZSBzYW1lDQo+
ICAgICAgIEFjY3QtTXVsdGktU2Vzc2lvbi1JZC4iDQo+IA0KPiBXaGlsZSBpbiB0aGUgZGVzY3Jp
YmVkIHNjZW5hcmlvIHRoZXJlIGlzIGEgc2luZ2xlIHNlc3Npb24gdGhhdCBjYXJyaWVzIG11bHRp
cGxlIHRyYWZmaWMgZmxvd3M6IElQdjQgYW5kIElQdjYuDQoNCiAgWWVzLCBJIHVuZGVyc3Rvb2Qg
dGhhdC4gIEkgc3RpbGwgcHJvcG9zZWQgdGhlIHNvbHV0aW9uIGJlY2F1c2U6DQoNCihhKSBpdCB3
b3Jrcw0KKGIpIGl0J3Mgbm90IGFjdHVhbGx5IGZvcmJpZGRlbiBieSB0aGUgUkZDcw0KKGMpIGl0
IHNlZW1zIHRvIGJlIGEgcHJhY3RpY2FsIHVzZS1jYXNlIGZvciBBY2N0LU11bHRpLVNlc3Npb24t
SWQNCg0KPiBJbiBhZGRpdGlvbiBJIHNlZSBhbiBvcGVyYXRpb25hbCBpc3N1ZSBpbiB0ZXJtcyBv
ZiBlZmZpY2llbmN5IGluIGRvdWJsaW5nIHRoZSBudW1iZXIgb2YgQWNjb3VudGluZyBzdHJlYW1z
LCBiZWNhdXNlIHdlIHVzdWFsbHkgaGF2ZSBhcm91bmQgMjAtMzAgdGhvdXNhbmQgYWN0aXZlIHN1
YnNjcmliZXJzIGluIGEgc2luZ2xlIE5BUyB0aHVzICBzZW5kaW5nIHRoZSBBY2NvdW50aW5nIHN0
cmVhbSB0d2ljZSBtYXkgYWZmZWN0IHRoZSBwZXJmb3JtYW5jZSBvZiB0aGUgTkFTLg0KDQogIFJB
RElVUyBpc24ndCBwZXJmZWN0LiAgWW91IGhhdmUgdG8gbWFrZSB0cmFkZS1vZmZzIHNvbWV3aGVy
ZS4gICBUaGUNCmNob2ljZSBpcyBiZXR3ZWVuIG1vcmUgdHJhZmZpYyBmb3IgdGhlIE5BUyAoYnV0
IHdpdGggd2VsbC1kZWZpbmVkDQpzZW1hbnRpY3MpLCBvciBtb3JlIGF0dHJpYnV0ZXMgaW4gdGhl
IHN0YW5kYXJkIHNwYWNlLg0KDQogIEFsYW4gRGVLb2suDQo=

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

Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 26 Feb 2010 16:27:41 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: "'aland@deployingradius.com'" <aland@deployingradius.com>, "'roberta.maglione@telecomitalia.it'" <roberta.maglione@telecomitalia.it>
CC: "'radiusext@ops.ietf.org'" <radiusext@ops.ietf.org>, "'alan.kavanagh@ericsson.com'" <alan.kavanagh@ericsson.com>, "'suresh.krishnan@ericsson.com'" <suresh.krishnan@ericsson.com>, "'varga.balazs@telekom.hu'" <varga.balazs@telekom.hu>
Date: Fri, 26 Feb 2010 11:26:33 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq2+UXTaTa5E/pLT6q9ZmdALCDXmwABy98Z
Message-ID: <AF6CC6ADFC631348B9C22998A699B9EC02FAE0@m679t05.fpmis.bridgewatersys.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0

SSBhZ3JlZSB3aXRoIEFsYW4uICBUaGlzIGlzIGluZmFjdCB3aGF0IGlzIGJlaW5nIGRvbmUgaW4g
d2ltYXggYW5kIDNncHAyLg0KDQpGdXJ0aGVybW9yZSwgIGhhdmluZyBtdWx0aXBsZSBhY2NvdW50
aW5nIHNlc3Npb24gZm9yIGEgc2luZ2xlIGFjY2VzcyByZXF1ZXN0IGlzIGFsbG93ZWQgYW5kIGlz
IHVzZWQgLSBldmVuIGZvciBhIHNpbmdsZSBpcCBzZXNzaW9uLg0KDQpBcyBJIHNhaWQgYmVmb3Jl
LCB0aGUgcHJvcG9zZWQgc29sdXRpb24gZmFsbHMgc2hvcnQgaW4gbWFueSBhc3BlY3RzLg0KDQoN
Ci0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IEFsYW4gRGVLb2sgPGFsYW5kQGRl
cGxveWluZ3JhZGl1cy5jb20+DQpUbzogTWFnbGlvbmUgUm9iZXJ0YSA8cm9iZXJ0YS5tYWdsaW9u
ZUB0ZWxlY29taXRhbGlhLml0Pg0KQ2M6IEF2aSBMaW9yOyByYWRpdXNleHRAb3BzLmlldGYub3Jn
IDxyYWRpdXNleHRAb3BzLmlldGYub3JnPjsgQWxhbiBLYXZhbmFnaCA8YWxhbi5rYXZhbmFnaEBl
cmljc3Nvbi5jb20+OyBTdXJlc2ggS3Jpc2huYW4gPHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5j
b20+OyBWYXJnYSBCYWzDoXpzIDx2YXJnYS5iYWxhenNAdGVsZWtvbS5odT4NClNlbnQ6IEZyaSBG
ZWIgMjYgMTA6MzU6MDMgMjAxMApTdWJqZWN0OiBSZTogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9u
IGZvciBkcmFmdC1tYWdsaW9uZS1yYWRleHQtaXB2Ni1hY2N0LWV4dGVuc2lvbnMtMDANCg0KTWFn
bGlvbmUgUm9iZXJ0YSB3cm90ZToNCj4gSSdtIG5vdCBzdXJlIHdlIGNvdWxkIHVzZSB0aGUgQWNj
dC1NdWx0aS1TZXNzaW9uLUlkIGZvciB0aGlzIHB1cnBvc2UgYmVjYXVzZSBhY2NvcmRpbmcgdG8g
dGhlIGRlZmluaXRpb24gaW4gUkZDIDI4NjYsIEFjY3QtTXVsdGktU2Vzc2lvbi1JZCBsaW5rcyB0
b2dldGhlciBtdWx0aXBsZSBzZXNzaW9ucyB3aXRoIGRpZmZlcmVudCBBY2N0LVNlc3Npb24tSWQN
Cj4gDQo+ICI1LjExICBUaGlzIGF0dHJpYnV0ZSBpcyBhIHVuaXF1ZSBBY2NvdW50aW5nIElEIHRv
IG1ha2UgaXQgZWFzeSB0byBsaW5rDQo+ICAgICAgIHRvZ2V0aGVyIG11bHRpcGxlIHJlbGF0ZWQg
c2Vzc2lvbnMgaW4gYSBsb2cgZmlsZS4gIEVhY2ggc2Vzc2lvbg0KPiAgICAgICBsaW5rZWQgdG9n
ZXRoZXIgd291bGQgaGF2ZSBhIHVuaXF1ZSBBY2N0LVNlc3Npb24tSWQgYnV0IHRoZSBzYW1lDQo+
ICAgICAgIEFjY3QtTXVsdGktU2Vzc2lvbi1JZC4iDQo+IA0KPiBXaGlsZSBpbiB0aGUgZGVzY3Jp
YmVkIHNjZW5hcmlvIHRoZXJlIGlzIGEgc2luZ2xlIHNlc3Npb24gdGhhdCBjYXJyaWVzIG11bHRp
cGxlIHRyYWZmaWMgZmxvd3M6IElQdjQgYW5kIElQdjYuDQoNCiAgWWVzLCBJIHVuZGVyc3Rvb2Qg
dGhhdC4gIEkgc3RpbGwgcHJvcG9zZWQgdGhlIHNvbHV0aW9uIGJlY2F1c2U6DQoNCihhKSBpdCB3
b3Jrcw0KKGIpIGl0J3Mgbm90IGFjdHVhbGx5IGZvcmJpZGRlbiBieSB0aGUgUkZDcw0KKGMpIGl0
IHNlZW1zIHRvIGJlIGEgcHJhY3RpY2FsIHVzZS1jYXNlIGZvciBBY2N0LU11bHRpLVNlc3Npb24t
SWQNCg0KPiBJbiBhZGRpdGlvbiBJIHNlZSBhbiBvcGVyYXRpb25hbCBpc3N1ZSBpbiB0ZXJtcyBv
ZiBlZmZpY2llbmN5IGluIGRvdWJsaW5nIHRoZSBudW1iZXIgb2YgQWNjb3VudGluZyBzdHJlYW1z
LCBiZWNhdXNlIHdlIHVzdWFsbHkgaGF2ZSBhcm91bmQgMjAtMzAgdGhvdXNhbmQgYWN0aXZlIHN1
YnNjcmliZXJzIGluIGEgc2luZ2xlIE5BUyB0aHVzICBzZW5kaW5nIHRoZSBBY2NvdW50aW5nIHN0
cmVhbSB0d2ljZSBtYXkgYWZmZWN0IHRoZSBwZXJmb3JtYW5jZSBvZiB0aGUgTkFTLg0KDQogIFJB
RElVUyBpc24ndCBwZXJmZWN0LiAgWW91IGhhdmUgdG8gbWFrZSB0cmFkZS1vZmZzIHNvbWV3aGVy
ZS4gICBUaGUNCmNob2ljZSBpcyBiZXR3ZWVuIG1vcmUgdHJhZmZpYyBmb3IgdGhlIE5BUyAoYnV0
IHdpdGggd2VsbC1kZWZpbmVkDQpzZW1hbnRpY3MpLCBvciBtb3JlIGF0dHJpYnV0ZXMgaW4gdGhl
IHN0YW5kYXJkIHNwYWNlLg0KDQogIEFsYW4gRGVLb2suDQo=

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 26 Feb 2010 15:36:10 +0000
Message-ID: <4B87EA27.2020206@deployingradius.com>
Date: Fri, 26 Feb 2010 16:35:03 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
CC: Avi Lior <avi@bridgewatersystems.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>,  Suresh Krishnan <suresh.krishnan@ericsson.com>, =?ISO-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Maglione Roberta wrote:
> I'm not sure we could use the Acct-Multi-Session-Id for this purpose because according to the definition in RFC 2866, Acct-Multi-Session-Id links together multiple sessions with different Acct-Session-Id
> 
> "5.11  This attribute is a unique Accounting ID to make it easy to link
>       together multiple related sessions in a log file.  Each session
>       linked together would have a unique Acct-Session-Id but the same
>       Acct-Multi-Session-Id."
> 
> While in the described scenario there is a single session that carries multiple traffic flows: IPv4 and IPv6.

  Yes, I understood that.  I still proposed the solution because:

(a) it works
(b) it's not actually forbidden by the RFCs
(c) it seems to be a practical use-case for Acct-Multi-Session-Id

> In addition I see an operational issue in terms of efficiency in doubling the number of Accounting streams, because we usually have around 20-30 thousand active subscribers in a single NAS thus  sending the Accounting stream twice may affect the performance of the NAS.

  RADIUS isn't perfect.  You have to make trade-offs somewhere.   The
choice is between more traffic for the NAS (but with well-defined
semantics), or more attributes in the standard space.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 26 Feb 2010 15:02:07 +0000
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Alan DeKok' <aland@deployingradius.com>, Avi Lior <avi@bridgewatersystems.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Fri, 26 Feb 2010 16:00:51 +0100
Subject: RE: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq2xlNRWlEz1mBZS3qffNv5QNj9yAALCbfQ
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7E61FC82@GRFMBX704BA020.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: en-US
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Alan,

>  I suppose you could distinguish traffic IPv4/v6 for a session by
> simply sending two different accounting streams.  e.g. one with an IPv4
> address, and another with an IPv6 address.  The Acct-Multi-Session-Id
> attribute would be good for this.

I'm not sure we could use the Acct-Multi-Session-Id for this purpose becaus=
e according to the definition in RFC 2866, Acct-Multi-Session-Id links toge=
ther multiple sessions with different Acct-Session-Id

"5.11  This attribute is a unique Accounting ID to make it easy to link
      together multiple related sessions in a log file.  Each session
      linked together would have a unique Acct-Session-Id but the same
      Acct-Multi-Session-Id."

While in the described scenario there is a single session that carries mult=
iple traffic flows: IPv4 and IPv6.

In addition I see an operational issue in terms of efficiency in doubling t=
he number of Accounting streams, because we usually have around 20-30 thous=
and active subscribers in a single NAS thus  sending the Accounting stream =
twice may affect the performance of the NAS.

Regards,
Roberta

-----Original Message-----
From: Alan DeKok [mailto:aland@deployingradius.com]
Sent: Friday, February 26, 2010 10:30 AM
To: Avi Lior
Cc: Maglione Roberta; radiusext@ops.ietf.org; Alan Kavanagh; Suresh Krishna=
n; Varga Bal=E1zs
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-e=
xtensions-00

Avi Lior wrote:
> Wouldn't the IP address contained in the IP session be sufficient to crea=
te the context for the accounting message?

  I suppose you could distinguish traffic IPv4/v6 for a session by
simply sending two different accounting streams.  e.g. one with an IPv4
address, and another with an IPv6 address.  The Acct-Multi-Session-Id
attribute would be good for this.

  e.g. for IPv4, send:

Framed-IP-Address =3D ...
Acct-Session-Id =3D 1234
Acct-Multi-Session-Id =3D foo
(octets / packet counters)

  For IPv6, send:

Framed-IPv6-Address =3D ... (presuming draft-lourdelet is standardized)
Acct-Session-Id =3D 5678
Acct-Multi-Session-Id =3D foo
(octets / packet counters)

  IIRC, this functionality is already used to track different kinds of
user traffic in certain environments.  It's not widely supported in the
ISP / dial-up environment, but it shouldn't be hard to add.

  Leveraging the existing functionality of RADIUS would mean that this
document is unnecessary.

  Alan DeKok.

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, 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-data0@psg.com
Delivery-date: Fri, 26 Feb 2010 09:31:49 +0000
Message-ID: <4B8794A7.3070105@deployingradius.com>
Date: Fri, 26 Feb 2010 10:30:15 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Maglione Roberta <roberta.maglione@telecomitalia.it>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>,  Suresh Krishnan <suresh.krishnan@ericsson.com>, =?ISO-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Avi Lior wrote:
> Wouldn't the IP address contained in the IP session be sufficient to create the context for the accounting message?

  I suppose you could distinguish traffic IPv4/v6 for a session by
simply sending two different accounting streams.  e.g. one with an IPv4
address, and another with an IPv6 address.  The Acct-Multi-Session-Id
attribute would be good for this.

  e.g. for IPv4, send:

Framed-IP-Address = ...
Acct-Session-Id = 1234
Acct-Multi-Session-Id = foo
(octets / packet counters)

  For IPv6, send:

Framed-IPv6-Address = ... (presuming draft-lourdelet is standardized)
Acct-Session-Id = 5678
Acct-Multi-Session-Id = foo
(octets / packet counters)

  IIRC, this functionality is already used to track different kinds of
user traffic in certain environments.  It's not widely supported in the
ISP / dial-up environment, but it shouldn't be hard to add.

  Leveraging the existing functionality of RADIUS would mean that this
document is unnecessary.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 20:02:40 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Alan Kavanagh <alan.kavanagh@ericsson.com>
CC: Suresh Krishnan <suresh.krishnan@ericsson.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Thu, 25 Feb 2010 15:01:55 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq2VWIw48L/T/CfTCOvPlPcWeVsGQ==
Message-ID: <8AC4AAEC-D587-4C84-A9E2-A56B9FC2776F@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 23-02-2010, at 20:40 , Alan Kavanagh wrote:

> Hi Avi
>=20
>=20
>=20
> -----Original Message-----
> From: Avi Lior [mailto:avi@bridgewatersystems.com]=20
> Sent: February 23, 2010 5:03 PM
> To: Suresh Krishnan
> Cc: Maglione Roberta; radiusext@ops.ietf.org; Alan Kavanagh; Varga Bal=E1=
zs
> Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct=
-extensions-00
>=20
> Why do you need separate counters for IPv6?
>=20
> Is it because you want to have different counters for different IP techno=
logy at the same time in the accounting stream?
>>> A.K.--> it may be that you have some sessions that are IPv4 only as we =
have today, some sessions that are IPv6 only and some sessions for dual sta=
ck hosts where the SP wants to count the traffic volume seperately for IPv4=
 and IPv6 for stats purposes as one example. Also, in the dual stack host c=
ase, if the AAA assigns both IPv4/v6 Addresses, there are some cases that t=
he IPv4 address does not get assigned down to the end host until some spefi=
cied time x and as such we still want to count the IPv6 packets for an ongo=
ing current session.
>=20
> If yes there are other problems with that approach.  Accounting is used f=
or both volume and time accounting.  While having distinct volume counters =
for one technology may solve the volume aspect it does not address the time=
 aspect.  Consider the fact that even if you have both IPv4 and IPv6 enable=
d one may start at a different time then the other and one may stop at a di=
fferent time then the other.
>=20
>>> A.K.--> Agree as I noted above we agree on this and the intention of th=
e draft is primarily for volume based accounting.
Avi: Here I have an issue.  You can't solve the problem only for Volume Bas=
ed and even for volume based you are not solving the problem in general.  Y=
ou are only assuming that the device is getting one IPv4 and one IPv6 addre=
ss - that is not the case always.  The current model already supports Volum=
e Based and Time Based and other things.  The current model is to send an a=
ccounting packet for each IP session.
>=20
> There are other information elements that are accounted for that may be s=
pecific to a particular IP technology and not the other.
>=20
> As well, a user may have multiple IPv4 addresses and multiple IPv6 addres=
ses.
>=20
>>> A.K.--> Can you expand on this a little more, are you siting a prefix a=
s oppsoed to a 128-bit address?
Avi:  Regarding multiple IP addresses.  I am not talking about a prefix vs =
128-bit addresses.  That can always be true.  What I am talking about is a =
given session can be assigned multiple IPv4 addresses only, multiple IPv6 a=
ddresses only or any combination of multiple IPv4 and multiple IPv6 address=
es.  Your proposed solution can only handle the case where a single IPv4 an=
d/or Single IPv6 address is assigned.

>=20
> So I am concerned that you are not really addressing all the issues. =20
>=20
> Separate accounting streams per IP session solves these problems.
>=20
> What is the problem with having separate accounting streams per IP sessio=
n?
>=20
>>> A.K.--> nothing prevents you from doing that, but you still require to =
count IPv6 packets when you have a dual stack session that are logically co=
mbined at the NAS.
But I don't need to have distinct IPv6 counters.  You can do what you want =
to achieve without creation of distinct IPv6 counters.  My argument is that=
 you can do a better (better =3D more general flexible solution) job with t=
he current approach.


>=20
> //Alan
>=20
>> Hi Avi,
>>  Thanks for your comments.
>>=20
>> On 10-02-23 12:38 PM, Avi Lior wrote:
>>> Hi,'
>>>=20
>>> What makes you say that the existing accounting attributes for octet/pa=
cket counts are for IPv4 ?
>>=20
>> You are right. They are not. They are not protocol specific. We are=20
>> looking to define separate counters for IPv6. We will change the=20
>> wording in the draft to correspond to this.
>>=20
>>>=20
>>> Wouldn't the IP address contained in the IP session be sufficient to cr=
eate the context for the accounting message?
>>=20
>> This will require us to send two different messages (one for IPv6 only=20
>> and one for all protocols combined together).
>>=20
>> Thanks
>> Suresh
>=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-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 17:57:20 +0000
Message-ID: <BLU137-W2396B4A27DAEA704629FC793400@phx.gbl>
Content-Type: multipart/alternative; boundary="_29310c53-70ee-4345-99a0-ac23683b7125_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: FW: draft-ietf-radext-dynamic-discovery-01.txt
Date: Thu, 25 Feb 2010 09:56:52 -0800
MIME-Version: 1.0

--_29310c53-70ee-4345-99a0-ac23683b7125_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


> Date: Thu=2C 25 Feb 2010 15:55:43 +0100
> From: mail@stefan-winter.de
> To: leslie@thinkingcat.com
> CC: mikem@open.com.au=3B Bernard_Aboba@hotmail.com=3B d.b.nelson@comcast.=
net
> Subject: Re: draft-ietf-radext-dynamic-discovery-01.txt
>=20
> Hi=2C
>=20
> sorry for being so late to get back to you.
>=20
> > You may find that S-NAPTR (RFC3958) does the trick for you.
>=20
> Indeed it does! After looking through 3958=2C it looks like an almost
> perfect match. It's not quite a 100%=2C but if I may=2C I'd like to solic=
it
> your opinion on what could be done to make it so. In very short terms:
>=20
> The service my draft describes is "roaming" based on NAI user names
> (which are derived from DNS domain names). It can=2C among others=2C be u=
sed
> with the protocol RADIUS over TLS. On first glance=2C it would thus seem
> prudent to register a service "roaming" and an application type
> "radius.tls" for the S-NAPTR DDDS application=2C like
>=20
> host -t NAPTR restena.lu
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming:radius.tls" "" radius-1.r=
estena.lu.
>=20
>=20
> That is unfortunately barely short of what's needed. Roaming consortia
> are usually selective about who they peer with. It may be possible that
> one realm participates in "n" roaming consortia=2C and thus has multiple
> NAPTR records for those. Iterating through all NAPTR resolutions and
> trying which TLS connection will actually be accepted is one way of
> course=2C but not very efficient and might cause end-user delays. A uniqu=
e
> per-consortium label would be beneficial here.
>=20
> The short and cheap solution is to use a label "x-consortium" to avoid
> writing an RFC for the consortium and circumvent IANA registration. In
> our specific case=2C we could do x-eduroam.
>=20
> But I was wondering about a more elegant solution to this=2C that doesn't
> force operators to flee to dimension x-. If the service label were to
> contain a sub-space with arbitrary but unique consortium handles=2C this
> would be rather elegant. I'm envisaging sth like
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#eduroam:radius.tls" "" ra=
dius-1.restena.lu.
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#3gpp:radius.tls" "" radiu=
s-1.restena.lu.
> restena.lu has NAPTR record 100 10 "a" "roaming#wimax:radius.tls" "" radi=
us-1.restena.lu.
>=20
>=20
> This would of course require charging IANA with handling a "sub-registry"=
 below "roaming"=2C and I'm not sure if that's what's wanted. To take the l=
oad off IANA=2C it can also be imagined to ensure uniqueness of the sub-spa=
ce by piggybacking it on an established namespace registry=2C like DNS name=
s of the consortia. Like
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#eduroam.org:radius.tls" "=
" radius-1.restena.lu.
>=20
> restena.lu has NAPTR record 100 10 "a" "roaming#3gppnetworks.org:radius.t=
ls" "" radius-1.restena.lu.
> restena.lu has NAPTR record 100 10 "a" "roaming#wimaxforum.com:radius.tls=
" "" radius-1.restena.lu.
>=20
> Do you think such a "wildcard" subspace allocation would fly?
>=20
> Thanks for any advice=2C
>=20
> Stefan Winter
>=20
>=20
 		 	   		  =

--_29310c53-70ee-4345-99a0-ac23683b7125_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
&gt=3B Date: Thu=2C 25 Feb 2010 15:55:43 +0100<br>&gt=3B From: mail@stefan-=
winter.de<br>&gt=3B To: leslie@thinkingcat.com<br>&gt=3B CC: mikem@open.com=
.au=3B Bernard_Aboba@hotmail.com=3B d.b.nelson@comcast.net<br>&gt=3B Subjec=
t: Re: draft-ietf-radext-dynamic-discovery-01.txt<br>&gt=3B <br>&gt=3B Hi=
=2C<br>&gt=3B <br>&gt=3B sorry for being so late to get back to you.<br>&gt=
=3B <br>&gt=3B &gt=3B You may find that S-NAPTR (RFC3958) does the trick fo=
r you.<br>&gt=3B <br>&gt=3B Indeed it does! After looking through 3958=2C i=
t looks like an almost<br>&gt=3B perfect match. It's not quite a 100%=2C bu=
t if I may=2C I'd like to solicit<br>&gt=3B your opinion on what could be d=
one to make it so. In very short terms:<br>&gt=3B <br>&gt=3B The service my=
 draft describes is "roaming" based on NAI user names<br>&gt=3B (which are =
derived from DNS domain names). It can=2C among others=2C be used<br>&gt=3B=
 with the protocol RADIUS over TLS. On first glance=2C it would thus seem<b=
r>&gt=3B prudent to register a service "roaming" and an application type<br=
>&gt=3B "radius.tls" for the S-NAPTR DDDS application=2C like<br>&gt=3B <br=
>&gt=3B host -t NAPTR restena.lu<br>&gt=3B <br>&gt=3B restena.lu has NAPTR =
record 100 10 "a" "roaming:radius.tls" "" radius-1.restena.lu.<br>&gt=3B <b=
r>&gt=3B <br>&gt=3B That is unfortunately barely short of what's needed. Ro=
aming consortia<br>&gt=3B are usually selective about who they peer with. I=
t may be possible that<br>&gt=3B one realm participates in "n" roaming cons=
ortia=2C and thus has multiple<br>&gt=3B NAPTR records for those. Iterating=
 through all NAPTR resolutions and<br>&gt=3B trying which TLS connection wi=
ll actually be accepted is one way of<br>&gt=3B course=2C but not very effi=
cient and might cause end-user delays. A unique<br>&gt=3B per-consortium la=
bel would be beneficial here.<br>&gt=3B <br>&gt=3B The short and cheap solu=
tion is to use a label "x-consortium" to avoid<br>&gt=3B writing an RFC for=
 the consortium and circumvent IANA registration. In<br>&gt=3B our specific=
 case=2C we could do x-eduroam.<br>&gt=3B <br>&gt=3B But I was wondering ab=
out a more elegant solution to this=2C that doesn't<br>&gt=3B force operato=
rs to flee to dimension x-. If the service label were to<br>&gt=3B contain =
a sub-space with arbitrary but unique consortium handles=2C this<br>&gt=3B =
would be rather elegant. I'm envisaging sth like<br>&gt=3B <br>&gt=3B reste=
na.lu has NAPTR record 100 10 "a" "roaming#eduroam:radius.tls" "" radius-1.=
restena.lu.<br>&gt=3B <br>&gt=3B restena.lu has NAPTR record 100 10 "a" "ro=
aming#3gpp:radius.tls" "" radius-1.restena.lu.<br>&gt=3B restena.lu has NAP=
TR record 100 10 "a" "roaming#wimax:radius.tls" "" radius-1.restena.lu.<br>=
&gt=3B <br>&gt=3B <br>&gt=3B This would of course require charging IANA wit=
h handling a "sub-registry" below "roaming"=2C and I'm not sure if that's w=
hat's wanted. To take the load off IANA=2C it can also be imagined to ensur=
e uniqueness of the sub-space by piggybacking it on an established namespac=
e registry=2C like DNS names of the consortia. Like<br>&gt=3B <br>&gt=3B re=
stena.lu has NAPTR record 100 10 "a" "roaming#eduroam.org:radius.tls" "" ra=
dius-1.restena.lu.<br>&gt=3B <br>&gt=3B restena.lu has NAPTR record 100 10 =
"a" "roaming#3gppnetworks.org:radius.tls" "" radius-1.restena.lu.<br>&gt=3B=
 restena.lu has NAPTR record 100 10 "a" "roaming#wimaxforum.com:radius.tls"=
 "" radius-1.restena.lu.<br>&gt=3B <br>&gt=3B Do you think such a "wildcard=
" subspace allocation would fly?<br>&gt=3B <br>&gt=3B Thanks for any advice=
=2C<br>&gt=3B <br>&gt=3B Stefan Winter<br>&gt=3B <br>&gt=3B <br> 		 	   		 =
 </body>
</html>=

--_29310c53-70ee-4345-99a0-ac23683b7125_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 17:50:36 +0000
Message-ID: <BLU137-DS7D5C366B3876B0A69BC8693400@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>
CC: "'Ignacio Goyret'" <i.goyret@alcatel-lucent.com>, <radiusext@ops.ietf.org>
Subject: RE: Review of draft-ietf-radext-status-server-05 (Part II)
Date: Thu, 25 Feb 2010 09:49:23 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: Acq15EzZkptTkcTyQP+SHbQKdpv3PgAXiJRg
Content-Language: en-us

Alan said:

"  Say a NAS has two paths to realm FOO.  It can ask each one; can *you*
reach FOO?  The one that answers "yes" has packets sent to it.

  The Status-Server isn't being forwarded.  But the NAS still finds out
the proxies view of the reachability of realm FOO."


[BA] The effectiveness of this will depend on the definition of
"reachability" in this context. For example, does a "yes" mean:

1. "Proxy has realm FOO in its routing table"  OR
2. "Proxy got a response from realm FOO in the last X seconds" OR
3. "Proxy tested reachability to realm FOO as a result of receiving
Status-Server with a realm request and got a response"


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 12:18:15 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAB614.8394DA26"
Subject: AW: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Date: Thu, 25 Feb 2010 13:17:35 +0100
Message-ID: <D83105B2AC38794CB78ADA2959F2C44F03F07461@S4DE9JSAACY.ost.t-com.de>
Thread-Topic: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
thread-index: Acq0xT8uBPxYy20STV+Ko3u61xMO7gAmQM/QAC1I/qA=
From: <Olaf.Bonness@telekom.de>
To: <radiusext@ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAB614.8394DA26
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

 I think SPs that are operating access networks (like DSL) need to =
transport these attributes between NAS and their Radius servers and am =
that's why in favour to adopt this I-D as WG item.
Regards
    Olaf
=20
  _____ =20

From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] =
On Behalf Of Bernard Aboba
Sent: 23 February 2010 21:18
To: radiusext@ops.ietf.org
Subject: Call for adoption of "RADIUS Attributes for IPv6 Access =
Networks"



During the RADEXT Virtual Interim, we discussed adoption of "RADIUS =
Attributes for IPv6 Access Networks" as a RADEXT WG work item.=20

=20

We would now like to request mailing list confirmation of the decision =
to adopt this draft.=20

=20

The document is available here:

http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02

=20

If you have an opinion on the adoption  of this document as a RADEXT WG =
work item, please reply to this email.=20

=20

=20

=20


------_=_NextPart_001_01CAB614.8394DA26
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D608370912-25022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;I think SPs that are operating access =
networks (like=20
DSL) need to transport these attributes between NAS and their Radius =
servers and=20
am that's why in favour to adopt this I-D as WG =
item.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D608370912-25022010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D608370912-25022010>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>Olaf</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D608370912-25022010>&nbsp;</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma size=3D2><B>From:</B>=20
owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] <B>On =
Behalf=20
Of </B>Bernard Aboba<BR><B>Sent:</B> 23 February 2010 =
21:18<BR><B>To:</B>=20
radiusext@ops.ietf.org<BR><B>Subject:</B> Call for adoption of "RADIUS=20
Attributes for IPv6 Access Networks"<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal>During the RADEXT Virtual Interim, we discussed =
adoption of=20
  "RADIUS Attributes for IPv6 Access Networks" as a RADEXT WG work item. =

  <o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>We would now like to request mailing list =
confirmation of=20
  the decision to adopt this draft. <o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>The document is available here:<o:p></o:p></P>
  <P=20
  =
class=3DMsoNormal>http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-=
access-02<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>If you have an opinion on the adoption&nbsp; of =
this=20
  document as a RADEXT WG work item, please reply to this email. =
<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P =
class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAB614.8394DA26--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 08:41:54 +0000
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Alan DeKok' <aland@deployingradius.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Thu, 25 Feb 2010 09:41:04 +0100
Subject: RE: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq1l1nTYyKCMXOGS8O53zgkHYE6UgAXeG1w
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7E61FC79@GRFMBX704BA020.griffon.local>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hello Alan,
    thanks for your comments.

-----Original Message-----
From: Alan DeKok [mailto:aland@deployingradius.com]
Sent: Wednesday, February 24, 2010 10:22 PM
To: Maglione Roberta
Cc: radiusext@ops.ietf.org; Alan Kavanagh; Suresh Krishnan; Varga Bal=E1zs
Subject: Re: FW: New Version Notification for draft-maglione-radext-ipv6-ac=
ct-extensions-00

Maglione Roberta wrote:
> Hi All,
>      we have just posted a new draft about RADIUS attributes for IPv6 sta=
tistics:
> http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
> Your comments are welcome.

   [RFC2866]and [RFC2869] specify RADIUS attributes to be used for
   carrying statistics regarding how many packets/octets/Gigawords have
   been sent/received over a port while delivering the service.  These
   attributes are IPv4 specific.

 That isn't correct.  RFC 2866 has *no* references to IPv4.  I suggest
deleting it.

[RM] ok, we will delete it

   With the introduction of the IPv6 in
   broadband environment there is a need to be able to collect IPv4 and
   IPv6 statistics separately, thus new RADIUS attribute have to be
   defined.

 That might be true, and is a better problem statement than the previous
sentence.

[RM] This is the main intent of document

  However, there is a LOT of information that could potentially be
carried in RADIUS accounting.  There have been requests to track data
down to specific applications and/or ports.  These suggestions have a
number of problems in practice.  (Which I won't go into here.)


4. Operation
...

  This section repeats existing definitions of RADIUS accounting.  I
suggest deleting it.


5.
...
   This section defines six new RADIUS attributes for IPv6 statistics.
   These attributes correspond to the attributes Acct-Input-Octets,
   Acct-Output-Octets,Acct-Input-Packets, Acct-Output-Packets, Acct-
   Input-Gigawords and Acct-Output-Gigawords as defined in
   [RFC2866][RFC2869] that are defined for collecting combined
   statistics for IPv4 and IPv6 traffic.

  This last sentence directly contradicts the sentence in the
introduction.  It would be good to have the document internally consistent.

[RM] We will re-word this sentence to make it consistent

   Since service providers may
   like to collect statistics for IPv6 traffic separately from IPv4
   traffic, separate counters for IPv6 traffic are needed.

  Repetition of the justification is unnecessary, and can be deleted.

  It would be good to add a sentence or two on how these attributes
interact with the existing counters.  e.g. how IPv4-specific counters
can be derived.

[RM] ok we will add it

Thanks,
Roberta

  Alan DeKok.

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, 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-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 07:06:11 +0000
Message-ID: <4B862144.6050704@deployingradius.com>
Date: Thu, 25 Feb 2010 08:05:40 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Ignacio Goyret <i.goyret@alcatel-lucent.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Ignacio Goyret wrote:
> I'm just questioning the choice of MUST vs SHOULD.
> I've seen far too many specs that include MUSTs that should
> have been less restrictive.

  I agree.

> So, unless it hurts interoperability, I'd suggest replacing
> that MUST with a SHOULD, leaving the door open for servers
> to use other attributes, if their admins choose to do so.

  It won't hurt interoperability, so far as I can tell.

> Makes sense?

  Yes.

  I don't have strong opinions either way.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 25 Feb 2010 06:33:26 +0000
Message-ID: <4B86197B.20906@deployingradius.com>
Date: Thu, 25 Feb 2010 07:32:27 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: 'Ignacio Goyret' <i.goyret@alcatel-lucent.com>,  radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Alan said:
> [BA] Since Status-Server isn't forwardable, I'm not sure how it could help
> with the realm reachability issue.  

  Say a NAS has two paths to realm FOO.  It can ask each one; can *you*
reach FOO?  The one that answers "yes" has packets sent to it.

  The Status-Server isn't being forwarded.  But the NAS still finds out
the proxies view of the reachability of realm FOO.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 22:27:39 +0000
Message-ID: <BLU137-DS451546B1E94A9DAD9779993410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>, "'Ignacio Goyret'" <i.goyret@alcatel-lucent.com>
CC: <radiusext@ops.ietf.org>
Subject: RE: Review of draft-ietf-radext-status-server-05 (Part II)
Date: Wed, 24 Feb 2010 14:27:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: Acq1nfuntwwGqiS6SBCzHY8YE4NrxQAAl/fA
Content-Language: en-us

Alan said:

"  I could see this being useful for checking "liveliness" of upstream
realms.  But some providers have dozens, if not hundreds of realms, and
this functionality gets awkward pretty quickly."

[BA] Since Status-Server isn't forwardable, I'm not sure how it could help
with the realm reachability issue.  


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 22:06:44 +0000
Message-ID: <4B85A2D5.2020906@deployingradius.com>
Date: Wed, 24 Feb 2010 23:06:13 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Ignacio Goyret <i.goyret@alcatel-lucent.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>,  "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Ignacio Goyret wrote:
>>> [BA] You might say that the server MUST ignore other attributes. 
>                                       ^^^^
> Why MUST?
> 
> Shouldn't that be up to the server's local policy?
> What if the server needs/wants to check one of those extra attributes?
> (possibly including vendor-specific attributes)

  What are the checks for?  The only possible decision that can be made
is whether or not to reply to a Status-Server.

  Would it be useful to allow a server to *not* respond, if it saw a VSA
with a particular value?

  I could see this being useful for checking "liveliness" of upstream
realms.  But some providers have dozens, if not hundreds of realms, and
this functionality gets awkward pretty quickly.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 21:22:24 +0000
Message-ID: <4B859860.9060001@deployingradius.com>
Date: Wed, 24 Feb 2010 22:21:36 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>,  Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?ISO-8859-1?Q?Varga_B?= =?ISO-8859-1?Q?al=E1zs?= <varga.balazs@telekom.hu>
Subject: Re: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Maglione Roberta wrote:
> Hi All,
>      we have just posted a new draft about RADIUS attributes for IPv6 statistics:
> http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
> Your comments are welcome.

   [RFC2866]and [RFC2869] specify RADIUS attributes to be used for
   carrying statistics regarding how many packets/octets/Gigawords have
   been sent/received over a port while delivering the service.  These
   attributes are IPv4 specific.

 That isn't correct.  RFC 2866 has *no* references to IPv4.  I suggest
deleting it.

   With the introduction of the IPv6 in
   broadband environment there is a need to be able to collect IPv4 and
   IPv6 statistics separately, thus new RADIUS attribute have to be
   defined.

 That might be true, and is a better problem statement than the previous
sentence.

  However, there is a LOT of information that could potentially be
carried in RADIUS accounting.  There have been requests to track data
down to specific applications and/or ports.  These suggestions have a
number of problems in practice.  (Which I won't go into here.)

4. Operation
...

  This section repeats existing definitions of RADIUS accounting.  I
suggest deleting it.


5.
...
   This section defines six new RADIUS attributes for IPv6 statistics.
   These attributes correspond to the attributes Acct-Input-Octets,
   Acct-Output-Octets,Acct-Input-Packets, Acct-Output-Packets, Acct-
   Input-Gigawords and Acct-Output-Gigawords as defined in
   [RFC2866][RFC2869] that are defined for collecting combined
   statistics for IPv4 and IPv6 traffic.

  This last sentence directly contradicts the sentence in the
introduction.  It would be good to have the document internally consistent.


   Since service providers may
   like to collect statistics for IPv6 traffic separately from IPv4
   traffic, separate counters for IPv6 traffic are needed.

  Repetition of the justification is unnecessary, and can be deleted.

  It would be good to add a sentence or two on how these attributes
interact with the existing counters.  e.g. how IPv4-specific counters
can be derived.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 16:45:41 +0000
Message-ID: <BLU137-DS471C4718699DFD2B3E87493410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alan DeKok'" <aland@deployingradius.com>
CC: <radiusext@ops.ietf.org>
Subject: RE: FW: Review of Radius Guidelines 11
Date: Wed, 24 Feb 2010 08:45:57 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acq1bLmx0z7jpBMbSYml+AmkmZj9xAAA+fYQ
Content-Language: en-us

In terms of process, my suggestion is to discuss proposed changes to the
text on the list, and incorporate them within a -12 version to be submitted
by the deadline.  At IETF 77, we can then go over what additional changes
(if any) are necessary. 

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Alan DeKok
Sent: Wednesday, February 24, 2010 8:12 AM
To: Bernard Aboba
Cc: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11

Alan DeKok wrote:

  To summarize: the comments can be divided into a few rough areas:

- minor fixes
  - these should be addressed

- requests to define *new* methods/architectures in the document
  - these should be rejected

- requests to change the document or add explanations
  - I would appreciate suggested text.

  As editor, I welcome suggestions from the WG on how to improve the
document.  I have offered many suggestions in the past, and given the
volume of requested changes, ask for guidance from the WG on what to do
next.

  Alan DeKok.

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


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 16:12:46 +0000
Message-ID: <4B854FDD.3080203@deployingradius.com>
Date: Wed, 24 Feb 2010 17:12:13 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Alan DeKok wrote:

  To summarize: the comments can be divided into a few rough areas:

- minor fixes
  - these should be addressed

- requests to define *new* methods/architectures in the document
  - these should be rejected

- requests to change the document or add explanations
  - I would appreciate suggested text.

  As editor, I welcome suggestions from the WG on how to improve the
document.  I have offered many suggestions in the past, and given the
volume of requested changes, ask for guidance from the WG on what to do
next.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 15:04:54 +0000
Message-ID: <BLU137-DS9EB161DAD2A5C53B137E193410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RE: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Date: Wed, 24 Feb 2010 07:05:02 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: Acq1N9XnMYpsV1LWTOKq5YlJyZMrXwAKs8uA
Content-Language: en-us

I agree that the presentation was helpful (the first coherent =
explanation of
how it works), and I
also support adoption.=20

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] =
On
Behalf Of Stefan Winter
Sent: Wednesday, February 24, 2010 1:54 AM
To: radiusext@ops.ietf.org
Subject: Re: Call for adoption of "RADIUS Attributes for IPv6 Access
Networks"

Am 23.02.2010 21:17, schrieb Bernard Aboba:
>
> During the RADEXT Virtual Interim, we discussed adoption of "RADIUS=20
> Attributes for IPv6 Access Networks" as a RADEXT WG work item.
>
> =20
>
> We would now like to request mailing list confirmation of the decision =

> to adopt this draft.
>
> =20
>
> The document is available here:
>
> http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02
>
> =20
>
> If you have an opinion on the adoption  of this document as a RADEXT=20
> WG work item, please reply to this email.
>

The presentation yesterday convinced me that it solves a real-world =
problem.
I support adoption of the document.

Greetings,

Stefan Winter

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

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-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 14:49:28 +0000
Message-ID: <BLU137-DS4C503CEF590C0E9F1C99B93410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: PROTO writeup for RADIUS over TCP document
Date: Wed, 24 Feb 2010 06:49:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007E_01CAB51D.8BACFF10"
Thread-Index: Acq1YJk2CQYmRG6TRi2lGYxForhuCg==
Content-Language: en-us

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

PROTO Writeup for draft-ietf-radext-tcp-transport

=================================================

 

http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

 

   (1.a)  Who is the Document Shepherd for this document?  Has the

      Document Shepherd personally reviewed this version of the document

      and, in particular, does he or she believe this version is ready

      for forwarding to the IESG for publication?

 

Bernard Aboba is the document shepherd.  I have personally reviewed

the document, and believe it is ready for publication as an Experimental

RFC. 

 

   (1.b)  Has the document had adequate review both from key members of

      the interested community and others?  Does the Document Shepherd

      have any concerns about the depth or breadth of the reviews that

      have been performed?

 

The document has undergone review within the community of RTLS

implementers, as well as within the RADEXT WG.  It could benefit

from additional review by the transport community. 

 

   (1.c)  Does the Document Shepherd have concerns that the document

      needs more review from a particular or broader perspective, e.g.,

      security, operational complexity, someone familiar with AAA,

      internationalization or XML?

 

This document should be reviewed by the Transport Directorate prior

to publication. 

 

   (1.d)  Does the Document Shepherd have any specific concerns or

      issues with this document that the Responsible Area Director

      and/or the IESG should be aware of?  For example, perhaps he or

      she is uncomfortable with certain parts of the document, or has

      concerns whether there really is a need for it.  In any event, if

      the interested community has discussed those issues and has

      indicated that it still wishes to advance the document, detail

      those concerns here.

 

As noted in Section 2.5, there are situations (such as NAS avalanche
restart)

where a proxy implementing RADIUS over TCP/TLS would be unable to keep up

with the UDP packets generated by NAS devices not implementing the 

congestion control algorithm described in RFC 5080 Section 2.2.1.

 

   (1.e)  How solid is the consensus of the interested community behind

      this document?  Does it represent the strong concurrence of a few

      individuals, with others being silent, or does the interested

      community as a whole understand and agree with it?

 

There is consensus within the RADEXT WG to publish the document as

an Experimental RFC. 

 

   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme

      discontent?  If so, please summarise the areas of conflict in

      separate email messages to the Responsible Area Director.  (It

      should be in a separate email because this questionnaire is

      entered into the ID Tracker.)

 

No. 

 

   (1.g)  Has the Document Shepherd personally verified that the

      document satisfies all ID nits?  (See

      http://www.ietf.org/ID-Checklist.html and

      http://tools.ietf.org/tools/idnits/).  Boilerplate checks are not

      enough; this check needs to be thorough.  Has the document met all

      formal review criteria it needs to, such as the MIB Doctor, media

      type and URI type reviews?

 

idnits is clean:

 

idnits 2.12.00 

 

tmp/draft-ietf-radext-tcp-transport-05.txt:

 

  Checking boilerplate required by RFC 5378 and the IETF Trust (see

  http://trustee.ietf.org/license-info):

 
----------------------------------------------------------------------------

 

     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: Experimental

 
----------------------------------------------------------------------------

 

  -- Unexpected draft version: The latest known version of 

     draft-ietf-radext-status-server is -03, but you're referring to -06.

     (However, the state information for draft-ietf-radext-status-server is

     not up-to-date.  The last update was 2009-02-13)

 

 

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

 

   (1.h)  Has the document split its references into normative and

      informative?  Are there normative references to documents that are

      not ready for advancement or are otherwise in an unclear state?

      If such normative references exist, what is the strategy for their

      completion?  Are there normative references that are downward

      references, as described in [RFC3967]?  If so, list these downward

      references to support the Area Director in the Last Call procedure

      for them [RFC3967].

 

The references in the document have been split into normative and

informative. 

 

Normative references are all stable documents published as RFCs.

 

   (1.i)  Has the Document Shepherd verified that the document IANA

      consideration section exists and is consistent with the body of

      the document?  If the document specifies protocol extensions, are

      reservations requested in appropriate IANA registries?  Are the

      IANA registries clearly identified?  If the document creates a new

      registry, does it define the proposed initial contents of the

      registry and an allocation procedure for future registrations?

      Does it suggested a reasonable name for the new registry?  See

      [I-D.narten-iana-considerations-rfc2434bis].  If the document

      describes an Expert Review process has Shepherd conferred with the

      Responsible Area Director so that the IESG can appoint the needed

      Expert during the IESG Evaluation?

 

The IANA Considerations section exists (section 4).  It requires no

action by IANA. 

 

   (1.j)  Has the Document Shepherd verified that sections of the

      document that are written in a formal language, such as XML code,

      BNF rules, MIB definitions, etc., validate correctly in an

      automated checker?

 

Not applicable.

 

   (1.k)  The IESG approval announcement includes a Document

      Announcement Write-Up.  Please provide such a Document

      Announcement Writeup?  Recent examples can be found in the

      "Action" announcements for approved documents.  The approval

      announcement contains the following sections:

 

      Technical Summary

 

RADIUS has traditionally used UDP as its underlying transport layer, for

reasons described in RFC 2865 Section 2.4.  This document defines RADIUS

over TCP, in order to address handling issues related to RADIUS over TLS

(RTLS).  It is not intended to define TCP as a transport protocol for

RADIUS in the absence of TLS.   

 

      Working Group Summary

 

This document is part of a set (including the Status-Server and RTLS

specifications) which together define RADIUS over TLS (RTLS).

This document has completed RADEXT WG last call, with the primary

areas of discussion relating to liveness detection and congestion control. 

 

      Document Quality

 

The document has been reviewed by IETF RADEXT WG members. 

 

RADIUS over TLS/TCP has been implemented by multiple vendors, 

including RADIATOR and FreeRADIUS.  The protocol is currently

the subject of a large scale experiment involving deployment 

by EDUROAM, an educational roaming consortium supporting more

than one million users worldwide.

 

      Personnel

 

Bernard Aboba is the document shepherd for this document. 

Dan Romascanu is the responsible AD.


------=_NextPart_000_007E_01CAB51D.8BACFF10
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>PROTO Writeup for =
draft-ietf-radext-tcp-transport<o:p></o:p></p>

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

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

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-ietf-radext-tcp-transp=
ort<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.a)&nbsp; Who is the Document =
Shepherd for this document?&nbsp;
Has the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Document Shepherd =
personally reviewed this version of
the document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and, in particular, =
does he or she believe this
version is ready<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for forwarding to =
the IESG for publication?<o:p></o:p></p>

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

<p class=3DMsoNormal>Bernard Aboba is the document shepherd.&nbsp; I =
have personally
reviewed<o:p></o:p></p>

<p class=3DMsoNormal>the document, and believe it is ready for =
publication as an
Experimental<o:p></o:p></p>

<p class=3DMsoNormal>RFC. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.b)&nbsp; Has the document had =
adequate review both from key
members of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the interested =
community and others?&nbsp; Does the
Document Shepherd<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have any concerns =
about the depth or breadth of the
reviews that<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have been =
performed?<o:p></o:p></p>

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

<p class=3DMsoNormal>The document has undergone review within the =
community of
RTLS<o:p></o:p></p>

<p class=3DMsoNormal>implementers, as well as within the RADEXT =
WG.&nbsp; It could
benefit<o:p></o:p></p>

<p class=3DMsoNormal>from additional review by the transport community. =
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.c)&nbsp; Does the Document Shepherd =
have concerns that the
document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs more review =
from a particular or broader
perspective, e.g.,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;security, =
operational complexity, someone familiar
with AAA,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; internationalization =
or XML?<o:p></o:p></p>

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

<p class=3DMsoNormal>This document should be reviewed by the Transport
Directorate prior<o:p></o:p></p>

<p class=3DMsoNormal>to publication. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.d)&nbsp; Does the Document Shepherd =
have any specific
concerns or<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; issues with this =
document that the Responsible Area
Director<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and/or the IESG =
should be aware of?&nbsp; For example,
perhaps he or<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; she is uncomfortable =
with certain parts of the
document, or has<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; concerns whether =
there really is a need for it.&nbsp; In
any event, if<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the interested =
community has discussed those issues
and has<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicated that it =
still wishes to advance the
document, detail<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; those concerns =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>As noted in Section 2.5, there are situations (such =
as NAS
avalanche restart)<o:p></o:p></p>

<p class=3DMsoNormal>where a proxy implementing RADIUS over TCP/TLS =
would be
unable to keep up<o:p></o:p></p>

<p class=3DMsoNormal>with the UDP packets generated by NAS devices not
implementing the <o:p></o:p></p>

<p class=3DMsoNormal>congestion control algorithm described in RFC 5080 =
Section
2.2.1.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.e)&nbsp; How solid is the consensus =
of the interested
community behind<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this document?&nbsp; =
Does it represent the strong
concurrence of a few<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; individuals, with =
others being silent, or does the
interested<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; community as a whole =
understand and agree with it?<o:p></o:p></p>

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

<p class=3DMsoNormal>There is consensus within the RADEXT WG to publish =
the
document as<o:p></o:p></p>

<p class=3DMsoNormal>an Experimental RFC. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.f)&nbsp; Has anyone threatened an =
appeal or otherwise
indicated extreme<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discontent?&nbsp; If =
so, please summarise the areas of
conflict in<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separate email =
messages to the Responsible Area
Director.&nbsp; (It<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be in a =
separate email because this
questionnaire is<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entered into the ID =
Tracker.)<o:p></o:p></p>

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

<p class=3DMsoNormal>No. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.g)&nbsp; Has the Document Shepherd =
personally verified that
the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document satisfies =
all ID nits?&nbsp; (See<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
http://www.ietf.org/ID-Checklist.html and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
http://tools.ietf.org/tools/idnits/).&nbsp; Boilerplate
checks are not<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enough; this check =
needs to be thorough.&nbsp; Has the
document met all<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; formal review =
criteria it needs to, such as the MIB
Doctor, media<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type and URI type =
reviews?<o:p></o:p></p>

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

<p class=3DMsoNormal>idnits is clean:<o:p></o:p></p>

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

<p class=3DMsoNormal>idnits 2.12.00 <o:p></o:p></p>

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

<p =
class=3DMsoNormal>tmp/draft-ietf-radext-tcp-transport-05.txt:<o:p></o:p><=
/p>

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

<p class=3DMsoNormal>&nbsp; Checking boilerplate required by RFC 5378 =
and the IETF
Trust (see<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp; =
http://trustee.ietf.org/license-info):<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp; Checking nits according to
http://www.ietf.org/ietf/1id-guidelines.txt:<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp; Checking nits according to
http://www.ietf.org/ID-Checklist.html:<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

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

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; No issues found =
here.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp; Checking references for intended status: =
Experimental<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp; -- Unexpected draft version: The latest =
known version of <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ietf-radext-status-server is -03, but you're
referring to -06.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; (However, the state =
information for draft-ietf-radext-status-server
is<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; not up-to-date.&nbsp; The =
last update was 2009-02-13)<o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Summary: 0 errors (**), 0 =
warnings (=3D=3D), 1 comment
(--).<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.h)&nbsp; Has the document split its =
references into
normative and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informative?&nbsp; =
Are there normative references to
documents that are<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not ready for =
advancement or are otherwise in an
unclear state?<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If such normative =
references exist, what is the
strategy for their<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; completion?&nbsp; =
Are there normative references that are
downward<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; references, as =
described in [RFC3967]?&nbsp; If so, list
these downward<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; references to =
support the Area Director in the Last
Call procedure<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for them =
[RFC3967].<o:p></o:p></p>

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

<p class=3DMsoNormal>The references in the document have been split into
normative and<o:p></o:p></p>

<p class=3DMsoNormal>informative. <o:p></o:p></p>

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

<p class=3DMsoNormal>Normative references are all stable documents =
published as
RFCs.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.i)&nbsp; Has the Document Shepherd =
verified that the
document IANA<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; consideration =
section exists and is consistent with
the body of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the document?&nbsp; =
If the document specifies protocol extensions,
are<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; reservations =
requested in appropriate IANA
registries?&nbsp; Are the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IANA registries =
clearly identified?&nbsp; If the document
creates a new<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; registry, does it =
define the proposed initial contents
of the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; registry and an =
allocation procedure for future
registrations?<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does it suggested a =
reasonable name for the new
registry?&nbsp; See<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[I-D.narten-iana-considerations-rfc2434bis].&nbsp; If the
document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; describes an Expert =
Review process has Shepherd
conferred with the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Responsible Area =
Director so that the IESG can appoint
the needed<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Expert during the =
IESG Evaluation?<o:p></o:p></p>

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

<p class=3DMsoNormal>The IANA Considerations section exists (section =
4).&nbsp; It
requires no<o:p></o:p></p>

<p class=3DMsoNormal>action by IANA. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.j)&nbsp; Has the Document Shepherd =
verified that sections
of the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document that are =
written in a formal language, such
as XML code,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BNF rules, MIB =
definitions, etc., validate correctly
in an<o:p></o:p></p>

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

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

<p class=3DMsoNormal>Not applicable.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; (1.k)&nbsp; The IESG approval =
announcement includes a Document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Announcement =
Write-Up.&nbsp; Please provide such a Document<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Announcement =
Writeup?&nbsp; Recent examples can be found in
the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Action&quot; =
announcements for approved
documents.&nbsp; The approval<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; announcement =
contains the following sections:<o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>RADIUS has traditionally used UDP as its underlying
transport layer, for<o:p></o:p></p>

<p class=3DMsoNormal>reasons described in RFC 2865 Section 2.4.&nbsp; =
This document
defines RADIUS<o:p></o:p></p>

<p class=3DMsoNormal>over TCP, in order to address handling issues =
related to
RADIUS over TLS<o:p></o:p></p>

<p class=3DMsoNormal>(RTLS).&nbsp; It is not intended to define TCP as a =
transport
protocol for<o:p></o:p></p>

<p class=3DMsoNormal>RADIUS in the absence of TLS.&nbsp;&nbsp; =
<o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>This document is part of a set (including the =
Status-Server
and RTLS<o:p></o:p></p>

<p class=3DMsoNormal>specifications) which together define RADIUS over =
TLS
(RTLS).<o:p></o:p></p>

<p class=3DMsoNormal>This document has completed RADEXT WG last call, =
with the
primary<o:p></o:p></p>

<p class=3DMsoNormal>areas of discussion relating to liveness detection =
and
congestion control. <o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>The document has been reviewed by IETF RADEXT WG =
members. <o:p></o:p></p>

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

<p class=3DMsoNormal>RADIUS over TLS/TCP has been implemented by =
multiple
vendors, <o:p></o:p></p>

<p class=3DMsoNormal>including RADIATOR and FreeRADIUS.&nbsp; The =
protocol is
currently<o:p></o:p></p>

<p class=3DMsoNormal>the subject of a large scale experiment involving =
deployment
<o:p></o:p></p>

<p class=3DMsoNormal>by EDUROAM, an educational roaming consortium =
supporting
more<o:p></o:p></p>

<p class=3DMsoNormal>than one million users worldwide.<o:p></o:p></p>

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

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

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

<p class=3DMsoNormal>Bernard Aboba is the document shepherd for this =
document. <o:p></o:p></p>

<p class=3DMsoNormal>Dan Romascanu is the responsible AD.<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_007E_01CAB51D.8BACFF10--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 14:44:27 +0000
Content-Type: multipart/mixed; boundary="_3a074c2f-6ef7-4451-9e2b-960e668eb16e_"
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Bernard Aboba' <bernard_aboba@hotmail.com>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Date: Wed, 24 Feb 2010 15:42:54 +0100
Subject: RE: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Thread-Topic: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Thread-Index: Acq0xT8uBPxYy20STV+Ko3u61xMO7gAmd+UA
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35163B@GRFMBX704BA020.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: en-US
acceptlanguage: en-US, it-IT
MIME-Version: 1.0

--_3a074c2f-6ef7-4451-9e2b-960e668eb16e_
Content-Type: multipart/alternative;
	boundary="_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_"

--_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


I support adoption of this document as WG item: this work is needed for IPv=
6 deployment in Broadband access environment.

Best Regards,
Roberta

________________________________
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On=
 Behalf Of Bernard Aboba
Sent: Tuesday, February 23, 2010 9:18 PM
To: radiusext@ops.ietf.org
Subject: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"

During the RADEXT Virtual Interim, we discussed adoption of "RADIUS Attribu=
tes for IPv6 Access Networks" as a RADEXT WG work item.

We would now like to request mailing list confirmation of the decision to a=
dopt this draft.

The document is available here:
http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02

If you have an opinion on the adoption  of this document as a RADEXT WG wor=
k item, please reply to this email.



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.

[cid:00000000000000000000000000000001@TI.Disclaimer]Rispetta l'ambiente. No=
n stampare questa mail se non ? necessario.


--_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:ns1=3D"http://schemas.microsoft.com/office/20=
04/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:offic=
e:smarttags" name=3D"PersonName" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=3D"IT" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial">I support adoption of this document as WG item: t=
his work is needed for IPv6 deployment in Broadband access environment.<o:p=
></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial">Best Regards,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span lang=3D"EN-US"=
 style=3D"font-size:
10.0pt;font-family:Arial">Roberta<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:Arial;color:navy"><o:=
p>&nbsp;</o:p></span></font></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt;font-family:
&quot;Times New Roman&quot;">
<hr size=3D"3" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</=
span></font></b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:Tahoma"> owner-<st1:PersonName w:st=3D"on"=
>radiusext@ops.ietf.org</st1:PersonName>
 [mailto:owner-<st1:PersonName w:st=3D"on">radiusext@ops.ietf.org</st1:Pers=
onName>]
<b><span style=3D"font-weight:
bold">On Behalf Of </span></b>Bernard Aboba<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, February 23, =
2010 9:18 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> <st1:PersonName w:st=3D"=
on">radiusext@ops.ietf.org</st1:PersonName><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Call for adoption o=
f &quot;RADIUS Attributes for IPv6 Access Networks&quot;</span></font><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt;
font-family:&quot;Times New Roman&quot;"><o:p></o:p></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span style=3D"fon=
t-size:11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">During the RADEXT Virtual Interim, we discussed adoption of &quot;R=
ADIUS Attributes for IPv6 Access Networks&quot; as a RADEXT WG work item.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">We would now like to request mailing list confirmation of the decis=
ion to adopt this draft.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">The document is available here:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02<o:=
p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt">If you have an opinion on the adoption&nbsp; of this document as a =
RADEXT WG work item, please reply to this email.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Calibri"><span lang=3D"EN-U=
S" style=3D"font-size:
11.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<style type=3D"text/css">
<!--
span.GramE {mso-style-name:"";
	mso-gram-e:yes;}
-->
</style>
<table style=3D"width:600px;">
<tbody>
<tr>
<td style=3D"width:585px; font-family: Verdana, Arial; font-size:12px; colo=
r:#000; text-align: justify" width=3D"395">
<div align=3D"justify"><span class=3D"MsoNormal" style=3D"text-align:justif=
y; line-height:normal"><span style=3D"font-size:7.5pt;font-family:Verdana">=
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi
 altra azione derivante dalla conoscenza di queste informazioni sono rigoro=
samente vietate. Qualora abbiate ricevuto questo documento per errore siete=
 cortesemente pregati di darne immediata comunicazione al mittente e di pro=
vvedere alla sua distruzione, Grazie.
</span></span></div>
<p align=3D"justify"><span class=3D"MsoNormal" style=3D"text-align:justify;=
 line-height:normal"><i><span lang=3D"EN-GB" style=3D"font-size:7.5pt;font-=
family:Verdana;mso-ansi-language:EN-GB">This e-mail and any attachments</sp=
an></i><i><span lang=3D"EN-GB" style=3D"font-size:
  7.5pt;mso-bidi-font-size:11.0pt;font-family:Verdana;mso-ansi-language:EN-=
GB">&nbsp;<span class=3D"GramE">is</span>&nbsp;</span></i><i><span lang=3D"=
EN-GB" style=3D"font-size:
  7.5pt;font-family:Verdana;mso-ansi-language:EN-GB">confidential
 and may contain privileged information intended for the addressee(s) only.=
 Dissemination, copying, printing or use by anybody else is unauthorised. I=
f you are not the intended recipient, please delete this message and any at=
tachments and advise the sender
 by return e-mail, Thanks.</span></i><span lang=3D"EN-GB" style=3D"mso-ansi=
-language:EN-GB">
</span></span></p>
<b><span style=3D"font-size:7.5pt;
  font-family:Verdana"><img src=3D"cid:00000000000000000000000000000001@TI.=
Disclaimer" alt=3D"rispetta l'ambiente" width=3D"26" height=3D"40">Rispetta=
 l'ambiente. Non stampare questa mail se non &egrave; necessario.</span></b=
>
<p></p>
</td>
</tr>
</tbody>
</table>
</body>
</html>

--_000_282BBE8A501E1F4DA9C775F964BB21FE3E7C35163BGRFMBX704BA02_--

--_3a074c2f-6ef7-4451-9e2b-960e668eb16e_
Content-Description: logo Ambiente_foglia.jpg
Content-Type: image/jpeg; name="logo Ambiente_foglia.jpg"
Content-Disposition: inline; filename="logo Ambiente_foglia.jpg"
Content-Transfer-Encoding: base64
Content-ID: 00000000000000000000000000000001@TI.Disclaimer

R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo
8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5
+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9
p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxw
SBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0
FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6
YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfl
uh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds
3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaV
OmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDi
oY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAkn
qnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=

--_3a074c2f-6ef7-4451-9e2b-960e668eb16e_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 14:15:10 +0000
Message-ID: <4B85341E.4050902@deployingradius.com>
Date: Wed, 24 Feb 2010 15:13:50 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

From: Avi Lior [mailto:avi@bridgewatersystems.com]
...
> -------
> 
> I am a little confused about the purpose of section 2 RADIUS Data Model and
> the purpose of Section 3 Data Model Issues.
> 
> Is the intent of section 2 to describe the data model then it should just do
> that and move discussions of issues to section 3.

  We can simplify that text.  Do you have any suggestions, or comments
on the suggestions from Hannes?

> ---------------
> Section 2:
> Please define Standard Space

  IANA managed RADIUS attribute space.

> Please define complex attributes. (you do so much later) or give a reference
> to where they are defined.

  Attributes of type *other* than the 5-6 "basic" types already defined.
 (RFC 2865, plus additions)

> "The format of this space is defined by individual vendors but the same TLV
> encoding used by the standard space..."
> 
> Change to:
> 
> "The format of the payload of these attributes is defined by individual
> vendors but the same TLV encoding...."

  OK.

> -----------------
> 2.1.1
> 
>    "However in order
>    to prevent future ambiguities, it is recommended that future RADIUS
>    attribute specifications explicitly define newly created data types
>    at the beginning of the document, and indicate clearly the data type
>    to be used for each attribute."
> 
> Do we care about the structure of the document.  I think the issue is that
> specification should define newly created data types and indicate clearly
> the data type to be used for each attribute.  

  The types should be defined before they are used in the document.

> Second issue: It seems to me that we are okay with folks creating new data
> types in standard space.  I think creation of new data types should be
> discouraged right?

  The doc doesn't say it's OK to create new data types in the standard
space.  It says that the IETF has change control over IETF protocols.
It says that no one else has change control over the "standard space".

> -----------------------
> 
> " It is worth noting that since RADIUS only supports unsigned integers
>    of 32 bits, attributes using signed integer data types or unsigned
>    integer types of other sizes will require code changes, and SHOULD be
>    avoided."
> 
> Why are we talking specifically signed integers?  This is already covered in
> the discussion of creating new types.

  Yes.

> But since we do bring this up - I suppose that we are talking about this
> because this is a common issue.  After all there is no way to represent
> negative numbers in RADIUS (or signed integers).  This creates a problem in
> general and specific when translating Diameter signed integers to RADIUS.  I
> think this document should either remove this paragraph or offer
> guidance/solution.

  Solutions are explicitly *out of scope* of this document.

> --------------
> 2.1.2
> 
> " For these reasons, the tagging scheme described in RFC 2868 is NOT
>    RECOMMENDED for use as a generic grouping mechanism."
> 
> What do you mean by generic grouping mechanism?

  Grouping of attributes?

> What about guidance on how to achieve this?

  Solutions are explicitly *out of scope* of this document.

> --------------------
> Section 2.1.3 Complex Types
> 
> Can we not re-write this section to be a little more concise and to the
> point? 

  Suggested text is welcome.

> "However, some standard attributes do not follow this format."
> Please give an example of an attribute.

  Hmm... I'm not sure what that text is doing there.  I suggest simply
deleting it.

>  "Attributes that use sub-fields instead of using a basic data type are
>    known as "complex attributes". "
> 
> What are sub-fields.

  I'm not sure what's unclear about that.

> Is an attribute that codefies a bit map a complex attribute?  I think yes.
> This is probably the most common complex type that people use.  What
> guidance do we offer to designers that need a bit-field?  Each bit is an
> attribute?  

  We don't.  Solutions are explicitly *out of scope* of this document.

> ---------
> 
> "   * it is easier for the user to enter the data as well-known
>         types, rather than complex structures;"
> This bullet should be removed.  Following good engineer practices of
> seperation of concerns and in this case seperation of presentation and the
> model (MVC).  We dont want to encourage users to edit raw data as codefied
> by the RADIUS protocol.  For example, we dont want user to enter a IPv4
> address as a 32bit value or an Address type. But rather as an IP address in
> dot notation.

  Of course.  So why would we remove text that says entering data as the
proper type?

> --------
>       * it enables additional error checking by leveraging the
>         parsing and validation routines for well-known types;
> 
>       * it simplifies implementations by eliminating special-case
>         attribute-specific parsing.
> 
> These two bullets are the same and should be combined.

  OK.

> --------------
> 
> One of the fundamental goals of the RADIUS protocol design was to
>    allow RADIUS servers to be configured to support new attributes
>    without requiring server code changes.  RADIUS server implementations
>    typically provide support for basic data types, and define attributes
>    in a data dictionary.  This architecture enables a new attribute to
>    be supported by the addition of a dictionary entry, without requiring
>    other RADIUS server code changes.
> 
> This is totally misleading.  We should explain when this is true -- it is
> mostly not true today since RADIUS is increasingly supporting dynamic
> policies and thus always requires code change to handle the introduction of
> any new attribute whether it is an attribute of an existing type or not.

  Sorry, but this point has been hashed to death.

  Every single RADIUS server implementation supports at *least* the
functionality above.  If your implementation supports a more complex
dictionary capability, then it is *also* covered by the above text.

  There is no need to change the text.

> As well the above appears under the complex attribute section 2.1.3 - It is
> true also if we were to introduce a new attribute type.

  Of course.  But that is outside of the scope of the guidelines docuemnt.

> ----------
> 
> " On the RADIUS client, code changes are typically required in order to
>    implement a new attribute. "
> 
> A new attribute or a new attribute type or a complex attribute? Which one?

  The text is clear as-is.  "new" attribute means "new attribute".

> ----
> 
>   "The RADIUS client typically has to
>    compose the attribute dynamically when sending.  When receiving, a
>   RADIUS client needs to be able to parse the attribute and carry out
>    the requested service.  As a result, a detailed understanding of the
>    new attribute is required on clients, and data dictionaries are less
>    useful on clients than on servers.
> 
> Many of the reasons given here are also true for servers. 

  OK.

> ----------
> 
>   "The RADIUS server can be configured to send a new static attribute by
>    entering its type and data format in the RADIUS server dictionary,
>    and then filling in the value within a policy based on the attribute
>    name, data type and type-specific value."
> 
> The above is only true if the new static attribute is an existing type.

  Or if your dictionary definitions support more than existing types.

> --------
> 
> "Code changes can also be required in policy management and in the
>    RADIUS server's receive path.  These changes are due to limitations
>    in RADIUS server policy languages, which typically only provide for
>    limited operations (such as comparisons or arithmetic operations) on
>    the existing data types.  Many existing RADIUS policy languages
>    typically are not capable of parsing sub-elements, or providing
>    sophisticated matching functionality."
> 
> What is a RADIUS server policy language?  

  Do you have a suggested definition, or is "policy language" unclear?

> RADIUS policy languages are not part of the IETF - the IETF did not conduct
> a survey and thus cannot make statements such as these.

  Addressing implementation limitations is well within the scope of
IETF.  The alternative is to pretend that we know nothing about
implementations because we didn't commission an official survey.

> Most policy languages i know about contain REgExp that is sophisticated and
> can extract any information out of any type. Typicially these have been
> first added to be able to parse the RADIUS username.

  Yes.  That functionality goes back if not to the Livingston server,
then at least to multiple implementations after 1996.

> Remove this paragraph.

  There is no demonstrated need.

> ------------------
> The paragraph starting with "Given these limitations..." seems out of place
> since it talks about new types, not complex types....

  I don't see why.  A signed 8-bit integer is a new type that could
require code changes.  It's definitely not a complex type.

> Then it talks about attribute specific parsing which is not really related
> to new types.

  That could be "parsing of new types", or refer to "ad hoc" attributes
that define a new complex type unique to that attribute.

> Then it talks about the intoduction of new complex data types within RADIUS
> attribute specification be avoided.
> 
> So now we have a new thing called a "new complex data type".    Dont we mean
> new types and complex data types?

  Yes.

> Also this paragraph repeats text made earilier  by the bullet points.
> -----
> "The only other exception to the recommendation against complex types
>    is for types that can be treated as opaque data by the RADIUS server."
> 
> The assertions that the document is making in this sentence is wrong and we
> should remove this statement.  We have seen examples like in RADIUS digest
> where we flattened out an attribute to create more then a dozen attributes.
> There are other cases as well.  Remove this paragraph.

  There is no need.  The rest of the text in the document should make it
clear that design is a balancing act, not a set of hard and fast rules.

> ------
> 
>  " If the RADIUS Server simply passes the contents of an attribute to
>    some non-RADIUS portion of the network, then the data is opaque, and
>    SHOULD be defined to be of type String.  A concrete way of judging
>    this requirement is whether or not the attribute definition in the
>    RADIUS document contains delineated fields for sub-parts of the data.
>    If those fields need to be delineated in RADIUS, then the data is not
>    opaque, and it SHOULD be separated into individual RADIUS attributes."
> 
> 
> The document is attempting to define a RADIUS Server architecture.

  No.  It is acknowledging that RADIUS servers may exist within a wider
framework.

  Is this idea controversial?

>  We
> should do this properly.  An equally valid architecture is the Diameter one
> where the Server is composed of a lower layer defined by RFC 3588 and an
> application layer.  We should state that as well.

  Defining new RADIUS architectures is *out of scope* of this document.

> Here the document gives an impression that the only "application" layer
> possible is some foreign entity not part of the RADIUS server - that is just
> not true today.

  The text contains no reference to an "application" layer.  And there
is nothing in the text that restricts it to *only* an application layer.

  So your comment is therefore not relevant to the document.

> ---------
> 2.1.4
> " RADIUS specifications define how an existing service or protocol can
>    be provisioned using RADIUS.  Therefore, it is expected that a RADIUS
>    attribute specification will reference documents defining the
>    protocol or service to be provisioned.  Within the IETF, a RADIUS
>    attribute specification SHOULD NOT be used to define the protocol or
>    service being provisioned.  New services using RADIUS for
>    provisioning SHOULD be defined elsewhere and referenced in the RADIUS
>    specification."
> 
> 
> I am confused by what we are trying to say in this section.

  OK.

> -------
> 
> "New attributes, or new values of existing attributes, SHOULD NOT be
>    used to define new RADIUS commands.  RADIUS attributes are intended
>    to:"
> 
> Shouldn't this be a different section.

  Like... where?

> ----------
> 2.2
> 
> " However, instead of doing this, vendors have defined the following
>    non-standard VSA formats:"
> 
> The standard allows Vendors to define their VSA as they wish.  How can you
> say "non-standard VSA formats"?

  RFC 2865 defines a suggested VSA format.  Vendors are free to do as
they wish, including defining formats not recommended by the standards.
 So... this means "non-standard format".

> Howecer instead of following the recommendation vendors have defiend the
> following:
> 
> ------------
> 
>   "All VSA schemes that do not follow the [RFC2865] recommendations are
>    NOT RECOMMENDED.  These non-standard formats will typically not be
>    implementable without RADIUS server code changes.  This includes all
>    the above formats, as well as Vendor types of more than 8 bits,
>    vendor lengths of less than 8 bits, vendor lengths of more than 8
>    bits and Vendor-Specific contents that are not in Type-Length-Value
>    format."
> 
> Its up to the vendors or SDO to decide and the specification allows for
> that.  RFC2865 makes a recommendation and we should just leave it at that.

  So the guidelines document shouldn't have guidelines for attribute design?

> You can state the problems that this may create but I think the document is
> out of bounds when it states that it is not recommended.  2865 makes a
> recommendation and that is enough.

  If that's true, the *entire* guidelines document is unnecessary.

  However... vendors have created *unnecessarily* different VSA
encodings.  The IETF is well within it's right as owner of the RADIUS
protocol to recommend how vendors use it.

> ---------------
> 
> " Although [RFC2865] does not mandate it, implementations commonly
>    assume that the Vendor Id can be used as a key to determine the on-
>    the-wire format of a VSA.  Vendors therefore SHOULD NOT use multiple
>    formats for VSAs that are associated with a particular Vendor Id.  A
>    vendor wishing to use multiple VSA formats SHOULD request one Vendor
>    Id for each VSA format that they will use."
> 
> What do you mean by on-the-wire format?  

  I'm unsure how to answer that.  The definition should be clear.

> ---------
> Section 3 is not only about data model issues.
> 
> We need a better name.

  Do you have a suggestion?

> -----------
> 
> 3.3
> 
> Why are we repeating the recommendations fo 5080.  Just remind people that
> they need to read it.

  Do you have suggested replacement text?

> ---------
> 
> Section 5
> 
> "Where new RADIUS attributes encapsulate complex data types, or transport
> opaque data, the security considerations discussed in Sectiont 2.1.4 SHOULD
> be addressed"
> 
> The contents of 2.1.4 was moved to the security section

  OK.

> -----
> 5.1
> 
> The title should be Complex Types and New Data types no?

  Sure.

> The text in this section should be fixed as well.  Sometimes it refers to
> one where the other is also applicable.

  Do you have suggested replacement text?

> -------
> 
>    "Any system consuming opaque data that originates from a RADIUS system
>    SHOULD be properly isolated from that RADIUS system, and SHOULD run
>    with minimal privileges.  Any potential vulnerabilities in the non-
>    RADIUS system will then have minimal impact on the security of the
>    system as a whole."
> 
> fear mongering a bit here and not true???  I can inject code in the opaque
> data which could cause the system to run at higher privelages. Can we make
> more concrete recommendations such as use care to validate the opaque data
> for example to ensure no buffer overruns etc etc....It is pretty standard
> practice to validate data coming from potentially untrusted sources or that
> can be compromized along the way.

  Do you have suggested replacement text?

> 
> 
> Appendix A
> 
> A.1
> 
> Simple Data vs Radius Data types.  They are the same no?  We need to use the
> term consistantly throughout the document.

  Sure.

> A.1.2
> 
> *Complex data types...which the RADIUS servers are expected to parse..."
> 
> I think you need to explain the model here.  This is a common theme
> throughout the document.  What is a RADIUS server?

  Suggest some text.

  Alan DeKok.



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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 09:54:59 +0000
Message-ID: <4B84F755.2080803@restena.lu>
Date: Wed, 24 Feb 2010 10:54:29 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: Re: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6AECE5BB270C1FDEC2A3E046"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6AECE5BB270C1FDEC2A3E046
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Am 23.02.2010 21:17, schrieb Bernard Aboba:
>
> During the RADEXT Virtual Interim, we discussed adoption of "RADIUS
> Attributes for IPv6 Access Networks" as a RADEXT WG work item.
>
> =20
>
> We would now like to request mailing list confirmation of the decision
> to adopt this draft.
>
> =20
>
> The document is available here:
>
> http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02
>
> =20
>
> If you have an opinion on the adoption  of this document as a RADEXT
> WG work item, please reply to this email.
>

The presentation yesterday convinced me that it solves a real-world
problem. I support adoption of the document.

Greetings,

Stefan Winter

> =20
>
> =20
>
> =20
>


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473



--------------enig6AECE5BB270C1FDEC2A3E046
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuE91kACgkQ+jm90f8eFWYBWQCfU4zVJ1B6HncKs9qx2p/oheKJ
LX4An2r4mS4AonQBTBkBiBYUPF1KB7hA
=NCxp
-----END PGP SIGNATURE-----

--------------enig6AECE5BB270C1FDEC2A3E046--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 09:34:22 +0000
Message-ID: <4B84F26C.8070305@deployingradius.com>
Date: Wed, 24 Feb 2010 10:33:32 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> We would now like to request mailing list confirmation of the decision
> to adopt this draft.

  I support adoption.

Nits: IPv6-DNS-Server-Address doesn't follow the same naming schema as
"NAS-IPv6-Address" and others.  It could instead be
"DNS-Server-IPv6-Address".

  This is minor, though.  It doesn't really matter either way.

  Alan DeKok.


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 07:53:40 +0000
Message-ID: <4B84DAD8.1000700@restena.lu>
Date: Wed, 24 Feb 2010 08:52:56 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0
MIME-Version: 1.0
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Issue 306: Suggested text
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig314D86BC6D608DEBD9A65BBA"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig314D86BC6D608DEBD9A65BBA
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Hi,

I'm currently assembling the -06 draft of RADIUS over TLS. This is a
proposed new section 2.3 to cover issue "NAS Identity":

Please comment...

2.3.  Connecting Client Identity

   In RADIUS, clients are uniquely identified by their IP address.  This
   does not permit to determine whether the connecting entity is a NAS
   or a different server which proxies a request.  When NAT is used on
   the path to the server, it also does not permit to determine whether
   there is more than one entity connecting from the same IP address.

   RADIUS over TLS makes it possible to preserve this traditional RADIUS
   semantics by identifying a connecting client by the IP address which
   initiated the TLS connection.  In addition, it does permit a much
   more fine-grained identification.  The parameters of the TLS
   connection can be attributed to the RADIUS packets inside the TLS
   connection.  An implementation of RADIUS over TLS should expose as
   many details of the TLS connection which belongs to an incoming
   RADIUS packet as possible to the application administrator to allow
   the administrator to define the identification criteria which are
   applicable to his desired operational model.  In X.509 certificate
   operation, at least the following parameters of the TLS connection
   should be exposed:

   o  Originating IP address

   o  Certificate Fingerprint

   o  Issuer

   o  Subject

   o  all X509v3 Extended Key Usage

   o  all X509v3 Subject Alternative Name

   o  all X509v3 Certificate Policies

   In TLS-PSK operation, at least the following parameters of the TLS
   connection should be exposed:

   o  Originating IP address

   o  TLS Identifier

Greetings,

Stefan Winter

(I created this text outside of my sponsor project's time)

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473



--------------enig314D86BC6D608DEBD9A65BBA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuE2t4ACgkQ+jm90f8eFWaqiACfZV7cuaGVeVlZITtdjRpRuk4T
s1IAn2DSMdvZED+MLZmUh+9jh00CJ6sc
=QHDY
-----END PGP SIGNATURE-----

--------------enig314D86BC6D608DEBD9A65BBA--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 06:07:26 +0000
Message-ID: <BLU137-W238F693E6D06B45058E0C393410@phx.gbl>
Content-Type: multipart/alternative; boundary="_3c60324e-b72b-4e3b-9588-a8fab915295b_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: PROTO writeup for Status-Server document
Date: Tue, 23 Feb 2010 22:06:39 -0800
MIME-Version: 1.0

--_3c60324e-b72b-4e3b-9588-a8fab915295b_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


PROTO Writeup for draft-ietf-radext-status-server
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
http://tools.ietf.org/html/draft-ietf-radext-status-server
=20
   (1.a)  Who is the Document Shepherd for this document?  Has the
      Document Shepherd personally reviewed this version of the document
      and=2C in particular=2C does he or she believe this version is ready
      for forwarding to the IESG for publication?
=20
Bernard Aboba is the document shepherd.  I have personally reviewed
the document=2C and believe it is ready for publication as an Informational
RFC.=20
=20
   (1.b)  Has the document had adequate review both from key members of
      the interested community and others?  Does the Document Shepherd
      have any concerns about the depth or breadth of the reviews that
      have been performed?
=20
The goal of this document is to specify the Status-Server functionality
that has been implemented in the field.  Therefore=2C the major concern
is whether the document reflects existing implementations.  So
far the specification has been reviewed by the implementers of the
RADIATOR and FreeRADIUS servers=2C both of which support Status-Server.
This would appear to address the review depth issue.=20

   (1.c)  Does the Document Shepherd have concerns that the document
      needs more review from a particular or broader perspective=2C e.g.=2C
      security=2C operational complexity=2C someone familiar with AAA=2C
      internationalization or XML?
=20
No.=20
=20
   (1.d)  Does the Document Shepherd have any specific concerns or
      issues with this document that the Responsible Area Director
      and/or the IESG should be aware of?  For example=2C perhaps he or
      she is uncomfortable with certain parts of the document=2C or has
      concerns whether there really is a need for it.  In any event=2C if
      the interested community has discussed those issues and has
      indicated that it still wishes to advance the document=2C detail
      those concerns here.
=20
Status-Server is being published as an Informational RFC due to
limitations of the design which are documented in the Applicability
section.  However=2C the goal is largely to document what has
been implemented rather than trying to re-design it.=20

   (1.e)  How solid is the consensus of the interested community behind
      this document?  Does it represent the strong concurrence of a few
      individuals=2C with others being silent=2C or does the interested
      community as a whole understand and agree with it?
=20
There is consensus within the RADEXT WG to publish the document as
an Informational RFC. =20
=20
   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
      discontent?  If so=2C please summarise the areas of conflict in
      separate email messages to the Responsible Area Director.  (It
      should be in a separate email because this questionnaire is
      entered into the ID Tracker.)
=20
No.=20
=20
   (1.g)  Has the Document Shepherd personally verified that the
      document satisfies all ID nits?  (See
      http://www.ietf.org/ID-Checklist.html and
      http://tools.ietf.org/tools/idnits/).  Boilerplate checks are not
      enough=3B this check needs to be thorough.  Has the document met all
      formal review criteria it needs to=2C such as the MIB Doctor=2C media
      type and URI type reviews?
=20
The document is clean in idnits:

idnits 2.12.00=20

tmp/draft-ietf-radext-status-server-06.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  -------------------------------------------------------------------------=
---

     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: Informational
  -------------------------------------------------------------------------=
---

     No issues found here.

     No nits found.
---------------------------------------------------------------------------=
-----
=20
   (1.h)  Has the document split its references into normative and
      informative?  Are there normative references to documents that are
      not ready for advancement or are otherwise in an unclear state?
      If such normative references exist=2C what is the strategy for their
      completion?  Are there normative references that are downward
      references=2C as described in [RFC3967]?  If so=2C list these downwar=
d
      references to support the Area Director in the Last Call procedure
      for them [RFC3967].
=20
The references in the document have been split into normative and
informative.=20

Normative references are all stable documents published as RFCs.
=20
   (1.i)  Has the Document Shepherd verified that the document IANA
      consideration section exists and is consistent with the body of
      the document?  If the document specifies protocol extensions=2C are
      reservations requested in appropriate IANA registries?  Are the
      IANA registries clearly identified?  If the document creates a new
      registry=2C does it define the proposed initial contents of the
      registry and an allocation procedure for future registrations?
      Does it suggested a reasonable name for the new registry?  See
      [I-D.narten-iana-considerations-rfc2434bis].  If the document
      describes an Expert Review process has Shepherd conferred with the
      Responsible Area Director so that the IESG can appoint the needed
      Expert during the IESG Evaluation?
=20
The IANA considerations section (7) exists=2C and is consistent with
the body of the document.  Note that no new registries are created
nor does the document require assignment of any new protocol parameters=2C=
=20
since the Status-Server Code (12) was assigned in RFC 2865.=20
=20
   (1.j)  Has the Document Shepherd verified that sections of the
      document that are written in a formal language=2C such as XML code=2C
      BNF rules=2C MIB definitions=2C etc.=2C validate correctly in an
      automated checker?

Not applicable.
=20
   (1.k)  The IESG approval announcement includes a Document
      Announcement Write-Up.  Please provide such a Document
      Announcement Writeup?  Recent examples can be found in the
      "Action" announcements for approved documents.  The approval
      announcement contains the following sections:
=20
      Technical Summary

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

The RADEXT WG elected to recommend this document for publication
as an Informational RFC rather than as a standards-Track RFC due
to concerns about problems with deployed implementations.  The
fixes recommended within the document are compatible with=20
existing servers that receive Status-Server packets=2C but impose new
security requirements on clients that send Status-Server packets.
=20
      Document Quality
=20
The document has been reviewed by IETF RADEXT WG members.=20
An expert review has been carried out by Ignacio Goyret.=20
=20
Status-Server has been implemented by multiple vendors=2C=20
including RADIATOR=2C FreeRADIUS and Cistron.=20
=20
      Personnel
=20
Bernard Aboba is the document shepherd for this document.=20
Dan Romascanu is the responsible AD.=20










 		 	   		  =

--_3c60324e-b72b-4e3b-9588-a8fab915295b_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
PROTO Writeup for draft-ietf-radext-status-server<br>=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>&nbsp=3B<br>http://t=
ools.ietf.org/html/draft-ietf-radext-status-server<br>&nbsp=3B<br>&nbsp=3B&=
nbsp=3B (1.a)&nbsp=3B Who is the Document Shepherd for this document?&nbsp=
=3B Has the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Document Shepherd p=
ersonally reviewed this version of the document<br>&nbsp=3B&nbsp=3B&nbsp=3B=
&nbsp=3B&nbsp=3B and=2C in particular=2C does he or she believe this versio=
n is ready<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B for forwarding to th=
e IESG for publication?<br>&nbsp=3B<br>Bernard Aboba is the document shephe=
rd.&nbsp=3B I have personally reviewed<br>the document=2C and believe it is=
 ready for publication as an Informational<br>RFC. <br>&nbsp=3B<br>&nbsp=3B=
&nbsp=3B (1.b)&nbsp=3B Has the document had adequate review both from key m=
embers of<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B the interested commun=
ity and others?&nbsp=3B Does the Document Shepherd<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B have any concerns about the depth or breadth of the rev=
iews that<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B have been performed?<=
br>&nbsp=3B<br>The goal of this document is to specify the Status-Server fu=
nctionality<br>that has been implemented in the field.&nbsp=3B Therefore=2C=
 the major concern<br>is whether the document reflects existing implementat=
ions.&nbsp=3B So<br>far the specification has been reviewed by the implemen=
ters of the<br>RADIATOR and FreeRADIUS servers=2C both of which support Sta=
tus-Server.<br>This would appear to address the review depth issue. <br><br=
>&nbsp=3B&nbsp=3B (1.c)&nbsp=3B Does the Document Shepherd have concerns th=
at the document<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B needs more revi=
ew from a particular or broader perspective=2C e.g.=2C<br>&nbsp=3B&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B security=2C operational complexity=2C someone famil=
iar with AAA=2C<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B internationaliz=
ation or XML?<br>&nbsp=3B<br>No. <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.d)&nbs=
p=3B Does the Document Shepherd have any specific concerns or<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B issues with this document that the Responsib=
le Area Director<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B and/or the IES=
G should be aware of?&nbsp=3B For example=2C perhaps he or<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B she is uncomfortable with certain parts of the =
document=2C or has<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B concerns whe=
ther there really is a need for it.&nbsp=3B In any event=2C if<br>&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B the interested community has discussed thos=
e issues and has<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B indicated that=
 it still wishes to advance the document=2C detail<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B those concerns here.<br>&nbsp=3B<br>Status-Server is be=
ing published as an Informational RFC due to<br>limitations of the design w=
hich are documented in the Applicability<br>section.&nbsp=3B However=2C the=
 goal is largely to document what has<br>been implemented rather than tryin=
g to re-design it. <br><br>&nbsp=3B&nbsp=3B (1.e)&nbsp=3B How solid is the =
consensus of the interested community behind<br>&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B this document?&nbsp=3B Does it represent the strong concurren=
ce of a few<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B individuals=2C with=
 others being silent=2C or does the interested<br>&nbsp=3B&nbsp=3B&nbsp=3B&=
nbsp=3B&nbsp=3B community as a whole understand and agree with it?<br>&nbsp=
=3B<br>There is consensus within the RADEXT WG to publish the document as<b=
r>an Informational RFC.&nbsp=3B <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.f)&nbsp=
=3B Has anyone threatened an appeal or otherwise indicated extreme<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B discontent?&nbsp=3B If so=2C please sum=
marise the areas of conflict in<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
 separate email messages to the Responsible Area Director.&nbsp=3B (It<br>&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B should be in a separate email becau=
se this questionnaire is<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B entere=
d into the ID Tracker.)<br>&nbsp=3B<br>No. <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B=
 (1.g)&nbsp=3B Has the Document Shepherd personally verified that the<br>&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B document satisfies all ID nits?&nbsp=
=3B (See<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B http://www.ietf.org/ID=
-Checklist.html and<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B http://tool=
s.ietf.org/tools/idnits/).&nbsp=3B Boilerplate checks are not<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B enough=3B this check needs to be thorough.&n=
bsp=3B Has the document met all<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
 formal review criteria it needs to=2C such as the MIB Doctor=2C media<br>&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B type and URI type reviews?<br>&nbsp=
=3B<br>The document is clean in idnits:<br><br>idnits 2.12.00 <br><br>tmp/d=
raft-ietf-radext-status-server-06.txt:<br><br>&nbsp=3B Checking boilerplate=
 required by RFC 5378 and the IETF Trust (see<br>&nbsp=3B http://trustee.ie=
tf.org/license-info):<br>&nbsp=3B -----------------------------------------=
-----------------------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
 No issues found here.<br><br>&nbsp=3B Checking nits according to http://ww=
w.ietf.org/ietf/1id-guidelines.txt:<br>&nbsp=3B ---------------------------=
-------------------------------------------------<br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B No issues found here.<br><br>&nbsp=3B Checking nits accordin=
g to http://www.ietf.org/ID-Checklist.html:<br>&nbsp=3B -------------------=
---------------------------------------------------------<br><br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B No issues found here.<br><br>&nbsp=3B Miscellaneous =
warnings:<br>&nbsp=3B -----------------------------------------------------=
-----------------------<br><br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issu=
es found here.<br><br>&nbsp=3B Checking references for intended status: Inf=
ormational<br>&nbsp=3B ----------------------------------------------------=
------------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issues =
found here.<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No nits found.<br>-----=
---------------------------------------------------------------------------=
<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.h)&nbsp=3B Has the document split its r=
eferences into normative and<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B in=
formative?&nbsp=3B Are there normative references to documents that are<br>=
&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B not ready for advancement or are o=
therwise in an unclear state?<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B I=
f such normative references exist=2C what is the strategy for their<br>&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B completion?&nbsp=3B Are there normativ=
e references that are downward<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B =
references=2C as described in [RFC3967]?&nbsp=3B If so=2C list these downwa=
rd<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B references to support the Ar=
ea Director in the Last Call procedure<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&=
nbsp=3B for them [RFC3967].<br>&nbsp=3B<br>The references in the document h=
ave been split into normative and<br>informative. <br><br>Normative referen=
ces are all stable documents published as RFCs.<br>&nbsp=3B<br>&nbsp=3B&nbs=
p=3B (1.i)&nbsp=3B Has the Document Shepherd verified that the document IAN=
A<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B consideration section exists =
and is consistent with the body of<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B the document?&nbsp=3B If the document specifies protocol extensions=2C =
are<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B reservations requested in a=
ppropriate IANA registries?&nbsp=3B Are the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B IANA registries clearly identified?&nbsp=3B If the document cr=
eates a new<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B registry=2C does it=
 define the proposed initial contents of the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B registry and an allocation procedure for future registrations=
?<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Does it suggested a reasonabl=
e name for the new registry?&nbsp=3B See<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B [I-D.narten-iana-considerations-rfc2434bis].&nbsp=3B If the doc=
ument<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B describes an Expert Revie=
w process has Shepherd conferred with the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B Responsible Area Director so that the IESG can appoint the need=
ed<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Expert during the IESG Evalu=
ation?<br>&nbsp=3B<br>The IANA considerations section (7) exists=2C and is =
consistent with<br>the body of the document.&nbsp=3B Note that no new regis=
tries are created<br>nor does the document require assignment of any new pr=
otocol parameters=2C <br>since the Status-Server Code (12) was assigned in =
RFC 2865. <br>&nbsp=3B<br>&nbsp=3B&nbsp=3B (1.j)&nbsp=3B Has the Document S=
hepherd verified that sections of the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B document that are written in a formal language=2C such as XML code=
=2C<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B BNF rules=2C MIB definition=
s=2C etc.=2C validate correctly in an<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&n=
bsp=3B automated checker?<br><br>Not applicable.<br>&nbsp=3B<br>&nbsp=3B&nb=
sp=3B (1.k)&nbsp=3B The IESG approval announcement includes a Document<br>&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Announcement Write-Up.&nbsp=3B Plea=
se provide such a Document<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Anno=
uncement Writeup?&nbsp=3B Recent examples can be found in the<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B&nbsp=3B "Action" announcements for approved document=
s.&nbsp=3B The approval<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B announc=
ement contains the following sections:<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B Technical Summary<br><br>This document specifies a depl=
oyed extenion to RADIUS which enables<br>clients to query the status of a R=
ADIUS server.&nbsp=3B While the<br>Status-Server Code (12) was defined as e=
xperimental in RFC 2865<br>Section 3=2C details of the protocol's operation=
 have not been<br>documented until now.&nbsp=3B <br>&nbsp=3B<br>&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B Working Group Summary<br><br>The RADEXT WG el=
ected to recommend this document for publication<br>as an Informational RFC=
 rather than as a standards-Track RFC due<br>to concerns about problems wit=
h deployed implementations.&nbsp=3B The<br>fixes recommended within the doc=
ument are compatible with <br>existing servers that receive Status-Server p=
ackets=2C but impose new<br>security requirements on clients that send Stat=
us-Server packets.<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B =
Document Quality<br>&nbsp=3B<br>The document has been reviewed by IETF RADE=
XT WG members. <br>An expert review has been carried out by Ignacio Goyret.=
 <br>&nbsp=3B<br>Status-Server has been implemented by multiple vendors=2C =
<br>including RADIATOR=2C FreeRADIUS and Cistron. <br>&nbsp=3B<br>&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Personnel<br>&nbsp=3B<br>Bernard Aboba is t=
he document shepherd for this document. <br>Dan Romascanu is the responsibl=
e AD. <br><br><br><br><br><br><br><br><br><br><table style=3D"border-top: 1=
px solid black=3B font-weight: bold=3B font-family: 'Segoe UI'=2CTahoma=2Cs=
an-serif=3B"><tbody><tr><td><a href=3D"http://im.live.com/Messenger/IM/Home=
/?source=3DEML_WLHM_GreaterGood" style=3D"font-size: 9pt=3B color: rgb(1=2C=
 132=2C 203)=3B text-decoration: none=3B"><span style=3D"padding: 0px 24px=
=3B font-size: 8pt=3B color: rgb(63=2C 181=2C 85)=3B text-decoration: under=
line=3B"></span></a><br></td></tr></tbody></table> 		 	   		  </body>
</html>=

--_3c60324e-b72b-4e3b-9588-a8fab915295b_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 24 Feb 2010 02:57:02 +0000
Message-ID: <BLU137-DS15DE29B915A016EA5984F093410@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Internet Draft Cut-off Dates Reminder (fwd)
Date: Tue, 23 Feb 2010 18:56:10 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_047F_01CAB4B9.DD283670"
Thread-Index: Acq0/OsOsfaxAXO+St+/+lUubkIr6A==
Content-Language: en-us

------=_NextPart_000_047F_01CAB4B9.DD283670
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit





From: IETF Secretariat <ietf-secretariat
<mailto:ietf-secretariat%20at%20ietf.org>  at ietf.org>

Date: February 22, 2010 9:00:01 PM CEST

To: ietf-announce at ietf.org <mailto:ietf-announce%20at%20ietf.org> 

Subject: Internet Draft Cut-off Dates Reminder 

 


This is a reminder that the Internet Draft Cut-off Dates are approaching.


The initial draft (version -00) cut-off date is Monday, March 1, 2010. 
These submissions are due by 17:00 PST (01:00 Tuesday, March 2 UTC).

The Internet Draft final submission (version -01 and up) cut-off is
Monday, March 8, 2010 at 17:00 PST (01:00 Tuesday, March 2 UTC).

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/idst/upload.cgi
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

 


------=_NextPart_000_047F_01CAB4B9.DD283670
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.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>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>From: </span></b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif"'>IETF
Secretariat &lt;<a =
href=3D"mailto:ietf-secretariat%20at%20ietf.org">ietf-secretariat
at ietf.org</a>&gt;</span><o:p></o:p></p>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>Date: </span></b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif"'>February
22, 2010 9:00:01 PM CEST</span><o:p></o:p></p>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>To: </span></b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif"'><a
href=3D"mailto:ietf-announce%20at%20ietf.org">ietf-announce at =
ietf.org</a></span><o:p></o:p></p>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.5pt;font-family:"Helvetica","sans-serif";
color:black'>Subject: </span></b><b><span =
style=3D'font-size:10.5pt;font-family:
"Helvetica","sans-serif"'>Internet Draft Cut-off Dates Reminder<span
class=3Dapple-converted-space>&nbsp;</span></span></b><o:p></o:p></p>

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

<p class=3DMsoNormal><br>
This is a reminder that the Internet Draft Cut-off Dates are =
approaching.<br>
<br>
<br>
The initial draft (version -00) cut-off date is Monday, March 1, 2010. =
<br>
These submissions are due by 17:00 PST (01:00 Tuesday, March 2 UTC).<br>
<br>
The Internet Draft final submission (version -01 and up) cut-off is<br>
Monday, March 8, 2010 at 17:00 PST (01:00 Tuesday, March 2 UTC).<br>
<br>
All drafts can be uploaded using the ID submission tool located =
here:<br>
<a =
href=3D"https://datatracker.ietf.org/idst/upload.cgi">https://datatracker=
.ietf.org/idst/upload.cgi</a><br>
_______________________________________________<br>
IETF-Announce mailing list<br>
IETF-Announce at ietf.org<br>
https://www.ietf.org/mailman/listinfo/ietf-announce<o:p></o:p></p>

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

</div>

</body>

</html>

------=_NextPart_000_047F_01CAB4B9.DD283670--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 22:03:54 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
CC: Maglione Roberta <roberta.maglione@telecomitalia.it>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Tue, 23 Feb 2010 17:03:25 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Thread-Index: Acq01AapUUCqFjABR1CW7ENRLjZowg==
Message-ID: <1456B38F-1724-4C35-BCE6-8E54E1A79D9E@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Why do you need separate counters for IPv6?

Is it because you want to have different counters for different IP technolo=
gy at the same time in the accounting stream?

If yes there are other problems with that approach.  Accounting is used for=
 both volume and time accounting.  While having distinct volume counters fo=
r one technology may solve the volume aspect it does not address the time a=
spect.  Consider the fact that even if you have both IPv4 and IPv6 enabled =
one may start at a different time then the other and one may stop at a diff=
erent time then the other.

There are other information elements that are accounted for that may be spe=
cific to a particular IP technology and not the other.

As well, a user may have multiple IPv4 addresses and multiple IPv6 addresse=
s.

So I am concerned that you are not really addressing all the issues. =20

Separate accounting streams per IP session solves these problems.

What is the problem with having separate accounting streams per IP session?

> Hi Avi,
>   Thanks for your comments.
>=20
> On 10-02-23 12:38 PM, Avi Lior wrote:
>> Hi,'
>>=20
>> What makes you say that the existing accounting attributes for octet/pac=
ket counts are for IPv4 ?
>=20
> You are right. They are not. They are not protocol specific. We are=20
> looking to define separate counters for IPv6. We will change the wording=
=20
> in the draft to correspond to this.
>=20
>>=20
>> Wouldn't the IP address contained in the IP session be sufficient to cre=
ate the context for the accounting message?
>=20
> This will require us to send two different messages (one for IPv6 only=20
> and one for all protocols combined together).
>=20
> Thanks
> Suresh


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 21:20:24 +0000
Message-ID: <4B844673.1080206@deployingradius.com>
Date: Tue, 23 Feb 2010 22:19:47 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
CC: radiusext@ops.ietf.org
Subject: Re: My Suggestions regarding the RADIUS Design Guidelines Document
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hannes Tschofenig wrote:
> I was asked what specifically has to be changed in the document in order to
> address my comments. Here is a short summary: 
> 
> 1) Shorten Section 2 and Section 3 considerably. I believe that readability
> can be improved by shortening the text. Funny enough the right text is
> already in the draft, namely in the appendix. I am proposing a new structure
> at the bottom of this mail. 

  On a quick scan, it looks good.

> 2) Be precise what you mean by "basic" vs. "complex" attribute

  "basic" == "defined (mostly) in an existing RFC"

  "complex" == "everything else".

> Section 2 is quite fuzzy in it's description. I would instead re-use the
> text you have in the appendix. 

  OK.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 20:43:42 +0000
Message-ID: <4B843CD2.8080406@ericsson.com>
Date: Tue, 23 Feb 2010 15:38:42 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Avi Lior <avi@bridgewatersystems.com>
CC: Maglione Roberta <roberta.maglione@telecomitalia.it>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, "=?ISO-8859-1?Q?Varga_Bal=E1?= =?ISO-8859-1?Q?zs?=" <varga.balazs@telekom.hu>
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Hi Avi,
   Thanks for your comments.

On 10-02-23 12:38 PM, Avi Lior wrote:
> Hi,'
> 
> What makes you say that the existing accounting attributes for octet/packet counts are for IPv4 ?

You are right. They are not. They are not protocol specific. We are 
looking to define separate counters for IPv6. We will change the wording 
in the draft to correspond to this.

> 
> Wouldn't the IP address contained in the IP session be sufficient to create the context for the accounting message?

This will require us to send two different messages (one for IPv6 only 
and one for all protocols combined together).

Thanks
Suresh

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 20:17:50 +0000
Message-ID: <BLU137-DS3A3CA71925E59BFE3F28493420@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Call for adoption of "RADIUS Attributes for IPv6 Access Networks"
Date: Tue, 23 Feb 2010 12:17:39 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CAB482.336844E0"
Thread-Index: Acq0xT8uBPxYy20STV+Ko3u61xMO7g==
Content-Language: en-us

------=_NextPart_000_000A_01CAB482.336844E0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

During the RADEXT Virtual Interim, we discussed adoption of "RADIUS
Attributes for IPv6 Access Networks" as a RADEXT WG work item. 

 

We would now like to request mailing list confirmation of the decision to
adopt this draft. 

 

The document is available here:

http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access-02

 

If you have an opinion on the adoption  of this document as a RADEXT WG work
item, please reply to this email. 

 

 

 


------=_NextPart_000_000A_01CAB482.336844E0
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:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal>During the RADEXT Virtual Interim, we discussed =
adoption of &quot;RADIUS
Attributes for IPv6 Access Networks&quot; as a RADEXT WG work item. =
<o:p></o:p></p>

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

<p class=3DMsoNormal>We would now like to request mailing list =
confirmation of
the decision to adopt this draft. <o:p></o:p></p>

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

<p class=3DMsoNormal>The document is available here:<o:p></o:p></p>

<p =
class=3DMsoNormal>http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-=
access-02<o:p></o:p></p>

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

<p class=3DMsoNormal>If you have an opinion on the adoption&nbsp; of =
this
document as a RADEXT WG work item, please reply to this email. =
<o:p></o:p></p>

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

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

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

</div>

</body>

</html>

------=_NextPart_000_000A_01CAB482.336844E0--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 20:17:45 +0000
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: <radiusext@ops.ietf.org>
Subject: My Suggestions regarding the RADIUS Design Guidelines Document
Date: Tue, 23 Feb 2010 22:07:04 +0200
Message-ID: <000001cab4c3$c7ca5970$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acq0w8SHLK8n3aorSWOrkCaPAkSXIg==

-- I believe this mail never made it to the list (and I hope I got the right
version)

Hi all, 

I was asked what specifically has to be changed in the document in order to
address my comments. Here is a short summary: 

1) Shorten Section 2 and Section 3 considerably. I believe that readability
can be improved by shortening the text. Funny enough the right text is
already in the draft, namely in the appendix. I am proposing a new structure
at the bottom of this mail. 

2) Be precise what you mean by "basic" vs. "complex" attribute

Section 2 is quite fuzzy in it's description. I would instead re-use the
text you have in the appendix. 

Ciao
Hannes

-----------------------

2.  RADIUS Data Model

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

Unlike SNMP, first defined in [RFC1157] and [RFC1155], RADIUS does not
define a formal data definition language.  The data type of RADIUS
attributes is not transported on the wire.  Rather, the data type of a
RADIUS attribute is fixed when an attribute is defined.

To explain the implications of this early RADIUS design decision we
distinguish two types of attributes, namely 'basic' and 'complex'. Basic
attributes are those encapsulated in a [RFC2865] format RADIUS attribute, or
in a [RFC2865] format RADIUS VSA that uses one of the existing RADIUS data
types:

 * << Copy the text from Section A.1.1 in here. >> 

All other attributes are referred as complex attributes. 

When designing new RADIUS attributes a protocol designer has to ask himself
/ herself the following two questions: 

 (a) Will this attribute require code changes at the RADIUS server when sent
from the RADIUS server to the RADIUS client? Typically, data than can be
encoded using basic data types will not require code changes to a RADIUS
server. 

 (b) Will this attribute require code changes at the RADIUS server when
received by the RADIUS server?  

Note: It is assumed that code changes to the RADIUS client are always
necessary to implement the additional functionality offered by the newly
defined RADIUS attribute(s).
 
Many RADIUS server implementations utilize a data dictionary to recognize
data types and also offer a simple policy language that only provides
limited operations (such as comparisons or arithmetic operations) on these
basic data types. Many existing RADIUS policy languages typically are not
capable of parsing sub-elements, or providing sophisticated matching
functionality.

Ideally, a protocol designer might want to write a specification that does
not require code changes to most exist RADIUS servers. Sometimes, however,
code changes will be unavoidable and they lead to additional implementation
efforts, more testing overhead and additional security vulernabilities as
more lines of code lead to more potential vulnerabilities. It is RECOMMENDED
that protocol designers briefly describe their expected processing model and
in particular if they expect RADIUS server changes (for example due to the
need for the RADIUS server to analyse incoming RADIUS attributes and to
return responses based on the presence of a more sophisticated policy
language). 

>>> I wouldn't actually say too much more here in this section. I don't have
a good suggestion for placing the text about the polymorphic attributes. <<<


3. Standard vs. Vendor-specific Attribute Space

>>> discussion about standard vs. vendor-specific attribute space. 


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 17:39:04 +0000
From: Avi Lior <avi@bridgewatersystems.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Tue, 23 Feb 2010 12:38:18 -0500
Subject: Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Index: Acq0rvzFN72H/re8Rni0tRhA8+Eeyg==
Message-ID: <D4C5B5FE-5C59-4BF2-8844-984A8FA8CB5B@bridgewatersystems.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,'

What makes you say that the existing accounting attributes for octet/packet=
 counts are for IPv4 ?

Wouldn't the IP address contained in the IP session be sufficient to create=
 the context for the accounting message?


On 23-02-2010, at 06:31 , Maglione Roberta wrote:

> Hi All,
>     we have just posted a new draft about RADIUS attributes for IPv6 stat=
istics:
> http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
> Your comments are welcome.
>=20
> Thanks,
> Regards,
> Roberta
>=20
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Tuesday, February 23, 2010 11:43 AM
> To: Maglione Roberta
> Cc: suresh.krishnan@ericsson.com; alan.kavanagh@ericsson.com; varga.balaz=
s@telekom.hu
> Subject: New Version Notification for draft-maglione-radext-ipv6-acct-ext=
ensions-00
>=20
>=20
> A new version of I-D, draft-maglione-radext-ipv6-acct-extensions-00.txt h=
as been successfuly submitted by Roberta Maglione and posted to the IETF re=
pository.
>=20
> Filename:        draft-maglione-radext-ipv6-acct-extensions
> Revision:        00
> Title:           RADIUS Accounting Extensions for IPv6
> Creation_date:   2010-02-23
> WG ID:           Independent Submission
> Number_of_pages: 10
>=20
> Abstract:
> This document describes additional RADIUS attributes to be used for
> collecting IPv6 statistics in RADIUS Accounting messages.
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20
>=20
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle p=
ersone indicate. La diffusione, copia o qualsiasi altra azione derivante da=
lla conoscenza di queste informazioni sono rigorosamente vietate. Qualora a=
bbiate ricevuto questo documento per errore siete cortesemente pregati di d=
arne immediata comunicazione al mittente e di provvedere alla sua distruzio=
ne, Grazie.
>=20
> This e-mail and any attachments is confidential and may contain privilege=
d information intended for the addressee(s) only. Dissemination, copying, p=
rinting or use by anybody else is unauthorised. If you are not the intended=
 recipient, please delete this message and any attachments and advise the s=
ender by return e-mail, Thanks.
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 23 Feb 2010 14:32:46 +0000
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
CC: Alan Kavanagh <alan.kavanagh@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, =?iso-8859-1?Q?Varga_Bal=E1zs?= <varga.balazs@telekom.hu>
Date: Tue, 23 Feb 2010 15:31:49 +0100
Subject: FW: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Topic: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00 
Thread-Index: Acq0dWLIIt4q+HckQ/ehIwN9aQMNRQAEzSmw
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7C35162C@GRFMBX704BA020.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: en-US
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi All,
     we have just posted a new draft about RADIUS attributes for IPv6 stati=
stics:
http://tools.ietf.org/html/draft-maglione-radext-ipv6-acct-extensions-00
Your comments are welcome.

Thanks,
Regards,
Roberta

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
Sent: Tuesday, February 23, 2010 11:43 AM
To: Maglione Roberta
Cc: suresh.krishnan@ericsson.com; alan.kavanagh@ericsson.com; varga.balazs@=
telekom.hu
Subject: New Version Notification for draft-maglione-radext-ipv6-acct-exten=
sions-00


A new version of I-D, draft-maglione-radext-ipv6-acct-extensions-00.txt has=
 been successfuly submitted by Roberta Maglione and posted to the IETF repo=
sitory.

Filename:        draft-maglione-radext-ipv6-acct-extensions
Revision:        00
Title:           RADIUS Accounting Extensions for IPv6
Creation_date:   2010-02-23
WG ID:           Independent Submission
Number_of_pages: 10

Abstract:
This document describes additional RADIUS attributes to be used for
collecting IPv6 statistics in RADIUS Accounting messages.



The IETF Secretariat.



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, 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-data0@psg.com
Delivery-date: Mon, 22 Feb 2010 20:12:59 +0000
Message-ID: <BLU137-DS7B020CCE718F044DE2A1793430@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: FW: Review of Radius Guidelines 11
Date: Mon, 22 Feb 2010 12:12:04 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQHZqC/5zypIw/6vMRSzbnyC1HnsVpG0pjBQ
Content-Language: en-us

-----Original Message-----
From: Avi Lior [mailto:avi@bridgewatersystems.com] 
Sent: Monday, February 22, 2010 11:32 AM
To: Bernard Aboba; Alan DeKok DeKok
Subject: Review of Radius Guidelines 11

Review of RADIUS Design Guidelines - this is the version that Alan sent to
me earlier.  The one uploaded may have some slight corrections

-------

I am a little confused about the purpose of section 2 RADIUS Data Model and
the purpose of Section 3 Data Model Issues.

Is the intent of section 2 to describe the data model then it should just do
that and move discussions of issues to section 3.

---------------
Section 2:
Please define Standard Space
Please define complex attributes. (you do so much later) or give a reference
to where they are defined.

"The format of this space is defined by individual vendors but the same TLV
encoding used by the standard space..."

Change to:

"The format of the payload of these attributes is defined by individual
vendors but the same TLV encoding...."
-----------------
2.1.1

   "However in order
   to prevent future ambiguities, it is recommended that future RADIUS
   attribute specifications explicitly define newly created data types
   at the beginning of the document, and indicate clearly the data type
   to be used for each attribute."

Do we care about the structure of the document.  I think the issue is that
specification should define newly created data types and indicate clearly
the data type to be used for each attribute.  

Second issue: It seems to me that we are okay with folks creating new data
types in standard space.  I think creation of new data types should be
discouraged right?
-----------------------

" It is worth noting that since RADIUS only supports unsigned integers
   of 32 bits, attributes using signed integer data types or unsigned
   integer types of other sizes will require code changes, and SHOULD be
   avoided."

Why are we talking specifically signed integers?  This is already covered in
the discussion of creating new types.

But since we do bring this up - I suppose that we are talking about this
because this is a common issue.  After all there is no way to represent
negative numbers in RADIUS (or signed integers).  This creates a problem in
general and specific when translating Diameter signed integers to RADIUS.  I
think this document should either remove this paragraph or offer
guidance/solution.
--------------
2.1.2

" For these reasons, the tagging scheme described in RFC 2868 is NOT
   RECOMMENDED for use as a generic grouping mechanism."

What do you mean by generic grouping mechanism?

What about guidance on how to achieve this?

--------------------
Section 2.1.3 Complex Types

Can we not re-write this section to be a little more concise and to the
point? 

Complex types and New Types require code changes in the client and/or the
server.
Code changes creates security risks see security consideration section.

Thus one should avoid creating new types or using complex types.

--------

"However, some standard attributes do not follow this format."
Please give an example of an attribute.

 "Attributes that use sub-fields instead of using a basic data type are
   known as "complex attributes". "

What are sub-fields.
Is an attribute that codefies a bit map a complex attribute?  I think yes.
This is probably the most common complex type that people use.  What
guidance do we offer to designers that need a bit-field?  Each bit is an
attribute?  

---------

"   * it is easier for the user to enter the data as well-known
        types, rather than complex structures;"
This bullet should be removed.  Following good engineer practices of
seperation of concerns and in this case seperation of presentation and the
model (MVC).  We dont want to encourage users to edit raw data as codefied
by the RADIUS protocol.  For example, we dont want user to enter a IPv4
address as a 32bit value or an Address type. But rather as an IP address in
dot notation.

--------
      * it enables additional error checking by leveraging the
        parsing and validation routines for well-known types;

      * it simplifies implementations by eliminating special-case
        attribute-specific parsing.

These two bullets are the same and should be combined.

--------------

One of the fundamental goals of the RADIUS protocol design was to
   allow RADIUS servers to be configured to support new attributes
   without requiring server code changes.  RADIUS server implementations
   typically provide support for basic data types, and define attributes
   in a data dictionary.  This architecture enables a new attribute to
   be supported by the addition of a dictionary entry, without requiring
   other RADIUS server code changes.

This is totally misleading.  We should explain when this is true -- it is
mostly not true today since RADIUS is increasingly supporting dynamic
policies and thus always requires code change to handle the introduction of
any new attribute whether it is an attribute of an existing type or not.

As well the above appears under the complex attribute section 2.1.3 - It is
true also if we were to introduce a new attribute type.
----------

" On the RADIUS client, code changes are typically required in order to
   implement a new attribute. "

A new attribute or a new attribute type or a complex attribute? Which one?
----

  "The RADIUS client typically has to
   compose the attribute dynamically when sending.  When receiving, a
  RADIUS client needs to be able to parse the attribute and carry out
   the requested service.  As a result, a detailed understanding of the
   new attribute is required on clients, and data dictionaries are less
   useful on clients than on servers.

Many of the reasons given here are also true for servers. 

----------

  "The RADIUS server can be configured to send a new static attribute by
   entering its type and data format in the RADIUS server dictionary,
   and then filling in the value within a policy based on the attribute
   name, data type and type-specific value."

The above is only true if the new static attribute is an existing type.
--------

"Code changes can also be required in policy management and in the
   RADIUS server's receive path.  These changes are due to limitations
   in RADIUS server policy languages, which typically only provide for
   limited operations (such as comparisons or arithmetic operations) on
   the existing data types.  Many existing RADIUS policy languages
   typically are not capable of parsing sub-elements, or providing
   sophisticated matching functionality."

What is a RADIUS server policy language?  
RADIUS policy languages are not part of the IETF - the IETF did not conduct
a survey and thus cannot make statements such as these.
Most policy languages i know about contain REgExp that is sophisticated and
can extract any information out of any type. Typicially these have been
first added to be able to parse the RADIUS username.
Remove this paragraph.

------------------
The paragraph starting with "Given these limitations..." seems out of place
since it talks about new types, not complex types....
Then it talks about attribute specific parsing which is not really related
to new types.

Then it talks about the intoduction of new complex data types within RADIUS
attribute specification be avoided.

So now we have a new thing called a "new complex data type".    Dont we mean
new types and complex data types?


Also this paragraph repeats text made earilier  by the bullet points.
-----
"The only other exception to the recommendation against complex types
   is for types that can be treated as opaque data by the RADIUS server."

The assertions that the document is making in this sentence is wrong and we
should remove this statement.  We have seen examples like in RADIUS digest
where we flattened out an attribute to create more then a dozen attributes.
There are other cases as well.  Remove this paragraph.

------

 " If the RADIUS Server simply passes the contents of an attribute to
   some non-RADIUS portion of the network, then the data is opaque, and
   SHOULD be defined to be of type String.  A concrete way of judging
   this requirement is whether or not the attribute definition in the
   RADIUS document contains delineated fields for sub-parts of the data.
   If those fields need to be delineated in RADIUS, then the data is not
   opaque, and it SHOULD be separated into individual RADIUS attributes."


The document is attempting to define a RADIUS Server architecture.  We
should do this properly.  An equally valid architecture is the Diameter one
where the Server is composed of a lower layer defined by RFC 3588 and an
application layer.  We should state that as well.

Here the document gives an impression that the only "application" layer
possible is some foreign entity not part of the RADIUS server - that is just
not true today.

---------
2.1.4
" RADIUS specifications define how an existing service or protocol can
   be provisioned using RADIUS.  Therefore, it is expected that a RADIUS
   attribute specification will reference documents defining the
   protocol or service to be provisioned.  Within the IETF, a RADIUS
   attribute specification SHOULD NOT be used to define the protocol or
   service being provisioned.  New services using RADIUS for
   provisioning SHOULD be defined elsewhere and referenced in the RADIUS
   specification."


I am confused by what we are trying to say in this section.

-------

"New attributes, or new values of existing attributes, SHOULD NOT be
   used to define new RADIUS commands.  RADIUS attributes are intended
   to:"

Shouldn't this be a different section.

----------
2.2

" However, instead of doing this, vendors have defined the following
   non-standard VSA formats:"

The standard allows Vendors to define their VSA as they wish.  How can you
say "non-standard VSA formats"?

Howecer instead of following the recommendation vendors have defiend the
following:

------------

  "All VSA schemes that do not follow the [RFC2865] recommendations are
   NOT RECOMMENDED.  These non-standard formats will typically not be
   implementable without RADIUS server code changes.  This includes all
   the above formats, as well as Vendor types of more than 8 bits,
   vendor lengths of less than 8 bits, vendor lengths of more than 8
   bits and Vendor-Specific contents that are not in Type-Length-Value
   format."

Its up to the vendors or SDO to decide and the specification allows for
that.  RFC2865 makes a recommendation and we should just leave it at that.
You can state the problems that this may create but I think the document is
out of bounds when it states that it is not recommended.  2865 makes a
recommendation and that is enough.

---------------

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

What do you mean by on-the-wire format?  
     
---------
Section 3 is not only about data model issues.

We need a better name.
-----------

3.3

Why are we repeating the recommendations fo 5080.  Just remind people that
they need to read it.

---------

Section 5

"Where new RADIUS attributes encapsulate complex data types, or transport
opaque data, the security considerations discussed in Sectiont 2.1.4 SHOULD
be addressed"

The contents of 2.1.4 was moved to the security section
-----
5.1

The title should be Complex Types and New Data types no?

The text in this section should be fixed as well.  Sometimes it refers to
one where the other is also applicable.

-------

   "Any system consuming opaque data that originates from a RADIUS system
   SHOULD be properly isolated from that RADIUS system, and SHOULD run
   with minimal privileges.  Any potential vulnerabilities in the non-
   RADIUS system will then have minimal impact on the security of the
   system as a whole."

fear mongering a bit here and not true???  I can inject code in the opaque
data which could cause the system to run at higher privelages. Can we make
more concrete recommendations such as use care to validate the opaque data
for example to ensure no buffer overruns etc etc....It is pretty standard
practice to validate data coming from potentially untrusted sources or that
can be compromized along the way.
 


Appendix A

A.1

Simple Data vs Radius Data types.  They are the same no?  We need to use the
term consistantly throughout the document.

A.1.2

*Complex data types...which the RADIUS servers are expected to parse..."

I think you need to explain the model here.  This is a common theme
throughout the document.  What is a RADIUS server?

A.3





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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 20 Feb 2010 07:33:52 +0000
Message-ID: <BLU137-DS7BB6FA4E8DDFCA13B99DD93450@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Virtual interim presenters:  Request for Slides
Date: Fri, 19 Feb 2010 23:34:05 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0134_01CAB1BC.0A456B10"
Thread-Index: Acqx/xTIJb9wP7HMQgGf/lwMnO1XVA==
Content-Language: en-us

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

If you're on the agenda for the RADEXT Virtual Interim meeting on February
23, 2010, please send your slides to myself or Dave no later than Tuesday,
February 22, so that we can get them up on the archive in time. 

 

Thanks in advance!


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

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>If you&#8217;re on the agenda for the RADEXT =
Virtual Interim
meeting on February 23, 2010, please send your slides to myself or Dave =
no
later than Tuesday, February 22, so that we can get them up on the =
archive in
time. <o:p></o:p></p>

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

<p class=3DMsoNormal>Thanks in advance!<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0134_01CAB1BC.0A456B10--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 20 Feb 2010 07:31:38 +0000
Message-ID: <BLU137-DS54DF70EC3EAA60F5015EE93450@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take Four
Date: Fri, 19 Feb 2010 23:31:48 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012A_01CAB1BB.B55BBF50"
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAB15MsgAAA2mBQAABiObA=
Content-Language: en-us

------=_NextPart_000_012A_01CAB1BB.B55BBF50
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Jabber room:  radext at jabber.ietf.org (please join)

Presentations:  <http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/>
http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/

WebEx conference parameters:
<http://ops.ietf.org/lists/radiusext/2010/msg00169.html>
http://ops.ietf.org/lists/radiusext/2010/msg00169.html

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (50 minutes)

11:15 AM - 12:05 PM PT Design Guidelines, Alan DeKok (50 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

Issue 325: Review
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325>  (Submitted
by Joe Salowey) 

Issue 327: Applicability
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327>  (Submitted
by Avi Lior)    Proposed
<http://ops.ietf.org/lists/radiusext/2010/msg00175.html>  Resolution


Pre-Work Item Review (10 minutes)

12:05 PM PT - 12:15 PT RADIUS Attributes for IPv6 Networks, W. Dec (10
minutes)

http://tools.ietf.org/html/
<http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access>
draft-lourdelet-radext-ipv6-access

Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


------=_NextPart_000_012A_01CAB1BB.B55BBF50
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time</span><span =
style=3D'font-size:10.0pt;font-family:
"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>Jabber room:&nbsp; =
radext at
jabber.ietf.org (please join)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>Presentations: <a
href=3D"http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><span
style=3D'color:black'>http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/</=
span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'>WebEx conference =
parameters: </span><span
style=3D'color:black'><a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00169.html"><span
style=3D'color:black'>http://ops.ietf.org/lists/radiusext/2010/msg00169.h=
tml</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a></span><=
span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines =
(</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>5</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'=
>0 minutes)<br>
<br>
11:15 AM &#8211; 12:</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>0</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>5 PM PT Design Guidelines, Alan DeKok (</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>5</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'=
>0
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 325: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
325">Review</a>
(Submitted by Joe Salowey) <span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 327: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
327">Applicability</a>
(Submitted by Avi Lior)<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> &nbsp;&nbsp;&nbsp;<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00175.html">Proposed
Resolution</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Pre-Work Item Review (</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>1</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>0 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>12:05 PM PT &#8211; =
12:15 PT RADIUS
Attributes for IPv6 Networks, W. Dec (10 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/<span
style=3D'font-family:"Arial","sans-serif"'>draft-lourdelet-radext-ipv6-ac=
cess</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_012A_01CAB1BB.B55BBF50--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 20 Feb 2010 07:05:58 +0000
Message-ID: <BLU137-DS459F4850D1779DFC7D27A93450@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take Three
Date: Fri, 19 Feb 2010 23:05:37 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0113_01CAB1B8.0C9A2D50"
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAB15MsgA==
Content-Language: en-us

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

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (50 minutes)

11:15 AM - 12:05 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

Issue 325: Review
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325>  (Submitted
by Joe Salowey) 

Issue 327: Applicability
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327>  (Submitted
by Avi Lior)    Proposed
<http://ops.ietf.org/lists/radiusext/2010/msg00175.html>  Resolution


Pre-Work Item Review (10 minutes)

12:05 PM PT - 12:15 PT RADIUS Attributes for IPv6 Networks, W. Dec (10
minutes)

http://tools.ietf.org/html/
<http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access>
draft-lourdelet-radext-ipv6-access

Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


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

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time<br>
<br>
Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a></span><=
span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines =
(</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>5</span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'=
>0
minutes)<br>
<br>
11:15 AM &#8211; 12:</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>0</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>5 PM PT Design Guidelines, Alan DeKok (60 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 325: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
325">Review</a>
(Submitted by Joe Salowey) <span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Issue 327: </span><a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
327">Applicability</a>
(Submitted by Avi Lior)<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> &nbsp;&nbsp;&nbsp;<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00175.html">Proposed
Resolution</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Pre-Work Item Review (</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>1</span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>0 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>12:05 PM PT &#8211; =
12:15 PT RADIUS
Attributes for IPv6 Networks, W. Dec (10 minutes)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><a
href=3D"http://tools.ietf.org/html/draft-lourdelet-radext-ipv6-access">ht=
tp://tools.ietf.org/html/<span
style=3D'font-family:"Arial","sans-serif"'>draft-lourdelet-radext-ipv6-ac=
cess</span></a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_0113_01CAB1B8.0C9A2D50--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 19 Feb 2010 13:02:09 +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-11.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100219130002.4170428C1F7@core3.amsl.com>
Date: Fri, 19 Feb 2010 05:00:02 -0800 (PST)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.


	Title           : RADIUS Design Guidelines
	Author(s)       : G. Weber, A. DeKok
	Filename        : draft-ietf-radext-design-11.txt
	Pages           : 38
	Date            : 2010-02-19

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

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

--NextPart--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 19 Feb 2010 12:58:35 +0000
Message-ID: <4B7E8AC1.80702@deployingradius.com>
Date: Fri, 19 Feb 2010 13:57:37 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: REQUIRED READING: RADEXT Virtual Interim Design Guidelines Discussion
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Bernard Aboba wrote:
> [BA]  I have collected Avi Lior’s review of the -10 text (and suggested changes) within Issue 327: Applicability <http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327> .  Joe Salowey’s review is  
> provided in Issue 325: Review <http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325> .  As noted in a previous message summarizing the results of the “Last Look” (http://ops.ietf.org/lists/radiusext/2010/msg00150.html) there appears to be WG consensus to make changes to the document to address the concerns that have been raised.

  I've submitted a -11 version of the document.  The only change from
the previous -11 version on my web site is a paragraph addressing one of
Joe's comments.  The text was proposed on the list, and accepted.

  A full review of all issues is below.  At this point, I think that all
open issues have been addressed.



300: replacement text

In order to characterize current attribute usage, both the basic and
complex data types defined in the existing RADIUS RFCs are reviewed.

301: replacement text

Does the data fit within the basic data types described in Section
2.1.1, as outlined below?  If so, it SHOULD be encapsulated in a
[RFC2865] format RADIUS attribute, or in a [RFC2865] format RADIUS VSA
that uses one of the existing RADIUS data types.

302: deleted references to [EXTEN]

304: addressed in prior revisions

311: addressed in prior revisions

312: removed references to [EXTEN] in prior revisions

313: clarified in prior revisions

314: issue was closed

318: rejected.

319: addressed in prior revisions

320: addressed in prior revisions

325: addresed in -11

327: addressed in -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-data0@psg.com
Delivery-date: Fri, 19 Feb 2010 10:47:06 +0000
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D Action:draft-ietf-radext-tcp-transport-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100219104502.1FE9328C185@core3.amsl.com>
Date: Fri, 19 Feb 2010 02:45:02 -0800 (PST)

--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 Over TCP
	Author(s)       : A. DeKok
	Filename        : draft-ietf-radext-tcp-transport-05.txt
	Pages           : 18
	Date            : 2010-02-19

The Remote Authentication Dial In User Server (RADIUS) Protocol has
traditionally used the User Datagram Protocol (UDP) as its underlying
transport layer.  This document defines RADIUS over the Transmission
Control Protocol (TCP), in order to address handling issues related
to RADIUS over TLS [RTLS].  It is not intended to define TCP as a
transport protocol for RADIUS in the absence of TLS.

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

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

--NextPart--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 19 Feb 2010 10:44:09 +0000
Message-ID: <4B7E6B68.5070006@deployingradius.com>
Date: Fri, 19 Feb 2010 11:43:52 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-tcp-transport (Part III)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> I am wondering whether this document should take a position on the
> recommendations described in [RFC3539] Section 3, particularly:
> 
> 3.2.  Use of Nagle Algorithm
> 3.3.  Multiple Connections
> 3.4.2 Primary/Secondary failover
> 3.4.3 Connection Load Balancing
> 3.6 Invalidation of Transport Parameter Estimates
> 3.7 Inability to Use Fast Retransmit
> 3.8 Head of Line Blocking
> 3.9 Congestion Avoidance
> 3.10 Premature Failover

  There's already a "catch-all" sentence in the doc:

The guidelines defined in [RFC3539] for implementing a AAA protocol
over reliable transport are applicable to RADIUS over TLS/TCP.


  I think that should be fine.  I don't want to reproduce 3539 here, or
do a section-by-section review, saying "this applies, too".

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 19 Feb 2010 10:40:29 +0000
Message-ID: <4B7E6A83.9000600@deployingradius.com>
Date: Fri, 19 Feb 2010 11:40:03 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-tcp-transport (Part II)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Bernard Aboba wrote:
> [BA] How about this?

  OK.

>    The changes to RADIUS implementations required to implement this
>    specification are largely limited to the portions that send and
>    receive packets on the network.
>  
> 
> [BA] Is this sentence necessary?  What portions of a RADIUS
> implementation **don’t** relate
> To sending and receiving packets?   I’d recommend that it be deleted.

  Implementations have re-tranmission timers for UDP sockets.  These
timers need to be disabled for TCP sockets.

  The timers are usually "internal" to an implementation, and don't
directly involve recv() or send() calls.

> [BA] You might say “Since these ports are unused by existing RADIUS
> implementations, 
> the assigned values SHOULD be used as the default ports for RADIUS over
> TCP.”

  OK.

> I would merge section 2.4 into this section so that one section can
> cover ports 
> for both RADIUS over TCP and RADIUS over TLS.

  OK.

> You might revise this section to make it clear that the advice for use
> of MIBs 
> with RADIUS over TCP also applies to RADIUS over TLS.

  I thought I'd leave that to the RTLS document.

> [BA] Suggest this section be renamed “Liveness Detection”.

  How about "detecting live servers" ?

>    Implementations of this specification SHOULD treat the "silently 
>    discard" texts referenced above as "silently discard and close the
>    connection." 
> 
> [BA] What is the alternative to this behavior?  Could this be a MUST?

  There are some cases where "silently discard" is OK for TCP.  I don't
recall right now, but I do remember auditing the previous documents.

  The text following that sentence outlines the situations where closing
the connection is a MUST.

>    TCP connections MAY be closed if any of the circumstances outlined 
>    below are seen.  Alternatively, the TCP connection MAY remain open if
>    any of the following circumstances are seen, but the invalid packet
>    MUST BE silently discarded.
>
> [BA] Not sure how you can do this in practice.  Are you assuming that the 
> Length field remains valid?

  Yes.  The previous MUST requirement are applied first.

  How about the clarifications to the text:

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

> Section 2.6.6
>
> Given the discussion in Section 1.1, I’m wondering if this section (or
> some other section) 
> shouldn’t make a recommendation on the maximum RADIUS message size
> applicable to use with
> RADIUS/EAP.  It seems to me that using a larger RADIUS message size
> would make a lot of sense. 

  Only when the transport protocol to the supplicant allows large EAP
packets.

  If the NAS sends a Framed-MTU, most RADIUS servers will honor it.
This works today when large packets are allowed.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Fri, 19 Feb 2010 10:13:46 +0000
Message-ID: <4B7E642C.2080705@deployingradius.com>
Date: Fri, 19 Feb 2010 11:13:00 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: Review of draft-ietf-radext-tcp-transport (Part I)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Bernard Aboba wrote:
> [BA] In particular, filters routers and firewalls often drop UDP
> fragments, since otherwise they would need to reassemble them in order
> to apply the filter rules.
> 
> However, this is not a “transport” issue, so much as a
> forwarding/filtering issue.  Instead of “Transport” you might say
> “handling”.

  OK.

> [BA] Note double periods in first sentence, and no period in the last
> sentence.  As I read the document, it is really only suggesting a
> different set of tradeoffs for inter-server proxying.  So you might say
> “For use-cases such as inter-server proxying, [RTLS] suggests an
> alternative transport and security model -- RADIUS over TLS.  This
> document describes the transport implications of running RADIUS over
> TLS/TCP.”

  OK.

> [BA]  Suggested rewrite:
> ...the larger congestion
>    window supported by TCP may allow multiple TCP segments to
>    be sent within a single window.  As a result, RADIUS/EAP
>    traffic required for an EAP-TLS authentication with 8KB
>    certificate chains may be reduced to 7 round-trips or less,
>    resulting in substantially reduced authentication times.

  Is that really true?  The common limitation on EAP is the 1022 byte
maximum overhead for EAPoL.  Allowing 4K RADIUS packet sizes helps only
when doing EAP *without* EAPoL.  That's a pretty rare occurance.

...  In addition, most TCP
>    implementations discover Path MTU better than RADIUS application
>    implementations, resulting in significantly fewer fragmented packets.

  This is duplicate text.

  I've done some word-smithing, and updated the doc.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 18 Feb 2010 19:30:19 +0000
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAB0D0.B1CE620F"
Subject: RE: RADEXT Virtual Interim Agenda, Take Two
Date: Thu, 18 Feb 2010 20:29:26 +0100
Message-ID: <A16B9A4922C4A544A94565E870362B5001457C15@XMB-AMS-111.cisco.com>
Thread-Topic: RADEXT Virtual Interim Agenda, Take Two
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAAG6JCIAFxmguQ
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>
Cc: <radiusext@ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAB0D0.B1CE620F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Resending, as I have not seen a response.


________________________________

	From: Wojciech Dec (wdec)=20
	Sent: 11 February 2010 12:05
	To: 'Bernard Aboba'
	Subject: RE: RADEXT Virtual Interim Agenda, Take Two
=09
=09
	Hi Bernard,
	=20
	could you add a 10min slot for
draft-lourdelet-radext-ipv6-access to the agenda?
	=20
	Thanks,
	Woj.


________________________________

		From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
		Sent: 10 February 2010 22:54
		To: radiusext@ops.ietf.org
		Subject: RADEXT Virtual Interim Agenda, Take Two
	=09
	=09

		RADEXT Virtual Interim Meeting
		Tuesday, February 23, 2010
		10 AM - 12:30 PM Pacific Time
	=09
		Agenda
	=09
		10 AM - 10:15 AM PT: Preliminaries=20
	=09
		     Conference issues/debugging
		     Attendance
		     Note takers
		     Agenda bash
	=09
		RADSEC (60 minutes)
	=09
		10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15
minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-status-server

		10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok
(15 minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>=20

		10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15
minutes)
		http://tools.ietf.org/html/draft-ietf-radext-radsec

	=09
		11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan
Winter (15 minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

		Design Guidelines (60 minutes)
	=09
		11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60
minutes)
=09
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

	=09
		Wrap-up (15 minutes)
	=09
		12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:
WG Chairs & ADs (15 minutes)


------_=_NextPart_001_01CAB0D0.B1CE620F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5880" name=3DGENERATOR>
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D952272719-18022010>Resending, as I have not seen a=20
response.</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 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> Wojciech Dec (wdec) =
<BR><B>Sent:</B> 11=20
  February 2010 12:05<BR><B>To:</B> 'Bernard Aboba'<BR><B>Subject:</B> =
RE:=20
  RADEXT Virtual Interim Agenda, Take Two<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2>Hi Bernard,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial><FONT=20
  size=3D2>could you add a 10min slot =
for&nbsp;draft-lourdelet-radext-ipv6-access=20
  to the agenda<SPAN=20
class=3D983360411-11022010>?</SPAN></FONT></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2>Thanks,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D113330311-11022010><FONT =
face=3DArial=20
  size=3D2>Woj.</FONT></SPAN></DIV></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 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> =
owner-radiusext@ops.ietf.org=20
    [mailto:owner-radiusext@ops.ietf.org] <B>On Behalf Of </B>Bernard=20
    Aboba<BR><B>Sent:</B> 10 February 2010 22:54<BR><B>To:</B>=20
    radiusext@ops.ietf.org<BR><B>Subject:</B> RADEXT Virtual Interim =
Agenda,=20
    Take Two<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">RADEXT=20
    Virtual Interim Meeting<BR>Tuesday, February 23, 2010<BR>10 AM - =
12:30 PM=20
    Pacific Time<BR><BR>Agenda<BR><BR>10 AM - 10:15 AM PT: Preliminaries =

    <BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; Conference=20
    issues/debugging<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
    Attendance<BR>&nbsp;&nbsp;&nbsp;&nbsp; Note=20
    takers<BR>&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<BR><BR>RADSEC (60=20
    minutes)<BR><BR>10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, =
Alan DeKok (15=20
    minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</A></SPAN><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:30=20
    AM PT &#8211; 10:45 AM PT RADIUS over TCP, Alan DeKok (15 =
minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><SPAN=
=20
    style=3D"COLOR: =
black">http://tools.ietf.org/html/draft-ietf-radext-tcp-transport</SPAN><=
/A></SPAN><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:45=20
    AM - 11:00 AM PT&nbsp; RADSEC, Stefan Winter (15 minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</A><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>11:00=20
    AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</A><o:p></o=
:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Design=20
    Guidelines (60 minutes)<BR><BR>11:15 AM &#8211; 12:15 PM PT Design =
Guidelines,=20
    Alan DeKok (60 minutes)<BR><A=20
    =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</A><o:p></o=
:p></SPAN></P>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>Wrap-up=20
    (15 minutes)<BR><BR>12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; =
Discussion and=20
    Next Steps:&nbsp; WG Chairs &amp; ADs (15=20
    =
minutes)<o:p></o:p></SPAN></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HT=
ML>

------_=_NextPart_001_01CAB0D0.B1CE620F--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 16 Feb 2010 16:32:16 +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-06.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100216163002.11B5E3A7B72@core3.amsl.com>
Date: Tue, 16 Feb 2010 08:30:02 -0800 (PST)

--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-06.txt
	Pages           : 24
	Date            : 2010-02-16

This document describes a deployed extension to the Remote
Authentication Dial In User Service (RADIUS) protocol, enabling
clients to query the status of a RADIUS server.  This extension
utilizes the Status-Server (12) Code, which was reserved for
experimental use in RFC 2865.

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

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

--NextPart--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 16 Feb 2010 15:00:15 +0000
Message-ID: <4B7AB2E8.4070108@deployingradius.com>
Date: Tue, 16 Feb 2010 15:59:52 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (part III)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Section 4.3
> 
> On reading this section I am unsure about whether the discussion relates
> to failover between proxies or servers.
> Suggested rewrite:
> 
> 
>       4.3. Fail-over with Status-Server

  OK.  Looks good to me.

> Section 5
> 
> You might want to add a table entry for User-Name.

  OK, and User-Password, CHAP-Password, etc.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 16 Feb 2010 14:52:47 +0000
Message-ID: <4B7AB10C.5030800@deployingradius.com>
Date: Tue, 16 Feb 2010 15:51:56 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (Part II)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> Sections 2.1 and Section 2.2
> 
> Section 2 explains the unique properties of Status-Server and why a
> RADIUS client might want to use it.  RFC 2865 Section 2.6
> explains why "keepalives" are a bad idea.  Presumably this advice
> applies to both RADIUS Access-Request and Accounting-Request
> keepalives.  Given that, Sections 2.1 and 2.2 belabor the point.  I'd
> suggest that they be deleted.

  I think that they have some use.  There are a number of
implementations which "overload" Access-Requests for all kinds of
functionality.  Having an explanation as to why this is bad can help
guide implementors.

> Section 2.3
> 
> I would suggest deleting this section as well.

  OK.

> Section 2.3.1
> 
> My advice is to incorporate the material in this section into Section 2
> (To be retitled Overview).

  Done.

> Section 3
> 
>      Response Authenticator
> 
>          The value of the Authenticator field in Access-Accept, or
>          Accounting-Response packets is called the Response
>          Authenticator, and contains a one-way MD5 hash calculated over
>          a stream of octets consisting of: the RADIUS packet, beginning
>          with the Code field, including the Identifier, the Length, the
>          Request Authenticator field from the Status-Server packet, and
>          the response Attributes (if any), followed by the shared
>          secret.  That is, ResponseAuth =
>          MD5(Code+ID+Length+RequestAuth+Attributes+Secret) where +
>          denotes concatenation.
> 
> [BA] Why is this material here?  If you need it at all (I don't think so), you can just reference
> RFC 2865 and/or 2866. 

  Otherwise there will be confusion over how to calculate it.  The other
RFCs define how the Response Authenticator is calculated for response
packets.  It's not a *bad* idea to include similar text here.

>    Status-Server packets MAY include NAS-Identifier, and one of NAS-IP-
>    Address or NAS-IPv6-Address.  These attributes are not necessary for
>    the operation of Status-Server, but may be useful information to a
>    server that receives those packets.
> 
> [BA] You might say that the server MUST ignore other attributes. 

  OK.

>    Other attributes SHOULD NOT be included in a Status-Server packet.
>    User authentication credentials such as User-Password, CHAP-Password,
>    EAP-Message, etc. MUST NOT appear in a Status-Server packet sent to a
>    RADIUS authentication port.  User or NAS accounting attributes such
>    as Acct-Session-Id, Acct-Status-Type, Acct-Input-Octets, etc.  MUST
>    NOT appear in a Status-Server packet sent to a RADIUS accounting
>    port.
> 
> [BA] Also, presumably User-Name is not included (relevant to the point about realms made earlier). 

  Yes.  I'll add that in.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 16 Feb 2010 14:52:40 +0000
Message-ID: <4B7AB10D.4010005@deployingradius.com>
Date: Tue, 16 Feb 2010 15:51:57 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: Review of draft-ietf-radext-status-server-05 (part I)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> [BA] My suggestion is that this material be moved to Section 2, since it doesn't relate to the
> reasons why publication is recommended as an Informational RFC. 

  OK.

  I've added that text with minor rewording, and integrated Section
2.3.1 as per your other suggestion.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Mon, 15 Feb 2010 02:07:58 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: <radiusext@ops.ietf.org>
Subject: RE: Proposal for resolution of Issue 327:  Applicability
Date: Sun, 14 Feb 2010 21:07:03 -0500
Message-ID: <F5236010EB2D41B987DB4ED8D390A173@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AcqtviIKEF5ysBQ5Q/qwbbyUB5JzPAAJT5Gw

Bernard Aboba writes...

> The concerns expressed in Issue 327 appear to apply to
> Sections 1, 1.3, 3.1.2, 3.1.3 and 3.1.4.=20
>
> Here is a proposed resolution.=A0 Comments welcome.

I think this is helpful.



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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 14 Feb 2010 21:32:17 +0000
Message-ID: <BLU137-W377F2298AEEB878B736E09934B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Proposal for resolution of Issue 327:  Applicability
Date: Sun, 14 Feb 2010 13:31:10 -0800
MIME-Version: 1.0

--_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The concerns expressed in Issue 327 appear to apply to Sections 1=2C 1.3=2C=
 3.1.2=2C 3.1.3 and 3.1.4.=20

Here is a proposed resolution.  Comments welcome.=20
















Section 1

=20

   This document provides guidelines for the design of
RADIUS attributes

   both within the IETF as well as within other SDOs.  By
articulating

   RADIUS design guidelines=2C it is hoped that this document
will

   encourage the development and publication of high quality
RADIUS

   attribute specifications.

=20

   However=2C the advice in this document will not be helpful
unless it is

   put to use.  As with "Guidelines for Authors and
Reviewers of MIB

   Documents" [RFC4181]=2C it is expected that this document
will be used

   by authors to check their document against the guidelines
prior to

   requesting review (such as an "Expert Review"
described in

   [RFC3575]).  Similarly=2C it is expected that this document
will used

   by reviewers (such as WG participants or the AAA Doctors
[DOCTORS])=2C

   resulting in an improvement in the consistency of
reviews.

=20

   In order to meet these objectives=2C this document needs to
cover not

   only the science of attribute design=2C but also the art.=20
Therefore=2C

   in addition to covering the most frequently encountered
issues=2C this

   document attempts to provide some of the considerations
motivating

   the guidelines.

=20

   In order to characterize current attribute usage=2C both
the basic and

   complex data types defined in the existing RADIUS RFCs
are reviewed.

=20

[BA] Proposed
change is to replace Section 1 with the following:


=20

   "This document provides guidelines for the design of
RADIUS attributes

   used to encode service-provisioning or authentication
data=2C=20

   based on the data model and attribute formats defined in
RFC 2865 and

   subsequent RADIUS RFCs.   In order to characterize
current attribute=20

   usage=2C both the basic and complex data types defined in
the existing=20

   RADIUS RFCs are reviewed. Since the RADEXT WG is
currently considering

   extensions to the RADIUS data model and attribute
formats=2C=20

   future documents may extend the data model and guidelines
provided here.

=20

   In order to meet these objectives=2C this document needs to
cover not

   only the science of attribute design=2C but also the art.=20
Therefore=2C

   in addition to covering the most frequently encountered
issues=2C this

   document attempts to provide some of the considerations
motivating

   the guidelines.

=20

   RADIUS protocol changes=2C or specification of attributes=20

   (such as Service-Type) that can be used to=2C in effect=2C
provide=20

   new RADIUS commands require greater expertise and deeper
review=2C=20

   as do changes to the RADIUS operational model as
discussed in Section=20

   3.3.  As a result=2C such changes are outside the scope of
this

   document and MUST NOT be undertaken outside the IETF.=20
Registration policies

   for RADIUS parameters are discussed in [RFC3575] Section
2.1."=20

=20

1.3.  Applicability

=20

   As RADIUS has become more widely accepted as a management
protocol=2C

   its usage has become more prevalent=2C both within the IETF
as well as

   within other SDOs.  Given the expanded utilization of
RADIUS=2C it has

   become apparent that requiring SDOs to accomplish all
their RADIUS

   work within the IETF is inherently inefficient and
unscalable.  By

   articulating guidelines for RADIUS attribute design=2C this
document

   enables SDOs out of the IETF to design their own RADIUS
attributes

   within the Vendor-Specific Attribute (VSA) space.

=20

   It is RECOMMENDED that SDOs follow the guidelines
articulated in this

   document.  Doing so will ensure the widest possible
applicability and

   interoperability of the specifications=2C while requiring
minimal

   changes to existing systems.  Specifications that do not
follow the

   guidelines articulated herein are NOT RECOMMENDED.=20
However=2C we

   recognize that there are some situations where SDOs or
vendors

   require the creation of specifications not following these

   guidelines.  We do not forbid these specifications=2C but
it is

   RECOMMENDED that they are created only if they have a
limited scope

   of applicability=2C and all attributes defined in those
specifications

   are VSAs=2C as discussed Appendix A.5=2C below.

=20

   It is RECOMMENDED that SDOs and vendors seek review of
RADIUS

   attribute specifications from the IETF.  However=2C when
specifications

   are SDO specific=2C re-use existing data types=2C and follow
these

   guidelines=2C they do not require IETF review.

=20

   In order to enable IETF review of such specifications=2C
the authors

   recommend that:

=20

      * SDOs make their RADIUS attribute specifications
publicly

      available=3B

=20

      * SDOs request review of RADIUS attribute
specifications by

      sending email to the AAA Doctors [DOCTORS] or
equivalent mailing

      list=3B

=20

      * IETF and SDO RADIUS attribute specifications are
reviewed

      according to the guidelines proposed in this document=3B

=20

      * Reviews of specifications are posted to the RADEXT
WG mailing

      list=2C the AAA Doctors mailing list [DOCTORS] or
another IETF

      mailing list suggested by the Operations &
Management Area

      Directors of the IETF.

=20

   These reviews can assist with creation of specifications
that meet

   the SDO requirements=2C and which are also compatible with
the

   traditional data model and uses of RADIUS.  While these
reviews

   require access to public specifications=2C the review
process does not

   require publication of an IETF RFC.

=20

   The advice in this document applies to attributes used to
encode

   service-provisioning or authentication data.  RADIUS
protocol

   changes=2C or specification of attributes (such as
Service-Type) that

   can be used to=2C in effect=2C provide new RADIUS commands
require

   greater expertise and deeper review=2C as do changes to the
RADIUS

   operational model as discussed below in Section 3.3.=20
Such changes

   MUST NOT be undertaken outside the IETF and when handled
within the

   IETF require "IETF Consensus" for adoption=2C as
noted in [RFC3575]

   Section 2.1.



=20

[BA] Proposed change is to replace Section 1.3 with the following:=20

=20

   "   As RADIUS has become more widely accepted as a
management protocol=2C

   its usage has become more prevalent=2C by vendors as well
as the IETF and

  other SDOs.  By articulating RADIUS design guidelines=2C it
is hoped that

   this document will encourage the development and
publication of=20

   high quality RADIUS attribute specifications.  As with
"Guidelines=20

   for Authors and Reviewers of MIB Documents"
[RFC4181]=2C it is=20

   expected that this document will be used by authors to
check their=20

   document against the guidelines prior to requesting
review=20

   (such as an "Expert Review" described in

   [RFC3575]).  Similarly=2C it is expected that this document
will used

   by reviewers (such as WG participants or the AAA Doctors
[DOCTORS])=2C

   resulting in an improvement in the consistency of
reviews.

=20

   The guidelines articulated in this document enable the
design

   of attributes with the widest possible interoperability=2C

   while requiring minimal changes to existing systems.

   As a result=2C they are suitable for application to
attributes=20

   designed for general usage.  It is RECOMMENDED=20

   that these guidelines be applied to review of documents=20

   requesting allocations within the IETF standard attribute


   space defined in [RFC2865].=20

=20

   These guidelines may also prove useful in the design of=20

   attributes within the Vendor-Specific Attribute (VSA)

   space.  As noted in RFC 2865 Section 5.26=2C RADIUS VSAs=20

   were created "to allow vendors to support their own
extended=20

   Attributes not suitable for general usage." =20

   Rather than requesting allocation of standard attributes

   for those uses=2C [RFC2865] Section 6.2 notes that
utilization

   of VSAs "should be encouraged instead of allocation
of global=20

   attribute types=2C for functions specific only to one
vendor's=20

   implementation of RADIUS=2C where no interoperability is
deemed useful."=20

=20

   However=2C experience has shown that attributes not
originally=20

   designed for general usage can subsequently garner
wide-spread=20

   deployment.  An example is the vendor-specific attributes


   defined in [RFC2548]=2C which have been widely implemented=20

   within IEEE 802.11 Access Points.=20

=20

   As a result=2C while SDOs and vendors MAY choose to create=20

   specifications not following these guidelines for use in

   scenarios within a limited scope of applicability=2C

   where general usage is possible=2C  adhering to the=20

   design guidelines is RECOMMENDED.  Discussion of

   vendor allocations is provided in Section 3.1.2=3B=20

   discussion of SDO allocations is provided in Section

   3.1.3.   SDOs and vendors desiring review of their=20

   specifications by the IETF are encouraged to follow=20

   the advice presented in Section 3.1.4."=20

=20

3.1.2.  Vendor Allocations

=20

   Vendor RADIUS Attribute specifications SHOULD allocate
attributes

   from the vendor space=2C rather than requesting an
allocation from the

   RADIUS standard attribute space.

=20

   As discussed in [RFC2865] Section 5.26=2C the vendor space
is intended

   for vendors to support their own Attributes not suitable
for general

   use.  However=2C it is RECOMMENDED that vendors follow the
guidelines

   outlined here=2C which are intended to enable maximum
interoperability

   with minimal changes to existing systems.

=20

   Following these guidelines means that RADIUS servers can
be updated

   to support the vendor's equipment by editing a RADIUS
dictionary.  If

   these guidelines are not followed=2C then the vendor's
equipment can

   only be supported via code changes in RADIUS server
implementations.

   Such code changes add complexity and delay to
implementations.

=20

[BA] Proposed change is to replace Section 3.1.2 with the following:


=20

"  As noted in [RFC3575] Section 2.1=2C vendors are
encouraged

   to utilize VSAs to define functions "specific only
to one vendor's

   implementation of RADIUS=2C where no interoperability is
deemed useful.

   For functions specific only to one vendor's
implementation of RADIUS=2C

   the use of that should be encouraged instead of the
allocation of

   global attribute types."

=20

   Nevertheless=2C following the guidelines outlined within
this document

   has several advantages=2C including maximum
interoperability with

   minimal changes to existing systems.  Following these
guidelines=20

   means that RADIUS servers can be updated to support the
vendor's=20

   equipment by editing a RADIUS dictionary.  If these
guidelines are=20

   not followed=2C then the vendor's equipment can only be
supported=20

   via code changes in RADIUS server implementations.

   Such code changes add complexity and delay to
implementations."

=20

3.1.3.  SDO Allocations

=20

   SDO RADIUS Attribute specifications SHOULD allocate
attributes from

   the vendor space=2C rather than requesting an allocation
from the

   RADIUS standard attribute space=2C for attributes matching
any of the

   following criteria:

=20

      * attributes relying on data types not defined within
RADIUS

=20

      * attributes intended primarily for use within an SDO

=20

      * attributes intended primarily for use within a group
of SDOs.

=20

   Any new RADIUS attributes or values intended for
interoperable use

   across a broad spectrum of the Internet Community SHOULD
follow the

   normal IETF process=2C and SHOULD result in allocations
from the RADIUS

   standard space.

=20

   The recommendation for SDOs to allocate attributes from a
vendor

   space rather than via the IETF process is a recognition
that SDOs may

   desire to assert change control over their own RADIUS
specifications.

   This change control can be obtained by requesting a PEC
from the

   Internet Assigned Number Authority (IANA)=2C for use as a
Vendor-Id

   within a Vendor-Specific attribute.  Further allocation
of attributes

   inside of the VSA space defined by that Vendor-Id is
subject solely

   to the discretion of the SDO.  Similarly=2C the use of data
types

   (complex or not) within that VSA space is solely under
the discretion

   of the SDO.  It is RECOMMENDED that SDOs follow the
guidelines

   outlined here=2C which are intended to enable maximum
interoperability

   with minimal changes to existing systems.

=20

   It should be understood that SDOs do not have to rehost
VSAs into the

   standards space solely for the purpose of obtaining IETF
review.

   Rehosting puts pressure on the standards space=2C and may
be harmful to

   interoperability=2C since it can create two ways to
provision the same

   service.  Rehosting may also require changes to the
RADIUS data model

   which will affect implementations that do not intend to
support the

   SDO specifications.

=20

[BA] Proposed change is to replace Section 3.1.3 with the following:


=20

"  Given the expanded utilization of RADIUS=2C it has

   become apparent that requiring SDOs to accomplish all
their RADIUS

   work within the IETF is inherently inefficient and
unscalable. =20

=20

  SDO RADIUS Attribute specifications SHOULD allocate
attributes from

   the vendor space=2C rather than requesting an allocation
from the

   RADIUS standard attribute space=2C for attributes matching
any of the

   following criteria:

=20

      * attributes relying on data types not defined within
RADIUS

=20

      * attributes intended primarily for use within an SDO

=20

      * attributes intended primarily for use within a group
of SDOs.

=20

   Allocation of new RADIUS attributes or values intended
for interoperable use

   across a broad spectrum of the Internet Community SHOULD
follow the

   allocation process defined in [RFC3575].=20

=20

   The recommendation for SDOs to allocate attributes from
the vendor

   space rather than via the IETF process recognizes the
need for SDOs

   to assert change control over their own RADIUS
specifications.

   SDOs desiring to define their VSAs are encouraged to=20

   request allocation of a Private Enterprise Code (PEC)
from the

   Internet Assigned Number Authority (IANA)=2C for use as a
Vendor-Id. =20

   The SDO can then allocate attributes within the VSA space
defined=20

   by that Vendor-Id=2C at their sole discretion.  Similarly=2C
the use of=20

   data types (complex or otherwise) within that VSA space
is solely

   under the discretion of the SDO."

=20

3.1.4.  Publication of specifications

=20

   SDOs are encouraged to seek early review of SSA
specifications by the

   IETF.  This review may be initiated by sending mail to
the AAA

   Doctors list [DOCTORS]=2C with the understanding that this
review is a

   voluntary-based service offered on best-effort basis.=20
Since the IETF

   is not a membership organization=2C in order to enable the
RADIUS SSA

   specification to be reviewed=2C it is RECOMMENDED that it
be made

   publicly available=3B this also encourages interoperability.=20
Where the

   RADIUS SSA specification is embedded within a larger
document which

   cannot be made public=2C the RADIUS attribute and value
definitions

   SHOULD be published instead as an Informational RFC=2C as
with

   [RFC4679].  This process SHOULD be followed instead of
requesting

   IANA allocations from within the standard RADIUS
attribute space.

=20

   Similarly=2C vendors are encouraged to make their
specifications

   publicly available=2C for maximum interoperability.=20
However=2C it is not

   necessary for them to request publication of their VSA
specifications

   as Informational RFCs by the IETF.

=20

   All other specifications=2C including new authentication=2C

   authorization=2C and/or security mechanisms SHOULD be
allocated via the

   standard RADIUS space=2C as noted in [RFC3575] Section 2.1.

=20

[BA] Proposed change is to replace Section 3.1.4 with the following:

=20

"  SDOs or vendors desiring review of their RADIUS
specifications=20

   by the IETF are  encouraged to seek review as early as
possible=2C=20

   so as to avoid potential delays.  Since reviews are
handled by volunteers=2C=20

   responses are provided on a best-effort basis=2C with no
service

   level guarantees.   In order to provide reviewers with
access to the

   specification=2C  SDOs and vendors are encouraged to make
them publicly available.

   Where the RADIUS specification is embedded within a
larger document which

   cannot be made public=2C the RADIUS attribute and value
definitions

   can be made available on a public web site or can be
published as=20

   an Informational RFC=2C as with [RFC4679].=20

=20

   Review can be requested by sending email to the AAA
Doctors [DOCTORS]

   or equivalent mailing list.  The IETF Operations &
Management

   Area Directors will then arrange for the review to be

   completed and posted to the AAA Doctors mailing list

   [DOCTORS]=2C RADEXT WG mailing list=2C or other IETF mailing

   list. =20

=20

   The review process requires neither allocation of
attributes=20

   within the IETF standard attribute space nor publication
of an=20

   IETF RFC.  Requiring SDOs or vendors to rehost VSAs into
the IETF standards=20

   attribute space solely for the purpose of obtaining
review

   would put pressure on the standards space=2C and may be
harmful to

   interoperability=2C since it can create two ways to
provision the same

   service.  Rehosting may also require changes to the
RADIUS data model

   which will affect implementations that do not intend to
support the

   SDO or vendor specifications."

 		 	   		  =

--_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
The concerns expressed in Issue 327 appear to apply to Sections 1=2C 1.3=2C=
 3.1.2=2C 3.1.3 and 3.1.4. <br><br>Here is a proposed resolution.&nbsp=3B C=
omments welcome. <br><br>






<style>
.ExternalClass p.ecxMsoNormal=2C .ExternalClass li.ecxMsoNormal=2C .Externa=
lClass div.ecxMsoNormal
{margin-bottom:.0001pt=3Bfont-size:11.0pt=3Bfont-family:'Calibri'=2C'sans-s=
erif'=3B}
.ExternalClass a:link=2C .ExternalClass span.ecxMsoHyperlink
{color:blue=3Btext-decoration:underline=3B}
.ExternalClass a:visited=2C .ExternalClass span.ecxMsoHyperlinkFollowed
{color:purple=3Btext-decoration:underline=3B}
.ExternalClass span.ecxEmailStyle17
{font-family:'Calibri'=2C'sans-serif'=3Bcolor:windowtext=3B}
.ExternalClass .ecxMsoChpDefault
{=3B}
@page Section1
{size:8.5in 11.0in=3B}
.ExternalClass div.ecxSection1
{page:Section1=3B}
</style>





<div class=3D"ecxSection1">

<p class=3D"ecxMsoNormal">Section 1</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B This document provides guideline=
s for the design of
RADIUS attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B both within the IETF as well as =
within other SDOs.&nbsp=3B By
articulating</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS design guidelines=2C it i=
s hoped that this document
will</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B encourage the development and pu=
blication of high quality
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B However=2C the advice in this do=
cument will not be helpful
unless it is</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B put to use.&nbsp=3B As with "Gui=
delines for Authors and
Reviewers of MIB</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Documents" [RFC4181]=2C it is ex=
pected that this document
will be used</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by authors to check their docume=
nt against the guidelines
prior to</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B requesting review (such as an "E=
xpert Review"
described in</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [RFC3575]).&nbsp=3B Similarly=2C=
 it is expected that this document
will used</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by reviewers (such as WG partici=
pants or the AAA Doctors
[DOCTORS])=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B resulting in an improvement in t=
he consistency of
reviews.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to meet these objective=
s=2C this document needs to
cover not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B only the science of attribute de=
sign=2C but also the art.&nbsp=3B
Therefore=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B in addition to covering the most=
 frequently encountered
issues=2C this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document attempts to provide som=
e of the considerations
motivating</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the guidelines.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to characterize current=
 attribute usage=2C both
the basic and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B complex data types defined in th=
e existing RADIUS RFCs
are reviewed.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed
change is to replace Section 1 with the following:<br></p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B "This document provides guidelin=
es for the design of
RADIUS attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B used to encode service-provision=
ing or authentication
data=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B based on the data model and attr=
ibute formats defined in
RFC 2865 and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B subsequent RADIUS RFCs.&nbsp=3B&=
nbsp=3B In order to characterize
current attribute </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B usage=2C both the basic and comp=
lex data types defined in
the existing </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS RFCs are reviewed. Since =
the RADEXT WG is
currently considering</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B extensions to the RADIUS data mo=
del and attribute
formats=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B future documents may extend the =
data model and guidelines
provided here.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to meet these objective=
s=2C this document needs to
cover not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B only the science of attribute de=
sign=2C but also the art.&nbsp=3B
Therefore=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B in addition to covering the most=
 frequently encountered
issues=2C this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document attempts to provide som=
e of the considerations
motivating</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the guidelines.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS protocol changes=2C or sp=
ecification of attributes </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B (such as Service-Type) that can =
be used to=2C in effect=2C
provide </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B new RADIUS commands require grea=
ter expertise and deeper
review=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B as do changes to the RADIUS oper=
ational model as
discussed in Section </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B 3.3.&nbsp=3B As a result=2C such=
 changes are outside the scope of
this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document and MUST NOT be underta=
ken outside the IETF.&nbsp=3B
Registration policies</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for RADIUS parameters are discus=
sed in [RFC3575] Section
2.1." </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">1.3.&nbsp=3B Applicability</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As RADIUS has become more widely=
 accepted as a management
protocol=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B its usage has become more preval=
ent=2C both within the IETF
as well as</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within other SDOs.&nbsp=3B Given=
 the expanded utilization of
RADIUS=2C it has</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B become apparent that requiring S=
DOs to accomplish all
their RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B work within the IETF is inherent=
ly inefficient and
unscalable.&nbsp=3B By</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B articulating guidelines for RADI=
US attribute design=2C this
document</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B enables SDOs out of the IETF to =
design their own RADIUS
attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within the Vendor-Specific Attri=
bute (VSA) space.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B It is RECOMMENDED that SDOs foll=
ow the guidelines
articulated in this</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document.&nbsp=3B Doing so will =
ensure the widest possible
applicability and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B interoperability of the specific=
ations=2C while requiring
minimal</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B changes to existing systems.&nbs=
p=3B Specifications that do not
follow the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B guidelines articulated herein ar=
e NOT RECOMMENDED.&nbsp=3B
However=2C we</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B recognize that there are some si=
tuations where SDOs or
vendors</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B require the creation of specific=
ations not following these</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B guidelines.&nbsp=3B We do not fo=
rbid these specifications=2C but
it is</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RECOMMENDED that they are create=
d only if they have a
limited scope</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of applicability=2C and all attr=
ibutes defined in those
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B are VSAs=2C as discussed Appendi=
x A.5=2C below.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B It is RECOMMENDED that SDOs and =
vendors seek review of
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute specifications from th=
e IETF.&nbsp=3B However=2C when
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B are SDO specific=2C re-use exist=
ing data types=2C and follow
these</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B guidelines=2C they do not requir=
e IETF review.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B In order to enable IETF review o=
f such specifications=2C
the authors</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B recommend that:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * SDOs m=
ake their RADIUS attribute specifications
publicly</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B availabl=
e=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * SDOs r=
equest review of RADIUS attribute
specifications by</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B sending =
email to the AAA Doctors [DOCTORS] or
equivalent mailing</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B list=3B<=
/p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * IETF a=
nd SDO RADIUS attribute specifications are
reviewed</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B accordin=
g to the guidelines proposed in this document=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * Review=
s of specifications are posted to the RADEXT
WG mailing</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B list=2C =
the AAA Doctors mailing list [DOCTORS] or
another IETF</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B mailing =
list suggested by the Operations &amp=3B
Management Area</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Director=
s of the IETF.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B These reviews can assist with cr=
eation of specifications
that meet</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the SDO requirements=2C and whic=
h are also compatible with
the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B traditional data model and uses =
of RADIUS.&nbsp=3B While these
reviews</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B require access to public specifi=
cations=2C the review
process does not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B require publication of an IETF R=
FC.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The advice in this document appl=
ies to attributes used to
encode</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B service-provisioning or authenti=
cation data.&nbsp=3B RADIUS
protocol</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B changes=2C or specification of a=
ttributes (such as
Service-Type) that</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B can be used to=2C in effect=2C p=
rovide new RADIUS commands
require</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B greater expertise and deeper rev=
iew=2C as do changes to the
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B operational model as discussed b=
elow in Section 3.3.&nbsp=3B
Such changes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B MUST NOT be undertaken outside t=
he IETF and when handled
within the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IETF require "IETF Consensus" fo=
r adoption=2C as
noted in [RFC3575]</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Section 2.1.</p>



<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 1.3 wi=
th the following: </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B "&nbsp=3B&nbsp=3B As RADIUS has =
become more widely accepted as a
management protocol=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B its usage has become more preval=
ent=2C by vendors as well
as the IETF and</p>

<p class=3D"ecxMsoNormal">&nbsp=3B other SDOs. &nbsp=3BBy articulating RADI=
US design guidelines=2C it
is hoped that</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B this document will encourage the=
 development and
publication of </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B high quality RADIUS attribute sp=
ecifications.&nbsp=3B As with
"Guidelines </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for Authors and Reviewers of MIB=
 Documents"
[RFC4181]=2C it is </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B expected that this document will=
 be used by authors to
check their </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B document against the guidelines =
prior to requesting
review </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B (such as an "Expert Review" desc=
ribed in</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [RFC3575]).&nbsp=3B Similarly=2C=
 it is expected that this document
will used</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by reviewers (such as WG partici=
pants or the AAA Doctors
[DOCTORS])=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B resulting in an improvement in t=
he consistency of
reviews.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The guidelines articulated in th=
is document enable the
design</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of attributes with the widest po=
ssible interoperability=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B while requiring minimal changes =
to existing systems.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As a result=2C they are suitable=
 for application to
attributes </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B designed for general usage.&nbsp=
=3B It is RECOMMENDED </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B that these guidelines be applied=
 to review of documents </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B requesting allocations within th=
e IETF standard attribute
</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space defined in [RFC2865]. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B These guidelines may also prove =
useful in the design of </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attributes within the Vendor-Spe=
cific Attribute (VSA)</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space.&nbsp=3B As noted in RFC 2=
865 Section 5.26=2C RADIUS VSAs </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B were created "to allow vendors t=
o support their own
extended </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Attributes not suitable for gene=
ral usage."&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Rather than requesting allocatio=
n of standard attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for those uses=2C [RFC2865] Sect=
ion 6.2 notes that
utilization</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of VSAs "should be encouraged in=
stead of allocation
of global </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute types=2C for functions=
 specific only to one
vendor's </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B implementation of RADIUS=2C wher=
e no interoperability is
deemed useful." </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B However=2C experience has shown =
that attributes not
originally </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B designed for general usage can s=
ubsequently garner
wide-spread </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B deployment.&nbsp=3B An example i=
s the vendor-specific attributes
</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B defined in [RFC2548]=2C which ha=
ve been widely implemented </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within IEEE 802.11 Access Points=
. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As a result=2C while SDOs and ve=
ndors MAY choose to create </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specifications not following the=
se guidelines for use in</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B scenarios within a limited scope=
 of applicability=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B where general usage is possible=
=2C&nbsp=3B adhering to the </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B design guidelines is RECOMMENDED=
.&nbsp=3B Discussion of</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B vendor allocations is provided i=
n Section 3.1.2=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B discussion of SDO allocations is=
 provided in Section</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B 3.1.3. &nbsp=3B&nbsp=3BSDOs and =
vendors desiring review of their </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specifications by the IETF are e=
ncouraged to follow </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the advice presented in Section =
3.1.4." </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">3.1.2.&nbsp=3B Vendor Allocations</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Vendor RADIUS Attribute specific=
ations SHOULD allocate
attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B from the vendor space=2C rather =
than requesting an
allocation from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS standard attribute space.=
</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B As discussed in [RFC2865] Sectio=
n 5.26=2C the vendor space
is intended</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B for vendors to support their own=
 Attributes not suitable
for general</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B use.&nbsp=3B However=2C it is RE=
COMMENDED that vendors follow the
guidelines</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B outlined here=2C which are inten=
ded to enable maximum
interoperability</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B with minimal changes to existing=
 systems.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Following these guidelines means=
 that RADIUS servers can
be updated</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to support the vendor's equipmen=
t by editing a RADIUS
dictionary.&nbsp=3B If</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B these guidelines are not followe=
d=2C then the vendor's
equipment can</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B only be supported via code chang=
es in RADIUS server
implementations.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Such code changes add complexity=
 and delay to
implementations.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 3.1.2 =
with the following:<br></p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">"&nbsp=3B As noted in [RFC3575] Section 2.1=2C ve=
ndors are
encouraged</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to utilize VSAs to define functi=
ons "specific only
to one vendor's</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B implementation of RADIUS=2C wher=
e no interoperability is
deemed useful.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B For functions specific only to o=
ne vendor's
implementation of RADIUS=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the use of that should be encour=
aged instead of the
allocation of</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B global attribute types."</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Nevertheless=2C following the gu=
idelines outlined within
this document</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B has several advantages=2C includ=
ing maximum
interoperability with</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B minimal changes to existing syst=
ems.&nbsp=3B Following these
guidelines </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B means that RADIUS servers can be=
 updated to support the
vendor's </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B equipment by editing a RADIUS di=
ctionary.&nbsp=3B If these
guidelines are </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B not followed=2C then the vendor'=
s equipment can only be
supported </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B via code changes in RADIUS serve=
r implementations.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Such code changes add complexity=
 and delay to
implementations."</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">3.1.3.&nbsp=3B SDO Allocations</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDO RADIUS Attribute specificati=
ons SHOULD allocate
attributes from</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the vendor space=2C rather than =
requesting an allocation
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS standard attribute space=
=2C for attributes matching
any of the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B following criteria:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes relying on data types not defined within
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within an SDO</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within a group
of SDOs.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Any new RADIUS attributes or val=
ues intended for
interoperable use</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B across a broad spectrum of the I=
nternet Community SHOULD
follow the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B normal IETF process=2C and SHOUL=
D result in allocations
from the RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B standard space.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The recommendation for SDOs to a=
llocate attributes from a
vendor</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space rather than via the IETF p=
rocess is a recognition
that SDOs may</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B desire to assert change control =
over their own RADIUS
specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B This change control can be obtai=
ned by requesting a PEC
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Internet Assigned Number Authori=
ty (IANA)=2C for use as a
Vendor-Id</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within a Vendor-Specific attribu=
te.&nbsp=3B Further allocation
of attributes</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B inside of the VSA space defined =
by that Vendor-Id is
subject solely</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to the discretion of the SDO.&nb=
sp=3B Similarly=2C the use of data
types</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B (complex or not) within that VSA=
 space is solely under
the discretion</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B of the SDO.&nbsp=3B It is RECOMM=
ENDED that SDOs follow the
guidelines</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B outlined here=2C which are inten=
ded to enable maximum
interoperability</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B with minimal changes to existing=
 systems.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B It should be understood that SDO=
s do not have to rehost
VSAs into the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B standards space solely for the p=
urpose of obtaining IETF
review.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Rehosting puts pressure on the s=
tandards space=2C and may
be harmful to</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B interoperability=2C since it can=
 create two ways to
provision the same</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B service.&nbsp=3B Rehosting may a=
lso require changes to the
RADIUS data model</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B which will affect implementation=
s that do not intend to
support the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDO specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 3.1.3 =
with the following:<br></p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">"&nbsp=3B Given the expanded utilization of RADIU=
S=2C it has</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B become apparent that requiring S=
DOs to accomplish all
their RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B work within the IETF is inherent=
ly inefficient and
unscalable.&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B SDO RADIUS Attribute specifications SHOU=
LD allocate
attributes from</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B the vendor space=2C rather than =
requesting an allocation
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS standard attribute space=
=2C for attributes matching
any of the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B following criteria:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes relying on data types not defined within
RADIUS</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within an SDO</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B * attrib=
utes intended primarily for use within a group
of SDOs.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Allocation of new RADIUS attribu=
tes or values intended
for interoperable use</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B across a broad spectrum of the I=
nternet Community SHOULD
follow the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B allocation process defined in [R=
FC3575]. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The recommendation for SDOs to a=
llocate attributes from
the vendor</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B space rather than via the IETF p=
rocess recognizes the
need for SDOs</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B to assert change control over th=
eir own RADIUS
specifications.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDOs desiring to define their VS=
As are encouraged to </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B request allocation of a Private =
Enterprise Code (PEC)
from the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Internet Assigned Number Authori=
ty (IANA)=2C for use as a
Vendor-Id.&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The SDO can then allocate attrib=
utes within the VSA space
defined </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by that Vendor-Id=2C at their so=
le discretion.&nbsp=3B Similarly=2C
the use of </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B data types (complex or otherwise=
) within that VSA space
is solely</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B under the discretion of the SDO.=
"</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">3.1.4.&nbsp=3B Publication of specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDOs are encouraged to seek earl=
y review of SSA
specifications by the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IETF.&nbsp=3B This review may be=
 initiated by sending mail to
the AAA</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Doctors list [DOCTORS]=2C with t=
he understanding that this
review is a</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B voluntary-based service offered =
on best-effort basis.&nbsp=3B
Since the IETF</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B is not a membership organization=
=2C in order to enable the
RADIUS SSA</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specification to be reviewed=2C =
it is RECOMMENDED that it
be made</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B publicly available=3B this also =
encourages interoperability.&nbsp=3B
Where the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B RADIUS SSA specification is embe=
dded within a larger
document which</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B cannot be made public=2C the RAD=
IUS attribute and value
definitions</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SHOULD be published instead as a=
n Informational RFC=2C as
with</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [RFC4679].&nbsp=3B This process =
SHOULD be followed instead of
requesting</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IANA allocations from within the=
 standard RADIUS
attribute space.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Similarly=2C vendors are encoura=
ged to make their
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B publicly available=2C for maximu=
m interoperability.&nbsp=3B
However=2C it is not</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B necessary for them to request pu=
blication of their VSA
specifications</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B as Informational RFCs by the IET=
F.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B All other specifications=2C incl=
uding new authentication=2C</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B authorization=2C and/or security=
 mechanisms SHOULD be
allocated via the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B standard RADIUS space=2C as note=
d in [RFC3575] Section 2.1.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">[BA] Proposed change is to replace Section 3.1.4 =
with the following:</p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">"&nbsp=3B SDOs or vendors desiring review of thei=
r RADIUS
specifications </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B by the IETF are&nbsp=3B encourag=
ed to seek review as early as
possible=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B so as to avoid potential delays.=
&nbsp=3B Since reviews are
handled by volunteers=2C </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B responses are provided on a best=
-effort basis=2C with no
service</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B level guarantees.&nbsp=3B&nbsp=
=3B In order to provide reviewers with
access to the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B specification=2C&nbsp=3B SDOs an=
d vendors are encouraged to make
them publicly available.</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Where the RADIUS specification i=
s embedded within a
larger document which</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B cannot be made public=2C the RAD=
IUS attribute and value
definitions</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B can be made available on a publi=
c web site or can be
published as </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B an Informational RFC=2C as with =
[RFC4679]. </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Review can be requested by sendi=
ng email to the AAA
Doctors [DOCTORS]</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B or equivalent mailing list.&nbsp=
=3B The IETF Operations &amp=3B
Management</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B Area Directors will then arrange=
 for the review to be</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B completed and posted to the AAA =
Doctors mailing list</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B [DOCTORS]=2C RADEXT WG mailing l=
ist=2C or other IETF mailing</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B list.&nbsp=3B </p>

<p class=3D"ecxMsoNormal">&nbsp=3B</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B The review process requires neit=
her allocation of
attributes </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B within the IETF standard attribu=
te space nor publication
of an </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B IETF RFC.&nbsp=3B Requiring SDOs=
 or vendors to rehost VSAs into
the IETF standards </p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B attribute space solely for the p=
urpose of obtaining
review</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B would put pressure on the standa=
rds space=2C and may be
harmful to</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B interoperability=2C since it can=
 create two ways to
provision the same</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B service.&nbsp=3B Rehosting may a=
lso require changes to the
RADIUS data model</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B which will affect implementation=
s that do not intend to
support the</p>

<p class=3D"ecxMsoNormal">&nbsp=3B&nbsp=3B SDO or vendor specifications."</=
p>

</div> 		 	   		  </body>
</html>=

--_9228ebb3-5c4f-4dd3-82ce-73e1e27fef6a_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 14 Feb 2010 02:13:55 +0000
Message-ID: <BLU137-DS2801F368B1134D7EA2B3E934B0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: REQUIRED READING: RADEXT Virtual Interim Design Guidelines Discussion
Date: Sat, 13 Feb 2010 18:14:46 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CAACD8.6CD963A0"
Thread-Index: AcqtGmp+Mp9kWH1mT7SZV3/KM1CU2gAACIrQ
Content-Language: en-us

------=_NextPart_000_000A_01CAACD8.6CD963A0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dan Romascanu said:

 

"I hope that the WG will use the time until the virtual meeting and the
meeting itself to make progress and clean up the remaining open issues. I
suggested a few weeks ago that Avi and Alan work together on the text that
describes what this document exactly covers and what is being left for
future work. I do not know if this happened, but we have new text proposals.
I suggest that Avi, Woj, and the other WG participants who made comments
during the 'Last Look' period address the changes in the document suggested
by Alan and send back feedback and comments to the list or their agreement
with the proposed changes even before the virtual meeting. All participants
in the WG are  of course welcome and invited to express their opinions with
comments or 'I am OK with the document' messages."

 
[BA]  I have collected Avi Lior's review of the -10 text (and suggested
changes) within Issue 327:
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 327>
Applicability .  Joe Salowey's review is 
provided in Issue 325:
<http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue 325> Review .
As noted in a previous message summarizing the results of the "Last Look" (
<http://ops.ietf.org/lists/radiusext/2010/msg00150.html>
http://ops.ietf.org/lists/radiusext/2010/msg00150.html) there appears to be
WG consensus to make changes to the document to address the concerns that
have been raised.
 
In order for the interim meeting to go smoothly on February 23, 2010, it
would be ideal to have proposed text changes to resolve each issue, as Dan
suggests.  To further this, it would be ideal for Avi and Joe to examine the
modified text and confirm (or deny) that their issues have been addressed:

http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt

 Changes between -10 and -11 are available here:

http://git.freeradius.org/ietf/10-11-diff.html

 
Note that if we do not have proposed text changes by February 20, 2010 then
the chairs will go over the existing issues and propose changes on the
mailing list which we will discuss at the Interim.  
 
 
 
 

 


------=_NextPart_000_000A_01CAACD8.6CD963A0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal>Dan Romascanu said:<o:p></o:p></p>

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

<p class=3DMsoNormal>&#8220;<span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I hope that the WG will use the time until the virtual =
meeting and
the meeting itself to make progress and clean up the remaining open =
issues. I
suggested a few weeks ago that Avi and Alan work together on the text =
that
describes what this document exactly covers and what is being left for =
future
work. I do not know if this happened, but we have new text proposals. I =
suggest
that </span><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Avi, Woj, and the other WG participants who made comments =
during
the&nbsp;'Last Look' period address the changes in the document =
suggested by
Alan and send back feedback&nbsp;and comments to the list or their =
</span><span
lang=3DEN style=3D'color:blue'>agreement with the proposed =
changes</span><span
lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>&n=
bsp;even
before&nbsp;the virtual meeting.&nbsp;All participants in the WG =
are&nbsp; of
course welcome and invited to express their opinions with comments or 'I =
am OK
with the document' messages.</span>&#8221;<o:p></o:p></p>

<pre><o:p>&nbsp;</o:p></pre><pre><span style=3D'color:black'>[BA] =
&nbsp;I have collected Avi Lior&#8217;s review of the -10 text (and =
suggested changes) within Issue 327: <a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
327"><span
style=3D'color:black'>Applicability</span></a> .&nbsp; Joe =
Salowey&#8217;s review is <o:p></o:p></span></pre><pre><span
style=3D'color:black'>provided in Issue 325: <a
href=3D"http://www.drizzle.com/~aboba/RADEXT/radissues3.html#Issue =
325"><span
style=3D'color:black'>Review</span></a> .&nbsp; As noted in a previous =
message summarizing the results of the &#8220;Last Look&#8221; (<a
href=3D"http://ops.ietf.org/lists/radiusext/2010/msg00150.html"><span
style=3D'color:black'>http://ops.ietf.org/lists/radiusext/2010/msg00150.h=
tml</span></a>) there appears to be WG consensus to make changes to the =
document to address the concerns that have been =
raised.<o:p></o:p></span></pre><pre><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'color:black'>In order for the interim meeting to go smoothly on =
February 23, 2010, it would be ideal to have proposed text changes to =
resolve each issue, as Dan suggests.&nbsp; To further this, it would be =
ideal for Avi and Joe to examine the modified text and confirm (or deny) =
that their issues have been addressed:<o:p></o:p></span></pre>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:#1F497D'><a
href=3D"http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt">h=
ttp://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt</a></span><=
span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:#1F497D'>&nbsp;Changes between -10 and -11 are available =
here:</span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style=3D'color:#1F497D'><a =
href=3D"http://git.freeradius.org/ietf/10-11-diff.html">http://git.freera=
dius.org/ietf/10-11-diff.html</a></span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<pre><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'color:black'>Note that if we do not have proposed text changes =
by February 20, 2010 then the chairs will go over the existing issues =
and propose changes on the mailing list which we will discuss at the =
Interim. =
&nbsp;<o:p></o:p></span></pre><pre>&nbsp;<o:p></o:p></pre><pre><o:p>&nbsp=
;</o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre>

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

</div>

</body>

</html>

------=_NextPart_000_000A_01CAACD8.6CD963A0--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 11 Feb 2010 13:03:05 +0000
Message-ID: <BLU137-DS1D3D18B35F5FC5597400A934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <radiusext@ops.ietf.org>
Subject: RE: RADEXT Virtual Interim Agenda, Take Two
Date: Thu, 11 Feb 2010 05:02:51 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AD_01CAAAD7.76E5E970"
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAAFhM7wAAJjiAQ
Content-Language: en-us

------=_NextPart_000_01AD_01CAAAD7.76E5E970
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

For those interested in reviewing the proposed changes to Design Guidelines,
I believe that the strawman is available here:

http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt

 

Changes between -10 and -11 are available here:

http://git.freeradius.org/ietf/10-11-diff.html

 

 

 

From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, February 11, 2010 12:34 AM
To: Bernard Aboba; radiusext@ops.ietf.org
Subject: RE: RADEXT Virtual Interim Agenda, Take Two

 

> 11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
<http://tools.ietf.org/html/draft-ietf-radext-design-guidelines>
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

 

I hope that the WG will use the time until the virtual meeting and the
meeting itself to make progress and clean up the remaining open issues. I
suggested a few weeks ago that Avi and Alan work together on the text that
describes what this document exactly covers and what is being left for
future work. I do not know if this happened, but we have new text proposals.
I suggest that Avi, Woj, and the other WG participants who made comments
during the 'Last Look' period address the changes in the document suggested
by Alan and send back feedback and comments to the list or their agreement
with the proposed changes even before the virtual meeting. All participants
in the WG are  of course welcome and invited to express their opinions with
comments or 'I am OK with the document' messages.

 

Thanks and Regards,

 

Dan

 

 

  _____  

From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Bernard Aboba
Sent: Wednesday, February 10, 2010 11:54 PM
To: radiusext@ops.ietf.org
Subject: RADEXT Virtual Interim Agenda, Take Two

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (60 minutes)

11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines


Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


------=_NextPart_000_01AD_01CAAAD7.76E5E970
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

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

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

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For those interested in reviewing the proposed changes to =
Design
Guidelines, I believe that the strawman is available =
here:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href=3D"http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt">h=
ttp://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt</a><o:p></o=
:p></span></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Changes between -10 and -11 are available =
here:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a =
href=3D"http://git.freeradius.org/ietf/10-11-diff.html">http://git.freera=
dius.org/ietf/10-11-diff.html</a><o:p></o:p></span></p>

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

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] <b>On =
Behalf
Of </b>Romascanu, Dan (Dan)<br>
<b>Sent:</b> Thursday, February 11, 2010 12:34 AM<br>
<b>To:</b> Bernard Aboba; radiusext@ops.ietf.org<br>
<b>Subject:</b> RE: RADEXT Virtual Interim Agenda, Take =
Two<o:p></o:p></span></p>

</div>

</div>

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

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>&gt; 11:15 AM &#8211; 12:15 PM PT Design Guidelines, Alan =
DeKok (60
minutes) </span><span style=3D'font-size:10.0pt;color:blue'><a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines"><=
span
style=3D'font-family:"Verdana","sans-serif"'>http://tools.ietf.org/html/d=
raft-ietf-radext-design-guidelines</span></a></span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<span =
style=3D'font-size:10.0pt;color:blue'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I hope that the WG will use the time until the virtual =
meeting and
the meeting itself to make progress and clean up the remaining open =
issues. I
suggested a few weeks ago that Avi and Alan work together on the text =
that
describes what this document exactly covers and what is being left for =
future
work. I do not know if this happened, but we have new text proposals. I =
suggest
that </span><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Avi, Woj, and the other WG participants who made comments =
during
the&nbsp;'Last Look' period address the changes in the document =
suggested by
Alan and send back feedback&nbsp;and comments to the list or their =
</span><span
lang=3DEN style=3D'color:blue'>agreement with the proposed =
changes</span><span
lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>&n=
bsp;even
before&nbsp;the virtual meeting.&nbsp;All participants in the WG =
are&nbsp; of
course welcome and invited to express their opinions with comments or 'I =
am OK
with the document' messages.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Thanks and Regards,</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Dan</span><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 blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] <b>On Behalf Of </b>Bernard =
Aboba<br>
<b>Sent:</b> Wednesday, February 10, 2010 11:54 PM<br>
<b>To:</b> radiusext@ops.ietf.org<br>
<b>Subject:</b> RADEXT Virtual Interim Agenda, Take =
Two</span><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time<br>
<br>
Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines (60 =
minutes)<br>
<br>
11:15 AM &#8211; 12:15 PM PT Design Guidelines, Alan DeKok (60 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_01AD_01CAAAD7.76E5E970--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 11 Feb 2010 08:36:10 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAAAF5.011C3211"
Subject: RE: RADEXT Virtual Interim Agenda, Take Two
Date: Thu, 11 Feb 2010 09:34:17 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0E357@307622ANEX5.global.avaya.com>
Thread-Topic: RADEXT Virtual Interim Agenda, Take Two
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mAAFhM7wA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <radiusext@ops.ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAAAF5.011C3211
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> 11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines
<http://tools.ietf.org/html/draft-ietf-radext-design-guidelines>=20
=20
I hope that the WG will use the time until the virtual meeting and the
meeting itself to make progress and clean up the remaining open issues.
I suggested a few weeks ago that Avi and Alan work together on the text
that describes what this document exactly covers and what is being left
for future work. I do not know if this happened, but we have new text
proposals. I suggest that Avi, Woj, and the other WG participants who
made comments during the 'Last Look' period address the changes in the
document suggested by Alan and send back feedback and comments to the
list or their agreement with the proposed changes even before the
virtual meeting. All participants in the WG are  of course welcome and
invited to express their opinions with comments or 'I am OK with the
document' messages.
=20
Thanks and Regards,
=20
Dan
=20


________________________________

	From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
	Sent: Wednesday, February 10, 2010 11:54 PM
	To: radiusext@ops.ietf.org
	Subject: RADEXT Virtual Interim Agenda, Take Two
=09
=09

	RADEXT Virtual Interim Meeting
	Tuesday, February 23, 2010
	10 AM - 12:30 PM Pacific Time
=09
	Agenda
=09
	10 AM - 10:15 AM PT: Preliminaries=20
=09
	     Conference issues/debugging
	     Attendance
	     Note takers
	     Agenda bash
=09
	RADSEC (60 minutes)
=09
	10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
	http://tools.ietf.org/html/draft-ietf-radext-status-server

	10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15
minutes)
	http://tools.ietf.org/html/draft-ietf-radext-tcp-transport
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>=20

	10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
	http://tools.ietf.org/html/draft-ietf-radext-radsec

=09
	11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter
(15 minutes)
	http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

	Design Guidelines (60 minutes)
=09
	11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60
minutes)
	http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

=09
	Wrap-up (15 minutes)
=09
	12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG
Chairs & ADs (15 minutes)


------_=_NextPart_001_01CAAAF5.011C3211
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: =
auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal
}
SPAN.EmailStyle19 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
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 vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D187272508-11022010><FONT color=3D#0000ff =
size=3D2><FONT=20
face=3DVerdana color=3D#000000>&gt; 11:15 AM &#8211; 12:15 PM PT Design =
Guidelines, Alan=20
DeKok (60 minutes) </FONT><A=20
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines"><=
FONT=20
face=3DVerdana>http://tools.ietf.org/html/draft-ietf-radext-design-guidel=
ines</FONT></A></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT color=3D#0000ff=20
size=3D2><o:p></o:p></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2>I hope=20
that the WG will use the time until the virtual meeting and the meeting =
itself=20
to make progress and clean up the remaining open issues. I suggested a =
few weeks=20
ago that Avi and Alan work together on the text that describes what this =

document exactly covers and what is being left for future work. I do not =
know if=20
this happened, but we have new text proposals. I suggest that <SPAN =
lang=3DEN>Avi,=20
Woj, and the other WG participants who made comments during =
the&nbsp;'Last Look'=20
period address the changes in the document suggested by Alan and send =
back=20
feedback&nbsp;and comments to the list or their <FONT face=3D"Times New =
Roman"=20
size=3D3>agreement with the proposed changes</FONT>&nbsp;even =
before&nbsp;the=20
virtual meeting.&nbsp;All participants in the WG are&nbsp; of course =
welcome and=20
invited to express their opinions with comments or 'I am OK with the =
document'=20
messages.</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN>Thanks and Regards,</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN>Dan</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D187272508-11022010><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
lang=3DEN></SPAN></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=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> owner-radiusext@ops.ietf.org =

  [mailto:owner-radiusext@ops.ietf.org] <B>On Behalf Of </B>Bernard=20
  Aboba<BR><B>Sent:</B> Wednesday, February 10, 2010 11:54 =
PM<BR><B>To:</B>=20
  radiusext@ops.ietf.org<BR><B>Subject:</B> RADEXT Virtual Interim =
Agenda, Take=20
  Two<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">RADEXT=20
  Virtual Interim Meeting<BR>Tuesday, February 23, 2010<BR>10 AM - 12:30 =
PM=20
  Pacific Time<BR><BR>Agenda<BR><BR>10 AM - 10:15 AM PT: Preliminaries=20
  <BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; Conference=20
  issues/debugging<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  Attendance<BR>&nbsp;&nbsp;&nbsp;&nbsp; Note =
takers<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  Agenda bash<BR><BR>RADSEC (60 minutes)<BR><BR>10:15 AM &#8211; 10:30 =
AM PT&nbsp;=20
  Status-Server, Alan DeKok (15 minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</A></SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:30=20
  AM PT &#8211; 10:45 AM PT RADIUS over TCP, Alan DeKok (15 =
minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><SPAN=
=20
  style=3D"COLOR: =
black">http://tools.ietf.org/html/draft-ietf-radext-tcp-transport</SPAN><=
/A></SPAN><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: =
'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">10:45=20
  AM - 11:00 AM PT&nbsp; RADSEC, Stefan Winter (15 minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</A><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>11:00=20
  AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</A><o:p></o=
:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Design=20
  Guidelines (60 minutes)<BR><BR>11:15 AM &#8211; 12:15 PM PT Design =
Guidelines, Alan=20
  DeKok (60 minutes)<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</A><o:p></o=
:p></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'"><BR>Wrap-up=20
  (15 minutes)<BR><BR>12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; =
Discussion and Next=20
  Steps:&nbsp; WG Chairs &amp; ADs (15=20
minutes)<o:p></o:p></SPAN></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAAAF5.011C3211--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 11 Feb 2010 05:39:34 +0000
Message-ID: <BLU137-DS18C7E0625FD2D1AF0530E934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
CC: "'Klaas Wierenga'" <klaas@wierenga.net>
Subject: RADEXT Virtual Interim
Date: Wed, 10 Feb 2010 21:39:47 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Thread-Index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNADr90Lg
Content-Language: en-us

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN='radiusext@ops.ietf.org';RSVP=TRUE:mailto:radiusext@ops.ietf.or
	g
ATTENDEE;CN="'Klaas Wierenga'";ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:klaas@
	wierenga.net
CLASS:PUBLIC
CREATED:20100211T053946Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: WebEx\n\nNote: The GMT offset above 
	does not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\
	n\nRADEXT Virtual Interim Meeting\nTuesday\, February 23\, 2010\n10 AM - 1
	2:30 PM Pacific Time\n\nJabber room (please join):  radext at jabber.ietf.
	org\nAgenda: http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/agenda.txt\n
	Presentations:  http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/\nWebEx p
	arameters:  http://ops.ietf.org/lists/radiusext/2010/msg00169.html\n\n
DTEND:20100223T203000Z
DTSTAMP:20100211T053946Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100211T053946Z
LOCATION:WebEx
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:4
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: WebEx</FONT></SPAN></P>\n\n<P DIR=LTR><SP
	AN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset above does not r
	eflect daylight saving time adjustments.</FONT></SPAN></P>\n\n<P DIR=LTR><
	SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*</FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN
	 LANG="en-us"><FONT COLOR="#000000" SIZE=2 FACE="Verdana">RADEXT Virtual I
	nterim Meeting<BR>\nTuesday\, February 23\, 2010<BR>\n10 AM - 12:30 PM Pac
	ific Time</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN 
	LANG="en-us"></SPAN><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Jabber r
	oom (please join):&nbsp\; radext at jabber.ietf.org</FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Agenda:</FONT></SP
	AN><SPAN LANG="en-us"> </SPAN><A HREF="http://www.drizzle.com/~aboba/RADEX
	T/Feb-Interim/agenda.txt"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></S
	PAN><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">http:
	//www.drizzle.com/~aboba/RADEXT/Feb-Interim/agenda.txt</FONT></U></SPAN><S
	PAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><
	/SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FON
	T SIZE=2 FACE="Tahoma">Presentations:&nbsp\;</FONT></SPAN><SPAN LANG="en-u
	s"> </SPAN><A HREF="http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><SP
	AN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><U><FO
	NT COLOR="#0000FF" SIZE=2 FACE="Tahoma">http://www.drizzle.com/~aboba/RADE
	XT/Feb-Interim/</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG=
	"en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN></P>\n\
	n<P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">WebEx parameters
	:&nbsp\;</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.
	org/lists/radiusext/2010/msg00169.html"><SPAN LANG="en-us"></SPAN><SPAN LA
	NG="en-us"></SPAN><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE=
	"Tahoma">http://ops.ietf.org/lists/radiusext/2010/msg00169.html</FONT></U>
	</SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG=
	"en-us"></SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"></SPAN></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTLASTSEQUENCE:3
X-MS-OLK-APPTSEQTIME:20100211T045741Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 11 Feb 2010 04:57:17 +0000
Message-ID: <BLU137-DS6E50466CDC7C50900A285934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
CC: "'Klaas Wierenga'" <klaas@wierenga.net>
Subject: RADEXT Virtual Interim
Date: Wed, 10 Feb 2010 20:57:41 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Thread-Index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNADqfvdg
Content-Language: en-us

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN='radiusext@ops.ietf.org';RSVP=TRUE:mailto:radiusext@ops.ietf.or
	g
ATTENDEE;CN="'Klaas Wierenga'";ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:klaas@
	wierenga.net
CLASS:PUBLIC
CREATED:20100211T045741Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: WebEx\n\nNote: The GMT offset above 
	does not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\
	n\nRADEXT Virtual Interim Meeting\nTuesday\, February 23\, 2010\n10 AM - 1
	2:30 PM Pacific Time\n\nJabber room (please join):  radext at jabber.ietf.
	org\nAgenda: http://ops.ietf.org/lists/radiusext/2010/msg00168.html\nPrese
	ntations:  http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/\nWebEx parame
	ters:  http://ops.ietf.org/lists/radiusext/2010/msg00169.html\n\n
DTEND:20100223T203000Z
DTSTAMP:20100211T045741Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100211T045741Z
LOCATION:WebEx
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:3
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: WebEx</FONT></SPAN></P>\n\n<P DIR=LTR><SP
	AN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset above does not r
	eflect daylight saving time adjustments.</FONT></SPAN></P>\n\n<P DIR=LTR><
	SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*</FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN
	 LANG="en-us"><FONT COLOR="#000000" SIZE=2 FACE="Verdana">RADEXT Virtual I
	nterim Meeting<BR>\nTuesday\, February 23\, 2010<BR>\n10 AM - 12:30 PM Pac
	ific Time</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN 
	LANG="en-us"></SPAN><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Jabber r
	oom (please join):&nbsp\; radext at jabber.ietf.org</FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Agenda:</FONT></SP
	AN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.org/lists/radiusext
	/2010/msg00168.html"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><
	SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">http://ops
	.ietf.org/lists/radiusext/2010/msg00168.html</FONT></U></SPAN><SPAN LANG="
	en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPA
	N LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT SIZE=2 F
	ACE="Tahoma">Presentations:&nbsp\;</FONT></SPAN><SPAN LANG="en-us"> </SPAN
	><A HREF="http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><SPAN LANG="e
	n-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><U><FONT COLOR="
	#0000FF" SIZE=2 FACE="Tahoma">http://www.drizzle.com/~aboba/RADEXT/Feb-Int
	erim/</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></
	SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LT
	R><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">WebEx parameters:&nbsp\;</
	FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.org/lists/
	radiusext/2010/msg00169.html"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"
	></SPAN><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">h
	ttp://ops.ietf.org/lists/radiusext/2010/msg00169.html</FONT></U></SPAN><SP
	AN LANG="en-us"></SPAN></A><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></
	SPAN><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPA
	N></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTLASTSEQUENCE:2
X-MS-OLK-APPTSEQTIME:20100207T065058Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 11 Feb 2010 04:53:26 +0000
Message-ID: <BLU137-DS6E2C2B13FFF8C7F31A223934E0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Updated RADEXT Virtual Interim Conference Parameters
Date: Wed, 10 Feb 2010 20:53:02 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0152_01CAAA93.0947DF20"
Thread-Index: Acqq08fGATi+Z0ibT8mY/2G7aWWbmAAAgpCg
Content-Language: en-us

------=_NextPart_000_0152_01CAAA93.0947DF20
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

IETF Secretariat invites you to attend this online meeting.=20

Topic: RADEXT WG Virtual Meeting=20
Date: Tuesday, February 23, 2010=20
Time: 10:00 am, Pacific Standard Time (San Francisco, GMT-08:00)=20
Meeting Number: 962 354 516=20
Meeting Password: (This meeting does not require a password.)=20


-------------------------------------------------------=20
To join the online meeting (Now from iPhones too!)=20
-------------------------------------------------------=20
1. Go to https://workgreen.webex.com/workgreen/j.php?ED=3D131933892 =
<https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&UID=3D1115189=
972&RT=3DMiM0> &UID=3D1115189972&RT=3DMiM0=20
2. Enter your name and email address.=20
3. Enter the meeting password: (This meeting does not require a =
password.)=20
4. Click "Join Now".=20

To view in other time zones or languages, please click the link:=20
https://workgreen.webex.com/workgreen/j.php?ED=3D131933892 =
<https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&UID=3D1115189=
972&ORT=3DMiM0> &UID=3D1115189972&ORT=3DMiM0=20

-------------------------------------------------------=20
To join the audio conference only=20
-------------------------------------------------------=20
To receive a call back, provide your phone number when you join the =
meeting, or call the number below and enter the access code.=20
Call-in toll number (US/Canada): 1-408-792-6300=20
Global call-in numbers: =
https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=3DMC =
<https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=3DMC&=
ED=3D131933892&tollFree=3D0> &ED=3D131933892&tollFree=3D0=20

Access code:962 354 516=20

-------------------------------------------------------=20
For assistance=20
-------------------------------------------------------=20
1. Go to https://workgreen.webex.com/workgreen/mc=20
2. On the left navigation bar, click "Support".=20

You can contact me at:=20
amorris@amsl.com=20
1-510-492-4081=20

To add this meeting to your calendar program (for example Microsoft =
Outlook), click this link:=20
https://workgreen.webex.com/workgreen/j.php?ED=3D131933892 =
<https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&UID=3D1115189=
972&ICS=3DMI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DPpj3MUqKboUgp-uDBR-4R-ROZCDrjedd=
whYuFW9GSq8=3D&RT=3DMiM0> =
&UID=3D1115189972&ICS=3DMI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DPpj3MUqKboUgp-uDBR=
-4R-ROZCDrjeddwhYuFW9GSq8=3D&RT=3DMiM0=20

The playback of UCF (Universal Communications Format) rich media files =
requires appropriate players. To view this type of rich media files in =
the meeting, please check whether you have the players installed on your =
computer by going to =
https://workgreen.webex.com/workgreen/systemdiagnosis.php=20

Sign up for a free trial of WebEx=20
http://www.webex.com/go/mcemfreetrial=20

http://www.webex.com=20



IMPORTANT NOTICE: This WebEx service includes a feature that allows =
audio and any documents and other materials exchanged or viewed during =
the session to be recorded. By joining this session, you automatically =
consent to such recordings. If you do not consent to the recording, do =
not join the session.=20


------=_NextPart_000_0152_01CAAA93.0947DF20
Content-Type: text/html; charset="UTF-8"
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=3Dutf-8">
<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;}
 /* 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>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>IETF
Secretariat invites you to attend this online meeting. <br>
<br>
Topic: RADEXT WG Virtual Meeting <br>
Date: Tuesday, February 23, 2010 <br>
<span style=3D'color:black'>Time: 10:00 am, Pacific Standard Time (San =
Francisco,
GMT-08:00)</span> <br>
Meeting Number: 962 354 516 <br>
Meeting Password: (This meeting does not require a password.) <br>
<br>
<br>
------------------------------------------------------- <br>
To join the online meeting (Now from iPhones too!) <br>
------------------------------------------------------- <br>
1. Go to <a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&amp;UI=
D=3D1115189972&amp;RT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D131933=
892&amp;UID=3D1115189972&amp;RT=3DMiM0</a>
<br>
2. Enter your name and email address. <br>
3. Enter the meeting password: (This meeting does not require a =
password.) <br>
4. Click &quot;Join Now&quot;. <br>
<br>
To view in other time zones or languages, please click the link: <br>
<a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&amp;UI=
D=3D1115189972&amp;ORT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D131933=
892&amp;UID=3D1115189972&amp;ORT=3DMiM0</a>
<br>
<br>
------------------------------------------------------- <br>
To join the audio conference only <br>
------------------------------------------------------- <br>
To receive a call back, provide your phone number when you join the =
meeting, or
call the number below and enter the access code. <br>
Call-in toll number (US/Canada): 1-408-792-6300 <br>
Global call-in numbers: <a
href=3D"https://workgreen.webex.com/workgreen/globalcallin.php?serviceTyp=
e=3DMC&amp;ED=3D131933892&amp;tollFree=3D0"
target=3D"_blank">https://workgreen.webex.com/workgreen/globalcallin.php?=
serviceType=3DMC&amp;ED=3D131933892&amp;tollFree=3D0</a>
<br>
<br>
Access code:962 354 516 <br>
<br>
------------------------------------------------------- <br>
For assistance <br>
------------------------------------------------------- <br>
1. Go to <a href=3D"https://workgreen.webex.com/workgreen/mc" =
target=3D"_blank">https://workgreen.webex.com/workgreen/mc</a>
<br>
2. On the left navigation bar, click &quot;Support&quot;. <br>
<br>
You can contact me at: <br>
<a href=3D"mailto:amorris@amsl.com">amorris@amsl.com</a> <br>
1-510-492-4081 <br>
<br>
To add this meeting to your calendar program (for example Microsoft =
Outlook),
click this link: <br>
<a
href=3D"https://workgreen.webex.com/workgreen/j.php?ED=3D131933892&amp;UI=
D=3D1115189972&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SHA2=3DP=
pj3MUqKboUgp-uDBR-4R-ROZCDrjeddwhYuFW9GSq8=3D&amp;RT=3DMiM0"
target=3D"_blank">https://workgreen.webex.com/workgreen/j.php?ED=3D131933=
892&amp;UID=3D1115189972&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&am=
p;SHA2=3DPpj3MUqKboUgp-uDBR-4R-ROZCDrjeddwhYuFW9GSq8=3D&amp;RT=3DMiM0</a>=

<br>
<br>
The playback of UCF (Universal Communications Format) rich media files =
requires
appropriate players. To view this type of rich media files in the =
meeting,
please check whether you have the players installed on your computer by =
going
to <a href=3D"https://workgreen.webex.com/workgreen/systemdiagnosis.php"
target=3D"_blank">https://workgreen.webex.com/workgreen/systemdiagnosis.p=
hp</a> <br>
<br>
Sign up for a free trial of WebEx <br>
<a href=3D"http://www.webex.com/go/mcemfreetrial" =
target=3D"_blank">http://www.webex.com/go/mcemfreetrial</a>
<br>
<br>
<a href=3D"http://www.webex.com" =
target=3D"_blank">http://www.webex.com</a> <br>
<br>
<br>
<br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows =
audio and
any documents and other materials exchanged or viewed during the session =
to be
recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, do not join the =
session. </span><o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0152_01CAAA93.0947DF20--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 10 Feb 2010 21:54:39 +0000
Message-ID: <BLU137-DS570599EE0D8C6B358FD13934F0@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take Two
Date: Wed, 10 Feb 2010 13:53:47 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004A_01CAAA58.78127540"
Thread-Index: AcqnhZvO8flAQf8QR3ibsoavOvSPkADFDehwAABo2mA=
Content-Language: en-us

------=_NextPart_000_004A_01CAAA58.78127540
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

RADEXT Virtual Interim Meeting
Tuesday, February 23, 2010
10 AM - 12:30 PM Pacific Time

Agenda

10 AM - 10:15 AM PT: Preliminaries 

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

RADSEC (60 minutes)

10:15 AM - 10:30 AM PT  Status-Server, Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

10:30 AM PT - 10:45 AM PT RADIUS over TCP, Alan DeKok (15 minutes)
 <http://tools.ietf.org/html/draft-ietf-radext-tcp-transport>
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport

10:45 AM - 11:00 AM PT  RADSEC, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec


11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

Design Guidelines (60 minutes)

11:15 AM - 12:15 PM PT Design Guidelines, Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines


Wrap-up (15 minutes)

12:15 PM PT - 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (15
minutes)


------=_NextPart_000_004A_01CAAA58.78127540
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>RADEXT Virtual Interim =
Meeting<br>
Tuesday, February 23, 2010<br>
10 AM - 12:30 PM Pacific Time<br>
<br>
Agenda<br>
<br>
10 AM - 10:15 AM PT: Preliminaries <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; Conference issues/debugging<br>
&nbsp;&nbsp;&nbsp;&nbsp; Attendance<br>
&nbsp;&nbsp;&nbsp;&nbsp; Note takers<br>
&nbsp;&nbsp;&nbsp;&nbsp; Agenda bash<br>
<br>
RADSEC (60 minutes)<br>
<br>
10:15 AM &#8211; 10:30 AM PT&nbsp; Status-Server, Alan DeKok (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-status-server">http:=
//tools.ietf.org/html/draft-ietf-radext-status-server</a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:30 AM PT &#8211; =
10:45 AM PT
RADIUS over TCP, Alan DeKok (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><span=

style=3D'color:black'>http://tools.ietf.org/html/draft-ietf-radext-tcp-tr=
ansport</span></a></span><span
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>10:45 AM - 11:00 AM =
PT&nbsp;
RADSEC, Stefan Winter (15 minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-radsec">http://tools=
.ietf.org/html/draft-ietf-radext-radsec</a><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
11:00 AM - 11:15 AM PT NAI-Based Peer Discovery, Stefan Winter (15 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery">h=
ttp://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>Design Guidelines (60 =
minutes)<br>
<br>
11:15 AM &#8211; 12:15 PM PT Design Guidelines, Alan DeKok (60 =
minutes)<br>
<a =
href=3D"http://tools.ietf.org/html/draft-ietf-radext-design-guidelines">h=
ttp://tools.ietf.org/html/draft-ietf-radext-design-guidelines</a><o:p></o=
:p></span></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
Wrap-up (15 minutes)<br>
<br>
12:15 PM PT &#8211; 12:30 PM PT&nbsp;&nbsp; Discussion and Next =
Steps:&nbsp; WG
Chairs &amp; ADs (15 minutes)<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_004A_01CAAA58.78127540--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 07 Feb 2010 09:13:31 +0000
Message-ID: <4B6E8410.6080801@deployingradius.com>
Date: Sun, 07 Feb 2010 10:12:48 +0100
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Re: RADEXT Virtual Interim Agenda, Take One
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
> 10:15 AM - 11:15 AM PT Design Guidelines, Alan DeKok (60 minutes)
> http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

  Avi, etc.: Please provide a review of of the proposed -11 at

http://git.freeradius.org/ietf/

  This will help make the interim meeting more efficient.

  Alan DeKok.

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 07 Feb 2010 06:50:05 +0000
Message-ID: <BLU137-DS37AC01122F6C69A0C5D6493520@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
CC: "'Klaas Wierenga'" <klaas@wierenga.net>
Subject: RADEXT Virtual Interim
Date: Sat, 6 Feb 2010 22:50:58 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Thread-Index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNAAlSU3Q
Content-Language: en-us

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN='radiusext@ops.ietf.org';RSVP=TRUE:mailto:radiusext@ops.ietf.or
	g
ATTENDEE;CN="'Klaas Wierenga'";ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:klaas@
	wierenga.net
CLASS:PUBLIC
CREATED:20100207T065058Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: 702-473-3463 #222622\n\nNote: The GM
	T offset above does not reflect daylight saving time adjustments.\n\n*~*~*
	~*~*~*~*~*~*~*\n\nThe IETF RADEXT WG will hold a Virtual Interim on Februa
	ry 23\, 2010 10:00:AM PST. To join the Dimdim event simply click here <htt
	ps://webmeeting.dimdim.com/portal/JoinForm.action?confKey=baboba&email=ber
	nard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&attendeePwd=>  \nYou can also join by entering the Meeting Roo
	m "baboba" at Dimdim.com <http://www.dimdim.com/join>  at the time listed 
	above.  <https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=babo
	ba&email=bernard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40
	-4fc0-9835-cf1fdfcc0a4b&attendeePwd>    \n\nMeeting : RADEXT Virtual Inter
	im  \nKey:   \nDial In: 702-473-3463 \nPass Code: 222622   \nStart: Februa
	ry 23\, 2010 10:00:AM PST (Add to Outlook <https://webmeeting.dimdim.com/p
	ortal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&email
	=bernard.aboba@gmail.com&attendeePwd=> )   \nSchedule Ends At: 12:30 PM PS
	T\n\nHint: You don't need to be a member of Dimdim to attend this meeting.
	\n\n It's easy to join and get started\, Click here to sign up for Dimdim 
	Free. <http://www.dimdim.com/registration/Dimdim_Signup.html>  \n\nBut you
	 may find it helpful to check your bandwidth and your A/V setup here <http
	://www.dimdim.com/support/dimdim_tools.html> . \n\n\nRADEXT Virtual Interi
	m Meeting\nTuesday\, February 23\, 2010\n10 AM - 12:30 PM Pacific Time\n\n
	Conferencing Details:\n\nSlide Presentations: http://www.drizzle.com/~abob
	a/RADEXT/Feb-Interim/\nJabber room:  radext at jabber.ietf.org (Please joi
	n)\nDial-in Audioconference details:  http://ops.ietf.org/lists/radiusext/
	2010/msg00161.html\n\nAgenda\n\n10 AM - 10:15 AM PT: Preliminaries \n\n   
	  Conference issues/debugging\n     Attendance\n     Note takers\n     Age
	nda bash\n\nDesign Guidelines (60 minutes)\n\n10:15 AM - 11:15 AM PT Desig
	n Guidelines\, Alan DeKok (60 minutes)\nhttp://tools.ietf.org/html/draft-i
	etf-radext-design-guidelines\n\nRADSEC (60 minutes)\n\n11:15 AM - 11:30 AM
	 PT  RADSEC\, Stefan Winter (15 minutes)\nhttp://tools.ietf.org/html/draft
	-ietf-radext-radsec\n\n11:30 AM - 11:45 AM PT NAI-Based Peer Discovery\, S
	tefan Winter (15 minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-dy
	namic-discovery\n\n11:45 AM - 12:00 PM PT  Status-Server\, Alan DeKok (15 
	minutes)\nhttp://tools.ietf.org/html/draft-ietf-radext-status-server\n\n12
	:00 PM PT - 12:15 PM PT RADIUS over TCP\, Alan DeKok (15 minutes)\nhttp://
	tools.ietf.org/html/draft-ietf-radext-tcp-transport\n\n\nWrap-up (15 minut
	es)\n\n12:15 PM PT – 12:30 PM PT   Discussion and Next Steps:  WG Chairs
	 & ADs (15 minutes)\n
DTEND:20100223T203000Z
DTSTAMP:20100207T065058Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100207T065058Z
LOCATION:702-473-3463 #222622
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:2
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: 702-473-3463 #222622</FONT></SPAN></P>\n\
	n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset a
	bove does not reflect daylight saving time adjustments.</FONT></SPAN></P>\
	n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*<
	/FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Th
	e IETF RADEXT WG will hold a Virtual Interim on</FONT></SPAN><SPAN LANG="e
	n-us"><B> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PST</FONT></B><
	/SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.</FONT></SPAN><SPAN LANG="e
	n-us"> </SPAN><A HREF="https://webmeeting.dimdim.com/portal/JoinForm.actio
	n?confKey=baboba&amp\;email=bernard.aboba@gmail.com&amp\;asPresenter=false
	&amp\;meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp\;attendeePwd="><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">To join the Dimdi
	m event simply click here</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><
	SPAN LANG="en-us"><FONT FACE="Calibri"><BR>\nYou can also join by entering
	 the Meeting Room &quot\;baboba&quot\; at</FONT></SPAN><SPAN LANG="en-us">
	 </SPAN><A HREF="http://www.dimdim.com/join"><SPAN LANG="en-us"><U><FONT C
	OLOR="#0000FF" FACE="Calibri">Dimdim.com</FONT></U></SPAN><SPAN LANG="en-u
	s"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri"> at the time listed 
	above.</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="https://webmeeting
	.dimdim.com/portal/JoinForm.action?confKey=baboba&amp\;email=bernard.aboba
	@gmail.com&amp\;asPresenter=false&amp\;meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&amp\;attendeePwd"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"
	></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calib
	ri"></FONT></SPAN><SPAN LANG="en-us"></SPAN></SPAN><SPAN LANG="en-us"> <FO
	NT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><
	B><FONT FACE="Calibri">Meeting :</FONT></B></SPAN><SPAN LANG="en-us"> <FON
	T FACE="Calibri">RADEXT Virtual Interim  </FONT></SPAN></P>\n\n<P DIR=LTR
	><SPAN LANG="en-us"><B><FONT FACE="Calibri">Key:</FONT></B></SPAN><SPAN LA
	NG="en-us"> <FONT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN
	 LANG="en-us"><B><FONT FACE="Calibri">Dial In:</FONT></B></SPAN><SPAN LANG
	="en-us"> <FONT FACE="Calibri">702-473-3463 </FONT></SPAN></P>\n\n<P DIR=L
	TR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Pass Code:</FONT></B></SPAN>
	<SPAN LANG="en-us"> <FONT FACE="Calibri">222622   </FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Start:</FONT></B></SP
	AN><SPAN LANG="en-us"> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PS
	T (</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="https://webmeeting.dim
	dim.com/portal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0
	a4b&amp\;email=bernard.aboba@gmail.com&amp\;attendeePwd="><SPAN LANG="en-u
	s"><U><FONT COLOR="#0000FF" FACE="Calibri">Add to Outlook</FONT></U></SPAN
	><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">) 
	  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Cali
	bri">Schedule Ends At:</FONT></B></SPAN><SPAN LANG="en-us"> <FONT FACE="Ca
	libri">12:30 PM PST<BR>\n<BR>\n</FONT></SPAN><SPAN LANG="en-us"><B><FONT F
	ACE="Calibri">Hint:</FONT></B></SPAN><SPAN LANG="en-us"><FONT FACE="Calibr
	i"> You don't need to be a member of Dimdim to attend this meeting.</FONT>
	</SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;I
	t's easy to join and get started\,</FONT></SPAN><SPAN LANG="en-us"> </SPAN
	><A HREF="http://www.dimdim.com/registration/Dimdim_Signup.html"><SPAN LAN
	G="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">Click here to sign up fo
	r Dimdim Free.</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="
	en-us"><FONT FACE="Calibri"> </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="
	en-us"><FONT FACE="Calibri">But you may find it helpful to check your band
	width and your A/V setup</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="
	http://www.dimdim.com/support/dimdim_tools.html"><SPAN LANG="en-us"><U><FO
	NT COLOR="#0000FF" FACE="Calibri">here</FONT></U></SPAN><SPAN LANG="en-us"
	></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">.<BR>\n</FONT></SPAN><
	/P>\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>\n\n<P DIR=LTR><SPAN LANG=
	"en-us"><FONT FACE="Calibri">RADEXT Virtual Interim Meeting<BR>\nTuesday\,
	 February 23\, 2010<BR>\n10 AM - 12:30 PM Pacific Time<BR>\n<BR>\nConferen
	cing Details:<BR>\n<BR>\nSlide Presentations:</FONT></SPAN><SPAN LANG="en-
	us"> </SPAN><A HREF="http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/"><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://www.drizzl
	e.com/~aboba/RADEXT/Feb-Interim/</FONT></U></SPAN><SPAN LANG="en-us"></SPA
	N></A><SPAN LANG="en-us"><BR>\n<FONT FACE="Calibri">Jabber room:  radext 
	at jabber.ietf.org (Please join)<BR>\nDial-in Audioconference details: </
	FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="http://ops.ietf.org/lists/
	radiusext/2010/msg00161.html"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" 
	FACE="Calibri">http://ops.ietf.org/lists/radiusext/2010/msg00161.html</FON
	T></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><BR>\n<BR>\n
	<FONT FACE="Calibri">Agenda<BR>\n<BR>\n10 AM - 10:15 AM PT: Preliminaries<
	BR>\n<BR>\n     Conference issues/debugging<BR>\n     Attendance<B
	R>\n     Note takers<BR>\n     Agenda bash<BR>\n<BR>\nDesign Guide
	lines (60 minutes)<BR>\n<BR>\n10:15 AM - 11:15 AM PT Design Guidelines\, A
	lan DeKok (60 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HRE
	F="http://tools.ietf.org/html/draft-ietf-radext-design-guidelines"><SPAN L
	ANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf.org/
	html/draft-ietf-radext-design-guidelines</FONT></U></SPAN><SPAN LANG="en-u
	s"></SPAN></A><SPAN LANG="en-us"><BR>\n<BR>\n<FONT FACE="Calibri">RADSEC (
	60 minutes)<BR>\n<BR>\n11:15 AM - 11:30 AM PT  RADSEC\, Stefan Winter (15
	 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="http://too
	ls.ietf.org/html/draft-ietf-radext-radsec"><SPAN LANG="en-us"><U><FONT COL
	OR="#0000FF" FACE="Calibri">http://tools.ietf.org/html/draft-ietf-radext-r
	adsec</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><B
	R>\n<BR>\n<FONT FACE="Calibri">11:30 AM - 11:45 AM PT NAI-Based Peer Disco
	very\, Stefan Winter (15 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></
	SPAN><A HREF="http://tools.ietf.org/html/draft-ietf-radext-dynamic-discove
	ry"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tool
	s.ietf.org/html/draft-ietf-radext-dynamic-discovery</FONT></U></SPAN><SPAN
	 LANG="en-us"></SPAN></A><SPAN LANG="en-us"><BR>\n<BR>\n<FONT FACE="Calibr
	i">11:45 AM - 12:00 PM PT  Status-Server\, Alan DeKok (15 minutes)<BR>\n<
	/FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="http://tools.ietf.org/html
	/draft-ietf-radext-status-server"><SPAN LANG="en-us"><U><FONT COLOR="#0000
	FF" FACE="Calibri">http://tools.ietf.org/html/draft-ietf-radext-status-ser
	ver</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><BR>
	\n<BR>\n<FONT FACE="Calibri">12:00 PM PT - 12:15 PM PT RADIUS over TCP\, A
	lan DeKok (15 minutes)<BR>\n</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HRE
	F="http://tools.ietf.org/html/draft-ietf-radext-tcp-transport"><SPAN LANG=
	"en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">http://tools.ietf.org/html
	/draft-ietf-radext-tcp-transport</FONT></U></SPAN><SPAN LANG="en-us"></SPA
	N></A><SPAN LANG="en-us"><BR>\n<BR>\n<BR>\n<FONT FACE="Calibri">Wrap-up (1
	5 minutes)<BR>\n<BR>\n12:15 PM PT – 12:30 PM PT   Discussion and Next 
	Steps:  WG Chairs &amp\; ADs (15 minutes)</FONT></SPAN><SPAN LANG="en-us"
	></SPAN></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTLASTSEQUENCE:1
X-MS-OLK-APPTSEQTIME:20100206T195856Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 07 Feb 2010 00:48:24 +0000
Message-ID: <BLU137-W1951B040BEFCE55D331E9D93520@phx.gbl>
Content-Type: multipart/alternative; boundary="_0544eaae-d222-4b38-81d4-343cf222f213_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-status-server-05 (part III)
Date: Sat, 6 Feb 2010 16:47:47 -0800
MIME-Version: 1.0

--_0544eaae-d222-4b38-81d4-343cf222f213_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Section 4.3

On reading this section I am unsure about whether the discussion relates to=
 failover between proxies or servers.=20
Suggested rewrite:

4.3.  Fail-over with Status-Server

   A client may wish to failover from one proxy to another in the event tha=
t it does not receive a=20
   response to an Access-Request.  In order to determine whether the lack o=
f response is due to a=20
   problem with the proxy or a downstream server=2C  the client can send pe=
riodic Status-Server packets=20
   to a proxy after lack of a response.  The inter-packet period is Tw=2C a=
s described in Section 4.1.=20

   These packets will help the client determine if the failure was due to a=
n issue on the path between
   the client and proxy or the proxy itself=2C or whether the issue is occu=
rring downstream.=20

   If no response is received to Status-Server packets=2C the RADIUS client=
 can initiate failover to=20
   another proxy.  By continuing to send Status-Server packets to the origi=
nal proxy at an interval
   of Tw=2C the RADIUS client can determine when the original proxy becomes=
 responsive again.=20

   Once three time periods have passed where Status-Server packets have
   been sent and responded to=2C the original proxy should be deemed respon=
sive
   and RADIUS requests may sent to it again.  This determination should
   be made separately for each proxy that the client has a relationship
   with.  The same algorithm should be used for both authentication and
   accounting ports.  The client MUST treat each destination (ip=2C port)
   combination as a unique proxy for the purposes of this
   determination.

   The above behavior is modelled after [RFC3539] Section 3.4.1.  We
   note that if a reliable transport is used for RADIUS=2C then the
   algorithms specified in [RFC3539] MUST be used in preference to the
   ones given here.
Section 5

You might want to add a table entry for User-Name.=20
 		 	   		  =

--_0544eaae-d222-4b38-81d4-343cf222f213_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Section 4.3<br><br>On reading this section I am unsure about whether the di=
scussion relates to failover between proxies or servers. <br>Suggested rewr=
ite:<br><br><pre class=3D"newpage"><span class=3D"h3"><h3><a name=3D"sectio=
n-4.3">4.3</a>.  Fail-over with Status-Server</h3></span><br><br>   A clien=
t may wish to failover from one proxy to another in the event that it does =
not receive a <br>   response to an Access-Request.  In order to determine =
whether the lack of response is due to a <br>   problem with the proxy or a=
 downstream server=2C  the client can send periodic Status-Server packets <=
br>   to a proxy after lack of a response.  The inter-packet period is Tw=
=2C as described in Section 4.1. <br><br>   These packets will help the cli=
ent determine if the failure was due to an issue on the path between<br>   =
the client and proxy or the proxy itself=2C or whether the issue is occurri=
ng downstream. <br><br>   If no response is received to Status-Server packe=
ts=2C the RADIUS client can initiate failover to <br>   another proxy.  By =
continuing to send Status-Server packets to the original proxy at an interv=
al<br>   of Tw=2C the RADIUS client can determine when the original proxy b=
ecomes responsive again. <br><br>   Once three time periods have passed whe=
re Status-Server packets have<br>   been sent and responded to=2C the origi=
nal proxy should be deemed responsive<br>   and RADIUS requests may sent to=
 it again.  This determination should<br>   be made separately for each pro=
xy that the client has a relationship<br>   with.  The same algorithm shoul=
d be used for both authentication and<br>   accounting ports.  The client M=
UST treat each destination (ip=2C port)<br>   combination as a unique proxy=
 for the purposes of this<br>   determination.<br><br>   The above behavior=
 is modelled after <a href=3D"http://tools.ietf.org/html/rfc3539#section-3.=
4.1">[RFC3539] Section&nbsp=3B3.4.1</a>.  We<br>   note that if a reliable =
transport is used for RADIUS=2C then the<br>   algorithms specified in [<a =
href=3D"http://tools.ietf.org/html/rfc3539" title=3D"&quot=3BAuthentication=
=2C Authorization=2C and Accounting (AAA) Transport Profile&quot=3B">RFC353=
9</a>] MUST be used in preference to the<br>   ones given here.<br></pre>Se=
ction 5<br><br>You might want to add a table entry for User-Name. <br> 		 	=
   		  </body>
</html>=

--_0544eaae-d222-4b38-81d4-343cf222f213_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 07 Feb 2010 00:32:46 +0000
Message-ID: <BLU137-W6861B435730E1D4BA388293520@phx.gbl>
Content-Type: multipart/alternative; boundary="_34f144e5-0f72-47bb-b6f9-d40329427b27_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-status-server-05 (Part II)
Date: Sat, 6 Feb 2010 16:32:26 -0800
MIME-Version: 1.0

--_34f144e5-0f72-47bb-b6f9-d40329427b27_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Sections 2.1 and Section 2.2

Section 2 explains the unique properties of Status-Server and why a RADIUS =
client might want to use it.  RFC 2865 Section 2.6
explains why "keepalives" are a bad idea.  Presumably this advice applies t=
o both RADIUS Access-Request and Accounting-Request keepalives.  Given that=
=2C Sections 2.1 and 2.2 belabor the point.  I'd suggest that they be delet=
ed.=20

Section 2.3

I would suggest deleting this section as well.=20

Section 2.3.1

My advice is to incorporate the material in this section into Section 2 (To=
 be retitled Overview).=20

Section 3

     Response Authenticator

         The value of the Authenticator field in Access-Accept=2C or
         Accounting-Response packets is called the Response
         Authenticator=2C and contains a one-way MD5 hash calculated over
         a stream of octets consisting of: the RADIUS packet=2C beginning
         with the Code field=2C including the Identifier=2C the Length=2C t=
he
         Request Authenticator field from the Status-Server packet=2C and
         the response Attributes (if any)=2C followed by the shared
         secret.  That is=2C ResponseAuth =3D
         MD5(Code+ID+Length+RequestAuth+Attributes+Secret) where +
         denotes concatenation.

[BA] Why is this material here?  If you need it at all (I don't think so)=
=2C you can just reference
RFC 2865 and/or 2866.=20

   Status-Server packets MAY include NAS-Identifier=2C and one of NAS-IP-
   Address or NAS-IPv6-Address.  These attributes are not necessary for
   the operation of Status-Server=2C but may be useful information to a
   server that receives those packets.

[BA] You might say that the server MUST ignore other attributes.=20

   Other attributes SHOULD NOT be included in a Status-Server packet.
   User authentication credentials such as User-Password=2C CHAP-Password=
=2C
   EAP-Message=2C etc. MUST NOT appear in a Status-Server packet sent to a
   RADIUS authentication port.  User or NAS accounting attributes such
   as Acct-Session-Id=2C Acct-Status-Type=2C Acct-Input-Octets=2C etc.  MUS=
T
   NOT appear in a Status-Server packet sent to a RADIUS accounting
   port.

[BA] Also=2C presumably User-Name is not included (relevant to the point ab=
out realms made earlier).=20



 		 	   		  =

--_34f144e5-0f72-47bb-b6f9-d40329427b27_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Sections 2.1 and Section 2.2<br><br>Section 2 explains the unique propertie=
s of Status-Server and why a RADIUS client might want to use it.&nbsp=3B RF=
C 2865 Section 2.6<br>explains why "keepalives" are a bad idea.&nbsp=3B Pre=
sumably this advice applies to both RADIUS Access-Request and Accounting-Re=
quest keepalives.&nbsp=3B Given that=2C Sections 2.1 and 2.2 belabor the po=
int.&nbsp=3B I'd suggest that they be deleted. <br><br>Section 2.3<br><br>I=
 would suggest deleting this section as well. <br><br>Section 2.3.1<br><br>=
My advice is to incorporate the material in this section into Section 2 (To=
 be retitled Overview). <br><br>Section 3<br><br><pre class=3D"newpage">   =
  Response Authenticator<br><br>         The value of the Authenticator fie=
ld in Access-Accept=2C or<br>         Accounting-Response packets is called=
 the Response<br>         Authenticator=2C and contains a one-way MD5 hash =
calculated over<br>         a stream of octets consisting of: the RADIUS pa=
cket=2C beginning<br>         with the Code field=2C including the Identifi=
er=2C the Length=2C the<br>         Request Authenticator field from the St=
atus-Server packet=2C and<br>         the response Attributes (if any)=2C f=
ollowed by the shared<br>         secret.  That is=2C ResponseAuth =3D<br> =
        MD5(Code+ID+Length+RequestAuth+Attributes+Secret) where +<br>      =
   denotes concatenation.<br><br>[BA] Why is this material here?  If you ne=
ed it at all (I don't think so)=2C you can just reference<br>RFC 2865 and/o=
r 2866. <br><br>   Status-Server packets MAY include NAS-Identifier=2C and =
one of NAS-IP-<br>   Address or NAS-IPv6-Address.  These attributes are not=
 necessary for<br>   the operation of Status-Server=2C but may be useful in=
formation to a<br>   server that receives those packets.<br><br>[BA] You mi=
ght say that the server MUST ignore other attributes. <br><br>   Other attr=
ibutes SHOULD NOT be included in a Status-Server packet.<br>   User authent=
ication credentials such as User-Password=2C CHAP-Password=2C<br>   EAP-Mes=
sage=2C etc. MUST NOT appear in a Status-Server packet sent to a<br>   RADI=
US authentication port.  User or NAS accounting attributes such<br>   as Ac=
ct-Session-Id=2C Acct-Status-Type=2C Acct-Input-Octets=2C etc.  MUST<br>   =
NOT appear in a Status-Server packet sent to a RADIUS accounting<br>   port=
.<br><br>[BA] Also=2C presumably User-Name is not included (relevant to the=
 point about realms made earlier). <br><br><br><br></pre> 		 	   		  </body=
>
</html>=

--_34f144e5-0f72-47bb-b6f9-d40329427b27_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sun, 07 Feb 2010 00:18:00 +0000
Message-ID: <BLU137-W35CCBE493A9F2C672FE20C93520@phx.gbl>
Content-Type: multipart/alternative; boundary="_e6303a6f-9138-4e94-9116-b1205323940c_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-status-server-05 (part I)
Date: Sat, 6 Feb 2010 16:17:40 -0800
MIME-Version: 1.0

--_e6303a6f-9138-4e94-9116-b1205323940c_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Overall=2C I believe that this document is very close to being ready for su=
bmission to the IESG as an Informational RFC.=20

Section 1.1

   This specification is also limited to being a "hop by hop" query.

   When RADIUS packets transition one or more RADIUS Proxies=2C any
   information about the status of downstreamservers is unavailable to
   the client.  In addition=2C it queries only the status of a RADIUS
   server=2C cannot carry information about specific realms.

   These limitations are discussed in more detail below.


[BA] My suggestion is that this material be moved to Section 2=2C since it =
doesn't relate to the
reasons why publication is recommended as an Informational RFC.=20

Section 2

This section includes a statement of the problem and justification for why =
the Status-Server solution was
chosen.   My suggestion is to begin this section with an explanation of wha=
t Status-Server does=2C then move
on from there. =20

Suggested rewrite:=20

Status-Server packets are sent by a RADIUS client to a RADIUS server in ord=
er to test the status of that=20
server.  Since a Status-Server packet MUST NOT be forwarded by a RADIUS pro=
xy or server=2C the destination
of a Status-Server packet is set to that of the server which is being teste=
d.  As a result=2C the=20
client is provided with an indication of the status of that server only=2C =
since no RADIUS proxies=20
are on the path between the RADIUS client and server.  Since servers respon=
d to a Status-Server packet=20
without examining the  User-Name attribute=2C the response to a Status-Serv=
er packet cannot be used to=20
infer any information about the reachability of specific realms.

The "hop by hop" functionality of Status-Server packets is useful to RADIUS=
 clients attempting to determine
the status of elements on the path between the client and a server.   Since=
 the Status-Server packet=20
is non-forwardable=2C lack of a response may only be due to packet loss or =
the failure of the server in the
destination IP address=2C not due to faults in downstream links=2C proxies =
or servers.  It therefore provides an unambiguous indication
of the status of a server.=20

This information may be useful in situations where the RADIUS client does n=
ot receive a response to
an Access-Request.  A client may have multiple proxies configured=2C with o=
ne proxy marked
as primary and another marked as secondary.  If the client does not
receive a response to a request sent to the primary proxy=2C it can
"fail over" to the secondary=2C and send requests to the secondary
instead of to the primary proxy.

However=2C it is possible that the lack of a response to requests sent
to the primary proxy was due not to a failure within the the
primary=2C but to alternative causes such as a failed link along the=20
path to the destination server=2C or the failure of the destination server.=
=20

In such a situation=2C it may be useful for the client to be able to
distinguish between failure causes so that it does not trigger failover
inappropriately.  For example=2C if the primary proxy is down=2C then quick
failover to the secondary proxy would be prudent=2C whereas if a downstream
failure is the cause=2C  then the value of failover to a secondary proxy wi=
ll
depend on whether packets forwarded by the secondary will utilize independe=
nt
links=2C intermediaries or destination servers.

The Status-Server packet is not a "Keep-Alive" as discussed in
[RFC2865] Section 2.6.  "Keep-Alives" are Access-Request packets sent to
determine whether a downstream server is responsive.  These packets
are typically sent only when a server is suspected to be down=2C and are
no longer sent as soon as the server is available again.=20


 		 	   		  =

--_e6303a6f-9138-4e94-9116-b1205323940c_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Overall=2C I believe that this document is very close to being ready for su=
bmission to the IESG as an Informational RFC. <br><br>Section 1.1<br><pre c=
lass=3D"newpage"><br>   This specification is also limited to being a "hop =
by hop" query.<br><br>   When RADIUS packets transition one or more RADIUS =
Proxies=2C any<br>   information about the status of downstreamservers is u=
navailable to<br>   the client.  In addition=2C it queries only the status =
of a RADIUS<br>   server=2C cannot carry information about specific realms.=
<br><br>   These limitations are discussed in more detail below.<br><br><br=
>[BA] My suggestion is that this material be moved to Section 2=2C since it=
 doesn't relate to the<br>reasons why publication is recommended as an Info=
rmational RFC. <br><br>Section 2<br><br>This section includes a statement o=
f the problem and justification for why the Status-Server solution was<br>c=
hosen.   My suggestion is to begin this section with an explanation of what=
 Status-Server does=2C then move<br>on from there.  <br><br>Suggested rewri=
te: <br><br>Status-Server packets are sent by a RADIUS client to a RADIUS s=
erver in order to test the status of that <br>server.  Since a Status-Serve=
r packet MUST NOT be forwarded by a RADIUS proxy or server=2C the destinati=
on<br>of a Status-Server packet is set to that of the server which is being=
 tested.  As a result=2C the <br>client is provided with an indication of t=
he status of that server only=2C since no RADIUS proxies <br>are on the pat=
h between the RADIUS client and server.  Since servers respond to a Status-=
Server packet <br>without examining the  User-Name attribute=2C the respons=
e to a Status-Server packet cannot be used to <br>infer any information abo=
ut the reachability of specific realms.<br><br>The "hop by hop" functionali=
ty of Status-Server packets is useful to RADIUS clients attempting to deter=
mine<br>the status of elements on the path between the client and a server.=
   Since the Status-Server packet <br>is non-forwardable=2C lack of a respo=
nse may only be due to packet loss or the failure of the server in the<br>d=
estination IP address=2C not due to faults in downstream links=2C proxies o=
r servers.  It therefore provides an unambiguous indication<br>of the statu=
s of a server. <br><br>This information may be useful in situations where t=
he RADIUS client does not receive a response to<br>an Access-Request.  A cl=
ient may have multiple proxies configured=2C with one proxy marked<br>as pr=
imary and another marked as secondary.  If the client does not<br>receive a=
 response to a request sent to the primary proxy=2C it can<br>"fail over" t=
o the secondary=2C and send requests to the secondary<br>instead of to the =
primary proxy.<br><br>However=2C it is possible that the lack of a response=
 to requests sent<br>to the primary proxy was due not to a failure within t=
he the<br>primary=2C but to alternative causes such as a failed link along =
the <br>path to the destination server=2C or the failure of the destination=
 server. <br><br>In such a situation=2C it may be useful for the client to =
be able to<br>distinguish between failure causes so that it does not trigge=
r failover<br>inappropriately.  For example=2C if the primary proxy is down=
=2C then quick<br>failover to the secondary proxy would be prudent=2C where=
as if a downstream<br>failure is the cause=2C  then the value of failover t=
o a secondary proxy will<br>depend on whether packets forwarded by the seco=
ndary will utilize independent<br>links=2C intermediaries or destination se=
rvers.<br><br>The Status-Server packet is not a "Keep-Alive" as discussed i=
n<br><a href=3D"http://tools.ietf.org/html/rfc2865#section-2.6">[RFC2865] S=
ection&nbsp=3B2.6</a>.  "Keep-Alives" are Access-Request packets sent to<br=
>determine whether a downstream server is responsive.  These packets<br>are=
 typically sent only when a server is suspected to be down=2C and are<br>no=
 longer sent as soon as the server is available again. <br><br><br></pre> 	=
	 	   		  </body>
</html>=

--_e6303a6f-9138-4e94-9116-b1205323940c_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 06 Feb 2010 23:40:11 +0000
Message-ID: <BLU137-W11E7A39B6E682E9624AF8793530@phx.gbl>
Content-Type: multipart/alternative; boundary="_ff87476a-ab98-4816-901a-6f2e2bc0406f_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Agenda, Take One
Date: Sat, 6 Feb 2010 15:39:22 -0800
MIME-Version: 1.0

--_ff87476a-ab98-4816-901a-6f2e2bc0406f_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


RADEXT Virtual Interim Meeting
Tuesday=2C February 23=2C 2010
10 AM - 12:30 PM Pacific Time

Conferencing Details:

Slide Presentations: http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/
Jabber room:  radext at jabber.ietf.org (Please join)
Dial-in Audioconference details:  http://ops.ietf.org/lists/radiusext/2010/=
msg00161.html

Agenda

10 AM - 10:15 AM PT: Preliminaries=20

     Conference issues/debugging
     Attendance
     Note takers
     Agenda bash

Design Guidelines (60 minutes)

10:15 AM - 11:15 AM PT Design Guidelines=2C Alan DeKok (60 minutes)
http://tools.ietf.org/html/draft-ietf-radext-design-guidelines

RADSEC (60 minutes)

11:15 AM - 11:30 AM PT  RADSEC=2C Stefan Winter (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-radsec

11:30 AM - 11:45 AM PT NAI-Based Peer Discovery=2C Stefan Winter (15 minute=
s)
http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery

11:45 AM - 12:00 PM PT  Status-Server=2C Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-status-server

12:00 PM PT - 12:15 PM PT RADIUS over TCP=2C Alan DeKok (15 minutes)
http://tools.ietf.org/html/draft-ietf-radext-tcp-transport


Wrap-up (15 minutes)

12:15 PM PT =96 12:30 PM PT   Discussion and Next Steps:  WG Chairs & ADs (=
15 minutes)


 		 	   		  =

--_ff87476a-ab98-4816-901a-6f2e2bc0406f_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
RADEXT Virtual Interim Meeting<br>Tuesday=2C February 23=2C 2010<br>10 AM -=
 12:30 PM Pacific Time<br><br>Conferencing Details:<br><br>Slide Presentati=
ons: http://www.drizzle.com/~aboba/RADEXT/Feb-Interim/<br>Jabber room:&nbsp=
=3B radext at jabber.ietf.org (Please join)<br>Dial-in Audioconference deta=
ils:&nbsp=3B http://ops.ietf.org/lists/radiusext/2010/msg00161.html<br><br>=
Agenda<br><br>10 AM - 10:15 AM PT: Preliminaries <br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B Conference issues/debugging<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=
=3B Attendance<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Note takers<br>&nbsp=3B&=
nbsp=3B&nbsp=3B&nbsp=3B Agenda bash<br><br>Design Guidelines (60 minutes)<b=
r><br>10:15 AM - 11:15 AM PT Design Guidelines=2C Alan DeKok (60 minutes)<b=
r>http://tools.ietf.org/html/draft-ietf-radext-design-guidelines<br><br>RAD=
SEC (60 minutes)<br><br>11:15 AM - 11:30 AM PT&nbsp=3B RADSEC=2C Stefan Win=
ter (15 minutes)<br>http://tools.ietf.org/html/draft-ietf-radext-radsec<br>=
<br>11:30 AM - 11:45 AM PT NAI-Based Peer Discovery=2C Stefan Winter (15 mi=
nutes)<br>http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery<br=
><br>11:45 AM - 12:00 PM PT&nbsp=3B Status-Server=2C Alan DeKok (15 minutes=
)<br>http://tools.ietf.org/html/draft-ietf-radext-status-server<br><br>12:0=
0 PM PT - 12:15 PM PT RADIUS over TCP=2C Alan DeKok (15 minutes)<br>http://=
tools.ietf.org/html/draft-ietf-radext-tcp-transport<br><br><br>Wrap-up (15 =
minutes)<br><br>12:15 PM PT =96 12:30 PM PT&nbsp=3B&nbsp=3B Discussion and =
Next Steps:&nbsp=3B WG Chairs &amp=3B ADs (15 minutes)<br><br><table style=
=3D"border-top: 1px solid black=3B font-weight: bold=3B font-family: 'Segoe=
 UI'=2CTahoma=2Csan-serif=3B"><tbody><tr><td><br></td></tr></tbody></table>=
 		 	   		  </body>
</html>=

--_ff87476a-ab98-4816-901a-6f2e2bc0406f_--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 06 Feb 2010 19:59:25 +0000
Message-ID: <BLU137-DS6C63CE1CD7E507805EF5393530@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim Meeting:  February 23, 2010
Date: Sat, 6 Feb 2010 11:59:25 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_018C_01CAA723.D40C99D0"
thread-index: AcqnZuHjY5WTvlBdS1ChT0H7FQ7p4g==
Content-Language: en-us

------=_NextPart_000_018C_01CAA723.D40C99D0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The IETF RADEXT WG will hold a Virtual Interim on February 23, 2010 10:00:AM
PST. To join the Dimdim event simply click here
<https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=baboba&email=b
ernard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40-4fc0-9835-c
f1fdfcc0a4b&attendeePwd=> 

 

Meeting : RADEXT Virtual Interim  

Key:   

Dial In: 702-473-3463 

Pass Code: 222622   

Start: February 23, 2010 10:00:AM PST (Add to Outlook
<https://webmeeting.dimdim.com/portal/calendar.action?meetingId=3aaea628-1b4
0-4fc0-9835-cf1fdfcc0a4b&email=bernard.aboba@gmail.com&attendeePwd=> )   

Schedule Ends At: 12:30 PM Pacific Time

 

This meeting happens only once   

 

Meeting Agenda:  TBD

Hint: You don't need to be a member of Dimdim to attend this meeting.

 

 It's easy to join and get started, Click
<http://www.dimdim.com/registration/Dimdim_Signup.html>  here to sign up for
Dimdim Free. 

 

But you may find it helpful to check your bandwidth and your A/V setup here
<http://www.dimdim.com/support/dimdim_tools.html> . 



 

 


------=_NextPart_000_018C_01CAA723.D40C99D0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>The IETF RADEXT WG will hold a Virtual Interim on =
<b>February
23, 2010 10:00:AM PST</b>. <a
href=3D"https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=3Dba=
boba&amp;email=3Dbernard.aboba@gmail.com&amp;asPresenter=3Dfalse&amp;meet=
ingId=3D3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp;attendeePwd=3D"
target=3D"_blank">To join the Dimdim event simply click =
here</a><b><o:p></o:p></b></p>

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

<p class=3DMsoNormal><b>Meeting : </b>RADEXT Virtual Interim =
&nbsp;<o:p></o:p></p>

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

<p class=3DMsoNormal><b>Dial In: </b>702-473-3463 <o:p></o:p></p>

<p class=3DMsoNormal><b>Pass Code: </b>222622 &nbsp; <o:p></o:p></p>

<p class=3DMsoNormal><b>Start: </b>February 23, 2010 10:00:AM PST (<a
href=3D"https://webmeeting.dimdim.com/portal/calendar.action?meetingId=3D=
3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp;email=3Dbernard.aboba@gmail.com&=
amp;attendeePwd=3D"
target=3D"_blank">Add to Outlook</a>) &nbsp; <o:p></o:p></p>

<p class=3DMsoNormal><b>Schedule Ends At: </b>12:30 PM Pacific =
Time<o:p></o:p></p>

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

<p class=3DMsoNormal>This meeting happens only once &nbsp; =
<o:p></o:p></p>

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

<p class=3DMsoNormal><b>Meeting Agenda: &nbsp;TBD</b><br>
<br>
<b>Hint:</b> You don't need to be a member of Dimdim to attend this =
meeting.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;It's easy to join and get started, <a
href=3D"http://www.dimdim.com/registration/Dimdim_Signup.html" =
target=3D"_blank">Click
here to sign up for Dimdim Free.</a> <o:p></o:p></p>

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

<p class=3DMsoNormal>But you may find it helpful to check your bandwidth =
and your
A/V setup <a href=3D"http://www.dimdim.com/support/dimdim_tools.html"
target=3D"_blank">here</a>. <br>
<br>
<o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_018C_01CAA723.D40C99D0--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 06 Feb 2010 19:59:16 +0000
Message-ID: <BLU137-DS7151BA276DF1E00BBF0DA93530@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interim
Date: Sat, 6 Feb 2010 11:58:56 -0800
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST; charset="UTF-8"
Content-Transfer-Encoding: 8bit
thread-index: AcqnLMHezqhhBxG4SnyMTG4GbpWbNAAOg8Cg
Content-Language: en-us

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
ATTENDEE;CN=radiusext@ops.ietf.org;RSVP=TRUE:mailto:radiusext@ops.ietf.org
CLASS:PUBLIC
CREATED:20100206T195856Z
DESCRIPTION:When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00
	) Pacific Time (US & Canada).\nWhere: 702-473-3463 #222622\n\nNote: The GM
	T offset above does not reflect daylight saving time adjustments.\n\n*~*~*
	~*~*~*~*~*~*~*\n\nThe IETF RADEXT WG will hold a Virtual Interim on Februa
	ry 23\, 2010 10:00:AM PST. To join the Dimdim event simply click here <htt
	ps://webmeeting.dimdim.com/portal/JoinForm.action?confKey=baboba&email=ber
	nard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&attendeePwd=>  \nYou can also join by entering the Meeting Roo
	m "baboba" at Dimdim.com <http://www.dimdim.com/join>  at the time listed 
	above.  <https://webmeeting.dimdim.com/portal/JoinForm.action?confKey=babo
	ba&email=bernard.aboba@gmail.com&asPresenter=false&meetingId=3aaea628-1b40
	-4fc0-9835-cf1fdfcc0a4b&attendeePwd>    \n\nMeeting : RADEXT Virtual Inter
	im  \nKey:   \nDial In: 702-473-3463 \nPass Code: 222622   \nStart: Februa
	ry 23\, 2010 10:00:AM PST (Add to Outlook <https://webmeeting.dimdim.com/p
	ortal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&email
	=bernard.aboba@gmail.com&attendeePwd=> )   \nSchedule Ends At: Not Applica
	ble   \n\nThis meeting happens only once   \n\nMeeting Agenda:  TBD\n\nHin
	t: You don't need to be a member of Dimdim to attend this meeting.\n\n It'
	s easy to join and get started\, Click here to sign up for Dimdim Free. <h
	ttp://www.dimdim.com/registration/Dimdim_Signup.html>  \n\nBut you may fin
	d it helpful to check your bandwidth and your A/V setup here <http://www.d
	imdim.com/support/dimdim_tools.html> . \n\n\n
DTEND:20100223T203000Z
DTSTAMP:20100206T195856Z
DTSTART:20100223T180000Z
LAST-MODIFIED:20100206T195856Z
LOCATION:702-473-3463 #222622
ORGANIZER;CN="Bernard Aboba":mailto:bernard_aboba@hotmail.com
PRIORITY:5
SEQUENCE:1
SUMMARY;LANGUAGE=en-us:RADEXT Virtual Interim
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E008000000005007BBB3E9A6CA01000000000000000
	010000000D941E73185E4004186779692A1221D1D
X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E
	N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve
	rsion 08.00.0681.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n<!-- Converted f
	rom text/rtf format -->\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calib
	ri">When: Tuesday\, February 23\, 2010 10:00 AM-12:30 PM (UTC-08:00) Pacif
	ic Time (US &amp\; Canada).</FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en
	-us"><FONT FACE="Calibri">Where: 702-473-3463 #222622</FONT></SPAN></P>\n\
	n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Note: The GMT offset a
	bove does not reflect daylight saving time adjustments.</FONT></SPAN></P>\
	n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">*~*~*~*~*~*~*~*~*~*<
	/FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Th
	e IETF RADEXT WG will hold a Virtual Interim on</FONT></SPAN><SPAN LANG="e
	n-us"><B> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PST</FONT></B><
	/SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.</FONT></SPAN><SPAN LANG="e
	n-us"> </SPAN><A HREF="https://webmeeting.dimdim.com/portal/JoinForm.actio
	n?confKey=baboba&amp\;email=bernard.aboba@gmail.com&amp\;asPresenter=false
	&amp\;meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0a4b&amp\;attendeePwd="><S
	PAN LANG="en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">To join the Dimdi
	m event simply click here</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><
	SPAN LANG="en-us"><FONT FACE="Calibri"><BR>\nYou can also join by entering
	 the Meeting Room &quot\;baboba&quot\; at</FONT></SPAN><SPAN LANG="en-us">
	 </SPAN><A HREF="http://www.dimdim.com/join"><SPAN LANG="en-us"><U><FONT C
	OLOR="#0000FF" FACE="Calibri">Dimdim.com</FONT></U></SPAN><SPAN LANG="en-u
	s"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri"> at the time listed 
	above.</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="https://webmeeting
	.dimdim.com/portal/JoinForm.action?confKey=baboba&amp\;email=bernard.aboba
	@gmail.com&amp\;asPresenter=false&amp\;meetingId=3aaea628-1b40-4fc0-9835-c
	f1fdfcc0a4b&amp\;attendeePwd"><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"
	></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calib
	ri"></FONT></SPAN><SPAN LANG="en-us"></SPAN></SPAN><SPAN LANG="en-us"> <FO
	NT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><
	B><FONT FACE="Calibri">Meeting :</FONT></B></SPAN><SPAN LANG="en-us"> <FON
	T FACE="Calibri">RADEXT Virtual Interim  </FONT></SPAN></P>\n\n<P DIR=LTR
	><SPAN LANG="en-us"><B><FONT FACE="Calibri">Key:</FONT></B></SPAN><SPAN LA
	NG="en-us"> <FONT FACE="Calibri">  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN
	 LANG="en-us"><B><FONT FACE="Calibri">Dial In:</FONT></B></SPAN><SPAN LANG
	="en-us"> <FONT FACE="Calibri">702-473-3463 </FONT></SPAN></P>\n\n<P DIR=L
	TR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Pass Code:</FONT></B></SPAN>
	<SPAN LANG="en-us"> <FONT FACE="Calibri">222622   </FONT></SPAN></P>\n\n<
	P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Start:</FONT></B></SP
	AN><SPAN LANG="en-us"> <FONT FACE="Calibri">February 23\, 2010 10:00:AM PS
	T (</FONT></SPAN><SPAN LANG="en-us"></SPAN><A HREF="https://webmeeting.dim
	dim.com/portal/calendar.action?meetingId=3aaea628-1b40-4fc0-9835-cf1fdfcc0
	a4b&amp\;email=bernard.aboba@gmail.com&amp\;attendeePwd="><SPAN LANG="en-u
	s"><U><FONT COLOR="#0000FF" FACE="Calibri">Add to Outlook</FONT></U></SPAN
	><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">) 
	  </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Cali
	bri">Schedule Ends At:</FONT></B></SPAN><SPAN LANG="en-us"> <FONT FACE="Ca
	libri">Not Applicable   </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-u
	s"><FONT FACE="Calibri">This meeting happens only once   </FONT></SPAN></
	P>\n\n<P DIR=LTR><SPAN LANG="en-us"><B><FONT FACE="Calibri">Meeting Agenda
	:&nbsp\; TBD</FONT></B></SPAN><SPAN LANG="en-us"><BR>\n<BR>\n<B><FONT FACE
	="Calibri">Hint:</FONT></B></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">
	 You don't need to be a member of Dimdim to attend this meeting.</FONT></S
	PAN></P>\n\n<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">&nbsp\;It's
	 easy to join and get started\,</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A
	 HREF="http://www.dimdim.com/registration/Dimdim_Signup.html"><SPAN LANG="
	en-us"><U><FONT COLOR="#0000FF" FACE="Calibri">Click here to sign up for D
	imdim Free.</FONT></U></SPAN><SPAN LANG="en-us"></SPAN></A><SPAN LANG="en-
	us"><FONT FACE="Calibri"> </FONT></SPAN></P>\n\n<P DIR=LTR><SPAN LANG="en-
	us"><FONT FACE="Calibri">But you may find it helpful to check your bandwid
	th and your A/V setup</FONT></SPAN><SPAN LANG="en-us"> </SPAN><A HREF="htt
	p://www.dimdim.com/support/dimdim_tools.html"><SPAN LANG="en-us"><U><FONT 
	COLOR="#0000FF" FACE="Calibri">here</FONT></U></SPAN><SPAN LANG="en-us"></
	SPAN></A><SPAN LANG="en-us"><FONT FACE="Calibri">.<BR>\n</FONT></SPAN></P>
	\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>\n\n</BODY>\n</HTML>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-ALLOWEXTERNCHECK:TRUE
X-MS-OLK-APPTSEQTIME:20100206T195656Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Sat, 06 Feb 2010 13:04:09 +0000
Message-ID: <BLU137-DS6B2770B9691F98F0BC27593530@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RADEXT Virtual Interm Date
Date: Sat, 6 Feb 2010 05:03:57 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012E_01CAA6E9.C9DFD240"
thread-index: AcqnLNe9DBGDR06bQDOc+0wrkHRP/g==
Content-Language: en-us

------=_NextPart_000_012E_01CAA6E9.C9DFD240
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The RADEXT Virtual Interim will take place on Tuesday, February 23, 2010
from 10 AM - 12:30 PM Pacific Time. 

 

Details will be forthcoming. 


------=_NextPart_000_012E_01CAA6E9.C9DFD240
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>The RADEXT Virtual Interim will take place on =
Tuesday,
February 23, 2010 from 10 AM &#8211; 12:30 PM Pacific Time. =
<o:p></o:p></p>

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

<p class=3DMsoNormal>Details will be forthcoming. <o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_012E_01CAA6E9.C9DFD240--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 04 Feb 2010 01:12:52 +0000
Message-ID: <BLU137-DS4F4F654FDF24869ACFA1A93550@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: RE: Review of draft-ietf-radext-tcp-transport (Part III)
Date: Wed, 3 Feb 2010 17:12:30 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0080_01CAA4F4.118DC680"
Thread-Index: AcqlL3gql8AYAuqeR7CGu3QgwGzRQwABl9zw
Content-Language: en-us

------=_NextPart_000_0080_01CAA4F4.118DC680
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Additional comments

 

I am wondering whether this document should take a position on the
recommendations described in [RFC3539] Section 3, particularly:

 

3.2.  Use of Nagle Algorithm

3.3.  Multiple Connections

3.4.2 Primary/Secondary failover

3.4.3 Connection Load Balancing

3.6 Invalidation of Transport Parameter Estimates

3.7 Inability to Use Fast Retransmit

3.8 Head of Line Blocking

3.9 Congestion Avoidance

3.10 Premature Failover

 

 

 

 

 

 

 

 

 


------=_NextPart_000_0080_01CAA4F4.118DC680
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:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.grey
	{mso-style-name:grey;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Additional =
comments<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>I am wondering =
whether this
document should take a position on the recommendations described in =
[RFC3539]
Section 3, particularly:<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.2.&nbsp;
Use of Nagle Algorithm<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.3.&nbsp;
Multiple Connections<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.4.2
Primary/Secondary failover<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.4.3
Connection Load Balancing<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.6
Invalidation of Transport Parameter Estimates<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.7
Inability to Use Fast Retransmit<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.8
Head of Line Blocking<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.9
Congestion Avoidance<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>3.10
Premature Failover<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

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

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

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

</div>

</body>

</html>

------=_NextPart_000_0080_01CAA4F4.118DC680--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 04 Feb 2010 01:04:01 +0000
Message-ID: <BLU137-DS648B9E69F4725B4DC99BC93550@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-tcp-transport (Part II)
Date: Wed, 3 Feb 2010 17:03:15 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0073_01CAA4F2.C70142F0"
Thread-Index: AcqlL3gql8AYAuqeR7CGu3QgwGzRQwAAI1Tw
Content-Language: en-us

------=_NextPart_000_0073_01CAA4F2.C70142F0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Section 2

 

   Adding TCP as a RADIUS transport has a number of impacts on the

   protocol, on applications using the protocol, and on networks that

   deploy the protocol.  In short, RADIUS over TCP is little more than

   sending RADIUS formatted messages over a TCP connection.

 

   As always, there are additional details that need to be discussed.

   This section outlines the various impacts of using RADIUS over TCP,

   and the discusses the proposal in more detail.

 

[BA] How about this? 

 

RADIUS over TCP involves sending RADIUS formatted messages over a TCP
connection.  

In the sections that follow, we discuss the implications for the RADIUS
packet format

(Section 2.1),  port usage (Section 2.2), RADIUS MIBs (Section 2.3) and
RADIUS proxies

(Section 2.5).  TCP-specific issues are discussed in Section 2.6. 

 

Section 2.1

 

   The changes to RADIUS implementations required to implement this

   specification are largely limited to the portions that send and

   receive packets on the network.

 

[BA] Is this sentence necessary?  What portions of a RADIUS implementation
*don't* relate

To sending and receiving packets?   I'd recommend that it be deleted. 

 

Section 2.2

 

   These ports are unused by existing RADIUS applications.

   Implementations SHOULD use the assigned values as the default ports

   for RADIUS over TCP.

 

[BA] You might say "Since these ports are unused by existing RADIUS
implementations,

the assigned values SHOULD be used as the default ports for RADIUS over
TCP."

 

I would merge section 2.4 into this section so that one section can cover
ports

for both RADIUS over TCP and RADIUS over TLS. 

 

Section 2.3

 

You might revise this section to make it clear that the advice for use of
MIBs 

with RADIUS over TCP also applies to RADIUS over TLS. 

 

Section 2.4

 

I'd merge this with Section 2.2. 

 

Section 2.5

 

[BA] Suggest this section be renamed "Liveness Detection". 

 

   If a request is proxied through intermediate proxies, it is not

   possible to detect which of the later hops is responsible for the

   absence of a reply.  An intermediate proxy also cannot signal that

   the outage lies in a later hop because RADIUS does not have the

   ability to carry such signalling information.  This issue is further

   exacerbated by some proxy implementations that do not reply to a

   client if they do not receive a reply to a proxied request.

 

 

[BA] This paragraph makes it seem that absence of a response by a proxy is
incorrect behavior. 

Suggest:

 

   "Within RADIUS as defined in [RFC2865], proxies typically only forward

   traffic between the NAS and RADIUS server, and do not generate their

   own responses.  As a result, when a NAS does not receive a response to

   a request, this could be the result of packet loss between the NAS

   and proxy, a problem on the proxy, loss between the RADIUS proxy and

   server, or a problem with the server."  

 

 

   For RADIUS over TCP, the continued existence of the TCP connection

   SHOULD be used to deduce that the service on the other end of the

   connection is still responsive.  Further, the application layer

   watchdog defined in [RFC3539] Section
<http://tools.ietf.org/html/rfc3539#section-3.4>  3.4 enables clients to

   determine that the server is "live", even though it may not have

   responded recently to non-watchdog requests.

 

[BA] Suggest the following:

 

   "For RADIUS over TLS/TCP, it is RECOMMENDED that implementations

   utilize the existence of a TCP connection along with the 

   application layer watchdog defined in [RFC3539] Section
<http://tools.ietf.org/html/rfc3539#section-3.4>  3.4 to

   determine that the server is "live"."

 

 

   Additional issues with RADIUS proxies involve transport protocol

   changes where the proxy receives packets on one transport protocol,

   and forwards them on a different transport protocol.  There are

   several situations in which the law of "conservation of packets"

   could be violated on an end-to-end basis (e.g. where more packets

   could enter the system than could leave it on a short-term basis):

 

      * Where TCP is used between proxies, it is possible that the

      bandwidth consumed by incoming UDP packets destined to a given

      upstream server could exceed the sending rate of a single TCP

      connection to that server, based on the window size/RTT estimate.

 

      * It is possible for the incoming rate of TCP packets destined to

      a given realm to exceed the UDP throughput achievable using the

      transport guidelines established in [RFC5080
<http://tools.ietf.org/html/rfc5080> ].  This could happen,

      for example, where the TCP window between proxies has opened, but

      packet loss is being experienced on the UDP leg, so that the

      effective congestion window on the UDP side is 1.

 

   Intrinsically, proxy systems operate with multiple control loops

   instead of one end-to-end loop, and so are less stable.  This is true

   even for TCP-TCP proxies.  As discussed in [RFC3539
<http://tools.ietf.org/html/rfc3539> ], the only way to

   achieve stability equivalent to a single TCP connection is to mimic

   the end-to-end behavior of a single TCP connection.  This typically

   is not achievable with an application-layer RADIUS implementation,

   regardless of transport.

 

[BA] I suggest this material be put into a different section entitled

"Congestion Control Issues", since it doesn't relate to liveness detection

(the subject of the rest of the section). 

 

Section 2.6

 

   The guidelines defined in [RFC3539 <http://tools.ietf.org/html/rfc3539> ]
for implementing an AAA protocol

   operating over a reliable transport MUST be followed by implementors

   of this specification.

 

[BA] Not sure the MUST adds value here.  I suggest:

 

"The guidelines defined in [RFC3539] for implementing a AAA protocol over

reliable transport are applicable to RADIUS over TLS/TCP."

 

 

   Implementations MUST NOT confuse UDP and TCP transport.  That is,

   RADIUS clients and servers MUST be treated as unique based on a key

   of the three-tuple (IP address, port, transport protocol).

   Implementations MUST permit different shared secrets to be used for

   UDP and TCP connections to the same destination IP address and

   numerical port.

 

 

 

[BA] I'd suggest "RADIUS over TLS/TCP Implementations MUST support receiving
RADIUS packets over both UDP and TLS/TCP transports originating from the
same  endpoint. 

RADIUS packets received over UDP MUST be replied to over UDP;   RADIUS
packets received over TLS/TCP MUST be replied to over TLS/TCP.  That is,

   RADIUS clients and servers MUST be treated as unique based on a key

   of the three-tuple (IP address, port, transport protocol).

   Implementations MUST permit different shared secrets to be used for

   UDP and TLS/TCP connections to the same destination IP address and

   numerical port.

 


2.6.2.  Head of Line Blocking

 
 
   When using UDP as a transport for RADIUS, there is no ordering of
   packets.  If a packet sent by a client is lost, that loss has no
   effect on subsequent packets sent by that client.
 
   Unlike UDP, TCP is subject to issues related to Head of Line (HoL)
   blocking.  This occurs when when a TCP segment is lost and a
   subsequent TCP segment arrives out of order.  While the RADIUS server
   can process RADIUS packets out of order, the semantics of TCP makes
   this impossible.  This limitation can lower the maximum packet
   processing rate of RADIUS over TCP.

 

[BA] Suggest:

 

   When using UDP as a transport for RADIUS, there is no ordering of
   packets.  If a packet sent by a client is lost, that loss has no
   effect on subsequent packets sent by that client.
 
   Unlike UDP, TLS/TCP is subject to issues related to Head of Line (HoL)
   blocking.  This occurs when when a TLS/TCP segment is lost and a
   subsequent TLS/TCP segment arrives out of order.  While the RADIUS server
   can process RADIUS packets out of order, the semantics of TLS/TCP makes
   this impossible.  This limitation can lower the maximum packet
   processing rate of RADIUS over TLS/TCP.
 

2.6.3.  Shared Secrets

 
 
   The use of shared secrets in calculating the Response Authenticator,
   and other attributes such as User-Password or Message-Authenticator
   [RFC3579 <http://tools.ietf.org/html/rfc3579> ] MUST be unchanged from
previous specifications
 
[BA] I'd suggest that this text be merged with Section 2.1, and that the
above paragraph be changed to the following:
 
"The use of TLS/TCP transport does not change the calculation of
security-related
fields (such as the Response-Authenticator) in RADIUS [RFC2865] or RADIUS
Dynamic 
Authorization [RFC5176].  Calculation of attributes such as
User-Password [RFC2865] or Message-Authenticator [RFC3579] also does not
change." 

 

Section 2.6.4

 

   Implementations of this specification SHOULD treat the "silently

   discard" texts referenced above as "silently discard and close the

   connection."  

 

[BA] What is the alternative to this behavior?  Could this be a MUST?

 

   TCP connections MAY be closed if any of the circumstances outlined

   below are seen.  Alternatively, the TCP connection MAY remain open if

   any of the following circumstances are seen, but the invalid packet

   MUST BE silently discarded.

 

[BA] Not sure how you can do this in practice.  Are you assuming that the

Length field remains valid? 

 

Section 2.6.6

 

Given the discussion in Section 1.1, I'm wondering if this section (or some
other section)

shouldn't make a recommendation on the maximum RADIUS message size
applicable to use with 

RADIUS/EAP.  It seems to me that using a larger RADIUS message size would
make a lot of 

sense. 

 

 

 

 

 

 


------=_NextPart_000_0073_01CAA4F2.C70142F0
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:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
h4
	{mso-style-priority:9;
	mso-style-link:"Heading 4 Char";
	margin-top:10.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-style:italic;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.grey
	{mso-style-name:grey;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Heading4Char
	{mso-style-name:"Heading 4 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 4";
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-weight:bold;
	font-style:italic;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Section =
2<o:p></o:p></span></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Adding =
TCP as a
RADIUS transport has a number of impacts on the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
protocol, on
applications using the protocol, and on networks =
that<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; deploy =
the
protocol.&nbsp; In short, RADIUS over TCP is little more =
than<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
sending RADIUS
formatted messages over a TCP connection.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; As =
always,
there are additional details that need to be =
discussed.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; This =
section
outlines the various impacts of using RADIUS over =
TCP,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; and =
the
discusses the proposal in more detail.<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>[BA] How about this? =
<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>RADIUS over TCP =
involves sending
RADIUS formatted messages over a TCP connection.&nbsp; =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>In the sections that =
follow, we
discuss the implications for the RADIUS packet =
format<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>(Section 2.1), =
&nbsp;port usage
(Section 2.2), RADIUS MIBs (Section 2.3) and RADIUS =
proxies<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>(Section 2.5).&nbsp;
TCP-specific issues are discussed in Section 2.6. <o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Section =
2.1<o:p></o:p></span></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; The =
changes to
RADIUS implementations required to implement this<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
specification
are largely limited to the portions that send and<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
receive packets
on the network.<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>[BA] Is this sentence =
necessary?&nbsp;
What portions of a RADIUS implementation *<b>don&#8217;t</b>* =
relate<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>To sending and =
receiving
packets? &nbsp;&nbsp;I&#8217;d recommend that it be deleted. =
<o:p></o:p></span></p>

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

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Section =
2.2<o:p></o:p></span></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; These =
ports are
unused by existing RADIUS applications.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
SHOULD use the assigned values as the default =
ports<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; for =
RADIUS over
TCP.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
You might say &#8220;Since these ports are unused by existing RADIUS
implementations,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>the
assigned values SHOULD be used as the default ports for RADIUS over =
TCP.&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>I
would merge section 2.4 into this section so that one section can cover =
ports<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>for
both RADIUS over TCP and RADIUS over TLS. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section
2.3<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>You
might revise this section to make it clear that the advice for use of =
MIBs <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>with
RADIUS over TCP also applies to RADIUS over TLS. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section
2.4<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>I&#8217;d
merge this with Section 2.2. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section
2.5<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
Suggest this section be renamed &#8220;Liveness Detection&#8221;. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; If a =
request is
proxied through intermediate proxies, it is not<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
possible to
detect which of the later hops is responsible for =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
absence of a
reply.&nbsp; An intermediate proxy also cannot signal =
that<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; the =
outage lies
in a later hop because RADIUS does not have the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
ability to
carry such signalling information.&nbsp; This issue is =
further<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
exacerbated by
some proxy implementations that do not reply to a<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; client =
if they
do not receive a reply to a proxied request.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
This paragraph makes it seem that absence of a response by a proxy is =
incorrect
behavior. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Suggest:<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
&#8220;Within RADIUS as defined in [RFC2865], proxies typically only =
forward<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
traffic between the NAS and RADIUS server, and do not generate =
their<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
own responses.&nbsp; As a result, when a NAS does not receive a response =
to<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
a request, this could be the result of packet loss between the =
NAS<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
and proxy, a problem on the proxy, loss between the RADIUS proxy =
and<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
server, or a problem with the server.&#8221; =
&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; For =
RADIUS over
TCP, the continued existence of the TCP connection<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; SHOULD =
be used
to deduce that the service on the other end of the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
connection is
still responsive.&nbsp; Further, the application =
layer<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
watchdog
defined in <a =
href=3D"http://tools.ietf.org/html/rfc3539#section-3.4">[RFC3539] =
Section&nbsp;3.4</a>
enables clients to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
determine that
the server is &quot;live&quot;, even though it may not =
have<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
responded
recently to non-watchdog requests.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA]
Suggest the following:<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
&#8220;For
RADIUS over TLS/TCP, it is RECOMMENDED that =
implementations<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
utilize the existence
of a TCP connection along with the <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
application
layer watchdog defined in <a
href=3D"http://tools.ietf.org/html/rfc3539#section-3.4">[RFC3539] =
Section&nbsp;3.4</a>
to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
determine that
the server is &quot;live&#8221;.&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Additional
issues with RADIUS proxies involve transport =
protocol<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
changes where
the proxy receives packets on one transport =
protocol,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; and =
forwards
them on a different transport protocol.&nbsp; There =
are<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
several
situations in which the law of &quot;conservation of =
packets&quot;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; could =
be
violated on an end-to-end basis (e.g. where more =
packets<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; could =
enter the
system than could leave it on a short-term basis):<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
* Where TCP is used between proxies, it is possible that =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
bandwidth consumed by incoming UDP packets destined to a =
given<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
upstream server could exceed the sending rate of a single =
TCP<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
connection to that server, based on the window size/RTT =
estimate.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
* It is possible for the incoming rate of TCP packets destined =
to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
a given realm to exceed the UDP throughput achievable using =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
transport guidelines established in [<a
href=3D"http://tools.ietf.org/html/rfc5080"
title=3D"&quot;Common Remote Authentication Dial In User Service =
(RADIUS) Implementation Issues and Suggested =
Fixes&quot;">RFC5080</a>].&nbsp;
This could happen,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
for example, where the TCP window between proxies has opened, =
but<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
packet loss is being experienced on the UDP leg, so that =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
effective congestion window on the UDP side is 1.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Intrinsically,
proxy systems operate with multiple control loops<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
instead of one
end-to-end loop, and so are less stable.&nbsp; This is =
true<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; even =
for
TCP-TCP proxies.&nbsp; As discussed in [<a
href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>],
the only way to<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
achieve
stability equivalent to a single TCP connection is to =
mimic<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; the =
end-to-end
behavior of a single TCP connection.&nbsp; This =
typically<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; is not
achievable with an application-layer RADIUS =
implementation,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
regardless of
transport.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] I suggest this =
material
be put into a different section entitled<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&#8220;Congestion =
Control
Issues&#8221;, since it doesn&#8217;t relate to liveness =
detection<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>(the subject of the =
rest of
the section). <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section =
2.6<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; The =
guidelines
defined in [<a href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>]
for implementing an AAA protocol<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
operating over
a reliable transport MUST be followed by =
implementors<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of =
this
specification.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] Not sure the =
MUST adds
value here.&nbsp; I suggest:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&#8220;The =
guidelines
defined in [RFC3539] for implementing a AAA protocol =
over<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>reliable transport =
are
applicable to RADIUS over TLS/TCP.&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
MUST NOT confuse UDP and TCP transport.&nbsp; That =
is,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; RADIUS =
clients
and servers MUST be treated as unique based on a =
key<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of the
three-tuple (IP address, port, transport =
protocol).<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
MUST permit different shared secrets to be used =
for<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; UDP =
and TCP
connections to the same destination IP address and<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
numerical port.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'>[BA] I&#8217;d suggest &#8220;RADIUS over =
TLS/TCP Implementations
MUST support receiving RADIUS packets over both UDP and TLS/TCP =
transports originating
from the same &nbsp;endpoint. <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'>RADIUS packets received over UDP MUST be =
replied to
over UDP;&nbsp;&nbsp; RADIUS packets received over TLS/TCP MUST be =
replied to
over TLS/TCP. &nbsp;</span><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>That is,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; RADIUS =
clients
and servers MUST be treated as unique based on a =
key<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of the
three-tuple (IP address, port, transport =
protocol).<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
MUST permit different shared secrets to be used =
for<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; UDP =
and TLS/TCP
connections to the same destination IP address and<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
numerical port.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<h4 style=3D'page-break-before:always'><a name=3Dsection-2.6.2><span =
lang=3DEN
style=3D'font-size:10.0pt'>2.6.2</span></a><span lang=3DEN =
style=3D'font-size:10.0pt'>.&nbsp;
Head of Line Blocking<o:p></o:p></span></h4>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; When using UDP as a transport =
for RADIUS, there is no ordering of<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; packets.&nbsp; If a packet sent =
by a client is lost, that loss has no<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; effect on subsequent packets =
sent by that client.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Unlike UDP, TCP is subject to =
issues related to Head of Line (HoL)<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; blocking.&nbsp; This occurs when =
when a TCP segment is lost and a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; subsequent TCP segment arrives =
out of order.&nbsp; While the RADIUS server<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; can process RADIUS packets out =
of order, the semantics of TCP makes<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; this impossible.&nbsp; This =
limitation can lower the maximum packet<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; processing rate of RADIUS over =
TCP.<o:p></o:p></span></pre>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] =
Suggest:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; When using UDP as a transport =
for RADIUS, there is no ordering of<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; packets.&nbsp; If a packet sent =
by a client is lost, that loss has no<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; effect on subsequent packets =
sent by that client.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Unlike UDP, TLS/TCP is subject =
to issues related to Head of Line (HoL)<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; blocking.&nbsp; This occurs when =
when a TLS/TCP segment is lost and a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; subsequent TLS/TCP segment =
arrives out of order.&nbsp; While the RADIUS =
server<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; can process RADIUS packets out =
of order, the semantics of TLS/TCP makes<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; this impossible.&nbsp; This =
limitation can lower the maximum packet<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; processing rate of RADIUS over =
TLS/TCP.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre>

<h4 style=3D'page-break-before:always'><a name=3Dsection-2.6.3><span =
lang=3DEN
style=3D'font-size:10.0pt'>2.6.3</span></a><span lang=3DEN =
style=3D'font-size:10.0pt'>.&nbsp;
Shared Secrets<o:p></o:p></span></h4>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; The use of shared secrets in =
calculating the Response Authenticator,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and other attributes such as =
User-Password or Message-Authenticator<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; [<a
href=3D"http://tools.ietf.org/html/rfc3579"
title=3D"&quot;RADIUS (Remote Authentication Dial In User Service) =
Support For Extensible Authentication Protocol (EAP)&quot;">RFC3579</a>] =
MUST be unchanged from previous =
specifications<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>[BA] I&#8217;d suggest that this text be =
merged with Section 2.1, and that the<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>above paragraph be changed to the =
following:<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&#8220;The use of TLS/TCP transport does not =
change the calculation of security-related<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>fields (such as the Response-Authenticator) =
in RADIUS [RFC2865] or RADIUS Dynamic <o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>Authorization [RFC5176].&nbsp; Calculation of =
attributes such as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>User-Password [RFC2865] or =
Message-Authenticator [RFC3579] also does not change.&#8221; =
</span><span
lang=3DEN style=3D'font-size:10.0pt'><o:p></o:p></span></pre>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section =
2.6.4<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
Implementations
of this specification SHOULD treat the =
&quot;silently<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
discard&quot;
texts referenced above as &quot;silently discard and close =
the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;
connection.&quot;&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>[BA] =
What is the
alternative to this behavior?&nbsp; Could this be a =
MUST?<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; TCP =
connections
MAY be closed if any of the circumstances outlined<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; below =
are
seen.&nbsp; Alternatively, the TCP connection MAY remain open =
if<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; any of =
the
following circumstances are seen, but the invalid =
packet<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; MUST =
BE
silently discarded.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] Not sure how =
you can do
this in practice.&nbsp; Are you assuming that the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Length field =
remains valid? <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Section =
2.6.6<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>Given the =
discussion in
Section 1.1, I&#8217;m wondering if this section (or some other =
section)<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>shouldn&#8217;t =
make a
recommendation on the maximum RADIUS message size applicable to use with =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>RADIUS/EAP. =
&nbsp;It seems
to me that using a larger RADIUS message size would make a lot of =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>sense. =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

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

</div>

</body>

</html>

------=_NextPart_000_0073_01CAA4F2.C70142F0--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Thu, 04 Feb 2010 00:18:52 +0000
Message-ID: <BLU137-DS1E00B50A4DE6656D314EB93550@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: Review of draft-ietf-radext-tcp-transport (Part I)
Date: Wed, 3 Feb 2010 16:17:43 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0066_01CAA4EC.6A4F27D0"
Thread-Index: AcqlL3gql8AYAuqeR7CGu3QgwGzRQw==
Content-Language: en-us

------=_NextPart_000_0066_01CAA4EC.6A4F27D0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Section 1

 

      Transport of fragmented UDP packets

      appears to be a poorly tested code path on network devices.  Some

      devices appear to be incapable of transporting fragmented UDP

      packets, making it difficult to deploy RADIUS in a network where

      those devices are deployed.

 

[BA] In particular, filters routers and firewalls often drop UDP fragments,
since otherwise they would need to reassemble them in order to apply the
filter rules. 

However, this is not a "transport" issue, so much as a forwarding/filtering
issue.  Instead of "Transport" you might say "handling". 

 

 

      * Connectionless transport.  Neither clients nor servers receive
      positive statements that a "connection" is down.  This information
      has to be deduced instead from the absence of a reply to a
      request.

 

[BA] The same thing is also true of TCP transport, unless you're willing to
wait for a Reset or connection timeout.  That's why the Watchdog timer is
needed. 

 

   As RADIUS is widely deployed, and has been widely deployed for well
   over a decade, these issues have been minor in some use-cases, and
   problematic in others..  New systems may be interested in choosing a
   different set of trade-offs than those outlined in [RFC2865
<http://tools.ietf.org/html/rfc2865> ] Section
   2.4.  New systems may also be interested in choosing a more reliable
   transport for use-cases such as inter-server proxying.  For those
   systems, we define RADIUS over TCP

 

[BA] Note double periods in first sentence, and no period in the last
sentence.  As I read the document, it is really only suggesting a different
set of tradeoffs for inter-server proxying.  So you might say "For use-cases
such as inter-server proxying, [RTLS] suggests an alternative transport and
security model -- RADIUS over TLS.  This document describes the transport
implications of running RADIUS over TLS/TCP."

 


1.1.  Applicability of Reliable Transport

 
 
   The intent of this document is to address transport issues related to
   RADIUS over TLS [RTLS
<http://tools.ietf.org/html/draft-ietf-radext-tcp-transport-04#ref-RTLS> ].
The use of "bare" TCP transport (i.e.
   without TLS) is NOT RECOMMENDED, as there has been little
   implementational or operational experience with it.  Additionally,
   [RFC2865] Section <http://tools.ietf.org/html/rfc2865#section-2.4>  2.4
contains a list of reasons why UDP was
   originally chosen as the transport protocol for RADIUS.  UDP SHOULD
   be used as transport protocol in all cases where the rationale given
   in [RFC2865] Section <http://tools.ietf.org/html/rfc2865#section-2.4>
2.4 applies.
 
   Deployment experience with RADIUS over TLS indicates that it is most
   useful for inter-server communication, such as inter-domain
   communication between proxies.  These situations benefit from the
   confidentiality and ciphersuite negotiation that can be provided by
   TLS. Since TLS is already widely available within the operating
   systems used by proxies, implementation barriers are low.
 
   RADIUS over TCP has a similar set of use cases.  Use of TCP as a
   transport between a NAS and RADIUS server is a poor fit, since as
   noted in [RFC3539 <http://tools.ietf.org/html/rfc3539> ], there is likely
to be insufficient traffic for
   the congestion window to remain above the minimum value on a long-
   term basis.  The result is an increase in packets due to ACKs as
   compared to UDP, without a corresponding set of benefits.
 
   In server-server communications the traffic levels in both directions
   are typically high enough to support a larger congestion window as
   well as ACK piggy-backing.  Through use of an application-layer
   watchdog as described in [RFC3539 <http://tools.ietf.org/html/rfc3539> ],
it is possible to address the
   objections to reliable transport described in [RFC2865] Section
<http://tools.ietf.org/html/rfc2865#section-2.4>  2.4.
   However, in these scenarios "bare" TCP does not provide for
   confidentiality or enable negotiation of stronger ciphersuites than
   are available in RADIUS.
 
   As a result of these considerations, use of RADIUS over TCP SHOULD be
   restricted to situations where RADIUS over TLS is employed.  RADIUS
   over "bare" TCP is NOT RECOMMENDED.
 
   There are still a number of benefits to using a reliable transport.
   For example, when RADIUS is used to carry EAP conversions [RFC3579
<http://tools.ietf.org/html/rfc3579> ],
   the EAP exchanges may involve 5 round trips at the RADIUS application
   layer.  We may assume a probability P of packet loss in each
   direction (with P having a value of 1% or less).  Any one
   authentication attempt will then have at least one lost packet, with
   a probability of approximately (10 * P).
 
   These lost packets require the supplicant and/or the NAS to re-
   transmit packets at the application layer.  The difficulty with this
   approach is that retransmission implementations have historically
   been poor.  Some implementations retransmit packets, others do not,
   and others send new packets rather then performing retransmission.
   Some implementations are incapable of detecting EAP retransmissions,
   and will instead treat the retransmitted packet as an error.
 
   These retransmissions have a high likelihood of causing the entire
   authentication session to fail.  For a system with a million logins a
   day, and having a packet loss probability of P=0.01%, we expect that
   0.1% of connections will experience a lost packet.  That is, 1,000
   user sessions each day will experience authentication failure.
 
   In addition, transport of fragmented UDP packets is a poorly tested
   code path on network devices.  Some devices appear to be incapable of
   transporting fragmented UDP packets, meaning that the packet loss
   rate for fragmented packets approaches 100 percent.  The net effect
   can be to prevent the deployment of authentication methods such as
   EAP-TLS that require large RADIUS packets.
 
   Using a reliable transport method such as TCP means that RADIUS
   implementations can remove all application-layer retransmissions, and
   instead rely on the Operating System (OS) kernel's well-tested TCP
   transport to ensure reliable delivery.  In addition, most TCP
   implementations discover Path MTU better than RADIUS application
   implementations, resulting in significantly fewer fragmented packets.
   Modern TCP implementations also implement anti-spoofing provisions,
   which is more difficult to do in UDP applications.
 
   Transporting RADIUS over TCP means that the RADIUS applications can
   leverage these additional protections offered by TCP.
 
   However, there are also some drawbacks to using TCP.  RADIUS over TCP
   has some drawbacks, as noted in [RFC2865] Section
<http://tools.ietf.org/html/rfc2865#section-2.4>  2.4.  [RFC3539]
<http://tools.ietf.org/html/rfc3539#section-2> 
 <http://tools.ietf.org/html/rfc3539#section-2>    Section 2 discusses
further issues with using TCP as a transport for
   Authentication, Authorization, and/or Accounting (AAA) protocols such
   as RADIUS.
 
   Specifically, as noted in [RFC3539] Section
<http://tools.ietf.org/html/rfc3539#section-2.1>  2.1, for systems
   originating low numbers of RADIUS request packets, inter-packet
   spacing is often larger than the packet RTT.  In those situations,
   RADIUS over TCP SHOULD NOT be used.
 
   In general, RADIUS clients generating small amounts of RADIUS traffic
   SHOULD NOT use TCP.  This suggestion will usually apply to most
   NASes, and to most clients that originate CoA-Request and Disconnect-
   Request packets.
 
   RADIUS over TCP is most applicable to RADIUS proxies that exchange a
   large volume of packets with RADIUS clients and servers (10's to
   1000's of packets per second).  In those situations, RADIUS over TCP
   may be a good fit, and may result in increased network stability and
   performance.

 

[BA]  Suggested rewrite:

 

Section 1.1

 

   The intent of this document is to address transport issues related to

   RADIUS over TLS [RTLS] in inter-server communications scenarios, 

   such as inter-domain communication between proxies.  These 

   situations benefit from the confidentiality and ciphersuite 

   negotiation that can be provided by TLS. Since TLS is already 

   widely available within the operating systems used by proxies, 

   implementation barriers are low.  

 

   In scenarios where RADIUS proxies exchange a large volume of

   packets (10+ packets per second), it is likely that there will be
sufficient

   traffic to enable the congestion window to be widened beyond

   the minimum value on a long-term basis, enabling ACK piggy-backing. 

   Through use of an application-layer watchdog as described in [RFC3539], 

   it is possible to address the objections to reliable transport 

   described in [RFC2865] Section 2.4 without substantial

   watchdog traffic, since regular traffic is expected in both 

   directions.  

 

   In addition, use of RADIUS over TLS/TCP has been found to

   improve operational performance when used with multi-round

   trip authentication mechanisms such as RADIUS over EAP [RFC3579].

   In such exchanges, it is typical for EAP fragmentation to

   increase the number of round-trips required.  For example, where

   EAP-TLS authentication [RFC5216] is attempted and both the EAP

   peer and server utilize certificate chains of 8KB, as many as

   15 round-trips can be required if RADIUS packets are restricted

   to 1500 octets in size.  Fragmentation of RADIUS over UDP packets

   is generally inadvisable due to lack of fragmentation support 

   within intermediate devices such as filtering routers, firewalls 

   and NATs.  However, since RADIUS over UDP implementations typically do

   not support MTU discovery, fragmentation can occur even when the

   maximum RADIUS over UDP packet size is restricted to 1500 octets. 

 

   These problems disappear if a 4096 application-layer payload

   can be used alongside RADIUS over TLS/TCP.  Since most TCP

   implementations support MTU discovery, the TCP MSS is automatically

   adjusted to account for the MTU, and the larger congestion

   window supported by TCP may allow multiple TCP segments to

   be sent within a single window.  As a result, RADIUS/EAP

   traffic required for an EAP-TLS authentication with 8KB

   certificate chains may be reduced to 7 round-trips or less, 

   resulting in substantially reduced authentication times. 

 

   In addition, experience indicates that EAP sessions transported 

   over RTLS are less likely to abort unsuccessfully.  Historically,

   RADIUS over UDP implementations have exhibited poor retransmission

   behavior.  Some implementations retransmit packets, others do not,

   and others send new packets rather then performing retransmission.

   Some implementations are incapable of detecting EAP retransmissions,

   and will instead treat the retransmitted packet as an error.  

   As a result, within RADIUS over UDP implementations, retransmissions

   have a high likeilhood of causing an EAP authentication session

   to fail.  For a system with a million logins a day running EAP-TLS

   mutual authentication with 15 round-trips, and having a packet loss 

   probability of P=0.01%, we expect that 0.3% of connections will
experience 

   at least one lost packet.  That is, 3,000 user sessions each day 

   will experience authentication failure.  This is an unacceptable

   failure rate for a mass-market network service. 

 

   Using a reliable transport method such as TCP means that RADIUS

   implementations can remove all application-layer retransmissions, and

   instead rely on the Operating System (OS) kernel's well-tested TCP

   transport to ensure reliable delivery.  In addition, most TCP

   implementations discover Path MTU better than RADIUS application

   implementations, resulting in significantly fewer fragmented packets.

   Modern TCP implementations also implement anti-spoofing provisions,

   which is more difficult to do in UDP applications.

 

   In contrast, use of TLS/TCP as a transport between a NAS and a 

   RADIUS server is a poor fit.  As noted in [RFC3539] Section 2.1, 

   for systems originating low numbers of RADIUS request packets, 

   inter-packet spacing is often larger than the packet RTT, and

   as a result, the congestion window will t ypically not remain

   above the minimum value on a long-term basis. The 

   result is an increase in packets due to ACKs as compared to UDP, 

   without a corresponding set of benefits.  In addition, the lack

   of substantial traffic implies the need for additional watchdog

   traffic to confirm reachability.  

 

   As a result, the objections to reliable transport indicated in 

   [RFC2865] Section 2.4 continue to apply to NAS-RADIUS server 

   communications and UDP SHOULD continue to be used as the transport 

   protocol in this scenario.  In addition, it is recommended that

   implementations of "RADIUS Dynamic AUthorization Extensions" [RFC5176]

   SHOULD continue to utilize UDP transport, since the volume of

   dynamic authorization traffic is usually expected to be small.  

 

   Since "bare" TCP does not provide for confidentiality or enable 

   negotiation of credible ciphersuites, its use is not appropriate for 

   inter-server communications where strong security is required.  As a
result 

   the use of "bare" TCP transport (i.e. without TLS) is NOT RECOMMENDED 

   for use in any situation, and there has been little or no

   operational experience with it.

 

 


------=_NextPart_000_0066_01CAA4EC.6A4F27D0
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:11.0pt;
	font-family:"Calibri","sans-serif";}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Courier New";
	font-weight:bold;}
span.grey
	{mso-style-name:grey;}
.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>

<p class=3DMsoNormal>Section 1<o:p></o:p></p>

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

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Transport of fragmented UDP packets<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
appears to be a poorly tested code path on network devices.&nbsp; =
Some<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
devices appear to be incapable of transporting fragmented =
UDP<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
packets, making it difficult to deploy RADIUS in a network =
where<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
those devices are deployed.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] In particular, =
filters routers
and firewalls often drop UDP fragments, since otherwise they would need =
to
reassemble them in order to apply the filter rules. =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>However, this is =
not a &#8220;transport&#8221;
issue, so much as a forwarding/filtering issue.&nbsp; Instead of =
&#8220;Transport&#8221;
you might say &#8220;handling&#8221;. <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * =
Connectionless transport.&nbsp; Neither clients nor servers =
receive<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; positive =
statements that a &quot;connection&quot; is down.&nbsp; This =
information<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has to be =
deduced instead from the absence of a reply to =
a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
request.<o:p></o:p></span></pre>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier New"'>[BA] The same thing =
is also
true of TCP transport, unless you&#8217;re willing to wait for a Reset =
or connection
timeout. &nbsp;That&#8217;s why the Watchdog timer is needed. =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'page-break-before:always'><span lang=3DEN
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; As RADIUS is widely deployed, =
and has been widely deployed for well<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; over a decade, these issues have =
been minor in some use-cases, and<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; problematic in others..&nbsp; =
New systems may be interested in choosing a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; different set of trade-offs than =
those outlined in [<a
href=3D"http://tools.ietf.org/html/rfc2865"
title=3D"&quot;Remote Authentication Dial In User Service =
(RADIUS)&quot;">RFC2865</a>] Section<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 2.4.&nbsp; New systems may also =
be interested in choosing a more reliable<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transport for use-cases such as =
inter-server proxying.&nbsp; For those<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; systems, we define RADIUS over =
TCP<o:p></o:p></span></pre>

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

<p class=3DMsoNormal>[BA] Note double periods in first sentence, and no =
period in
the last sentence.&nbsp; As I read the document, it is really only =
suggesting a
different set of tradeoffs for inter-server proxying.&nbsp; So you might =
say &#8220;For
use-cases such as inter-server proxying, [RTLS] suggests an alternative =
transport
and security model -- RADIUS over TLS. &nbsp;This document describes the
transport implications of running RADIUS over =
TLS/TCP.&#8221;<o:p></o:p></p>

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

<h3 style=3D'page-break-before:always'><a name=3Dsection-1.1><span =
lang=3DEN
style=3D'font-size:10.0pt'>1.1</span></a><span lang=3DEN =
style=3D'font-size:10.0pt'>.&nbsp;
Applicability of Reliable Transport<o:p></o:p></span></h3>

<pre style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; The intent of this document is =
to address transport issues related to<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TLS [<a
href=3D"http://tools.ietf.org/html/draft-ietf-radext-tcp-transport-04#ref=
-RTLS"
title=3D"&quot;TLS encryption for RADIUS over TCP =
(RadSec)&quot;">RTLS</a>].&nbsp; The use of &quot;bare&quot; TCP =
transport (i.e.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; without TLS) is NOT RECOMMENDED, =
as there has been little<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementational or operational =
experience with it.&nbsp; Additionally,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; <a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a> contains a list of reasons why UDP =
was<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; originally chosen as the =
transport protocol for RADIUS.&nbsp; UDP =
SHOULD<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; be used as transport protocol in =
all cases where the rationale given<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; in <a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a> applies.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Deployment experience with =
RADIUS over TLS indicates that it is most<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; useful for inter-server =
communication, such as inter-domain<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; communication between =
proxies.&nbsp; These situations benefit from =
the<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; confidentiality and ciphersuite =
negotiation that can be provided by<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; TLS. Since TLS is already widely =
available within the operating<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; systems used by proxies, =
implementation barriers are low.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TCP has a similar =
set of use cases.&nbsp; Use of TCP as a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transport between a NAS and =
RADIUS server is a poor fit, since as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; noted in [<a
href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>], there is likely to be =
insufficient traffic for<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; the congestion window to remain =
above the minimum value on a long-<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; term basis.&nbsp; The result is =
an increase in packets due to ACKs as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; compared to UDP, without a =
corresponding set of benefits.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In server-server communications =
the traffic levels in both directions<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; are typically high enough to =
support a larger congestion window as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; well as ACK piggy-backing.&nbsp; =
Through use of an application-layer<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; watchdog as described in [<a
href=3D"http://tools.ietf.org/html/rfc3539"
title=3D"&quot;Authentication, Authorization and Accounting (AAA) =
Transport Profile&quot;">RFC3539</a>], it is possible to address =
the<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; objections to reliable transport =
described in <a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a>.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; However, in these scenarios =
&quot;bare&quot; TCP does not provide for<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; confidentiality or enable =
negotiation of stronger ciphersuites than<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; are available in =
RADIUS.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; As a result of these =
considerations, use of RADIUS over TCP SHOULD =
be<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; restricted to situations where =
RADIUS over TLS is employed.&nbsp; RADIUS<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; over &quot;bare&quot; TCP is NOT =
RECOMMENDED.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; There are still a number of =
benefits to using a reliable transport.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; For example, when RADIUS is used =
to carry EAP conversions [<a
href=3D"http://tools.ietf.org/html/rfc3579"
title=3D"&quot;RADIUS (Remote Authentication Dial In User Service) =
Support For Extensible Authentication Protocol =
(EAP)&quot;">RFC3579</a>],<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; the EAP exchanges may involve 5 =
round trips at the RADIUS application<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; layer.&nbsp; We may assume a =
probability P of packet loss in each<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; direction (with P having a value =
of 1% or less).&nbsp; Any one<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; authentication attempt will then =
have at least one lost packet, with<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; a probability of approximately =
(10 * P).<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'> &nbsp;&nbsp;These lost packets require the =
supplicant and/or the NAS to re-<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transmit packets at the =
application layer.&nbsp; The difficulty with =
this<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; approach is that retransmission =
implementations have historically<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; been poor.&nbsp; Some =
implementations retransmit packets, others do =
not,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and others send new packets =
rather then performing retransmission.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Some implementations are =
incapable of detecting EAP retransmissions,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and will instead treat the =
retransmitted packet as an error.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; These retransmissions have a =
high likelihood of causing the entire<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; authentication session to =
fail.&nbsp; For a system with a million logins =
a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; day, and having a packet loss =
probability of P=3D0.01%, we expect that<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 0.1% of connections will =
experience a lost packet.&nbsp; That is, =
1,000<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; user sessions each day will =
experience authentication failure.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In addition, transport of =
fragmented UDP packets is a poorly tested<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; code path on network =
devices.&nbsp; Some devices appear to be incapable =
of<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transporting fragmented UDP =
packets, meaning that the packet loss<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; rate for fragmented packets =
approaches 100 percent.&nbsp; The net effect<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; can be to prevent the deployment =
of authentication methods such as<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; EAP-TLS that require large =
RADIUS packets.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Using a reliable transport =
method such as TCP means that RADIUS<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementations can remove all =
application-layer retransmissions, and<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; instead rely on the Operating =
System (OS) kernel's well-tested TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; transport to ensure reliable =
delivery.&nbsp; In addition, most TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementations discover Path =
MTU better than RADIUS application<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; implementations, resulting in =
significantly fewer fragmented packets.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Modern TCP implementations also =
implement anti-spoofing provisions,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; which is more difficult to do in =
UDP applications.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Transporting RADIUS over TCP =
means that the RADIUS applications can<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; leverage these additional =
protections offered by TCP.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; However, there are also some =
drawbacks to using TCP.&nbsp; RADIUS over =
TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; has some drawbacks, as noted in =
<a
href=3D"http://tools.ietf.org/html/rfc2865#section-2.4">[RFC2865] =
Section&nbsp;2.4</a>.&nbsp; <a
href=3D"http://tools.ietf.org/html/rfc3539#section-2">[RFC3539]<o:p></o:p=
></a></span></pre><pre
style=3D'page-break-before:always'><span class=3DMsoHyperlink><span =
lang=3DEN
style=3D'font-size:10.0pt'><a =
href=3D"http://tools.ietf.org/html/rfc3539#section-2">&nbsp;&nbsp; =
Section&nbsp;2</a></span></span><span
lang=3DEN style=3D'font-size:10.0pt'> discusses further issues with =
using TCP as a transport for<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Authentication, Authorization, =
and/or Accounting (AAA) protocols such<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; as =
RADIUS.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Specifically, as noted in <a
href=3D"http://tools.ietf.org/html/rfc3539#section-2.1">[RFC3539] =
Section&nbsp;2.1</a>, for systems<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; originating low numbers of =
RADIUS request packets, inter-packet<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; spacing is often larger than the =
packet RTT.&nbsp; In those situations,<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TCP SHOULD NOT be =
used.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In general, RADIUS clients =
generating small amounts of RADIUS traffic<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; SHOULD NOT use TCP.&nbsp; This =
suggestion will usually apply to most<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; NASes, and to most clients that =
originate CoA-Request and Disconnect-<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Request =
packets.<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; RADIUS over TCP is most =
applicable to RADIUS proxies that exchange a<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; large volume of packets with =
RADIUS clients and servers (10's to<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1000's of packets per =
second).&nbsp; In those situations, RADIUS over =
TCP<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; may be a good fit, and may =
result in increased network stability and<o:p></o:p></span></pre><pre
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; =
performance.<o:p></o:p></span></pre>

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

<p class=3DMsoNormal>[BA] &nbsp;Suggested rewrite:<o:p></o:p></p>

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

<p class=3DMsoNormal>Section 1.1<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; The intent of this document is to =
address
transport issues related to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; RADIUS over TLS [RTLS] in inter-server
communications scenarios, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; such as inter-domain communication =
between
proxies.&nbsp; These <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; situations benefit from the =
confidentiality and
ciphersuite <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; negotiation that can be provided by =
TLS. Since
TLS is already <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; widely available within the operating =
systems
used by proxies, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementation barriers are low.&nbsp; =
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; In scenarios where RADIUS proxies =
exchange a
large volume of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; packets (10+ packets per second), it =
is likely
that there will be sufficient<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; traffic to enable the congestion =
window to be
widened beyond<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; the minimum value on a long-term =
basis,
enabling ACK piggy-backing. <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Through use of an application-layer =
watchdog as
described in [RFC3539], <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; it is possible to address the =
objections to reliable
transport <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; described in [RFC2865] Section 2.4 =
without
substantial<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; watchdog traffic, since regular =
traffic is
expected in both <o:p></o:p></p>

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

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

<p class=3DMsoNormal>&nbsp;&nbsp; In addition, use of RADIUS over =
TLS/TCP has
been found to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; improve operational performance when =
used with
multi-round<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; trip authentication mechanisms such as =
RADIUS
over EAP [RFC3579].<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; In such exchanges, it is typical for =
EAP
fragmentation to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; increase the number of round-trips
required.&nbsp; For example, where<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; EAP-TLS authentication [RFC5216] is =
attempted
and both the EAP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; peer and server utilize certificate =
chains of
8KB, as many as<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; 15 round-trips can be required if =
RADIUS
packets are restricted<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; to 1500 octets in size.&nbsp; =
Fragmentation of
RADIUS over UDP packets<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; is generally inadvisable due to lack =
of
fragmentation support <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; within intermediate devices such as =
filtering
routers, firewalls <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; and NATs.&nbsp; However, since RADIUS =
over UDP
implementations typically do<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; not support MTU discovery, =
fragmentation can
occur even when the<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp; &nbsp;maximum RADIUS over UDP packet size is
restricted to 1500 octets. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; These problems disappear if a 4096
application-layer payload<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; can be used alongside RADIUS over
TLS/TCP.&nbsp; Since most TCP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations support MTU discovery, =
the TCP
MSS is automatically<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; adjusted to account for the MTU, and =
the larger
congestion<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; window supported by TCP may allow =
multiple TCP
segments to<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; be sent within a single window.&nbsp; =
As a
result, RADIUS/EAP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; traffic required for an EAP-TLS =
authentication
with 8KB<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; certificate chains may be reduced to 7
round-trips or less, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; resulting in substantially reduced
authentication times. <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; In addition, experience indicates that =
EAP
sessions transported <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; over RTLS are less likely to abort
unsuccessfully.&nbsp; Historically,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; RADIUS over UDP implementations have =
exhibited
poor retransmission<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; behavior.&nbsp; Some implementations =
retransmit
packets, others do not,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; and others send new packets rather =
then
performing retransmission.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Some implementations are incapable of =
detecting
EAP retransmissions,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; and will instead treat the =
retransmitted packet
as an error.&nbsp; <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; As a result, within RADIUS over UDP
implementations, retransmissions<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; have a high likeilhood of causing an =
EAP
authentication session<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; to fail.&nbsp; For a system with a =
million
logins a day running EAP-TLS<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; mutual authentication with 15 =
round-trips, and
having a packet loss <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; probability of P=3D0.01%, we expect =
that 0.3% of
connections will experience <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; at least one lost packet.&nbsp; That =
is, 3,000
user sessions each day <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; will experience authentication =
failure.&nbsp;
This is an unacceptable<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; failure rate for a mass-market network =
service.
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; Using a reliable transport method such =
as TCP
means that RADIUS<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations can remove all
application-layer retransmissions, and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; instead rely on the Operating System =
(OS)
kernel's well-tested TCP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; transport to ensure reliable =
delivery.&nbsp; In
addition, most TCP<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations discover Path MTU =
better than
RADIUS application<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations, resulting in =
significantly
fewer fragmented packets.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Modern TCP implementations also =
implement
anti-spoofing provisions,<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; which is more difficult to do in UDP =
applications.<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; In contrast, use of TLS/TCP as a =
transport
between a NAS and a <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; RADIUS server is a poor fit.&nbsp; As =
noted in
[RFC3539] Section 2.1, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; for systems originating low numbers of =
RADIUS
request packets, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; inter-packet spacing is often larger =
than the
packet RTT, and<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; as a result, the congestion window =
will t
ypically not remain<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; above the minimum value on a long-term =
basis.
The <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; result is an increase in packets due =
to ACKs as
compared to UDP, <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; without a corresponding set of =
benefits.&nbsp; In
addition, the lack<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; of substantial traffic implies the =
need for
additional watchdog<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; traffic to confirm reachability.&nbsp; =
<o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; As a result, the objections to =
reliable
transport indicated in <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; [RFC2865] Section 2.4 continue to =
apply to
NAS-RADIUS server <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; communications and UDP SHOULD continue =
to be
used as the transport <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; protocol in this scenario.&nbsp; In =
addition,
it is recommended that<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; implementations of &quot;RADIUS =
Dynamic
AUthorization Extensions&quot; [RFC5176]<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; SHOULD continue to utilize UDP =
transport, since
the volume of<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; dynamic authorization traffic is =
usually
expected to be small.&nbsp; <o:p></o:p></p>

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

<p class=3DMsoNormal>&nbsp;&nbsp; Since &quot;bare&quot; TCP does not =
provide for
confidentiality or enable <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; negotiation of credible ciphersuites, =
its use
is not appropriate for <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; inter-server communications where =
strong
security is required.&nbsp; As a result <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; the use of &quot;bare&quot; TCP =
transport (i.e.
without TLS) is NOT RECOMMENDED <o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; for use in any situation, and there =
has been
little or no<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; operational experience with =
it.<o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_0066_01CAA4EC.6A4F27D0--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Wed, 03 Feb 2010 23:01:57 +0000
Message-ID: <BLU137-DS60EA45DB6619AE83D9CD693560@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: REMINDER:  Doodle Poll for RADEXT Virtual Interim Meeting
Date: Wed, 3 Feb 2010 15:01:01 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01CAA4E1.B3973AF0"
Thread-Index: AcqlJMGBswPppdhkSQKp4Ia3o90Sjg==
Content-Language: en-us

------=_NextPart_000_003B_01CAA4E1.B3973AF0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

RADEXT WG is going to hold a Virtual Interim meeting the week of February
22, 2010.   If you haven't already done so, please fill in your potentially
available times:

http://www.doodle.com/pc9p7y4dfb6fz48w

 

The major topic of discussion for the Virtual Interim  will be resolving the
"Last Look" comments on the Design Guidelines document.   


------=_NextPart_000_003B_01CAA4E1.B3973AF0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>RADEXT WG is going to hold a Virtual Interim =
meeting the
week of February 22, 2010.&nbsp;&nbsp; If you haven&#8217;t already done =
so, please fill
in your potentially available times:<o:p></o:p></p>

<p class=3DMsoNormal><a =
href=3D"http://www.doodle.com/pc9p7y4dfb6fz48w">http://www.doodle.com/pc9=
p7y4dfb6fz48w</a><o:p></o:p></p>

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

<p class=3DMsoNormal>The major topic of discussion for the Virtual =
Interim&nbsp; will
be resolving the &#8220;Last Look&#8221; comments on the Design =
Guidelines document.&nbsp;&nbsp;
<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_003B_01CAA4E1.B3973AF0--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 02 Feb 2010 21:30:27 +0000
Message-ID: <BLU137-DS5117ABCDA9D26AC23808593570@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <radiusext@ops.ietf.org>
Subject: New Doodle Poll on RADEXT Virtual Interim
Date: Tue, 2 Feb 2010 13:30:39 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0378_01CAA40B.E917FF60"
Thread-Index: AcqkTvbzttsXRkCcS5qjeTznqb3oDA==
Content-Language: en-us

------=_NextPart_000_0378_01CAA40B.E917FF60
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Here is a link to a new Doodle poll for the RADEXT Virtual Interim.  Due to
the two week notice requirement, the new poll is for the week of February
22-26, 2010. 

 

Doodle Poll:

http://www.doodle.com/pc9p7y4dfb6fz48w

 

 


------=_NextPart_000_0378_01CAA40B.E917FF60
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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>

<p class=3DMsoNormal>Here is a link to a new Doodle poll for the RADEXT =
Virtual
Interim.&nbsp; Due to the two week notice requirement, the new poll is =
for the week
of February 22-26, 2010. <o:p></o:p></p>

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

<p class=3DMsoNormal>Doodle Poll:<o:p></o:p></p>

<p class=3DMsoNormal><a =
href=3D"http://www.doodle.com/pc9p7y4dfb6fz48w">http://www.doodle.com/pc9=
p7y4dfb6fz48w</a><o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_0378_01CAA40B.E917FF60--

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


Envelope-to: radiusext-data0@psg.com
Delivery-date: Tue, 02 Feb 2010 19:59:46 +0000
Cc:  <radiusext@ops.ietf.org>
Message-Id: <E52BFEA6-E4F6-46EA-B7B2-E449254CF30B@elbrysnetworks.com>
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Doodle: RADEXT Virtual Interim
Date: Tue, 2 Feb 2010 14:58:58 -0500

On Jan 28, 2010, at 7:46 PM, Bernard Aboba wrote:

> I have gotten some reports that the DOODLE link for the RADEXT  
> Virtual Interim is behaving strangely.
>
> Try this link instead:
> http://www.doodle.com/9huzzmkgi4vrvvrm

That doesn't seem to work better.  The first "invite" sent to the list  
had already been "consumed" by Dan R. and the second "invite" didn't  
appear to be a valid "invite" .  The web site says to contact Bernard  
for an "invite" to add to the poll.



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

